Guidelines for Writing an IANA Considerations Section in RFCs

This RFC 2434 was published in 1998.

Abstract

Many protocols make use of identifiers consisting of constants and other well-known values.
Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., for a new option type in DHCP, or a new encryption or authentication algorithm for IPSec).
To insure that such quantities have consistent values and interpretations in different implementations, their assignment must be administered by a central authority.
For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA).

RFC 2434 introduction

Many protocols make use of fields that contain constants and other well-known values (e.g., the Protocol field in the IP header [IP] or MIME types in mail messages [MIME-REG]).
Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., a new option type in DHCP [DHCP] or a new encryption or authentication algorithm for IPSec [IPSEC]).
To insure that such fields have consistent values and interpretations in different implementations, their assignment must be administered by a central authority.
For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA).

Download links

Click here to download RFC 2434: TXT format PDF format (coming soon)

Related Request for Comments

Popular RFCs

©2015 RFC-Base.org - all rights reserved.