2.3.7 Dynamic Host Configuration (dhc)

NOTE: This charter is a snapshot of the 71st IETF Meeting in Philadelphia, PA USA. It may now be out-of-date.
In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at:

       Additional DHC Page

Last Modified: 2008-01-21

Chair(s):

Ralph Droms <rdroms@cisco.com>
John Jason Brzozowski <john_brzozowski@cable.comcast.com>

Internet Area Director(s):

Jari Arkko <jari.arkko@piuha.net>
Mark Townsley <townsley@cisco.com>

Internet Area Advisor:

Jari Arkko <jari.arkko@piuha.net>

Mailing Lists:

General Discussion: dhcwg@ietf.org
To Subscribe: http://www1.ietf.org/mailman/listinfo/dhcwg
Archive: http://www.ietf.org/mail-archive/web/dhcwg/index.html

Description of Working Group:

The dhc working group (DHC WG) has developed DHCP for automated
allocation, configuration and management of IP addresses and TCP/IP
protocol stack parameters. DHCPv4 is currently a "Draft Standard" and
is documented in RFC 2131 and RFC 2132. DHCPv6 is currently a
"Proposed Standard" and is documented in RFC 3315. Subsequent RFCs
document additional options and other enhancements to the
specifications.

The DHC WG is responsible for reviewing (and sometimes developing)
DHCP options or other extensions (for both IPv4 and IPv6). The DHC WG
is expected to review all proposed extensions to DHCP to ensure that
they are consistent with the DHCP specification and other option
formats, that they do not duplicate existing mechanisms, etc. The DHC
WG will not (generally) be responsible for evaluating the semantic
content of proposed options. The DHC WG will not adopt new proposals
for extensions to DHCP as working group documents without first
coordinating with other relevant working groups and determining who
has the responsibility for reviewing the semantic content of an
option.

The DHC WG has the following main objectives:

* Address security in DHCP

o Develop and document security requirements for DHCP. RFC 3118
defines current security mechanisms for DHCPv4. Unfortunately,
RFC 3118 has neither been implemented nor deployed to date.
Specific issues to be considered include:

- Improved key management and scalability

- Security for messages passed between relay agents and servers

- Threats of DoS attacks through DHCPFORCERENEW

- The increased usage of DHC on unsecured (e.g., wireless) and
public LANs

- The need for clients to be able to authenticate servers, without
simultaneously requiring client authentication by the server.

o Develop and document a roadmap of any new documents or protocols
needed to meet the security requirements for DHCP

* Write an analysis of the DHCP specification, including RFC 2131,
RFC 2132 and other RFCs defining additional options, which
identifies ambiguities, contradictory specifications and other
obstacles to development of interoperable implementations. Recommend
a process for resolving identified problems and incorporating the
resolutions into the DHCP specification.

* Assess the requirements for a dual-stack host to use DHCP to obtain
configuration settings for both IPv4 and IPv6. Hosts that include
implementations of both IPv4 and IPv6 ("dual-stack hosts") may use
DHCP to obtain configuration settings (including assigned addresses)
for both IPv4 and IPv6. The DHCPv4 and DHCPv6 specifications (RFC
2131, RFC 2132, RFC 3315 and subsequent RFCs) do not explicitly
explain how a dual-stack host uses DHCP to obtain configuration
settings for both IP stacks. The DHC WG will evaluate solutions for
configuration of dual-stack hosts through DHCP and select a solution
that will be developed and published by the WG.

* Assess the requirements for informing DHCPv6 clients of changes in
configuration information. The DHCPv6 specification in RFC 3315
includes a mechanism through which clients can obtain other
configuration information without obtaining an address or addresses.
This mechanisms is sometimes called "stateless DHCPv6" and is
specified in RFC 3736. RFC 3315 includes no provision for notifying
DHCPv6 clients using stateless DHCPv6 of changes in the
configuration information supplied to the client or any
recommendations as to when a client should obtain possibly updated
information. The DHC WG will evaluate solutions for informing
DHCPv6 clients of changes in configuration information and select a
solution that will be developed and published by the WG.

Goals and Milestones:

