Protocol Action: Dynamic Host Configuration Protocol to Draft Standard

The IESG <iesg-secretary@CNRI.Reston.VA.US> Wed, 29 January 1997 18:49 UTC

Received: from by id aa25211; 29 Jan 97 13:49 EST
Received: from by id aa24751; 29 Jan 97 13:42 EST
To: IETF-Announce:;
Cc: RFC Editor <>
Cc: Internet Architecture Board <>
From: The IESG <iesg-secretary@CNRI.Reston.VA.US>
Subject: Protocol Action: Dynamic Host Configuration Protocol to Draft Standard
Date: Wed, 29 Jan 1997 13:42:27 -0500
Message-ID: <>

  The IESG has approved the following documents:

    1. Dynamic Host Configuration Protocol
    2. DHCP Options and BOOTP Vendor Extensions
    3. Interoperation Between DHCP and BOOTP
    4. Clarifications and Extensions for the Bootstrap Protocol

  as Draft Standards. These documents are the product of the Dynamic
  Host Configuration Working Group. The IESG contact persons are Frank
  Kastenholz and Jeffrey Burgan.

Technical Summary

  The first document describes The Dynamic Host Configuration Protocol
  (DHCP) which provides a framework for passing configuration
  information to hosts on a TCP/IP network.  DHCP is based on the
  Bootstrap Protocol (BOOTP), adding the capability of automatic
  allocation of reusable network addresses and additional configuration
  options. 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. "The second document specifies the current set of DHCP
  options. The third document describes the interactions between DHCP
  and BOOTP network participants. DHCP provides a superset of the
  functions provided by BOOTP. The last document attempts to clarify
  and strengthen the BOOTP protocol specification which was loosely
  defined in the original specification.

Working Group Summary

   The Working Group came to consensus and there were no significant
   changes as the result of the last call.

Protocol Quality

   These protocols have been reviewed by Frank Kastenholz and Jeffrey Burgan
   of the IESG. There are several independent implementations of DHCP
   available today. A partial list includes:

	FTP     Microsoft       cisco   Sun     IBM

Included below is a list of information about several DHCP implementations,
in support if the requirement for independent, interoperable
implementations before acceptance of the protocol specification as a Draft
Standard.  The list is only a partial list of available implementation; I