[dhcwg] WG last call on draft-ietf-dhc-failover-12.txt

Ralph Droms <rdroms@cisco.com> Fri, 31 October 2003 13:45 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28060; Fri, 31 Oct 2003 08:45:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFZaH-0007QL-T3; Fri, 31 Oct 2003 08:45:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFZZV-0007Nc-JZ for dhcwg@optimus.ietf.org; Fri, 31 Oct 2003 08:44:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27979 for <dhcwg@ietf.org>; Fri, 31 Oct 2003 08:44:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFZZU-00009h-00 for dhcwg@ietf.org; Fri, 31 Oct 2003 08:44:12 -0500
Received: from sj-core-1.cisco.com ([171.71.177.237]) by ietf-mx with esmtp (Exim 4.12) id 1AFZZT-00009M-00 for dhcwg@ietf.org; Fri, 31 Oct 2003 08:44:11 -0500
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h9VDhcGl025672 for <dhcwg@ietf.org>; Fri, 31 Oct 2003 05:43:40 -0800 (PST)
Received: from rdroms-w2k01.cisco.com ([161.44.65.208]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id ADP69891; Fri, 31 Oct 2003 08:43:37 -0500 (EST)
Message-Id: <4.3.2.7.2.20031031083814.01f53720@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 31 Oct 2003 08:43:32 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [dhcwg] WG last call on draft-ietf-dhc-failover-12.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>

This message announces a WG last call on "DHCP Failover Protocol"
<draft-ietf-dhc-failover-12.txt>.  The last call will conclude at 5PM ET on 
Monday, 11/17/2003.

This WG last call is a second last call on draft-ietf-dhc-failover-12.txt.  
There was insufficient response to the earlier WG last call to determine 
consensus on WG acceptance of the document.

Please respond to this WG last call.  If you support acceptance of the
document without change, respond with a simple acknowledgment, so that
support for the document can be assessed.

Lack of response does *not* represent acceptance of the document.  If there 
is insufficient response to this WG last call, the document will not be 
submitted to the IESG for publication.  Because of the unusual overlap 
between the set of authors of this document and the set of implementors 
interested in the specification, authors are encouraged to respond to this 
WG last call.

draft-ietf-dhc-failover-12.txt defines a protocol to provide
synchronization between two DHCP servers.  The DHCP specification [RFC
2131] allows for multiple servers to be operating on a single network.
For a deployment with multiple servers to work reliably, 
cooperating primary and secondary servers must be synchronized to
maintain a consistent database of the lease information.  This
document is being considered for Proposed Standard, and is available
as http://www.ietf.org/internet-drafts/draft-ietf-dhc-failover-12.txt

- Ralph Droms 


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg