<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-dhc-dhcpv6-failover-requirements" target="https://datatracker.ietf.org/doc/html/draft-ietf-dhc-dhcpv6-failover-requirements-02">
   <front>
      <title>DHCPv6 Failover Requirements</title>
      <author initials="T." surname="Mrugalski" fullname="Tomek Mrugalski">
         </author>
      <author initials="K." surname="Kinnear" fullname="Kim Kinnear">
         </author>
      <date month="September" day="7" year="2012" />
      <abstract>
	 <t>   The DHCPv6 protocol, defined in [RFC3315] allows for multiple servers
   to operate on a single network, however it does not define any way
   the servers could share information about currently active clients
   and their leases.  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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-dhc-dhcpv6-failover-requirements-02" />
   
</reference>
