RE: [dhcwg] applicability of draft-ietf-dhc-dhcpv6-ctep-opt-01
"Bernie Volz" <volz@cisco.com> Fri, 09 April 2004 16: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 MAA07499 for <dhcwg-archive@odin.ietf.org>; Fri, 9 Apr 2004 12:49:56 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBzC5-0000Mg-8b for dhcwg-archive@odin.ietf.org; Fri, 09 Apr 2004 12:49:29 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i39GnTPm001397 for dhcwg-archive@odin.ietf.org; Fri, 9 Apr 2004 12:49:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBzC5-0000MS-4T for dhcwg-web-archive@optimus.ietf.org; Fri, 09 Apr 2004 12:49:29 -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 MAA07438 for <dhcwg-web-archive@ietf.org>; Fri, 9 Apr 2004 12:49:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BBzC2-0000MB-00 for dhcwg-web-archive@ietf.org; Fri, 09 Apr 2004 12:49:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BBzAB-00003L-00 for dhcwg-web-archive@ietf.org; Fri, 09 Apr 2004 12:47:32 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BBz7p-0007ZJ-00 for dhcwg-web-archive@ietf.org; Fri, 09 Apr 2004 12:45:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBz7l-0008Ti-Iq; Fri, 09 Apr 2004 12:45:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBz7X-0008Sw-Rw for dhcwg@optimus.ietf.org; Fri, 09 Apr 2004 12:44:47 -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 MAA07143 for <dhcwg@ietf.org>; Fri, 9 Apr 2004 12:44:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BBz7V-0007Xr-00 for dhcwg@ietf.org; Fri, 09 Apr 2004 12:44:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BBz53-0007EN-00 for dhcwg@ietf.org; Fri, 09 Apr 2004 12:42:13 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx with esmtp (Exim 4.12) id 1BBz2J-0006rw-00 for dhcwg@ietf.org; Fri, 09 Apr 2004 12:39:23 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-1.cisco.com with ESMTP; 09 Apr 2004 09:49:20 -0700
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i39GcnCC014718; Fri, 9 Apr 2004 12:38:49 -0400 (EDT)
Received: from volzw2k (sjc-vpn4-400.cisco.com [10.21.81.144]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AHM46945; Fri, 9 Apr 2004 12:38:47 -0400 (EDT)
From: Bernie Volz <volz@cisco.com>
To: 'Pekka Savola' <pekkas@netcore.fi>, 'Ralph Droms' <rdroms@cisco.com>
Cc: dhcwg@ietf.org
Subject: RE: [dhcwg] applicability of draft-ietf-dhc-dhcpv6-ctep-opt-01
Date: Fri, 09 Apr 2004 12:38:47 -0400
Organization: Cisco
Message-ID: <002f01c41e51$21e422c0$6401a8c0@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
In-Reply-To: <Pine.LNX.4.44.0404091746260.20329-100000@netcore.fi>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200
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>
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
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
I guess the solution is to ask the authors to add specific examples of the environments in which this option will be used, if they still feel this option is needed. -----Original Message----- From: dhcwg-admin@ietf.org [mailto:dhcwg-admin@ietf.org] On Behalf Of Pekka Savola Sent: Friday, April 09, 2004 10:51 AM To: Ralph Droms Cc: dhcwg@ietf.org Subject: Re: [dhcwg] applicability of draft-ietf-dhc-dhcpv6-ctep-opt-01 On Fri, 9 Apr 2004, Ralph Droms wrote: > My apologies for thoroughly confusing the conversation... No problem :) > So, let's leave draft-daniel-dhc-ipv6in4-opt-02 out of this discussion > for the moment. Back to the scenario you asked about...I can imagine > (if you'll give me a moment of suspension-of-disbelief) that an ISP > might want to provide IPv6/linklocal service between the service > provider's edge router and the customer routers, without going to full > IPv6 connectivity in its core. In that scenario, the customer router > could use DHCPv6 to obtain a prefix and a tunnel endpoint from a > server in the service provider's edge router, while needing the tunnel > for full external IPv6 connectivity. > > But that does seem like a far-fetched scenario... Yes, it's very far-fetched, because in this specific scenario: 1) the access network is usually the most difficult part to get native v6, and 2) it's much simpler for all the concerned parties for the ISP to use internal tunneling to bridge the gaps in its core network. Whether these tunnels are manually configured, set up automatically using 6PE ("BGP-tunneling") between the border boxes, etc. makes little difference. It's very simple to provide v6 support across v4 core if your edge device supports v6 already. So, as stated -- I'm having a lot of trouble figuring out the real applicability of this option, and I don't think we should go forward with it. The danger is that it's more confusing than it's worth... -- 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 / 神明達哉