Done  WG Last Call on DHCP Options for Internet Storage Name Service (draft-ietf-dhc-isnsoption-03.txt)
Done  WG Last Call on Load Balancing for DHCPv6 (draft-ietf-dhc-dhcpv6-loadb-02.txt)
Done  WG Last Call on Time Configuration Options for DHCPv6 (draft-ietf-dhc-dhcpv6-opt-timeconfig-01.txt)
Done  WG Last Call on IPv6 Prefix Options for DHCPv6 (draft-troan-dhcpv6-opt-prefix-delegation-02.txt)
Done  WG Last Call on DNS Configuration options for DHCPv6 (draft-ietf-dhc-dhcpv6-opt-dnsconfig-01.txt)
Done  WG Last Call on NIS Configuration Options for DHCPv6 (draft-ietf-dhc-dhcpv6-opt-nisconfig-01.txt)
Done  Resubmit draft-ietf-dhc-dhcpv6-28.txt to IESG
Done  Identify DHCPv4 authentication design team
Done  Identify DHCPv4 specification review design team
Done  Identify DHCPv4 relay agent message authentication design team
Done  Submit DHCP Options for Internet Storage Name Service to IESG (draft-ietf-dhc-isnsoption)
Done  Submit DNS Configuration options for DHCPv6 to IESG (draft-ietf-dhc-dhcpv6-opt-dnsconfig)
Done  Submit NIS Configuratio Options for DHCPv6 to IESG (draft-ietf-dhc-dhcpv6-opt-nisconfig)
Done  Submit IPv6 Prefix Options for DHCPv6 to IESG (draft-troan-dhcpv6-opt-prefix-delegation)
Done  Submit 'Detection of Network Attachment (DNA) in IPv4' to IESG (draft-ietf-dhc-dna-ipv4)
Done  Resolve IPR issues around 'Rapid Commit Option for DHCPv4'
Done  Publish report on dual-stack issues in DHCP (draft-ietf-dhc-dual-stack)
Done  Publish report on requirements for renumbering using stateless DHCPv6 (draft-ietf-dhc-stateless-dhcpv6-renumbering)
Done  Submit 'Lifetime Option for DHCPv6' to IESG (draft-ietf-dhc-lifetime)
Done  Submit 'Rapid Commit Option for DHCPv4' to IESG (draft-ietf-dhc-rapid-commit-opt)
Done  Submit DDNS/DHCP documents to IESG
Done  Submit 'Node-Specific Client Identifiers for DHCPv4' to IESG (draft-ietf-dhc-3315id-for-v4)
Done  WG last call for 'Subnet Allocation Option'
Done  WG last call on 'Virtual Subnet Selection Option',
Oct 2007  Submit 'Subnet Allocation Option' to IESG for Proposed Standard
Nov 2007  WG last call on 'Guidelines for Creating New DHCP Options'
Nov 2007  Submit 'Virtual Subnet Selection Option', and to IESG for Proposed Standard
Dec 2007  WG last call for 'Domain Suffix Option for DHCPv6'
Jan 2008  Submit 'Domain Suffix Option for DHCPv6' to IESG for Proposed Standard
Jan 2008  Submit 'Guidelines for Creating New DHCP Options' to IESG for Best Current Practice
Jan 2008  Develop plan for advancing DHCPv4 and DHCPv6 plan to include completion of DHCPv4 specification review report, 'Implementation Issues with RFC 2131' for Informational
Feb 2008  WG last call for 'Status of Reclassifying DHCPv4 Options'
Feb 2008  WG last call for 'Dual-stack clients and merging of data from DHCPv4 and DHCPv6' ; waiting for more experience with IPv6 deployment
Feb 2008  WG last call for 'Rebind Capability in DHCPv6 Reconfigure Messages'
Mar 2008  Submit 'Status of Reclassifying DHCPv4 Options' to IESG for Informational
Apr 2008  WG last call for 'DHCP Relay Agent Assignment Notification Option and 'DHCPv6 Server Reply Sequence Number Option'
May 2008  Submit 'Rebind Capability in DHCPv6 Reconfigure Messages' to IESG for Proposed Standard
Jun 2008  WG last call on 'Layer 2 Relay Agent Behaviour'
Jul 2008  Submit 'Layer 2 Relay Agent Behaviour' to IESG for Informational
Jul 2008  Submit 'DHCP Relay Agent Assignment Notification Option' and 'DHCPv6 Server Reply Sequence Number Option' to IESG for Proposed Standard
Jul 2008  Recharter, if needed

