Early IANA Allocation of Standards Track Code Points
draft-rfc4020bis-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Michelle Cotton | ||
| Last updated | 2013-02-11 (Latest revision 2012-09-04) | ||
| Replaced by | draft-cotton-rfc4020bis | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-cotton-rfc4020bis | |
| 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 a 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 that would normally trigger code point allocation. This document obsoletes RFC 4020.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)