RFC 6603: Prefix Exclude Option for DHCPv6-based Prefix Delegation
In plain English — editorial summary, not part of the RFC
This specification defines an optional mechanism to allow exclusion of one specific prefix from a delegated prefix set when using DHCPv6-based prefix delegation. The new mechanism updates RFC 3633. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6603
- Published
- May 2012
- Authors
- J. Korhonen; T. Savolainen; S. Krishnan; O. Troan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 10
- Also known as
- —
- Updates:
- RFC 3633
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6602Bulk Binding Update Support for Proxy Mobile IPv6Current
May 2012
- RFC 6604xNAME RCODE and Status Bits ClarificationCurrent
April 2012
- RFC 6605Elliptic Curve Digital Signature Algorithm (DSA) for DNSSECCurrent
April 2012
- RFC 6606Problem Statement and Requirements for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) RoutingCurrent
May 2012
- RFC 6607Virtual Subnet Selection Options for DHCPv4 and DHCPv6Current
April 2012
- RFC 6610DHCP Options for Home Information Discovery in Mobile IPv6 (MIPv6)Current
May 2012
- RFC 6611Mobile IPv6 (MIPv6) Bootstrapping for the Integrated ScenarioCurrent
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?