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

Ralph Droms <rdroms@cisco.com> Thu, 12 August 2010 14:09 UTC

Return-Path: <rdroms@cisco.com>
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 830223A6A27 for <softwires@core3.amsl.com>; Thu, 12 Aug 2010 07:09:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.381
X-Spam-Level:
X-Spam-Status: No, score=-10.381 tagged_above=-999 required=5 tests=[AWL=0.218, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 ikCJlt4qeKpt for <softwires@core3.amsl.com>; Thu, 12 Aug 2010 07:09:17 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id B212C3A6A3F for <softwires@ietf.org>; Thu, 12 Aug 2010 07:09:17 -0700 (PDT)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAN6dY0yrRN+J/2dsb2JhbACgPXGgOps3hToEhC6FLg
X-IronPort-AV: E=Sophos;i="4.55,358,1278288000"; d="scan'208";a="272159429"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-2.cisco.com with ESMTP; 12 Aug 2010 14:09:54 +0000
Received: from sjc-vpnasa-833.cisco.com (sjc-vpnasa-833.cisco.com [10.21.107.64]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o7CE9sIi026569; Thu, 12 Aug 2010 14:09:54 GMT
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset="us-ascii"
From: Ralph Droms <rdroms@cisco.com>
In-Reply-To: <BA887853-17B9-4FD9-B6BC-08E0E0CAA40D@juniper.net>
Date: Thu, 12 Aug 2010 07:09:53 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E0C9FCA-302E-4219-9176-81607352C56C@cisco.com>
References: <20100810223005.AA3E73A6AE3@core3.amsl.com> <F6FAFA3B-EFE3-4108-90B7-370A872CD5C7@free.fr> <6D86FFCC-62BB-4658-B0E0-E7CB63269530@cisco.com> <BA887853-17B9-4FD9-B6BC-08E0E0CAA40D@juniper.net>
To: Alain Durand <adurand@juniper.net>
X-Mailer: Apple Mail (2.1078)
Cc: Softwires <softwires@ietf.org>
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: Thu, 12 Aug 2010 14:09:18 -0000

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