RFC 8156: DHCPv6 Failover Protocol
In plain English — editorial summary, not part of the RFC
DHCPv6 as defined in "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)" (RFC 3315) does not offer server redundancy. This document defines a protocol implementation to provide DHCPv6 failover, a mechanism for running two servers with the capability for either server to take over clients' leases in case of server failure or network partition. It meets the requirements for DHCPv6 failover detailed in "DHCPv6 Failover Requirements" (RFC 7031).
Document record
- Document ID
- RFC8156
- Published
- June 2017
- Authors
- T. Mrugalski; K. Kinnear
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 96
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7031DHCPv6 Failover RequirementsCurrent
September 2013
- RFC 8168DHCPv6 Prefix-Length Hint IssuesCurrent
May 2017
- RFC 7969Customizing DHCP Configuration on the Basis of Network TopologyCurrent
October 2016
- RFC 8415Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Obsoleted
November 2018
- RFC 7844Anonymity Profiles for DHCP ClientsCurrent
May 2016
- RFC 7839Access-Network-Identifier Option in DHCPCurrent
June 2016
- RFC 7653DHCPv6 Active LeasequeryCurrent
October 2015
- RFC 7598DHCPv6 Options for Configuration of Softwire Address and Port-Mapped ClientsUpdated
July 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?