…registration procedure "IETF Consensus", which was changed to "IETF Review" by [RFC8126]. To align with the new terminology, IANA has updated the following registries to "IETF Review": o TLS Authorization Data Formats [RFC4680] o TLS Supplemental Data Formats (SupplementalDataTyp…

… registration procedure "IETF Consensus", which was changed to "IETF Review" by RFC8126 ]. To align with the new terminology, IANA has updated the following registries to "IETF Review": o TLS Authorization Data Formats [ RFC4680 o TLS Supplemental Data Formats (SupplementalDataTy…

… RFC-ietf-tls-tls12-frozen-08 ][ RFC9847 Note If the "Specification Required" [ RFC8126 ] procedure applies, registration requests can be sent to iana@iana.org or submitted via IANA's [ application form ], per [ RFC9847 ]. IANA will forward the submission to the expert mailing li…

… RFC-ietf-tls-tls12-frozen-08 ][ RFC9847 Note If the "Specification Required" [ RFC8126 ] procedure applies, registration requests can be sent to iana@iana.org or submitted via IANA's [ application form ], per [ RFC9847 ]. IANA will forward the submission to the expert mailing li…

…rations in this registry are assigned using the Specification Required policy ( RFC8126 ), except for values between 0x00 and 0x3f (in hexadecimal; inclusive), which are assigned using Standards Action or IESG Approval as defined in Sections 4.9 and 4.10 of RFC8126 While this reg…

…gistry operates under either of the "IETF Review" or "IESG Approval" policies [ RFC8126 ] for values from 0x00 up to and including 0xef, with values from 0xf0 up to and including 0xff being reserved for Experimental Use. While this registry is separate from the "HTTP/2 Frame Type…

…rations in this registry are assigned using the Specification Required policy ( RFC8126 ), except for values between 0x00 and 0x3f (in hexadecimal; inclusive), which are assigned using Standards Action or IESG Approval as defined in Sections 4.9 and 4.10 of RFC8126 While this reg…

…F-8 data are to be allocated according to the "First Come First Served" policy [RFC8126]. Lhomme, et al. Expires 14 October 2026 [Page 39] Internet-Draft Matroska Tags April 2026 * binary: the value of the Tag is stored in TagBinary, Matroska Tag Names for binary data are to be a…

… using Standards Action or IESG Approval as defined in Sections 4.9 and 4.10 of RFC8126 Permanent registrations for values larger than 0x3f, which are assigned using the Specification Required policy ( RFC8126 Provisional registrations for values larger than 0x3f, which require E…

…licitly requested. Adding a value with a value of "Y" requires Standards Action RFC8126 Reference: The specification where the ECHConfigExtension is defined Notes: Any notes associated with the entry New entries in the "ECHConfig Extension" registry are subject to the Specificati…

…his registry operates under the "Specification Required" policy as defined in [ RFC8126 ]. The designated expert will require the inclusion of a reference to a permanent and readily available specification that enables the creation of interoperable implementations using the ident…

…cification, a new IANA registry has been created, following the procedures in [ RFC8126 ] , for the namespace associated with the "UDP/DTLS/SCTP" and "TCP/DTLS/SCTP" protocol identifiers. Each fmt value describes the usage of an entire SCTP association, including all SCTP streams…

…nt of new message types is done through an RFC Required action, as defined in [ RFC8126 ] . Documentation of new message types MUST contain the following information: ¶ A name for the new message type. ¶ A detailed procedural description of how each message type is used with with…

…review@ietf.org mailing list, on the advice of one or more Designated Experts [ RFC8126 ]. However, to allow for the allocation of values prior to publication, the Designated Experts may approve registration once they are satisfied that such a specification will be published. Reg…

…a key length of one use the Specification Required policy, per Section 4.6 of [ RFC8126 Registration requests for priority parameters with a key length greater than one use the Expert Review policy, per Section 4.5 of [ RFC8126 . A specification document is appreciated but not re…