HTTP/2 200 date: Mon, 14 Jul 2025 15:56:17 GMT content-type: application/xml cache-control: public, max-age=3600 cross-origin-opener-policy: same-origin expires: Mon, 14 Jul 2025 16:56:16 GMT referrer-policy: same-origin vary: Cookie, origin, Accept-Encoding x-content-type-options: nosniff x-frame-options: DENY x-resolution-methods: manual;auto;fallback x-resolution-outcomes: ;RfcSubseriesAdapter: using docid IETF BCP 100 -> using query @.type == "IETF" && @.primary == true && @.id like_regex "(?i)^BCP[^a-zA-Z0-9]100$" -> 1 found,; last-modified: Mon, 14 Jul 2025 15:56:16 GMT cf-cache-status: EXPIRED server: cloudflare cf-ray: 95f23585fd683585-BLR content-encoding: gzip alt-svc: h3=":443"; ma=86400 This memo describes the process for early allocation of code points by IANA from registries for which "Specification Required", "RFC Required", "IETF Review", or "Standards Action" policies apply. This process can be used to alleviate the problem where code point allocation is needed to facilitate desired or required implementation and deployment experience prior to publication of an RFC, which would normally trigger code point allocation. The procedures in this document are intended to apply only to IETF Stream documents.