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

Thomas Narten <narten@us.ibm.com> Thu, 09 May 2002 12:10 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 IAA16843 for <dhcwg-archive@odin.ietf.org>; Thu, 9 May 2002 08:10:37 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id IAA21011 for dhcwg-archive@odin.ietf.org; Thu, 9 May 2002 08:10:45 -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 IAA20933; Thu, 9 May 2002 08:09:30 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA20911 for <dhcwg@optimus.ietf.org>; Thu, 9 May 2002 08:09:29 -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 IAA16811 for <dhcwg@ietf.org>; Thu, 9 May 2002 08:09:20 -0400 (EDT)
Received: from cichlid.adsl.duke.edu (narten@localhost) by cichlid.adsl.duke.edu (8.11.6/8.11.6) with ESMTP id g49C89o05305; Thu, 9 May 2002 08:08:09 -0400
Message-Id: <200205091208.g49C89o05305@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 "Wed, 08 May 2002 19:38:17 EDT." <4.3.2.7.2.20020508193307.03149740@funnel.cisco.com>
Date: Thu, 09 May 2002 08:08:08 -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

Ralph Droms <rdroms@cisco.com> writes:

> Thomas comment (below) raised a question in my mind.  Is the state
> of the managedFlag always go to FALSE or is it maintained across
> systems restarts?  That is, does a host always come up in stateless
> mode and then switch to stateful upon receipt of the first RA.  If
> the client does always come up in stateless mode, does the following
> text cause the first Solicit to be delayed until at least the
> receipt of the first RA?

My take. When a node reboots, the first thing it *always* does is
solicit an RA. When it gets the response RA, it has new information
that overrides the old information. So the old information isn't
relevant. That information either says invoke DHC or don't.

If it *doesn't* get an RA, that implies there are no routers. But the
ND (or addrconf?) spec already says that if there are no routers, then
you invoke stateful.

So I think no special words are needed, reasonable behavior is already
defined elsewhere.

Thomas

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