RFC 6607: Virtual Subnet Selection Options for DHCPv4 and DHCPv6
In plain English — editorial summary, not part of the RFC
This memo defines a DHCPv4 Virtual Subnet Selection (VSS) option, a DHCPv6 VSS option, and the DHCPv4 VSS and VSS-Control sub-options carried in the DHCPv4 Relay Agent Information 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-options, this memo documents and extends existing usage as per RFC 3942. This memo updates RFC 3046 regarding details relating to the copying of sub- options (see Section 8).
Document record
- Document ID
- RFC6607
- Published
- April 2012
- Authors
- K. Kinnear; R. Johnson; M. Stapp
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 26
- Also known as
- —
- Updates:
- RFC 3046
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6606Problem Statement and Requirements for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) RoutingCurrent
May 2012
- RFC 6605Elliptic Curve Digital Signature Algorithm (DSA) for DNSSECCurrent
April 2012
- RFC 6610DHCP Options for Home Information Discovery in Mobile IPv6 (MIPv6)Current
May 2012
- RFC 6604xNAME RCODE and Status Bits ClarificationCurrent
April 2012
- RFC 6611Mobile IPv6 (MIPv6) Bootstrapping for the Integrated ScenarioCurrent
May 2012
- RFC 6603Prefix Exclude Option for DHCPv6-based Prefix DelegationCurrent
May 2012
- RFC 6602Bulk Binding Update Support for Proxy Mobile IPv6Current
May 2012
- RFC 6612Interactions between Proxy Mobile IPv6 (PMIPv6) and Mobile IPv6 (MIPv6): Scenarios and Related IssuesCurrent
May 2012
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?