Dynamic Host Configuration (dhc)

Dynamic Host Configuration (dhc)
--------------------------------

Charter
Last Modified: 2006-03-30

Current Status: Active Working Group

Chair(s):
Ralph Droms <[email protected]>
Stig Venaas <[email protected]>

Internet Area Director(s):
Jari Arkko <[email protected]>
Mark Townsley <[email protected]>

Internet Area Advisor:
Jari Arkko <[email protected]>

Mailing Lists:
General Discussion:[email protected]
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)

Sep 2004 DHCPv4 authentication design team report completed, 'Dynamic
Host Configuration Protocol for IPv4 (DHCPv4) Threat Analysis'

Sep 2004 DHCPv4 specification review report completed

Sep 2004 Submit 'DHCP Failover Protocol' to IESG
(draft-ietf-dhc-failover)

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)

Internet-Drafts:

Posted Revised I-D Title <Filename>
------ ------- --------------------------------------------
Jul 2001 Mar 2007 <draft-ietf-dhc-agent-vpn-id-04.txt>
Virtual Subnet Selection Sub-Option for the Relay Agent
Information Option for DHCPv4

Jul 2001 Apr 2007 <draft-ietf-dhc-vpn-option-06.txt>
Virtual Subnet Selection Option

Feb 2003 Oct 2006 <draft-ietf-dhc-server-override-04.txt>
DHCP Server Identifier Override Suboption

Feb 2003 Oct 2006 <draft-ietf-dhc-subnet-alloc-04.txt>
Subnet Allocation Option

Oct 2005 Dec 2006 <draft-ietf-dhc-paa-option-05.txt>
DHCP options for PANA Authentication Agents

Oct 2005 Dec 2006 <draft-ietf-dhc-dhcpv6-opt-dnsdomain-04.txt>
Domain Suffix Option for DHCPv6

Jan 2006 Nov 2006 <draft-ietf-dhc-dhcpv6-agentopt-delegate-02.txt>
DHCPv6 Relay Agent Assignment Notification (RAAN) Option

May 2006 Nov 2006 <draft-ietf-dhc-timezone-option-05.txt>
A Timezone Option for DHCP

Jun 2006 Feb 2007 <draft-ietf-dhc-relay-agent-flags-02.txt>
DHCPv4 Relay Agent Flags Suboption

Aug 2006 Apr 2007 <draft-ietf-dhc-pxelinux-01.txt>
PXELINUX Use of 'Site Local' Option Space

Aug 2006 Nov 2006 <draft-ietf-dhc-dhcpv6-reconfigure-rebind-01.txt>
Rebind Capability in DHCPv6 Reconfigure Messages

Oct 2006 Mar 2007 <draft-ietf-dhc-dhcpv6-ero-01.txt>
DHCPv6 Relay Agent Echo Request Option

Nov 2006 Mar 2007 <draft-ietf-dhc-dhcpv6-srsn-option-01.txt>
DHCPv6 Server Reply Sequence Number Option

Mar 2007 Mar 2007 <draft-ietf-dhc-dhcpv6-leasequery-00.txt>
DHCPv6 Leasequery

Request For Comments:

RFC Stat Published Title
------- -- ----------- ------------------------------------
RFC1531 PS Oct 1993 Dynamic Host Configuration Protocol

RFC1532 PS Oct 1993 Clarifications and Extensions for the Bootstrap Protocol

RFC1534 DS Oct 1993 Interoperation Between DHCP and BOOTP

RFC1533 PS Oct 1993 DHCP Options and BOOTP Vendor Extensions

RFC1542 DS Oct 1993 Clarifications and Extensions for the Bootstrap Protocol

RFC1541 PS Oct 1993 Dynamic Host Configuration Protocol

RFC2131 DS Apr 1997 Dynamic Host Configuration Protocol

RFC2132 DS Apr 1997 DHCP Options and BOOTP Vendor Extensions

RFC2241 PS Nov 1997 DHCP Options for Novell Directory Services

RFC2242 PS Nov 1997 Netware/IP Domain Name and Information

RFC2485 PS Jan 1999 DHCP Option for The Open Group's User Authentication
Protocol

RFC2489BCP Jan 1999 Procedure for Defining New DHCP Options

RFC2563 PS May 1999 DHCP Option to Disable Stateless Auto-Configuration in
IPv4 Clients

RFC2610 PS Jun 1999 DHCP Options for Service Location Protocol

RFC2939BCP Oct 2000 Procedure for Defining New DHCP Options and Message
Types

RFC2937 PS Oct 2000 The Name Service Search Option for DHCP

