Dynamic Host Configuration (dhc)
| WG | Name | Dynamic Host Configuration | |||
|---|---|---|---|---|---|
| Acronym | dhc | ||||
| Area | Internet Area (int) | ||||
| State | Active | ||||
| Charter | charter-ietf-dhc-09 Approved | ||||
| Dependencies | Document dependency graph (SVG) | ||||
| Additional URLs |
|
||||
| Personnel | Chairs |
Bernie Volz
Tomek Mrugalski |
|||
| Area Director |
Suresh Krishnan
|
||||
| Mailing list | Address | dhcwg@ietf.org | |||
| To subscribe | http://www.ietf.org/mailman/listinfo/dhcwg | ||||
| Archive | https://mailarchive.ietf.org/arch/browse/dhcwg/ | ||||
| Jabber chat | Room address | xmpp:dhc@jabber.ietf.org?join | |||
| Logs | https://jabber.ietf.org/logs/dhc/ | ||||
Charter for Working Group
The Dynamic Host Configuration Working Group (DHC WG) has developed DHCP
for automated allocation, configuration and management of IP addresses,
IPv6 prefixes, IP protocol stack and other parameters. DHCPv4 is
currently a Draft Standard and is documented in RFC 2131 and RFC 2132.
DHCPv6 is currently a Proposed Standard and is being updated. The WG
plans to advance the DHCPv6 protocol to Internet standard.
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 generally outside of scope for the DHC WG. Such
options should be defined within their respective WGs or sponsored by an
appropriate AD and reviewed by DHCP experts in the Internet Area
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. Work on informational documents providing operational or implementation advice
about DHCPv6, as well as documents specifying standard mechanisms for
operating, administering and managing DHCPv6 servers, clients, and relay
agents.
2. Assist other WGs and independent submissions in defining options
(that follow RFC 7227 guidelines) and to assure DHCP operational
considerations are properly documented.
3. Issue an updated version of the DHCPv6 base specification, and after
an appropriate interval following publication, advance to Internet standard.
Milestones
| Date | Milestone |
|---|---|
| Mar 2019 |
Advance 3315bis RFC to Internet Standard
draft-ietf-dhc-rfc3315bis |
| Aug 2018 |
WGLC draft-ietf-dhc-dhcpv6-yang
draft-ietf-dhc-dhcpv6-yang |
| Mar 2018 |
WGLC draft-ietf-dhc-dhcpv6-lwm2m-bootstrap-options
draft-ietf-dhc-dhcpv6-lwm2m-bootstrap-options |
| Mar 2018 |
WGLC draft-ietf-dhc-dhcpv4-forcerenew-extensions
draft-ietf-dhc-dhcpv4-forcerenew-extensions |
| Mar 2018 |
WGLC draft-ietf-dhc-dhcp4o6-saddr-opt
draft-ietf-dhc-dhcp4o6-saddr-opt |
1 new milestone currently in Area Director review.