Re: [dhcwg] Renumbering DNS with stateless DHCPv6 - bug?
Vijayabhaskar A K <vijayak@india.hp.com> Thu, 13 November 2003 21:30 UTC
Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21642 for <dhcwg-archive@odin.ietf.org>; Thu, 13 Nov 2003 16:30:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKP2V-0007pf-Bv for dhcwg-archive@odin.ietf.org; Thu, 13 Nov 2003 16:30:07 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hADLU7rJ030101 for dhcwg-archive@odin.ietf.org; Thu, 13 Nov 2003 16:30:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKP2V-0007pO-5o for dhcwg-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 16:30: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 QAA21604 for <dhcwg-web-archive@ietf.org>; Thu, 13 Nov 2003 16:29:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKP2T-0005ga-00 for dhcwg-web-archive@ietf.org; Thu, 13 Nov 2003 16:30:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKP2S-0005gX-00 for dhcwg-web-archive@ietf.org; Thu, 13 Nov 2003 16:30:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKP2T-0007mn-KS; Thu, 13 Nov 2003 16:30:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKP29-0007lS-Gd for dhcwg@optimus.ietf.org; Thu, 13 Nov 2003 16:29:45 -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 QAA21583 for <dhcwg@ietf.org>; Thu, 13 Nov 2003 16:29:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKP27-0005gL-00 for dhcwg@ietf.org; Thu, 13 Nov 2003 16:29:43 -0500
Received: from palrel12.hp.com ([156.153.255.237]) by ietf-mx with esmtp (Exim 4.12) id 1AKP26-0005gI-00 for dhcwg@ietf.org; Thu, 13 Nov 2003 16:29:42 -0500
Received: from iconsrv5.india.hp.com (iconsrv5.india.hp.com [15.42.229.13]) by palrel12.hp.com (Postfix) with ESMTP id 2CA1B1C016CB; Thu, 13 Nov 2003 13:29:40 -0800 (PST)
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 CAA24525; Fri, 14 Nov 2003 02:58:24 +0530 (IST)
Message-ID: <3FB3F7BD.7030301@india.hp.com>
Date: Fri, 14 Nov 2003 02:59:33 +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: SHIRASAKI Yasuhiro <yasuhiro@nttv6.jp>, dnsop@cafax.se, dhcwg@ietf.org
Subject: Re: [dhcwg] Renumbering DNS with stateless DHCPv6 - bug?
References: <20031113191145.GS3473@login.ecs.soton.ac.uk> <20031114.051205.48455194.yasuhiro@nttv6.jp> <20031113205931.GF3473@login.ecs.soton.ac.uk>
In-Reply-To: <20031113205931.GF3473@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
Tim Chown wrote: >>Both setting the trigger of re-request on renumbering of prefix in RA, >>and a multicast Reconfigure message might cause all nodes to rush on >>the single DHCPv6-lite server for information-request reply exchange. >>It could work with small number of clients though. >> >> > >I guess you could add some random delays, but you should also scale your >DHCPv6 server provision to have multiple servers? > >I guess we can say that: > >(1) Automatic renumbering is broken if people hard-code data in clients > >(2) If a secure environment for reconfigure is needed, a multicast message > adds some complexity > >(3) The Reconfigure message is really designed for a fully stateful DHCPv6 > environment, not a purely stateless one providing options info (?) > >(4) Periodic polling of the DHCPv6 server by clients allows renumbering > but is not a full solution for more rapid (unplanned) renumbering. > > Though, rapid renumbering is not more likely to happen, periodic polling will take some network bandwidth, >(5) There isn't really a ethod now for a client to be informed of a > renumbering event of a stateless DHCPv6 option (DNS, NTP) > >(6) We don't want to use RA method because that would also mean an NTP > extension for RA (?) > >(7) If the network renumbers, statelessly configuring hosts should/could > use the new prefix seen on an RA as a hint to re-request DHCPv6 > options if the O bit is set. > >So is something overlooked, or do we not feel we need a solution to (5), >given we could use (7)? Not sure how explicit (7) is... > > I guess, (7) is better than inventing a solution for (5)... The client can assume the prefix change mean, there is a very good chance that some of the configuration information may have changed and it can go ahead and initiate re-request in the case O bit is set in RAs.. Vijay -- __________________________________________________________ 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
- [dhcwg] Renumbering DNS with stateless DHCPv6 - b… Tim Chown
- Re: [dhcwg] Renumbering DNS with stateless DHCPv6… Vijayabhaskar A K
- Re: [dhcwg] Renumbering DNS with stateless DHCPv6… Tim Chown
- Re: [dhcwg] Renumbering DNS with stateless DHCPv6… Vijayabhaskar A K
- Re: [dhcwg] Renumbering DNS with stateless DHCPv6… Vijayabhaskar A K
- Re: [dhcwg] Renumbering DNS with stateless DHCPv6… Stig Venaas
- [dhcwg] Re: Renumbering DNS with stateless DHCPv6… Iljitsch van Beijnum
- Re: [dhcwg] Renumbering DNS with stateless DHCPv6… Stig Venaas
- Re: [dhcwg] Renumbering DNS with stateless DHCPv6… Vijayabhaskar A K
- RE: [dhcwg] Renumbering DNS with stateless DHCPv6… Bernie Volz
- [dhcwg] Re: Renumbering DNS with stateless DHCPv6… Masataka Ohta
- Re: [dhcwg] Re: Renumbering DNS with stateless DH… Stig Venaas
- [dhcwg] Re: Renumbering DNS with stateless DHCPv6… Thomas Narten
- [dhcwg] Re: Renumbering DNS with stateless DHCPv6… Tim Chown
- Re: [dhcwg] Re: Renumbering DNS with stateless DH… Stig Venaas
- Re: [dhcwg] Re: Renumbering DNS with stateless DH… Masataka Ohta
- RE: [dhcwg] Re: Renumbering DNS with stateless DH… Bernie Volz
- Re: [dhcwg] Re: Renumbering DNS with stateless DH… Masataka Ohta
- Re: [dhcwg] Re: Renumbering DNS with stateless DH… Stig Venaas
- RE: [dhcwg] Re: Renumbering DNS with stateless DH… Bernie Volz
- Re: [dhcwg] Re: Renumbering DNS with stateless DH… Stig Venaas
- RE: [dhcwg] Re: Renumbering DNS with stateless DH… Bernie Volz