RFC 7227: Guidelines for Creating New DHCPv6 Options
In plain English — editorial summary, not part of the RFC
This document provides guidance to prospective DHCPv6 option developers to help them create option formats that are easily adoptable by existing DHCPv6 software. It also provides guidelines for expert reviewers to evaluate new registrations. This document updates RFC 3315.
Document record
- Document ID
- RFC7227
- Published
- May 2014
- Authors
- D. Hankins; T. Mrugalski; M. Siodelski; S. Jiang; S. Krishnan
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- int
- Pages
- 35
- Also known as
- BCP187
- Updates:
- RFC 3315
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7283Handling Unknown DHCPv6 MessagesObsoleted
July 2014
- RFC 7341DHCPv4-over-DHCPv6 (DHCP 4o6) TransportCurrent
August 2014
- RFC 7037RADIUS Option for the DHCPv6 Relay AgentCurrent
October 2013
- RFC 7031DHCPv6 Failover RequirementsCurrent
September 2013
- RFC 7598DHCPv6 Options for Configuration of Softwire Address and Port-Mapped ClientsUpdated
July 2015
- RFC 6853DHCPv6 Redundancy Deployment ConsiderationsCurrent
February 2013
- RFC 7653DHCPv6 Active LeasequeryCurrent
October 2015
- RFC 7839Access-Network-Identifier Option in DHCPCurrent
June 2016
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?