…nt (ACME) Protocol" and are administered under a Specification Required policy [RFC8126]. 9.7.1. Fields in Account Objects The "ACME Account Object Fields" registry lists field names that are defined for use in ACME account objects. Fields marked as "configurable" may be included…

…Layer Security", and assignments are made via the Specification Required policy RFC8126 . See Section 16.5 for additional information about the MLS Designated Experts (DEs). RFC EDITOR: Please replace XXXX throughout with the RFC number assigned to this document 16.1. MLS Ciphers…

…Provisional registrations require Expert Review, as defined in Section 4.5 of [ RFC8126 . The designated expert or experts are advised that only registrations for an excessive proportion of remaining codepoint space or the very first unassigned value (see Section 22.1.2 ) can be …

…y has been created to use the "Expert Review Required" registration procedure [ RFC8126 ]. Guidelines for the experts are provided in Section 16.11 . It should be noted that, in addition to the expert review, some portions of the registry require a specification, potentially a St…

…ry has been created to use the "Expert Review Required" registration procedure [RFC8126]. Guidelines for the experts are provided in Section 16.11. It should be noted that, in addition to the expert review, some portions of the registry require a specification, potentially a Stan…

…pecification text Values to be added to this namespace require IETF Review (see RFC8126 ], Section 4.8 ). 16.1.2. Considerations for New Methods Standardized methods are generic; that is, they are potentially applicable to any resource, not just one particular media type, kind of…

…ts are assigned by the "IETF Review" or "IESG Approval" procedures described in RFC8126 ]. User Ports are assigned by IANA using the "IETF Review" process, the "IESG Approval" process, or the "Expert Review" process, as per RFC6335 ]. Dynamic Ports are not assigned. The registrat…

…ion Functions (VDAF)", and administered under the Specification Required policy RFC8126 The "VDAF Identifiers" registry lists identifiers for Distributed Aggregation Functions (DAFs) and Verifiable Distributed Aggregation Functions (VDAFs). These identifiers are four-byte values,…

…ocedure(s) Reserved ranges may be allocated in accordance with section 4.3 of [ RFC8126 ]. Reference RFC7252, Section 12.1 Available Formats CSV Code Description Reference 0.00 Indicates an Empty message. RFC7252, section 4.1 0.01-0.31 Indicates a request. Values in this range ar…

…ssignments in this registry are to be defined by Standards Action as defined by RFC8126 . Assignments consist of the MPTCP subtype's symbolic name, its associated value, and a reference to its specification. 7.3. MPTCP Handshake Algorithms The "MPTCP Handshake Algorithms" subregi…

…ecification text Values to be added to this namespace require IETF Review (see [RFC8126] Section 4.8 ). 16.1.2. Considerations for New Methods Standardized methods are generic; that is, they are potentially applicable to any resource, not just one particular media type, kind of r…

…ocedure(s) Reserved ranges may be allocated in accordance with section 4.3 of [ RFC8126 ]. Reference RFC7252, Section 12.1 Available Formats CSV Code Description Reference 0.00 Indicates an Empty message. RFC7252, section 4.1 0.01-0.31 Indicates a request. Values in this range ar…

…pecification text Values to be added to this namespace require IETF Review (see RFC8126 ], Section 4.8 ). 16.1.2. Considerations for New Methods Standardized methods are generic; that is, they are potentially applicable to any resource, not just one particular media type, kind of…

…y has been created to use the "Expert Review Required" registration procedure [ RFC8126 ]. Guidelines for the experts are provided in Section 16.11 . It should be noted that, in addition to the expert review, some portions of the registry require a specification, potentially a St…

…Indication when set * Reference The registration procedure is Standards Action [RFC8126]. The initial allocation is as indicated in Table 24: +============+======================+===========+ | Bit Number | Indication When Set | Reference | +============+======================+==…