IETF Logo Mail Archive

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

Simon Perreault <simon.perreault@viagenie.ca> Mon, 10 June 2013 12:46 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 EDE2321F86B2 for <behave@ietfa.amsl.com>; Mon, 10 Jun 2013 05:46:35 -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 A0YP6aSaKFx1 for <behave@ietfa.amsl.com>; Mon, 10 Jun 2013 05:46:34 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0EF6A21F8481 for <behave@ietf.org>; Mon, 10 Jun 2013 05:38:49 -0700 (PDT)
Received: from [IPv6:::1] (unknown [IPv6:2001:660:3001:4012:975:db0c:5b8b:bf26]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 7C15D4044B for <behave@ietf.org>; Mon, 10 Jun 2013 08:38:31 -0400 (EDT)
Message-ID: <51B5C8C5.5030006@viagenie.ca>
Date: Mon, 10 Jun 2013 14:38:29 +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> <51B03A65.6040701@viagenie.ca> <5309D333-092B-45C6-B57B-8F6AB5AEF185@apple.com>
In-Reply-To: <5309D333-092B-45C6-B57B-8F6AB5AEF185@apple.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: Mon, 10 Jun 2013 12:46:36 -0000

Le 2013-06-08 03:10, james woodyatt a écrit :
> On Jun 6, 2013, at 00:29 , Simon Perreault <simon.perreault@viagenie.ca> wrote:
>
>> And HTTP doesn't need EIM for NAT traversal.
>
> You're going to make me send a PCP requests to get EI mappings for my TCP state in the NAT?

No, I'm suggesting that a NAT could by itself decide to use EDM for HTTP 
flows. There's no PCP here, and nothing to change on the clients.

Simon

v2.23.0 | Report a Bug | By Email