Re: [v4v6interim] "IPv4->IPv6 is hard"

Rémi Després <remi.despres@free.fr> Tue, 21 October 2008 06:19 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 1A5B63A6AEB; Mon, 20 Oct 2008 23:19:42 -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 B81E63A6AEB for <v4v6interim@core3.amsl.com>; Mon, 20 Oct 2008 23:19:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[AWL=0.199, BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
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 G17spC1mLOnV for <v4v6interim@core3.amsl.com>; Mon, 20 Oct 2008 23:19:40 -0700 (PDT)
Received: from smtp6-g19.free.fr (smtp6-g19.free.fr [212.27.42.36]) by core3.amsl.com (Postfix) with ESMTP id B41243A6A04 for <v4v6interim@ietf.org>; Mon, 20 Oct 2008 23:19:39 -0700 (PDT)
Received: from smtp6-g19.free.fr (localhost.localdomain [127.0.0.1]) by smtp6-g19.free.fr (Postfix) with ESMTP id 6358819756; Tue, 21 Oct 2008 08:20:52 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by smtp6-g19.free.fr (Postfix) with ESMTP id E045B1724F; Tue, 21 Oct 2008 08:20:51 +0200 (CEST)
Message-ID: <48FD746C.6070604@free.fr>
Date: Tue, 21 Oct 2008 08:19:24 +0200
From: Rémi Després <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Xing Li <xing@cernet.edu.cn>
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> <F2C58F5B-4A97-4F86-8987-832F41424D6E@cisco.com> <48FC30EC.50609@cernet.edu.cn>
In-Reply-To: <48FC30EC.50609@cernet.edu.cn>
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

Xing,

1.
I share the view that,  for ISPs that haven't enough v4 addresses for
all their customers (there will be more and more), charging a higher
price for those that need one or several  global IPv4 address makes a
lot of sense.

It is not in conflict with the fact that ISPs that still have enough v4
space to distribute can also distribute IPv6 prefixes without extra
price.  (Free did in France, using 6rd for that).

I fully agree with Fred and you that, for the coexistence period,
progress on _technologies_ is more than ever a high priority.
The goal must be workable proposals among which ISPs and other Internet
actors will make their choices.

2.
Now, for ISPs that are short in v4 addresses, I believe that merging
IVI and SAM would permit to offer IPv4 connectivity across IPv6
networks at no extra price.

ISPs would for this assign port-restricted IPv4 addresses to ordinary 
customers, with 1:1 correspondence between their IPv6 prefixes and their 
port-restricted addresses. This is what is envisaged in section 6.2 of 
your draft-xli-behave-ivi-00, but in fixing details as proposed in SAM. 
(A new draft on SAM is planned for Minneapolis. It should be easier to
read than draft-despres-sam-00 and draft-despres-sam-scenarios-00 that I 
hastily finished writing for the Montreal meeting).

First simplification compared to the current IVI:
- In SAM, v4 packets that traverse IPv6 domains are for this 
encapsulated in v6 packets.
- Thus, no SIIT translation (and no ALG) is needed between IPv4 and IP 
v6 at the border between the IPv4 and IPv6 domains :-).

Second simplification:
- In an IPv6 address, SAM embeds only the part of the port-restricted 
IPv4 address that is useful to find a route (not the first bits of the 
IPv4 address that are redundant with the IPv6 prefix).
- Thus, as long as the IPv6 prefix fits in 64 bits (which should be the
rule), no new v6 address format is needed :-).

Support of the IPv4->IPv6 scenario:
If a host that supports SAM is attached to an IPv6-only network that has 
SAM gateways at its border with the IPv4 Internet, this host can be 
reached, at its port-restricted IPv4 address, by any host on the global
IPv4 Internet. This is similar to the idea of hosts that directly 
support IVI, the "more interesting scenario" of section 4.8  in your 
draft-xli-behave-ivi-00.

3.
Trying to  take the best of IVI, SAM, and A+P, and possibly merge them,
would IMHO be an interesting subject for discussion in Minneapolis.


Best regards

Rémi






Xing Li   (m/j/a) 10/20/08 9:19 AM:
> Fred Baker 写道:
>> Let's work on the technology.
> Agree. We are working on technology and provide feasible solutions. 
> The market will make the decision. 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