Dynamic Host Configuration (dhc)

In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at:

       Additional DHC Page

Last Modified: 2008-12-10

Additional information is available at tools.ietf.org/wg/dhc

Chair(s):

  • Ralph Droms <rdroms@cisco.com>

  • John Jason Brzozowski <john_brzozowski@cable.comcast.com>

    Internet Area Director(s):

  • Jari Arkko <jari.arkko@piuha.net>
  • Mark Townsley <townsley@cisco.com>

    Internet Area Advisor:

  • Jari Arkko <jari.arkko@piuha.net>

    Mailing Lists:

    General Discussion: dhcwg@ietf.org
    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 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. Generally speaking, the DHC WG
    will not be responsible for evaluating the semantic content of
    proposed options. Similarly, the ownership of specifications typically
    belongs the relevant working group that needs more functionality from
    DHCP, not the DHC WG. The DHC WG coordinates reviews of the proposed
    options together with those working groups. It is required that those
    working groups have consensus to take on the work and that the work is
    within their charter. Exceptionally, with AD agreement, this same
    process can also be used for Individual Submissions originating
    outside WGs.

    However, the DHC WG can in some cases develop its own options that
    relate to either maintenance of existing specifications or
    improvements in the operation of the DHCP infrastructure itself.

    The DHC WG has the following main objectives:

    * Develop extensions to the DHCP infrastructure as required to meet
    new applications and deployments of DHCP. The topics currently
    in development are:

    - Subnet allocation mechanisms
    - Virtual subnet identification option
    - Option for passing DNS domain information in DHCPv6
    - DHCP relay agent assignment notification in DHCPv6
    - Option for DHCPv6 server reply sequence numbers
    - Rebinding capability for DHCPv6 Reconfigure messages
    - Behavior of layer 2 relay agents

    The adoption of new items requires explicit agreement from
    the AD or rechartering.

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

    Secondly, advance DHCPv4 (RFC 2131 and RFC 2132) and DHCPv6 (RFC
    3315) in IETF Standards Track.

    Thirdly, specify guidelines for creating new DHCP options, and
    report on the status of DHCPv4 option reclassification.

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

    * Hold a discussion whether on-link prefix information and default
    router information is needed in DHCP in addition to router
    advertisements. Actual solutions are out of scope for the WG,
    however.

    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)
    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)
    Done  WG last call for 'Subnet Allocation Option'
    Done  WG last call on 'Virtual Subnet Selection Option'
    Oct 2007  Submit 'Subnet Allocation Option' (draft-ietf-dhc-subnet-alloc-04) to IESG for Proposed Standard
    Nov 2007  WG last call on 'Guidelines for Creating New DHCP Options' (draft-ietf-dhc-option-guidelines)
    Nov 2007  Submit 'Virtual Subnet Selection Option', (draft-ietf-dhc-vpn-option) and (draft-ietf-dhc-agent-vpn-id) to IESG for Proposed Standard
    Dec 2007  WG last call for 'Domain Suffix Option for DHCPv6' (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
    Jan 2008  Submit 'Domain Suffix Option for DHCPv6' (draft-ietf-dhc-dhcpv6-opt-dnsdomain) to IESG for Proposed Standard
    Jan 2008  Submit 'Guidelines for Creating New DHCP Options' (draft-ietf-dhc-option-guidelines) to IESG for Best Current Practice
    Jan 2008  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) for Informational
    Feb 2008  WG last call for 'Status of Reclassifying DHCPv4 Options' (draft-ietf-dhc-status-3942)
    Feb 2008  WG last call for 'Dual-stack clients and merging of data from DHCPv4 and DHCPv6' (draft-ietf-dhc-dual-stack-merge); waiting for more experience with IPv6 deployment
    Feb 2008  WG last call for 'Rebind Capability in DHCPv6 Reconfigure Messages' (draft-ietf-dhc-dhcpv6-reconfigure-rebind)
    Mar 2008  Submit 'Status of Reclassifying DHCPv4 Options' (draft-ietf-dhc-status-3942) to IESG for Informational
    Apr 2008  2nd WG last call for 'DHCP Relay Agent Assignment Notification Option (draft-ietf-dhc-dhcpv6-agentopt-delegate) and 'DHCPv6 Server Reply Sequence Number Option' (draft-ietf-dhc-dhcpv6-srsn-option)
    May 2008  Submit 'Rebind Capability in DHCPv6 Reconfigure Messages' (draft-ietf-dhc-dhcpv6-reconfigure-rebind) to IESG for Proposed Standard
    Jun 2008  WG last call on 'Layer 2 Relay Agent Behaviour' (draft-ietf-dhc-layer2-relay-agent)
    Jul 2008  Submit 'Layer 2 Relay Agent Behaviour' to IESG (draft-ietf-dhc-layer2-relay-agent) for Informational
    Jul 2008  Submit 'DHCP Relay Agent Assignment Notification Option' (draft-ietf-dhc-dhcpv6-agentopt-delegate) and 'DHCPv6 Server Reply Sequence Number Option' (draft-ietf-dhc-dhcpv6-srsn-option) to IESG for Proposed Standard
    Jul 2008  Recharter, if needed

    Internet-Drafts:

    Rebind Capability in DHCPv6 Reconfigure Messages (11878 bytes)
    Guidelines for Creating New DHCP Options (40126 bytes)
    Container Option for Server Configuration (19709 bytes)
    Layer 2 Relay Agent Information (30300 bytes)
    DHCPv6 Bulk Leasequery (42418 bytes)
    The DHCPv4 Relay Agent Identifier Suboption (13857 bytes)
    DHCPv6 option for network boot (24474 bytes)
    DHCPv4 Leasequery by relay agent remote ID (44289 bytes)

    Request For Comments:

    Dynamic Host Configuration Protocol (RFC 1531) (96192 bytes) obsoleted by RFC 1541
    Clarifications and Extensions for the Bootstrap Protocol (RFC 1532) (51545 bytes) obsoletes RFC 951/ obsoleted by RFC 1542
    Interoperation Between DHCP and BOOTP (RFC 1534) (6966 bytes)
    DHCP Options and BOOTP Vendor Extensions (RFC 1533) (50919 bytes) obsoletes RFC 1497/ obsoleted by RFC 2131,RFC 2132
    Clarifications and Extensions for the Bootstrap Protocol (RFC 1542) (52948 bytes) obsoletes RFC 1532
    Dynamic Host Configuration Protocol (RFC 1541) (96950 bytes) obsoletes RFC 1531/ obsoleted by RFC 2131
    Dynamic Host Configuration Protocol (RFC 2131) (113738 bytes) obsoletes RFC 1541,RFC 1533/ updated by RFC 3396,RFC 4361
    DHCP Options and BOOTP Vendor Extensions (RFC 2132) (63670 bytes) obsoletes RFC 1533/ updated by RFC 3442,RFC 3942,RFC 4361,RFC 4833
    Netware/IP Domain Name and Information (RFC 2242) (10653 bytes)
    DHCP Options for Novell Directory Services (RFC 2241) (8419 bytes)
    DHCP Option for The Open Group's User Authentication Protocol (RFC 2485) (7205 bytes)
    Procedure for Defining New DHCP Options (RFC 2489) (10484 bytes) obsoleted by RFC 2939
    DHCP Option to Disable Stateless Auto-Configuration in IPv4 Clients (RFC 2563) (17838 bytes)
    DHCP Options for Service Location Protocol (RFC 2610) (10859 bytes)
    Procedure for Defining New DHCP Options and Message Types (RFC 2939) (13631 bytes) obsoletes RFC 2489
    The Name Service Search Option for DHCP (RFC 2937) (8368 bytes)
    The Subnet Selection Option for DHCP (RFC 3011) (13967 bytes)
    The User Class Option for DHCP (RFC 3004) (10423 bytes)
    DHCP Relay Agent Information Option (RFC 3046) (30633 bytes)
    DHC load balancing algorithm (RFC 3074) (19374 bytes)
    Authentication for DHCP Messages (RFC 3118) (35536 bytes)
    DHCP reconfigure extension (RFC 3203) (11857 bytes)
    The DOCSIS Device Class DHCP Relay Agent Information Sub-option (RFC 3256) (8551 bytes)
    Encoding Long Options in DHCPv4 (RFC 3396) (18779 bytes) updates RFC 2131
    The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4 (RFC 3442) (19370 bytes) updates RFC 2132
    Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client Configuration (RFC 3495) (26817 bytes)
    Link Selection sub-option for the Relay Agent Information Option for DHCPv4 (RFC 3527) (16831 bytes)
    Dynamic Host Configuration Protocol for IPv6 (DHCPv6) (RFC 3315) (231402 bytes) updated by RFC 4361
    PacketCable Security Ticket Control Sub-option for the the DHCP CableLabs Client Configuration (CCC)Option (RFC 3594) (12521 bytes)
    DNS Configuration Options for DHCPv6 (RFC 3646) (13312 bytes)
    IPv6 Prefix Options for DHCPv6 (RFC 3633) (45308 bytes)
    KDC Server Address Sub-option (RFC 3634) (13163 bytes)
    Unused DHCP Option Codes (RFC 3679) (13804 bytes)
    Stateless DHCP Service for IPv6 (RFC 3736) (18510 bytes)
    NIS Configuration Options for DHCPv6 (RFC 3898) (13955 bytes)
    Vendor-Identifying Vendor Options for DHCPv4 (RFC 3925) (17999 bytes)
    Reclassifying DHCPv4 Options (RFC 3942) (13996 bytes) updates RFC 2132
    RADIUS Attributes Sub-option for the DHCP Relay Agent Information Option (RFC 4014) (15416 bytes)
    DHCP Subscriber ID Suboption for the DHCP Relay Agent Option (RFC 3993) (13938 bytes)
    Rapid Commit Option for the Dynamic Host Configuration Protocol version 4 (DHCPv4) (RFC 4039) (22297 bytes)
    The Authentication Suboption for the DHCP Relay Agent Option (RFC 4030) (34332 bytes)
    Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6 (RFC 4075) (9424 bytes)
    Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6) (RFC 4076) (15745 bytes)
    The IPv4 Dynamic Host Configuration Protocol (DHCP) Options for the Internet Storage Name Service (RFC 4174) (29485 bytes)
    Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6) (RFC 4242) (14759 bytes)
    Dynamic Host Configuration Protocol (DHCP) Options for Broadcast and Multicast Control Servers (RFC 4280) (23001 bytes)
    Vendor-Specific Information Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option (RFC 4243) (14342 bytes)
    Node-Specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4) (RFC 4361) (28009 bytes) updates RFC 2131,RFC 2132,RFC 3315
    Dynamic Host Configuration Protocol (DHCP) Leasequery (RFC 4388) (63914 bytes)
    Detecting Network Attachment in IPv4 (DNAv4) (RFC 4436) (35991 bytes)
    Dynamic Host Configuration Protocol (DHCP): IPv4 and IPv6 Dual-Stack Issues (RFC 4477) (30440 bytes)
    Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Subscriber-ID Option (RFC 4580) (10937 bytes)
    Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID Option (RFC 4649) (10940 bytes)
    The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option (RFC 4704) (32359 bytes)
    Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host Configuration Protocol (DHCP) Clients (RFC 4703) (29690 bytes)
    The Dynamic Host Configuration Protocol (DHCP) Client Fully Qualified Domain Name (FQDN) Option (RFC 4702) (37534 bytes)
    Dynamic Host Configuration Protocol (DHCP) Options for the Intel Preboot eXecution Environment (PXE) (RFC 4578) (13238 bytes)
    A Timezone Option for DHCP (RFC 4833) (19573 bytes) updates RFC 2132
    The Dynamic Host Configuration Protocol Version 4 (DHCPv4) Relay Agent Flags Suboption (RFC 5010) (13834 bytes)
    DHCPv6 Leasequery (RFC 5007) (47186 bytes)
    DHCPv6 Relay Agent Echo Request Option (RFC 4994) (10978 bytes)
    Dynamic Host Configuration Protocol Options Used by PXELINUX (RFC 5071) (26777 bytes)
    DHCP Server Identifier Override Suboption (RFC 5107) (14837 bytes)
    DHCP Options for Protocol for Carrying Authentication for Network Access (PANA) Authentication Agents (RFC 5192) (14986 bytes)
    IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

    Return to working group directory.

    Return to IETF home page.