Dynamic Host Configuration (dhc) Internet Drafts

Virtual Subnet Selection Options for DHCPv4 and DHCPv6

draft-ietf-dhc-vpn-option-08.txt

Date: 22/02/2008

Authors: Kim Kinnear, Richard Johnson, Mark Stapp, Jay Kumarasamy

Working Group: Dynamic Host Configuration (dhc)

Formats: txt

This memo defines a Virtual Subnet Selection (VSS) option for DHCPv4 and DHCPv6, and a DHCPv4 relay-agent-information sub-option. These are intended for use by DHCP clients, relay agents, and proxy clients in situations where VSS information needs to be passed to the DHCP server for proper address or prefix allocation to take place. For the DHCPv4 option and relay-agent-information sub-option, this memo documents existing usage as per RFC 3942.

Container Option for Server Configuration

draft-ietf-dhc-container-opt-00.txt

Date: 24/01/2008

Authors: Ralph Droms

Working Group: Dynamic Host Configuration (dhc)

Formats: txt

In some DHCP service deployments, it is desirable for a DHCP server in one administrative domain to pass configuration options to a DHCP server in a different administrative domain. This DHCP option carries a set of DHCP options that can be used by another DHCP server.

Layer 2 Relay Agent Information

draft-ietf-dhc-l2ra-01.txt

Date: 16/05/2008

Authors: Bharat Joshi, Pavan Kurapati

Working Group: Dynamic Host Configuration (dhc)

Formats: txt

In some networks, DHCP servers rely on Relay Agent Information option appended by Relay Agents for IP address and other parameter assignment policies. This works fine when end hosts are directly connected to Relay Agents. In some network configurations, one or more Layer 2 devices may reside between DHCP clients and Relay agent. In these network scenarios, it is difficult to use the Relay Agent Information option for IP address and other parameter assignment policies effectively. So there is a need for the device that is closest to the end hosts to append Relay Agent Information option in DHCP messages. These devices are typically known as Layer 2 Relay Agents. This document aims to describe the network scenarios where Layer 2 Relay Agent is in use and also how it handles DHCP messages.

DHCPv6 Bulk Leasequery

draft-ietf-dhc-dhcpv6-bulk-leasequery-03.txt

Date: 12/06/2008

Authors: Mark Stapp

Working Group: Dynamic Host Configuration (dhc)

Formats: xml txt

The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) has been extended with a Leasequery capability that allows a client to request information about DHCPv6 bindings. That mechanism is limited to queries for individual bindings. In some situations individual binding queries may not be efficient, or even possible. This document expands on the Leasequery protocol, adding new query types and allowing for bulk transfer of DHCPv6 binding data via TCP.

Extensions to Layer 2 Relay Agent

draft-ietf-dhc-l2ra-extensions-00.txt

Date: 14/06/2008

Authors: Bharat Joshi, Pavan Kurapati, Mukund Kamath, Stefaan De Cnodder

Working Group: Dynamic Host Configuration (dhc)

Formats: txt

As per industry trends, Access Networks have been migrating from traditional ATM based networks to Ethernet networks. In Ethernet based access networks, Access Concentrators are typically configured to act as a transparent bridge in Layer 2 mode. These Access Concentrators also act as Layer 2 relay agents. Layer 2 Relay Agent functionality does not provide means to avoid flooding of DHCP messages and also needs to be extended to support DHCP LeaseQuery This draft discusses these issues and provides solutions for the same.

The DHCPv4 Relay Agent Identifier Suboption

draft-ietf-dhc-relay-id-suboption-00.txt

Date: 16/06/2008

Authors: Mark Stapp

Working Group: Dynamic Host Configuration (dhc)

Formats: txt xml

This memo defines a new Relay Agent Identifier suboption for the Dynamic Host Configuration Protocol's (DHCP) Relay Agent Information option. The suboption carries a unique identifier configured or generated at the relay agent. The suboption allows a DHCP relay agent to include the unique identifier in the DHCP messages it sends.

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-04-23

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 (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:

* 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

* Write an analysis of the DHCP specification, including RFC 2131,
RFC 2132 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.

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

* Assess the requirements for informing DHCPv6 clients of changes in
configuration information. The DHCPv6 specification in RFC 3315
includes a mechanism through which clients can obtain other
configuration information without obtaining an address or addresses.
This mechanisms is sometimes called "stateless DHCPv6" and is
specified in RFC 3736. RFC 3315 includes no provision for notifying
DHCPv6 clients using stateless DHCPv6 of changes in the
configuration information supplied to the client or any
recommendations as to when a client should obtain possibly updated
information. The DHC WG will evaluate solutions for informing
DHCPv6 clients of changes in configuration information and select a
solution that will be developed and published by the WG.

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' to IESG for Proposed Standard
Nov 2007		WG last call on 'Guidelines for Creating New DHCP Options'
Nov 2007		Submit 'Virtual Subnet Selection Option', and to IESG for Proposed Standard
Dec 2007		WG last call for 'Domain Suffix Option for DHCPv6'
Jan 2008		Submit 'Domain Suffix Option for DHCPv6' to IESG for Proposed Standard
Jan 2008		Submit 'Guidelines for Creating New DHCP Options' 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' for Informational
Feb 2008		WG last call for 'Status of Reclassifying DHCPv4 Options'
Feb 2008		WG last call for 'Dual-stack clients and merging of data from DHCPv4 and DHCPv6' ; waiting for more experience with IPv6 deployment
Feb 2008		WG last call for 'Rebind Capability in DHCPv6 Reconfigure Messages'
Mar 2008		Submit 'Status of Reclassifying DHCPv4 Options' to IESG for Informational
Apr 2008		WG last call for 'DHCP Relay Agent Assignment Notification Option and 'DHCPv6 Server Reply Sequence Number Option'
May 2008		Submit 'Rebind Capability in DHCPv6 Reconfigure Messages' to IESG for Proposed Standard
Jun 2008		WG last call on 'Layer 2 Relay Agent Behaviour'
Jul 2008		Submit 'Layer 2 Relay Agent Behaviour' to IESG for Informational
Jul 2008		Submit 'DHCP Relay Agent Assignment Notification Option' and 'DHCPv6 Server Reply Sequence Number Option' to IESG for Proposed Standard
Jul 2008		Recharter, if needed

Internet-Drafts:

Virtual Subnet Selection Options for DHCPv4 and DHCPv6 (37108 bytes)
Container Option for Server Configuration (17430 bytes)
Layer 2 Relay Agent Information (30275 bytes)
DHCPv6 Bulk Leasequery (44390 bytes)
Extensions to Layer 2 Relay Agent (37797 bytes)
The DHCPv4 Relay Agent Identifier Suboption (11524 bytes)

Request For Comments:

IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

Return to working group directory.

Return to IETF home page.