[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: Ralph Droms <rdroms@cisco.com>
cc: dnsop@cafax.se
From: Pekka Savola <pekkas@netcore.fi>
Date: Fri, 7 Nov 2003 15:40:01 +0200 (EET)
In-Reply-To: <4.3.2.7.2.20031106221405.046bdd80@flask.cisco.com>
Sender: owner-dnsop@cafax.se
Subject: Re: Sense of the WG on DNS discovery

On Thu, 6 Nov 2003, Ralph Droms wrote:
> Fair enough, but asynchronous notification of configuration changes hasn't
> been a requirement in IPv4 (well, there is the FORCERENEW message in RFC
> 3203; as far as I know there are no implementations of RFC 3203).  Why would
> it be needed for IPv6?

IMHO, this certainly shouldn't be in the stateless DHCP spec at least.   
The point is to run a user-level process to configure settings, and exist.  
The latter would require some form of a daemon, and add complexity.

If we want to make renumbering easier (I suggest we do!), my 
recommendation would be stating that implementations should consider 
running stateless DHCP service every N <time-units>, e.g. once a week, 
day, hour, whatever is required.  Nothing prevents that.  There is little 
need for "network-forced renumber that I could see.  Going even a bit 
further, one could add the code in an implementation so that when new 
prefixes are seen in RA's, one would re-run DHCP-lite (with some 
rate-limit) again, just to be sure..

Conclusion: with a stateless method, there is little need for 
network-forced reconfiguration.  With a stateful method, there may be a 
need for it, because you can't really run stateful DHCP many times in a 
row..

> At 11:29 AM 11/7/2003 +0900, SHIRASAKI Yasuhiro wrote:
> > > 1. a "stateless" subset of the current DHCPv6, as specified in
> > >    draft-ietf-dhc-dhcpv6-stateless-01.txt
> > > 2. an extension to the current DHCPv6 that has the ability to
> > >    multicast the stateless information (that I guess Alain first
> > >    proposed)
> >
> > >       (i).    In what way is DHCPv6-lite insufficient?
> >
> >DHCPv6-lite has no way to inform a DNS recursing server renumbering.
> >A DHCPv6-lite server could send Reconfigure messages for its clients,
> >if the server hold a client list, but it's not -lite.
> >
> >DHCPv6-lite with a multicast extension might help this.
> >
> >--
> >SHIRASAKI Yasuhiro @ NTT Communications
> >t: +81-3-6800-3262, f: +81-3-5365-2990
> >#----------------------------------------------------------------------
> ># To unsubscribe, send a message to <dnsop-request@cafax.se>.
> 
> #----------------------------------------------------------------------
> # To unsubscribe, send a message to <dnsop-request@cafax.se>.
> 

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.

Home | Date list | Subject list