Re: [dhcwg] Failover: transition out of potential-conflict.

Ted Lemon <mellon@nominum.com> Mon, 05 November 2001 20:22 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 PAA06337 for <dhcwg-archive@odin.ietf.org>; Mon, 5 Nov 2001 15:22:25 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id PAA23531 for dhcwg-archive@odin.ietf.org; Mon, 5 Nov 2001 15:22:28 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA23475; Mon, 5 Nov 2001 15:13:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA23450 for <dhcwg@optimus.ietf.org>; Mon, 5 Nov 2001 15:13:11 -0500 (EST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06067 for <dhcwg@ietf.org>; Mon, 5 Nov 2001 15:13:07 -0500 (EST)
Received: from green.bisbee.fugue.com (205-140-116-229.ip.theriver.com [205.140.116.229]) by toccata.fugue.com (8.11.3/8.6.11) with ESMTP id fA5KBWv23519; Mon, 5 Nov 2001 12:11:32 -0800 (PST)
Received: from dechen (localhost [127.0.0.1]) by green.bisbee.fugue.com (8.10.2/8.6.11) with ESMTP id fA5KDkM01467; Mon, 5 Nov 2001 13:13:46 -0700 (MST)
Date: Mon, 05 Nov 2001 13:13:46 -0700
Subject: Re: [dhcwg] Failover: transition out of potential-conflict.
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v472)
Cc: Kim Kinnear <kkinnear@cisco.com>, dhcwg@ietf.org
To: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
From: Ted Lemon <mellon@nominum.com>
In-Reply-To: <66F66129A77AD411B76200508B65AC697B3868@eambunt705.ena-east.ericsson.se>
Message-Id: <9DE0D56C-D229-11D5-908D-00039317663C@nominum.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.472)
Content-Transfer-Encoding: 7bit
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
Content-Transfer-Encoding: 7bit

> I'm a bit confused as to what the problem really is. When both servers 
> contact
> each other, the primary will request the secondary to send it full details.
>  Once
> the primary has done that, why can it not lease out addresses? It has all 
> of the
> information in order to do this.

D'oh!   My brain appears to have been operating on only one cylinder.   You 
are quite correct.   I'm sorry for the confusion that I may have caused by 
bringing this up.


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