DHCPv6 Failover Protocol

The information below is for an old version of the document
Document Type Expired Internet-Draft (dhc WG)
Authors Tomek Mrugalski  , Kim Kinnear 
Last updated 2016-06-26 (latest revision 2015-12-24)
Replaces draft-ietf-dhc-dhcpv6-failover-design
Stream IETF
Intended RFC status Proposed Standard
Expired & archived
pdf htmlized (tools) htmlized bibtex
Additional Resources
- Mailing list discussion
Stream WG state In WG Last Call
Document shepherd Bernie Volz
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Bernie Volz" <volz@cisco.com>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


DHCPv6 as defined in "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)" (RFC3315) does not offer server redundancy. This document defines a protocol implementation to provide for DHCPv6 failover, a mechanism for running two servers on the same network 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" (RFC7031).


Tomek Mrugalski (tomasz.mrugalski@gmail.com)
Kim Kinnear (kkinnear@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)