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

Exactly.
/jim

> -----Original Message-----
> From: Thomas Narten [mailto:narten@us.ibm.com]
> Sent: Thursday, May 09, 2002 8:08 AM
> To: Ralph Droms
> Cc: dhcwg@ietf.org
> Subject: Re: [dhcwg] dhcpv6-24: randomization delay before 
> invoking DHC 
> 
> 
> 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
> 

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