DHCPv6 Failover Requirements
RFC 7031, “DHCPv6 Failover Requirements”, is an Informational document published in September 2013 by T. Mrugalski, K. Kinnear. The canonical text is published by the RFC Editor.
Abstract
The DHCPv6 protocol, defined in RFC 3315, 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. RFC 3315 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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 7031 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7030 Enrollment over Secure Transport
- RFC 7032 LDP Downstream-on-Demand in Seamless MPLS
- RFC 7029 Extensible Authentication Protocol Mutual Cryptographic Binding
- RFC 7033 WebFinger
- RFC 7028 Multicast Mobility Routing Optimizations for Proxy Mobile IPv6
- RFC 7034 HTTP Header Field X-Frame-Options
- RFC 7027 Elliptic Curve Cryptography Brainpool Curves for Transport Layer Security
- RFC 7035 Relative Location Representation