IETF Logo Mail Archive

Re: [dhcwg] applicability of draft-ietf-dhc-dhcpv6-ctep-opt-01

JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp> Tue, 13 April 2004 03:39 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 XAA04302 for <dhcwg-archive@odin.ietf.org>; Mon, 12 Apr 2004 23:39:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BDElE-0006jD-7Y for dhcwg-archive@odin.ietf.org; Mon, 12 Apr 2004 23:38:56 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3D3cuRl025859 for dhcwg-archive@odin.ietf.org; Mon, 12 Apr 2004 23:38:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BDElE-0006j0-2t for dhcwg-web-archive@optimus.ietf.org; Mon, 12 Apr 2004 23:38:56 -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 XAA04293 for <dhcwg-web-archive@ietf.org>; Mon, 12 Apr 2004 23:38:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BDElB-00079W-00 for dhcwg-web-archive@ietf.org; Mon, 12 Apr 2004 23:38:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BDEkX-00077a-00 for dhcwg-web-archive@ietf.org; Mon, 12 Apr 2004 23:38:13 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BDEjO-00075f-00 for dhcwg-web-archive@ietf.org; Mon, 12 Apr 2004 23:37:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BDEjN-0006Kj-V7; Mon, 12 Apr 2004 23:37:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BDEeM-00064O-5p for dhcwg@optimus.ietf.org; Mon, 12 Apr 2004 23:31:56 -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 XAA04138 for <dhcwg@ietf.org>; Mon, 12 Apr 2004 23:31:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BDEeI-0006uw-00 for dhcwg@ietf.org; Mon, 12 Apr 2004 23:31:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BDEd3-0006sF-00 for dhcwg@ietf.org; Mon, 12 Apr 2004 23:30:30 -0400
Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx with esmtp (Exim 4.12) id 1BDEbm-0006oO-00 for dhcwg@ietf.org; Mon, 12 Apr 2004 23:29:11 -0400
Received: from ocean.jinmei.org (unknown [2001:200:0:8002:200:39ff:fe5e:cfd7]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 4E09515214; Tue, 13 Apr 2004 12:29:04 +0900 (JST)
Date: Tue, 13 Apr 2004 12:29:04 +0900
Message-ID: <y7vhdvov9mn.wl@ocean.jinmei.org>
From: JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>
To: Pekka Savola <pekkas@netcore.fi>
Cc: Ralph Droms <rdroms@cisco.com>, dhcwg@ietf.org
Subject: Re: [dhcwg] applicability of draft-ietf-dhc-dhcpv6-ctep-opt-01
In-Reply-To: <Pine.LNX.4.44.0404091746260.20329-100000@netcore.fi>
References: <4.3.2.7.2.20040409100329.02acd940@flask.cisco.com> <Pine.LNX.4.44.0404091746260.20329-100000@netcore.fi>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset="US-ASCII"
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

>>>>> On Fri, 9 Apr 2004 17:51:03 +0300 (EEST), 
>>>>> Pekka Savola <pekkas@netcore.fi> said:

> 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...

FWIW, I tend to agree with you here.  But, apparently the authors are
now trying to clarify the applicability, so I'm open to listening to
it.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

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

v2.23.0 | Report a Bug | By Email