Defining the Role and Function of the IETF-IANA
draft-huston-iana-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Geoff Huston , Scott O. Bradner | ||
| Last updated | 2002-10-22 | ||
| Replaced by | RFC 6220 | ||
| 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-iab-iana | |
| 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 role and function of the IETF-IANA. Many IETF protocols make use of commonly defined values that are passed within protocol objects. To ensure consistent interpretation of these values between independent implementations, there is a need to ensure that the values and associated semantic intent are uniquely defined. The IETF uses a single registry to register these protocol values and their associated semantic intent. In this memo the registry function is referred to as the IETF Internet Assigned Numbers Authority (IETF-IANA). This document provides a description of this function and proposes that this description be adopted by the Internet Architecture Board (IAB).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)