"Virtual Subnet Selection Sub-Option for the Relay Agent Information Option for DHCPv4", Kim Kinnear, Richard Johnson, Mark Stapp, Jay Kumarasamy, 18-Dec-07. ( bytes)

In some environments, a relay agent resides in a network element which also has access to one or more virtual private networks (VPNs). If a DHCP server wishes to offer service to DHCP clients on those different VPNs the DHCP server needs to know information about the VPN on which each client resides. The Virtual Subnet Selection sub- option of the relay-agent-information option is used by the relay agent to tell the DHCP server important information about the VPN (called the Virtual Subnet Selection information, or VSS) for every DHCP request it passes on to the DHCP server, and is also used to properly forward any DHCP reply that the DHCP server sends back to the relay agent.

"Virtual Subnet Selection Options for DHCPv4 and DHCPv6", Kim Kinnear, Richard Johnson, Mark Stapp, Jay Kumarasamy, 22-Feb-08. ( bytes)

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.

"Subnet Allocation Option", Richard Johnson, 16-Nov-07. ( bytes)

This document defines a new DHCP option which is passed between the DHCP Client and the DHCP Server to request dynamic allocation of a subnet, give specifications of subnet(s) allocated, and report usage statistics. This memo documents the current usage of the option in agreement with RFC-3942[4], which declares that any pre-existing usages of option numbers in the range 128 - 223 should be documented and the working group will try to officially assign those numbers to those options.

"DHCP options for PANA Authentication Agents", Lionel Morand, 18-Dec-06. ( bytes)

This document defines new DHCPv4 and DHCPv6 options that contain a list of IP addresses to locate one or more of PANA Authentication Agents (PAA). This is one of the methods that a PANA Client (PaC) can use to locate PANA Authentication Agents (PAA).

"Rebind Capability in DHCPv6 Reconfigure Messages", D Evans, Ralph Droms, 4-Dec-07. ( bytes)

This document updates RFC 3315 to allow the Rebind message type to appear in the Reconfigure Message option of a Reconfigure message, which allows DHCPv6 servers to instruct clients to perform a Rebind operation as well as a Renew operation. The document also clarifies how a DHCPv6 client responds to a received Reconfigure message.

"Container Option for Server Configuration", Ralph Droms, 24-Jan-08. ( bytes)

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", Bharat Joshi, Pavan Kurapati, 28-Jan-08. ( bytes)

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", Mark Stapp, 11-Feb-08. ( bytes)

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 specifies extensions to the Leasequery protocol that add new query types and allow for bulk transfer of DHCPv6 binding data.

Return to Internet-Draft directory.

Return to IETF home page.