Skip to main content

DHCPv6 Failover Design

Document Type Replaced Internet-Draft (dhc WG)
Expired & archived
Authors Tomek Mrugalski , Kim Kinnear
Last updated 2015-10-14 (Latest revision 2013-09-13)
Replaces draft-mrugalski-dhc-dhcpv6-failover-design
Replaced by RFC 8156
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd Bernie Volz
Shepherd write-up Show Last changed 2013-09-24
IESG IESG state Replaced by draft-ietf-dhc-dhcpv6-failover-protocol
Action Holders
Consensus boilerplate Yes
Telechat date (None)
Responsible AD Ted Lemon
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


DHCPv6 defined in [RFC3315] does not offer server redundancy. This document defines a design for DHCPv6 failover, a mechanism for running two servers on the same network with capability for either server to take over clients' leases in case of server failure or network partition. This is a DHCPv6 Failover design document, it is not a protocol specification document. It is a second document in a planned series of three documents. DHCPv6 failover requirements are specified in [I-D.ietf-dhc-dhcpv6-failover-requirements]. A protocol specification document is planned to follow this document.


Tomek Mrugalski
Kim Kinnear

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