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:

* Develop extensions to the DHCP infrastructure as required to meet
  new applications and deployments of DHCP.

* Advance DHCPv4 (RFC 2131 and RFC 2132) and DHCPv6 (RFC 3315) in IETF
  Standards Track.  Write analyses of the DHCPv4 and DHCPv6
  specifications, including RFC 2131, RFC 2132, RFC 3315 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.

* 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

* 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.

* Complete WG work on DHCP failover protocol.

Milestones:
Nov 06 Develop plan for advancing DHCPv4 and DHCPv6; plan to include
       completion of DHCPv4 specification review report, "Implementation
       Issues with RFC 2131" <draft-ietf-dhc-implementation-02>
Nov 06 Develop plan for addressing security in DHCP; plan to include
       completion of DHCPv4 authentication design team report,
       "Dynamic Host Configuration Protocol for IPv4 <DHCPv4> Threat
       Analysis" <draft-ietf-dhc-v4-threat-analysis-03.txt>
Nov 06 Submit "DHCP Server-ID Override Suboption"
       <draft-ietf-dhc-server-override-04> and "DHCPv4 Relay Agent
       Flags Suboption" <draft-ietf-dhc-relay-agent-flags-01> to IESG
Nov 06 WG last call for "DHCP Relay Agent Assignment Notification
       Option" <draft-ietf-dhc-dhcpv6-agentopt-delegate-01> and
       "DHCPv6 Server Reply Sequence Number Option"
       <draft-volz-dhc-dhcpv6-srsn-option-00>
Nov 06 WG last call for "Rebind Capability in DHCPv6 Reconfigure
       Messages" <draft-ietf-dhc-dhcpv6-reconfigure-rebind-00>
Nov 06 WG last call for "Subnet Allocation Option"
       <draft-ietf-dhc-subnet-alloc-04>
Nov 06 WG last call for "DHCPv6 Leasequery"
       <draft-ietf-dhc-dhcvp6-leasequery-00>
Nov 06 WG last call for "DHCPv6 Relay Agent Echo Request Option"
       <draft-ietf-dhc-dhcpv6-ero-00>
Dec 06 Submit "DHCP Relay Agent Assignment Notification Option"
       <draft-ietf-dhc-dhcpv6-agentopt-delegate-01> and "DHCPv6 Server
       Reply Sequence Number Option"
       <draft-volz-dhc-dhcpv6-srsn-option-00> to IESG
Dec 06 Submit "Rebind Capability in DHCPv6 Reconfigure Messages"
       <draft-ietf-dhc-dhcpv6-reconfigure-rebind-00> to IESG
Dec 06 Submit "Subnet Allocation Option"
       <draft-ietf-dhc-subnet-alloc-04> to IESG
Dec 06 Submit "DHCPv6 Relay Agent Echo Request Option"
       <draft-ietf-dhc-dhcpv6-ero-00> to IESG
Feb 06 Submit "DHCPv6 Leasequery"
       <draft-ietf-dhc-dhcvp6-leasequery-00> to IESG
Apr 07 Submit "DHCP Failover Protocol"
       <draft-ietf-dhc-failover-12.txt> to IESG
Oct 07 WG last call for "Dual-stack clients and merging of data from
       DHCPv4 and DHCPv6" <draft-ietf-dhc-dual-stack-merge-01.txt>;
       waiting for more experience with IPv6 deployment