Browse Prior Art Database

Guidelines for Writing an IANA Considerations Section in RFCs (RFC2434)

IP.com Disclosure Number: IPCOM000003012D
Original Publication Date: 1998-Oct-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 9 page(s) / 23K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

T. Narten: AUTHOR [+2]

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).

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 13% of the total text.

Network Working Group T. Narten

Request for Comments: 2434 IBM

BCP: 26 H. Alvestrand

Category: Best Current Practice Maxware

October 1998

Guidelines for Writing an IANA Considerations Section in RFCs

Status of this Memo

This document specifies an Internet Best Current Practices for the

Internet Community, and requests discussion and suggestions for

improvements. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1998). All Rights Reserved.

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).

In order for the IANA to manage a given name space prudently, it

needs guidelines describing the conditions under which new values can

be assigned. If the IANA is expected to play a role in the management

of a name space, the IANA must be given clear and concise

instructions describing that role. This document discusses issues

that should be considered in formulating a policy for assigning

values to a name space and provides guidelines to document authors on

the specific text that must be included in documents that place

demands on the IANA.

Table of Contents

Status of this Memo.......................................... 1

1. Introduction............................................. 2

2. Issues To Consider....................................... 3

3. Registration maintenance................................. 6

4. What To Put In Documents................................. 7

5. Applicability to Past and Future RFCs.................... 8

6. Security Considerations.................................. 8

7. Acknowledgments.......................................... 9

8. References............................................... 9

9. Authors' Addresses....................................... 10

10. Full Copyright Statement................................. 11

1. 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 encrypti...