Guidelines for Writing an IANA Considerations Section in RFCs
draft-leiba-cotton-iana-5226bis-04

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2014-05-16 (latest revision 2013-11-12)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Reviews
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-leiba-cotton-iana-5226bis-04.txt

Abstract

Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values used in these fields do not have conflicting uses, and to promote interoperability, their allocation is often coordinated by a central authority. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA). To make assignments in a given namespace prudently, IANA needs guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the guidance given to IANA is clear and addresses the various issues that are likely in the operation of a registry. This is the third edition, and obsoletes RFC 5226.

Authors

Michelle Cotton (michelle.cotton@icann.org)
Barry Leiba (barryleiba@computer.org)
Thomas Narten (narten@us.ibm.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)