…Notes (optional) Values to be added to this namespace require IETF Review (see [RFC5226] Section 4.1 ). 5.1.2. Considerations for New Authentication Schemes There are certain aspects of the HTTP Authentication Framework that put constraints on how new authentication schemes can w…

…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 Name Description Reference bytes a range of octets Section 2.1 none reserved a…

…ESG or their delegate), with a Specification Required (using terminology from [ RFC5226 ]). The requirements for registered relation types are described in Section 4.1 Registration requests consist of the completed registration template below, typically published in an RFC or Ope…

…RN namespaces is Expert Review as defined in the IANA Considerations document [ RFC5226 ]. For URN namespaces or their definitions that are intended to become standards or constituent parts of standards, the output of the Expert Review process is intended to be a report rather th…

…ESG or their delegate), with a Specification Required (using terminology from [ RFC5226 ]). The requirements for registered relation types are described in Section 4.1 Registration requests consist of the completed registration template below, typically published in an RFC or Ope…

…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 …

…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 …

…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…

…specification. The registration procedure for values is Specification Required [RFC5226] after a three-week review period on the jose-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 publica…

…n the "IANA Considerations" section of a document that has passed IETF Review [ RFC5226 ]. The "IANA Considerations" section must include all of the information specified in Section 2.2.1 of this document. 2.2.1 . Information Requirements The IPv4 and IPv6 Special-Purpose Address…

…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…

…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…

…. 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 Notifica…