DHCPv6 Failover Design

The information below is for an old version of the document
Document Type Expired Internet-Draft (dhc WG)
Last updated 2013-04-25 (latest revision 2012-10-22)
Replaces draft-mrugalski-dhc-dhcpv6-failover-design
Replaced by RFC 8156, RFC 8156
Stream IETF
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Additional Resources
- Mailing list discussion
Stream WG state WG Document
Document shepherd None
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

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


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 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 (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.)