RFC 6853: DHCPv6 Redundancy Deployment Considerations
In plain English — editorial summary, not part of the RFC
This document provides information for those wishing to use DHCPv6 to support their deployment of IPv6. In particular, it discusses the provision of semi-redundant DHCPv6 services.
Document record
- Document ID
- RFC6853
- Published
- February 2013
- Authors
- J. Brzozowski; J. Tremblay; J. Chen; T. Mrugalski
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- int
- Pages
- 16
- Also known as
- BCP180
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7031DHCPv6 Failover RequirementsCurrent
September 2013
- RFC 7037RADIUS Option for the DHCPv6 Relay AgentCurrent
October 2013
- RFC 7227Guidelines for Creating New DHCPv6 OptionsCurrent
May 2014
- RFC 7283Handling Unknown DHCPv6 MessagesObsoleted
July 2014
- RFC 7341DHCPv4-over-DHCPv6 (DHCP 4o6) TransportCurrent
August 2014
- RFC 7598DHCPv6 Options for Configuration of Softwire Address and Port-Mapped ClientsUpdated
July 2015
- RFC 6059Simple Procedures for Detecting Network Attachment in IPv6Current
November 2010
- RFC 7653DHCPv6 Active LeasequeryCurrent
October 2015
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?