RFC 7283: Handling Unknown DHCPv6 Messages
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8415.
Current document in this lineage: RFC 9915 — Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
In plain English — editorial summary, not part of the RFC
DHCPv6 is not specific about handling messages with unknown types. This memo describes the problems associated with receiving DHCPv6 messages with unknown types, and defines how a DHCPv6 server, client, or relay agent should behave when receiving unknown DHCPv6 messages. This document also provides advice for authors of future documents that define new messages to be sent from DHCP servers to DHCP relay agents. This document updates RFC 3315.
Document record
- Document ID
- RFC7283
- Published
- July 2014
- Authors
- Y. Cui; Q. Sun; T. Lemon
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 7
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 9 RFCs, each formally replacing the one before it.
- RFC 3315 (2003)
- RFC 3633 (2003)
- RFC 3736 (2004)
- RFC 4242 (2005)
- RFC 7083 (2013)
- RFC 7283 (2014)
- RFC 7550 (2015)
- RFC 8415 (2018)
- RFC 9915 (2026) ✓
Read the full history of Dynamic Host Configuration Protocol for IPv6 (DHCPv6) →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7227Guidelines for Creating New DHCPv6 OptionsCurrent
May 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 7653DHCPv6 Active LeasequeryCurrent
October 2015
- RFC 6853DHCPv6 Redundancy Deployment ConsiderationsCurrent
February 2013
- 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?