Browse Prior Art Database

Procedure for Defining New DHCP Options (RFC2489)

IP.com Disclosure Number: IPCOM000003069D
Original Publication Date: 1999-Jan-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 4 page(s) / 10K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Droms: AUTHOR

Abstract

The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCP/IP network. Configuration parameters and other control information are carried in tagged data items that are stored in the 'options' field of the DHCP message. The data items themselves are also called "options."

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

Network Working Group R. Droms

Request for Comments: 2489 Bucknell University

BCP: 29 January 1999

Category: Best Current Practice

Procedure for Defining New DHCP Options

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 (1999). All Rights Reserved.

Abstract

The Dynamic Host Configuration Protocol (DHCP) provides a framework

for passing configuration information to hosts on a TCP/IP network.

Configuration parameters and other control information are carried in

tagged data items that are stored in the 'options' field of the DHCP

message. The data items themselves are also called "options."

New DHCP options may be defined after the publication of the DHCP

specification to accommodate requirements for conveyance of new

configuration parameters. This document describes the procedure for

defining new DHCP options.

1. Introduction

The Dynamic Host Configuration Protocol (DHCP) [1] provides a

framework for passing configuration information to hosts on a TCP/IP

network. Configuration parameters and other control information are

carried in tagged data items that are stored in the 'options' field

of the DHCP message. The data items themselves are also called

"options." [2]

This document describes the procedure for defining new DHCP options.

The procedure will guarantee that:

* allocation of new option numbers is coordinated from a single

authority,

* new options are reviewed for technical correctness and

appropriateness, and

* documentation for new options is complete and published.

As indicated in "Guidelines for Writing an IANA Considerations

Section in RFCs" (see references), IANA acts as a central authority

for assignment of numbers such as DHCP option codes. The new

procedure outlined in this document will provide guidance to IANA in

the assignment of new option codes.

2. Overview and background

The procedure described in this document modifies and clarifies the

procedure for defining new options in RFC 2131 [2]. The primary

modification is to the time at which a new DHCP option is assigned an

option number. In the procedure described in this document, the

option number is not assigned until specification for the option is

about to be published as an RFC.

Since the publication of RFC 2132, the option number space for

publically defined DHCP options (1-127) has almost been exhausted.

Many of the defined option numbers have not been followed up with

Internet Drafts submitted to the DHC WG. There has been a lack of

specific guidance to IANA from the DHC WG as to the assignment of

DHCP option numbers

The procedure as specified ...