…licy for additions to this registry is "Specification Required" as defined in [ RFC8126 ] (which involves an Expert Review) for names that do not include an internal dot and "IETF Review" for names that do include an internal dot. The expert reviewer is specifically instructed th…

…uired" policy for values 256-16383, and under "Experimental Use" otherwise (see RFC8126 for the definition of relevant policies). Experimental Use extensions can be used both on private networks and over the open Internet. The procedures for requesting values in the Specification…

… [DSS] or [RFC7748]. Values 0xFE00 through 0xFEFF are reserved for Private Use [RFC8126]. Finite Field Groups (DHE): Indicates support for the corresponding finite field group, defined in [RFC7919]. Values 0x01FC through 0x01FF are reserved for Private Use. Items in named_group_l…

…licy for additions to this registry is "Specification Required" as defined in [ RFC8126 ] (which involves an Expert Review) for names that do not include an internal dot and "IETF Review" for names that do include an internal dot. The expert reviewer is specifically instructed th…

…stored. New registrations happen on a "RFC Required" basis (see Section 4.7 of [RFC8126]). The attribute to be registered MUST match the "extension-av" syntax defined in Section 4.1.1. Note that attribute names are generally defined in CamelCase, but technically accepted case-ins…

…of one or more experts, with a Specification Required (using terminology from [ RFC8126 ]). The experts' primary considerations in evaluating registration requests are: o Conformance to the requirements in Section 3 o The availability and stability of the specifying document o Th…

… Values to be added to this namespace require IETF Review (see Section 4.8 of [ RFC8126 ) and MUST conform to the purpose of transfer coding defined in this specification. Use of program names for the identification of encoding formats is not desirable and is discouraged for futu…

… Values to be added to this namespace require IETF Review (see Section 4.8 of [ RFC8126 ) and MUST conform to the purpose of transfer coding defined in this specification. Use of program names for the identification of encoding formats is not desirable and is discouraged for futu…

…pes are registered using the Specification Required policy (see Section 4.6 of [RFC8126] ), which implies review and approval by a designated expert. The goal of the registry is to reflect common use of links on the Internet. Therefore, the expert(s) should be strongly biased tow…

… entries in this registry are subject to an Expert Review registration policy ( RFC8126 ], Section 4.5 ). The designated expert MUST ensure that the Format Reference is stable and publicly available, and that it specifies how to convert the SvcParamValue's presentation format to …

…pes are registered using the Specification Required policy (see Section 4.6 of [RFC8126] ), which implies review and approval by a designated expert. The goal of the registry is to reflect common use of links on the Internet. Therefore, the expert(s) should be strongly biased tow…

…n this registry are subject to the Specification Required registration policy ( RFC8126 ], Section 4.6 ). Designated experts need to ensure that the token type is defined to be used for both token issuance and redemption. Additionally, the experts can reject registrations on the …

…pes are registered using the Specification Required policy (see Section 4.6 of [RFC8126] ), which implies review and approval by a designated expert. The goal of the registry is to reflect common use of links on the Internet. Therefore, the expert(s) should be strongly biased tow…

…DSS ] or RFC7748 ]. Values 0xFE00 through 0xFEFF are reserved for Private Use [ RFC8126 ]. Finite Field Groups (DHE): Indicates support for the corresponding finite field group, defined in [ RFC7919 ]. Values 0x01FC through 0x01FF are reserved for Private Use. Items in named_grou…

… Public Key Encryption", and administered under a Specification Required policy RFC8126 11.1. KEM Identifiers The "HPKE KEM Identifiers" registry lists identifiers for key encapsulation algorithms defined for use with HPKE. These identifiers are two-byte values, so the maximum po…