Re: [dhcwg] applicability of draft-ietf-dhc-dhcpv6-ctep-opt-01
Ralph Droms <rdroms@cisco.com> Fri, 09 April 2004 13:47 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 JAA27676 for <dhcwg-archive@odin.ietf.org>; Fri, 9 Apr 2004 09:47:18 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBwLL-0005wZ-Av for dhcwg-archive@odin.ietf.org; Fri, 09 Apr 2004 09:46:51 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i39Dkpuf022843 for dhcwg-archive@odin.ietf.org; Fri, 9 Apr 2004 09:46:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBwLL-0005wM-5d for dhcwg-web-archive@optimus.ietf.org; Fri, 09 Apr 2004 09:46:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27651 for <dhcwg-web-archive@ietf.org>; Fri, 9 Apr 2004 09:46:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BBwLI-0006qJ-00 for dhcwg-web-archive@ietf.org; Fri, 09 Apr 2004 09:46:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BBwJY-0006hC-00 for dhcwg-web-archive@ietf.org; Fri, 09 Apr 2004 09:45:01 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BBwId-0006cP-00 for dhcwg-web-archive@ietf.org; Fri, 09 Apr 2004 09:44:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBwIb-0005d5-FX; Fri, 09 Apr 2004 09:44:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBwHt-0005bL-LO for dhcwg@optimus.ietf.org; Fri, 09 Apr 2004 09:43:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27523 for <dhcwg@ietf.org>; Fri, 9 Apr 2004 09:43:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BBwHq-0006XF-00 for dhcwg@ietf.org; Fri, 09 Apr 2004 09:43:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BBwGN-0006Sb-00 for dhcwg@ietf.org; Fri, 09 Apr 2004 09:41:44 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx with esmtp (Exim 4.12) id 1BBwFj-0006Md-00 for dhcwg@ietf.org; Fri, 09 Apr 2004 09:41:03 -0400
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i39DeNKj013766; Fri, 9 Apr 2004 06:40:23 -0700 (PDT)
Received: from rdroms-w2k01.cisco.com ([161.44.65.128]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AHM32480; Fri, 9 Apr 2004 09:40:21 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040409093555.02ae0008@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 09 Apr 2004 09:40:19 -0400
To: Pekka Savola <pekkas@netcore.fi>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] applicability of draft-ietf-dhc-dhcpv6-ctep-opt-01
Cc: Ted Lemon <mellon@fugue.com>, dhcwg@ietf.org
In-Reply-To: <Pine.LNX.4.44.0404050903560.18946-100000@netcore.fi>
References: <99C4FAC6-869E-11D8-869D-000A95D9C74C@fugue.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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.0 required=5.0 tests=AWL autolearn=no version=2.60
It is not be necessary to touch the router in all cases... An IPv6 "home gateway" with a single upstream interface (to the service provider) and one or more downstream interfaces will operate in a sufficiently constrained environment so as to allow plug-and-play operation with only minimal configuration (such as a prefix delegated from the service provider). In this case, if the service provider makes IPv6 service available through a configured tunnel, the only other configuration required would be the address of the other endpoint of the tunnel. It would make sense to provide that endpoint address through DHCP along with the delegated prefix. Now, the dhc WG is debating whether or not to take on this option as a WG work item, because it applies to router configuration rather than host configuration. The use case is there - it's a matter of charter scope. - Ralph At 09:06 AM 4/5/2004 +0300, Pekka Savola wrote: >On Sun, 4 Apr 2004, Ted Lemon wrote: > > On Apr 2, 2004, at 7:44 AM, Pekka Savola wrote: > > > You're trading off having to > > > configure 90 tunnels in 10 border routers to having to configure 90 > > > tunnels in 10 DHCPv6 servers. > > > > > > IMHO, in this kind of set-up, Using DHCPv6 just doesn't seem to make > > > sense. > > > > Possibly it's easier to configure a DHCP server on a central server > > somewhere with all this information rather than configuring the router, > > because if the router dies then you have to remember to reconfigure it. > > > > But basically, I don't know. :') > >You'll have to reconfigure the router in any case to get the other >connectivity working ;-). > >Here, you don't get aggregation benefits as you have to configure >exactly the same information in 10 DHCPv6 servers as you'd have to do >in 10 routers. If you would only need to configure 1 DHCPv6 server to >get the config to all the routers, some folks might think this gives >additional benefits. > >-- >Pekka Savola "You each name yourselves king, yet the >Netcore Oy kingdom bleeds." >Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings > > >_______________________________________________ >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
- [dhcwg] applicability of draft-ietf-dhc-dhcpv6-ct… Pekka Savola
- Re: [dhcwg] applicability of draft-ietf-dhc-dhcpv… Ted Lemon
- Re: [dhcwg] applicability of draft-ietf-dhc-dhcpv… Pekka Savola
- Re: [dhcwg] applicability of draft-ietf-dhc-dhcpv… Ralph Droms
- Re: [dhcwg] applicability of draft-ietf-dhc-dhcpv… Pekka Savola
- Re: [dhcwg] applicability of draft-ietf-dhc-dhcpv… Ralph Droms
- Re: [dhcwg] applicability of draft-ietf-dhc-dhcpv… Pekka Savola
- RE: [dhcwg] applicability of draft-ietf-dhc-dhcpv… Bernie Volz
- RE: [dhcwg] applicability of draft-ietf-dhc-dhcpv… S. Daniel Park
- Re: [dhcwg] applicability of draft-ietf-dhc-dhcpv… JINMEI Tatuya / 神明達哉