2.3.2 Dynamic Host Configuration (dhc)

NOTE: This charter is a snapshot of the 42nd IETF Meeting in Chicago, Illinois. It may now be out-of-date. Last Modified: 23-Jul-98


Ralph Droms <droms@bucknell.edu>

Internet Area Director(s):

Jeffrey Burgan <burgan@home.net>
Thomas Narten <narten@raleigh.ibm.com>

Internet Area Advisor:

Thomas Narten <narten@raleigh.ibm.com>

Mailing Lists:

General Discussion:dhcp-v4@bucknell.edu
To Subscribe: listserv@bucknell.edu
In Body: subscribe listname Your Name
Archive: Send email to listserv@bucknell.edu with HELP as the text.

Description of Working Group:

This working group will produce a protocol for automated allocation, configuration and management of IP addresses and TCP/IP protocol stack parameters. Specific functions to be included in the protocol include:

o Automated allocation and recovery of IP addresses

o Automated configuration of all TCP/IP stack parameters, as described in the Host Requirements documents

o Interaction between DHCP and DNS dynamic update protocol (ddns)

o Automated configuration of other host parameters such as application layer services

o Inter-server communication for coordination of multiple servers

o Mechanisms for the authentication of clients and servers

A specification the Dynamic Host Configuration Protocol (DHCP) for IPv4 has been entered into the IETF standards track. As of 3/97, it has been accepted as a "Draft Standard". The working group is also developing a specification for DHCP for IPv6 (DHCPv6), which is currently available as an Internet Draft.

More information on DHCP and the DHC WG can be found at http://www.bucknell.edu/~droms/dhcp.

Other DHC Lists:

General Discussion: dhcp-v4@bucknell.edu DHCP-DNS Interaction: dhcp-dns@bucknell.edu Implementation issues: dhcp-impl@bucknell.edu Bakeoff events: dhcp-bake@bucknell.edu Inter-server protocol: dhcp-serve@bucknell.edu DHCP for IPv6: dhcp-v6@bucknell.edu Implementation issues for DHCPv6: dhcp-v6impl@bucknell.edu

Goals and Milestones:



Revise the DHCPv6 Internet-Draft for discussion at the Dallas IETF meeting.



Submit the DHCP options specification to the IESG for consideration as a Draft Standard.



Submit server-server protocol specification as an Internet-Draft.



Submit FQDN, option 127 and option acceptence process documents to IESG for consideration as a Proposed Standard.



Develop options for automated registration in DNS.



Submit the DHCPv6 Protocol and options specification for WG Last Call.

Nov 97


Complete revisions to the DHCPv6 protocol specifications based on response to the IETF Last Call.

Dec 97


Submit the DHCPv6 protocol specifications to the IESG for consideration as a Proposed Standard.

Sep 98


Submit the DHCP Protocol specification to the IESG for consideration as an Internet Standard.


Request For Comments:







Interoperation Between DHCP and BOOTP



Clarifications and Extensions for the Bootstrap Protocol



DHCP Options and BOOTP Vendor Extensions



Dynamic Host Configuration Protocol



DHCP Options for Novell Directory Services



Netware/IP Domain Name and Information

Current Meeting Report

These minutes were prepared by Ralph Droms; thanks to Barr Hibbs for taking notes
during the meetings and to the WG for revisions and corrections to the minutes.

The WG met twice on 8/24. Several issues were discussed in the morning session.
DHCP authentication and the web proxy server option were discussed in the afternoon
session. The morning session included the following topics; any WG action associated
with each topic is included with the topic summary:

- Relay options draft, Mike Patrick (Motorola): summary of changes to option spec
based on input from WG; WG agreed to WG last call and submit this option for
Proposed Standard status

- DHCP in cable modem nets, Poornima Lalwaney (General Instruments): described
use of DHCP in both RF and telco return cable systems, asked that WG consider
additional DHCP functions to support cable modem operation: server MIB, 3rd
party query, relay agent information option; WG asked that the proposed use of
DHCP be published as an I-D

- VAMAC agent sub-option, Burcak Beser (3Com): described proposed sub-option
to relay agent information option for "virtual agent" operation; WG asked that the
proposed sub-option be published as an I-D; WG also asked that Beser and
Lalwaney consider merging their proposals into a single document

- New process for allocating option numbers, Ralph Droms (Bucknell): reviewed
modified process published in <draft-ietf-dhc-new-options-02.txt>; WG asked
process be modified so option number is assigned when RFC for new option is
published; WG agreed to WG last call after editorial changes and submit this
option for Informational status (to be merged into RFC2132 when DHCP goes to
Standard status)

- Host systems characteristics options, Mike Henry (Intel): reviewed changes to host
systems characteristics options and changes to WFM spec that accommodate use
of existing options, and asked that the WG change the 'client identifier' option to
be a globally unique identifier; WG agreed to change, and agreed to publish host
systems characteristics options as Informational, with limitation on use of these
options to 6 years; WG asked that relevant text from WFM docs be extracted into
I-D for DHC WG

- DHCP futures panel, Mike Carney (Sun): reported that there is a new draft of
recommendations from the futures panel

- DHCP autoconfiguration control, Ryan Troll (CMU): reviewed a proposal for a
draft of an option that controls use of autop-configuration by DHCP hosts; WG
agreed to WG last call four weeks after revised draft published and submit for
Proposed Standard status

- DHCP MIB, Glenn Waters (BayNetworks): announced that new server MIB would
be available in two weeks

- There was an expression of interest in development of DHCP schema, with the
suggestion for an interim meeting to work on convergence of the several (3?)
outstanding proposals

- User authentication server option, Steve Drach (Sun): described option to provide
URL of NC authentication server; WG agreed to go to WG last call 4 weeks after
publication of revised draft and submit option for Propsoed Standard

- Safe failover protocol, Bernie Volz (Process): described protocol resulting from
merger of failover and safe failover I-Ds <draft-ietf-dhc-failover-02.txt>

In the afternoon session, Ralph Droms reviewed the minutes from the interim meeting
on DHC authentication from June. Bill Arbaugh described the Schiller/Huitema/
Droms/Arbaugh (SHDA) protocol, which performs "delayed authentication" based on
discussion at the interim meeting. The outcome of the interim working group was to
recommend the SHDA and Patel protocols to the WG. The WG agreed to select the
SHDA protocol for future development.

Finally, Josh Cohen (Microsoft) described the web proxy server option. There was
discussion of the advisability of combining this option with the authentication server
option in a general purpose "typed URL option". The WG came to consensus that the
two options should be left separate and the URL option should be considered for the
expanded option space (recommended by the futures panel). The WG acknowledged
that the current options space is nearly exhausted; Mike Carney agreed to investigate
recovering some of the option space in 128-254 and Ralph Droms agreed to try to
recover previously assigned options that have not been used.


Session Agenda
Review of 6/98 Interim Meeting on DHCP Authentication
VAMAC Agent Sub-Option
VAMAC Agent Sub-Option

Attendees List

go to list