Re: [dhcwg] dhcpv6-24: randomization delay before invoking DHC

Thomas Narten <narten@us.ibm.com> Thu, 09 May 2002 12:31 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 IAA17404 for <dhcwg-archive@odin.ietf.org>; Thu, 9 May 2002 08:31:20 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id IAA22030 for dhcwg-archive@odin.ietf.org; Thu, 9 May 2002 08:31:28 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21614; Thu, 9 May 2002 08:29:28 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21585 for <dhcwg@optimus.ietf.org>; Thu, 9 May 2002 08:29:25 -0400 (EDT)
Received: from cichlid.adsl.duke.edu (cichlid.adsl.duke.edu [152.16.64.203]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17306 for <dhcwg@ietf.org>; Thu, 9 May 2002 08:29:16 -0400 (EDT)
Received: from cichlid.adsl.duke.edu (narten@localhost) by cichlid.adsl.duke.edu (8.11.6/8.11.6) with ESMTP id g49CS5L05366; Thu, 9 May 2002 08:28:05 -0400
Message-Id: <200205091228.g49CS5L05366@cichlid.adsl.duke.edu>
To: Ralph Droms <rdroms@cisco.com>
cc: dhcwg@ietf.org
Subject: Re: [dhcwg] dhcpv6-24: randomization delay before invoking DHC
In-Reply-To: Message from Ralph Droms <rdroms@cisco.com> of "Thu, 09 May 2002 01:52:44 EDT." <4.3.2.7.2.20020509014238.03136ee8@funnel.cisco.com>
Date: Thu, 09 May 2002 08:28:04 -0400
From: Thomas Narten <narten@us.ibm.com>
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

> I believe that the problem can be fixed be rewriting the sentence in 
> question as:

>      In the case of a Solicit message transmitted when DHCP
>      is initiated by IPv6 Neighbor Discovery, the delay gives the amount
>      of time to wait after IPv6 Neighbor Discvoery causes the client to
>      invoke the stateful address autoconfiguration protocol (see
>      section 5.5.3 of RFC2462).

> That is, I think RFC2462 defines the times at which the client begins the 
> DHCP process by sending a Solicit.  The DHCP spec can then define the 
> randomization to be applied to that starting time.

Works for me.

Thomas

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