Update of and Clarification to IANA Policy Definitions in BCP 26
draft-leiba-iana-policy-update-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Barry Leiba | ||
| Last updated | 2012-11-05 (Latest revision 2012-04-24) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
Section 4.1 of BCP 26 (RFC 5226) discusses possible IANA registration policies that might be used in documents with IANA actions, and defines some well-known policy terms. This document clarifies the usage of these terms, and discourages the use of overly restrictive registration policies. The author is working with IANA on an update to BCP 26, and this document's contents will be folded into that effort. While that's in process, this draft will be kept alive for reference.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)