DHCPv6 Failover Requirements
draft-mrugalski-dhc-dhcpv6-failover-requirements-00

Document Type Replaced Internet-Draft (individual)
Last updated 2013-02-19 (latest revision 2011-06-26)
Replaced by draft-ietf-dhc-dhcpv6-failover-requirements
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-requirements
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-requirements-00.txt

Abstract

The DHCPv6 protocol, defined in [RFC3315] allows for multiple servers to operate on a single network, however it does not define any way to decide which server responds to which client queries. Some sites are interested in running multiple servers in such a way as to provide increased availability in case of server failure. In order for this to work reliably, the cooperating primary and secondary servers must maintain a consistent database of the lease information. [RFC3315] allows for but does not define any redundancy or failover mechanisms. This document outlines requirements for DHCPv6 failover, enumerates related problems, and discusses the proposed scope of work to be conducted. This document does not define a DHCPv6 failover protocol.

Authors

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

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