Re: [Softwires] dual-stack-lite-06 - Too biased against static port sharing

Rémi Després <remi.despres@free.fr> Fri, 13 August 2010 08:46 UTC

Return-Path: <remi.despres@free.fr>
X-Original-To: softwires@core3.amsl.com
Delivered-To: softwires@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A6FC3A6993 for <softwires@core3.amsl.com>; Fri, 13 Aug 2010 01:46:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.605
X-Spam-Level:
X-Spam-Status: No, score=-1.605 tagged_above=-999 required=5 tests=[AWL=0.344, 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 QnUgZ7fVIm9M for <softwires@core3.amsl.com>; Fri, 13 Aug 2010 01:46:15 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.20]) by core3.amsl.com (Postfix) with ESMTP id 3D87A3A698F for <softwires@ietf.org>; Fri, 13 Aug 2010 01:46:15 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2306.sfr.fr (SMTP Server) with ESMTP id 85F007000094; Fri, 13 Aug 2010 10:46:51 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2306.sfr.fr (SMTP Server) with ESMTP id E6FDE7000096; Fri, 13 Aug 2010 10:46:50 +0200 (CEST)
X-SFR-UUID: 20100813084650946.E6FDE7000096@msfrf2306.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="iso-8859-1"
From: Rémi Després <remi.despres@free.fr>
In-Reply-To: <C889F178.30988%yiu_lee@cable.comcast.com>
Date: Fri, 13 Aug 2010 10:46:50 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3CB80FE4-042D-494C-A32C-E65DD46C7F3A@free.fr>
References: <C889F178.30988%yiu_lee@cable.comcast.com>
To: "Yiu L. Lee" <yiu_lee@cable.comcast.com>
X-Mailer: Apple Mail (2.1081)
Cc: Softwires <softwires@ietf.org>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [Softwires] dual-stack-lite-06 - Too biased against static port sharing
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 13 Aug 2010 08:46:16 -0000

Le 13 août 2010 à 00:44, Yiu L. Lee a écrit :

> If 8.4 and Appendix C cause any concern, I agree with Alain to remove both
> sections.

+1 to delete them.
RD

> 
> 
> On 8/12/10 10:09 AM, "Ralph Droms" <rdroms@cisco.com> wrote:
> 
>> I think a lot of the text in section 8.4.1 is a matter of opinion or
>> speculation; perhaps it would be better to describe the pros and cons of
>> dynamic and fixed port assignment without making a recommendation before we
>> have much deployment experience.
>> 
>> - Ralph
>> 
>> On Aug 11, 2010, at 6:50 PM 8/11/10, Alain Durand wrote:
>> 
>>> 
>>> On Aug 11, 2010, at 6:00 PM, Ralph Droms wrote:
>>> 
>>>> 
>>>>> 2. If the number of assignable IPv4 addresses is for a start multiplied by
>>>>> 10, by statically sharing ports of each address among 10 customers, this
>>>>> still leaves several thousands of IPv4 ports per customer. (Exactly 6144
>>>>> ports per customer if, as appropriate, the first 4K ports, that include
>>>>> well-known ports and have special value are excluded).
>>>> 
>>>> Agreed; one could argue that even sharing an IPv4 address among 5 customers
>>>> allows 5x as many customers in the existing IPv4 address assignment, which
>>>> should be more than enough to bridge the gap until IPv6 is available.
>>> 
>>> The later part of this comment is IMHO a matter of opinion...
>>> It is very hard to know for sure how much IPv4 translation will be needed in
>>> the feature.
>> 
>> 
>> 
>>> The major issue with any scheme that allocates a fixed number of ports is
>>> what do you do when that number is exhausted?
>>> How do you even know this is happening? This may or may bot be an issue if we
>>> are talking about 10k ports per customers,
>>> but as pressure mounts on the IPv4 space and the address compression ratio
>>> need to be increased, you soon end-up with much less ports per customers. And
>>> then what?
>>> 
>>> 
>>>>> 3. Where applicable static sharing is much simpler to operate.
>>>> 
>>>> Agreed.
>>> 
>>> Logs can indeed be simpler to manage, sure. But this is a trade-off. Other
>>> parts of the systems are more complex, see above.
>>> 
>>> All this being said, the discussion of the advantages or inconvenients of A+B
>>> belong  to the A+P mailing list.
>>> 
>>>   - Alain.
>>> _______________________________________________
>>> Softwires mailing list
>>> Softwires@ietf.org
>>> https://www.ietf.org/mailman/listinfo/softwires
>> 
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
> 
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires