RFC 6656: Description of Cisco Systems' Subnet Allocation Option for DHCPv4
In plain English — editorial summary, not part of the RFC
This memo documents a DHCPv4 option that currently exists and was previously privately defined for the operation and usage of the Cisco Systems' Subnet Allocation Option for DHCPv4. The option is passed between the DHCPv4 Client and the DHCPv4 Server to request dynamic allocation of a subnet, give specifications of the subnet(s) allocated, and report usage statistics. This memo documents the current usage of the option in agreement with RFC 3942, which declares that any preexisting usages of option numbers in the range 128-223 should be documented and that the working group will try to officially assign those numbers to those options. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6656
- Published
- July 2012
- Authors
- R. Johnson; K. Kinnear; M. Stapp
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 24
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6644Rebind Capability in DHCPv6 Reconfigure MessagesCurrent
July 2012
- RFC 6672DNAME Redirection in the DNSCurrent
June 2012
- RFC 6674Gateway-Initiated Dual-Stack Lite DeploymentCurrent
July 2012
- RFC 6636Tuning the Behavior of the Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) for Routers in Mobile and Wireless NetworksCurrent
May 2012
- RFC 6626Dynamic Prefix Allocation for Network Mobility for Mobile IPv4 (NEMOv4)Current
May 2012
- RFC 6620FCFS SAVI: First-Come, First-Served Source Address Validation Improvement for Locally Assigned IPv6 AddressesCurrent
May 2012
- RFC 6618Mobile IPv6 Security Framework Using Transport Layer Security for Communication between the Mobile Node and Home AgentCurrent
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?