…ecification text Values to be added to this namespace require IETF Review (see [RFC5226], Section 4.1). 7.1.2. Considerations for New Cache Control Directives New extension directives ought to consider defining: o What it means for a directive to be specified multiple times, o Wh…

…fication text Values to be added to this name space are subject to IETF review [RFC5226], Section 4.1 ). Fielding, et al. Expires July 7, 2012 [Page 8] Internet-Draft HTTP/1.1, Part 2 January 2012 The registry itself is maintained at >. 2.2.1 . Considerations for New Methods When…

…ecification text Values to be added to this namespace require IETF Review (see [RFC5226], Section 4.1 ). 7.1.2 . Considerations for New Cache Control Directives New extension directives ought to consider defining: o What it means for a directive to be specified multiple times, o …

…es defined in Section 4.1 . Values are registered on a Specification Required [ RFC5226 ] basis after a three-week review period on the jwt-reg-review@ietf.org mailing list, on the advice of one or more Designated Experts. However, to allow for the allocation of values prior to p…

… Members of this family MUST be explicitly registered using the "IETF Review" [ RFC5226 ] registration procedure. Reviews MUST be requested on the SASL mailing list <sasl@ietf.org> (or a successor designated by the responsible Security AD). Note to future SCRAM-mechanism designer…

…rotocol. This registry operates under the "Expert Review" policy as defined in [RFC5226]. The designated expert is advised to encourage the inclusion of a reference to a permanent and readily available specification that enables the creation of interoperable implementations of th…

… explained in "Guidelines for Writing an IANA Considerations Section in RFCs" ([RFC5226]). Petrie & Channabasappa Standards Track [Page 46] RFC 6080 SIP Configuration Framework March 2011 Registrations with the IANA MUST include the profile type, and a published document that des…

…ition to the registry of reserved IID values, which requires Standards Action [ RFC5226 ] according to [ RFC5453 ]. Full deployment of a new reserved IID value would require updates to IID generation code in every deployed IPv6 stack, so the technical justification for such a Sta…

…below; future assignments are to be made through IETF Review or IESG Approval [ RFC5226 ]. Assignments consist of an extension token (as defined in Section 15.1 of [RFC5245] ) and a reference to the document defining the extension. Token Reference ----- --------- UDP RFC 5245, Se…

…ken_type_hint" (see Section 2.1) are registered with a Specification Required ([RFC5226]) after a two- week review period on the oauth-ext-review@ietf.org mailing list, on the advice of one or more Designated Experts. However, to allow for the allocation of values prior to public…

…n_type_hint" (see Section 2.1 ) are registered with a Specification Required ([ RFC5226 ]) after a two- week review period on the oauth-ext-review@ietf.org mailing list, on the advice of one or more Designated Experts. However, to allow for the allocation of values prior to publi…

…ecification text Values to be added to this namespace require IETF Review (see [RFC5226], Section 4.1). 5.1.2. Registrations The initial range unit registry contains the registrations below: +-------------+---------------------------------------+-------------+ | Range Unit | Desc…

…w definitions for scop values will be made following the "IETF Review" policy [ RFC5226 ]. For each future RFC that defines a Realm-Local scope for new network technologies (scop 3), IANA will add a reference to the defining document in the "IPv6 Multicast Address Scopes" registr…

…he form of the following template and is "Specification Required" per RFC 5226 [RFC5226]. URN: The URI that identifies the registered functionality. Common Name: The name by which the functionality being registered is generally known. Change Controller: For Standards Track RFCs, …

… The initial values are contained in this document. Using IANA Considerations [ RFC5226 ] terminology, entries that do not start with "vnd." are allocated by IETF Consensus, while those starting with "vnd." are allocated First Come First Served. 7 . Security Considerations Notifi…