[dhcwg] Unplanned renumbering scenarios
matthew.ford@bt.com Mon, 08 March 2004 15:49 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09147 for <dhcwg-archive@odin.ietf.org>; Mon, 8 Mar 2004 10:49:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B0Mzj-0000Qy-67 for dhcwg-archive@odin.ietf.org; Mon, 08 Mar 2004 10:48:43 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i28FmhxW001667 for dhcwg-archive@odin.ietf.org; Mon, 8 Mar 2004 10:48:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B0Mzj-0000Qo-2a for dhcwg-web-archive@optimus.ietf.org; Mon, 08 Mar 2004 10:48:43 -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 KAA09100 for <dhcwg-web-archive@ietf.org>; Mon, 8 Mar 2004 10:48:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B0Mzg-0000Zg-00 for dhcwg-web-archive@ietf.org; Mon, 08 Mar 2004 10:48:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B0Myk-0000OR-00 for dhcwg-web-archive@ietf.org; Mon, 08 Mar 2004 10:47:43 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B0Mxi-0000Du-00 for dhcwg-web-archive@ietf.org; Mon, 08 Mar 2004 10:46:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B0MxI-0000A0-EY; Mon, 08 Mar 2004 10:46:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B0Mwu-00005S-Ja for dhcwg@optimus.ietf.org; Mon, 08 Mar 2004 10:45:48 -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 KAA08885 for <dhcwg@ietf.org>; Mon, 8 Mar 2004 10:45:44 -0500 (EST)
From: matthew.ford@bt.com
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B0Mws-00005X-00 for dhcwg@ietf.org; Mon, 08 Mar 2004 10:45:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B0Mw2-0007jx-00 for dhcwg@ietf.org; Mon, 08 Mar 2004 10:44:54 -0500
Received: from smtp2.smtp.bt.com ([217.32.164.150] helo=i2kc02-ukbr.domain1.systemhost.net) by ietf-mx with esmtp (Exim 4.12) id 1B0Mvb-0007XO-00 for dhcwg@ietf.org; Mon, 08 Mar 2004 10:44:28 -0500
Received: from i2km95-ukbr.domain1.systemhost.net ([193.113.197.29]) by i2kc02-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(5.0.2195.6713); Mon, 8 Mar 2004 15:43:52 +0000
Received: from i2km41-ukdy.domain1.systemhost.net ([193.113.30.29]) by i2km95-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(5.0.2195.6713); Mon, 8 Mar 2004 15:43:52 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 08 Mar 2004 15:43:51 -0000
Message-ID: <0AAF93247C75E3408638B965DEE11A7006022C75@i2km41-ukdy.domain1.systemhost.net>
Thread-Topic: Unplanned renumbering scenarios
Thread-Index: AcQFJCibEuEabdZGTturijeoF/NHqw==
To: dhcwg@ietf.org
X-OriginalArrivalTime: 08 Mar 2004 15:43:52.0077 (UTC) FILETIME=[27F86BD0:01C40524]
Content-Transfer-Encoding: quoted-printable
Subject: [dhcwg] Unplanned renumbering scenarios
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL, NO_REAL_NAME autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
With regard to draft-chown-dhc-stateless-dhcpv6-renumbering-00, I'm having problems getting to grips with the concept of an 'unplanned' renumbering scenario. As far as I can see the only time this makes sense is if there is a set of config information that cannot be propagated until it is required - why would this ever be the case? Changming described a scenario that seemed to fit this, but as has been pointed out on the list, there are alternative, much better solutions to address this. Other possible scenarios for unplanned renumbering events might be where the config information is outwith the control of the DHCPv6 admin. How likely is that? Are there many network operators that change DNS server addresses on their subscribers without telling them in advance? If it's a case of having multiple paths for redundancy or whatever, then advertise the combined info. Essentially I'm not sure that the concept of an 'unplanned' event is relevant in this context. Mat. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Unplanned renumbering scenarios matthew.ford
- Re: [dhcwg] Unplanned renumbering scenarios Ted Lemon