[dhcwg] I-D ACTION:draft-ietf-dhc-failover-11.txt

Internet-Drafts@ietf.org Mon, 04 November 2002 15:07 UTC

Received: from www1.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16851 for <dhcwg-archive@odin.ietf.org>; Mon, 4 Nov 2002 10:07:46 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gA4F9jV31317 for dhcwg-archive@odin.ietf.org; Mon, 4 Nov 2002 10:09:45 -0500
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4F9jv31314 for <dhcwg-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 10:09:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16835 for <dhcwg-web-archive@ietf.org>; Mon, 4 Nov 2002 10:07:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4F7Zv31086; Mon, 4 Nov 2002 10:07:35 -0500
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4F5Jv30349 for <dhcwg@optimus.ietf.org>; Mon, 4 Nov 2002 10:05:19 -0500
Received: from CNRI.Reston.VA.US (localhost []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15676; Mon, 4 Nov 2002 10:02:49 -0500 (EST)
Message-Id: <200211041502.KAA15676@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: dhcwg@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Mon, 04 Nov 2002 10:02:49 -0500
Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-failover-11.txt
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

	Title		: DHCP Failover Protocol
	Author(s)	: R. Droms, K. Kinnear
	Filename	: draft-ietf-dhc-failover-11.txt
	Pages		: 132
	Date		: 2002-11-1
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

A URL for this Internet-Draft is:

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-dhc-failover-11.txt".

A list of Internet-Drafts directories can be found in
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-failover-11.txt".
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the