RFC3004 PS Dec 2000 The User Class Option for DHCP

RFC3011 PS Dec 2000 The Subnet Selection Option for DHCP

RFC3046 PS Feb 2001 DHCP Relay Agent Information Option

RFC3074 PS Mar 2001 DHC load balancing algorithm

RFC3118 PS Jun 2001 Authentication for DHCP Messages

RFC3203 PS Dec 2001 DHCP reconfigure extension

RFC3256 PS Apr 2002 The DOCSIS Device Class DHCP Relay Agent Information
Sub-option

RFC3396 PS Nov 2002 Encoding Long Options in DHCPv4

RFC3442 PS Dec 2002 The Classless Static Route Option for Dynamic Host
Configuration Protocol (DHCP) version 4

RFC3495 PS Mar 2003 Dynamic Host Configuration Protocol (DHCP) Option for
CableLabs Client Configuration

RFC3527 PS Apr 2003 Link Selection sub-option for the Relay Agent
Information Option for DHCPv4

RFC3315 PS Jul 2003 Dynamic Host Configuration Protocol for IPv6 (DHCPv6)

RFC3594 PS Sep 2003 PacketCable Security Ticket Control Sub-option for the
the DHCP CableLabs Client Configuration (CCC)Option

RFC3646Standard Dec 2003 DNS Configuration Options for DHCPv6

RFC3633Standard Dec 2003 IPv6 Prefix Options for DHCPv6

RFC3634Standard Jan 2004 KDC Server Address Sub-option

RFC3679 I Jan 2004 Unused DHCP Option Codes

RFC3736Standard Apr 2004 Stateless DHCP Service for IPv6

RFC3898Standard Oct 2004 NIS Configuration Options for DHCPv6

RFC3925Standard Nov 2004 Vendor-Identifying Vendor Options for DHCPv4

RFC3942Standard Dec 2004 Reclassifying DHCPv4 Options

RFC4014Standard Feb 2005 RADIUS Attributes Sub-option for the DHCP Relay Agent
Information Option

RFC3993Standard Mar 2005 DHCP Subscriber ID Suboption for the DHCP Relay Agent
Option

RFC4030Standard Apr 2005 The Authentication Suboption for the DHCP Relay Agent
Option

RFC4039Standard Apr 2005 Rapid Commit Option for the Dynamic Host Configuration
Protocol version 4 (DHCPv4)

RFC4075Standard May 2005 Simple Network Time Protocol (SNTP) Configuration Option
for DHCPv6

RFC4076 I May 2005 Renumbering Requirements for Stateless Dynamic Host
Configuration Protocol for IPv6 (DHCPv6)

RFC4174Standard Sep 2005 The IPv4 Dynamic Host Configuration Protocol (DHCP)
Options for the Internet Storage Name Service

RFC4242Standard Dec 2005 Information Refresh Time Option for Dynamic Host
Configuration Protocol for IPv6 (DHCPv6)

RFC4280Standard Dec 2005 Dynamic Host Configuration Protocol (DHCP) Options for
Broadcast and Multicast Control Servers

RFC4243Standard Dec 2005 Vendor-Specific Information Suboption for the Dynamic
Host Configuration Protocol (DHCP) Relay Agent Option

RFC4361Standard Feb 2006 Node-Specific Client Identifiers for Dynamic Host
Configuration Protocol Version Four (DHCPv4)

RFC4388 PS Feb 2006 Dynamic Host Configuration Protocol (DHCP) Leasequery

RFC4436 PS Mar 2006 Detecting Network Attachment in IPv4 (DNAv4)

RFC4477 I May 2006 Dynamic Host Configuration Protocol (DHCP): IPv4 and
IPv6 Dual-Stack Issues

RFC4580 PS Jun 2006 Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
Relay Agent Subscriber-ID Option

RFC4649 PS Aug 2006 Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
Relay Agent Remote-ID Option

RFC4704 PS Oct 2006 The Dynamic Host Configuration Protocol for IPv6
(DHCPv6) Client Fully Qualified Domain Name (FQDN)
Option

RFC4703 PS Oct 2006 Resolution of Fully Qualified Domain Name (FQDN)
Conflicts among Dynamic Host Configuration Protocol
(DHCP) Clients

RFC4702 PS Oct 2006 The Dynamic Host Configuration Protocol (DHCP) Client
Fully Qualified Domain Name (FQDN) Option

RFC4578 I Nov 2006 Dynamic Host Configuration Protocol (DHCP) Options for
the Intel Preboot eXecution Environment (PXE)