Re: [v4v6interim] "IPv4->IPv6 is hard"
Xing Li <xing@cernet.edu.cn> Mon, 20 October 2008 07:17 UTC
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 26C933A6A18; Mon, 20 Oct 2008 00:17:22 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB0953A6A18 for <v4v6interim@core3.amsl.com>; Mon, 20 Oct 2008 00:17:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.073
X-Spam-Level: *
X-Spam-Status: No, score=1.073 tagged_above=-999 required=5 tests=[AWL=-0.514, BAYES_05=-1.11, FH_HAS_XAIMC=2.696]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hl7xvZ0YiJg2 for <v4v6interim@core3.amsl.com>; Mon, 20 Oct 2008 00:17:20 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 5BFA53A6988 for <v4v6interim@ietf.org>; Mon, 20 Oct 2008 00:17:18 -0700 (PDT)
Received: from [127.0.0.1]([59.66.24.169]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm548fc47b5; Mon, 20 Oct 2008 15:18:28 +0800
Message-ID: <48FC30A5.202@cernet.edu.cn>
Date: Mon, 20 Oct 2008 15:17:57 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com> <4391DDA1-6432- 4DCD-8A38-F351C68058B5@muada.com><0F551636-8059-4C93-81F6-AB5421CD4F3F@cisco.com> <48FBC96D.5020207@cernet.edu.cn> <48FC2AFC.60405@it.uc3m.es>
In-Reply-To: <48FC2AFC.60405@it.uc3m.es>
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: jtECprUB
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6 coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>, <mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>, <mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org
marcelo bagnulo braun 写道: >> >> Some additional notes based on CERNET two years experience of running a >> pure IPv6 backbone. >> >> We believe the selection of the scenarios could be based on the >> incentive of the owner of the IPv6 hosts. >> (1) If the IPv6 host needs to be an IPv4-accessible server, they will >> use the IVI address. Otherwise, it will use non-IVI address. This is to >> say that there is no need to provide a general scheme for any IPv4 host >> initiates communication with ANY IPv6 host, since the owner of the IPv6 >> host can select the suitable category of the IPv6 addresses. > here is where i disagree > I think we should support communications to some v6 addresses creating > some manual or automatic 1:1 mapping because it is the best that we > can do without having to use very nasty hacks like the ones defined in > the original natpt, not because there is no need for such scheme Why not? This is What IVI is doing in CERNET2. The 1:1 stateless is for the IPv4 initiated communication. > Many many hosts today run p2p applications. they certainly can use a > reachable address wihtout neededing to rely on nat traversal > techniques. and this is just one example. you can think about other > cases, like your home camrea that you want to access from the internet > and so on. > > So, i think it makes a lot of sense if any v6 address could be reached > from the v4 internet and i think this would result in faster adoption > of v6, but i don't think we can achieve this in a sufficiently clean > way (not yet at least, maybe in some near future, the natpt would be > sufficiently clean :-) IVI 1:N mapping can solve this problem. The 1:N Stateful is for the IPv6 initiated communication. xing > > > >> (2) As the ISP, we price IVI addresses (1:1 mapping of IPv4 address, >> scarce resource) and non-IVI addresses (non-scarce resource) >> differently. So it is also economically reasonable. > Right, this is exactly what i would like to prevent, that ISPs have > control on whether their clients are able or not to publish content > from their sites > > Regards, marcelo > > > >> >> Just our two cents. >> >> xing >>> >>> _______________________________________________ >>> v4v6interim mailing list >>> v4v6interim@ietf.org >>> https://www.ietf.org/mailman/listinfo/v4v6interim >>> >>> >> >> >> >> >> _______________________________________________ >> v4v6interim mailing list >> v4v6interim@ietf.org >> https://www.ietf.org/mailman/listinfo/v4v6interim > > _______________________________________________ v4v6interim mailing list v4v6interim@ietf.org https://www.ietf.org/mailman/listinfo/v4v6interim
- [v4v6interim] "IPv4->IPv6 is hard" Fred Baker
- Re: [v4v6interim] "IPv4->IPv6 is hard" Mark Townsley
- Re: [v4v6interim] "IPv4->IPv6 is hard" Fred Baker
- Re: [v4v6interim] "IPv4->IPv6 is hard" Iljitsch van Beijnum
- Re: [v4v6interim] "IPv4->IPv6 is hard" Ed Jankiewicz
- Re: [v4v6interim] "IPv4->IPv6 is hard" Fred Baker
- Re: [v4v6interim] "IPv4->IPv6 is hard" Randy Bush
- Re: [v4v6interim] "IPv4->IPv6 is hard" Ed Jankiewicz
- Re: [v4v6interim] "IPv4->IPv6 is hard" Randy Bush
- Re: [v4v6interim] "IPv4->IPv6 is hard" Ed Jankiewicz
- Re: [v4v6interim] "IPv4->IPv6 is hard" Eric Vyncke (evyncke)
- Re: [v4v6interim] "IPv4->IPv6 is hard" Fred Baker
- Re: [v4v6interim] "IPv4->IPv6 is hard" Fred Baker
- Re: [v4v6interim] "IPv4->IPv6 is hard" Xing Li
- Re: [v4v6interim] "IPv4->IPv6 is hard" marcelo bagnulo braun
- Re: [v4v6interim] "IPv4->IPv6 is hard" Fred Baker
- Re: [v4v6interim] "IPv4->IPv6 is hard" Xing Li
- Re: [v4v6interim] "IPv4->IPv6 is hard" Xing Li
- Re: [v4v6interim] "IPv4->IPv6 is hard" marcelo bagnulo braun
- Re: [v4v6interim] "IPv4->IPv6 is hard" Mark Townsley
- Re: [v4v6interim] "IPv4->IPv6 is hard" Rémi Després
- Re: [v4v6interim] "IPv4->IPv6 is hard" Xing Li