IETF Logo Mail Archive

Re: [BEHAVE] Home NAPT44 - How many ports?

Simon Perreault <simon.perreault@viagenie.ca> Thu, 06 June 2013 07:29 UTC

Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BE3421F9635 for <behave@ietfa.amsl.com>; Thu, 6 Jun 2013 00:29:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 Exr+Xl4oDtTb for <behave@ietfa.amsl.com>; Thu, 6 Jun 2013 00:29:44 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 482C321F9640 for <behave@ietf.org>; Thu, 6 Jun 2013 00:29:42 -0700 (PDT)
Received: from [IPv6:::1] (unknown [IPv6:2001:660:3001:4012:2905:fce2:6a47:af4e]) by jazz.viagenie.ca (Postfix) with ESMTPSA id AFD744149F for <behave@ietf.org>; Thu, 6 Jun 2013 03:29:40 -0400 (EDT)
Message-ID: <51B03A65.6040701@viagenie.ca>
Date: Thu, 06 Jun 2013 09:29:41 +0200
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: behave@ietf.org
References: <45A697A8FFD7CF48BCF2BE7E106F0604090A0A82@xmb-rcd-x04.cisco.com> <51AF805D.4000101@nttv6.jp> <B14A62A57AB87D45BB6DD7D9D2B78F0B116D33C0@xmb-rcd-x06.cisco.com>
In-Reply-To: <B14A62A57AB87D45BB6DD7D9D2B78F0B116D33C0@xmb-rcd-x06.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Subject: Re: [BEHAVE] Home NAPT44 - How many ports?
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2013 07:29:44 -0000

Le 2013-06-05 21:04, Rajiv Asati (rajiva) a écrit :
> That's a good suggestion, though the captured data suggests that UDP NAT exhaustion is not a problem, but TCP NAT is.

For better TCP scaling, I'd be curious to see how your data set would 
look like if the NAT used endpoint-dependent mapping with aggressive 
port overloading for HTTP connections. Since HTTP clients often connect 
to several different hosts in parallel, multiple connections could share 
the same source port. And HTTP doesn't need EIM for NAT traversal.

Simon

v2.23.0 | Report a Bug | By Email