Dynamic Host Configuration
|The information below is for an old version of the document
Dynamic Host Configuration WG
||Dynamic Host Configuration
||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
- New NTP option to replace OPTION_NTP_SERVER (RFC 5908)
- DNS registration for SLAAC
Additional topics may only be added with approval from the responsible
Area Director or by re-chartering.
2. Specify guidelines for creating new DHCPv6 options.
3. Develop documents that help explain operational considerations for
the wider community.
4. Advance DHCPv6 (RFC 3315 and RFC 3633) along the IETF Standards
5. Write analyses, corrections, and clarifications of the DHCPv6
specifications, including RFC 3315, RFC 3633, RFC 3736 and other RFCs
defining additional options, which identifies and resolves
ambiguities, contradictory specifications and other obstacles to
development of interoperable implementations.