draft-ietf-dhc-failover-09.txt   draft-ietf-dhc-failover-10.txt 
Network Working Group Ralph Droms Network Working Group Ralph Droms
INTERNET DRAFT Kim Kinnear INTERNET DRAFT Kim Kinnear
Mark Stapp Mark Stapp
Cisco Systems Cisco Systems
Bernie Volz Bernie Volz
Ericsson Ericsson
Steve Gonczi Steve Gonczi
Network Engines Relicore
Greg Rabil Greg Rabil
Mike Dooley Mike Dooley
Arun Kapur Arun Kapur
Lucent Technologies Lucent Technologies
July 2001 January 2002
Expires January 2002 Expires July 2002
DHCP Failover Protocol DHCP Failover Protocol
<draft-ietf-dhc-failover-09.txt> <draft-ietf-dhc-failover-10.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 48 skipping to change at page 1, line 48
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract Abstract
DHCP [RFC 2131] allows for multiple servers to be operating on a DHCP [RFC 2131] allows for multiple servers to be operating on a
single network. Some sites are interested in running multiple single network. Some sites are interested in running multiple
servers in such a way so as to provide redundancy in case of server 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 failure. In order for this to work reliably, the cooperating primary
and secondary servers must maintain a consistent database of the and secondary servers must maintain a consistent database of the
lease information. This implies that servers will need to coordinate lease information. This implies that servers will need to coordinate
any and all lease activity so that this information is synchronized any and all lease activity so that this information is synchronized
skipping to change at page 106, line 21 skipping to change at page 106, line 21
| >--UPDREQ--------------------> | | >--UPDREQ--------------------> |
| | | |
| <---------------------BNDUPD--< | | <---------------------BNDUPD--< |
| >--BNDACK--------------------> | | >--BNDACK--------------------> |
... ... ... ...
| | | |
| <---------------------BNDUPD--< | | <---------------------BNDUPD--< |
| >--BNDACK--------------------> | | >--BNDACK--------------------> |
| | | |
| <--------------------UPDDONE--< | | <--------------------UPDDONE--< |
NORMAL | CONFLICT-DONE |
| >--STATE--(NORMAL)-----------> | | >--STATE--(CONFLICT-DONE)----> |
| <---------------------UPDREQ--< | | <---------------------UPDREQ--< |
| | | |
| >--BNDUPD--------------------> | | >--BNDUPD--------------------> |
| <---------------------BNDACK--< | | <---------------------BNDACK--< |
... ... ... ...
| >--BNDUPD--------------------> | | >--BNDUPD--------------------> |
| <---------------------BNDACK--< | | <---------------------BNDACK--< |
| | | |
| >--UPDDONE-------------------> | | >--UPDDONE-------------------> |
| NORMAL | NORMAL
| <------------STATE--(NORMAL)--< | | <------------STATE--(NORMAL)--< |
NORMAL |
| >--STATE--(NORMAL)-----------> |
| | | |
| <--------------------POOLREQ--< | | <--------------------POOLREQ--< |
| >------POOLRESP-(n)----------> | | >------POOLRESP-(n)----------> |
| addresses | | addresses |
Figure 9.8.3-1: Transition out of POTENTIAL-CONFLICT Figure 9.10.3-1: Transition out of POTENTIAL-CONFLICT
9.11. RESOLUTION-INTERRUPTED state 9.11. RESOLUTION-INTERRUPTED state
This state indicates that the two servers were attempting to re- This state indicates that the two servers were attempting to re-
integrate with each other in POTENTIAL-CONFLICT state, but integrate with each other in POTENTIAL-CONFLICT state, but
communications failed prior to completion of re-integration. communications failed prior to completion of re-integration.
If the servers remained in POTENTIAL-CONFLICT while communications If the servers remained in POTENTIAL-CONFLICT while communications
was interrupted, neither server would be responsive to DHCP client was interrupted, neither server would be responsive to DHCP client
requests, and if one server had crashed, then there might be no requests, and if one server had crashed, then there might be no
skipping to change at page 129, line 25 skipping to change at page 129, line 25
several technical updates as well as numerous editorial revisions several technical updates as well as numerous editorial revisions
that enhanced both correctness as well as clarity. that enhanced both correctness as well as clarity.
The -08 draft was edited by Kim Kinnear and was based on the results The -08 draft was edited by Kim Kinnear and was based on the results
of two conference calls held in October and November of 2000. It of two conference calls held in October and November of 2000. It
includes the correct second port number, a new state to synchronize includes the correct second port number, a new state to synchronize
conflict resolution with load balancing, a generally accepted conflict resolution with load balancing, a generally accepted
approach to secondary pool allocation, and many other updates based approach to secondary pool allocation, and many other updates based
on both operational as well as implementation experience. on both operational as well as implementation experience.
This, the -09 draft was edited by Kim Kinnear based on discussions The -09 draft was edited by Kim Kinnear based on discussions held at
held at the Minneapolis IETF in December of 2000, as well as issues the Minneapolis IETF in December of 2000, as well as issues raised by
raised by Ted Lemon based on implementation and deployment. The Ted Lemon based on implementation and deployment. The specific
specific changes were mailed to the dhcp-v4 list. changes were mailed to the dhcp-v4 list.
This, the -10 draft, differs from the -09 draft in that figure
9.8.3-1 was correctly relabeled figure 9.10.3-1, and updated to
include the CONFLICT-DONE message. One of the authors affiliations
was also updated.
These most recent changes have not been widely circulated among the These most recent changes have not been widely circulated among the
other authors prior to submission to the IETF. other authors prior to submission to the IETF.
Glenn Waters of Nortel Networks contributed ideas and enthusiasm to Glenn Waters of Nortel Networks contributed ideas and enthusiasm to
make a Failover protocol that was both "safe" and "lazy". make a Failover protocol that was both "safe" and "lazy".
15. References 15. References
[DHCID] Stapp, M., Lemon, T., Gustafsson, A., "draft-ietf-dnsext- [DHCID] Stapp, M., Lemon, T., Gustafsson, A., "draft-ietf-dnsext-
skipping to change at page 131, line 33 skipping to change at page 131, line 39
Bernie Volz Bernie Volz
Ericsson Ericsson
959 Concord St. 959 Concord St.
Framingham, MA 01701 Framingham, MA 01701
Phone: +1-617-513-9060 Phone: +1-617-513-9060
EMail: bernie.volz@ericsson.com EMail: bernie.volz@ericsson.com
Steve Gonczi Steve Gonczi
Network Engines, Inc. Relicore, Inc.
25 Dan Road 5 Burlington Woods, Suite 201
Canton, MA 02021-2817 Burlington, MA 01803
Phone: (781) 332-1165 Phone: (781) 229-1122
Email: steve.gonczi@networkengines.com Email: steve@relicore.com
Greg Rabil, Mike Dooley, Arun Kapur Greg Rabil, Mike Dooley, Arun Kapur
Lucent Technologies Lucent Technologies
400 Lapp Road 400 Lapp Road
Malvern, PA 19355 Malvern, PA 19355
Phone: (800) 208-2747 Phone: (800) 208-2747
EMail: grabil@lucent.com EMail: grabil@lucent.com
mdooley@lucent.com mdooley@lucent.com
akapur@lucent.com akapur@lucent.com
17. Full Copyright Statement 17. Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to oth- This document and translations of it may be copied and furnished to oth-
ers, and derivative works that comment on or otherwise explain it or ers, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and dis- assist in its implementation may be prepared, copied, published and dis-
tributed, in whole or in part, without restriction of any kind, provided tributed, in whole or in part, without restriction of any kind, provided
that the above copyright notice and this paragraph are included on all that the above copyright notice and this paragraph are included on all
such copies and derivative works. However, this document itself may not such copies and derivative works. However, this document itself may not
be modified in any way, such as by removing the copyright notice or be modified in any way, such as by removing the copyright notice or
references to the Internet Society or other Internet organizations, references to the Internet Society or other Internet organizations,
except as needed for the purpose of developing Internet standards in except as needed for the purpose of developing Internet standards in
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/