2.3.2 Dynamic Host Configuration (dhc)

NOTE: This charter is a snapshot of the 41st IETF Meeting in Los Angeles, California. It may now be out-of-date. Last Modified: 22-Jan-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 acceptance 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

Minutes of the Dynamic Host Configuration (dhc) Working Group

The WG met first to discuss DHCPv4 issues. Mike Carney (Sun) reported on the DHCP futures panel. He presented the panel's charge and agenda. The panel will proceed to consider and resolve the agenda items.

Charlie Perkins (Sun) reviewed recent changes to options 78 and 79 (for SLP); these changes track changes to SLP. The I-D for these options will be submitted for WG last call.

Ralph Droms (Bucknell) reported that Yakov Rekhter (cisco) requested that the DHCP-DNS draft (version -08) be submitted for WG last call. Several members of the WG expressed a need for more description of the mechanism through which a DHCP server updates the A record for a DHCP client. The consensus of the WG was that more work is needed on the case in which the DHCP server updates the client's A record. Kim Kinnear (American Internet) will draft specific changes for the draft by mid-May.

Barr Hibbs (Pacific Bell) described his draft DHCP server MIB. There was sufficient interest from the WG to continue working on the DHCP server MIB.

Peter Ford (Microsoft) described Microsoft's automatic address allocation for IPv4, which is similar in concept to IPv6 link-local addresses. Microsoft is applying for a defensive patent on this technology.

Ed Lewis (TIS) (for Olafur Gudmundsson (TIS)) presented a set of requirements for DHCP authentication. Peter Ford volunteered to put together a panel to move forward on authentication. Ford also proposed that an interim meeting be held to discuss security.

Mike Henry (Intel) described his options for systems. After much discussion within the WG as to the need for these options (perhaps duplicating function of vendor identifier?), the WG agreed to push discussion off to the mailing list.

Richard Woundy (American Internet) described a "third-party query" protocol that would allow DHCP relay agents and management tools to retrieve information from DHCP servers.

Ted Lemon (ISC) responded to Thomas Narten's comments about the agent options draft. Mike Patrick (Motorola) will submit a revised draft based on Narten's comments.

Kim Kinnear (American Internet) and Ralph Droms (Bucknell) led a discussion of the safe failover and failover protocol drafts. There was sufficient interest in the WG to continue pursuing this protocol. The WG expressed consensus in desiring that the two drafts be merged into a single protocol specification, and all parts of that protocol should be mandatory. The authors of the two drafts (spec., Kinnear and Arun Kapur (Quadritek)) have agreed to merge their documents into a single draft.

In the DHCPv6 meeting, Charlie Perkins (Sun) reviewed changes to the v6 specs based on input from the DC WG meeting and from responses to the WG last call. The consensus of the WG was to submit the docs for IETF last call after the authors make a final revision based on input from the WG at the meeting.


None Received

Attendees List

go to list