Re: [dhcwg] Renumbering DNS with stateless DHCPv6 - bug?

Vijayabhaskar A K <vijayak@india.hp.com> Thu, 13 November 2003 20:31 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18870 for <dhcwg-archive@odin.ietf.org>; Thu, 13 Nov 2003 15:31:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKO7Q-0003wu-DD for dhcwg-archive@odin.ietf.org; Thu, 13 Nov 2003 15:31:15 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hADKV8C2015154 for dhcwg-archive@odin.ietf.org; Thu, 13 Nov 2003 15:31:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKO7P-0003ue-Ca for dhcwg-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 15:31:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18750 for <dhcwg-web-archive@ietf.org>; Thu, 13 Nov 2003 15:30:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKO79-0004bc-00 for dhcwg-web-archive@ietf.org; Thu, 13 Nov 2003 15:30:51 -0500
Received: from manatick.foretec.com ([4.17.168.5] helo=manatick) by ietf-mx with esmtp (Exim 4.12) id 1AKO0M-0004RZ-02 for dhcwg-web-archive@ietf.org; Thu, 13 Nov 2003 15:23:50 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org) by manatick with esmtp (Exim 4.24) id 1AKNtq-0002rw-C3 for dhcwg-web-archive@ietf.org; Thu, 13 Nov 2003 15:17:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKNtk-0002eW-Qr; Thu, 13 Nov 2003 15:17:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKNtR-0002eE-Sy for dhcwg@optimus.ietf.org; Thu, 13 Nov 2003 15:16:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17795 for <dhcwg@ietf.org>; Thu, 13 Nov 2003 15:16:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKNtQ-0004L0-00 for dhcwg@ietf.org; Thu, 13 Nov 2003 15:16:40 -0500
Received: from atlrel8.hp.com ([156.153.255.206]) by ietf-mx with esmtp (Exim 4.12) id 1AKNtP-0004Kx-00 for dhcwg@ietf.org; Thu, 13 Nov 2003 15:16:40 -0500
Received: from iconsrv5.india.hp.com (iconsrv5.india.hp.com [15.42.229.13]) by atlrel8.hp.com (Postfix) with ESMTP id 299AC1C00CCD; Thu, 13 Nov 2003 15:16:37 -0500 (EST)
Received: from india.hp.com (nt23056.india.hp.com [15.42.230.56]) by iconsrv5.india.hp.com (8.9.3 (PHNE_29774)/8.9.3 SMKit7.02) with ESMTP id BAA20377; Fri, 14 Nov 2003 01:45:21 +0530 (IST)
Message-ID: <3FB3E69E.4060705@india.hp.com>
Date: Fri, 14 Nov 2003 01:46:30 +0530
From: Vijayabhaskar A K <vijayak@india.hp.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031014 Thunderbird/0.3
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>
Cc: dnsop@cafax.se, dhcwg@ietf.org
Subject: Re: [dhcwg] Renumbering DNS with stateless DHCPv6 - bug?
References: <20031113191145.GS3473@login.ecs.soton.ac.uk>
In-Reply-To: <20031113191145.GS3473@login.ecs.soton.ac.uk>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I guess, "stateless" means the server doesn't need to maintain the 
lifetime of the configuration information it has assigned to the clients 
and it doesn't mean that it doesn't need to maintain the information 
about the clients..

The proposal of sending multicast reconfigure message was discussed, but 
it was dropped as its very difficult to achieve multicast security and 
reconfigure mechanism mandates auth...

Vijay

Tim Chown wrote:

>Hi,
>
>I was mulling over the renumbering scenario for hosts that use
>stateless autoconf for address allocation and DHCPv6 Light (stateless
>DHCPv6) for DNS options.
>
>Let's assume either the site renumbers, or the DNS servers are
>renumbered.   The latter case means that you can't just use a new
>prefix on an RA as a hint to re-request DNS options via DHCPv6 Light.
>
>With an RA method for DNS option configuration, you put the new DNS
>option information in the RA.
>
>With DHCPv6 Light for DNS option configuration, how is the client told
>that DNS options have changed?  The reconfigure message seems to be
>unicast to the clients, but if the DHCPv6 server is stateless, it won't
>have a list of clients (with leased IPs) to send that Reconfigure
>message to?
>
>Is this a general problem for any options set by a host that only uses 
>stateless DHCPv6 for options, and use RFC2462 for addresses.
>
>One option for passing the new DNS options from the DHCPv6 Light server
>to the client is a multicast Reconfigure message.    That would work 
>if the DHCPv6 Light server is on link, but if relays are used and there
>is no multicast routing on site, this seems to be a gap (and a case for the 
>RA method - though of course with RA method you still need to reconfigure 
>the router for the new RA...)
>
>Thoughts?
>
>Tim
>
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/dhcwg
>
>
>  
>


-- 
__________________________________________________________
Vijayabhaskar A K            Phone : +91-80-2053085
Hewlett Packard              Mobile: +91-9845241382
29 Cunningham Road           Telnet: 847-3085
Bangalore 52                 Email : vijayak@india.hp.com

Until you have the courage to lose sight of the shore,
you will not know the terror of being forever lost at sea.
 __________________________________________________________




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