Initial Assignment for the Content Security Policy Directives Registry
RFC 7762


Document	Type	RFC - Informational (January 2016; No errata) Was draft-west-webappsec-csp-reg (individual)
	Last updated	2016-01-28
	Stream	IETF
	Formats	plain text pdf html bibtex
Stream	WG state	(None)
	Document shepherd	Mark Nottingham
	Shepherd write-up	Show (last changed 2015-10-11)
IESG	IESG state	RFC 7762 (Informational)
	Consensus Boilerplate	Yes
	Telechat date
	Responsible AD	Barry Leiba
	Send notices to	(None)
IANA	IANA review state	Version Changed - Review Needed
	IANA action state	RFC-Ed-Ack

Email authors IPR References Referenced by Nits

Internet Engineering Task Force (IETF)                           M. West
Request for Comments: 7762                                   Google, Inc
Category: Informational                                     January 2016
ISSN: 2070-1721

 Initial Assignment for the Content Security Policy Directives Registry

Abstract

   This document establishes an Internet Assigned Number Authority
   (IANA) registry for Content Security Policy directives and populates
   that registry with the directives defined in the Content Security
   Policy Level 2 specification.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7762.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

West                          Informational                     [Page 1]
RFC 7762      Content Security Policy Registry Assignments  January 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Use of the Registry . . . . . . . . . . . . . . . . . . . . .   2
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Content Security Policy Directives Registry . . . . . . .   3
     4.2.  Registration Policy for Content Security Policy
           Directives  . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The Content Security Policy (CSP) specification [CSP] defines a
   mechanism that web developers can use to control the resources that a
   particular page can fetch or execute, as well as a number of
   additional security-relevant policy decisions.

   The policy language specified in that document consists of an
   extensible set of "directives", each of which controls a specific
   resource type or policy decision.  This specification establishes a
   registry to ensure that extensions to CSP are listed and
   standardized.

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

3.  Use of the Registry

   Content Security Policy directives must be documented in a readily
   available public specification in order to be registered by IANA.
   This documentation MUST fully explain the syntax, intended usage, and
   semantics of the directive.  The intent of this requirement is to
   assure interoperable independent implementations, and to prevent
   accidental namespace collisions between implementations of dissimilar
   features.

   Documents defining new Content Security Policy directives MUST
   register them with IANA, as described in Section 3.  The IANA

West                          Informational                     [Page 2]
RFC 7762      Content Security Policy Registry Assignments  January 2016

   registration policy for such parameters is "Specification Required"

Show full document text

Initial Assignment for the Content Security Policy Directives RegistryRFC 7762

Initial Assignment for the Content Security Policy Directives Registry
RFC 7762