Re: [Softwires] Keeping support of CE IPv4 prefixes in the v4/v6 address mapping?

Jacni Qin <jacni@jacni.com> Fri, 04 November 2011 01:38 UTC

Return-Path: <jacni@jacni.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C75E31F0C4D for <softwires@ietfa.amsl.com>; Thu, 3 Nov 2011 18:38:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.864
X-Spam-Level:
X-Spam-Status: No, score=-1.864 tagged_above=-999 required=5 tests=[AWL=0.123, BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17HMyJwiGHHu for <softwires@ietfa.amsl.com>; Thu, 3 Nov 2011 18:38:58 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id D32FD1F0C3D for <softwires@ietf.org>; Thu, 3 Nov 2011 18:38:58 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id 1ED553800C1 for <softwires@ietf.org>; Thu, 3 Nov 2011 21:38:57 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with SMTP id 9D757340085 for <softwires@ietf.org>; Fri, 4 Nov 2011 09:38:53 +0800 (CST)
Received: from [172.18.104.54] (unknown [221.11.61.100]) by app (Coremail) with SMTP id +AWowJAL6QQbQrNO2z4wAA--.29727S2; Fri, 04 Nov 2011 09:38:53 +0800 (CST)
Message-ID: <4EB34294.5090502@jacni.com>
Date: Fri, 04 Nov 2011 09:40:36 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Rémi Després <despres.remi@laposte.net>
References: <7017F405-CBEC-4D7D-94ED-56FF2B774C0C@laposte.net> <37EE7524-2AF1-4286-A80D-004E7958C5A0@gmail.com> <FCFFF724-847B-45D3-B6A5-1F937356F6B6@laposte.net> <94C682931C08B048B7A8645303FDC9F35A37B98DA7@PUEXCB1B.nanterre.francetelecom.fr> <BA1F9EBE-CDFE-47DB-BE40-08033E62AF17@cisco.com> <94C682931C08B048B7A8645303FDC9F35A37B98E17@PUEXCB1B.nanterre.francetelecom.fr> <88E22674-98FF-4F21-ADA4-4F3E77A6401D@laposte.net> <94C682931C08B048B7A8645303FDC9F35A37B98E3B@PUEXCB1B.nanterre.francetelecom.fr> <E296AD82-0AC6-460E-AB95-6AC6B8127008@cisco.com> <5225339E-1B72-456D-A0E7-2C96F2051EA3@juniper.net> <4EB214D3.7050900@jacni.com> <71723B71-64FD-4EE4-9E21-DE5D57E2FA60@laposte.net> <4EB255CC.30602@jacni.com> <CDFCECE5-A6F3-4C21-81D6-272C9F360E92@laposte.net>
In-Reply-To: <CDFCECE5-A6F3-4C21-81D6-272C9F360E92@laposte.net>
Content-Type: multipart/alternative; boundary="------------040000020101050606060509"
X-CM-TRANSID: +AWowJAL6QQbQrNO2z4wAA--.29727S2
X-Coremail-Antispam: 1UD129KBjvJXoW7Cw1kAw43Jw1fZryUJFyxXwb_yoW8GrWrpF yrXrs8tF97Aw1xuwn5XF1xWayruryfGFyUJr9xtw1UCan8WF9ayr1IkF4rKFyDGrn3KFy7 tr4qvFn5Zwn8ta7anT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUU7Gb7IF0VCYb41lb7IF0VCFI7km07C26c804VAKzcIF0wAYjsxI 4VWkKwAYFVCjjxCrM7CY07I20VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM2kK6xCIbVAIwI AEc20F6c8GOVW8Jr15Jr4lnx0Ec2IEnICE548m6r1DJrWUZwAv7VC0I7IYx2IY67AKxVWU JVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lF7xvr2IY64vIr41l7480Y4vEI4kI2Ix0rVAqx4 xJMxk0xIA0c2IEe2xFo4CEbIxvr21l42xK82IYc2Ij64vIr41l4IxY624lx4CE17CEb7AF 67AKxVWUAVWUtwCIc40Y0x0EwIxGrbIYCTnIWIevJa73UjIFyTuYvjxUcQzVUUUUU
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQICEko7lPH9NQAAsP
Cc: Ole Troan <ot@cisco.com>, Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] Keeping support of CE IPv4 prefixes in the v4/v6 address mapping?
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Nov 2011 01:38:59 -0000

hi Remi,

On 11/3/2011 5:04 PM, Rémi Després wrote:
> Le 3 nov. 2011 à 09:50, Jacni Qin a écrit :
>>>> if the MAP just covers "shared address with one single sharing ratio for one domain",
>>>> the design will be greatly simplified?
>>> Requiring ISPs to maintain IPv4 routing in their networks, just to serve the few users that need to keep IPv4 prefixes, seems to me a step backward.
>>>
>>> Besides, I have serious doubts about "greatly simplified".
>> I mean for the design of the address/port mapping algorithm, not the transport mechanism.
> Yes, but I don't see the great simplification of the algorithm.
> Keeping it general enough to support IPv4 prefixes is AFAIK easy. It doesn't prevent deployments where, IPv4 prefixes being not supported, fields can be at places that may be found more convenient.
Right, and I have already mentioned that in my previous message, the 
prefix case can be inherently supported. I just said that in the context 
of IPv4 address shortage, it may be not reasonable.
If the sharing ratio is unique, then it'll be easily to be calculated, 
some parameter is not required in the MAP Rule. And the simplicity can 
also mean straightforward to implementers and addressing planners, which 
IMHO is important for the solution to be accepted easily in practice.


Cheers,
Jacni

> Maybe you can be more specific on your concern.
>
> Cheers,
> RD
>
>