Dynamic Host Configuration
|The information below is for an older proposed charter
Dynamic Host Configuration WG
||Dynamic Host Configuration
Start Chartering/Rechartering (Internal Steering Group/IAB Review)
||Charter Edit AD
||Send notices to
Proposed Updated DHC WG Charter (August 26, 2013)
The Dynamic Host Configuration 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 defining DHCP protocol extensions.
Definitions of new DHCP options that are delivered using standard
mechanisms with documented semantics are not considered a protocol
extension and thus are outside of scope for the DHC WG. Such options
should be defined within their respective WGs and reviewed by the DHCP
Directorate. However, if such options require protocol extensions or new
semantics, the protocol extension work must be done in the DHC WG.
The DHC WG has the following main objectives:
1. Develop extensions to the DHCPv6 infrastructure as required to meet
new applications and deployments of DHCP. The topics currently in
- DHCPv6 Failover, High Availability and Load Balancing
- Extend DHCPv6 to work with multiple provisioning domains
- DHCP provisioning of IPv4 clients over IPv6 networks
- SOLMAXRT counter update
- Container option
- Access Network Identifier
- DNS registration for SLAAC
Additional topics may only be added with approval from the responsible
Area Director or by re-chartering.
2. Develop a replacement for OPTION_NTP_SERVER (RFC 5908). The
DHC working group will develop this option, taking input from the NTP
working group during the development process. Last call on this option
will be done in the DHC working group.
3. Specify guidelines for creating new DHCPv6 options.
4. Develop documents that help explain operational considerations for
the wider community.
5. Issue updated versions of the DHCP base specifications--
RFC 3315 (DHCPv6), RFC 3633 (DHCPv6 Prefix Delegation) and
RFC 3736 (Stateless DHCPv6) so as to fix errata and bring
the documents to the point where they can advance along the
IETF Standards Track.
6. In the process of updating the DHCP base specifications, in
cases where time is of the essence, issue analyses, corrections,
and clarifications of the specifications in order to quickly
address interoperability problems.
7. When serious interoperability problems are found in other DHCP
specifications, issue updated versions of those problems to
address the interoperability problems.