Internet-Drafts:

  • draft-ietf-dhc-agent-vpn-id-06.txt
  • draft-ietf-dhc-vpn-option-08.txt
  • draft-ietf-dhc-subnet-alloc-06.txt
  • draft-ietf-dhc-paa-option-05.txt
  • draft-ietf-dhc-dhcpv6-reconfigure-rebind-03.txt
  • draft-ietf-dhc-container-opt-00.txt
  • draft-ietf-dhc-l2ra-00.txt
  • draft-ietf-dhc-dhcpv6-bulk-leasequery-00.txt

    Request For Comments:

    RFCStatusTitle
    RFC1531 PS Dynamic Host Configuration Protocol
    RFC1532 PS Clarifications and Extensions for the Bootstrap Protocol
    RFC1533 PS DHCP Options and BOOTP Vendor Extensions
    RFC1534 DS Interoperation Between DHCP and BOOTP
    RFC1541 PS Dynamic Host Configuration Protocol
    RFC1542 DS Clarifications and Extensions for the Bootstrap Protocol
    RFC2131 DS Dynamic Host Configuration Protocol
    RFC2132 DS DHCP Options and BOOTP Vendor Extensions
    RFC2241 PS DHCP Options for Novell Directory Services
    RFC2242 PS Netware/IP Domain Name and Information
    RFC2485 PS DHCP Option for The Open Group's User Authentication Protocol
    RFC2489 BCP Procedure for Defining New DHCP Options
    RFC2563 PS DHCP Option to Disable Stateless Auto-Configuration in IPv4 Clients
    RFC2610 PS DHCP Options for Service Location Protocol
    RFC2937 PS The Name Service Search Option for DHCP
    RFC2939 BCP Procedure for Defining New DHCP Options and Message Types
    RFC3004 PS The User Class Option for DHCP
    RFC3011 PS The Subnet Selection Option for DHCP
    RFC3046 PS DHCP Relay Agent Information Option
    RFC3074 PS DHC load balancing algorithm
    RFC3118 PS Authentication for DHCP Messages
    RFC3203 PS DHCP reconfigure extension
    RFC3256 PS The DOCSIS Device Class DHCP Relay Agent Information Sub-option
    RFC3315 PS Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
    RFC3396 PS Encoding Long Options in DHCPv4
    RFC3442 PS The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4
    RFC3495 PS Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client Configuration
    RFC3527 PS Link Selection sub-option for the Relay Agent Information Option for DHCPv4
    RFC3594 PS PacketCable Security Ticket Control Sub-option for the the DHCP CableLabs Client Configuration (CCC)Option
    RFC3633 Standard IPv6 Prefix Options for DHCPv6
    RFC3634 Standard KDC Server Address Sub-option
    RFC3646 Standard DNS Configuration Options for DHCPv6
    RFC3679 I Unused DHCP Option Codes
    RFC3736 Standard Stateless DHCP Service for IPv6
    RFC3898 Standard NIS Configuration Options for DHCPv6
    RFC3925 Standard Vendor-Identifying Vendor Options for DHCPv4
    RFC3942 Standard Reclassifying DHCPv4 Options
    RFC3993 Standard DHCP Subscriber ID Suboption for the DHCP Relay Agent Option
    RFC4014 Standard RADIUS Attributes Sub-option for the DHCP Relay Agent Information Option
    RFC4030 Standard The Authentication Suboption for the DHCP Relay Agent Option
    RFC4039 Standard Rapid Commit Option for the Dynamic Host Configuration Protocol version 4 (DHCPv4)
    RFC4075 Standard Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6
    RFC4076 I Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
    RFC4174 Standard The IPv4 Dynamic Host Configuration Protocol (DHCP) Options for the Internet Storage Name Service
    RFC4242 Standard Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
    RFC4243 Standard Vendor-Specific Information Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option
    RFC4280 Standard Dynamic Host Configuration Protocol (DHCP) Options for Broadcast and Multicast Control Servers
    RFC4361 Standard Node-Specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4)
    RFC4388 PS Dynamic Host Configuration Protocol (DHCP) Leasequery
    RFC4436 PS Detecting Network Attachment in IPv4 (DNAv4)
    RFC4477 I Dynamic Host Configuration Protocol (DHCP): IPv4 and IPv6 Dual-Stack Issues
    RFC4578 I Dynamic Host Configuration Protocol (DHCP) Options for the Intel Preboot eXecution Environment (PXE)
    RFC4580 PS Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Subscriber-ID Option
    RFC4649 PS Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID Option
    RFC4702 PS The Dynamic Host Configuration Protocol (DHCP) Client Fully Qualified Domain Name (FQDN) Option
    RFC4703 PS Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host Configuration Protocol (DHCP) Clients
    RFC4704 PS The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option
    RFC4833 PS A Timezone Option for DHCP
    RFC4994 PS DHCPv6 Relay Agent Echo Request Option
    RFC5007 PS DHCPv6 Leasequery
    RFC5010 PS The Dynamic Host Configuration Protocol Version 4 (DHCPv4) Relay Agent Flags Suboption
    RFC5071 I Dynamic Host Configuration Protocol Options Used by PXELINUX
    RFC5107 PS DHCP Server Identifier Override Suboption

    Meeting Minutes


    Slides

    Administrivia
    3rd DHCPv6 Bake-Off
    Virtual Subnet Selection Options for DHCPv4 and DHCPv6
    Bulk Leasequery for DHCPv6
    Relay ID Suboption for DHCPv4
    DHCPv4 Leasequery by Remote ID
    Using DHCPv6 for Mobile Station Prefix Delegation
    Operational Issues of RA M/O Flags
    KDC option for DHCPv6
    Layer 2 Relay Agent Information
    Configuring BFD with DHCP and Other Musings