DHCP Failover Protocol
draft-ietf-dhc-failover-12

Document Type Expired Internet-Draft (dhc WG)
Last updated 2003-12-03 (latest revision 2003-03-06)
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
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
https://www.ietf.org/archive/id/draft-ietf-dhc-failover-12.txt

Abstract

DHCP [RFC 2131] allows for multiple servers to be operating on a single network. Some sites are interested in running multiple servers in such a way so as to provide redundancy 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. This implies that servers will need to coordinate any and all lease activity so that this information is synchronized in case of failover. This document defines a protocol to provide such synchronization between two servers. One server is designated the 'primary' server, the other is the 'secondary' server. This document also describes a way to integrate the failover protocol with the DHCP load balancing approach.

Authors

Ralph Droms (rdroms@cisco.com)
Kenneth Kinnear (kinnear@american.com)

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