DHCPv6 Failover Design
draft-mrugalski-dhc-dhcpv6-failover-design-01

Document Type Replaced Internet-Draft (individual)
Last updated 2013-02-19 (latest revision 2012-03-12)
Replaced by draft-ietf-dhc-dhcpv6-failover-design
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-dhc-dhcpv6-failover-design
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
https://www.ietf.org/archive/id/draft-mrugalski-dhc-dhcpv6-failover-design-01.txt

Abstract

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 [requirements]. A protocol specification document is planned to follow this document.

Authors

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