Early IANA Code Point Allocation for IETF Stream Internet-Drafts
draft-baber-ianabis-rfc7120bis-01
| Document | Type | Replaced Internet-Draft (ianabis WG) Expired & archived | |
|---|---|---|---|
| Authors | Amanda Baber , Sabrina Tanamal | ||
| Last updated | 2025-09-19 | ||
| Replaces | draft-iana-ianabis-rfc7120bis | ||
| Replaced by | draft-ietf-ianabis-rfc7120bis | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Best Current Practice | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-ianabis-rfc7120bis | |
| Consensus boilerplate | Yes | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This memo describes the requirements for securing IANA code point assignments before RFC publication. In particular, it describes the "early allocation" process that allows for temporary but renewable allocations from registries that would ordinarily require an IESG- approved Internet-Draft: primarily, registries maintained in accordance with the "Standards Action," "IETF Review," "RFC Required," and, in some cases, "Specification Required" policies described in RFC 8126. This process can be used when code point allocation is needed to facilitate desired or required implementation and deployment experience prior to publication. The procedures in this document are intended to apply only to IETF Stream documents. This document obsoletes RFC 7120.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)