An Inter-server Protocol for DHCP
draft-ietf-dhc-interserver-02
| Document | Type |
Expired Internet-Draft
(dhc WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Robert G. Cole , Ralph Droms , Kenneth E. Kinnear Jr. | ||
| Last updated | 1997-08-04 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The DHCP protocol is designed to allow for multiple DHCP servers, so that reliability of DHCP service can be improved through the use of redundant servers. To provide redundant service, multiple DHCP servers must carry the same information about assigned IP addresses and parameters; i.e., the servers must be configured with the same bindings. Because DHCP servers may dynamically assign new addresses or configuration parameters, or extend the lease on an existing address assignment, the bindings on some servers may become out of date. The DHCP inter-server protocol provides an automatic mechanism for synchronization of the bindings stored on a set of cooperating DHCP servers. The underlying capabilities of the DHCP inter-server protocol required for multiple server cache replications are based upon the Server Cache Synchronization Protocol (SCSP).
Authors
Robert G. Cole
Ralph Droms
Kenneth E. Kinnear Jr.
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)