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

…ESG or their delegate), with a Specification Required (using terminology from [ RFC5226 ]). However, to allow for the allocation of values prior to publication, the Designated Expert(s) may approve registration once they are satisfied that such a specification will be published. …

…or values that have been documented in a published RFC that has IETF Consensus [RFC5226]. This memo updates these registries as described below. Of note is the addition of a new "status" column. All registrations into these namespaces MUST include the name being registered, the d…

…egistry operates under either of the "IETF Review" or "IESG Approval" policies [RFC5226] for values between 0x00 and 0xef, with values between 0xf0 and 0xff being reserved for Experimental Use. New entries in this registry require the following information: Frame Type: A name or …

…racter subtags are assigned by IANA using the "IETF Review" policy defined by [ RFC5226 ]. This policy requires the development of an RFC, which SHALL define the name, purpose, processes, and procedures for maintaining the subtags. The maintaining or registering authority, includ…

…r values that have been documented in a published RFC that has IETF Consensus [ RFC5226 ]. This memo updates these registries as described below. Of note is the addition of a new "status" column. All registrations into these namespaces MUST include the name being registered, the …

…gistry operates under either of the "IETF Review" or "IESG Approval" policies [ RFC5226 ] for values between 0x00 and 0xef, with values between 0xf0 and 0xff being reserved for Experimental Use. New entries in this registry require the following information: Frame Type: A name or…

…es registry. Access token types 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…

…racter subtags are assigned by IANA using the "IETF Review" policy defined by [ RFC5226 ]. This policy requires the development of an RFC, which SHALL define the name, purpose, processes, and procedures for maintaining the subtags. The maintaining or registering authority, includ…

… the WebSocket Protocol in accordance with the principles set out in RFC 5226 [ RFC5226 ]. As part of this registry, IANA maintains the following information: Extension Identifier The identifier of the extension, as will be used in the |Sec-WebSocket-Extensions| header field regi…

…th the WebSocket Protocol in accordance with the principles set out in RFC 5226 RFC5226 ]. As part of this registry, IANA maintains the following information: Extension Identifier The identifier of the extension, as will be used in the |Sec-WebSocket-Extensions| header field regi…

…th the WebSocket Protocol in accordance with the principles set out in RFC 5226 RFC5226 ]. As part of this registry, IANA maintains the following information: Extension Identifier The identifier of the extension, as will be used in the |Sec-WebSocket-Extensions| header field regi…

…h the WebSocket protocol in accordance with the principles set out in RFC 5226 [RFC5226] As part of this registry IANA will maintain the following information: Extension Identifier The identifier of the extension, as will be used in the Sec-WebSocket-Extension header field regist…

…es registry. Access token types 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…

…ditions to this sub-registry is "IETF Review or IESG Approval" as described in [RFC5226]. The documentation of a Method Code should specify the semantics of a request with that code, including the following properties: o The Response Codes the method returns in the success case. …