From behave-bounces@ietf.org  Fri May  2 03:05:17 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC4013A6D64;
	Fri,  2 May 2008 03:05:17 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 076843A6C5E
	for <behave@core3.amsl.com>; Fri,  2 May 2008 03:05:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 6f7YbJB2obxn for <behave@core3.amsl.com>;
	Fri,  2 May 2008 03:05:15 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id A51FA3A6E31
	for <behave@ietf.org>; Fri,  2 May 2008 03:05:14 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	470682084A; Fri,  2 May 2008 12:05:15 +0200 (CEST)
X-AuditID: c1b4fb3c-af09dbb00000193b-ad-481ae75bfa55
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	2F35520808; Fri,  2 May 2008 12:05:15 +0200 (CEST)
Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 May 2008 12:05:14 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 2 May 2008 12:05:14 +0200
Message-ID: <A91F30A632473A47B40C18D2B107CA6F039EC307@esealmw105.eemea.ericsson.se>
In-Reply-To: <200804290911.32173.simon.perreault@viagenie.ca>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-ietf-behave-turn-ipv6-04
thread-index: Acip+pPK+E3TcNU8Tca7yDFYfPRhAgCM1Bvw
References: <200804290911.32173.simon.perreault@viagenie.ca>
From: "Oscar Novo" <oscar.novo@ericsson.com>
To: "Simon Perreault" <simon.perreault@viagenie.ca>,
	"Gonzalo Camarillo" <gonzalo.camarillo@ericsson.com>
X-OriginalArrivalTime: 02 May 2008 10:05:14.0910 (UTC)
	FILETIME=[043BC3E0:01C8AC3C]
X-Brightmail-Tracker: AAAAAA==
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Comments on draft-ietf-behave-turn-ipv6-04
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Simon,

Thanks for your comments. We'll include them in the next version. 
Regarding your comment 4.2, the draft already defined a 420 (unknown
attribute) for a wrong family.

Cheers,

Oscar

-----Original Message-----
From: Simon Perreault [mailto:simon.perreault@viagenie.ca] 
Sent: 29. huhtikuuta 2008 16:12
To: Gonzalo Camarillo; Oscar Novo
Cc: behave@ietf.org
Subject: Comments on draft-ietf-behave-turn-ipv6-04

Hello,

I had a first reading of draft-ietf-behave-turn-ipv6-04. Here are a few
comments.

1. Last paragraph of section 4.1:

   The REQUEST-ADDRESS-TYPE attribute MAY only be present in Allocate
   Requests.

This is in contradiction with section 4.2 which describes the usage of
REQUESTED-ADDRESS-TYPE in the Refresh request.

Also, s/REQUEST/REQUESTED/.

2. In section 4.2, there is confusing talk about bindings. Please
s/binding/allocation/ because you do not want to confuse the reader with
STUN bindings when you're really talking about TURN allocations.

3. In section 4.2:

   If the Allocate Response contains the same transport address as
   previously obtained, the binding has been refreshed.

There's an "else" missing. I suggest that server refresh the allocation
if the REQUESTED-ADDRESS-TYPE attribute is missing or of the same type
as previously allocated. If it is present but of the wrong family, reply
with a 400 Bad Request.

4. The last paragraph of section 5.1:

   If the REQUESTED-ADDRESS-TYPE attribute is absent, the server MUST
   allocate a IPv4 transport address to the TURN client.

This is incompatible with the current TURN draft, which says that the
relayed address must be of the same family as the mapped address, which
may be IPv6.

Otherwise, this draft is very straightforward and easy to understand.

Thanks,
Simon
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May  2 04:32:23 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0D6683A6928;
	Fri,  2 May 2008 04:32:23 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A58173A6815
	for <behave@core3.amsl.com>; Fri,  2 May 2008 04:32:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.099
X-Spam-Level: 
X-Spam-Status: No, score=-6.099 tagged_above=-999 required=5
	tests=[AWL=-0.150, BAYES_00=-2.599, HELO_EQ_SE=0.35,
	MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 bVqchoJSE2GZ for <behave@core3.amsl.com>;
	Fri,  2 May 2008 04:32:19 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 39A8B3A6AA4
	for <behave@ietf.org>; Fri,  2 May 2008 04:32:19 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	32941204E2
	for <behave@ietf.org>; Fri,  2 May 2008 13:32:20 +0200 (CEST)
X-AuditID: c1b4fb3e-ac995bb000004ec0-48-481afbc330b6
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	E88E920526
	for <behave@ietf.org>; Fri,  2 May 2008 13:32:19 +0200 (CEST)
Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 May 2008 13:32:18 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C8AC48.2DABF4FF"
Date: Fri, 2 May 2008 13:32:18 +0200
Message-ID: <A91F30A632473A47B40C18D2B107CA6F039EC309@esealmw105.eemea.ericsson.se>
In-Reply-To: <200804290911.32173.simon.perreault@viagenie.ca>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: =?iso-8859-1?Q?Nueva_versi=F3n_de_turn=3A_draft-ietf-behave-turn-ipv6-05?=
thread-index: Acip+pPK+E3TcNU8Tca7yDFYfPRhAgCTW+Yg
References: <200804290911.32173.simon.perreault@viagenie.ca>
From: "Oscar Novo" <oscar.novo@ericsson.com>
To: "Gonzalo Camarillo" <gonzalo.camarillo@ericsson.com>
X-OriginalArrivalTime: 02 May 2008 11:32:18.0864 (UTC)
	FILETIME=[2DF3E300:01C8AC48]
X-Brightmail-Tracker: AAAAAA==
Cc: behave@ietf.org
Subject: [BEHAVE] =?iso-8859-1?q?Nueva_versi=F3n_de_turn=3A_draft-ietf-beh?=
	=?iso-8859-1?q?ave-turn-ipv6-05?=
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8AC48.2DABF4FF
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Buenas,

Aqu=ED te envio la nueva versi=F3n del draft con los comentarios del tio =
(abajo).

Oscar

-----Original Message-----
From: Simon Perreault [mailto:simon.perreault@viagenie.ca]=20
Sent: 29. huhtikuuta 2008 16:12
To: Gonzalo Camarillo; Oscar Novo
Cc: behave@ietf.org
Subject: Comments on draft-ietf-behave-turn-ipv6-04

Hello,

I had a first reading of draft-ietf-behave-turn-ipv6-04. Here are a few =
comments.

1. Last paragraph of section 4.1:

   The REQUEST-ADDRESS-TYPE attribute MAY only be present in Allocate
   Requests.

This is in contradiction with section 4.2 which describes the usage of =
REQUESTED-ADDRESS-TYPE in the Refresh request.

Also, s/REQUEST/REQUESTED/.

2. In section 4.2, there is confusing talk about bindings. Please =
s/binding/allocation/ because you do not want to confuse the reader with =
STUN bindings when you're really talking about TURN allocations.

3. In section 4.2:

   If the Allocate Response contains the same transport address as
   previously obtained, the binding has been refreshed.

There's an "else" missing. I suggest that server refresh the allocation =
if the REQUESTED-ADDRESS-TYPE attribute is missing or of the same type =
as previously allocated. If it is present but of the wrong family, reply =
with a 400 Bad Request.

4. The last paragraph of section 5.1:

   If the REQUESTED-ADDRESS-TYPE attribute is absent, the server MUST
   allocate a IPv4 transport address to the TURN client.

This is incompatible with the current TURN draft, which says that the =
relayed address must be of the same family as the mapped address, which =
may be IPv6.

Otherwise, this draft is very straightforward and easy to understand.

Thanks,
Simon

------_=_NextPart_001_01C8AC48.2DABF4FF
Content-Type: text/plain;
	name="draft-ietf-behave-turn-ipv6-05.txt"
Content-Transfer-Encoding: base64
Content-Description: draft-ietf-behave-turn-ipv6-05.txt
Content-Disposition: attachment;
	filename="draft-ietf-behave-turn-ipv6-05.txt"

DQoNCg0KQkVIQVZFICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgRy4gQ2FtYXJpbGxvDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIE8uIE5vdm8NCkludGVuZGVkIHN0YXR1czog
U3RhbmRhcmRzIFRyYWNrICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBFcmljc3Nvbg0K
RXhwaXJlczogTm92ZW1iZXIgMywgMjAwOCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgIE1heSAyLCAyMDA4DQoNCg0KICAgIFRyYXZlcnNhbCBVc2luZyBSZWxheXMgYXJvdW5kIE5B
VCAoVFVSTikgRXh0ZW5zaW9uIGZvciBJUHY0L0lQdjYNCiAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICBUcmFuc2l0aW9uDQogICAgICAgICAgICAgICAgICAgZHJhZnQtaWV0Zi1iZWhhdmUt
dHVybi1pcHY2LTA1LnR4dA0KDQpTdGF0dXMgb2YgdGhpcyBNZW1vDQoNCiAgIEJ5IHN1Ym1pdHRp
bmcgdGhpcyBJbnRlcm5ldC1EcmFmdCwgZWFjaCBhdXRob3IgcmVwcmVzZW50cyB0aGF0IGFueQ0K
ICAgYXBwbGljYWJsZSBwYXRlbnQgb3Igb3RoZXIgSVBSIGNsYWltcyBvZiB3aGljaCBoZSBvciBz
aGUgaXMgYXdhcmUNCiAgIGhhdmUgYmVlbiBvciB3aWxsIGJlIGRpc2Nsb3NlZCwgYW5kIGFueSBv
ZiB3aGljaCBoZSBvciBzaGUgYmVjb21lcw0KICAgYXdhcmUgd2lsbCBiZSBkaXNjbG9zZWQsIGlu
IGFjY29yZGFuY2Ugd2l0aCBTZWN0aW9uIDYgb2YgQkNQIDc5Lg0KDQogICBJbnRlcm5ldC1EcmFm
dHMgYXJlIHdvcmtpbmcgZG9jdW1lbnRzIG9mIHRoZSBJbnRlcm5ldCBFbmdpbmVlcmluZw0KICAg
VGFzayBGb3JjZSAoSUVURiksIGl0cyBhcmVhcywgYW5kIGl0cyB3b3JraW5nIGdyb3Vwcy4gIE5v
dGUgdGhhdA0KICAgb3RoZXIgZ3JvdXBzIG1heSBhbHNvIGRpc3RyaWJ1dGUgd29ya2luZyBkb2N1
bWVudHMgYXMgSW50ZXJuZXQtDQogICBEcmFmdHMuDQoNCiAgIEludGVybmV0LURyYWZ0cyBhcmUg
ZHJhZnQgZG9jdW1lbnRzIHZhbGlkIGZvciBhIG1heGltdW0gb2Ygc2l4IG1vbnRocw0KICAgYW5k
IG1heSBiZSB1cGRhdGVkLCByZXBsYWNlZCwgb3Igb2Jzb2xldGVkIGJ5IG90aGVyIGRvY3VtZW50
cyBhdCBhbnkNCiAgIHRpbWUuICBJdCBpcyBpbmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1E
cmFmdHMgYXMgcmVmZXJlbmNlDQogICBtYXRlcmlhbCBvciB0byBjaXRlIHRoZW0gb3RoZXIgdGhh
biBhcyAid29yayBpbiBwcm9ncmVzcy4iDQoNCiAgIFRoZSBsaXN0IG9mIGN1cnJlbnQgSW50ZXJu
ZXQtRHJhZnRzIGNhbiBiZSBhY2Nlc3NlZCBhdA0KICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pZXRm
LzFpZC1hYnN0cmFjdHMudHh0Lg0KDQogICBUaGUgbGlzdCBvZiBJbnRlcm5ldC1EcmFmdCBTaGFk
b3cgRGlyZWN0b3JpZXMgY2FuIGJlIGFjY2Vzc2VkIGF0DQogICBodHRwOi8vd3d3LmlldGYub3Jn
L3NoYWRvdy5odG1sLg0KDQogICBUaGlzIEludGVybmV0LURyYWZ0IHdpbGwgZXhwaXJlIG9uIE5v
dmVtYmVyIDMsIDIwMDguDQoNCkFic3RyYWN0DQoNCiAgIFRoaXMgZG9jdW1lbnQgZGVmaW5lcyB0
aGUgUkVRVUVTVEVELUFERFJFU1MtVFlQRSBhdHRyaWJ1dGUgZm9yIHRoZQ0KICAgVHJhdmVyc2Fs
IFVzaW5nIFJlbGF5cyBhcm91bmQgTkFUIChUVVJOKSwgd2hpY2ggYWxsb3dzIGEgY2xpZW50IHRv
DQogICBleHBsaWNpdGx5IHJlcXVlc3QgdGhlIGFkZHJlc3MgdHlwZSB0aGUgVFVSTiBzZXJ2ZXIg
d2lsbCBhbGxvY2F0ZQ0KICAgKGUuZy4sIGFuIElQdjQtb25seSBub2RlIG1heSByZXF1ZXN0IHRo
ZSBUVVJOIHNlcnZlciB0byBhbGxvY2F0ZSBhbg0KICAgSVB2NiBhZGRyZXNzKS4gIEFkZGl0aW9u
YWxseSwgdGhpcyBkb2N1bWVudCBhbHNvIGRlZmluZXMgYSBuZXcgZXJyb3INCiAgIHJlc3BvbnNl
IGNvZGUgd2l0aCB0aGUgdmFsdWUgNDQwIChBZGRyZXNzIEZhbWlseSBub3QgU3VwcG9ydGVkKS4N
Cg0KDQoNCg0KDQoNCg0KDQpDYW1hcmlsbG8gJiBOb3ZvICAgICAgICBFeHBpcmVzIE5vdmVtYmVy
IDMsIDIwMDggICAgICAgICAgICAgICAgW1BhZ2UgMV0NCgwNCkludGVybmV0LURyYWZ0ICAgVFVS
TiBFeHRlbnNpb24gZm9yIElQdjQvSVB2NiB0cmFuc2l0aW9uICAgICAgICBNYXkgMjAwOA0KDQoN
ClRhYmxlIG9mIENvbnRlbnRzDQoNCiAgIDEuICBJbnRyb2R1Y3Rpb24gIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMw0KICAgMi4gIFRlcm1pbm9sb2d5
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAzDQog
ICAzLiAgT3ZlcnZpZXcgb2YgT3BlcmF0aW9uIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIDMNCiAgIDQuICBDbGllbnQgQmVoYXZpb3IgLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gNA0KICAgICA0LjEuICBJbml0aWFsIEFsbG9j
YXRlIFJlcXVlc3QgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiA0DQogICAgIDQu
Mi4gIFJlZnJlc2ggUmVxdWVzdCAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIDUNCiAgIDUuICBTZXJ2ZXIgQmVoYXZpb3IgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gNQ0KICAgICA1LjEuICBBbGxvY2F0ZSBSZXNwb25zZSAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiA1DQogICA2LiAgU2VjdXJp
dHkgQ29uc2lkZXJhdGlvbnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IDYNCiAgIDcuICBJQU5BIENvbnNpZGVyYXRpb25zIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gNg0KICAgICA3LjEuICBOZXcgU1RVTiBBdHRyaWJ1dGUgUmVnaXN0
cnkgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiA2DQogICAgIDcuMi4gIE5ldyBTVFVO
IFJlc3BvbnNlIENvZGUgUmVnaXN0cnkgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDYNCiAg
IDguICBBY2tub3dsZWRnZW1lbnRzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gNg0KICAgOS4gIE5vcm1hdGl2ZSBSZWZlcmVuY2VzICAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiA3DQogICBBdXRob3JzJyBBZGRyZXNzZXMgIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDcNCiAgIEludGVs
bGVjdHVhbCBQcm9wZXJ0eSBhbmQgQ29weXJpZ2h0IFN0YXRlbWVudHMgIC4gLiAuIC4gLiAuIC4g
LiAuIC4gOA0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KQ2FtYXJpbGxvICYgTm92byAgICAgICAgRXhwaXJlcyBOb3ZlbWJl
ciAzLCAyMDA4ICAgICAgICAgICAgICAgIFtQYWdlIDJdDQoMDQpJbnRlcm5ldC1EcmFmdCAgIFRV
Uk4gRXh0ZW5zaW9uIGZvciBJUHY0L0lQdjYgdHJhbnNpdGlvbiAgICAgICAgTWF5IDIwMDgNCg0K
DQoxLiAgSW50cm9kdWN0aW9uDQoNCiAgIFRoZSBUcmF2ZXJzYWwgVXNpbmcgUmVsYXlzIGFyb3Vu
ZCBOQVQgKFRVUk4pIFtJLUQuaWV0Zi1iZWhhdmUtdHVybl0NCiAgIGlzIGEgcHJvdG9jb2wgdGhh
dCBhbGxvd3MgZm9yIGFuIGVsZW1lbnQgYmVoaW5kIGEgTkFUIG9yIGZpcmV3YWxsIHRvDQogICBy
ZWNlaXZlIGluY29taW5nIGRhdGEgb3ZlciBUQ1Agb3IgVURQIGNvbm5lY3Rpb25zLiAgSXQgaXMg
bW9zdCB1c2VmdWwNCiAgIGZvciBlbGVtZW50cyBiZWhpbmQgc3ltbWV0cmljIE5BVHMgb3IgZmly
ZXdhbGxzIHRoYXQgd2lzaCB0byBiZSBvbg0KICAgdGhlIHJlY2VpdmluZyBlbmQgb2YgYSBjb25u
ZWN0aW9uIHRvIGEgc2luZ2xlIHBlZXIuDQoNCiAgIFRoaXMgZG9jdW1lbnQgZGVmaW5lcyB0aGUg
UkVRVUVTVEVELUFERFJFU1MtVFlQRSBhdHRyaWJ1dGUsIHdoaWNoIGlzDQogICBhbiBleHRlbnNp
b24gdG8gVFVSTiB0aGF0IGFsbG93cyBhIGNsaWVudCB0byBleHBsaWNpdGx5IHJlcXVlc3QgdGhl
DQogICBhZGRyZXNzIHR5cGUgdGhlIFRVUk4gc2VydmVyIHdpbGwgYWxsb2NhdGUgKGUuZy4sIGFu
IElQdjQtb25seSBub2RlDQogICBtYXkgcmVxdWVzdCB0aGUgVFVSTiBzZXJ2ZXIgdG8gYWxsb2Nh
dGUgYW4gSVB2NiBhZGRyZXNzKS4NCg0KICAgVGhpcyBkb2N1bWVudCBhbHNvIGRlZmluZXMgYW5k
IHJlZ2lzdGVycyBhIG5ldyBlcnJvciByZXNwb25zZSBjb2RlDQogICB3aXRoIHRoZSB2YWx1ZSA0
NDAgKEFkZHJlc3MgRmFtaWx5IG5vdCBTdXBwb3J0ZWQpLg0KDQoNCjIuICBUZXJtaW5vbG9neQ0K
DQogICBUaGUga2V5IHdvcmRzICJNVVNUIiwgIk1VU1QgTk9UIiwgIlJFUVVJUkVEIiwgIlNIQUxM
IiwgIlNIQUxMIE5PVCIsDQogICAiU0hPVUxEIiwgIlNIT1VMRCBOT1QiLCAiUkVDT01NRU5ERUQi
LCAiTUFZIiwgYW5kICJPUFRJT05BTCIgaW4gdGhpcw0KICAgZG9jdW1lbnQgYXJlIHRvIGJlIGlu
dGVycHJldGVkIGFzIGRlc2NyaWJlZCBpbiBbUkZDMjExOV0uDQoNCg0KMy4gIE92ZXJ2aWV3IG9m
IE9wZXJhdGlvbg0KDQogICBXaGVuIGEgdXNlciB3aXNoZXMgYSBUVVJOIHNlcnZlciB0byBhbGxv
Y2F0ZSBhbiBhZGRyZXNzIG9mIGEgc3BlY2lmaWMNCiAgIHR5cGUsIGl0IHNlbmRzIGFuIEFsbG9j
YXRlIFJlcXVlc3QgdG8gdGhlIFRVUk4gc2VydmVyIHdpdGggYQ0KICAgUkVRVUVTVEVELUFERFJF
U1MtVFlQRSBhdHRyaWJ1dGUuICBUVVJOIGNhbiBydW4gb3ZlciBVRFAgYW5kIFRDUCwgYXMNCiAg
IGl0IGFsbG93cyBmb3IgYSBjbGllbnQgdG8gcmVxdWVzdCBhZGRyZXNzL3BvcnQgcGFpcnMgZm9y
IHJlY2VpdmluZw0KICAgYm90aCBVRFAgYW5kIFRDUC4NCg0KICAgQXNzdW1pbmcgdGhlIHJlcXVl
c3QgaXMgYXV0aGVudGljYXRlZCBhbmQgaGFzIG5vdCBiZWVuIHRhbXBlcmVkIHdpdGgsDQogICB0
aGUgVFVSTiBzZXJ2ZXIgYWxsb2NhdGVzIGEgdHJhbnNwb3J0IGFkZHJlc3Mgb2YgdGhlIHR5cGUg
aW5kaWNhdGVkDQogICBpbiB0aGUgUkVRVUVTVEVELUFERFJFU1MtVFlQRSBhdHRyaWJ1dGUuICBU
aGlzIGFkZHJlc3MgaXMgY2FsbGVkIHRoZQ0KICAgYWxsb2NhdGVkIHRyYW5zcG9ydCBhZGRyZXNz
Lg0KDQogICBUaGUgVFVSTiBzZXJ2ZXIgcmV0dXJucyB0aGUgYWxsb2NhdGVkIGFkZHJlc3MgaW4g
dGhlIHJlc3BvbnNlIHRvIHRoZQ0KICAgQWxsb2NhdGUgUmVxdWVzdC4gIFRoaXMgcmVzcG9uc2Ug
Y29udGFpbnMgYSBSRUxBWS1BRERSRVNTIGF0dHJpYnV0ZQ0KICAgaW5kaWNhdGluZyB0aGUgbWFw
cGVkIElQIGFkZHJlc3MgYW5kIHBvcnQgdGhhdCB0aGUgc2VydmVyIGFzc2lnbmVkIHRvDQogICB0
aGUgY2xpZW50Lg0KDQogICBGb3Igc2ltcGxpY2l0eSByZWFzb25zLCBUVVJOIHNlcnZlcnMgYXJl
IGRlc2lnbmVkIHRvIGFsbG9jYXRlIGENCiAgIHNpbmdsZSBhZGRyZXNzIHBlciBhbGxvY2F0aW9u
IHJlcXVlc3QuICBUaGVyZWZvcmUsIEFsbG9jYXRlIFJlcXVlc3RzDQogICBjYW5ub3QgY2Fycnkg
bW9yZSB0aGFuIG9uZSBSRVFVRVNURUQtQUREUkVTUy1UWVBFIGF0dHJpYnV0ZS4NCiAgIENvbnNl
cXVlbnRseSwgYSBjbGllbnQgdGhhdCB3aXNoZXMgdG8gYWxsb2NhdGUgbW9yZSB0aGFuIG9uZSBh
ZGRyZXNzDQogICBhdCBhIFRVUk4gc2VydmVyIChlLmcuLCBhbiBJUHY0IGFuZCBhbiBJUHY2IGFk
ZHJlc3MpIG5lZWRzIHRvIHBlcmZvcm0NCiAgIHNldmVyYWwgYWxsb2NhdGlvbiByZXF1ZXN0cyAo
b25lIGFsbG9jYXRpb24gcmVxdWVzdCBwZXIgYWRkcmVzcykuDQoNCg0KDQpDYW1hcmlsbG8gJiBO
b3ZvICAgICAgICBFeHBpcmVzIE5vdmVtYmVyIDMsIDIwMDggICAgICAgICAgICAgICAgW1BhZ2Ug
M10NCgwNCkludGVybmV0LURyYWZ0ICAgVFVSTiBFeHRlbnNpb24gZm9yIElQdjQvSVB2NiB0cmFu
c2l0aW9uICAgICAgICBNYXkgMjAwOA0KDQoNCjQuICBDbGllbnQgQmVoYXZpb3INCg0KICAgQ2xp
ZW50IGJlaGF2aW9yIGZvciBBbGxvY2F0ZSByZXF1ZXN0cyBkZXBlbmRzIG9uIHdoZXRoZXIgdGhl
IHJlcXVlc3QNCiAgIGlzIGFuIGluaXRpYWwgb25lLCBmb3IgdGhlIHB1cnBvc2VzIG9mIG9idGFp
bmluZyBhIG5ldyByZWxheWVkDQogICB0cmFuc3BvcnQgYWRkcmVzcywgb3IgYSBzdWJzZXF1ZW50
IG9uZSwgdXNlZCBmb3IgcmVmcmVzaGluZyBhbg0KICAgZXhpc3RpbmcgYWxsb2NhdGlvbi4NCg0K
ICAgVGhlIGNsaWVudCBiZWhhdmlvciBzcGVjaWZpZWQgaGVyZSBhZmZlY3RzIHRoZSB0cmFuc3Bv
cnQgcHJvY2Vzc2luZw0KICAgZGVmaW5lZCBpbiBTZWN0aW9uIDYgb2YgVFVSTiBbSS1ELmlldGYt
YmVoYXZlLXR1cm5dLg0KDQo0LjEuICBJbml0aWFsIEFsbG9jYXRlIFJlcXVlc3QNCg0KICAgQSBj
bGllbnQgdGhhdCB3aXNoZXMgdG8gb2J0YWluIGEgdHJhbnNwb3J0IGFkZHJlc3Mgb2YgYSBzcGVj
aWZpYw0KICAgYWRkcmVzcyB0eXBlIGluY2x1ZGVzIGEgUkVRVUVTVEVELUFERFJFU1MtVFlQRSBh
dHRyaWJ1dGUgaW4gdGhlDQogICBBbGxvY2F0ZSBSZXF1ZXN0IHRoYXQgc2VuZHMgdG8gdGhlIFRV
Uk4gc2VydmVyLiAgQ2xpZW50cyBNVVNUIE5PVA0KICAgaW5jbHVkZSBtb3JlIHRoYW4gb25lIFJF
UVVFU1RFRC1BRERSRVNTLVRZUEUgYXR0cmlidXRlIGluIGFuIEFsbG9jYXRlDQogICBSZXF1ZXN0
LiAgVGhlIG1lY2hhbmlzbXMgdG8gZm9ybXVsYXRlIGFuIEFsbG9jYXRlIFJlcXVlc3QgYXJlDQog
ICBkZXNjcmliZWQgaW4gU2VjdGlvbiA2LjEgYW5kIDYuMyBvZiBbSS1ELmlldGYtYmVoYXZlLXR1
cm5dLg0KDQogICBUaGUgUkVRVUVTVEVELUFERFJFU1MtVFlQRSBhdHRyaWJ1dGUgaXMgdXNlZCBi
eSBjbGllbnRzIHRvIHJlcXVlc3QNCiAgIHRoZSBhbGxvY2F0aW9uIG9mIGEgc3BlY2lmaWMgYWRk
cmVzcyB0eXBlIGZyb20gYSBzZXJ2ZXIuICBUaGUNCiAgIGZvbGxvd2luZyBpcyB0aGUgZm9ybWF0
IG9mIHRoZSBSRVFVRVNURUQtQUREUkVTUy1UWVBFIGF0dHJpYnV0ZS4NCiAgIE5vdGUgdGhhdCBU
VVJOIGF0dHJpYnV0ZXMgYXJlIFRMViAoVHlwZS1MZW5ndGgtVmFsdWUpIGVuY29kZWQsIHdpdGgg
YQ0KICAgMTYgYml0IHR5cGUsIGEgMTYgYml0IGxlbmd0aCwgYW5kIGEgdmFyaWFibGUtbGVuZ3Ro
IHZhbHVlLg0KDQoNCg0KICAgICAgMCAgICAgICAgICAgICAgICAgICAxICAgICAgICAgICAgICAg
ICAgIDIgICAgICAgICAgICAgICAgICAgMw0KICAgICAgMCAxIDIgMyA0IDUgNiA3IDggOSAwIDEg
MiAzIDQgNSA2IDcgOCA5IDAgMSAyIDMgNCA1IDYgNyA4IDkgMCAxDQogICAgICstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rDQog
ICAgIHwgICAgICAgICBUeXBlICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgIExlbmd0aCAg
ICAgICAgICAgICB8DQogICAgICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rDQogICAgIHwgICAgIEZhbWlseSAgICB8ICAgICAg
ICAgICAgUmVzZXJ2ZWQgICAgICAgICAgICAgICAgICAgICAgICAgICB8DQogICAgICstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
DQoNCg0KICAgICAgICAgICBGaWd1cmUgMTogRm9ybWF0IG9mIFJFUVVFU1RFRC1BRERSRVNTLVRZ
UEUgQXR0cmlidXRlDQoNCiAgIFR5cGU6IHRoZSB0eXBlIG9mIHRoZSBSRVFVRVNURUQtQUREUkVT
Uy1UWVBFIGF0dHJpYnV0ZSBpcyAweDAwMTcuICBBcw0KICAgc3BlY2lmaWVkIGluIFtJLUQuaWV0
Zi1iZWhhdmUtcmZjMzQ4OWJpc10sIGF0dHJpYnV0ZXMgd2l0aCB2YWx1ZXMNCiAgIGJldHdlZW4g
MHgwMDAwIGFuZCAweDdGRkYgYXJlIGNvbXByZWhlbnNpb24tcmVxdWlyZWQsIHdoaWNoIG1lYW5z
DQogICB0aGF0IHRoZSBjbGllbnQgb3Igc2VydmVyIGNhbm5vdCBzdWNjZXNzZnVsbHkgcHJvY2Vz
cyB0aGUgbWVzc2FnZQ0KICAgdW5sZXNzIGl0IHVuZGVyc3RhbmRzIHRoZSBhdHRyaWJ1dGUuDQoN
CiAgIExlbmd0aDogdGhpcyAxNi1iaXQgZmllbGQgY29udGFpbnMgdGhlIGxlbmd0aCBvZiB0aGUg
YXR0cmlidXRlIGluDQogICBieXRlcy4gIFRoZSBsZW5ndGggb2YgdGhpcyBhdHRyaWJ1dGUgaXMg
NCBieXRlcy4NCg0KICAgRmFtaWx5OiB0aGVyZSBhcmUgdHdvIHZhbHVlcyBkZWZpbmVkIGZvciB0
aGlzIGZpZWxkIGFuZCBzcGVjaWZpZWQgaW4NCg0KDQoNCkNhbWFyaWxsbyAmIE5vdm8gICAgICAg
IEV4cGlyZXMgTm92ZW1iZXIgMywgMjAwOCAgICAgICAgICAgICAgICBbUGFnZSA0XQ0KDA0KSW50
ZXJuZXQtRHJhZnQgICBUVVJOIEV4dGVuc2lvbiBmb3IgSVB2NC9JUHY2IHRyYW5zaXRpb24gICAg
ICAgIE1heSAyMDA4DQoNCg0KICAgW0ktRC5pZXRmLWJlaGF2ZS1yZmMzNDg5YmlzXTogMHgwMSBm
b3IgSVB2NCBhZGRyZXNzZXMgYW5kIDB4MDIgZm9yDQogICBJUHY2IGFkZHJlc3Nlcy4NCg0KICAg
UmVzZXJ2ZWQ6IGF0IHRoaXMgcG9pbnQsIHRoZSAyNCBiaXRzIGluIHRoZSByZXNlcnZlZCBmaWVs
ZCBTSE9VTEQgYmUNCiAgIHNldCB0byB6ZXJvIGJ5IHRoZSBjbGllbnQgYW5kIE1VU1QgYmUgaWdu
b3JlZCBieSB0aGUgc2VydmVyLg0KDQo0LjIuICBSZWZyZXNoIFJlcXVlc3QNCg0KICAgVG8gcGVy
Zm9ybSBhbiBhbGxvY2F0aW9uIHJlZnJlc2gsIHRoZSBjbGllbnQgZ2VuZXJhdGVzIGEgUmVmcmVz
aA0KICAgUmVxdWVzdCBhcyBkZXNjcmliZWQgaW4gU2VjdGlvbiA3LjEgYW5kIDcuMyBvZg0KICAg
W0ktRC5pZXRmLWJlaGF2ZS10dXJuXS4gIFRoZSBjbGllbnQgaW5jbHVkZXMgdGhlIHNhbWUgUkVR
VUVTVEVELQ0KICAgQUREUkVTUy1UWVBFIGF0dHJpYnV0ZSBhcyBpdCBpbmNsdWRlZCBpbiBpdHMg
aW5pdGlhbCBBbGxvY2F0ZQ0KICAgUmVxdWVzdC4NCg0KICAgSWYgdGhlIEFsbG9jYXRlIFJlc3Bv
bnNlIGNvbnRhaW5zIHRoZSBzYW1lIHRyYW5zcG9ydCBhZGRyZXNzIGFzDQogICBwcmV2aW91c2x5
IG9idGFpbmVkIG9yIHRoZSBSRVFVRVNURUQtQUREUkVTUy1UWVBFIGF0dHJpYnV0ZSBpcw0KICAg
bWlzc2luZywgdGhlIGFsbG9jYXRpb24gaGFzIGJlZW4gcmVmcmVzaGVkLiAgSWYsIGhvd2V2ZXIs
IHRoZQ0KICAgcmVzcG9uc2Ugd2FzIGFuIEFsbG9jYXRlIEVycm9yIFJlc3BvbnNlIHdpdGggYW4g
RVJST1ItQ09ERSBiZXR3ZWVuDQogICA1MDAgdG8gNTk5LCB0aGUgY2xpZW50IE1BWSByZXNlbmQg
dGhlIHJlZnJlc2ggcmVxdWVzdC4gIEFueSBvdGhlcg0KICAgQWxsb2NhdGUgRXJyb3IgUmVzcG9u
c2UgY29kZXMgaW1wbHkgdGhhdCB0aGUgdHJhbnNhY3Rpb24gaGFzIGZhaWxlZC4NCg0KICAgVGhl
IFJFUVVFU1RFRC1BRERSRVNTLVRZUEUgYXR0cmlidXRlIE1BWSBvbmx5IGJlIHByZXNlbnQgaW4g
QWxsb2NhdGUNCiAgIFJlcXVlc3RzIGFuZCBSZWZyZXNoIFJlcXVlc3QuDQoNCg0KNS4gIFNlcnZl
ciBCZWhhdmlvcg0KDQogICBUaGUgc2VydmVyIGJlaGF2aW9yIHNwZWNpZmllZCBoZXJlIGFmZmVj
dHMgdGhlIHRyYW5zcG9ydCBwcm9jZXNzaW5nDQogICBkZWZpbmVkIGluIFNlY3Rpb24gNiBhbmQg
NyBvZiBUVVJOIFtJLUQuaWV0Zi1iZWhhdmUtdHVybl0uDQoNCjUuMS4gIEFsbG9jYXRlIFJlc3Bv
bnNlDQoNCiAgIEFzc3VtaW5nIHRoZSByZXF1ZXN0IGlzIGF1dGhlbnRpY2F0ZWQgYW5kIGhhcyBu
b3QgYmVlbiB0YW1wZXJlZCB3aXRoLA0KICAgdGhlIFRVUk4gc2VydmVyIHByb2Nlc3NlcyB0aGUg
cmVxdWVzdC4gIEZvbGxvd2luZyB0aGUgcnVsZXMgaW4NCiAgIFtJLUQuaWV0Zi1iZWhhdmUtcmZj
MzQ4OWJpc10sIGlmIHRoZSBzZXJ2ZXIgZG9lcyBub3QgdW5kZXJzdGFuZCB0aGUNCiAgIFJFUVVF
U1RFRC1BRERSRVNTLVRZUEUgYXR0cmlidXRlLCBpdCBnZW5lcmF0ZXMgYW4gQWxsb2NhdGUgRXJy
b3INCiAgIFJlc3BvbnNlLCB3aGljaCBpbmNsdWRlcyBhbiBFUlJPUi1DT0RFIGF0dHJpYnV0ZSB3
aXRoIHJlc3BvbnNlIGNvZGUNCiAgIDQyMCAoVW5rbm93biBBdHRyaWJ1dGUpLiAgVGhpcyByZXNw
b25zZSB3aWxsIGNvbnRhaW4gYW4gVU5LTk9XTi0NCiAgIEFUVFJJQlVURSBhdHRyaWJ1dGUgbGlz
dGluZyB0aGUgdW5rbm93biBSRVFVRVNURUQtQUREUkVTUy1UWVBFDQogICBhdHRyaWJ1dGUuDQoN
CiAgIFRoaXMgZG9jdW1lbnQgZGVmaW5lcyB0aGUgZm9sbG93aW5nIG5ldyBlcnJvciByZXNwb25z
ZSBjb2RlOg0KDQogICA0NDAgKEFkZHJlc3MgRmFtaWx5IG5vdCBTdXBwb3J0ZWQpOiAgVGhlIHNl
cnZlciBkaWQgbm90IHN1cHBvcnQgdGhlDQogICAgICBhZGRyZXNzIGZhbWlseSByZXF1ZXN0ZWQg
YnkgdGhlIGNsaWVudC4gIFRoZSBjbGllbnQgU0hPVUxEIG5vdA0KICAgICAgcmV0cnkuDQoNCiAg
IElmIHRoZSBzZXJ2ZXIgZG9lcyBub3Qgc3VwcG9ydCB0aGUgYWRkcmVzcyBmYW1pbHkgcmVxdWVz
dGVkIGJ5IHRoZQ0KDQoNCg0KQ2FtYXJpbGxvICYgTm92byAgICAgICAgRXhwaXJlcyBOb3ZlbWJl
ciAzLCAyMDA4ICAgICAgICAgICAgICAgIFtQYWdlIDVdDQoMDQpJbnRlcm5ldC1EcmFmdCAgIFRV
Uk4gRXh0ZW5zaW9uIGZvciBJUHY0L0lQdjYgdHJhbnNpdGlvbiAgICAgICAgTWF5IDIwMDgNCg0K
DQogICBjbGllbnQsIGl0IE1VU1QgZ2VuZXJhdGUgYW4gQWxsb2NhdGUgRXJyb3IgUmVzcG9uc2Us
IGFuZCBpdCBNVVNUDQogICBpbmNsdWRlIGFuIEVSUk9SLUNPREUgYXR0cmlidXRlIHdpdGggdGhl
IHJlc3BvbnNlIGNvZGUgZGVmaW5lZCBpbg0KICAgdGhpcyBkcmFmdCwgNDQwIChBZGRyZXNzIEZh
bWlseSBub3QgU3VwcG9ydGVkKS4NCg0KICAgSWYgdGhlIHNlcnZlciBjYW4gc3VjY2Vzc2Z1bGx5
IHByb2Nlc3MgdGhlIHJlcXVlc3QsIGl0IGFsbG9jYXRlcyBhDQogICB0cmFuc3BvcnQgYWRkcmVz
cyB0byB0aGUgVFVSTiBjbGllbnQsIGNhbGxlZCB0aGUgYWxsb2NhdGVkIHRyYW5zcG9ydA0KICAg
YWRkcmVzcywgYW5kIHJldHVybnMgaXQgaW4gdGhlIHJlc3BvbnNlIHRvIHRoZSBBbGxvY2F0ZSBS
ZXF1ZXN0Lg0KDQogICBBcyBzcGVjaWZpZWQgaW4gW0ktRC5pZXRmLWJlaGF2ZS10dXJuXSwgdGhl
IEFsbG9jYXRlIFJlc3BvbnNlDQogICBjb250YWlucyB0aGUgc2FtZSB0cmFuc2FjdGlvbiBJRCBj
b250YWluZWQgaW4gdGhlIEFsbG9jYXRlIFJlcXVlc3QNCiAgIGFuZCB0aGUgUkVMQVktQUREUkVT
UyBhdHRyaWJ1dGUgdGhhdCBzZXRzIGl0IHRvIHRoZSBhbGxvY2F0ZWQNCiAgIHRyYW5zcG9ydCBh
ZGRyZXNzLg0KDQogICBUaGUgUkVMQVktQUREUkVTUyBhdHRyaWJ1dGUgaW5kaWNhdGVzIHRoZSBt
YXBwZWQgSVAgYWRkcmVzcyBhbmQgcG9ydC4NCiAgIEl0IGlzIGVuY29kZWQgaW4gdGhlIHNhbWUg
d2F5IGFzIHRoZSBYT1ItTUFQUEVELUFERFJFU1MNCiAgIFtJLUQuaWV0Zi1iZWhhdmUtcmZjMzQ4
OWJpc10uDQoNCiAgIElmIHRoZSBSRVFVRVNURUQtQUREUkVTUy1UWVBFIGF0dHJpYnV0ZSBpcyBh
YnNlbnQsIHRoZSBzZXJ2ZXIgTVVTVA0KICAgYWxsb2NhdGUgYW4gSVB2NiB0cmFuc3BvcnQgYWRk
cmVzcyB0byB0aGUgVFVSTiBjbGllbnQuDQoNCg0KNi4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25z
DQoNCiAgIFRoZSBhdHRyaWJ1dGUgYW5kIGVycm9yIHJlc3BvbnNlIGNvZGUgZGVmaW5lZCBpbiB0
aGlzIGRvY3VtZW50IGRvIG5vdA0KICAgaGF2ZSBhbnkgc3BlY2lhbCBzZWN1cml0eSBjb25zaWRl
cmF0aW9ucyBiZXlvbmQgdGhvc2UgZm9yIG90aGVyDQogICBhdHRyaWJ1dGVzIGFuZCBFcnJvciBy
ZXNwb25zZSBjb2Rlcy4gIEFsbCB0aGUgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMNCiAgIGFwcGxp
Y2FibGUgdG8gU1RVTiBbSS1ELmlldGYtYmVoYXZlLXJmYzM0ODliaXNdIGFuZCBUVVJOIGFyZQ0K
ICAgYXBwbGljYWJsZSB0byB0aGlzIGRvY3VtZW50IGFzIHdlbGwuDQoNCg0KNy4gIElBTkEgQ29u
c2lkZXJhdGlvbnMNCg0KICAgVGhlIElBTkEgaXMgcmVxdWVzdGVkIHRvIHJlZ2lzdGVyIHRoZSBm
b2xsb3dpbmcgdmFsdWVzIHVuZGVyIHRoZSBTVFVODQogICBBdHRyaWJ1dGVzIHJlZ2lzdHJ5IGFu
ZCB1bmRlciB0aGUgU1RVTiBSZXNwb25zZSBDb2RlIFJlZ2lzdHJ5Lg0KDQo3LjEuICBOZXcgU1RV
TiBBdHRyaWJ1dGUgUmVnaXN0cnkNCg0KICAgMHgwMDE3OiBSRVFVRVNURUQtQUREUkVTUy1UWVBF
DQoNCjcuMi4gIE5ldyBTVFVOIFJlc3BvbnNlIENvZGUgUmVnaXN0cnkNCg0KICAgNDQwIEFkZHJl
c3MgRmFtaWx5IG5vdCBTdXBwb3J0ZWQNCg0KDQo4LiAgQWNrbm93bGVkZ2VtZW50cw0KDQogICBU
aGUgYXV0aG9ycyB3b3VsZCBsaWtlIHRvIHRoYW5rIEFsZnJlZCBFLiBIZWdnZXN0YWQgYW5kIFJl
bWkgRGVuaXMtDQogICBDb3VybW9udCBmb3IgdGhlaXIgZmVlZGJhY2sgb24gdGhpcyBkb2N1bWVu
dC4NCg0KDQoNCkNhbWFyaWxsbyAmIE5vdm8gICAgICAgIEV4cGlyZXMgTm92ZW1iZXIgMywgMjAw
OCAgICAgICAgICAgICAgICBbUGFnZSA2XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICBUVVJOIEV4dGVu
c2lvbiBmb3IgSVB2NC9JUHY2IHRyYW5zaXRpb24gICAgICAgIE1heSAyMDA4DQoNCg0KOS4gIE5v
cm1hdGl2ZSBSZWZlcmVuY2VzDQoNCiAgIFtJLUQuaWV0Zi1iZWhhdmUtcmZjMzQ4OWJpc10NCiAg
ICAgICAgICAgICAgUm9zZW5iZXJnLCBKLiwgTWFoeSwgUi4sIE1hdHRoZXdzLCBQLiwgYW5kIEQu
IFdpbmcsDQogICAgICAgICAgICAgICJTZXNzaW9uIFRyYXZlcnNhbCBVdGlsaXRpZXMgZm9yIChO
QVQpIChTVFVOKSIsDQogICAgICAgICAgICAgIGRyYWZ0LWlldGYtYmVoYXZlLXJmYzM0ODliaXMt
MTUgKHdvcmsgaW4gcHJvZ3Jlc3MpLA0KICAgICAgICAgICAgICBGZWJydWFyeSAyMDA4Lg0KDQog
ICBbSS1ELmlldGYtYmVoYXZlLXR1cm5dDQogICAgICAgICAgICAgIFJvc2VuYmVyZywgSi4sIE1h
aHksIFIuLCBhbmQgUC4gTWF0dGhld3MsICJUcmF2ZXJzYWwgVXNpbmcNCiAgICAgICAgICAgICAg
UmVsYXlzIGFyb3VuZCBOQVQgKFRVUk4pOiBSZWxheSBFeHRlbnNpb25zIHRvIFNlc3Npb24NCiAg
ICAgICAgICAgICAgVHJhdmVyc2FsIFV0aWxpdGllcyBmb3IgTkFUIChTVFVOKSIsDQogICAgICAg
ICAgICAgIGRyYWZ0LWlldGYtYmVoYXZlLXR1cm4tMDcgKHdvcmsgaW4gcHJvZ3Jlc3MpLA0KICAg
ICAgICAgICAgICBGZWJydWFyeSAyMDA4Lg0KDQogICBbUkZDMjExOV0gIEJyYWRuZXIsIFMuLCAi
S2V5IHdvcmRzIGZvciB1c2UgaW4gUkZDcyB0byBJbmRpY2F0ZQ0KICAgICAgICAgICAgICBSZXF1
aXJlbWVudCBMZXZlbHMiLCBCQ1AgMTQsIFJGQyAyMTE5LCBNYXJjaCAxOTk3Lg0KDQoNCkF1dGhv
cnMnIEFkZHJlc3Nlcw0KDQogICBHb256YWxvIENhbWFyaWxsbw0KICAgRXJpY3Nzb24NCiAgIEhp
cnNhbGFudGllIDExDQogICBKb3J2YXMgIDAyNDIwDQogICBGaW5sYW5kDQoNCiAgIEVtYWlsOiBH
b256YWxvLkNhbWFyaWxsb0Blcmljc3Nvbi5jb20NCg0KDQogICBPc2NhciBOb3ZvDQogICBFcmlj
c3Nvbg0KICAgSGlyc2FsYW50aWUgMTENCiAgIEpvcnZhcyAgMDI0MjANCiAgIEZpbmxhbmQNCg0K
ICAgRW1haWw6IE9zY2FyLk5vdm9AZXJpY3Nzb24uY29tDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KQ2FtYXJpbGxvICYgTm92byAgICAgICAgRXhwaXJlcyBOb3ZlbWJlciAzLCAyMDA4ICAg
ICAgICAgICAgICAgIFtQYWdlIDddDQoMDQpJbnRlcm5ldC1EcmFmdCAgIFRVUk4gRXh0ZW5zaW9u
IGZvciBJUHY0L0lQdjYgdHJhbnNpdGlvbiAgICAgICAgTWF5IDIwMDgNCg0KDQpGdWxsIENvcHly
aWdodCBTdGF0ZW1lbnQNCg0KICAgQ29weXJpZ2h0IChDKSBUaGUgSUVURiBUcnVzdCAoMjAwOCku
DQoNCiAgIFRoaXMgZG9jdW1lbnQgaXMgc3ViamVjdCB0byB0aGUgcmlnaHRzLCBsaWNlbnNlcyBh
bmQgcmVzdHJpY3Rpb25zDQogICBjb250YWluZWQgaW4gQkNQIDc4LCBhbmQgZXhjZXB0IGFzIHNl
dCBmb3J0aCB0aGVyZWluLCB0aGUgYXV0aG9ycw0KICAgcmV0YWluIGFsbCB0aGVpciByaWdodHMu
DQoNCiAgIFRoaXMgZG9jdW1lbnQgYW5kIHRoZSBpbmZvcm1hdGlvbiBjb250YWluZWQgaGVyZWlu
IGFyZSBwcm92aWRlZCBvbiBhbg0KICAgIkFTIElTIiBiYXNpcyBhbmQgVEhFIENPTlRSSUJVVE9S
LCBUSEUgT1JHQU5JWkFUSU9OIEhFL1NIRSBSRVBSRVNFTlRTDQogICBPUiBJUyBTUE9OU09SRUQg
QlkgKElGIEFOWSksIFRIRSBJTlRFUk5FVCBTT0NJRVRZLCBUSEUgSUVURiBUUlVTVCBBTkQNCiAg
IFRIRSBJTlRFUk5FVCBFTkdJTkVFUklORyBUQVNLIEZPUkNFIERJU0NMQUlNIEFMTCBXQVJSQU5U
SUVTLCBFWFBSRVNTDQogICBPUiBJTVBMSUVELCBJTkNMVURJTkcgQlVUIE5PVCBMSU1JVEVEIFRP
IEFOWSBXQVJSQU5UWSBUSEFUIFRIRSBVU0UgT0YNCiAgIFRIRSBJTkZPUk1BVElPTiBIRVJFSU4g
V0lMTCBOT1QgSU5GUklOR0UgQU5ZIFJJR0hUUyBPUiBBTlkgSU1QTElFRA0KICAgV0FSUkFOVElF
UyBPRiBNRVJDSEFOVEFCSUxJVFkgT1IgRklUTkVTUyBGT1IgQSBQQVJUSUNVTEFSIFBVUlBPU0Uu
DQoNCg0KSW50ZWxsZWN0dWFsIFByb3BlcnR5DQoNCiAgIFRoZSBJRVRGIHRha2VzIG5vIHBvc2l0
aW9uIHJlZ2FyZGluZyB0aGUgdmFsaWRpdHkgb3Igc2NvcGUgb2YgYW55DQogICBJbnRlbGxlY3R1
YWwgUHJvcGVydHkgUmlnaHRzIG9yIG90aGVyIHJpZ2h0cyB0aGF0IG1pZ2h0IGJlIGNsYWltZWQg
dG8NCiAgIHBlcnRhaW4gdG8gdGhlIGltcGxlbWVudGF0aW9uIG9yIHVzZSBvZiB0aGUgdGVjaG5v
bG9neSBkZXNjcmliZWQgaW4NCiAgIHRoaXMgZG9jdW1lbnQgb3IgdGhlIGV4dGVudCB0byB3aGlj
aCBhbnkgbGljZW5zZSB1bmRlciBzdWNoIHJpZ2h0cw0KICAgbWlnaHQgb3IgbWlnaHQgbm90IGJl
IGF2YWlsYWJsZTsgbm9yIGRvZXMgaXQgcmVwcmVzZW50IHRoYXQgaXQgaGFzDQogICBtYWRlIGFu
eSBpbmRlcGVuZGVudCBlZmZvcnQgdG8gaWRlbnRpZnkgYW55IHN1Y2ggcmlnaHRzLiAgSW5mb3Jt
YXRpb24NCiAgIG9uIHRoZSBwcm9jZWR1cmVzIHdpdGggcmVzcGVjdCB0byByaWdodHMgaW4gUkZD
IGRvY3VtZW50cyBjYW4gYmUNCiAgIGZvdW5kIGluIEJDUCA3OCBhbmQgQkNQIDc5Lg0KDQogICBD
b3BpZXMgb2YgSVBSIGRpc2Nsb3N1cmVzIG1hZGUgdG8gdGhlIElFVEYgU2VjcmV0YXJpYXQgYW5k
IGFueQ0KICAgYXNzdXJhbmNlcyBvZiBsaWNlbnNlcyB0byBiZSBtYWRlIGF2YWlsYWJsZSwgb3Ig
dGhlIHJlc3VsdCBvZiBhbg0KICAgYXR0ZW1wdCBtYWRlIHRvIG9idGFpbiBhIGdlbmVyYWwgbGlj
ZW5zZSBvciBwZXJtaXNzaW9uIGZvciB0aGUgdXNlIG9mDQogICBzdWNoIHByb3ByaWV0YXJ5IHJp
Z2h0cyBieSBpbXBsZW1lbnRlcnMgb3IgdXNlcnMgb2YgdGhpcw0KICAgc3BlY2lmaWNhdGlvbiBj
YW4gYmUgb2J0YWluZWQgZnJvbSB0aGUgSUVURiBvbi1saW5lIElQUiByZXBvc2l0b3J5IGF0DQog
ICBodHRwOi8vd3d3LmlldGYub3JnL2lwci4NCg0KICAgVGhlIElFVEYgaW52aXRlcyBhbnkgaW50
ZXJlc3RlZCBwYXJ0eSB0byBicmluZyB0byBpdHMgYXR0ZW50aW9uIGFueQ0KICAgY29weXJpZ2h0
cywgcGF0ZW50cyBvciBwYXRlbnQgYXBwbGljYXRpb25zLCBvciBvdGhlciBwcm9wcmlldGFyeQ0K
ICAgcmlnaHRzIHRoYXQgbWF5IGNvdmVyIHRlY2hub2xvZ3kgdGhhdCBtYXkgYmUgcmVxdWlyZWQg
dG8gaW1wbGVtZW50DQogICB0aGlzIHN0YW5kYXJkLiAgUGxlYXNlIGFkZHJlc3MgdGhlIGluZm9y
bWF0aW9uIHRvIHRoZSBJRVRGIGF0DQogICBpZXRmLWlwckBpZXRmLm9yZy4NCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQpDYW1hcmlsbG8gJiBOb3ZvICAgICAgICBFeHBpcmVzIE5vdmVtYmVyIDMsIDIw
MDggICAgICAgICAgICAgICAgW1BhZ2UgOF0NCgwNCg0K

------_=_NextPart_001_01C8AC48.2DABF4FF
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave

------_=_NextPart_001_01C8AC48.2DABF4FF--


From behave-bounces@ietf.org  Fri May  2 05:03:26 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1300F3A69C9;
	Fri,  2 May 2008 05:03:26 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 192E93A69C9
	for <behave@core3.amsl.com>; Fri,  2 May 2008 05:03:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 xXdmqHXe9ITY for <behave@core3.amsl.com>;
	Fri,  2 May 2008 05:03:23 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id D76783A67FD
	for <behave@ietf.org>; Fri,  2 May 2008 05:03:22 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m42C3K9D030559; Fri, 2 May 2008 15:03:21 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 2 May 2008 15:03:14 +0300
Received: from esdhcp041120.research.nokia.com ([172.21.41.120]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 2 May 2008 15:03:14 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: "ext Philip Matthews" <philip_matthews@magma.ca>
Date: Fri, 2 May 2008 15:04:26 +0300
User-Agent: KMail/1.9.9
References: <47F3FA30.2060403@acm.org>
	<200804030732.23763.remi.denis-courmont@nokia.com>
	<63DF6CD6-9865-4721-A5A8-83816D3F7918@magma.ca>
In-Reply-To: <63DF6CD6-9865-4721-A5A8-83816D3F7918@magma.ca>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805021504.26754.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 02 May 2008 12:03:14.0217 (UTC)
	FILETIME=[7FD44990:01C8AC4C]
X-Nokia-AV: Clean
Cc: behave@ietf.org
Subject: Re: [BEHAVE] IPv4/IPv6 relayed address allocation
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Le Thursday 24 April 2008 23:17:13 ext Philip Matthews, vous avez =E9crit=
=A0:
> > IMHO, I think TURN-07 is wrong and TURN-IPv6 is right.
> >
> > The relay cannot know if there was a protocol translator in the
> > middle, so that would be the only way to obtain sane defaults.
> >
> > So either the client must always explicitly specify the address
> > family, or the default should be independent of the relay-reflexive
> > address of the client.
>
> Sorry to be slow in replying here.
>
> I would really prefer to stick with the current turn-07 proposal and
> fix turn-ipv6 to match.
>
> If we went with the turn0-ipv6 proposal, then the base TURN
> specification would have to specify how to relay between IPv6 and
> IPv4.

In either case, IPv6 support is currently somewhat broken in TURN-07. =

Especially, the handling IPv6 flow information field is left unspecified, =

which is certainly wrong.

From a more general perspective, having the application-layer semantics dep=
end =

on the IP protocol version of the client looks like very bad engineering to =

me. Imagine DNS servers would return different results depending if you que=
ry =

them over v4 or v6!?!

Looking at TURN-07:

No issue for DSCP, ECN and TTL.
The DF bit text does simply not apply to IPv6. So no issue either.
No show-stopper with the current Path MTU text. The MTU would become always =

576, even in IPv6 case.

> This would happen if the server's transport address was IPv6, =

> since the base specification would always allocate a v4 relayed-
> transport-address. In particular, the base spec would have to go into
> the details of how to translate the IP headers when doing "fully-
> compliant relaying" (as described at the last meeting in Philly). This
> I would really like to avoid.

It is difficult to respond to such comments out of the blue. I cannot seem =
to =

find the relevant part of the spec at the moment.

> So instead, a TURN client much check the address family of the relayed-
> transport-address it gets back, just like it much check the address
> family of the mapped-address (these two families will always be the
> same under the current base spec proposal). If the client cannot
> handle this family, then it must delete the allocation.

This is IMHO broken. If the TURN server is dual-stack, IPv6 clients will on=
ly =

be able to use IPv6 with it, and IPv4 clients will only be able to use IPv4.

Since turn-ipv6 is not a mandatory extension, a well-designed TURN client =

implementation cannot assume the server supports it.

> If the WG feels this is not acceptable, then I will propose that we
> remove all handling of IPv6 from the base spec, and let draft-ietf-
> behave-turn-ipv6 cover these cases.
-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May  2 05:05:48 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 06D9628C146;
	Fri,  2 May 2008 05:05:48 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 721D83A6D21
	for <behave@core3.amsl.com>; Fri,  2 May 2008 05:05:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 Pz9bAaKx7BHf for <behave@core3.amsl.com>;
	Fri,  2 May 2008 05:05:42 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id 733BA28C425
	for <behave@ietf.org>; Fri,  2 May 2008 05:05:16 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m42C4wwU031987; Fri, 2 May 2008 15:05:13 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 2 May 2008 15:05:00 +0300
Received: from esdhcp041120.research.nokia.com ([172.21.41.120]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 2 May 2008 15:05:00 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: Dan Wing <dwing@cisco.com>
Date: Fri, 2 May 2008 15:06:12 +0300
User-Agent: KMail/1.9.9
References: <4810C3ED.7030901@ericsson.com>
In-Reply-To: <4810C3ED.7030901@ericsson.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805021506.12807.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 02 May 2008 12:05:00.0091 (UTC)
	FILETIME=[BEEF60B0:01C8AC4C]
X-Nokia-AV: Clean
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Consensus call on Adding "Client" attribute to STUN
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


	Dan,

I think I'll wait for the conclusion of this before I update the test vecto=
rs. =

I can see it coming that people will ask for a CLIENT attribute there.

Is that OK?

Le Thursday 24 April 2008 20:31:25 ext Magnus Westerlund, vous avez =E9crit=
=A0:
> This is a one week+ consensus call (until the 5th of May) if the WG
> thinks that STUN (draft-ietf-behave-rfc3489bis) shall be extended with
> an additional attribute "Client" before publication.
>
> With the general description along the lines of:
>
>     X.Y CLIENT
>
>     The client attribute contains a textual description of the software
>     being used by the client, including manufacturer and version number.
>     The attribute has no impact on operation of the protocol, and serves
>     only as a tool for diagnostic and debugging purposes.  The value of
>     CLIENT is variable length.  It MUST be a UTF-8 [RFC3629] encoded
>     sequence of less than 128 characters (which can be as long as 763
>     bytes).
>
> And some Security Considerations on the risk for targeted attacks
> against clients with this information. Plus other text needed to bring
> it in consistently
>
> The text is open for wordsmithing by the editors of the STUN spec.
>
> Please indicate your position on adding this or not.
>
> Cheers
>
> Magnus Westerlund
>
> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> F=E4r=F6gatan 6                | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave



-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May  2 05:23:01 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C3F303A6B56;
	Fri,  2 May 2008 05:23:01 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5D6E63A6A15
	for <behave@core3.amsl.com>; Fri,  2 May 2008 05:23:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
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 NeBoHckpnMHM for <behave@core3.amsl.com>;
	Fri,  2 May 2008 05:22:59 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2])
	by core3.amsl.com (Postfix) with ESMTP id 62B163A6B56
	for <behave@ietf.org>; Fri,  2 May 2008 05:22:59 -0700 (PDT)
Received: by jazz.viagenie.ca (Postfix, from userid 8)
	id 41E5929E1495; Fri,  2 May 2008 08:22:31 -0400 (EDT)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67])
	by jazz.viagenie.ca (Postfix) with ESMTP id 3940029E1485;
	Fri,  2 May 2008 08:22:31 -0400 (EDT)
From: Simon Perreault <simon.perreault@viagenie.ca>
Organization: =?iso-8859-1?q?Viag=E9nie?=
To: "Oscar Novo" <oscar.novo@ericsson.com>
Date: Fri, 2 May 2008 08:22:30 -0400
User-Agent: KMail/1.9.9
References: <200804290911.32173.simon.perreault@viagenie.ca>
	<A91F30A632473A47B40C18D2B107CA6F039EC307@esealmw105.eemea.ericsson.se>
In-Reply-To: <A91F30A632473A47B40C18D2B107CA6F039EC307@esealmw105.eemea.ericsson.se>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805020822.31007.simon.perreault@viagenie.ca>
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Comments on draft-ietf-behave-turn-ipv6-04
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Friday 02 May 2008 06:05:14 Oscar Novo wrote:
> Regarding your comment 4.2, the draft already defined a 420 (unknown
> attribute) for a wrong family.

That's not what I was talking about. By "wrong family" I meant "of a different 
(but known) family than the one previously allocated." This only makes sense 
in the context of refreshing an existing allocation.

> 3. In section 4.2:
>
>    If the Allocate Response contains the same transport address as
>    previously obtained, the binding has been refreshed.
>
> There's an "else" missing. I suggest that server refresh the allocation
> if the REQUESTED-ADDRESS-TYPE attribute is missing or of the same type
> as previously allocated. If it is present but of the wrong family, reply
> with a 400 Bad Request.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May  2 06:13:09 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 68AD33A6882;
	Fri,  2 May 2008 06:13:09 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 764AC3A6A14
	for <behave@core3.amsl.com>; Fri,  2 May 2008 06:13:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.174
X-Spam-Level: 
X-Spam-Status: No, score=-6.174 tagged_above=-999 required=5 tests=[AWL=0.075, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 QPsNpEefBYhK for <behave@core3.amsl.com>;
	Fri,  2 May 2008 06:13:07 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 8CFBB3A6806
	for <behave@ietf.org>; Fri,  2 May 2008 06:13:07 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	6ACFC2094D; Fri,  2 May 2008 15:13:08 +0200 (CEST)
X-AuditID: c1b4fb3c-ab095bb00000193b-97-481b1364a187
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	4E3612023F; Fri,  2 May 2008 15:13:08 +0200 (CEST)
Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 May 2008 15:13:08 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 2 May 2008 15:13:07 +0200
Message-ID: <A91F30A632473A47B40C18D2B107CA6F039EC30A@esealmw105.eemea.ericsson.se>
In-Reply-To: <200805020822.31007.simon.perreault@viagenie.ca>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-ietf-behave-turn-ipv6-04
thread-index: AcisTzNP7jWl+IHKSKi+GmjRk816dgABtIiw
References: <200804290911.32173.simon.perreault@viagenie.ca>
	<A91F30A632473A47B40C18D2B107CA6F039EC307@esealmw105.eemea.ericsson.se>
	<200805020822.31007.simon.perreault@viagenie.ca>
From: "Oscar Novo" <oscar.novo@ericsson.com>
To: "Simon Perreault" <simon.perreault@viagenie.ca>
X-OriginalArrivalTime: 02 May 2008 13:13:08.0031 (UTC)
	FILETIME=[438984F0:01C8AC56]
X-Brightmail-Tracker: AAAAAA==
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Comments on draft-ietf-behave-turn-ipv6-04
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

OK, now I understand your point. We could add this in the next version
as well.

Thanks,

Oscar 

-----Original Message-----
From: Simon Perreault [mailto:simon.perreault@viagenie.ca] 
Sent: 2. toukokuuta 2008 15:23
To: Oscar Novo
Cc: Gonzalo Camarillo; behave@ietf.org
Subject: Re: Comments on draft-ietf-behave-turn-ipv6-04

On Friday 02 May 2008 06:05:14 Oscar Novo wrote:
> Regarding your comment 4.2, the draft already defined a 420 (unknown
> attribute) for a wrong family.

That's not what I was talking about. By "wrong family" I meant "of a
different (but known) family than the one previously allocated." This
only makes sense in the context of refreshing an existing allocation.

> 3. In section 4.2:
>
>    If the Allocate Response contains the same transport address as
>    previously obtained, the binding has been refreshed.
>
> There's an "else" missing. I suggest that server refresh the 
> allocation if the REQUESTED-ADDRESS-TYPE attribute is missing or of 
> the same type as previously allocated. If it is present but of the 
> wrong family, reply with a 400 Bad Request.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May  2 08:52:53 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 268F93A6BAF;
	Fri,  2 May 2008 08:52:53 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 35E9228C228
	for <behave@core3.amsl.com>; Fri,  2 May 2008 08:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.428
X-Spam-Level: 
X-Spam-Status: No, score=-6.428 tagged_above=-999 required=5
	tests=[AWL=-0.129, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
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 8b836WBgMCsq for <behave@core3.amsl.com>;
	Fri,  2 May 2008 08:52:43 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by core3.amsl.com (Postfix) with ESMTP id F2ED23A6C98
	for <behave@ietf.org>; Fri,  2 May 2008 08:52:42 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,427,1204531200"; d="scan'208";a="24997968"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-5.cisco.com with ESMTP; 02 May 2008 08:52:44 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m42FqiFD000677; 
	Fri, 2 May 2008 08:52:44 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m42FqiXi003861;
	Fri, 2 May 2008 15:52:44 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "=?iso-8859-1?Q?'R=E9mi_Denis-Courmont'?=" <remi.denis-courmont@nokia.com>
References: <4810C3ED.7030901@ericsson.com>
	<200805021506.12807.remi.denis-courmont@nokia.com>
Date: Fri, 2 May 2008 08:52:44 -0700
Message-ID: <0c6401c8ac6c$8fc0c5c0$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <200805021506.12807.remi.denis-courmont@nokia.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: AcisTMrNQtFHqcOiQdiErv13VUOZvAAH2TbQ
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2706; t=1209743564;
	x=1210607564; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Consensus=20call=20on=20Addi
	ng=20=22Client=22=20attribute=20to=20STUN |Sender:=20;
	bh=xEdI2jrkWagWCM3YWPoIj0icHy1bjf5/QmNajZbqxxY=;
	b=lDdvToo92kL3nxOUqeV1rb2oaIXEUru+ppNSGCNHAK63aXx22CJyHZp7F+
	ubyZOGNhbfxoqmRzm7PfpyeD9HlHiMHe5PW5Apd9rNn8waIakb/rDhssrCWR
	iZdeqvRPUz;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Consensus call on Adding "Client" attribute to STUN
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

As chair: fine by me.  I was hoping more people would comment for/against
Magnus's consensus call. =


As an individual and co-author of rfc3489bis:  I support adding the new CLI=
ENT
attribute.

-d


> -----Original Message-----
> From: R=E9mi Denis-Courmont [mailto:remi.denis-courmont@nokia.com] =

> Sent: Friday, May 02, 2008 5:06 AM
> To: Dan Wing
> Cc: behave@ietf.org
> Subject: Re: [BEHAVE] Consensus call on Adding "Client" =

> attribute to STUN
> =

> =

> 	Dan,
> =

> I think I'll wait for the conclusion of this before I update =

> the test vectors. =

> I can see it coming that people will ask for a CLIENT attribute there.
> =

> Is that OK?
> =

> Le Thursday 24 April 2008 20:31:25 ext Magnus Westerlund, =

> vous avez =E9crit=A0:
> > This is a one week+ consensus call (until the 5th of May) if the WG
> > thinks that STUN (draft-ietf-behave-rfc3489bis) shall be =

> extended with
> > an additional attribute "Client" before publication.
> >
> > With the general description along the lines of:
> >
> >     X.Y CLIENT
> >
> >     The client attribute contains a textual description of =

> the software
> >     being used by the client, including manufacturer and =

> version number.
> >     The attribute has no impact on operation of the =

> protocol, and serves
> >     only as a tool for diagnostic and debugging purposes.  =

> The value of
> >     CLIENT is variable length.  It MUST be a UTF-8 [RFC3629] encoded
> >     sequence of less than 128 characters (which can be as =

> long as 763
> >     bytes).
> >
> > And some Security Considerations on the risk for targeted attacks
> > against clients with this information. Plus other text =

> needed to bring
> > it in consistently
> >
> > The text is open for wordsmithing by the editors of the STUN spec.
> >
> > Please indicate your position on adding this or not.
> >
> > Cheers
> >
> > Magnus Westerlund
> >
> > IETF Transport Area Director & TSVWG Chair
> > =

> ----------------------------------------------------------------------
> > Multimedia Technologies, Ericsson Research EAB/TVM
> > =

> ----------------------------------------------------------------------
> > Ericsson AB                | Phone +46 8 4048287
> > F=E4r=F6gatan 6                | Fax   +46 8 7575550
> > S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> > =

> ----------------------------------------------------------------------
> >
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www.ietf.org/mailman/listinfo/behave
> =

> =

> =

> -- =

> R=E9mi Denis-Courmont

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May  2 12:16:05 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF2063A6AE0;
	Fri,  2 May 2008 12:16:05 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0A3D33A6826
	for <behave@core3.amsl.com>; Fri,  2 May 2008 12:16:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5
	tests=[AWL=-0.150, BAYES_00=-2.599, 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 vdaDLVpBHMS7 for <behave@core3.amsl.com>;
	Fri,  2 May 2008 12:16:04 -0700 (PDT)
Received: from mail-09.primus.ca (mail4.primus.ca [216.254.141.171])
	by core3.amsl.com (Postfix) with ESMTP id 02D4028C1D4
	for <behave@ietf.org>; Fri,  2 May 2008 12:16:03 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-09.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1Js0jl-0002RT-0C; Fri, 02 May 2008 15:16:05 -0400
Message-Id: <C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
In-Reply-To: <200805021504.26754.remi.denis-courmont@nokia.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Fri, 2 May 2008 15:16:02 -0400
References: <47F3FA30.2060403@acm.org>
	<200804030732.23763.remi.denis-courmont@nokia.com>
	<63DF6CD6-9865-4721-A5A8-83816D3F7918@magma.ca>
	<200805021504.26754.remi.denis-courmont@nokia.com>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Cc: behave@ietf.org
Subject: Re: [BEHAVE] IPv4/IPv6 relayed address allocation
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Fri, 2-May-08, at 08:04 , R=E9mi Denis-Courmont wrote:
> Le Thursday 24 April 2008 23:17:13 ext Philip Matthews, vous avez  =

> =E9crit :
>>> IMHO, I think TURN-07 is wrong and TURN-IPv6 is right.
>>>
>>> The relay cannot know if there was a protocol translator in the
>>> middle, so that would be the only way to obtain sane defaults.
>>>
>>> So either the client must always explicitly specify the address
>>> family, or the default should be independent of the relay-reflexive
>>> address of the client.
>>
>> Sorry to be slow in replying here.
>>
>> I would really prefer to stick with the current turn-07 proposal and
>> fix turn-ipv6 to match.
>>
>> If we went with the turn0-ipv6 proposal, then the base TURN
>> specification would have to specify how to relay between IPv6 and
>> IPv4.
>
> In either case, IPv6 support is currently somewhat broken in TURN-07.
> Especially, the handling IPv6 flow information field is left  =

> unspecified,
> which is certainly wrong.

This is being fixed.
TURN-08 will say that a server should copy the flow label, and if this  =

cannot be done, then treat the packets to/from each peer as a separate  =

flow with separate labels. This is all part of the new concept of a  =

Preserving allocation (what I called a "Fully-Compliant allocation" in  =

Philly) that I am in the process of adding right now.

>
>
> From a more general perspective, having the application-layer  =

> semantics depend
> on the IP protocol version of the client looks like very bad  =

> engineering to
> me. Imagine DNS servers would return different results depending if  =

> you query
> them over v4 or v6!?!

Don't forget that you get exactly this behavior with a STUN server. If  =

you access the STUN server over IPv6, then the mapped-address you get  =

back is IPv6. If you access the same server over IPv4, you get back a  =

IPv4 mapped-address.

In my view, if one thinks of a TURN server as a relay, then it makes  =

sense that if one sends it v6 packets, they come out as v6 packets on  =

the other end.



>
>
> Looking at TURN-07:
>
> No issue for DSCP, ECN and TTL.
> The DF bit text does simply not apply to IPv6. So no issue either.
> No show-stopper with the current Path MTU text. The MTU would become  =

> always
> 576, even in IPv6 case.

All the text in section 11 has been totally rewritten as part of  =

adding the concept of Preserving vs. Non-Preserving allocations. I  =

have asked a couple of people to look it over, and then I expect to  =

post it. In the mean time, you can look at my presentation in Philly  =

for a high-level description.

>
>
>> This would happen if the server's transport address was IPv6,
>> since the base specification would always allocate a v4 relayed-
>> transport-address. In particular, the base spec would have to go into
>> the details of how to translate the IP headers when doing "fully-
>> compliant relaying" (as described at the last meeting in Philly).  =

>> This
>> I would really like to avoid.
>
> It is difficult to respond to such comments out of the blue. I  =

> cannot seem to
> find the relevant part of the spec at the moment.

See above.

>
>
>> So instead, a TURN client much check the address family of the  =

>> relayed-
>> transport-address it gets back, just like it much check the address
>> family of the mapped-address (these two families will always be the
>> same under the current base spec proposal). If the client cannot
>> handle this family, then it must delete the allocation.
>
> This is IMHO broken. If the TURN server is dual-stack, IPv6 clients  =

> will only
> be able to use IPv6 with it, and IPv4 clients will only be able to  =

> use IPv4.
>
> Since turn-ipv6 is not a mandatory extension, a well-designed TURN  =

> client
> implementation cannot assume the server supports it.


What if the base spec included the REQUESTED-ADDRESS-TYPE attribute  =

with the restriction that the address type given in the REQUESTED- =

ADDRESS-TYPE attribute MUST match the address type in the 5-tuple or  =

the Allocate request is rejected ?
TURN-IPv6 would then lift this restriction.

Would this make things better?


- Philip
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May  2 12:35:54 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9CF603A68E3;
	Fri,  2 May 2008 12:35:54 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A50023A68E3
	for <behave@core3.amsl.com>; Fri,  2 May 2008 12:35:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
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 xOtCUIrS+ixf for <behave@core3.amsl.com>;
	Fri,  2 May 2008 12:35:51 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2])
	by core3.amsl.com (Postfix) with ESMTP id 026A23A68E1
	for <behave@ietf.org>; Fri,  2 May 2008 12:35:51 -0700 (PDT)
Received: by jazz.viagenie.ca (Postfix, from userid 8)
	id B46FE29E1499; Fri,  2 May 2008 15:35:22 -0400 (EDT)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67])
	by jazz.viagenie.ca (Postfix) with ESMTP id ADFB929E1485
	for <behave@ietf.org>; Fri,  2 May 2008 15:35:22 -0400 (EDT)
From: Simon Perreault <simon.perreault@viagenie.ca>
Organization: =?iso-8859-1?q?Viag=E9nie?=
To: behave@ietf.org
Date: Fri, 2 May 2008 15:35:21 -0400
User-Agent: KMail/1.9.9
References: <47F3FA30.2060403@acm.org>
	<200805021504.26754.remi.denis-courmont@nokia.com>
	<C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>
In-Reply-To: <C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805021535.22100.simon.perreault@viagenie.ca>
Subject: Re: [BEHAVE] IPv4/IPv6 relayed address allocation
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Friday 02 May 2008 15:16:02 Philip Matthews wrote:
> What if the base spec included the REQUESTED-ADDRESS-TYPE attribute
> with the restriction that the address type given in the REQUESTED-
> ADDRESS-TYPE attribute MUST match the address type in the 5-tuple or
> the Allocate request is rejected ?
> TURN-IPv6 would then lift this restriction.
>
> Would this make things better?

Hehehe, that would be the shortest RFC ever.


===================

Abstract

This memo lifts a restriction concerning mixed address types in RFCXXXX.

1. Lifting a Restriction

The restriction to the effect that the address family contained in the 
REQUESTED-ADDRESS-TYPE attribute must match that of the server address is 
hereby lifted.

2. IANA Considerations

None.

3. Security Considerations

None.

Acknowledgements

I wish to dedicate this work to my parents, to God, etc. This is my lifetime 
achievement.

References

[RFCXXXX] TURN.

====================


Just don't put the restriction in TURN in the first place! ;)
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May  2 15:49:35 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC6C73A6A94;
	Fri,  2 May 2008 15:49:35 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F00C13A6B2F;
	Fri,  2 May 2008 15:49:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.439
X-Spam-Level: 
X-Spam-Status: No, score=-6.439 tagged_above=-999 required=5 tests=[AWL=0.160, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 XrWYHqxKZYKe; Fri,  2 May 2008 15:49:28 -0700 (PDT)
Received: from zrtps0kp.us.nortel.com (zrtps0kp.nortel.com [47.140.192.56])
	by core3.amsl.com (Postfix) with ESMTP id C49193A6D1B;
	Fri,  2 May 2008 15:49:09 -0700 (PDT)
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com
	[47.103.123.72])
	by zrtps0kp.us.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m42MmLq05414; Fri, 2 May 2008 22:48:22 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 2 May 2008 17:44:36 -0500
Message-ID: <F66D7286825402429571678A16C2F5EE03441E25@zrc2hxm1.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG Review: draft-ietf-sipping-nat-scenarios-07
Thread-Index: AcfkA4JMLLr1haz3SAe+B/y8OjV6qjIoJaLw
From: "Mary Barnes" <mary.barnes@nortel.com>
To: <sipping@ietf.org>
Cc: Chris Boulton <cboulton@avaya.com>, behave@ietf.org,
	Gonzalo.Camarillo@ericsson.com, mmusic@ietf.org
Subject: Re: [BEHAVE] WG Review: draft-ietf-sipping-nat-scenarios-07
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi folks,

This is to announce a Working Group Last Call on the following document
to be published a Best Current Practice (BCP):
http://www.ietf.org/internet-drafts/draft-ietf-sipping-nat-scenarios-08.
txt

The review period will end on 23 May 2008 (3 weeks time). 

Note that I have cross-posted to the BEHAVE and MMUSIC WGs, but ask that
you please send your comments only to the SIPPING WG and author(s). 

The following reviewers have already volunteered:  Vijay Gurbani,
Spencer Dawkins, Francois Audet, and Dan Wing  (thanks guys!)

However, we do encourage others to review and make any final comments on
the document at this time.  

Thanks,
Mary
SIPPING WG co-chair

As a reminder, the SIPPING WG review guidelines are available at:
https://softarmor.com/sipping/process/wg-review/sipping-review-guideline
s.html

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sat May  3 09:21:28 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0ADAF3A695A;
	Sat,  3 May 2008 09:21:28 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EDCED3A67A7;
	Sat,  3 May 2008 09:21:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level: 
X-Spam-Status: No, score=-6.454 tagged_above=-999 required=5 tests=[AWL=0.145, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 G-6onA44lRhS; Sat,  3 May 2008 09:21:26 -0700 (PDT)
Received: from zrtps0kn.us.nortel.com (zrtps0kn.nortel.com [47.140.192.55])
	by core3.amsl.com (Postfix) with ESMTP id 245543A695A;
	Sat,  3 May 2008 09:21:23 -0700 (PDT)
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com
	[47.103.123.72])
	by zrtps0kn.us.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m43GLJ206485; Sat, 3 May 2008 16:21:19 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 3 May 2008 11:17:20 -0500
Message-ID: <F66D7286825402429571678A16C2F5EE03441FA1@zrc2hxm1.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WGLC  Review: draft-ietf-sipping-nat-scenarios-08
Thread-Index: AcfkA4JMLLr1haz3SAe+B/y8OjV6qjIoJaLwACU85/A=
From: "Mary Barnes" <mary.barnes@nortel.com>
To: <sipping@ietf.org>
Cc: Chris Boulton <cboulton@avaya.com>, behave@ietf.org,
	Gonzalo.Camarillo@ericsson.com, mmusic@ietf.org
Subject: [BEHAVE] WGLC  Review: draft-ietf-sipping-nat-scenarios-08
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Sorry folks - obviously I had the wrong title in the original
announcement

-----Original Message-----
From: Barnes, Mary (RICH2:AR00) 
Sent: Friday, May 02, 2008 5:45 PM
To: 'sipping@ietf.org'
Cc: 'Chris Boulton'; 'Gonzalo.Camarillo@ericsson.com';
'jdrosen@cisco.com'; 'behave@ietf.org'; 'mmusic@ietf.org'
Subject: RE: WG Review: draft-ietf-sipping-nat-scenarios-07

Hi folks,

This is to announce a Working Group Last Call on the following document
to be published a Best Current Practice (BCP):
http://www.ietf.org/internet-drafts/draft-ietf-sipping-nat-scenarios-08.
txt

The review period will end on 23 May 2008 (3 weeks time). 

Note that I have cross-posted to the BEHAVE and MMUSIC WGs, but ask that
you please send your comments only to the SIPPING WG and author(s). 

The following reviewers have already volunteered:  Vijay Gurbani,
Spencer Dawkins, Francois Audet, and Dan Wing  (thanks guys!)

However, we do encourage others to review and make any final comments on
the document at this time.  

Thanks,
Mary
SIPPING WG co-chair

As a reminder, the SIPPING WG review guidelines are available at:
https://softarmor.com/sipping/process/wg-review/sipping-review-guideline
s.html

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sun May  4 23:25:18 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 580323A6BC7;
	Sun,  4 May 2008 23:25:17 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2CB3728C192
	for <behave@core3.amsl.com>; Sun,  4 May 2008 23:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.285
X-Spam-Level: 
X-Spam-Status: No, score=-3.285 tagged_above=-999 required=5
	tests=[BAYES_40=-0.185, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
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 7X9t8hV-9HFz for <behave@core3.amsl.com>;
	Sun,  4 May 2008 23:25:05 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 52A5228C306
	for <behave@ietf.org>; Sun,  4 May 2008 23:22:42 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m456LWxM015181; Mon, 5 May 2008 01:22:37 -0500
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 May 2008 09:22:34 +0300
Received: from esdhcp041131.research.nokia.com ([172.21.41.131]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 May 2008 09:22:34 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: "ext Philip Matthews" <philip_matthews@magma.ca>
Date: Mon, 5 May 2008 09:23:50 +0300
User-Agent: KMail/1.9.9
References: <47F3FA30.2060403@acm.org>
	<200805021504.26754.remi.denis-courmont@nokia.com>
	<C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>
In-Reply-To: <C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805050923.50429.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 05 May 2008 06:22:34.0405 (UTC)
	FILETIME=[67FDBD50:01C8AE78]
X-Nokia-AV: Clean
Cc: behave@ietf.org
Subject: Re: [BEHAVE] IPv4/IPv6 relayed address allocation
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Le Friday 02 May 2008 22:16:02 ext Philip Matthews, vous avez =E9crit=A0:
> This is being fixed.
> TURN-08 will say that a server should copy the flow label, and if this
> cannot be done, then treat the packets to/from each peer as a separate
> flow with separate labels. This is all part of the new concept of a
> Preserving allocation (what I called a "Fully-Compliant allocation" in
> Philly) that I am in the process of adding right now.

I myself am not sure what the "proper" handling of the flow infos is. If =

anyone knows, that would be some 6man and/or v6ops people (not including me=
). =

Flow infos is not just like DSCP. Reflecting this, the Linux(-specific) API =

for flow infos is completely different from that of DSCP and TTL...

> > From a more general perspective, having the application-layer
> > semantics depend on the IP protocol version of the client looks
> > like very bad engineering to me. Imagine DNS servers would return
> > different results depending if you query them over v4 or v6!?!
>
> Don't forget that you get exactly this behavior with a STUN server.

Or with any service that gives you your IP address from the perspective of =
the =

server. This seems quite specific, and not very relevant here.

(...)
> What if the base spec included the REQUESTED-ADDRESS-TYPE attribute
> with the restriction that the address type given in the REQUESTED-
> ADDRESS-TYPE attribute MUST match the address type in the 5-tuple or
> the Allocate request is rejected ?
> TURN-IPv6 would then lift this restriction.
>
> Would this make things better?

I think so, yeah.

-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May  5 00:38:36 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 912EC28C154;
	Mon,  5 May 2008 00:38:36 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1C74F3A6B6C;
	Mon,  5 May 2008 00:38:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.492
X-Spam-Level: 
X-Spam-Status: No, score=-3.492 tagged_above=-999 required=5 tests=[AWL=0.207, 
	BAYES_50=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 yCoj0YOB2HRq; Mon,  5 May 2008 00:38:33 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id EF9253A6A81;
	Mon,  5 May 2008 00:38:32 -0700 (PDT)
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m457cE1m013689; Mon, 5 May 2008 10:38:26 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 May 2008 10:38:20 +0300
Received: from esdhcp041131.research.nokia.com ([172.21.41.131]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 May 2008 10:38:19 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: behave@ietf.org
Date: Mon, 5 May 2008 10:39:35 +0300
User-Agent: KMail/1.9.9
References: <F66D7286825402429571678A16C2F5EE03441FA1@zrc2hxm1.corp.nortel.com>
In-Reply-To: <F66D7286825402429571678A16C2F5EE03441FA1@zrc2hxm1.corp.nortel.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805051039.35818.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 05 May 2008 07:38:19.0690 (UTC)
	FILETIME=[FD3130A0:01C8AE82]
X-Nokia-AV: Clean
Cc: mmusic@ietf.org, Chris Boulton <cboulton@avaya.com>, sipping@ietf.org,
	Gonzalo.Camarillo@ericsson.com
Subject: Re: [BEHAVE] WGLC  Review: draft-ietf-sipping-nat-scenarios-08
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

> -----Original Message-----
> From: Barnes, Mary (RICH2:AR00)
> Sent: Friday, May 02, 2008 5:45 PM
> To: 'sipping@ietf.org'
> Cc: 'Chris Boulton'; 'Gonzalo.Camarillo@ericsson.com';
> 'jdrosen@cisco.com'; 'behave@ietf.org'; 'mmusic@ietf.org'
> Subject: RE: WG Review: draft-ietf-sipping-nat-scenarios-07
>
> Hi folks,
>
> This is to announce a Working Group Last Call on the following document
> to be published a Best Current Practice (BCP):
> http://www.ietf.org/internet-drafts/draft-ietf-sipping-nat-scenarios-08.
> txt
>
> The review period will end on 23 May 2008 (3 weeks time).
>
> Note that I have cross-posted to the BEHAVE and MMUSIC WGs, but ask that
> you please send your comments only to the SIPPING WG and author(s).
>
> The following reviewers have already volunteered:  Vijay Gurbani,
> Spencer Dawkins, Francois Audet, and Dan Wing  (thanks guys!)
>
> However, we do encourage others to review and make any final comments on
> the document at this time.

I am overall happy with the document.

Section 5.2 refers to ANAT for v6 media transition. I thought it was being =

deprecated by ICE, so I am a bit confused.

Otherwise, minor typo in section 7.2. Not sure if it comes from bibxml or =

something:
              Camarillo, G., "IPv6 Transcition in the Session Initiation


Best regards,                                      ^^^


-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May  5 04:41:06 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ABC603A6DAE;
	Mon,  5 May 2008 04:41:06 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1775D3A6F31
	for <behave@core3.amsl.com>; Mon,  5 May 2008 04:41:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.191
X-Spam-Level: 
X-Spam-Status: No, score=-0.191 tagged_above=-999 required=5
	tests=[BAYES_40=-0.185, RCVD_IN_DNSWL_LOW=-1, RELAY_IS_203=0.994]
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 Vlq+3kS2yC0l for <behave@core3.amsl.com>;
	Mon,  5 May 2008 04:41:02 -0700 (PDT)
Received: from wipro-blr-out01.wipro.com (wipro-blr-out01.wipro.com
	[203.91.198.74])
	by core3.amsl.com (Postfix) with ESMTP id DE0E83A701E
	for <behave@ietf.org>; Mon,  5 May 2008 04:40:57 -0700 (PDT)
X-AuditID: cb5bdd57-a731cbb000004cff-00-481ef24662c8
Received: from blr-ec-bh01.wipro.com (unknown [10.201.50.91])
	by wipro-blr-out01.wipro.com (Symantec Mail Security) with ESMTP id
	DC8634E4002
	for <behave@ietf.org>; Mon,  5 May 2008 17:10:54 +0530 (IST)
Received: from BLR-EC-MBX08.wipro.com ([10.201.51.212]) by
	blr-ec-bh01.wipro.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 May 2008 17:10:54 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 May 2008 17:10:54 +0530
Message-ID: <C94A49F6B410A047A7EEE7FA6635DA35036A3F20@BLR-EC-MBX08.wipro.com>
In-Reply-To: <200805050923.50429.remi.denis-courmont@nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] :query about data indication...
thread-index: AciueNK7mNqYAU9BTiOP6PV0h+8zVgAK80Pw
References: <47F3FA30.2060403@acm.org><200805021504.26754.remi.denis-courmont@nokia.com><C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>
	<200805050923.50429.remi.denis-courmont@nokia.com>
From: <tamal.biswas@wipro.com>
To: <behave@ietf.org>
X-OriginalArrivalTime: 05 May 2008 11:40:54.0386 (UTC)
	FILETIME=[E0778D20:01C8AEA4]
X-Brightmail-Tracker: AAAAAA==
Subject: [BEHAVE]  :query about data indication...
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


 need a small clarification..
How many times do I need to send the data indication from TURN client?
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May  5 04:46:50 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0C82E3A6DC0;
	Mon,  5 May 2008 04:46:50 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B935D3A6DC0
	for <behave@core3.amsl.com>; Mon,  5 May 2008 04:46:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.896
X-Spam-Level: 
X-Spam-Status: No, score=-4.896 tagged_above=-999 required=5 tests=[AWL=1.404, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 VbY2vx+Wwaou for <behave@core3.amsl.com>;
	Mon,  5 May 2008 04:46:48 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 05E5E3A68A8
	for <behave@ietf.org>; Mon,  5 May 2008 04:46:47 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m45BkOKf018097 for <behave@ietf.org>; Mon, 5 May 2008 06:46:44 -0500
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 May 2008 14:46:05 +0300
Received: from esdhcp041131.research.nokia.com ([172.21.41.131]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 May 2008 14:46:05 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: behave@ietf.org
Date: Mon, 5 May 2008 14:47:20 +0300
User-Agent: KMail/1.9.9
References: <47F3FA30.2060403@acm.org>
	<200805050923.50429.remi.denis-courmont@nokia.com>
	<C94A49F6B410A047A7EEE7FA6635DA35036A3F20@BLR-EC-MBX08.wipro.com>
In-Reply-To: <C94A49F6B410A047A7EEE7FA6635DA35036A3F20@BLR-EC-MBX08.wipro.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805051447.21602.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 05 May 2008 11:46:05.0113 (UTC)
	FILETIME=[99ACBA90:01C8AEA5]
X-Nokia-AV: Clean
Subject: Re: [BEHAVE] :query about data indication...
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Le Monday 05 May 2008 14:40:54 ext tamal.biswas@wipro.com, vous avez =E9cri=
t=A0:
>  need a small clarification..
> How many times do I need to send the data indication from TURN client?

Why would you need to send it more or less than once??

-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May  5 05:33:07 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9D1AD3A6C51;
	Mon,  5 May 2008 05:33:07 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 343283A6C26
	for <behave@core3.amsl.com>; Mon,  5 May 2008 05:33:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.349
X-Spam-Level: 
X-Spam-Status: No, score=-1.349 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6,
	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 R-r2Z8Gw7nxb for <behave@core3.amsl.com>;
	Mon,  5 May 2008 05:33:06 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id 651CD3A6C51
	for <behave@ietf.org>; Mon,  5 May 2008 05:33:06 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id B8C073EA128;
	Mon,  5 May 2008 14:33:04 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id E6A2B3EA0AD;
	Mon,  5 May 2008 14:33:03 +0200 (CEST)
Message-ID: <481EFE86.3060808@free.fr>
Date: Mon, 05 May 2008 14:33:10 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?=
	<remi.denis-courmont@nokia.com>, v6ops <v6ops@ops.ietf.org>
References: <47F3FA30.2060403@acm.org>	<200805021504.26754.remi.denis-courmont@nokia.com>	<C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>
	<200805050923.50429.remi.denis-courmont@nokia.com>
In-Reply-To: <200805050923.50429.remi.denis-courmont@nokia.com>
Cc: behave@ietf.org, ext Philip Matthews <philip_matthews@magma.ca>
Subject: Re: [BEHAVE] IPv4/IPv6 relayed address allocation
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

R=E9mi Denis-Courmont a =E9crit :
> Le Friday 02 May 2008 22:16:02 ext Philip Matthews, vous avez =E9crit :

>> TURN-08 will say that a server should copy the flow label, and if this
>> cannot be done, then treat the packets to/from each peer as a separate
>> flow with separate labels. This is all part of the new concept of a
>> Preserving allocation (what I called a "Fully-Compliant allocation" in
>> Philly) that I am in the process of adding right now.
> =

> I myself am not sure what the "proper" handling of the flow infos is. If =

> anyone knows, that would be some 6man and/or v6ops people (not including =
me). =

> Flow infos is not just like DSCP. Reflecting this, the Linux(-specific) A=
PI =

> for flow infos is completely different from that of DSCP and TTL...

Pending any approved use of flow labels, there is IMU only one =

consistent behavior, everywhere: the flow label field MUST be ignored =

when received, and MUST be set to 0 when created .

If and when some use is approved, it will be time to decide whether, in =

TURN in particular, another behavior is more appropriate.

R=E9mi

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May  5 05:39:06 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4DDCA3A6C51;
	Mon,  5 May 2008 05:39:06 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 038873A6C6E
	for <behave@core3.amsl.com>; Mon,  5 May 2008 05:39:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.398
X-Spam-Level: 
X-Spam-Status: No, score=-1.398 tagged_above=-999 required=5 tests=[AWL=1.207, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RELAY_IS_203=0.994]
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 8PKu1s+0qzi3 for <behave@core3.amsl.com>;
	Mon,  5 May 2008 05:39:02 -0700 (PDT)
Received: from wipro-blr-out01.wipro.com (wipro-blr-out01.wipro.com
	[203.91.198.74])
	by core3.amsl.com (Postfix) with ESMTP id 566F33A6D26
	for <behave@ietf.org>; Mon,  5 May 2008 05:39:02 -0700 (PDT)
X-AuditID: cb5bdd57-a831ebb000004cff-f5-481effe39530
Received: from blr-ec-bh02.wipro.com (unknown [10.201.50.92])
	by wipro-blr-out01.wipro.com (Symantec Mail Security) with ESMTP id
	C1356355C001
	for <behave@ietf.org>; Mon,  5 May 2008 18:08:59 +0530 (IST)
Received: from BLR-EC-MBX08.wipro.com ([10.201.51.212]) by
	blr-ec-bh02.wipro.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 May 2008 18:08:38 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 May 2008 18:08:38 +0530
Message-ID: <C94A49F6B410A047A7EEE7FA6635DA35036A3FC1@BLR-EC-MBX08.wipro.com>
In-Reply-To: <200805051447.21602.remi.denis-courmont@nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE]  :query about data indication...
thread-index: AciupZy53aqkklSCRe+W9hdoe9QFSAABzDsw
References: <47F3FA30.2060403@acm.org>
	<200805050923.50429.remi.denis-courmont@nokia.com>
	<C94A49F6B410A047A7EEE7FA6635DA35036A3F20@BLR-EC-MBX08.wipro.com>
	<200805051447.21602.remi.denis-courmont@nokia.com>
From: <tamal.biswas@wipro.com>
To: <remi.denis-courmont@nokia.com>,
	<behave@ietf.org>
X-OriginalArrivalTime: 05 May 2008 12:38:38.0484 (UTC)
	FILETIME=[F13AF540:01C8AEAC]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [BEHAVE] :query about data indication...
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I was talking of retransmission. As we will be using UDP, so is retransmiss=
ion required? =



Thanks & Regards
Tamal Tanu Biswas

Arise! Awake! and stop not till the goal is reached.
                                               -Swami Vivekananda

-----Original Message-----
From: R=E9mi Denis-Courmont [mailto:remi.denis-courmont@nokia.com] =

Sent: Monday, May 05, 2008 5:17 PM
To: behave@ietf.org
Cc: Tamal Tanu biswas (WT01 - MCE-Mobile Devices)
Subject: Re: [BEHAVE] :query about data indication...

Le Monday 05 May 2008 14:40:54 ext tamal.biswas@wipro.com, vous avez =E9cri=
t=A0:
>  need a small clarification..
> How many times do I need to send the data indication from TURN client?

Why would you need to send it more or less than once??

--
R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May  5 05:48:24 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BC7A928C110;
	Mon,  5 May 2008 05:48:24 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3F6973A682C
	for <behave@core3.amsl.com>; Mon,  5 May 2008 05:48:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level: 
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5
	tests=[BAYES_40=-0.185]
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 4r6bcnTYVW6J for <behave@core3.amsl.com>;
	Mon,  5 May 2008 05:48:19 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2])
	by core3.amsl.com (Postfix) with ESMTP id 953383A6E02
	for <behave@ietf.org>; Mon,  5 May 2008 05:47:19 -0700 (PDT)
Received: by jazz.viagenie.ca (Postfix, from userid 8)
	id A808B29E148E; Mon,  5 May 2008 08:46:48 -0400 (EDT)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67])
	by jazz.viagenie.ca (Postfix) with ESMTP id 9F8A129E1482
	for <behave@ietf.org>; Mon,  5 May 2008 08:46:48 -0400 (EDT)
From: Simon Perreault <simon.perreault@viagenie.ca>
Organization: =?iso-8859-1?q?Viag=E9nie?=
To: behave@ietf.org
Date: Mon, 5 May 2008 08:46:48 -0400
User-Agent: KMail/1.9.9
References: <47F3FA30.2060403@acm.org>
	<200805051447.21602.remi.denis-courmont@nokia.com>
	<C94A49F6B410A047A7EEE7FA6635DA35036A3FC1@BLR-EC-MBX08.wipro.com>
In-Reply-To: <C94A49F6B410A047A7EEE7FA6635DA35036A3FC1@BLR-EC-MBX08.wipro.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805050846.48557.simon.perreault@viagenie.ca>
Subject: Re: [BEHAVE] :query about data indication...
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Monday 05 May 2008 08:38:38 tamal.biswas@wipro.com wrote:
> I was talking of retransmission. As we will be using UDP, so is
> retransmission required?

An indication is never acknowledged. Any retransmission is futile.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May  5 05:48:37 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7169E3A682C;
	Mon,  5 May 2008 05:48:37 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1DC673A69DF
	for <behave@core3.amsl.com>; Mon,  5 May 2008 05:48:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.363
X-Spam-Level: 
X-Spam-Status: No, score=-5.363 tagged_above=-999 required=5 tests=[AWL=0.936, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 0nBdC8QrXNrh for <behave@core3.amsl.com>;
	Mon,  5 May 2008 05:48:25 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id 13A3528C21A
	for <behave@ietf.org>; Mon,  5 May 2008 05:47:53 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m45Cllmg027320 for <behave@ietf.org>; Mon, 5 May 2008 15:47:49 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 May 2008 15:47:00 +0300
Received: from esdhcp041131.research.nokia.com ([172.21.41.131]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 May 2008 15:46:59 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: "ext tamal.biswas@wipro.com" <tamal.biswas@wipro.com>
Date: Mon, 5 May 2008 15:48:16 +0300
User-Agent: KMail/1.9.9
References: <47F3FA30.2060403@acm.org>
	<200805051447.21602.remi.denis-courmont@nokia.com>
	<C94A49F6B410A047A7EEE7FA6635DA35036A3FC1@BLR-EC-MBX08.wipro.com>
In-Reply-To: <C94A49F6B410A047A7EEE7FA6635DA35036A3FC1@BLR-EC-MBX08.wipro.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805051548.16288.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 05 May 2008 12:46:59.0770 (UTC)
	FILETIME=[1C0521A0:01C8AEAE]
X-Nokia-AV: Clean
Cc: behave@ietf.org
Subject: Re: [BEHAVE] :query about data indication...
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Le Monday 05 May 2008 15:38:38 ext tamal.biswas@wipro.com, vous avez =E9cri=
t=A0:
> I was talking of retransmission. As we will be using UDP, so is
> retransmission required?

How could there be retransmission at a layer that does not have an =

acknowledgement mechanism?

-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May  5 05:55:24 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E9AED3A6D26;
	Mon,  5 May 2008 05:55:24 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DF1253A6D26
	for <behave@core3.amsl.com>; Mon,  5 May 2008 05:55:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.597
X-Spam-Level: 
X-Spam-Status: No, score=-5.597 tagged_above=-999 required=5 tests=[AWL=0.702, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 QU3Wvmp5384m for <behave@core3.amsl.com>;
	Mon,  5 May 2008 05:55:23 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 3212F3A6CB9
	for <behave@ietf.org>; Mon,  5 May 2008 05:55:23 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m45Ct0ho022264 for <behave@ietf.org>; Mon, 5 May 2008 07:55:20 -0500
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 May 2008 15:53:59 +0300
Received: from esdhcp041131.research.nokia.com ([172.21.41.131]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 May 2008 15:53:59 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: "ext tamal.biswas@wipro.com" <tamal.biswas@wipro.com>, behave@ietf.org
Date: Mon, 5 May 2008 15:55:16 +0300
User-Agent: KMail/1.9.9
References: <47F3FA30.2060403@acm.org>
	<200805051548.16288.remi.denis-courmont@nokia.com>
	<C94A49F6B410A047A7EEE7FA6635DA35036A3FDB@BLR-EC-MBX08.wipro.com>
In-Reply-To: <C94A49F6B410A047A7EEE7FA6635DA35036A3FDB@BLR-EC-MBX08.wipro.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805051555.16138.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 05 May 2008 12:53:59.0577 (UTC)
	FILETIME=[163E9890:01C8AEAF]
X-Nokia-AV: Clean
Subject: Re: [BEHAVE] :query about data indication...
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Le Monday 05 May 2008 15:48:17 ext tamal.biswas@wipro.com, vous avez =E9cri=
t=A0:
> That is exactly what I am asking...
> Then how can I be sure that data has reached to my peer??

Obviously, you can't. UDP is not a reliable protocol, with nor without TURN.

-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May  5 06:23:07 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A48F3A6C69;
	Mon,  5 May 2008 06:23:07 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0C0D53A6B79
	for <behave@core3.amsl.com>; Mon,  5 May 2008 06:23:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 jddHWAfQ+AMy for <behave@core3.amsl.com>;
	Mon,  5 May 2008 06:23:05 -0700 (PDT)
Received: from mail-08.primus.ca (mail4.primus.ca [216.254.141.171])
	by core3.amsl.com (Postfix) with ESMTP id A25B23A69D4
	for <behave@ietf.org>; Mon,  5 May 2008 06:21:25 -0700 (PDT)
Received: from [216.13.42.68] (helo=[10.10.80.124])
	by mail-08.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1Jt0d8-0007wN-03; Mon, 05 May 2008 09:21:22 -0400
Message-Id: <9925D171-E6BA-4490-B9A8-D44419CA221D@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <481EFE86.3060808@free.fr>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 5 May 2008 09:21:21 -0400
References: <47F3FA30.2060403@acm.org>	<200805021504.26754.remi.denis-courmont@nokia.com>	<C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>
	<200805050923.50429.remi.denis-courmont@nokia.com>
	<481EFE86.3060808@free.fr>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.10.80.124]) [216.13.42.68]
Cc: v6ops <v6ops@ops.ietf.org>, behave@ietf.org
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Mon, 5-May-08, at 08:33 , R=E9mi Despr=E9s wrote:
> R=E9mi Denis-Courmont a =E9crit :
>> Le Friday 02 May 2008 22:16:02 ext Philip Matthews, vous avez =E9crit :
>
>>> TURN-08 will say that a server should copy the flow label, and if  =

>>> this
>>> cannot be done, then treat the packets to/from each peer as a  =

>>> separate
>>> flow with separate labels. This is all part of the new concept of a
>>> Preserving allocation (what I called a "Fully-Compliant  =

>>> allocation" in
>>> Philly) that I am in the process of adding right now.
>> I myself am not sure what the "proper" handling of the flow infos  =

>> is. If anyone knows, that would be some 6man and/or v6ops people  =

>> (not including me). Flow infos is not just like DSCP. Reflecting  =

>> this, the Linux(-specific) API for flow infos is completely  =

>> different from that of DSCP and TTL...
>
> Pending any approved use of flow labels, there is IMU only one  =

> consistent behavior, everywhere: the flow label field MUST be  =

> ignored when received, and MUST be set to 0 when created .
>
> If and when some use is approved, it will be time to decide whether,  =

> in TURN in particular, another behavior is more appropriate.


What about RFC 3697 ??
Are you saying that this does not describe approved behavior?

- Philip
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May  5 08:08:41 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 81B783A6E30;
	Mon,  5 May 2008 08:08:41 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 999AB3A6E03
	for <behave@core3.amsl.com>; Mon,  5 May 2008 08:08:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.261
X-Spam-Level: 
X-Spam-Status: No, score=-1.261 tagged_above=-999 required=5 tests=[AWL=0.688, 
	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 58ysea8xbGZt for <behave@core3.amsl.com>;
	Mon,  5 May 2008 08:08:26 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id 43D173A6AEF
	for <behave@ietf.org>; Mon,  5 May 2008 08:07:02 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id CAF633EA110;
	Mon,  5 May 2008 17:07:00 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id E97903EA0AF;
	Mon,  5 May 2008 17:06:59 +0200 (CEST)
Message-ID: <481F2299.5020305@free.fr>
Date: Mon, 05 May 2008 17:07:05 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <47F3FA30.2060403@acm.org>	<200805021504.26754.remi.denis-courmont@nokia.com>	<C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>
	<200805050923.50429.remi.denis-courmont@nokia.com>
	<481EFE86.3060808@free.fr>
	<9925D171-E6BA-4490-B9A8-D44419CA221D@magma.ca>
In-Reply-To: <9925D171-E6BA-4490-B9A8-D44419CA221D@magma.ca>
Cc: behave@ietf.org
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Philip Matthews wrote :

>> If and when some use is approved, it will be time to decide whether, =

>> in TURN in particular, another behavior is more appropriate.
> =

> =

> What about RFC 3697 ??
> Are you saying that this does not describe approved behavior?

I certainely should not say it this way.
But it is till unclear to me whether there is a real USE of it?

If there is one (with running code etc...), my comment is just inadequate.


Taking this opportunity, here is a proposal:

- Limit the RFC3697 use of flow labels (FLs) to a subset of all their =

possible values.
- The goal is that other future uses are not precluded (or at least are =

not made significantly more difficult).
- For example, have the first bit set to 1, or the first 4 bits set to =

1111, or the first octet different from OxFF.

Regards.

R=E9mi
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May  5 08:45:11 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A5C7E3A6B94;
	Mon,  5 May 2008 08:45:11 -0700 (PDT)
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id C46303A69E8; Mon,  5 May 2008 08:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20080505154501.C46303A69E8@core3.amsl.com>
Date: Mon,  5 May 2008 08:45:01 -0700 (PDT)
Cc: behave@ietf.org
Subject: [BEHAVE] I-D Action:draft-ietf-behave-dccp-00.txt
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Behavior Engineering for Hindrance Avoidance Working Group of the IETF.


	Title           : Network Address Translation (NAT) Behavioral Requirements for DCCP
	Author(s)       : R. Denis-Courmont
	Filename        : draft-ietf-behave-dccp-00.txt
	Pages           : 10
	Date            : 2008-05-04

This document defines a set of requirements for DCCP-capable NATs
that would allow certain applications, such as streaming applications
to operate consistently.  These requirements are very similar to the
TCP requirements for NATs already published by this IETF working
group.  Developing NATs that meet this set of requirements will
greatly increase the likelihood that applications using DCCP will
function properly.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-dccp-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-behave-dccp-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-05-05084330.I-D@ietf.org>


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave

--NextPart--


From behave-bounces@ietf.org  Mon May  5 09:01:12 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4606F3A6A82;
	Mon,  5 May 2008 09:01:12 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 49E4C28C19E
	for <behave@core3.amsl.com>; Mon,  5 May 2008 07:12:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 kGpiHD-Ac-3C for <behave@core3.amsl.com>;
	Mon,  5 May 2008 07:12:43 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id 971293A6D4C
	for <behave@ietf.org>; Mon,  5 May 2008 07:12:42 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m45ECU1T006132; Mon, 5 May 2008 17:12:37 +0300
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 May 2008 17:12:35 +0300
Received: from esebe101.NOE.Nokia.com ([172.21.138.215]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 May 2008 17:12:34 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 May 2008 17:12:34 +0300
Message-ID: <DD129318C94521409355FE397682A23603DB861E@esebe101.NOE.Nokia.com>
In-Reply-To: <9925D171-E6BA-4490-B9A8-D44419CA221D@magma.ca>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IPv6 Flow Label
Thread-Index: AciutA5dqpSWU+cASl+nAudEyKvmKgAAzYXA
References: <47F3FA30.2060403@acm.org>	<200805021504.26754.remi.denis-courmont@nokia.com>	<C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>
	<200805050923.50429.remi.denis-courmont@nokia.com>
	<481EFE86.3060808@free.fr>
	<9925D171-E6BA-4490-B9A8-D44419CA221D@magma.ca>
From: <jarno.rajahalme@nsn.com>
To: <philip_matthews@magma.ca>, <remi.despres@free.fr>
X-OriginalArrivalTime: 05 May 2008 14:12:34.0703 (UTC)
	FILETIME=[10ADB9F0:01C8AEBA]
X-Nokia-AV: Clean
X-Mailman-Approved-At: Mon, 05 May 2008 09:01:11 -0700
Cc: v6ops@ops.ietf.org, behave@ietf.org, Remi.Denis-Courmont@nokia.com
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Philip Matthews wrote:
>On Mon, 5-May-08, at 08:33 , R=E9mi Despr=E9s wrote:
>> R=E9mi Denis-Courmont a =E9crit :
>>> Le Friday 02 May 2008 22:16:02 ext Philip Matthews, vous =

>avez =E9crit :
>>
>>>> TURN-08 will say that a server should copy the flow label, and if =

>>>> this cannot be done, then treat the packets to/from each peer as a =

>>>> separate flow with separate labels.
>>> I myself am not sure what the "proper" handling of the flow infos is. =

>> Pending any approved use of flow labels, there is IMU only one =

>> consistent behavior, everywhere: the flow label field MUST be ignored =

>> when received, and MUST be set to 0 when created .
>>
>> If and when some use is approved, it will be time to decide whether, =

>> in TURN in particular, another behavior is more appropriate.
>
>
>What about RFC 3697 ??
>Are you saying that this does not describe approved behavior?
>

As per RFC 3697, the flow label is interpreted only in the context of the s=
ource and destination addresses. This means that the flow "identity" change=
s when relayed trough a TURN-relay, as the IP addresses change. This is als=
o true for NATs to begin with.

Nevertheless, I'd say the flow label should be copied over, if possible, so=
 that any possible future use would be minimally harmed.

Regards,

	Jarno Rajahalme
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May  5 09:31:02 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D67EA3A697B;
	Mon,  5 May 2008 09:31:02 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 810473A697B
	for <behave@core3.amsl.com>; Mon,  5 May 2008 09:31:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.461
X-Spam-Level: 
X-Spam-Status: No, score=-1.461 tagged_above=-999 required=5 tests=[AWL=0.538, 
	BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 2A52aCK0Bq8R for <behave@core3.amsl.com>;
	Mon,  5 May 2008 09:31:00 -0700 (PDT)
Received: from mail-01.primus.ca (mail3.primus.ca [216.254.141.170])
	by core3.amsl.com (Postfix) with ESMTP id 4475E3A69FB
	for <behave@ietf.org>; Mon,  5 May 2008 09:31:00 -0700 (PDT)
Received: from [216.13.42.68] (helo=[10.10.80.124])
	by mail-01.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1Jt3ac-0001BB-2Y; Mon, 05 May 2008 12:30:59 -0400
Message-Id: <E1324FFA-4E2F-40DA-A14B-96D84AA273D3@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Behave WG <behave@ietf.org>
In-Reply-To: <200805050923.50429.remi.denis-courmont@nokia.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 5 May 2008 12:30:59 -0400
References: <47F3FA30.2060403@acm.org>
	<200805021504.26754.remi.denis-courmont@nokia.com>
	<C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>
	<200805050923.50429.remi.denis-courmont@nokia.com>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.10.80.124]) [216.13.42.68]
Cc: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?= <Remi.Denis-Courmont@nokia.com>
Subject: Re: [BEHAVE] IPv4/IPv6 relayed address allocation
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Folks:

This discussion is prompted by discussions right now in v6OPS around  =

devices to translate between IPv6 and IPv4. So, for example, a client  =

might send an Allocate request over IPv6, but the request might arrive  =

at the TURN server over IPv4 (or vica-versa).

At present (in TURN-07), the TURN server allocates a relayed-transport- =

address in the same address family (IPv4 or IPv6) as the family over  =

which the Allocate request arrived. R=E9mi Denis-Courmont dislikes the  =

fact that the client might get back an address family different from  =

the one it "expected".

So I am looking for comments on one of two options going forward:

1) [Currently in TURN-07] The address family (IPv4 vs IPv6) of a  =

relayed-transport-address is the same as the address family over which  =

the Allocate request arrived.

2) [Proposal] TURN-08 will define the REQUESTED-ADDRESS-TYPE attribute  =

(which is currently defined in draft-ietf-behave-turn-ipv6) which  =

allows the client to request a particular address family for the  =

relayed-transport-address. However, TURN-08 will reject the Allocate  =

request if the requested address family is not the same as the address  =

family over which the Allocate request arrived.

Under either option, TURN-08 will still require that two address  =

families match. That is, TURN-08 will NOT specify IPv4 to IPv6  =

relaying (because the details for doing this are non-trivial). An  =

extension for relaying between address families will be left for draft- =

ietf-behave-turn-ipv6.

So the difference is that, when in cases where option (1) would cause  =

the client to get back an address family different than the one it  =

"expected", option (2) will cause the Allocate request to be rejected.

I am quite happy with option (2).

Comments?

- Philip





On Mon, 5-May-08, at 02:23 , R=E9mi Denis-Courmont wrote:
> Le Friday 02 May 2008 22:16:02 ext Philip Matthews, vous avez =E9crit :
>> This is being fixed.
>> TURN-08 will say that a server should copy the flow label, and if  =

>> this
>> cannot be done, then treat the packets to/from each peer as a  =

>> separate
>> flow with separate labels. This is all part of the new concept of a
>> Preserving allocation (what I called a "Fully-Compliant allocation"  =

>> in
>> Philly) that I am in the process of adding right now.
>
> I myself am not sure what the "proper" handling of the flow infos  =

> is. If
> anyone knows, that would be some 6man and/or v6ops people (not  =

> including me).
> Flow infos is not just like DSCP. Reflecting this, the Linux(- =

> specific) API
> for flow infos is completely different from that of DSCP and TTL...
>
>>> From a more general perspective, having the application-layer
>>> semantics depend on the IP protocol version of the client looks
>>> like very bad engineering to me. Imagine DNS servers would return
>>> different results depending if you query them over v4 or v6!?!
>>
>> Don't forget that you get exactly this behavior with a STUN server.
>
> Or with any service that gives you your IP address from the  =

> perspective of the
> server. This seems quite specific, and not very relevant here.
>
> (...)
>> What if the base spec included the REQUESTED-ADDRESS-TYPE attribute
>> with the restriction that the address type given in the REQUESTED-
>> ADDRESS-TYPE attribute MUST match the address type in the 5-tuple or
>> the Allocate request is rejected ?
>> TURN-IPv6 would then lift this restriction.
>>
>> Would this make things better?
>
> I think so, yeah.
>
> -- =

> R=E9mi Denis-Courmont
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May  5 10:33:42 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C27243A6C38;
	Mon,  5 May 2008 10:33:42 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8962C28C1AB
	for <behave@core3.amsl.com>; Mon,  5 May 2008 10:33:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level: 
X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[AWL=1.207, 
	BAYES_00=-2.599]
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 igpRbjZXIbBL for <behave@core3.amsl.com>;
	Mon,  5 May 2008 10:33:35 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2])
	by core3.amsl.com (Postfix) with ESMTP id 288B23A6C76
	for <behave@ietf.org>; Mon,  5 May 2008 10:33:35 -0700 (PDT)
Received: by jazz.viagenie.ca (Postfix, from userid 8)
	id 1DB4B29E1486; Mon,  5 May 2008 13:33:04 -0400 (EDT)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67])
	by jazz.viagenie.ca (Postfix) with ESMTP id 1464E29E1486
	for <behave@ietf.org>; Mon,  5 May 2008 13:33:04 -0400 (EDT)
From: Simon Perreault <simon.perreault@viagenie.ca>
Organization: =?iso-8859-1?q?Viag=E9nie?=
To: behave@ietf.org
Date: Mon, 5 May 2008 13:33:03 -0400
User-Agent: KMail/1.9.9
References: <47F3FA30.2060403@acm.org>
	<200805050923.50429.remi.denis-courmont@nokia.com>
	<E1324FFA-4E2F-40DA-A14B-96D84AA273D3@magma.ca>
In-Reply-To: <E1324FFA-4E2F-40DA-A14B-96D84AA273D3@magma.ca>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805051333.03912.simon.perreault@viagenie.ca>
Subject: Re: [BEHAVE] IPv4/IPv6 relayed address allocation
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Monday 05 May 2008 12:30:59 Philip Matthews wrote:
> TURN-08 will NOT specify IPv4 to IPv6
> relaying (because the details for doing this are non-trivial).

What details do you have in mind?
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May  5 11:51:52 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3F3E63A6DA4;
	Mon,  5 May 2008 11:51:52 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2154228C2DC;
	Mon,  5 May 2008 11:29:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
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 2P4t12T8WTeZ; Mon,  5 May 2008 11:29:31 -0700 (PDT)
Received: from smtp.mitel.com (smtp.mitel.com [216.191.234.102])
	by core3.amsl.com (Postfix) with ESMTP id 002C728C2B8;
	Mon,  5 May 2008 11:29:30 -0700 (PDT)
Received: from localhost (smtp.mitel.com [127.0.0.1])
	by smtp.mitel.com (Postfix) with ESMTP id D93512C013;
	Mon,  5 May 2008 14:29:29 -0400 (EDT)
X-Virus-Scanned: by amavisd-new (virusonly) at mitel.com
Received: from smtp.mitel.com ([127.0.0.1])
	by localhost (smtp.mitel.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 7bda+84f4Skk; Mon,  5 May 2008 14:29:29 -0400 (EDT)
Received: from LT4GKCG41 (unknown [10.31.8.26])
	by smtp.mitel.com (Postfix) with SMTP id B75492C004;
	Mon,  5 May 2008 14:29:29 -0400 (EDT)
From: "Jerry Yin" <jerry_yin@mitel.com>
To: "Mary Barnes" <mary.barnes@nortel.com>,
	<sipping@ietf.org>
Date: Mon, 5 May 2008 14:29:29 -0400
Message-ID: <GDEOKMPIPEGAEADGFFKEKEEEHNAA.jerry_yin@mitel.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
Importance: Normal
In-Reply-To: <F66D7286825402429571678A16C2F5EE03441FA1@zrc2hxm1.corp.nortel.com>
X-Mailman-Approved-At: Mon, 05 May 2008 11:51:51 -0700
Cc: behave@ietf.org, Gonzalo.Camarillo@ericsson.com
Subject: Re: [BEHAVE] [Sipping] WGLC Review:
	draft-ietf-sipping-nat-scenarios-08
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Here are some comments:

Editorial errors:
1. There are two Figure 6 in page 12 and 14 respectively, and reference
errors to the figures accordingly.
2. Page 13: 'connectionID", do you mean 'reg-id'?
3. Missing 'outbound' tag in the Supported header in all examples according
to the Outbound draft.
4. It seems the GRUU parameter in the INVITE example on page 19 does not
match the latest GRUU draft (version 14). Specifically, I don't see the
'grid=' tag in the latest GRUU draft. One suggestion is to add the 200 OK
response example with GRUU tags in section 4.1.2 (page 17), so that the
reader know how the GRUU tag is copied to the INVITE requests.

Technical problem:
In section 4.1.4, I think the INVITE from Proxy to the Client behind the NAT
is missing the Record-Route header. Without the RR header, the re-Invite or
any other request from the client (Callee behind the NAT) will go directly
to the caller's 'Contact' header, not the Proxy.

Regards,
Jerry

> -----Original Message-----
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org]On
> Behalf Of Mary Barnes
> Sent: Saturday, May 03, 2008 12:17 PM
> To: sipping@ietf.org
> Cc: behave@ietf.org; Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
> Subject: [Sipping] WGLC Review: draft-ietf-sipping-nat-scenarios-08
>
>
> Sorry folks - obviously I had the wrong title in the original
> announcement
>
> -----Original Message-----
> From: Barnes, Mary (RICH2:AR00)
> Sent: Friday, May 02, 2008 5:45 PM
> To: 'sipping@ietf.org'
> Cc: 'Chris Boulton'; 'Gonzalo.Camarillo@ericsson.com';
> 'jdrosen@cisco.com'; 'behave@ietf.org'; 'mmusic@ietf.org'
> Subject: RE: WG Review: draft-ietf-sipping-nat-scenarios-07
>
> Hi folks,
>
> This is to announce a Working Group Last Call on the following document
> to be published a Best Current Practice (BCP):
> http://www.ietf.org/internet-drafts/draft-ietf-sipping-nat-scenarios-08.
> txt
>
> The review period will end on 23 May 2008 (3 weeks time).
>
> Note that I have cross-posted to the BEHAVE and MMUSIC WGs, but ask that
> you please send your comments only to the SIPPING WG and author(s).
>
> The following reviewers have already volunteered:  Vijay Gurbani,
> Spencer Dawkins, Francois Audet, and Dan Wing  (thanks guys!)
>
> However, we do encourage others to review and make any final comments on
> the document at this time.
>
> Thanks,
> Mary
> SIPPING WG co-chair
>
> As a reminder, the SIPPING WG review guidelines are available at:
> https://softarmor.com/sipping/process/wg-review/sipping-review-guideline
> s.html
>
> _______________________________________________
> Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May  5 13:45:43 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DC68C3A6C38;
	Mon,  5 May 2008 13:45:43 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 17EF43A6C38
	for <behave@core3.amsl.com>; Mon,  5 May 2008 13:45:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.941
X-Spam-Level: 
X-Spam-Status: No, score=-1.941 tagged_above=-999 required=5 tests=[AWL=0.659, 
	BAYES_00=-2.599]
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 yINS-I1udcNs for <behave@core3.amsl.com>;
	Mon,  5 May 2008 13:45:42 -0700 (PDT)
Received: from mail-02.primus.ca (mail3.primus.ca [216.254.141.170])
	by core3.amsl.com (Postfix) with ESMTP id 504413A67D2
	for <behave@ietf.org>; Mon,  5 May 2008 13:45:42 -0700 (PDT)
Received: from [216.13.42.68] (helo=[10.10.80.124])
	by mail-02.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1Jt7Z6-0000Fy-2J; Mon, 05 May 2008 16:45:40 -0400
Message-Id: <65A49A0F-808D-472F-8C22-B0A5D86D402E@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Simon Perreault <simon.perreault@viagenie.ca>
In-Reply-To: <200805051333.03912.simon.perreault@viagenie.ca>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 5 May 2008 16:45:41 -0400
References: <47F3FA30.2060403@acm.org>
	<200805050923.50429.remi.denis-courmont@nokia.com>
	<E1324FFA-4E2F-40DA-A14B-96D84AA273D3@magma.ca>
	<200805051333.03912.simon.perreault@viagenie.ca>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.10.80.124]) [216.13.42.68]
Cc: behave@ietf.org
Subject: Re: [BEHAVE] IPv4/IPv6 relayed address allocation
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Mon, 5-May-08, at 13:33 , Simon Perreault wrote:
> On Monday 05 May 2008 12:30:59 Philip Matthews wrote:
>> TURN-08 will NOT specify IPv4 to IPv6
>> relaying (because the details for doing this are non-trivial).
>
> What details do you have in mind?

v4 to v6 relaying adds details to how relaying of IP header fields and  
ICMP messages are done. This is a feature coming in TURN-08 (as  
discussed in the last BEHAVE meeting in Philly). Moreover, the WG has  
already chartered draft-ietf-behave-turn-ipv6 for this, and I am  
really trying to finish the base TURN, not add new features.

- Philip
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May  5 13:50:15 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 129E428C309;
	Mon,  5 May 2008 13:50:15 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 140EB28C309
	for <behave@core3.amsl.com>; Mon,  5 May 2008 13:50:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level: 
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[AWL=0.494, 
	BAYES_00=-2.599]
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 UMzezIFpEqnN for <behave@core3.amsl.com>;
	Mon,  5 May 2008 13:50:12 -0700 (PDT)
Received: from mail-02.primus.ca (mail3.primus.ca [216.254.141.170])
	by core3.amsl.com (Postfix) with ESMTP id 65C3328C2B9
	for <behave@ietf.org>; Mon,  5 May 2008 13:50:12 -0700 (PDT)
Received: from [216.13.42.68] (helo=[10.10.80.124])
	by mail-02.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>) id 1Jt7dT-0003JK-0F
	for behave@ietf.org; Mon, 05 May 2008 16:50:11 -0400
Message-Id: <58DB1008-D64F-408E-9F31-BAA4E8CDC500@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Behave WG <behave@ietf.org>
In-Reply-To: <0c6401c8ac6c$8fc0c5c0$c3f0200a@cisco.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 5 May 2008 16:50:12 -0400
References: <4810C3ED.7030901@ericsson.com>
	<200805021506.12807.remi.denis-courmont@nokia.com>
	<0c6401c8ac6c$8fc0c5c0$c3f0200a@cisco.com>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.10.80.124]) [216.13.42.68]
Subject: Re: [BEHAVE] Consensus call on Adding "Client" attribute to STUN
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I have no problem with adding this attribute.
- Philip

On Fri, 2-May-08, at 11:52 , Dan Wing wrote:
> As chair: fine by me.  I was hoping more people would comment for/ =

> against
> Magnus's consensus call.
>
> As an individual and co-author of rfc3489bis:  I support adding the  =

> new CLIENT
> attribute.
>
> -d
>
>
>> -----Original Message-----
>> From: R=E9mi Denis-Courmont [mailto:remi.denis-courmont@nokia.com]
>> Sent: Friday, May 02, 2008 5:06 AM
>> To: Dan Wing
>> Cc: behave@ietf.org
>> Subject: Re: [BEHAVE] Consensus call on Adding "Client"
>> attribute to STUN
>>
>>
>> 	Dan,
>>
>> I think I'll wait for the conclusion of this before I update
>> the test vectors.
>> I can see it coming that people will ask for a CLIENT attribute  =

>> there.
>>
>> Is that OK?
>>
>> Le Thursday 24 April 2008 20:31:25 ext Magnus Westerlund,
>> vous avez =E9crit :
>>> This is a one week+ consensus call (until the 5th of May) if the WG
>>> thinks that STUN (draft-ietf-behave-rfc3489bis) shall be
>> extended with
>>> an additional attribute "Client" before publication.
>>>
>>> With the general description along the lines of:
>>>
>>>    X.Y CLIENT
>>>
>>>    The client attribute contains a textual description of
>> the software
>>>    being used by the client, including manufacturer and
>> version number.
>>>    The attribute has no impact on operation of the
>> protocol, and serves
>>>    only as a tool for diagnostic and debugging purposes.
>> The value of
>>>    CLIENT is variable length.  It MUST be a UTF-8 [RFC3629] encoded
>>>    sequence of less than 128 characters (which can be as
>> long as 763
>>>    bytes).
>>>
>>> And some Security Considerations on the risk for targeted attacks
>>> against clients with this information. Plus other text
>> needed to bring
>>> it in consistently
>>>
>>> The text is open for wordsmithing by the editors of the STUN spec.
>>>
>>> Please indicate your position on adding this or not.
>>>
>>> Cheers
>>>
>>> Magnus Westerlund
>>>
>>> IETF Transport Area Director & TSVWG Chair
>>>
>> ----------------------------------------------------------------------
>>> Multimedia Technologies, Ericsson Research EAB/TVM
>>>
>> ----------------------------------------------------------------------
>>> Ericsson AB                | Phone +46 8 4048287
>>> F=E4r=F6gatan 6                | Fax   +46 8 7575550
>>> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>>>
>> ----------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Behave mailing list
>>> Behave@ietf.org
>>> https://www.ietf.org/mailman/listinfo/behave
>>
>>
>>
>> -- =

>> R=E9mi Denis-Courmont
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May  5 18:20:24 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9746028C394;
	Mon,  5 May 2008 18:20:24 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6E50528C386
	for <behave@core3.amsl.com>; Mon,  5 May 2008 18:20:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 jzrf0jwlok6V for <behave@core3.amsl.com>;
	Mon,  5 May 2008 18:20:21 -0700 (PDT)
Received: from mail-06.primus.ca (mail3.primus.ca [216.254.141.170])
	by core3.amsl.com (Postfix) with ESMTP id 8413128C394
	for <behave@ietf.org>; Mon,  5 May 2008 18:20:21 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-06.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1JtBqr-0005ng-2f; Mon, 05 May 2008 21:20:18 -0400
Message-Id: <9F366B86-DEDB-4BD1-8D68-F614AB910FD8@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <481F7AEC.7030209@gmail.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 5 May 2008 21:20:17 -0400
References: <47F3FA30.2060403@acm.org>	<200805021504.26754.remi.denis-courmont@nokia.com>	<C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>
	<200805050923.50429.remi.denis-courmont@nokia.com>
	<481EFE86.3060808@free.fr>
	<9925D171-E6BA-4490-B9A8-D44419CA221D@magma.ca>
	<481F7AEC.7030209@gmail.com>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Cc: v6ops <v6ops@ops.ietf.org>, behave@ietf.org
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Mon, 5-May-08, at 17:23 , Brian E Carpenter wrote:
> On 2008-05-06 01:21, Philip Matthews wrote:
>>
>> On Mon, 5-May-08, at 08:33 , R=E9mi Despr=E9s wrote:
>>> R=E9mi Denis-Courmont a =E9crit :
>>>> Le Friday 02 May 2008 22:16:02 ext Philip Matthews, vous avez  =

>>>> =E9crit :
>>>
>>>>> TURN-08 will say that a server should copy the flow label, and  =

>>>>> if this
>>>>> cannot be done, then treat the packets to/from each peer as a  =

>>>>> separate
>>>>> flow with separate labels. This is all part of the new concept  =

>>>>> of a
>>>>> Preserving allocation (what I called a "Fully-Compliant  =

>>>>> allocation" in
>>>>> Philly) that I am in the process of adding right now.
>>>> I myself am not sure what the "proper" handling of the flow infos  =

>>>> is.
>>>> If anyone knows, that would be some 6man and/or v6ops people (not
>>>> including me). Flow infos is not just like DSCP. Reflecting this,  =

>>>> the
>>>> Linux(-specific) API for flow infos is completely different from  =

>>>> that
>>>> of DSCP and TTL...
>>>
>>> Pending any approved use of flow labels, there is IMU only one
>>> consistent behavior, everywhere: the flow label field MUST be  =

>>> ignored
>>> when received, and MUST be set to 0 when created .
>>>
>>> If and when some use is approved, it will be time to decide whether,
>>> in TURN in particular, another behavior is more appropriate.
>>
>>
>> What about RFC 3697 ??
>> Are you saying that this does not describe approved behavior?
>
> It does, of course. So the rule is really only that the flow label
> must be delivered *exactly* as it was set by the source host (and the
> default setting is zero).  TURN has to obey that rule like any other
> device that forwards packets.
>

For the folks in V6OPS, let me describe the situation more precisely.  =

A TURN server receives packets from a TURN client and relays them  =

toward a TURN peer. In the process, the server changes both the source  =

and destination address. Packets can also flow in the reverse direction.

For the IPv6 flow label, the best solution as far as I can see, is to  =

copy the flow label from the incoming packet to the outgoing packet.  =

This seems the right thing to do, even though the source and  =

destination addresses change. Since the addresses change, it is  =

possible that two logically distinct flows that originally had  =

distinct 3-tuples (source IP, dest IP, flow label) before reaching the  =

server get assigned the same 3-tuple after relaying. However, as far  =

as I can see, having the same 3-tuple does not means the packets ARE  =

part of the same flow, but just that they MAY be part of the same flow.

Copying the flow label and other fields in the IP header requires  =

special privileges on most modern OSes (e.g. RAW sockets or kernel  =

access). So TURN also allows a mode where fields in the IP header are  =

not copied, but are set as best as possible using unprivileged user- =

land APIs. I am not sure what the situation is for the flow label, but  =

for many other IP header fields, it is easy to set these fields on  =

outgoing packets, but impossible to read them on incoming packets. So  =

a somewhat less desirable but acceptable solution when relaying the  =

flow label, as I can see, is to assume all the packets coming from a  =

given client and going to a given peer constitute a distinct flow and  =

thus assign them a unique flow label after relaying the packets. And  =

similarly in the opposite direction.

Comments?

- Philip

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May  5 19:17:55 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C93B33A69F9;
	Mon,  5 May 2008 19:17:55 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A25B23A68E0
	for <behave@core3.amsl.com>; Mon,  5 May 2008 19:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 i6UeeliT-wff for <behave@core3.amsl.com>;
	Mon,  5 May 2008 19:17:53 -0700 (PDT)
Received: from mail-05.primus.ca (mail3.primus.ca [216.254.141.170])
	by core3.amsl.com (Postfix) with ESMTP id 832F13A69F9
	for <behave@ietf.org>; Mon,  5 May 2008 19:17:50 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-05.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1JtCjD-0004uj-2P; Mon, 05 May 2008 22:16:32 -0400
Message-Id: <AF472E83-5E94-4F4A-ABDA-6C3E39A7842E@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <9F366B86-DEDB-4BD1-8D68-F614AB910FD8@magma.ca>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 5 May 2008 22:17:37 -0400
References: <47F3FA30.2060403@acm.org>	<200805021504.26754.remi.denis-courmont@nokia.com>	<C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>
	<200805050923.50429.remi.denis-courmont@nokia.com>
	<481EFE86.3060808@free.fr>
	<9925D171-E6BA-4490-B9A8-D44419CA221D@magma.ca>
	<481F7AEC.7030209@gmail.com>
	<9F366B86-DEDB-4BD1-8D68-F614AB910FD8@magma.ca>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Cc: v6ops <v6ops@ops.ietf.org>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Resending message as I got a delivery error ...


On Mon, 5-May-08, at 17:23 , Brian E Carpenter wrote:
> On 2008-05-06 01:21, Philip Matthews wrote:
>>
>> On Mon, 5-May-08, at 08:33 , R=E9mi Despr=E9s wrote:
>>> R=E9mi Denis-Courmont a =E9crit :
>>>> Le Friday 02 May 2008 22:16:02 ext Philip Matthews, vous avez  =

>>>> =E9crit :
>>>
>>>>> TURN-08 will say that a server should copy the flow label, and  =

>>>>> if this
>>>>> cannot be done, then treat the packets to/from each peer as a  =

>>>>> separate
>>>>> flow with separate labels. This is all part of the new concept  =

>>>>> of a
>>>>> Preserving allocation (what I called a "Fully-Compliant  =

>>>>> allocation" in
>>>>> Philly) that I am in the process of adding right now.
>>>> I myself am not sure what the "proper" handling of the flow infos  =

>>>> is.
>>>> If anyone knows, that would be some 6man and/or v6ops people (not
>>>> including me). Flow infos is not just like DSCP. Reflecting this,  =

>>>> the
>>>> Linux(-specific) API for flow infos is completely different from  =

>>>> that
>>>> of DSCP and TTL...
>>>
>>> Pending any approved use of flow labels, there is IMU only one
>>> consistent behavior, everywhere: the flow label field MUST be  =

>>> ignored
>>> when received, and MUST be set to 0 when created .
>>>
>>> If and when some use is approved, it will be time to decide whether,
>>> in TURN in particular, another behavior is more appropriate.
>>
>>
>> What about RFC 3697 ??
>> Are you saying that this does not describe approved behavior?
>
> It does, of course. So the rule is really only that the flow label
> must be delivered *exactly* as it was set by the source host (and the
> default setting is zero).  TURN has to obey that rule like any other
> device that forwards packets.
>

For the folks in V6OPS, let me describe the situation more precisely.  =

A TURN server receives packets from a TURN client and relays them  =

toward a TURN peer. In the process, the server changes both the source  =

and destination address. Packets can also flow in the reverse direction.

For the IPv6 flow label, the best solution as far as I can see, is to  =

copy the flow label from the incoming packet to the outgoing packet.  =

This seems the right thing to do, even though the source and  =

destination addresses change. Since the addresses change, it is  =

possible that two logically distinct flows that originally had  =

distinct 3-tuples (source IP, dest IP, flow label) before reaching the  =

server get assigned the same 3-tuple after relaying. However, as far  =

as I can see, having the same 3-tuple does not means the packets ARE  =

part of the same flow, but just that they MAY be part of the same flow.

Copying the flow label and other fields in the IP header requires  =

special privileges on most modern OSes (e.g. RAW sockets or kernel  =

access). So TURN also allows a mode where fields in the IP header are  =

not copied, but are set as best as possible using unprivileged user- =

land APIs. I am not sure what the situation is for the flow label, but  =

for many other IP header fields, it is easy to set these fields on  =

outgoing packets, but impossible to read them on incoming packets. So  =

a somewhat less desirable but acceptable solution when relaying the  =

flow label, as I can see, is to assume all the packets coming from a  =

given client and going to a given peer constitute a distinct flow and  =

thus assign them a unique flow label after relaying the packets. And  =

similarly in the opposite direction.

Comments?

- Philip


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May  5 21:28:19 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 987D53A6F1D;
	Mon,  5 May 2008 21:28:18 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F214E3A69D3
	for <behave@core3.amsl.com>; Mon,  5 May 2008 21:28:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 ltAjTnYVVF1c for <behave@core3.amsl.com>;
	Mon,  5 May 2008 21:28:10 -0700 (PDT)
Received: from smtp-1.servers.netregistry.net (smtp.netregistry.net
	[202.124.241.204])
	by core3.amsl.com (Postfix) with ESMTP id 22CE53A6F88
	for <behave@ietf.org>; Mon,  5 May 2008 21:28:00 -0700 (PDT)
Received: from [211.27.108.142] (helo=[10.0.0.10])
	by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.63 #1
	(Debian)) id 1JtEmB-0006Nx-GQ; Tue, 06 May 2008 14:27:40 +1000
User-Agent: Microsoft-Entourage/12.1.0.080305
Date: Tue, 06 May 2008 14:27:30 +1000
From: Hesham Soliman <hesham@elevatemobile.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>,
	Philip Matthews <philip_matthews@magma.ca>
Message-ID: <C4461B52.6CEB%hesham@elevatemobile.com>
Thread-Topic: IPv6 Flow Label
Thread-Index: AcivMX8O3GkPE3FR4ECV0rJM/CqwRg==
In-Reply-To: <481FCE95.50006@gmail.com>
Mime-version: 1.0
Cc: v6ops <v6ops@ops.ietf.org>, behave@ietf.org
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


>> For the folks in V6OPS, let me describe the situation more precisely. A
>> TURN server receives packets from a TURN client and relays them toward a
>> TURN peer. In the process, the server changes both the source and
>> destination address. Packets can also flow in the reverse direction.
>> 
>> For the IPv6 flow label, the best solution as far as I can see, is to
>> copy the flow label from the incoming packet to the outgoing packet.
>> This seems the right thing to do, even though the source and destination
>> addresses change. Since the addresses change, it is possible that two
>> logically distinct flows that originally had distinct 3-tuples (source
>> IP, dest IP, flow label) before reaching the server get assigned the
>> same 3-tuple after relaying. However, as far as I can see, having the
>> same 3-tuple does not means the packets ARE part of the same flow, but
>> just that they MAY be part of the same flow.
>> 
>> Copying the flow label and other fields in the IP header requires
>> special privileges on most modern OSes (e.g. RAW sockets or kernel
>> access). So TURN also allows a mode where fields in the IP header are
>> not copied, but are set as best as possible using unprivileged user-land
>> APIs. I am not sure what the situation is for the flow label, but for
>> many other IP header fields, it is easy to set these fields on outgoing
>> packets, but impossible to read them on incoming packets. So a somewhat
>> less desirable but acceptable solution when relaying the flow label, as
>> I can see, is to assume all the packets coming from a given client and
>> going to a given peer constitute a distinct flow and thus assign them a
>> unique flow label after relaying the packets. And similarly in the
>> opposite direction.
>> 
>> Comments?
> 
> My comment is that there's never a valid reason to rewrite IPv6 addresses
> on the fly, so I don't see why the problem arises. I don't understand
> the context in which TURN would face this problem, therefore. If you
> terminate one IPv6 packet flow and originate another one carrying the
> same application data, that makes two independent flows and they should
> have independent flow labels.

=> I completely agree. Philip, it might help if you explain why this need
arises for IPv6. What is the scenario?

Hesham

> 
>    Brian
> 
> 


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May  5 21:38:44 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6D76C3A6A50;
	Mon,  5 May 2008 21:38:44 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B25FC3A6A50
	for <behave@core3.amsl.com>; Mon,  5 May 2008 21:38:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.911
X-Spam-Level: 
X-Spam-Status: No, score=-0.911 tagged_above=-999 required=5
	tests=[AWL=-0.008, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	MIME_QP_LONG_LINE=1.396]
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 mDVQiLU0GjDo for <behave@core3.amsl.com>;
	Mon,  5 May 2008 21:38:42 -0700 (PDT)
Received: from smtp-1.servers.netregistry.net (smtp.netregistry.net
	[202.124.241.204])
	by core3.amsl.com (Postfix) with ESMTP id BE3243A69C4
	for <behave@ietf.org>; Mon,  5 May 2008 21:38:42 -0700 (PDT)
Received: from [211.27.108.142] (helo=[10.0.0.10])
	by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.63 #1
	(Debian)) id 1JtEwl-0006l4-78; Tue, 06 May 2008 14:38:35 +1000
User-Agent: Microsoft-Entourage/12.1.0.080305
Date: Tue, 06 May 2008 14:38:30 +1000
From: Hesham Soliman <hesham@elevatemobile.com>
To: =?ISO-8859-1?B?UultaQ==?= =?ISO-8859-1?B?IERlc3By6XM=?=
	<remi.despres@free.fr>, Philip Matthews <philip_matthews@magma.ca>
Message-ID: <C4461DE6.6CEE%hesham@elevatemobile.com>
Thread-Topic: [BEHAVE] IPv6 Flow Label
Thread-Index: AcivMwhyo2PzCuoq2US7ePqpwpdJkQ==
In-Reply-To: <481F2299.5020305@free.fr>
Mime-version: 1.0
Cc: behave@ietf.org
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

>> What about RFC 3697 ??
>> Are you saying that this does not describe approved behavior?
> =

> I certainely should not say it this way.
> But it is till unclear to me whether there is a real USE of it?
> =

> If there is one (with running code etc...), my comment is just inadequate.
> =

> =

> Taking this opportunity, here is a proposal:
> =

> - Limit the RFC3697 use of flow labels (FLs) to a subset of all their
> possible values.
> - The goal is that other future uses are not precluded (or at least are
> not made significantly more difficult).
> - For example, have the first bit set to 1, or the first 4 bits set to
> 1111, or the first octet different from OxFF.

=3D> Something very similar to what you propose was discussed when the IPv6=
 WG
was producing RFC 3697 and the concensus was not to do that.
The use of the flow label was discussed for many years in the IPv6 WG so I
don't think it would be easy to change this now. In any case, these
proposals are best discussed in 6man.

Hesham

> =

> Regards.
> =

> R=E9mi
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 00:31:51 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E905C3A690B;
	Tue,  6 May 2008 00:31:51 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 433A73A690B
	for <behave@core3.amsl.com>; Tue,  6 May 2008 00:31:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.49
X-Spam-Level: 
X-Spam-Status: No, score=-1.49 tagged_above=-999 required=5 tests=[AWL=0.459, 
	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 pn2JsMDJY8JN for <behave@core3.amsl.com>;
	Tue,  6 May 2008 00:31:49 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id 727E73A684B
	for <behave@ietf.org>; Tue,  6 May 2008 00:31:49 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 4918B3EA0D6;
	Tue,  6 May 2008 09:31:47 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 056823EA0D0;
	Tue,  6 May 2008 09:31:46 +0200 (CEST)
Message-ID: <48200968.9030607@free.fr>
Date: Tue, 06 May 2008 09:31:52 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Hesham Soliman <hesham@elevatemobile.com>
References: <C4461DE6.6CEE%hesham@elevatemobile.com>
In-Reply-To: <C4461DE6.6CEE%hesham@elevatemobile.com>
Cc: behave@ietf.org
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hesham Soliman a =E9crit :
>>> What about RFC 3697 ??
>>> Are you saying that this does not describe approved behavior?
>> I certainely should not say it this way.
>> But it is till unclear to me whether there is a real USE of it?
>>
>> If there is one (with running code etc...), my comment is just inadequat=
e.
>>
>>
>> Taking this opportunity, here is a proposal:
>>
>> - Limit the RFC3697 use of flow labels (FLs) to a subset of all their
>> possible values.
>> - The goal is that other future uses are not precluded (or at least are
>> not made significantly more difficult).
>> - For example, have the first bit set to 1, or the first 4 bits set to
>> 1111, or the first octet different from OxFF.
> =

> =3D> Something very similar to what you propose was discussed when the IP=
v6 WG
> was producing RFC 3697 and the concensus was not to do that.
Unfortunate IMHO.
> The use of the flow label was discussed for many years in the IPv6 WG so I
> don't think it would be easy to change this now.
Agreed, at least as long as no really useful use of flow lebels is =

identified.
> In any case, these
> proposals are best discussed in 6man.
Right.

R=E9mi
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 01:38:21 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3C3F63A6827;
	Tue,  6 May 2008 01:38:21 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5BB293A6827
	for <behave@core3.amsl.com>; Tue,  6 May 2008 01:38:19 -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 QDPFaTxdHtGg for <behave@core3.amsl.com>;
	Tue,  6 May 2008 01:38:18 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id 873963A6822
	for <behave@ietf.org>; Tue,  6 May 2008 01:38:18 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id BFC2C3EA0CA;
	Tue,  6 May 2008 10:38:16 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id A2DF83EA0FE;
	Tue,  6 May 2008 10:38:15 +0200 (CEST)
Message-ID: <482018FD.2060208@free.fr>
Date: Tue, 06 May 2008 10:38:21 +0200
From: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <47F3FA30.2060403@acm.org>	<200805021504.26754.remi.denis-courmont@nokia.com>	<C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>
	<200805050923.50429.remi.denis-courmont@nokia.com>
	<481EFE86.3060808@free.fr>
	<9925D171-E6BA-4490-B9A8-D44419CA221D@magma.ca>
	<481F7AEC.7030209@gmail.com>
In-Reply-To: <481F7AEC.7030209@gmail.com>
Cc: v6ops <v6ops@ops.ietf.org>, behave@ietf.org
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

QnJpYW4gRSBDYXJwZW50ZXIgd3JvdGUgOgoKPiBTbyB0aGUgcnVsZSBpcyByZWFsbHkgb25seSB0
aGF0IHRoZSBmbG93IGxhYmVsCj4gbXVzdCBiZSBkZWxpdmVyZWQgKmV4YWN0bHkqIGFzIGl0IHdh
cyBzZXQgYnkgdGhlIHNvdXJjZSBob3N0IChhbmQgdGhlCj4gZGVmYXVsdCBzZXR0aW5nIGlzIHpl
cm8pLgpSaWdodC4KSG93ZXZlciwgYmV0d2VlbiBzb3VyY2UgYW5kIGRlc3RpbmF0aW9uIGhvc3Rz
ICpvZiBJUHY2IHBhY2tldHMqLgpPbiBhbiBBLVRVUk4tQiBwYXRoLCB0aGUgKmRlc3RpbmF0aW9u
IGhvc3QqIG9mIGEgcGFja2V0IGZyb20gQSBpcyBUVVJOIAoobm90IEIpLgoKPiBUVVJOIGhhcyB0
byBvYmV5IHRoYXQgcnVsZSBsaWtlIGFueSBvdGhlcgo+IGRldmljZSB0aGF0IGZvcndhcmRzIHBh
Y2tldHMuClRVUk4gaXMgaW4gdGhpcyByZXNwZWN0IGxpa2UgYW55IG90aGVyIGZ1bmN0aW9uIHRo
YXQgb3BlcmF0ZXMgd2l0aCAKZGlmZmVyZW50IDUtdHVwbGVzIG9uIGl0cyB1cHN0cmVhbSBhbmQg
ZG9ud3N0cmVhbSBpbnRlcmZhY2VzIChhYm92ZSB0aGUgCklQIGxheWVyKS4KCgpGb2xsb3dpbmcg
dGhlIGRpc2N1c2lvbiwgdGhpcyBpcyBJTUhPIHRoZSByaWdodCBsb2dpYzoKClRVUk4gbm9kZXMg
bWF5IGZyZWVseSBzdXBwb3J0IG9yIG5vdCBzdXBwb3J0IFJGQyAzNjk3IGZsb3cgbGFiZWxzLCBh
cyAKc291cmNlcyBvbiB0aGVpciBvdXRnb2luZyBpbnRlcmZhY2VzLC4KSW5kZXBlbmRlbnRseSwg
dGhleSBtYXkgZnJlZWx5IGlnbm9yZSByZWNlaXZlZCBmbG93IGxhYmVscywgb3IgcHJvY2VzcyAK
dGhlbSB0byBvcHRpbWl6ZSB0aGVpciB0cmFuc3BvcnQgZmxvdyByZWNvZ25pdGlvbiwgb24gdGhp
ciBpbmNvbWluZyAKaW50ZXJmYWNlcy4KCklmIFJGQyAzNjk3IGZsb3cgbGFiZWxzIGFyZSBpbXBs
ZW1lbnRlZCBieSB0aGUgdHdvIGVuZCBub2RlcyBhbmQgYnkgYW4gCmludGVybWVkaWF0ZSBUVVJO
IG5vZGUsIHRoZW4gcGFja2V0IGNsYXNzaWZpY2F0aW9uIGNhbiB0YWtlIGFkdmFudGFnZSBvZiAK
ZmxvdyBsYWJlbHMgaW4gYWxsIHRyYXZlcnNlZCByb3V0ZXJzLCBiZSBpdCB3aXRoIGNoYW5nZWQg
ZmxvdyBsYWJlbCAKdmFsdWVzIGFjcm9zcyB0aGUgVFVSTiBub2RlLgoKClLDqW1pCgoKCl9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCkJlaGF2ZSBtYWlsaW5n
IGxpc3QKQmVoYXZlQGlldGYub3JnCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGlu
Zm8vYmVoYXZlCg==


From behave-bounces@ietf.org  Tue May  6 02:14:28 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E12513A68C5;
	Tue,  6 May 2008 02:14:28 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C355C3A68C5
	for <behave@core3.amsl.com>; Tue,  6 May 2008 02:14:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, 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 ggMbTrRGGVm3 for <behave@core3.amsl.com>;
	Tue,  6 May 2008 02:14:27 -0700 (PDT)
Received: from smtp-1.servers.netregistry.net (smtp.netregistry.net
	[202.124.241.204])
	by core3.amsl.com (Postfix) with ESMTP id E8B1F3A6827
	for <behave@ietf.org>; Tue,  6 May 2008 02:14:26 -0700 (PDT)
Received: from [124.190.105.201] (helo=[192.168.0.187])
	by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.63 #1
	(Debian)) id 1JtJFZ-0004ra-5t; Tue, 06 May 2008 19:14:17 +1000
User-Agent: Microsoft-Entourage/12.1.0.080305
Date: Tue, 06 May 2008 19:14:05 +1000
From: Hesham Soliman <hesham@elevatemobile.com>
To: =?ISO-8859-1?B?UultaQ==?= =?ISO-8859-1?B?IERlc3By6XM=?=
	<remi.despres@free.fr>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <C4465E7D.6CFD%hesham@elevatemobile.com>
Thread-Topic: [BEHAVE] IPv6 Flow Label
Thread-Index: AcivWYgTpLnz9sbVS0GP0qF8xqUh6w==
In-Reply-To: <482018FD.2060208@free.fr>
Mime-version: 1.0
Cc: v6ops <v6ops@ops.ietf.org>, behave@ietf.org
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org




On 6/05/08 6:38 PM, "R=E9mi Despr=E9s" <remi.despres@free.fr> wrote:

> Brian E Carpenter wrote :


> So the rule is really only that the flow label
>
> must be delivered *exactly* as it was set by the source host (and the
>
> default setting is zero).
Right.
However, between source and destination hosts
> *of IPv6 packets*.
On an A-TURN-B path, the *destination host* of a packet
> from A is TURN =

(not B).

> TURN has to obey that rule like any other
> device
> that forwards packets.
TURN is in this respect like any other function that
> operates with =

different 5-tuples on its upstream and donwstream interfaces
> (above the =

IP layer).




  Following the discusion, this is IMHO the right
> logic:

TURN nodes may freely support or not support RFC 3697 flow labels, as
> =

sources on their outgoing interfaces,.
Independently, they may freely ignore
> received flow labels, or process =

them to optimize their transport flow
> recognition, on thir incoming =

interfaces.

If RFC 3697 flow labels are
> implemented by the two end nodes and by an =

intermediate TURN node, then
> packet classification can take advantage of =

flow labels in all traversed
> routers, be it with changed flow label =

values across the TURN
> node.




=3D> I don't understand two points:
- Why is the IPv6 address/header being re-written?
- If there is a good answer for the above question then why would you ignore
the flow label and not copy it across?

It is one thing to terminate the connection and restart it with the remote
node, but I don't see any reason for re-writing a header _and_ ignoring the
original content of that header.

Hesham



R=E9mi



_______________________________________________
Behave mailing
> list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave



_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 03:06:47 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 22F8128C21C;
	Tue,  6 May 2008 03:06:47 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D561F3A6A32;
	Tue,  6 May 2008 03:06:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level: 
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
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 HfPX6kTlOBNw; Tue,  6 May 2008 03:06:42 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id BDD783A69B3;
	Tue,  6 May 2008 03:06:42 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	81262214F6; Tue,  6 May 2008 12:06:39 +0200 (CEST)
X-AuditID: c1b4fb3e-ac995bb000004ec0-ae-48202daf4b73
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	707EA214A1; Tue,  6 May 2008 12:06:39 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 May 2008 12:06:39 +0200
Received: from [131.160.37.21] ([131.160.37.21]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 May 2008 12:06:38 +0200
Message-ID: <48202DAA.8000408@ericsson.com>
Date: Tue, 06 May 2008 13:06:34 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?=
 <remi.denis-courmont@nokia.com>
References: <F66D7286825402429571678A16C2F5EE03441FA1@zrc2hxm1.corp.nortel.com>
	<200805051039.35818.remi.denis-courmont@nokia.com>
In-Reply-To: <200805051039.35818.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 06 May 2008 10:06:38.0598 (UTC)
	FILETIME=[DFC48A60:01C8AF60]
X-Brightmail-Tracker: AAAAAA==
Cc: sipping@ietf.org, Chris Boulton <cboulton@avaya.com>, behave@ietf.org,
	mmusic@ietf.org
Subject: Re: [BEHAVE] WGLC  Review: draft-ietf-sipping-nat-scenarios-08
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi,

> Section 5.2 refers to ANAT for v6 media transition. I thought it was being 
> deprecated by ICE, so I am a bit confused.

yes, we have to remove the ANAT part. We will edit the draft so that it 
only refers  to ICE in that part.

Thanks,

Gonzalo
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 05:38:33 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8F2F428C1B9;
	Tue,  6 May 2008 05:38:33 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 233183A6CD7
	for <behave@core3.amsl.com>; Tue,  6 May 2008 05:38:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.591
X-Spam-Level: 
X-Spam-Status: No, score=-1.591 tagged_above=-999 required=5 tests=[AWL=0.359, 
	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 IPCDhGNWq9Kj for <behave@core3.amsl.com>;
	Tue,  6 May 2008 05:38:27 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id 3087D3A6EB9
	for <behave@ietf.org>; Tue,  6 May 2008 05:38:08 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id B006C3EA10C;
	Tue,  6 May 2008 14:38:05 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 741E83EA0F6;
	Tue,  6 May 2008 14:37:50 +0200 (CEST)
Message-ID: <4820511F.3060100@free.fr>
Date: Tue, 06 May 2008 14:37:51 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Hesham Soliman <hesham@elevatemobile.com>
References: <C4465E7D.6CFD%hesham@elevatemobile.com>
In-Reply-To: <C4465E7D.6CFD%hesham@elevatemobile.com>
Cc: v6ops <v6ops@ops.ietf.org>, behave@ietf.org,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hesham Soliman wrote :

> On 6/05/08 6:38 PM, "R=E9mi Despr=E9s" <remi.despres@free.fr> wrote:

>> Following the discusion, this is IMHO the right logic:
>> =

>> TURN nodes may freely support or not support RFC 3697 flow labels, as
>>  sources on their outgoing interfaces,. Independently, they may
>> freely ignore received flow labels, or process them to optimize their
>> transport flow recognition, on thir incoming interfaces.

> =3D> I don't understand two points: - Why is the IPv6 address/header
> being re-written? - If there is a good answer for the above question
> then why would you ignore the flow label and not copy it across?

The destination address of a packet received by a TURN relay is the =

address of the relay. That of the packet it forwards, with the same data =

  field, is the address of the next IP layer destination node (the =

destination host or an itermediate NAT).

RFC 3697 has a rule that non zero flow labels that leave a node MUST be =

all different for current flows having the same source-destination pair.

If flow labels received by a TURN relay from two different sources =

happen to be the same while the next IP destination happens to be the =

same NAT, copying flow labels will infringe the rule.

Therefore, IMU, flow labels *MUST NOT* be copied from upstream flows to =

downstream flows.



R=E9mi


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 05:46:47 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8FD0A3A6E1C;
	Tue,  6 May 2008 05:46:47 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E4D3D3A6BDB
	for <behave@core3.amsl.com>; Tue,  6 May 2008 05:46:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level: 
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[AWL=0.095, 
	BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 Z+R6uxjPfpHm for <behave@core3.amsl.com>;
	Tue,  6 May 2008 05:46:45 -0700 (PDT)
Received: from mail-02.primus.ca (mail3.primus.ca [216.254.141.170])
	by core3.amsl.com (Postfix) with ESMTP id DE5A43A6E1C
	for <behave@ietf.org>; Tue,  6 May 2008 05:46:44 -0700 (PDT)
Received: from [216.13.42.68] (helo=[10.10.80.124])
	by mail-02.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1JtMZ4-0001Cg-1V; Tue, 06 May 2008 08:46:38 -0400
Message-Id: <B7A6E4DD-CBAA-4D2A-80CF-92B81216E245@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Hesham Soliman <hesham@elevatemobile.com>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <C4461B52.6CEB%hesham@elevatemobile.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 6 May 2008 08:46:36 -0400
References: <C4461B52.6CEB%hesham@elevatemobile.com>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.10.80.124]) [216.13.42.68]
Cc: v6ops <v6ops@ops.ietf.org>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Tue, 6-May-08, at 00:27 , Hesham Soliman wrote:
>
>>> For the folks in V6OPS, let me describe the situation more  
>>> precisely. A
>>> TURN server receives packets from a TURN client and relays them  
>>> toward a
>>> TURN peer. In the process, the server changes both the source and
>>> destination address. Packets can also flow in the reverse direction.
>>>
>>> For the IPv6 flow label, the best solution as far as I can see, is  
>>> to
>>> copy the flow label from the incoming packet to the outgoing packet.
>>> This seems the right thing to do, even though the source and  
>>> destination
>>> addresses change. Since the addresses change, it is possible that  
>>> two
>>> logically distinct flows that originally had distinct 3-tuples  
>>> (source
>>> IP, dest IP, flow label) before reaching the server get assigned the
>>> same 3-tuple after relaying. However, as far as I can see, having  
>>> the
>>> same 3-tuple does not means the packets ARE part of the same flow,  
>>> but
>>> just that they MAY be part of the same flow.
>>>
>>> Copying the flow label and other fields in the IP header requires
>>> special privileges on most modern OSes (e.g. RAW sockets or kernel
>>> access). So TURN also allows a mode where fields in the IP header  
>>> are
>>> not copied, but are set as best as possible using unprivileged  
>>> user-land
>>> APIs. I am not sure what the situation is for the flow label, but  
>>> for
>>> many other IP header fields, it is easy to set these fields on  
>>> outgoing
>>> packets, but impossible to read them on incoming packets. So a  
>>> somewhat
>>> less desirable but acceptable solution when relaying the flow  
>>> label, as
>>> I can see, is to assume all the packets coming from a given client  
>>> and
>>> going to a given peer constitute a distinct flow and thus assign  
>>> them a
>>> unique flow label after relaying the packets. And similarly in the
>>> opposite direction.
>>>
>>> Comments?
>>
>> My comment is that there's never a valid reason to rewrite IPv6  
>> addresses
>> on the fly, so I don't see why the problem arises. I don't understand
>> the context in which TURN would face this problem, therefore. If you
>> terminate one IPv6 packet flow and originate another one carrying the
>> same application data, that makes two independent flows and they  
>> should
>> have independent flow labels.
>
> => I completely agree. Philip, it might help if you explain why this  
> need
> arises for IPv6. What is the scenario?


TURN is a protocol that allows a client to "engage" the services of a  
relay (= TURN server). The driving motivation for developing TURN is  
to allow a client located behind a non-BEHAVE-compliant NAT to talk  
with other nodes. However, there are other less-common v4 NAT (and  
firewall?) scenarios where TURN is useful.  TURN is an integral part  
of the ICE/STUN/TURN suite of protocols for NAT traversal.

I realize that the question of NATs in the IPv6 world is a touchy  
subject. If there are no NATs in the v6 world, then TURN may never be  
needed. Perhaps the best answer is to wait and see what develops.  
However, like all other IETF protocols, the IESG requires us to  
consider IPv6 support when developing TURN. In same way, ICE and STUN  
also include IPv6 support. So I am trying to specify something that  
seems right for IPv6 with TURN.

For the other fields in the IPv4 and IPv6 headers, TURN copies the  
field from the incoming packet to the outgoing packet except when it  
needs to do something else for relay purposes. That was my motivation  
for suggesting that the flow label also be copied (if possible). But  
from Brian's message, perhaps the more appropriate behavior would be  
to set the outgoing flow label to 0?

- Philip

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 05:53:08 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7A5663A6EB9;
	Tue,  6 May 2008 05:53:08 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6E33E3A6EB9
	for <behave@core3.amsl.com>; Tue,  6 May 2008 05:53:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.759
X-Spam-Level: 
X-Spam-Status: No, score=-1.759 tagged_above=-999 required=5 tests=[AWL=0.540, 
	BAYES_00=-2.599, 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 FWtmt9PdzbQW for <behave@core3.amsl.com>;
	Tue,  6 May 2008 05:53:02 -0700 (PDT)
Received: from smtp-2.servers.netregistry.net (smtp.netregistry.net
	[202.124.241.204])
	by core3.amsl.com (Postfix) with ESMTP id 015363A6801
	for <behave@ietf.org>; Tue,  6 May 2008 05:53:01 -0700 (PDT)
Received: from [124.190.105.201] (helo=[192.168.0.187])
	by smtp-2.servers.netregistry.net protocol: esmtpa (Exim 4.63 #1
	(Debian)) id 1JtMf8-0006J9-6j; Tue, 06 May 2008 22:52:54 +1000
User-Agent: Microsoft-Entourage/12.1.0.080305
Date: Tue, 06 May 2008 22:52:49 +1000
From: Hesham Soliman <hesham@elevatemobile.com>
To: =?ISO-8859-1?B?UultaQ==?= =?ISO-8859-1?B?IERlc3By6XM=?=
	<remi.despres@free.fr>
Message-ID: <C44691C1.6D0E%hesham@elevatemobile.com>
Thread-Topic: [BEHAVE] IPv6 Flow Label
Thread-Index: AciveBaXkrMDWFXocUCgYOvuhls6yg==
In-Reply-To: <4820511F.3060100@free.fr>
Mime-version: 1.0
Cc: v6ops <v6ops@ops.ietf.org>, behave@ietf.org,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


>> => I don't understand two points: - Why is the IPv6 address/header
>> being re-written? - If there is a good answer for the above question
>> then why would you ignore the flow label and not copy it across?
> 
> The destination address of a packet received by a TURN relay is the
> address of the relay.

=> This suggests to me that you have to distinct connections:
Node - relay
Relay - someone else

   That of the packet it forwards, with the same data
>   field, is the address of the next IP layer destination node (the
> destination host or an itermediate NAT).

=> Did you mean NAT? I thought we're talking about IPv6.

> 
> RFC 3697 has a rule that non zero flow labels that leave a node MUST be
> all different for current flows having the same source-destination pair.
> 
> If flow labels received by a TURN relay from two different sources
> happen to be the same while the next IP destination happens to be the
> same NAT, copying flow labels will infringe the rule.

=> I don't know why we're talking about NATs and IPv6. It sounds like a
flawed assumption from the beginning.
There are two situations I can think of that you might be referring to (I
haven't read TURN since 2004)
1. Two connections, node - TURN relay and TURN relay - another node. I have
a feeling this is not the case you have in mind.
2. Node - intermediate strange relay that overwrites headers - end node

There is no need for scenario 2 in IPv6.

If this is in effort to do something for Ipv6 NATs I think it's a waste of
time and adds confusion for the Internet as a whole.

Hesham


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 05:59:06 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 494B73A697C;
	Tue,  6 May 2008 05:59:06 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 184593A6801
	for <behave@core3.amsl.com>; Tue,  6 May 2008 05:59:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[AWL=0.691, 
	BAYES_00=-2.599]
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 eiDcBG10xfzt for <behave@core3.amsl.com>;
	Tue,  6 May 2008 05:59:03 -0700 (PDT)
Received: from smtp-2.servers.netregistry.net (smtp.netregistry.net
	[202.124.241.204])
	by core3.amsl.com (Postfix) with ESMTP id 2D3C028C152
	for <behave@ietf.org>; Tue,  6 May 2008 05:59:02 -0700 (PDT)
Received: from [124.190.105.201] (helo=[192.168.0.187])
	by smtp-2.servers.netregistry.net protocol: esmtpa (Exim 4.63 #1
	(Debian)) id 1JtMkw-0006Nt-E1; Tue, 06 May 2008 22:58:54 +1000
User-Agent: Microsoft-Entourage/12.1.0.080305
Date: Tue, 06 May 2008 22:58:51 +1000
From: Hesham Soliman <hesham@elevatemobile.com>
To: Philip Matthews <philip_matthews@magma.ca>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <C446932B.6D11%hesham@elevatemobile.com>
Thread-Topic: [BEHAVE] IPv6 Flow Label
Thread-Index: AciveO5bFKSmpskDcUi1FKnilqrnbA==
In-Reply-To: <B7A6E4DD-CBAA-4D2A-80CF-92B81216E245@magma.ca>
Mime-version: 1.0
Cc: v6ops <v6ops@ops.ietf.org>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Thanks for the detail Philip, I haven't read TURN for a long time.

>> => I completely agree. Philip, it might help if you explain why this
>> need
>> arises for IPv6. What is the scenario?
> 
> 
> TURN is a protocol that allows a client to "engage" the services of a
> relay (= TURN server). The driving motivation for developing TURN is
> to allow a client located behind a non-BEHAVE-compliant NAT to talk
> with other nodes. However, there are other less-common v4 NAT (and
> firewall?) scenarios where TURN is useful.  TURN is an integral part
> of the ICE/STUN/TURN suite of protocols for NAT traversal.
> 
> I realize that the question of NATs in the IPv6 world is a touchy
> subject. If there are no NATs in the v6 world, then TURN may never be
> needed. Perhaps the best answer is to wait and see what develops.
> However, like all other IETF protocols, the IESG requires us to
> consider IPv6 support when developing TURN. In same way, ICE and STUN
> also include IPv6 support. So I am trying to specify something that
> seems right for IPv6 with TURN.

=> I think that a perfectly useful answer to the IESG is to say that since
there is no _need_ for NATs in IPv6, we don't have to consider it. There are
many NAT traversal mechanisms that don't consider IPv6. There are a few that
do consider IPv6 in the context of allowing IPv4-encapsulated IPv6 traffic
to traverse NATs. But in those scenarios, I don't think the question of the
flow label or the IPv6 header in general needs to be addressed.

> 
> For the other fields in the IPv4 and IPv6 headers, TURN copies the
> field from the incoming packet to the outgoing packet except when it
> needs to do something else for relay purposes. That was my motivation
> for suggesting that the flow label also be copied (if possible). But
> from Brian's message, perhaps the more appropriate behavior would be
> to set the outgoing flow label to 0?

=> Personally, I think the appropriate behaviour is not to do anything for
IPv6 and NATs.

Hesham

> 
> - Philip
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 06:02:06 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 46EFA3A6EA4;
	Tue,  6 May 2008 06:01:53 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D016C3A6FD4
	for <behave@core3.amsl.com>; Tue,  6 May 2008 06:01:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level: 
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[AWL=0.604, 
	BAYES_00=-2.599]
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 b1m69dY-JRRP for <behave@core3.amsl.com>;
	Tue,  6 May 2008 06:01:31 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2])
	by core3.amsl.com (Postfix) with ESMTP id 03A2E3A6EA4
	for <behave@ietf.org>; Tue,  6 May 2008 06:01:04 -0700 (PDT)
Received: by jazz.viagenie.ca (Postfix, from userid 8)
	id A78E029E148D; Tue,  6 May 2008 09:00:32 -0400 (EDT)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67])
	by jazz.viagenie.ca (Postfix) with ESMTP id A0ED829E1483;
	Tue,  6 May 2008 09:00:32 -0400 (EDT)
From: Simon Perreault <simon.perreault@viagenie.ca>
Organization: =?iso-8859-1?q?Viag=E9nie?=
To: behave@ietf.org
Date: Tue, 6 May 2008 09:00:31 -0400
User-Agent: KMail/1.9.9
References: <C44691C1.6D0E%hesham@elevatemobile.com>
In-Reply-To: <C44691C1.6D0E%hesham@elevatemobile.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805060900.32340.simon.perreault@viagenie.ca>
Cc: v6ops <v6ops@ops.ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>,
	Hesham Soliman <hesham@elevatemobile.com>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Tuesday 06 May 2008 08:52:49 Hesham Soliman wrote:
> => I don't know why we're talking about NATs and IPv6. It sounds like a
> flawed assumption from the beginning.

I thought the use case for TURNv6 was to allow interoperability between 
v4-only and v6-only devices, but now I'm not so sure we're all on the same 
wavelength.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 06:15:16 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BD8C53A694F;
	Tue,  6 May 2008 06:15:16 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F1AAE28C13A
	for <behave@core3.amsl.com>; Tue,  6 May 2008 06:15:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.438
X-Spam-Level: 
X-Spam-Status: No, score=-5.438 tagged_above=-999 required=5 tests=[AWL=0.261, 
	BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
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 NkkXDz63q1FM for <behave@core3.amsl.com>;
	Tue,  6 May 2008 06:15:12 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id 90F643A6AA6
	for <behave@ietf.org>; Tue,  6 May 2008 06:15:11 -0700 (PDT)
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m46DF07u022128; Tue, 6 May 2008 16:15:01 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 6 May 2008 16:14:59 +0300
Received: from esdhcp04061.research.nokia.com ([172.21.40.61]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 6 May 2008 16:14:59 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: behave@ietf.org, "ext Hesham Soliman" <hesham@elevatemobile.com>,
	"ext Philip Matthews" <philip_matthews@magma.ca>
Date: Tue, 6 May 2008 16:16:15 +0300
User-Agent: KMail/1.9.9
References: <C44691C1.6D0E%hesham@elevatemobile.com>
In-Reply-To: <C44691C1.6D0E%hesham@elevatemobile.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805061616.16698.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 06 May 2008 13:14:59.0608 (UTC)
	FILETIME=[2FB1D180:01C8AF7B]
X-Nokia-AV: Clean
Cc: v6ops <v6ops@ops.ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Le Tuesday 06 May 2008 15:52:49 ext Hesham Soliman, vous avez =E9crit=A0:
> =3D> I don't know why we're talking about NATs and IPv6. It sounds like a
> flawed assumption from the beginning.
> There are two situations I can think of that you might be referring to (I
> haven't read TURN since 2004)
> 1. Two connections, node - TURN relay and TURN relay - another node. I ha=
ve
> a feeling this is not the case you have in mind.
> 2. Node - intermediate strange relay that overwrites headers - end node
>
> There is no need for scenario 2 in IPv6.
>
> If this is in effort to do something for Ipv6 NATs I think it's a waste of
> time and adds confusion for the Internet as a whole.

You are assuming that scenario 2 implies NAT.

I believe SOCKS (RFC1928) supports IPv6-IPv6 gatewaying, pretty much the sa=
me =

as TURN would. One obvious reason is firewalls. Last time I checked the V6C=
PE =

discussion, it did not seem like IPv6 would deprecate firewalls.

One can nevertheless question the usefulness of IPv6-IPv6 gateways. Afteral=
l =

SOCKS is quite old. And the main driver for TURN is NAT traversal, which is =

not an issue in IPv6-IPv6. Assuming that IPv6 firewalls are well BEHAVE'd, =

then TURN will never be needed in pure IPv6 cases. That seems like an =

optimistic assumption to me, but fine with me.


Then TURN should only support, IPv4-IPv4, IPv6-IPv4 and IPv4-IPv6 cases. An=
d =

then, the issue of flow infos preservation is moot, as flow infos don't exi=
st =

in IPv4. Also then, we're back to my point on that TURN should provide an =

IPv4 mapped address to _IPv6_ TURN clients by default.

-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 06:18:18 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1B72B3A6963;
	Tue,  6 May 2008 06:18:18 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 19D263A6963
	for <behave@core3.amsl.com>; Tue,  6 May 2008 06:18:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level: 
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[AWL=0.341, 
	BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 OV91MnVPdRYJ for <behave@core3.amsl.com>;
	Tue,  6 May 2008 06:18:12 -0700 (PDT)
Received: from smtp-2.servers.netregistry.net (smtp.netregistry.net
	[202.124.241.204])
	by core3.amsl.com (Postfix) with ESMTP id 247FB3A69C9
	for <behave@ietf.org>; Tue,  6 May 2008 06:18:11 -0700 (PDT)
Received: from [124.190.105.201] (helo=[192.168.0.187])
	by smtp-2.servers.netregistry.net protocol: esmtpa (Exim 4.63 #1
	(Debian)) id 1JtN3Y-0006XY-HF; Tue, 06 May 2008 23:18:08 +1000
User-Agent: Microsoft-Entourage/12.1.0.080305
Date: Tue, 06 May 2008 23:17:58 +1000
From: Hesham Soliman <hesham@elevatemobile.com>
To: Simon Perreault <simon.perreault@viagenie.ca>,
	<behave@ietf.org>
Message-ID: <C44697A6.6D17%hesham@elevatemobile.com>
Thread-Topic: [BEHAVE] IPv6 Flow Label
Thread-Index: Acive5oGKBCvkdS8tU+3Zw+x6wqKkg==
In-Reply-To: <200805060900.32340.simon.perreault@viagenie.ca>
Mime-version: 1.0
Cc: v6ops <v6ops@ops.ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org




On 6/05/08 11:00 PM, "Simon Perreault" <simon.perreault@viagenie.ca> wrote:

> On Tuesday 06 May 2008 08:52:49 Hesham Soliman wrote:
>> => I don't know why we're talking about NATs and IPv6. It sounds like a
>> flawed assumption from the beginning.
> 
> I thought the use case for TURNv6 was to allow interoperability between
> v4-only and v6-only devices, but now I'm not so sure we're all on the same
> wavelength.

=> Well, in that case the flow label is a moot point. Also, there are
requirements and solutions being worked on in v6ops to do this using NAT-PT.

Hesham


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 06:20:35 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 534793A694F;
	Tue,  6 May 2008 06:20:35 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A2D1B3A6BB3
	for <behave@core3.amsl.com>; Tue,  6 May 2008 06:20:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.761
X-Spam-Level: 
X-Spam-Status: No, score=-0.761 tagged_above=-999 required=5
	tests=[AWL=-0.458, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	MIME_8BIT_HEADER=0.3, MIME_QP_LONG_LINE=1.396]
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 H73pr7UGJ8MR for <behave@core3.amsl.com>;
	Tue,  6 May 2008 06:20:31 -0700 (PDT)
Received: from smtp-1.servers.netregistry.net (smtp.netregistry.net
	[202.124.241.204])
	by core3.amsl.com (Postfix) with ESMTP id EA80F3A6B15
	for <behave@ietf.org>; Tue,  6 May 2008 06:20:30 -0700 (PDT)
Received: from [124.190.105.201] (helo=[192.168.0.187])
	by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.63 #1
	(Debian)) id 1JtN5n-0007eG-Le; Tue, 06 May 2008 23:20:27 +1000
User-Agent: Microsoft-Entourage/12.1.0.080305
Date: Tue, 06 May 2008 23:20:18 +1000
From: Hesham Soliman <hesham@elevatemobile.com>
To: =?ISO-8859-1?B?UultaQ==?= Denis-Courmont <remi.denis-courmont@nokia.com>, 
	<behave@ietf.org>, ext Philip Matthews <philip_matthews@magma.ca>
Message-ID: <C4469832.6D1C%hesham@elevatemobile.com>
Thread-Topic: [BEHAVE] IPv6 Flow Label
Thread-Index: Acive+14nAMH/cIgqESvWNAJ5L0wXw==
In-Reply-To: <200805061616.16698.remi.denis-courmont@nokia.com>
Mime-version: 1.0
Cc: v6ops <v6ops@ops.ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org




On 6/05/08 11:16 PM, "R=E9mi Denis-Courmont" <remi.denis-courmont@nokia.com>
wrote:

> Le Tuesday 06 May 2008 15:52:49 ext Hesham Soliman, vous avez =E9crit=A0:
>> =3D> I don't know why we're talking about NATs and IPv6. It sounds like a
>> flawed assumption from the beginning.
>> There are two situations I can think of that you might be referring to (I
>> haven't read TURN since 2004)
>> 1. Two connections, node - TURN relay and TURN relay - another node. I h=
ave
>> a feeling this is not the case you have in mind.
>> 2. Node - intermediate strange relay that overwrites headers - end node
>> =

>> There is no need for scenario 2 in IPv6.
>> =

>> If this is in effort to do something for Ipv6 NATs I think it's a waste =
of
>> time and adds confusion for the Internet as a whole.
> =

> You are assuming that scenario 2 implies NAT.
> =

> I believe SOCKS (RFC1928) supports IPv6-IPv6 gatewaying, pretty much the =
same
> as TURN would. One obvious reason is firewalls. Last time I checked the V=
6CPE
> discussion, it did not seem like IPv6 would deprecate firewalls.

=3D> Again, this implies having two different connections and there should =
not
be an issue with flow labels.

> =

> One can nevertheless question the usefulness of IPv6-IPv6 gateways. After=
all
> SOCKS is quite old. And the main driver for TURN is NAT traversal, which =
is
> not an issue in IPv6-IPv6. Assuming that IPv6 firewalls are well BEHAVE'd,
> then TURN will never be needed in pure IPv6 cases. That seems like an
> optimistic assumption to me, but fine with me.
> =

> =

> Then TURN should only support, IPv4-IPv4, IPv6-IPv4 and IPv4-IPv6 cases. =
And
> then, the issue of flow infos preservation is moot, as flow infos don't e=
xist
> in IPv4. Also then, we're back to my point on that TURN should provide an
> IPv4 mapped address to _IPv6_ TURN clients by default.

=3D> Right. I don't know about your point for mapped addresses, but I agree
with the rest. =


Hesham


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 10:46:18 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A646A28C435;
	Tue,  6 May 2008 10:46:18 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7EB5E3A6C57
	for <behave@core3.amsl.com>; Mon,  5 May 2008 14:24:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 KEcNWC8E5ycQ for <behave@core3.amsl.com>;
	Mon,  5 May 2008 14:24:12 -0700 (PDT)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.182])
	by core3.amsl.com (Postfix) with ESMTP id 4B7073A6EA5
	for <behave@ietf.org>; Mon,  5 May 2008 14:24:09 -0700 (PDT)
Received: by wa-out-1112.google.com with SMTP id k34so389445wah.25
	for <behave@ietf.org>; Mon, 05 May 2008 14:24:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:organization:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	bh=OayquIl0ElweDhJH587V/oPS8Z92J/K/UM++36fC444=;
	b=r0zqSnxzG0WLq2LrefbnDpfdSAPbznDG5hR0AZXxiNkk43YUmUIOezShkWOk4e/rlz0qDtMltI+3po4IMV77ACPM+clNg/ZN/TvTM8gZiPG9UiuDVF7q1lel5oeUvCxirv3zjkDkJFt8AwiqlmznU3uegHAFhlnqal3GbAduERI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=jAOTdRP6lCZ8cSNPud54ylMKg1lWiOPv626ednrsT/PjrGjozvOZSlJMBBeKze8YzsRCt3Bdazq45d3l9Wl6U/60pxqY+364P+zKCFZM5c6OuS88nXZXzIzli3h8E3VA3CukhOZb1PbvH8ctYZD1GLGEWtjcpvl8MhHKGyMz08k=
Received: by 10.115.76.1 with SMTP id d1mr6168693wal.228.1210022646248;
	Mon, 05 May 2008 14:24:06 -0700 (PDT)
Received: from ?130.216.38.124? ( [130.216.38.124])
	by mx.google.com with ESMTPS id m40sm11491613wag.50.2008.05.05.14.23.59
	(version=SSLv3 cipher=RC4-MD5); Mon, 05 May 2008 14:24:01 -0700 (PDT)
Message-ID: <481F7AEC.7030209@gmail.com>
Date: Tue, 06 May 2008 09:23:56 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <47F3FA30.2060403@acm.org>	<200805021504.26754.remi.denis-courmont@nokia.com>	<C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>
	<200805050923.50429.remi.denis-courmont@nokia.com>
	<481EFE86.3060808@free.fr>
	<9925D171-E6BA-4490-B9A8-D44419CA221D@magma.ca>
In-Reply-To: <9925D171-E6BA-4490-B9A8-D44419CA221D@magma.ca>
X-Mailman-Approved-At: Tue, 06 May 2008 10:46:17 -0700
Cc: v6ops <v6ops@ops.ietf.org>, behave@ietf.org
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

T24gMjAwOC0wNS0wNiAwMToyMSwgUGhpbGlwIE1hdHRoZXdzIHdyb3RlOgo+IAo+IE9uIE1vbiwg
NS1NYXktMDgsIGF0IDA4OjMzICwgUsOpbWkgRGVzcHLDqXMgd3JvdGU6Cj4+IFLDqW1pIERlbmlz
LUNvdXJtb250IGEgw6ljcml0IDoKPj4+IExlIEZyaWRheSAwMiBNYXkgMjAwOCAyMjoxNjowMiBl
eHQgUGhpbGlwIE1hdHRoZXdzLCB2b3VzIGF2ZXogw6ljcml0IDoKPj4KPj4+PiBUVVJOLTA4IHdp
bGwgc2F5IHRoYXQgYSBzZXJ2ZXIgc2hvdWxkIGNvcHkgdGhlIGZsb3cgbGFiZWwsIGFuZCBpZiB0
aGlzCj4+Pj4gY2Fubm90IGJlIGRvbmUsIHRoZW4gdHJlYXQgdGhlIHBhY2tldHMgdG8vZnJvbSBl
YWNoIHBlZXIgYXMgYSBzZXBhcmF0ZQo+Pj4+IGZsb3cgd2l0aCBzZXBhcmF0ZSBsYWJlbHMuIFRo
aXMgaXMgYWxsIHBhcnQgb2YgdGhlIG5ldyBjb25jZXB0IG9mIGEKPj4+PiBQcmVzZXJ2aW5nIGFs
bG9jYXRpb24gKHdoYXQgSSBjYWxsZWQgYSAiRnVsbHktQ29tcGxpYW50IGFsbG9jYXRpb24iIGlu
Cj4+Pj4gUGhpbGx5KSB0aGF0IEkgYW0gaW4gdGhlIHByb2Nlc3Mgb2YgYWRkaW5nIHJpZ2h0IG5v
dy4KPj4+IEkgbXlzZWxmIGFtIG5vdCBzdXJlIHdoYXQgdGhlICJwcm9wZXIiIGhhbmRsaW5nIG9m
IHRoZSBmbG93IGluZm9zIGlzLgo+Pj4gSWYgYW55b25lIGtub3dzLCB0aGF0IHdvdWxkIGJlIHNv
bWUgNm1hbiBhbmQvb3IgdjZvcHMgcGVvcGxlIChub3QKPj4+IGluY2x1ZGluZyBtZSkuIEZsb3cg
aW5mb3MgaXMgbm90IGp1c3QgbGlrZSBEU0NQLiBSZWZsZWN0aW5nIHRoaXMsIHRoZQo+Pj4gTGlu
dXgoLXNwZWNpZmljKSBBUEkgZm9yIGZsb3cgaW5mb3MgaXMgY29tcGxldGVseSBkaWZmZXJlbnQg
ZnJvbSB0aGF0Cj4+PiBvZiBEU0NQIGFuZCBUVEwuLi4KPj4KPj4gUGVuZGluZyBhbnkgYXBwcm92
ZWQgdXNlIG9mIGZsb3cgbGFiZWxzLCB0aGVyZSBpcyBJTVUgb25seSBvbmUKPj4gY29uc2lzdGVu
dCBiZWhhdmlvciwgZXZlcnl3aGVyZTogdGhlIGZsb3cgbGFiZWwgZmllbGQgTVVTVCBiZSBpZ25v
cmVkCj4+IHdoZW4gcmVjZWl2ZWQsIGFuZCBNVVNUIGJlIHNldCB0byAwIHdoZW4gY3JlYXRlZCAu
Cj4+Cj4+IElmIGFuZCB3aGVuIHNvbWUgdXNlIGlzIGFwcHJvdmVkLCBpdCB3aWxsIGJlIHRpbWUg
dG8gZGVjaWRlIHdoZXRoZXIsCj4+IGluIFRVUk4gaW4gcGFydGljdWxhciwgYW5vdGhlciBiZWhh
dmlvciBpcyBtb3JlIGFwcHJvcHJpYXRlLgo+IAo+IAo+IFdoYXQgYWJvdXQgUkZDIDM2OTcgPz8K
PiBBcmUgeW91IHNheWluZyB0aGF0IHRoaXMgZG9lcyBub3QgZGVzY3JpYmUgYXBwcm92ZWQgYmVo
YXZpb3I/CgpJdCBkb2VzLCBvZiBjb3Vyc2UuIFNvIHRoZSBydWxlIGlzIHJlYWxseSBvbmx5IHRo
YXQgdGhlIGZsb3cgbGFiZWwKbXVzdCBiZSBkZWxpdmVyZWQgKmV4YWN0bHkqIGFzIGl0IHdhcyBz
ZXQgYnkgdGhlIHNvdXJjZSBob3N0IChhbmQgdGhlCmRlZmF1bHQgc2V0dGluZyBpcyB6ZXJvKS4g
IFRVUk4gaGFzIHRvIG9iZXkgdGhhdCBydWxlIGxpa2UgYW55IG90aGVyCmRldmljZSB0aGF0IGZv
cndhcmRzIHBhY2tldHMuCgogICAgQnJpYW4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fCkJlaGF2ZSBtYWlsaW5nIGxpc3QKQmVoYXZlQGlldGYub3JnCmh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vYmVoYXZlCg==


From behave-bounces@ietf.org  Tue May  6 10:46:18 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CA46D28C43B;
	Tue,  6 May 2008 10:46:18 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1B6F23A69BB
	for <behave@core3.amsl.com>; Mon,  5 May 2008 20:20:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.473
X-Spam-Level: 
X-Spam-Status: No, score=-1.473 tagged_above=-999 required=5 tests=[AWL=0.526, 
	BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 NW5YZmNFRbRP for <behave@core3.amsl.com>;
	Mon,  5 May 2008 20:20:54 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.230])
	by core3.amsl.com (Postfix) with ESMTP id 2760C3A6785
	for <behave@ietf.org>; Mon,  5 May 2008 20:20:53 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so112721rvf.49
	for <behave@ietf.org>; Mon, 05 May 2008 20:20:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:organization:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	bh=NAB/lDgyvCQYdQQNwqJrjLL8E3Ncs+jI5UnXD4iMorE=;
	b=O3DNfQVPT7fInyNKmJDsUSM5fDfAaEhvgHbLBDGluWFLkAUPQfbyDKiE60fmLBBpcV+elNzL0b6JmtusLw897vBgo3Sm3/dwL0blX2pV8frN/OaqUqCyU9LKst5og6I69Ks/c7185MUFOBo+s0SJAeY7IXqGJFIm3BgDCwUYcrQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=UspHjaJu2v84otlHD+fD4kEbgbw2DKZKRTZcU2qXgq8OrOK0d20wAhG7X05uKS1GAm5Dd5/5VEzOvP5V23RCTZ0JWC6DBX6yhhPj0llR7YjiwtYcLwgJC/XWYKHhDSTj01d+0vcq2dWTwoU1dfcO4UmMeIZX/6nAm3nzUE8/ob4=
Received: by 10.141.101.15 with SMTP id d15mr101887rvm.249.1210044052462;
	Mon, 05 May 2008 20:20:52 -0700 (PDT)
Received: from ?130.216.38.124? ( [130.216.38.124])
	by mx.google.com with ESMTPS id k41sm193387rvb.3.2008.05.05.20.20.50
	(version=SSLv3 cipher=RC4-MD5); Mon, 05 May 2008 20:20:52 -0700 (PDT)
Message-ID: <481FCE95.50006@gmail.com>
Date: Tue, 06 May 2008 15:20:53 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <47F3FA30.2060403@acm.org>	<200805021504.26754.remi.denis-courmont@nokia.com>	<C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>
	<200805050923.50429.remi.denis-courmont@nokia.com>
	<481EFE86.3060808@free.fr>
	<9925D171-E6BA-4490-B9A8-D44419CA221D@magma.ca>
	<481F7AEC.7030209@gmail.com>
	<9F366B86-DEDB-4BD1-8D68-F614AB910FD8@magma.ca>
In-Reply-To: <9F366B86-DEDB-4BD1-8D68-F614AB910FD8@magma.ca>
X-Mailman-Approved-At: Tue, 06 May 2008 10:46:17 -0700
Cc: v6ops <v6ops@ops.ietf.org>, behave@ietf.org
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

T24gMjAwOC0wNS0wNiAxMzoyMCwgUGhpbGlwIE1hdHRoZXdzIHdyb3RlOgo+IAo+IE9uIE1vbiwg
NS1NYXktMDgsIGF0IDE3OjIzICwgQnJpYW4gRSBDYXJwZW50ZXIgd3JvdGU6Cj4+IE9uIDIwMDgt
MDUtMDYgMDE6MjEsIFBoaWxpcCBNYXR0aGV3cyB3cm90ZToKPj4+Cj4+PiBPbiBNb24sIDUtTWF5
LTA4LCBhdCAwODozMyAsIFLDqW1pIERlc3Byw6lzIHdyb3RlOgo+Pj4+IFLDqW1pIERlbmlzLUNv
dXJtb250IGEgw6ljcml0IDoKPj4+Pj4gTGUgRnJpZGF5IDAyIE1heSAyMDA4IDIyOjE2OjAyIGV4
dCBQaGlsaXAgTWF0dGhld3MsIHZvdXMgYXZleiDDqWNyaXQgOgo+Pj4+Cj4+Pj4+PiBUVVJOLTA4
IHdpbGwgc2F5IHRoYXQgYSBzZXJ2ZXIgc2hvdWxkIGNvcHkgdGhlIGZsb3cgbGFiZWwsIGFuZCBp
Zgo+Pj4+Pj4gdGhpcwo+Pj4+Pj4gY2Fubm90IGJlIGRvbmUsIHRoZW4gdHJlYXQgdGhlIHBhY2tl
dHMgdG8vZnJvbSBlYWNoIHBlZXIgYXMgYQo+Pj4+Pj4gc2VwYXJhdGUKPj4+Pj4+IGZsb3cgd2l0
aCBzZXBhcmF0ZSBsYWJlbHMuIFRoaXMgaXMgYWxsIHBhcnQgb2YgdGhlIG5ldyBjb25jZXB0IG9m
IGEKPj4+Pj4+IFByZXNlcnZpbmcgYWxsb2NhdGlvbiAod2hhdCBJIGNhbGxlZCBhICJGdWxseS1D
b21wbGlhbnQKPj4+Pj4+IGFsbG9jYXRpb24iIGluCj4+Pj4+PiBQaGlsbHkpIHRoYXQgSSBhbSBp
biB0aGUgcHJvY2VzcyBvZiBhZGRpbmcgcmlnaHQgbm93Lgo+Pj4+PiBJIG15c2VsZiBhbSBub3Qg
c3VyZSB3aGF0IHRoZSAicHJvcGVyIiBoYW5kbGluZyBvZiB0aGUgZmxvdyBpbmZvcyBpcy4KPj4+
Pj4gSWYgYW55b25lIGtub3dzLCB0aGF0IHdvdWxkIGJlIHNvbWUgNm1hbiBhbmQvb3IgdjZvcHMg
cGVvcGxlIChub3QKPj4+Pj4gaW5jbHVkaW5nIG1lKS4gRmxvdyBpbmZvcyBpcyBub3QganVzdCBs
aWtlIERTQ1AuIFJlZmxlY3RpbmcgdGhpcywgdGhlCj4+Pj4+IExpbnV4KC1zcGVjaWZpYykgQVBJ
IGZvciBmbG93IGluZm9zIGlzIGNvbXBsZXRlbHkgZGlmZmVyZW50IGZyb20gdGhhdAo+Pj4+PiBv
ZiBEU0NQIGFuZCBUVEwuLi4KPj4+Pgo+Pj4+IFBlbmRpbmcgYW55IGFwcHJvdmVkIHVzZSBvZiBm
bG93IGxhYmVscywgdGhlcmUgaXMgSU1VIG9ubHkgb25lCj4+Pj4gY29uc2lzdGVudCBiZWhhdmlv
ciwgZXZlcnl3aGVyZTogdGhlIGZsb3cgbGFiZWwgZmllbGQgTVVTVCBiZSBpZ25vcmVkCj4+Pj4g
d2hlbiByZWNlaXZlZCwgYW5kIE1VU1QgYmUgc2V0IHRvIDAgd2hlbiBjcmVhdGVkIC4KPj4+Pgo+
Pj4+IElmIGFuZCB3aGVuIHNvbWUgdXNlIGlzIGFwcHJvdmVkLCBpdCB3aWxsIGJlIHRpbWUgdG8g
ZGVjaWRlIHdoZXRoZXIsCj4+Pj4gaW4gVFVSTiBpbiBwYXJ0aWN1bGFyLCBhbm90aGVyIGJlaGF2
aW9yIGlzIG1vcmUgYXBwcm9wcmlhdGUuCj4+Pgo+Pj4KPj4+IFdoYXQgYWJvdXQgUkZDIDM2OTcg
Pz8KPj4+IEFyZSB5b3Ugc2F5aW5nIHRoYXQgdGhpcyBkb2VzIG5vdCBkZXNjcmliZSBhcHByb3Zl
ZCBiZWhhdmlvcj8KPj4KPj4gSXQgZG9lcywgb2YgY291cnNlLiBTbyB0aGUgcnVsZSBpcyByZWFs
bHkgb25seSB0aGF0IHRoZSBmbG93IGxhYmVsCj4+IG11c3QgYmUgZGVsaXZlcmVkICpleGFjdGx5
KiBhcyBpdCB3YXMgc2V0IGJ5IHRoZSBzb3VyY2UgaG9zdCAoYW5kIHRoZQo+PiBkZWZhdWx0IHNl
dHRpbmcgaXMgemVybykuICBUVVJOIGhhcyB0byBvYmV5IHRoYXQgcnVsZSBsaWtlIGFueSBvdGhl
cgo+PiBkZXZpY2UgdGhhdCBmb3J3YXJkcyBwYWNrZXRzLgo+Pgo+IAo+IEZvciB0aGUgZm9sa3Mg
aW4gVjZPUFMsIGxldCBtZSBkZXNjcmliZSB0aGUgc2l0dWF0aW9uIG1vcmUgcHJlY2lzZWx5LiBB
Cj4gVFVSTiBzZXJ2ZXIgcmVjZWl2ZXMgcGFja2V0cyBmcm9tIGEgVFVSTiBjbGllbnQgYW5kIHJl
bGF5cyB0aGVtIHRvd2FyZCBhCj4gVFVSTiBwZWVyLiBJbiB0aGUgcHJvY2VzcywgdGhlIHNlcnZl
ciBjaGFuZ2VzIGJvdGggdGhlIHNvdXJjZSBhbmQKPiBkZXN0aW5hdGlvbiBhZGRyZXNzLiBQYWNr
ZXRzIGNhbiBhbHNvIGZsb3cgaW4gdGhlIHJldmVyc2UgZGlyZWN0aW9uLgo+IAo+IEZvciB0aGUg
SVB2NiBmbG93IGxhYmVsLCB0aGUgYmVzdCBzb2x1dGlvbiBhcyBmYXIgYXMgSSBjYW4gc2VlLCBp
cyB0bwo+IGNvcHkgdGhlIGZsb3cgbGFiZWwgZnJvbSB0aGUgaW5jb21pbmcgcGFja2V0IHRvIHRo
ZSBvdXRnb2luZyBwYWNrZXQuCj4gVGhpcyBzZWVtcyB0aGUgcmlnaHQgdGhpbmcgdG8gZG8sIGV2
ZW4gdGhvdWdoIHRoZSBzb3VyY2UgYW5kIGRlc3RpbmF0aW9uCj4gYWRkcmVzc2VzIGNoYW5nZS4g
U2luY2UgdGhlIGFkZHJlc3NlcyBjaGFuZ2UsIGl0IGlzIHBvc3NpYmxlIHRoYXQgdHdvCj4gbG9n
aWNhbGx5IGRpc3RpbmN0IGZsb3dzIHRoYXQgb3JpZ2luYWxseSBoYWQgZGlzdGluY3QgMy10dXBs
ZXMgKHNvdXJjZQo+IElQLCBkZXN0IElQLCBmbG93IGxhYmVsKSBiZWZvcmUgcmVhY2hpbmcgdGhl
IHNlcnZlciBnZXQgYXNzaWduZWQgdGhlCj4gc2FtZSAzLXR1cGxlIGFmdGVyIHJlbGF5aW5nLiBI
b3dldmVyLCBhcyBmYXIgYXMgSSBjYW4gc2VlLCBoYXZpbmcgdGhlCj4gc2FtZSAzLXR1cGxlIGRv
ZXMgbm90IG1lYW5zIHRoZSBwYWNrZXRzIEFSRSBwYXJ0IG9mIHRoZSBzYW1lIGZsb3csIGJ1dAo+
IGp1c3QgdGhhdCB0aGV5IE1BWSBiZSBwYXJ0IG9mIHRoZSBzYW1lIGZsb3cuCj4gCj4gQ29weWlu
ZyB0aGUgZmxvdyBsYWJlbCBhbmQgb3RoZXIgZmllbGRzIGluIHRoZSBJUCBoZWFkZXIgcmVxdWly
ZXMKPiBzcGVjaWFsIHByaXZpbGVnZXMgb24gbW9zdCBtb2Rlcm4gT1NlcyAoZS5nLiBSQVcgc29j
a2V0cyBvciBrZXJuZWwKPiBhY2Nlc3MpLiBTbyBUVVJOIGFsc28gYWxsb3dzIGEgbW9kZSB3aGVy
ZSBmaWVsZHMgaW4gdGhlIElQIGhlYWRlciBhcmUKPiBub3QgY29waWVkLCBidXQgYXJlIHNldCBh
cyBiZXN0IGFzIHBvc3NpYmxlIHVzaW5nIHVucHJpdmlsZWdlZCB1c2VyLWxhbmQKPiBBUElzLiBJ
IGFtIG5vdCBzdXJlIHdoYXQgdGhlIHNpdHVhdGlvbiBpcyBmb3IgdGhlIGZsb3cgbGFiZWwsIGJ1
dCBmb3IKPiBtYW55IG90aGVyIElQIGhlYWRlciBmaWVsZHMsIGl0IGlzIGVhc3kgdG8gc2V0IHRo
ZXNlIGZpZWxkcyBvbiBvdXRnb2luZwo+IHBhY2tldHMsIGJ1dCBpbXBvc3NpYmxlIHRvIHJlYWQg
dGhlbSBvbiBpbmNvbWluZyBwYWNrZXRzLiBTbyBhIHNvbWV3aGF0Cj4gbGVzcyBkZXNpcmFibGUg
YnV0IGFjY2VwdGFibGUgc29sdXRpb24gd2hlbiByZWxheWluZyB0aGUgZmxvdyBsYWJlbCwgYXMK
PiBJIGNhbiBzZWUsIGlzIHRvIGFzc3VtZSBhbGwgdGhlIHBhY2tldHMgY29taW5nIGZyb20gYSBn
aXZlbiBjbGllbnQgYW5kCj4gZ29pbmcgdG8gYSBnaXZlbiBwZWVyIGNvbnN0aXR1dGUgYSBkaXN0
aW5jdCBmbG93IGFuZCB0aHVzIGFzc2lnbiB0aGVtIGEKPiB1bmlxdWUgZmxvdyBsYWJlbCBhZnRl
ciByZWxheWluZyB0aGUgcGFja2V0cy4gQW5kIHNpbWlsYXJseSBpbiB0aGUKPiBvcHBvc2l0ZSBk
aXJlY3Rpb24uCj4gCj4gQ29tbWVudHM/CgpNeSBjb21tZW50IGlzIHRoYXQgdGhlcmUncyBuZXZl
ciBhIHZhbGlkIHJlYXNvbiB0byByZXdyaXRlIElQdjYgYWRkcmVzc2VzCm9uIHRoZSBmbHksIHNv
IEkgZG9uJ3Qgc2VlIHdoeSB0aGUgcHJvYmxlbSBhcmlzZXMuIEkgZG9uJ3QgdW5kZXJzdGFuZAp0
aGUgY29udGV4dCBpbiB3aGljaCBUVVJOIHdvdWxkIGZhY2UgdGhpcyBwcm9ibGVtLCB0aGVyZWZv
cmUuIElmIHlvdQp0ZXJtaW5hdGUgb25lIElQdjYgcGFja2V0IGZsb3cgYW5kIG9yaWdpbmF0ZSBh
bm90aGVyIG9uZSBjYXJyeWluZyB0aGUKc2FtZSBhcHBsaWNhdGlvbiBkYXRhLCB0aGF0IG1ha2Vz
IHR3byBpbmRlcGVuZGVudCBmbG93cyBhbmQgdGhleSBzaG91bGQKaGF2ZSBpbmRlcGVuZGVudCBm
bG93IGxhYmVscy4KCiAgIEJyaWFuCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXwpCZWhhdmUgbWFpbGluZyBsaXN0CkJlaGF2ZUBpZXRmLm9yZwpodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2JlaGF2ZQo=


From behave-bounces@ietf.org  Tue May  6 10:46:19 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 01DE328C43F;
	Tue,  6 May 2008 10:46:19 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AF05E3A6B66
	for <behave@core3.amsl.com>; Tue,  6 May 2008 07:13:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 EiCLeyrgPmoV for <behave@core3.amsl.com>;
	Tue,  6 May 2008 07:13:44 -0700 (PDT)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190])
	by core3.amsl.com (Postfix) with ESMTP id D3C1F3A68B9
	for <behave@ietf.org>; Tue,  6 May 2008 07:13:44 -0700 (PDT)
Received: from [10.0.1.197] (c-24-6-157-180.hsd1.ca.comcast.net [24.6.157.180])
	by virtualized.org (Postfix) with ESMTP id BC2A51EEBD3;
	Tue,  6 May 2008 07:13:42 -0700 (PDT)
Message-Id: <54C11BC4-76CC-44AC-BBD5-8EEA7ADD6909@virtualized.org>
From: David Conrad <drc@virtualized.org>
To: Hesham Soliman <hesham@elevatemobile.com>
In-Reply-To: <C446932B.6D11%hesham@elevatemobile.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 6 May 2008 07:13:42 -0700
References: <C446932B.6D11%hesham@elevatemobile.com>
X-Mailer: Apple Mail (2.919.2)
X-Mailman-Approved-At: Tue, 06 May 2008 10:46:16 -0700
Cc: v6ops <v6ops@ops.ietf.org>, Behave WG <behave@ietf.org>,
	Philip Matthews <philip_matthews@magma.ca>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hesham,

On May 6, 2008, at 5:58 AM, Hesham Soliman wrote:
> I think that a perfectly useful answer to the IESG is to say that  
> since
> there is no _need_ for NATs in IPv6, we don't have to consider it.

The fact that IPv6 has the same routing technology as IPv4 guarantees  
there will be a market for NATv6 (assuming IPv6 gets deployed), if for  
no other reason than people not wanting to be tied to their ISP.

> Personally, I think the appropriate behaviour is not to do anything  
> for
> IPv6 and NATs.

It would be sad if the IETF did not learn from past mistakes.

Regards,
-drc

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 10:46:19 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 262F828C443;
	Tue,  6 May 2008 10:46:19 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8198C3A69B6
	for <behave@core3.amsl.com>; Tue,  6 May 2008 07:24:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.046
X-Spam-Level: 
X-Spam-Status: No, score=-3.046 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_LOW=-1]
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 7cC1vj4J2VOM for <behave@core3.amsl.com>;
	Tue,  6 May 2008 07:24:48 -0700 (PDT)
Received: from brmea-mail-1.sun.com (brmea-mail-1.Sun.COM [192.18.98.31])
	by core3.amsl.com (Postfix) with ESMTP id EF60A3A6A14
	for <behave@ietf.org>; Tue,  6 May 2008 07:24:46 -0700 (PDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	m46EOi66003373 for <behave@ietf.org>; Tue, 6 May 2008 14:24:44 GMT
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
	(Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
	id <0K0G00301865RV00@mail-amer.sun.com>
	(original mail from Sebastien.Roy@Sun.COM) for behave@ietf.org; Tue,
	06 May 2008 08:24:44 -0600 (MDT)
Received: from [129.148.174.103] by mail-amer.sun.com
	(Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
	with ESMTPSA id <0K0G00F0GAP6UM70@mail-amer.sun.com>; Tue,
	06 May 2008 08:24:42 -0600 (MDT)
Date: Tue, 06 May 2008 10:24:41 -0400
From: Sebastien Roy <Sebastien.Roy@Sun.COM>
In-reply-to: <C446932B.6D11%hesham@elevatemobile.com>
To: Hesham Soliman <hesham@elevatemobile.com>
Message-id: <1210083881.19601.22.camel@strat>
Organization: Sun Microsystems
MIME-version: 1.0
X-Mailer: Evolution 2.22.0
References: <C446932B.6D11%hesham@elevatemobile.com>
X-Mailman-Approved-At: Tue, 06 May 2008 10:46:17 -0700
Cc: v6ops <v6ops@ops.ietf.org>, Behave WG <behave@ietf.org>,
	Philip Matthews <philip_matthews@magma.ca>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hesham,

On Tue, 2008-05-06 at 22:58 +1000, Hesham Soliman wrote:
> => I think that a perfectly useful answer to the IESG is to say that since
> there is no _need_ for NATs in IPv6, we don't have to consider it.

This is intended merely as a data-point, and not to fuel any NAT-related
fires:

I'm aware of IPv4 deployments using NAT in order to easily implement
transparent proxies.  Specifically, they use a NAT to transparently
redirect packets to a local address and port, and a user-space proxy
receives those packets, processes them, and retransmits them.  The use
of NAT here has nothing to do with preserving address space, but as a
hack to transparently redirect all packets to a local address and port
in order to have a local application receive them.

I'm also aware of deployments implementing this same hack for IPv6, so
to issue a blanket statement that there is no need for NATs with IPv6
may be ignoring some weird use cases like the one above.

That said, I don't know whether this particular use of NAT needs to be
considered here, I'm merely stating that there is IPv6 NAT out there
(much to my chagrin) that might need to be considered.

-Seb


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 14:23:07 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF2013A7057;
	Tue,  6 May 2008 14:23:03 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 23F7828C109
	for <behave@core3.amsl.com>; Tue,  6 May 2008 14:23:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=0.150, 
	BAYES_00=-2.599, 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 996pkkiM4gUr for <behave@core3.amsl.com>;
	Tue,  6 May 2008 14:23:00 -0700 (PDT)
Received: from mail-01.primus.ca (mail3.primus.ca [216.254.141.170])
	by core3.amsl.com (Postfix) with ESMTP id 7BA653A7060
	for <behave@ietf.org>; Tue,  6 May 2008 14:22:14 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-01.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1JtUc0-0007Rv-0g; Tue, 06 May 2008 17:22:12 -0400
Message-Id: <7D18EE08-2516-46F8-B9B4-1CE1A4E48459@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: v6ops <v6ops@ops.ietf.org>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>,
	Hesham Soliman <Hesham@elevatemobile.com>,
	=?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>,
	=?ISO-8859-1?Q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
In-Reply-To: <C4469832.6D1C%hesham@elevatemobile.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 6 May 2008 14:35:39 -0400
References: <C4469832.6D1C%hesham@elevatemobile.com>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I would prefer that this thread not dissolve into a debate on whether  
or not there will be NATs in IPv6 networks. I would also prefer that  
this thread not discuss scenarios in which TURN might or might not be  
used in IPv6 scenarios.  If you wish, let's discuss these on other  
threads.

In this thread, I would like to start with the assumption that TURN  
_is_ being used to relay IPv6 to IPv6.  IF this is done, then what is  
the appropriate treatment for the flow label field?

Right now, I see two alternatives:

1) Copy the flow label from the incoming packet to the outgoing packet  
if possible. If not possible (because the appropriate APIs do not  
exist on the OS on which the TURN server runs to allow the incoming  
flow label to be read), then treat each (client, peer) combination as  
defining a flow and assign unique flow labels correspondingly.

2) Always set the outgoing flow label to 0.

(See previous messages in this thread for more details).

If it helps the discussion, think about replacing the TURN server with  
any middleware box that modifies addresses (for example, an SIP  
Session Border Controller). I think the question is the same.

I would greatly appreciate help for folks familiar with the IPv6 flow  
label in making a decision between the two alternatives.

- Philip


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 16:25:48 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0A6F128C52F;
	Tue,  6 May 2008 16:23:07 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DCECA28C4F6
	for <behave@core3.amsl.com>; Tue,  6 May 2008 16:20:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.709
X-Spam-Level: 
X-Spam-Status: No, score=-1.709 tagged_above=-999 required=5 tests=[AWL=0.890, 
	BAYES_00=-2.599]
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 cSL5vyBut2aF for <behave@core3.amsl.com>;
	Tue,  6 May 2008 16:19:08 -0700 (PDT)
Received: from smtp-2.servers.netregistry.net (smtp.netregistry.net
	[202.124.241.204])
	by core3.amsl.com (Postfix) with ESMTP id DFE3D28C12A
	for <behave@ietf.org>; Tue,  6 May 2008 16:18:26 -0700 (PDT)
Received: from [124.190.105.201] (helo=[192.168.0.187])
	by smtp-2.servers.netregistry.net protocol: esmtpa (Exim 4.63 #1
	(Debian)) id 1JtWQJ-0006Go-Dc; Wed, 07 May 2008 09:18:15 +1000
User-Agent: Microsoft-Entourage/12.1.0.080305
Date: Wed, 07 May 2008 09:17:51 +1000
From: Hesham Soliman <hesham@elevatemobile.com>
To: Sebastien Roy <Sebastien.Roy@Sun.COM>
Message-ID: <C447243F.6D3A%hesham@elevatemobile.com>
Thread-Topic: [BEHAVE] IPv6 Flow Label
Thread-Index: Acivz2eG+zCPU1h7HkGftijoPZ+8OQ==
In-Reply-To: <1210083881.19601.22.camel@strat>
Mime-version: 1.0
Cc: v6ops <v6ops@ops.ietf.org>, Behave WG <behave@ietf.org>,
	Philip Matthews <philip_matthews@magma.ca>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org




On 7/05/08 12:24 AM, "Sebastien Roy" <Sebastien.Roy@Sun.COM> wrote:

> Hesham,
> 
> On Tue, 2008-05-06 at 22:58 +1000, Hesham Soliman wrote:
>> => I think that a perfectly useful answer to the IESG is to say that since
>> there is no _need_ for NATs in IPv6, we don't have to consider it.
> 
> This is intended merely as a data-point, and not to fuel any NAT-related
> fires:
> 
> I'm aware of IPv4 deployments using NAT in order to easily implement
> transparent proxies.  Specifically, they use a NAT to transparently
> redirect packets to a local address and port, and a user-space proxy
> receives those packets, processes them, and retransmits them.  The use
> of NAT here has nothing to do with preserving address space, but as a
> hack to transparently redirect all packets to a local address and port
> in order to have a local application receive them.
> 
> I'm also aware of deployments implementing this same hack for IPv6, so
> to issue a blanket statement that there is no need for NATs with IPv6
> may be ignoring some weird use cases like the one above.

=> As you acknowledge, those are hacks and weird cases. The above doesn't
imply a _technical need_. We don't develop standards for everyone who comes
along with  the hack of the day. If we did that, we'd be in trouble IMHO.

Hesham


> 
> That said, I don't know whether this particular use of NAT needs to be
> considered here, I'm merely stating that there is IPv6 NAT out there
> (much to my chagrin) that might need to be considered.
> 
> -Seb
> 
> 


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 16:28:51 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D729E28C50A;
	Tue,  6 May 2008 16:28:40 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D70D028C4FD
	for <behave@core3.amsl.com>; Tue,  6 May 2008 16:28:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.559
X-Spam-Level: 
X-Spam-Status: No, score=-1.559 tagged_above=-999 required=5 tests=[AWL=0.740, 
	BAYES_00=-2.599, 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 NrTHmM5+jePz for <behave@core3.amsl.com>;
	Tue,  6 May 2008 16:27:42 -0700 (PDT)
Received: from smtp-2.servers.netregistry.net (smtp.netregistry.net
	[202.124.241.204])
	by core3.amsl.com (Postfix) with ESMTP id A6BDE28C52A
	for <behave@ietf.org>; Tue,  6 May 2008 16:22:57 -0700 (PDT)
Received: from [124.190.105.201] (helo=[192.168.0.187])
	by smtp-2.servers.netregistry.net protocol: esmtpa (Exim 4.63 #1
	(Debian)) id 1JtWUW-0006Ra-Ha; Wed, 07 May 2008 09:22:40 +1000
User-Agent: Microsoft-Entourage/12.1.0.080305
Date: Wed, 07 May 2008 09:22:26 +1000
From: Hesham Soliman <hesham@elevatemobile.com>
To: Philip Matthews <philip_matthews@magma.ca>, v6ops <v6ops@ops.ietf.org>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>,
	=?ISO-8859-1?B?UultaQ==?= =?ISO-8859-1?B?IERlc3By6XM=?=
	<remi.despres@free.fr>, =?ISO-8859-1?B?UultaQ==?= Denis-Courmont
	<remi.denis-courmont@nokia.com>
Message-ID: <C4472552.6D3C%hesham@elevatemobile.com>
Thread-Topic: IPv6 Flow Label
Thread-Index: Aciv0Atv3LrEExMHnkmL6HhYRz8dPA==
In-Reply-To: <7D18EE08-2516-46F8-B9B4-1CE1A4E48459@magma.ca>
Mime-version: 1.0
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Philip, 

> I would prefer that this thread not dissolve into a debate on whether
> or not there will be NATs in IPv6 networks. I would also prefer that
> this thread not discuss scenarios in which TURN might or might not be
> used in IPv6 scenarios.  If you wish, let's discuss these on other
> threads.
> 
> In this thread, I would like to start with the assumption that TURN
> _is_ being used to relay IPv6 to IPv6.  IF this is done, then what is
> the appropriate treatment for the flow label field?

=> I think it is perfectly valid to question the scenario since you're
asking us about what needs to be done in that scenario. Bottom line, if
you're overwriting IPv6 addresses, it doesn't matter what you do with the
flow label because you already broke it.

> 
> Right now, I see two alternatives:
> 
> 1) Copy the flow label from the incoming packet to the outgoing packet
> if possible. If not possible (because the appropriate APIs do not
> exist on the OS on which the TURN server runs to allow the incoming
> flow label to be read), then treat each (client, peer) combination as
> defining a flow and assign unique flow labels correspondingly.
> 
> 2) Always set the outgoing flow label to 0.

=> If the addresses are being overwritten then 1) makes no sense and 2)
implies breaking the glow label use anyway.

Hesham


> 
> (See previous messages in this thread for more details).
> 
> If it helps the discussion, think about replacing the TURN server with
> any middleware box that modifies addresses (for example, an SIP
> Session Border Controller). I think the question is the same.
> 
> I would greatly appreciate help for folks familiar with the IPv6 flow
> label in making a decision between the two alternatives.
> 
> - Philip
> 
> 


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 18:42:01 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0DCC73A7046;
	Tue,  6 May 2008 18:42:01 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1B2683A7053
	for <behave@core3.amsl.com>; Tue,  6 May 2008 18:42:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.938
X-Spam-Level: 
X-Spam-Status: No, score=-1.938 tagged_above=-999 required=5 tests=[AWL=0.661, 
	BAYES_00=-2.599]
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 w4Utfn-Idc9q for <behave@core3.amsl.com>;
	Tue,  6 May 2008 18:41:59 -0700 (PDT)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183])
	by core3.amsl.com (Postfix) with ESMTP id 2CFD13A67C1
	for <behave@ietf.org>; Tue,  6 May 2008 18:41:59 -0700 (PDT)
Received: by wa-out-1112.google.com with SMTP id k34so119094wah.25
	for <behave@ietf.org>; Tue, 06 May 2008 18:41:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:organization:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	bh=iEd+xb/5knBHbAjWgXTqLjFRJSjZraSzIGhr46IKeVI=;
	b=qphgnlcuFEeE2b5Yl6eiUtiLp+UEFZEfQTSSiEUK3kpN8kbSX0zUOayfrEO5fUO6vR0P8Sxs9vxm8FFOFrZqMDEO9x1wgb+mU9DzQkvF+T8HTJQoulDRYw5vS8X0bimMNMS1jCPpaUkeOMNyMnclCabK0wRp0dPQho1vYrSP91U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=W+rcIXUUVEhhah1BkYm++Ln8qg1chKtzBgy+HTkRWrw9cMRYsl4tQFujbuK0Ik+KcIdhby8pDgWKHJv0c+wIIB2g8RtnepZ4sD9bkT+jheh5bpIg8XLqQtI410l7Wvjzo8VjIu7r32FTkLPYTiYk8hswe8+BmxeHCzbSfb9O/8s=
Received: by 10.114.76.1 with SMTP id y1mr1376092waa.38.1210124516790;
	Tue, 06 May 2008 18:41:56 -0700 (PDT)
Received: from ?130.216.38.124? ( [130.216.38.124])
	by mx.google.com with ESMTPS id j21sm3059034wah.6.2008.05.06.18.41.54
	(version=SSLv3 cipher=RC4-MD5); Tue, 06 May 2008 18:41:56 -0700 (PDT)
Message-ID: <482108DF.4020800@gmail.com>
Date: Wed, 07 May 2008 13:41:51 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <C4469832.6D1C%hesham@elevatemobile.com>
	<7D18EE08-2516-46F8-B9B4-1CE1A4E48459@magma.ca>
In-Reply-To: <7D18EE08-2516-46F8-B9B4-1CE1A4E48459@magma.ca>
Cc: =?UTF-8?B?UsOpbQ==?=@core3.amsl.com, Behave WG <behave@ietf.org>,
	v6ops <v6ops@ops.ietf.org>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 2008-05-07 06:35, Philip Matthews wrote:
> I would prefer that this thread not dissolve into a debate on whether or
> not there will be NATs in IPv6 networks. I would also prefer that this
> thread not discuss scenarios in which TURN might or might not be used in
> IPv6 scenarios.  If you wish, let's discuss these on other threads.
> 
> In this thread, I would like to start with the assumption that TURN _is_
> being used to relay IPv6 to IPv6.  IF this is done, then what is the
> appropriate treatment for the flow label field?
> 
> Right now, I see two alternatives:
> 
> 1) Copy the flow label from the incoming packet to the outgoing packet
> if possible. If not possible (because the appropriate APIs do not exist
> on the OS on which the TURN server runs to allow the incoming flow label
> to be read), then treat each (client, peer) combination as defining a
> flow and assign unique flow labels correspondingly.

I'm disturbed by the idea of copying the label. The rules
were designed in such a way that the 3tuple {DA, SA, flow label}
is bound to be unique, without any signaling, so that flows can
always be identified by any router they happen to go through.
So I think that any relay device that is not a simple packet
forwarder should assign a new flow label, to guarantee that
uniqueness.
> 
> 2) Always set the outgoing flow label to 0.

This is a subset of "assign a new flow label". Zero is always
allowed.

The rules in RFC3697 were intended to make the flow label's
semantics robust even when there are different use cases
operating simultaneously. It could be the case (I'm making
this up) that the originating host wants to use flow labels
to support load-spreading, and the TURN relay wants to use
flow labels to support some future QOS mechanism. "Assign
a new flow label" works well in that case.

So, I'd say that the default behavior for a relayed packet
should be "Assign 0", and "Assign a new flow label according to
RFC3697" should be optional (just as the whole of RFC3697 is optional).
And this is entirely independent of whether or not the incoming
packet has a non-zero flow label.

(The same is not true of the DSCP. There's every reason that should
be copied as-is. But I expect you know that.)

    Brian


> 
> (See previous messages in this thread for more details).
> 
> If it helps the discussion, think about replacing the TURN server with
> any middleware box that modifies addresses (for example, an SIP Session
> Border Controller). I think the question is the same.
> 
> I would greatly appreciate help for folks familiar with the IPv6 flow
> label in making a decision between the two alternatives.
> 
> - Philip
> 
> 
> 
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 20:13:38 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 39E343A69A2;
	Tue,  6 May 2008 20:13:38 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1479D3A67B2
	for <behave@core3.amsl.com>; Tue,  6 May 2008 20:13:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.049
X-Spam-Level: 
X-Spam-Status: No, score=-2.049 tagged_above=-999 required=5
	tests=[AWL=-0.050, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 Ne8laPWxIL71 for <behave@core3.amsl.com>;
	Tue,  6 May 2008 20:13:35 -0700 (PDT)
Received: from mail-05.primus.ca (mail3.primus.ca [216.254.141.170])
	by core3.amsl.com (Postfix) with ESMTP id 1CE2C3A69A2
	for <behave@ietf.org>; Tue,  6 May 2008 20:13:34 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-05.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1Jta4n-0001pD-2Z; Tue, 06 May 2008 23:12:18 -0400
Message-Id: <FF860B33-ABAF-4E9B-A8B2-B673CF2BAB99@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Hesham Soliman <Hesham@elevatemobile.com>
In-Reply-To: <C4472552.6D3C%hesham@elevatemobile.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 6 May 2008 23:13:28 -0400
References: <C4472552.6D3C%hesham@elevatemobile.com>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Cc: v6ops <v6ops@ops.ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>,
	Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org



On Tue, 6-May-08, at 19:22 , Hesham Soliman wrote:
> Philip,
>
>> I would prefer that this thread not dissolve into a debate on whether
>> or not there will be NATs in IPv6 networks. I would also prefer that
>> this thread not discuss scenarios in which TURN might or might not be
>> used in IPv6 scenarios.  If you wish, let's discuss these on other
>> threads.
>>
>> In this thread, I would like to start with the assumption that TURN
>> _is_ being used to relay IPv6 to IPv6.  IF this is done, then what is
>> the appropriate treatment for the flow label field?
>
> => I think it is perfectly valid to question the scenario since you're
> asking us about what needs to be done in that scenario. Bottom line,  
> if
> you're overwriting IPv6 addresses, it doesn't matter what you do  
> with the
> flow label because you already broke it.
>

Hesham:

If I understand you correctly, you are arguing that we should not  
consider this question, because TURN should never be used with IPv6.

My take on this is as follows. It may be that TURN will never get used  
as an IPv6-to-IPv6 relay.  If so, then this discussion is  
unnecessary.  However, v6OPS is currently discussing the possibility  
of NATing between IPv4 and IPv6, so there is the chance that TURN  
might be useful in a v6 context. Furthermore, the IESG requires that  
all protocols consider IPv6, so it is easier and faster for me (as  
TURN editor) to simply add the small extra text to cover the v6 case  
than to fight for a special exception to the rule.

Does this make sense? Do I correctly understand your position?

- Philip

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 20:34:32 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6836F3A6C8C;
	Tue,  6 May 2008 20:34:32 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0859B3A6BEB
	for <behave@core3.amsl.com>; Tue,  6 May 2008 20:34:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.337
X-Spam-Level: 
X-Spam-Status: No, score=-2.337 tagged_above=-999 required=5 tests=[AWL=0.263, 
	BAYES_00=-2.599]
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 vMzVKUQ68rol for <behave@core3.amsl.com>;
	Tue,  6 May 2008 20:34:30 -0700 (PDT)
Received: from mail-08.primus.ca (mail3.primus.ca [216.254.141.170])
	by core3.amsl.com (Postfix) with ESMTP id 04C693A69A2
	for <behave@ietf.org>; Tue,  6 May 2008 20:34:29 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-08.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1JtaQA-0008A3-2z; Tue, 06 May 2008 23:34:23 -0400
Message-Id: <D08A6D90-A2C5-4B28-B49B-265811C55741@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <482108DF.4020800@gmail.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 6 May 2008 23:34:22 -0400
References: <C4469832.6D1C%hesham@elevatemobile.com>
	<7D18EE08-2516-46F8-B9B4-1CE1A4E48459@magma.ca>
	<482108DF.4020800@gmail.com>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Cc: v6ops <v6ops@ops.ietf.org>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Tue, 6-May-08, at 21:41 , Brian E Carpenter wrote:
> On 2008-05-07 06:35, Philip Matthews wrote:
>> I would prefer that this thread not dissolve into a debate on  
>> whether or
>> not there will be NATs in IPv6 networks. I would also prefer that  
>> this
>> thread not discuss scenarios in which TURN might or might not be  
>> used in
>> IPv6 scenarios.  If you wish, let's discuss these on other threads.
>>
>> In this thread, I would like to start with the assumption that TURN  
>> _is_
>> being used to relay IPv6 to IPv6.  IF this is done, then what is the
>> appropriate treatment for the flow label field?
>>
>> Right now, I see two alternatives:
>>
>> 1) Copy the flow label from the incoming packet to the outgoing  
>> packet
>> if possible. If not possible (because the appropriate APIs do not  
>> exist
>> on the OS on which the TURN server runs to allow the incoming flow  
>> label
>> to be read), then treat each (client, peer) combination as defining a
>> flow and assign unique flow labels correspondingly.
>
> I'm disturbed by the idea of copying the label. The rules
> were designed in such a way that the 3tuple {DA, SA, flow label}
> is bound to be unique, without any signaling, so that flows can
> always be identified by any router they happen to go through.
> So I think that any relay device that is not a simple packet
> forwarder should assign a new flow label, to guarantee that
> uniqueness.
>>
>> 2) Always set the outgoing flow label to 0.
>
> This is a subset of "assign a new flow label". Zero is always
> allowed.
>
> The rules in RFC3697 were intended to make the flow label's
> semantics robust even when there are different use cases
> operating simultaneously. It could be the case (I'm making
> this up) that the originating host wants to use flow labels
> to support load-spreading, and the TURN relay wants to use
> flow labels to support some future QOS mechanism. "Assign
> a new flow label" works well in that case.
>
> So, I'd say that the default behavior for a relayed packet
> should be "Assign 0", and "Assign a new flow label according to
> RFC3697" should be optional (just as the whole of RFC3697 is  
> optional).
> And this is entirely independent of whether or not the incoming
> packet has a non-zero flow label.

I have no technical problem with doing with you suggest.

My only question is: if many devices adopt this approach, then won't  
this mean that the flow label will often be zero, and thus useless for  
things like load-balancing in equal-cost multi-path scenarios?

>
>
> (The same is not true of the DSCP. There's every reason that should
> be copied as-is. But I expect you know that.)

The proposed DSCP text says that the DSCP should be copied unless the  
relay believes, through unspecified means, that another value for the  
outgoing DSCP is appropriate. However, if the incoming value cannot be  
read, then set the outgoing value to Best Effort (again, unless the  
relay believes another value is more appropriate).

Believe me, the v4 cases have had much discussion (including the  
involvement of three current ADs).

- Philip


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 20:41:22 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7B56C28C388;
	Tue,  6 May 2008 20:41:22 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4B3F728C505
	for <behave@core3.amsl.com>; Tue,  6 May 2008 20:41:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.456
X-Spam-Level: 
X-Spam-Status: No, score=-1.456 tagged_above=-999 required=5 tests=[AWL=0.543, 
	BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 7PqutYhXCOEG for <behave@core3.amsl.com>;
	Tue,  6 May 2008 20:41:20 -0700 (PDT)
Received: from smtp-1.servers.netregistry.net (smtp.netregistry.net
	[202.124.241.204])
	by core3.amsl.com (Postfix) with ESMTP id 8151528C388
	for <behave@ietf.org>; Tue,  6 May 2008 20:41:19 -0700 (PDT)
Received: from [211.27.108.142] (helo=[10.0.0.10])
	by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.63 #1
	(Debian)) id 1JtaWZ-0000VI-28; Wed, 07 May 2008 13:40:59 +1000
User-Agent: Microsoft-Entourage/12.1.0.080305
Date: Wed, 07 May 2008 13:40:43 +1000
From: Hesham Soliman <hesham@elevatemobile.com>
To: Philip Matthews <philip_matthews@magma.ca>
Message-ID: <C44761DB.6D4B%hesham@elevatemobile.com>
Thread-Topic: IPv6 Flow Label
Thread-Index: Aciv9CBerG3fsS/nu0Ka1PiAXnUEKw==
In-Reply-To: <FF860B33-ABAF-4E9B-A8B2-B673CF2BAB99@magma.ca>
Mime-version: 1.0
Cc: v6ops <v6ops@ops.ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>,
	Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

> 
> Hesham:
> 
> If I understand you correctly, you are arguing that we should not
> consider this question, because TURN should never be used with IPv6.

=> No I was only referring to the IPv6-IPv6 relay scenario.

> 
> My take on this is as follows. It may be that TURN will never get used
> as an IPv6-to-IPv6 relay.  If so, then this discussion is
> unnecessary.  However, v6OPS is currently discussing the possibility
> of NATing between IPv4 and IPv6, so there is the chance that TURN
> might be useful in a v6 context.

=> That's fine with me. In that scenario the question of the flow label
would not come up though.

 Furthermore, the IESG requires that
> all protocols consider IPv6, so it is easier and faster for me (as
> TURN editor) to simply add the small extra text to cover the v6 case
> than to fight for a special exception to the rule.

=> I think you could think of analogous situations where the requirement
would not apply and therefore the IESG would not hold you responsible. For
instance, suppose we're updating the NAT RFC or RFC 1918. I'm pretty sure
the IESG would not require you to reserve a block of IPv6 addresses for
IPv6-IPv6 NATs. This is a similar case.

> 
> Does this make sense? Do I correctly understand your position?

=> I was only referring to IPv6-IPv6 scenarios, clearly there is merit in
the IPv4-IPv6 cases.

Hesham

> 
> - Philip
> 


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 20:50:12 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2B6503A6A8C;
	Tue,  6 May 2008 20:50:12 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 76B663A69BA
	for <behave@core3.amsl.com>; Tue,  6 May 2008 20:50:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=0.622, 
	BAYES_00=-2.599]
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 BuUQbdZALGPw for <behave@core3.amsl.com>;
	Tue,  6 May 2008 20:50:09 -0700 (PDT)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181])
	by core3.amsl.com (Postfix) with ESMTP id 880553A6843
	for <behave@ietf.org>; Tue,  6 May 2008 20:50:09 -0700 (PDT)
Received: by wa-out-1112.google.com with SMTP id k34so183027wah.25
	for <behave@ietf.org>; Tue, 06 May 2008 20:50:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:organization:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	bh=MElcPhDt61oZ+4bktv6Wis1knDZU4EFXMIVafSBmijQ=;
	b=Q9nha5POK1yDUIuxiQ9DL/fhG5s0PcuElGrwkuW5xVj0XYsMkvrTqAoHDfjFNVrUzR4wa5cFQ9hN1Oe4G6brGmIgDcHw+rbviu+xplv0Ua3q3Ab6UtM/b08Ve3gjndDo0If1VnDebqN4pgs9Pby6mDJFPE6ehWRcjfWoN7pxYzA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=UMJDqApdmz8rb7kkIKI64Vx0IUCYS4DovTY5bvW1ob+uD0Qz3IB2LepOv5+2qP/HamvYBAVhuqroPQo/GE/gCEmo6eBm3ZU9JqTiZ9NrGhKzaRJsZIFvwoMT8vxBPrnLbyZBNlCGI7ioBXgyFgXna+TUfrkpKqrpnvZ1I0cMZFY=
Received: by 10.114.58.6 with SMTP id g6mr1457596waa.68.1210132207288;
	Tue, 06 May 2008 20:50:07 -0700 (PDT)
Received: from ?130.216.38.124? ( [130.216.38.124])
	by mx.google.com with ESMTPS id k39sm3313897wah.3.2008.05.06.20.50.05
	(version=SSLv3 cipher=RC4-MD5); Tue, 06 May 2008 20:50:07 -0700 (PDT)
Message-ID: <482126E9.9070106@gmail.com>
Date: Wed, 07 May 2008 15:50:01 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <C4469832.6D1C%hesham@elevatemobile.com>
	<7D18EE08-2516-46F8-B9B4-1CE1A4E48459@magma.ca>
	<482108DF.4020800@gmail.com>
	<D08A6D90-A2C5-4B28-B49B-265811C55741@magma.ca>
In-Reply-To: <D08A6D90-A2C5-4B28-B49B-265811C55741@magma.ca>
Cc: =?UTF-8?B?UsOpbQ==?=@core3.amsl.com, Behave WG <behave@ietf.org>,
	v6ops <v6ops@ops.ietf.org>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

In line..

On 2008-05-07 15:34, Philip Matthews wrote:
> 
> On Tue, 6-May-08, at 21:41 , Brian E Carpenter wrote:
>> On 2008-05-07 06:35, Philip Matthews wrote:
>>> I would prefer that this thread not dissolve into a debate on whether or
>>> not there will be NATs in IPv6 networks. I would also prefer that this
>>> thread not discuss scenarios in which TURN might or might not be used in
>>> IPv6 scenarios.  If you wish, let's discuss these on other threads.
>>>
>>> In this thread, I would like to start with the assumption that TURN _is_
>>> being used to relay IPv6 to IPv6.  IF this is done, then what is the
>>> appropriate treatment for the flow label field?
>>>
>>> Right now, I see two alternatives:
>>>
>>> 1) Copy the flow label from the incoming packet to the outgoing packet
>>> if possible. If not possible (because the appropriate APIs do not exist
>>> on the OS on which the TURN server runs to allow the incoming flow label
>>> to be read), then treat each (client, peer) combination as defining a
>>> flow and assign unique flow labels correspondingly.
>>
>> I'm disturbed by the idea of copying the label. The rules
>> were designed in such a way that the 3tuple {DA, SA, flow label}
>> is bound to be unique, without any signaling, so that flows can
>> always be identified by any router they happen to go through.
>> So I think that any relay device that is not a simple packet
>> forwarder should assign a new flow label, to guarantee that
>> uniqueness.
>>>
>>> 2) Always set the outgoing flow label to 0.
>>
>> This is a subset of "assign a new flow label". Zero is always
>> allowed.
>>
>> The rules in RFC3697 were intended to make the flow label's
>> semantics robust even when there are different use cases
>> operating simultaneously. It could be the case (I'm making
>> this up) that the originating host wants to use flow labels
>> to support load-spreading, and the TURN relay wants to use
>> flow labels to support some future QOS mechanism. "Assign
>> a new flow label" works well in that case.
>>
>> So, I'd say that the default behavior for a relayed packet
>> should be "Assign 0", and "Assign a new flow label according to
>> RFC3697" should be optional (just as the whole of RFC3697 is optional).
>> And this is entirely independent of whether or not the incoming
>> packet has a non-zero flow label.
> 
> I have no technical problem with doing with you suggest.
> 
> My only question is: if many devices adopt this approach, then won't
> this mean that the flow label will often be zero, and thus useless for
> things like load-balancing in equal-cost multi-path scenarios?

That is today's situation - there was no consensus for assuming
that load-balancing is the primary use case, so no consensus for
making setting the label a SHOULD. I don't think that TURN is special
in this regard.

> 
>>
>>
>> (The same is not true of the DSCP. There's every reason that should
>> be copied as-is. But I expect you know that.)
> 
> The proposed DSCP text says that the DSCP should be copied unless the
> relay believes, through unspecified means, that another value for the
> outgoing DSCP is appropriate. However, if the incoming value cannot be
> read, then set the outgoing value to Best Effort (again, unless the
> relay believes another value is more appropriate).

OK, although I would be a bit more specific: unless the relay
includes a diffserv classifier (and associated policy). That's
how it obtains such a 'belief' in the diffserv model.

> Believe me, the v4 cases have had much discussion (including the
> involvement of three current ADs).

I don't doubt it ;-)

   Brian
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 22:56:51 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D4C8F28C53E;
	Tue,  6 May 2008 22:56:50 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CBF0028C55B
	for <behave@core3.amsl.com>; Tue,  6 May 2008 22:56:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.781
X-Spam-Level: 
X-Spam-Status: No, score=-5.781 tagged_above=-999 required=5 tests=[AWL=0.518, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 10gc25ilrhgp for <behave@core3.amsl.com>;
	Tue,  6 May 2008 22:56:42 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id 82B0D28C55F
	for <behave@ietf.org>; Tue,  6 May 2008 22:56:21 -0700 (PDT)
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m475tgox015012; Wed, 7 May 2008 08:56:06 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 7 May 2008 08:56:05 +0300
Received: from esdhcp04061.research.nokia.com ([172.21.40.61]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 7 May 2008 08:56:05 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: behave@ietf.org
Date: Wed, 7 May 2008 08:57:22 +0300
User-Agent: KMail/1.9.9
References: <C446932B.6D11%hesham@elevatemobile.com>
	<1210083881.19601.22.camel@strat>
In-Reply-To: <1210083881.19601.22.camel@strat>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805070857.23456.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 07 May 2008 05:56:05.0573 (UTC)
	FILETIME=[09CCB750:01C8B007]
X-Nokia-AV: Clean
Cc: v6ops <v6ops@ops.ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>,
	ext Sebastien Roy <Sebastien.Roy@sun.com>,
	Philip Matthews <philip_matthews@magma.ca>,
	Hesham Soliman <hesham@elevatemobile.com>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Le Tuesday 06 May 2008 17:24:41 ext Sebastien Roy, vous avez =E9crit=A0:
> I'm aware of IPv4 deployments using NAT in order to easily implement
> transparent proxies.  Specifically, they use a NAT to transparently
> redirect packets to a local address and port, and a user-space proxy
> receives those packets, processes them, and retransmits them.  The use
> of NAT here has nothing to do with preserving address space, but as a
> hack to transparently redirect all packets to a local address and port
> in order to have a local application receive them.

That's "destination" NAT, i.e. translating the passive-side address of the =

network flow. AFAIK, this is only done when it's "known to work", usually i=
n =

front of a plain TCP connection-based service (HTTP, SMTP, you-name-it...).

That's quite different from the more common "source" NAT. In any case, TURN=
 is =

meant to address the non-BEHAVE-compliant "source" NATs. Time will tell, bu=
t =

these will hopefully not be very common in IPv6.

-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May  6 23:46:55 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3642E3A70F1;
	Tue,  6 May 2008 23:46:55 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6BBD83A70AE
	for <behave@core3.amsl.com>; Tue,  6 May 2008 23:46:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.583
X-Spam-Level: 
X-Spam-Status: No, score=-1.583 tagged_above=-999 required=5 tests=[AWL=0.366, 
	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 fb6K1F454gdY for <behave@core3.amsl.com>;
	Tue,  6 May 2008 23:46:52 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id 301AC3A70CB
	for <behave@ietf.org>; Tue,  6 May 2008 23:46:27 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 5A4203EA0E0;
	Wed,  7 May 2008 08:46:24 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 40B243EA0DD;
	Wed,  7 May 2008 08:46:22 +0200 (CEST)
Message-ID: <48215043.10803@free.fr>
Date: Wed, 07 May 2008 08:46:27 +0200
From: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <C4469832.6D1C%hesham@elevatemobile.com>
	<7D18EE08-2516-46F8-B9B4-1CE1A4E48459@magma.ca>
	<482108DF.4020800@gmail.com>
In-Reply-To: <482108DF.4020800@gmail.com>
Cc: Behave WG <behave@ietf.org>, v6ops <v6ops@ops.ietf.org>,
	=?UTF-8?B?UsOpbWkgRGVuaXMtQ291?=@core3.amsl.com,
	Philip Matthews <philip_matthews@magma.ca>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

QnJpYW4gRSBDYXJwZW50ZXIgd3JvdGUgOgo+IFNvLCBJJ2Qgc2F5IHRoYXQgdGhlIGRlZmF1bHQg
YmVoYXZpb3IgZm9yIGEgcmVsYXllZCBwYWNrZXQgc2hvdWxkIGJlCj4gIkFzc2lnbiAwIiwgYW5k
ICJBc3NpZ24gYSBuZXcgZmxvdyBsYWJlbCBhY2NvcmRpbmcgdG8gUkZDMzY5NyIgc2hvdWxkCj4g
YmUgb3B0aW9uYWwgKGp1c3QgYXMgdGhlIHdob2xlIG9mIFJGQzM2OTcgaXMgb3B0aW9uYWwpLiBB
bmQgdGhpcyBpcwo+IGVudGlyZWx5IGluZGVwZW5kZW50IG9mIHdoZXRoZXIgb3Igbm90IHRoZSBp
bmNvbWluZyBwYWNrZXQgaGFzIGEKPiBub24temVybyBmbG93IGxhYmVsLgoKVGhpcyBpcyBJTVUg
dGhlIHJpZ2h0IGJlaGF2aW9yCgoKSSBoYWQgZXNzZW50aWFsbHkgdGhlIHNhbWUgY29uY2x1c2lv
biAoc2VlIGZvciBleGFtcGxlCmh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9i
ZWhhdmUvY3VycmVudC9tc2cwMzc4OS5odG1sKS4KCkEgc2xpZ2h0bHkgZGlmZmVyZW50IHdvcmRp
bmcgY291bGQgaG93ZXZlciwgSU1PLCBiZSBwcmVmZXJhYmxlLgoiQXNzaWduIDAiIGFuZCAiUkZD
MzY5NyIgc2hvdWxkIGJlIHBsYWNlZCBvbiBhbiBlcXVhbCBmb290aW5nLCBubyBvbmUKYmVpbmcg
bW9yZSAiZGVmYXVsdCIgdGhhbiB0aGUgb3RoZXI6IGEgc291cmNlIG1heSBoYXZlIGVpdGhlciBi
ZWhhdmlvcjsKYSBkZXN0aW5hdGlvbiBvciBhbiBpbnRlcm1lZGlhdGUgbm9kZSBtYXkgbm90IGFz
c3VtZSBhbnkgb2YgdGhlIHR3bwpiZWhhdmlvcnMgaW4gcGFydGljdWxhci4KCgpSw6ltaQoKX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KQmVoYXZlIG1haWxp
bmcgbGlzdApCZWhhdmVAaWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9iZWhhdmUK


From behave-bounces@ietf.org  Wed May  7 01:08:31 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E29643A691B;
	Wed,  7 May 2008 01:08:31 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 555A33A682A
	for <behave@core3.amsl.com>; Wed,  7 May 2008 01:08:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.899
X-Spam-Level: 
X-Spam-Status: No, score=-5.899 tagged_above=-999 required=5
	tests=[AWL=-0.250, BAYES_00=-2.599, HELO_EQ_SE=0.35,
	J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
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 wHeyjxs5STuM for <behave@core3.amsl.com>;
	Wed,  7 May 2008 01:08:29 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id F118F3A67AD
	for <behave@ietf.org>; Wed,  7 May 2008 01:08:28 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	78A7120825; Wed,  7 May 2008 10:08:23 +0200 (CEST)
X-AuditID: c1b4fb3c-af09dbb00000193b-d0-482163771764
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	5288820C5A; Wed,  7 May 2008 10:08:23 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 May 2008 10:08:23 +0200
Received: from [131.160.37.21] ([131.160.37.21]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 May 2008 10:08:22 +0200
Message-ID: <48216376.7010305@ericsson.com>
Date: Wed, 07 May 2008 11:08:22 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <47F3FA30.2060403@acm.org>	<200805021504.26754.remi.denis-courmont@nokia.com>	<C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>	<200805050923.50429.remi.denis-courmont@nokia.com>
	<E1324FFA-4E2F-40DA-A14B-96D84AA273D3@magma.ca>
In-Reply-To: <E1324FFA-4E2F-40DA-A14B-96D84AA273D3@magma.ca>
X-OriginalArrivalTime: 07 May 2008 08:08:22.0870 (UTC)
	FILETIME=[84CC1F60:01C8B019]
X-Brightmail-Tracker: AAAAAA==
Cc: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?= <Remi.Denis-Courmont@nokia.com>,
	Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] IPv4/IPv6 relayed address allocation
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi Philip,

once we agree on how to divide the text between both specs, we can =

copy/paste between both specs until we get the structure and the =

contents in both specs right.

Regarding your question (option 1 vs. option 2), we need to think of =

which implementations will only implement the base TURN spec (as opposed =

to implementing both the base TURN spec and TURN-ipv6). An IPv4-only =

TURN server does not need to worry about address families. So, it should =

be enough for that server to implement base TURN without worrying about =

REQUESTED-ADDRESS-TYPE attributes. On the other hand, an IPv4-IPv6 TURN =

server would need to implement both specs.

So, I guess this argues for keeping the definition of the =

REQUESTED-ADDRESS-TYPE in the TURN-ipv6 spec and moving the text on =

IP4-IPv6 relaying from base TURN to TURN-ipv6. I would leave the =

IPv6-IPv6 stuff, if we finally decide to keep it, on the base TURN spec. =

This way, the base TURN spec would deal with relaying within a single =

address family while TURN-ipv6 would deal with IPv4-IPv6 relaying.

Cheers,

Gonzalo


Philip Matthews wrote:
> Folks:
> =

> This discussion is prompted by discussions right now in v6OPS around  =

> devices to translate between IPv6 and IPv4. So, for example, a client  =

> might send an Allocate request over IPv6, but the request might arrive  =

> at the TURN server over IPv4 (or vica-versa).
> =

> At present (in TURN-07), the TURN server allocates a relayed-transport- =

> address in the same address family (IPv4 or IPv6) as the family over  =

> which the Allocate request arrived. R=E9mi Denis-Courmont dislikes the  =

> fact that the client might get back an address family different from  =

> the one it "expected".
> =

> So I am looking for comments on one of two options going forward:
> =

> 1) [Currently in TURN-07] The address family (IPv4 vs IPv6) of a  =

> relayed-transport-address is the same as the address family over which  =

> the Allocate request arrived.
> =

> 2) [Proposal] TURN-08 will define the REQUESTED-ADDRESS-TYPE attribute  =

> (which is currently defined in draft-ietf-behave-turn-ipv6) which  =

> allows the client to request a particular address family for the  =

> relayed-transport-address. However, TURN-08 will reject the Allocate  =

> request if the requested address family is not the same as the address  =

> family over which the Allocate request arrived.
> =

> Under either option, TURN-08 will still require that two address  =

> families match. That is, TURN-08 will NOT specify IPv4 to IPv6  =

> relaying (because the details for doing this are non-trivial). An  =

> extension for relaying between address families will be left for draft- =

> ietf-behave-turn-ipv6.
> =

> So the difference is that, when in cases where option (1) would cause  =

> the client to get back an address family different than the one it  =

> "expected", option (2) will cause the Allocate request to be rejected.
> =

> I am quite happy with option (2).
> =

> Comments?
> =

> - Philip
> =

> =

> =

> =

> =

> On Mon, 5-May-08, at 02:23 , R=E9mi Denis-Courmont wrote:
>> Le Friday 02 May 2008 22:16:02 ext Philip Matthews, vous avez =E9crit :
>>> This is being fixed.
>>> TURN-08 will say that a server should copy the flow label, and if  =

>>> this
>>> cannot be done, then treat the packets to/from each peer as a  =

>>> separate
>>> flow with separate labels. This is all part of the new concept of a
>>> Preserving allocation (what I called a "Fully-Compliant allocation"  =

>>> in
>>> Philly) that I am in the process of adding right now.
>> I myself am not sure what the "proper" handling of the flow infos  =

>> is. If
>> anyone knows, that would be some 6man and/or v6ops people (not  =

>> including me).
>> Flow infos is not just like DSCP. Reflecting this, the Linux(- =

>> specific) API
>> for flow infos is completely different from that of DSCP and TTL...
>>
>>>> From a more general perspective, having the application-layer
>>>> semantics depend on the IP protocol version of the client looks
>>>> like very bad engineering to me. Imagine DNS servers would return
>>>> different results depending if you query them over v4 or v6!?!
>>> Don't forget that you get exactly this behavior with a STUN server.
>> Or with any service that gives you your IP address from the  =

>> perspective of the
>> server. This seems quite specific, and not very relevant here.
>>
>> (...)
>>> What if the base spec included the REQUESTED-ADDRESS-TYPE attribute
>>> with the restriction that the address type given in the REQUESTED-
>>> ADDRESS-TYPE attribute MUST match the address type in the 5-tuple or
>>> the Allocate request is rejected ?
>>> TURN-IPv6 would then lift this restriction.
>>>
>>> Would this make things better?
>> I think so, yeah.
>>
>> -- =

>> R=E9mi Denis-Courmont
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>>
> =

> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> =


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May  7 05:31:25 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 004E93A6B63;
	Wed,  7 May 2008 05:31:25 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1BDFD3A6A21
	for <behave@core3.amsl.com>; Wed,  7 May 2008 05:31:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.197
X-Spam-Level: 
X-Spam-Status: No, score=-2.197 tagged_above=-999 required=5 tests=[AWL=0.402, 
	BAYES_00=-2.599]
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 4SIbVCHeCEC3 for <behave@core3.amsl.com>;
	Wed,  7 May 2008 05:31:21 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2])
	by core3.amsl.com (Postfix) with ESMTP id B131F3A6B6F
	for <behave@ietf.org>; Wed,  7 May 2008 05:31:21 -0700 (PDT)
Received: by jazz.viagenie.ca (Postfix, from userid 8)
	id 279B129E1499; Wed,  7 May 2008 08:30:49 -0400 (EDT)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67])
	by jazz.viagenie.ca (Postfix) with ESMTP id D069929E1433
	for <behave@ietf.org>; Wed,  7 May 2008 08:30:48 -0400 (EDT)
From: Simon Perreault <simon.perreault@viagenie.ca>
Organization: =?iso-8859-1?q?Viag=E9nie?=
To: Behave WG <behave@ietf.org>
Date: Wed, 7 May 2008 08:30:48 -0400
User-Agent: KMail/1.9.9
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805070830.48630.simon.perreault@viagenie.ca>
Subject: [BEHAVE] Announcing Numb, a new STUN/TURN server implementation
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hello all,

There is a new STUN/TURN server implementation:

	http://numb.viagenie.ca

Access is free. You just need to create an account via the web form. Long-term 
authentication is used.

We have implemented TURNv6 but our IPv6 block doesn't have global reachability 
and so IPv6 has been turned off for now. If there are people interested in 
that, please do tell us so that we know on which feature to work first.

This is the first public announcement so expect rough corners.

Comments? Questions? Suggestions? Inquiries? Insults?

Simon
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May  7 12:26:09 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 30F8F3A6C8E;
	Wed,  7 May 2008 12:26:09 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9CA6A3A6C8E
	for <behave@core3.amsl.com>; Wed,  7 May 2008 12:26:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.82
X-Spam-Level: 
X-Spam-Status: No, score=-1.82 tagged_above=-999 required=5 tests=[AWL=0.179, 
	BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 2WW17eQHrvfw for <behave@core3.amsl.com>;
	Wed,  7 May 2008 12:26:06 -0700 (PDT)
Received: from mail-05.primus.ca (mail9.primus.ca [216.254.141.176])
	by core3.amsl.com (Postfix) with ESMTP id 680A53A69D2
	for <behave@ietf.org>; Wed,  7 May 2008 12:26:06 -0700 (PDT)
Received: from [216.13.42.68] (helo=[10.10.80.124])
	by mail-05.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1JtpFy-0008JX-0p; Wed, 07 May 2008 15:24:50 -0400
Message-Id: <E4AC039B-910B-491B-9ACE-DDA1FAE26D70@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
In-Reply-To: <48216376.7010305@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 7 May 2008 15:26:02 -0400
References: <47F3FA30.2060403@acm.org>	<200805021504.26754.remi.denis-courmont@nokia.com>	<C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>	<200805050923.50429.remi.denis-courmont@nokia.com>
	<E1324FFA-4E2F-40DA-A14B-96D84AA273D3@magma.ca>
	<48216376.7010305@ericsson.com>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.10.80.124]) [216.13.42.68]
Cc: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?= <Remi.Denis-Courmont@nokia.com>,
	Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] IPv4/IPv6 relayed address allocation
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Wed, 7-May-08, at 04:08 , Gonzalo Camarillo wrote:
> Hi Philip,
>
> once we agree on how to divide the text between both specs, we can  =

> copy/paste between both specs until we get the structure and the  =

> contents in both specs right.
Yes.

>
>
> Regarding your question (option 1 vs. option 2), we need to think of  =

> which implementations will only implement the base TURN spec (as  =

> opposed to implementing both the base TURN spec and TURN-ipv6). An  =

> IPv4-only TURN server does not need to worry about address families.  =

> So, it should be enough for that server to implement base TURN  =

> without worrying about REQUESTED-ADDRESS-TYPE attributes.

If the base TURN spec does not include the REQUESTED-ADDRESS-TYPE  =

attribute, then we have to go with option (1). However, Remi prefers  =

option (2).


> On the other hand, an IPv4-IPv6 TURN server would need to implement  =

> both specs.

Yes.

>
>
> So, I guess this argues for keeping the definition of the REQUESTED- =

> ADDRESS-TYPE in the TURN-ipv6 spec and moving the text on IP4-IPv6  =

> relaying from base TURN to TURN-ipv6.

There is no text of IPv4-IPv6 relaying in the base TURN spec, and I am  =

trying hard not to add any.

> I would leave the IPv6-IPv6 stuff, if we finally decide to keep it,  =

> on the base TURN spec.

Yes.

> This way, the base TURN spec would deal with relaying within a  =

> single address family while TURN-ipv6 would deal with IPv4-IPv6  =

> relaying.

Yes. This is the way things are now, I am am trying hard to stick with  =

this.

>
>
> Cheers,
>
> Gonzalo
>
>
> Philip Matthews wrote:
>> Folks:
>> This discussion is prompted by discussions right now in v6OPS  =

>> around  devices to translate between IPv6 and IPv4. So, for  =

>> example, a client  might send an Allocate request over IPv6, but  =

>> the request might arrive  at the TURN server over IPv4 (or vica- =

>> versa).
>> At present (in TURN-07), the TURN server allocates a relayed- =

>> transport- address in the same address family (IPv4 or IPv6) as the  =

>> family over  which the Allocate request arrived. R=E9mi Denis- =

>> Courmont dislikes the  fact that the client might get back an  =

>> address family different from  the one it "expected".
>> So I am looking for comments on one of two options going forward:
>> 1) [Currently in TURN-07] The address family (IPv4 vs IPv6) of a   =

>> relayed-transport-address is the same as the address family over  =

>> which  the Allocate request arrived.
>> 2) [Proposal] TURN-08 will define the REQUESTED-ADDRESS-TYPE  =

>> attribute  (which is currently defined in draft-ietf-behave-turn- =

>> ipv6) which  allows the client to request a particular address  =

>> family for the  relayed-transport-address. However, TURN-08 will  =

>> reject the Allocate  request if the requested address family is not  =

>> the same as the address  family over which the Allocate request  =

>> arrived.
>> Under either option, TURN-08 will still require that two address   =

>> families match. That is, TURN-08 will NOT specify IPv4 to IPv6   =

>> relaying (because the details for doing this are non-trivial). An   =

>> extension for relaying between address families will be left for  =

>> draft- ietf-behave-turn-ipv6.
>> So the difference is that, when in cases where option (1) would  =

>> cause  the client to get back an address family different than the  =

>> one it  "expected", option (2) will cause the Allocate request to  =

>> be rejected.
>> I am quite happy with option (2).
>> Comments?
>> - Philip
>> On Mon, 5-May-08, at 02:23 , R=E9mi Denis-Courmont wrote:
>>> Le Friday 02 May 2008 22:16:02 ext Philip Matthews, vous avez  =

>>> =E9crit :
>>>> This is being fixed.
>>>> TURN-08 will say that a server should copy the flow label, and  =

>>>> if  this
>>>> cannot be done, then treat the packets to/from each peer as a   =

>>>> separate
>>>> flow with separate labels. This is all part of the new concept of a
>>>> Preserving allocation (what I called a "Fully-Compliant  =

>>>> allocation"  in
>>>> Philly) that I am in the process of adding right now.
>>> I myself am not sure what the "proper" handling of the flow infos   =

>>> is. If
>>> anyone knows, that would be some 6man and/or v6ops people (not   =

>>> including me).
>>> Flow infos is not just like DSCP. Reflecting this, the Linux(-  =

>>> specific) API
>>> for flow infos is completely different from that of DSCP and TTL...
>>>
>>>>> From a more general perspective, having the application-layer
>>>>> semantics depend on the IP protocol version of the client looks
>>>>> like very bad engineering to me. Imagine DNS servers would return
>>>>> different results depending if you query them over v4 or v6!?!
>>>> Don't forget that you get exactly this behavior with a STUN server.
>>> Or with any service that gives you your IP address from the   =

>>> perspective of the
>>> server. This seems quite specific, and not very relevant here.
>>>
>>> (...)
>>>> What if the base spec included the REQUESTED-ADDRESS-TYPE attribute
>>>> with the restriction that the address type given in the REQUESTED-
>>>> ADDRESS-TYPE attribute MUST match the address type in the 5-tuple  =

>>>> or
>>>> the Allocate request is rejected ?
>>>> TURN-IPv6 would then lift this restriction.
>>>>
>>>> Would this make things better?
>>> I think so, yeah.
>>>
>>> -- =

>>> R=E9mi Denis-Courmont
>>> _______________________________________________
>>> Behave mailing list
>>> Behave@ietf.org
>>> https://www.ietf.org/mailman/listinfo/behave
>>>
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>
>

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May  7 12:44:49 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 941BD3A6B2E;
	Wed,  7 May 2008 12:44:49 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E34CF3A6B2E
	for <behave@core3.amsl.com>; Wed,  7 May 2008 12:44:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 sSComrI6h-zC for <behave@core3.amsl.com>;
	Wed,  7 May 2008 12:44:48 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 2DE933A6D4E
	for <behave@ietf.org>; Wed,  7 May 2008 12:44:48 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	48368204F0; Wed,  7 May 2008 21:44:44 +0200 (CEST)
X-AuditID: c1b4fb3c-ac898bb00000193b-c5-482206acb5f9
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	29492204D4; Wed,  7 May 2008 21:44:44 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 May 2008 21:44:43 +0200
Received: from [153.88.14.44] ([153.88.14.44]) by esealmw128.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 May 2008 21:44:43 +0200
Message-ID: <482206A7.6050100@ericsson.com>
Date: Wed, 07 May 2008 22:44:39 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <47F3FA30.2060403@acm.org>	<200805021504.26754.remi.denis-courmont@nokia.com>	<C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>	<200805050923.50429.remi.denis-courmont@nokia.com>
	<E1324FFA-4E2F-40DA-A14B-96D84AA273D3@magma.ca>
	<48216376.7010305@ericsson.com>
	<E4AC039B-910B-491B-9ACE-DDA1FAE26D70@magma.ca>
In-Reply-To: <E4AC039B-910B-491B-9ACE-DDA1FAE26D70@magma.ca>
X-OriginalArrivalTime: 07 May 2008 19:44:43.0803 (UTC)
	FILETIME=[CC2C8EB0:01C8B07A]
X-Brightmail-Tracker: AAAAAA==
Cc: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?= <Remi.Denis-Courmont@nokia.com>,
	Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] IPv4/IPv6 relayed address allocation
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi,

> If the base TURN spec does not include the REQUESTED-ADDRESS-TYPE 
> attribute, then we have to go with option (1). However, Remi prefers 
> option (2).

but... what is the advantage of going with option 2?

Cheers,

Gonzalo

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May  7 13:15:48 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DDCBF3A6A5D;
	Wed,  7 May 2008 13:15:48 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 12AC63A69FF
	for <behave@core3.amsl.com>; Wed,  7 May 2008 13:15:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.143
X-Spam-Level: 
X-Spam-Status: No, score=-2.143 tagged_above=-999 required=5 tests=[AWL=0.456, 
	BAYES_00=-2.599]
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 iY43Nlh2ZLAX for <behave@core3.amsl.com>;
	Wed,  7 May 2008 13:15:43 -0700 (PDT)
Received: from mail-01.primus.ca (mail9.primus.ca [216.254.141.176])
	by core3.amsl.com (Postfix) with ESMTP id 3418E3A680C
	for <behave@ietf.org>; Wed,  7 May 2008 13:15:43 -0700 (PDT)
Received: from [216.13.42.68] (helo=[10.10.80.124])
	by mail-01.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1Jtq3A-000118-0a; Wed, 07 May 2008 16:15:40 -0400
Message-Id: <F47F4151-819E-43DA-AF54-2DCCDDCE32AD@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
In-Reply-To: <482206A7.6050100@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 7 May 2008 16:15:39 -0400
References: <47F3FA30.2060403@acm.org>	<200805021504.26754.remi.denis-courmont@nokia.com>	<C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>	<200805050923.50429.remi.denis-courmont@nokia.com>
	<E1324FFA-4E2F-40DA-A14B-96D84AA273D3@magma.ca>
	<48216376.7010305@ericsson.com>
	<E4AC039B-910B-491B-9ACE-DDA1FAE26D70@magma.ca>
	<482206A7.6050100@ericsson.com>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.10.80.124]) [216.13.42.68]
Cc: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?= <Remi.Denis-Courmont@nokia.com>,
	Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] IPv4/IPv6 relayed address allocation
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Wed, 7-May-08, at 15:44 , Gonzalo Camarillo wrote:
> Hi,
>
>> If the base TURN spec does not include the REQUESTED-ADDRESS-TYPE  
>> attribute, then we have to go with option (1). However, Remi  
>> prefers option (2).
>
> but... what is the advantage of going with option 2?

Under option (1), a client sending an Allocate request over IPv4 might  
get back an IPv6 relayed-transport-address, if the Allocate request  
passed through a v4-to-v6 translator (as is currently being considered  
in v6OPS). If the client is unable to handle this, it must delete the  
allocation.

Under option (2), a client sending an Allocation request over IPv4 can  
explicitly say that it wants an IPv4 relayed-transport-address. Thus,  
if the Allocate request passes through a v4-to-v6 translator, the  
server will detect that the request arrived over v6 but was for a v4  
relayed-transport-address, and thus reject the request.

- Philip



_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May  7 13:23:31 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EDBD33A6E6C;
	Wed,  7 May 2008 13:23:30 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 736DC3A6E64
	for <behave@core3.amsl.com>; Wed,  7 May 2008 13:23:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.043
X-Spam-Level: 
X-Spam-Status: No, score=-2.043 tagged_above=-999 required=5 tests=[AWL=0.256, 
	BAYES_00=-2.599, 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 JaLfN6npDkVz for <behave@core3.amsl.com>;
	Wed,  7 May 2008 13:23:28 -0700 (PDT)
Received: from mail-09.primus.ca (mail9.primus.ca [216.254.141.176])
	by core3.amsl.com (Postfix) with ESMTP id BEAAB3A6B47
	for <behave@ietf.org>; Wed,  7 May 2008 13:23:28 -0700 (PDT)
Received: from [216.13.42.68] (helo=[10.10.80.124])
	by mail-09.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1JtqAa-0002ME-1m; Wed, 07 May 2008 16:23:20 -0400
Message-Id: <8BF598CE-7721-4453-9C58-B1B29BFC5BBE@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <48215043.10803@free.fr>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 7 May 2008 16:23:18 -0400
References: <C4469832.6D1C%hesham@elevatemobile.com>
	<7D18EE08-2516-46F8-B9B4-1CE1A4E48459@magma.ca>
	<482108DF.4020800@gmail.com> <48215043.10803@free.fr>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.10.80.124]) [216.13.42.68]
Cc: v6ops <v6ops@ops.ietf.org>, Behave WG <behave@ietf.org>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [BEHAVE] IPv6 Flow Label
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Wed, 7-May-08, at 02:46 , R=E9mi Despr=E9s wrote:
> Brian E Carpenter wrote :
>> So, I'd say that the default behavior for a relayed packet should be
>> "Assign 0", and "Assign a new flow label according to RFC3697" should
>> be optional (just as the whole of RFC3697 is optional). And this is
>> entirely independent of whether or not the incoming packet has a
>> non-zero flow label.
>
> This is IMU the right behavior
>
>
> I had essentially the same conclusion (see for example
> http://www.ietf.org/mail-archive/web/behave/current/msg03789.html).
>
> A slightly different wording could however, IMO, be preferable.
> "Assign 0" and "RFC3697" should be placed on an equal footing, no one
> being more "default" than the other: a source may have either  =

> behavior;
> a destination or an intermediate node may not assume any of the two
> behaviors in particular.

If no one has any objections, I will adopt this behavior.

- Philip
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May  7 14:04:59 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3AC1528C5A2;
	Wed,  7 May 2008 14:04:59 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E688228C666
	for <behave@core3.amsl.com>; Wed,  7 May 2008 14:04:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 SxS8CCKCLvNu for <behave@core3.amsl.com>;
	Wed,  7 May 2008 14:04:40 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91])
	by core3.amsl.com (Postfix) with ESMTP id CF8FD28C6CE
	for <behave@ietf.org>; Wed,  7 May 2008 14:04:40 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001)
	id 5D10AD9D4248; Wed,  7 May 2008 21:04:38 +0000 (UTC)
Received: from [192.168.1.3] (c-67-161-24-129.hsd1.ca.comcast.net
	[67.161.24.129])
	by server.implementers.org (Postfix) with ESMTP id E6B40D9D4246;
	Wed,  7 May 2008 21:04:35 +0000 (UTC)
Message-ID: <48221963.6060804@acm.org>
Date: Wed, 07 May 2008 14:04:35 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla-Thunderbird 2.0.0.12 (X11/20080420)
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@cisco.com>
References: <47C072CD.3050003@cisco.com> <47C86B94.3040708@acm.org>
In-Reply-To: <47C86B94.3040708@acm.org>
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] updated rfc3489bis
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I never received any answer to this questions.  I am especially
interested in an answer to the second question.

Thanks.

Marc Petit-Huguenin wrote:
> I just did a complete review of my code against rfc3489bis-15 and have
> some questions:
> 
> - Section 7.1 "All STUN requests and responses sent over UDP SHOULD be
> less than the path MTU":  Shouldn't indications be added to this list?
> 
> - Section 9:  Now that there will be a default port defines for STUN
> over TLS, shouldn't the last sentence of the last paragraph removed?
> 
> - Section 15.8:  Shouln't the section says that the text must be a UTF-8
> encoded sequence, like for USERNAME and REALM?
> 
> Thanks.
> 
> Jonathan Rosenberg wrote:
>> Just submitted:
>> http://www.ietf.org/internet-drafts/draft-ietf-behave-rfc3489bis-15.txt
>>
>> Changes based on recent comments:
>>
>> * MTU limit from MUST to SHOULD, with an explanation of why (namely, 
>> behavior discovery)
>>
>> * added clarification on MD5 being the 16 byte output and not ascii 
>> armored, also including an example. This was some text that was in 
>> 3489bis till -05 and got lost in the big rewrite to -06.
>>
>> * clarified that the MTU limit applies to the entire datagram and not 
>> just the STUN message
>>
>> -Jonathan R.
> 
> 


-- 
Marc Petit-Huguenin           [                                 ]
Home: marc@petit-huguenin.org [RFC1855-compliant space for rent ]
Work: marc@8x8.com            [                                 ]
[                                                               ]
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May  7 14:43:54 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5AE4428C6DB;
	Wed,  7 May 2008 14:43:54 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4651B28C6B2
	for <behave@core3.amsl.com>; Wed,  7 May 2008 14:43:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 5XtiHeByWkb4 for <behave@core3.amsl.com>;
	Wed,  7 May 2008 14:43:48 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91])
	by core3.amsl.com (Postfix) with ESMTP id 0710928C6E7
	for <behave@ietf.org>; Wed,  7 May 2008 14:43:47 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001)
	id 672B1D9D424A; Wed,  7 May 2008 21:43:45 +0000 (UTC)
Received: from [192.168.1.3] (c-67-161-24-129.hsd1.ca.comcast.net
	[67.161.24.129])
	by server.implementers.org (Postfix) with ESMTP id 01D4CD9D4246
	for <behave@ietf.org>; Wed,  7 May 2008 21:43:42 +0000 (UTC)
Message-ID: <4822228E.3080401@acm.org>
Date: Wed, 07 May 2008 14:43:42 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla-Thunderbird 2.0.0.12 (X11/20080420)
MIME-Version: 1.0
To: Behave WG <behave@ietf.org>
Subject: [BEHAVE] TURN and TURNS URI and resolution mechanism (-01)
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I just submitted an updated I-D:

http://www.ietf.org/internet-drafts/draft-petithuguenin-behave-turn-uri-01.txt

Comments appreciated.

Thanks.


Changelog:

   o  Added <transport-ext> in the ABNF.
   o  Use the <rulename> and "literal" usages for free-form text defined
      by [RFC5234].
   o  Fixed various typos.
   o  Put the rule to convert <scheme> and <transport> to a TURN
      transport in a separate paragraph.
   o  Modified the SRV usage to be in line with RFC 2782.
   o  Clarified that the NAPTR protocol ranking must be used before the
      application ranking.
   o  Added an example.
   o  Added release notes.

-- 
Marc Petit-Huguenin           [                                 ]
Home: marc@petit-huguenin.org [RFC1855-compliant space for rent ]
Work: marc@8x8.com            [                                 ]
[                                                               ]
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May  7 20:55:58 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 47ACD28C7BE;
	Wed,  7 May 2008 20:55:58 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B8D4E3A6B01
	for <behave@core3.amsl.com>; Wed,  7 May 2008 20:55:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 5TUha4W1WsTs for <behave@core3.amsl.com>;
	Wed,  7 May 2008 20:55:56 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id A428C3A6C93
	for <behave@ietf.org>; Wed,  7 May 2008 20:55:55 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	814D72081D; Thu,  8 May 2008 05:55:46 +0200 (CEST)
X-AuditID: c1b4fb3c-af89ebb00000193b-d7-482279c2c804
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	60733203CA; Thu,  8 May 2008 05:55:46 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 8 May 2008 05:55:46 +0200
Received: from [153.88.12.20] ([153.88.12.20]) by esealmw127.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 8 May 2008 05:55:45 +0200
Message-ID: <482279BE.5010805@ericsson.com>
Date: Thu, 08 May 2008 06:55:42 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <47F3FA30.2060403@acm.org>	<200805021504.26754.remi.denis-courmont@nokia.com>	<C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>	<200805050923.50429.remi.denis-courmont@nokia.com>
	<E1324FFA-4E2F-40DA-A14B-96D84AA273D3@magma.ca>
	<48216376.7010305@ericsson.com>
	<E4AC039B-910B-491B-9ACE-DDA1FAE26D70@magma.ca>
	<482206A7.6050100@ericsson.com>
	<F47F4151-819E-43DA-AF54-2DCCDDCE32AD@magma.ca>
In-Reply-To: <F47F4151-819E-43DA-AF54-2DCCDDCE32AD@magma.ca>
X-OriginalArrivalTime: 08 May 2008 03:55:45.0899 (UTC)
	FILETIME=[64F3A3B0:01C8B0BF]
X-Brightmail-Tracker: AAAAAA==
Cc: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?= <Remi.Denis-Courmont@nokia.com>,
	Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] IPv4/IPv6 relayed address allocation
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi,

I think we all agree this should be the behavior for clients and 
servers. However, if we move all the meat from TURN-IPv6 to base TURN 
(we already moved the address family definition a while ago), it may 
make sense to merge both specs. Specifying the IPv4-IPv6 mapping may not 
be trivial, but it's not a big deal either.

The bottom line is that we are discussing an issue related to document 
structure. We seem to agree on the actual protocol behavior.

Cheers,

Gonzalo


Philip Matthews wrote:
> 
> On Wed, 7-May-08, at 15:44 , Gonzalo Camarillo wrote:
>> Hi,
>>
>>> If the base TURN spec does not include the REQUESTED-ADDRESS-TYPE 
>>> attribute, then we have to go with option (1). However, Remi prefers 
>>> option (2).
>>
>> but... what is the advantage of going with option 2?
> 
> Under option (1), a client sending an Allocate request over IPv4 might 
> get back an IPv6 relayed-transport-address, if the Allocate request 
> passed through a v4-to-v6 translator (as is currently being considered 
> in v6OPS). If the client is unable to handle this, it must delete the 
> allocation.
> 
> Under option (2), a client sending an Allocation request over IPv4 can 
> explicitly say that it wants an IPv4 relayed-transport-address. Thus, if 
> the Allocate request passes through a v4-to-v6 translator, the server 
> will detect that the request arrived over v6 but was for a v4 
> relayed-transport-address, and thus reject the request.
> 
> - Philip
> 
> 
> 

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu May  8 14:13:39 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6D60B3A6E9A;
	Thu,  8 May 2008 14:13:39 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 06F9C3A6D18
	for <behave@core3.amsl.com>; Thu,  8 May 2008 14:13:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.219
X-Spam-Level: 
X-Spam-Status: No, score=-2.219 tagged_above=-999 required=5 tests=[AWL=0.380, 
	BAYES_00=-2.599]
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 okeOev1-HtI2 for <behave@core3.amsl.com>;
	Thu,  8 May 2008 14:13:37 -0700 (PDT)
Received: from mail-02.primus.ca (mail9.primus.ca [216.254.141.176])
	by core3.amsl.com (Postfix) with ESMTP id 290973A6E14
	for <behave@ietf.org>; Thu,  8 May 2008 14:13:37 -0700 (PDT)
Received: from [216.13.42.68] (helo=[10.10.80.124])
	by mail-02.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1JuDQk-0001bg-2u; Thu, 08 May 2008 17:13:35 -0400
Message-Id: <07BC5FEF-84DF-4B37-B826-91A3223187C1@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
In-Reply-To: <482279BE.5010805@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Thu, 8 May 2008 17:13:34 -0400
References: <47F3FA30.2060403@acm.org>	<200805021504.26754.remi.denis-courmont@nokia.com>	<C85C0297-A488-44FB-97EC-C3E4B25904F2@magma.ca>	<200805050923.50429.remi.denis-courmont@nokia.com>
	<E1324FFA-4E2F-40DA-A14B-96D84AA273D3@magma.ca>
	<48216376.7010305@ericsson.com>
	<E4AC039B-910B-491B-9ACE-DDA1FAE26D70@magma.ca>
	<482206A7.6050100@ericsson.com>
	<F47F4151-819E-43DA-AF54-2DCCDDCE32AD@magma.ca>
	<482279BE.5010805@ericsson.com>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.10.80.124]) [216.13.42.68]
Cc: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?= <Remi.Denis-Courmont@nokia.com>,
	Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] IPv4/IPv6 relayed address allocation
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I really haven't spent any time thinking about it, but I am assuming  
that the details of IPv4-to-IPv6 relaying will take a few pages to  
specify, and there will be some design decisions to discuss, which  
will take time. Because of this assumption, I am trying to push it out  
of the base TURN spec. But perhaps I am wrong. Perhaps you would take  
a look and let me know?

- Philip

On Wed, 7-May-08, at 23:55 , Gonzalo Camarillo wrote:
> Hi,
>
> I think we all agree this should be the behavior for clients and  
> servers. However, if we move all the meat from TURN-IPv6 to base  
> TURN (we already moved the address family definition a while ago),  
> it may make sense to merge both specs. Specifying the IPv4-IPv6  
> mapping may not be trivial, but it's not a big deal either.
>
> The bottom line is that we are discussing an issue related to  
> document structure. We seem to agree on the actual protocol behavior.
>
> Cheers,
>
> Gonzalo
>
>
> Philip Matthews wrote:
>> On Wed, 7-May-08, at 15:44 , Gonzalo Camarillo wrote:
>>> Hi,
>>>
>>>> If the base TURN spec does not include the REQUESTED-ADDRESS-TYPE  
>>>> attribute, then we have to go with option (1). However, Remi  
>>>> prefers option (2).
>>>
>>> but... what is the advantage of going with option 2?
>> Under option (1), a client sending an Allocate request over IPv4  
>> might get back an IPv6 relayed-transport-address, if the Allocate  
>> request passed through a v4-to-v6 translator (as is currently being  
>> considered in v6OPS). If the client is unable to handle this, it  
>> must delete the allocation.
>> Under option (2), a client sending an Allocation request over IPv4  
>> can explicitly say that it wants an IPv4 relayed-transport-address.  
>> Thus, if the Allocate request passes through a v4-to-v6 translator,  
>> the server will detect that the request arrived over v6 but was for  
>> a v4 relayed-transport-address, and thus reject the request.
>> - Philip
>
>

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May  9 16:03:23 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 132D63A67EF;
	Fri,  9 May 2008 16:03:23 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8BE403A67EF
	for <behave@core3.amsl.com>; Fri,  9 May 2008 16:03:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.12
X-Spam-Level: 
X-Spam-Status: No, score=-4.12 tagged_above=-999 required=5 tests=[AWL=1.564, 
	BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4,
	SARE_MILLIONSOF=0.315]
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 VMevxhe10xye for <behave@core3.amsl.com>;
	Fri,  9 May 2008 16:02:53 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [83.149.65.1])
	by core3.amsl.com (Postfix) with ESMTP id 1838C3A67A8
	for <behave@ietf.org>; Fri,  9 May 2008 16:02:39 -0700 (PDT)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]
	([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m49H191S080468
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO)
	for <behave@ietf.org>; Fri, 9 May 2008 19:01:09 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: behave@ietf.org
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Fri, 9 May 2008 19:01:10 +0200
X-Mailer: Apple Mail (2.919.2)
Subject: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi all,

After being deprecated about a year ago, NAT-PT (network address  
translation - protocol translation between IPv6 and IPv4) is again on  
the table after discussions in v6ops.

Now obviously it makes sense for a NAT-PT (let me call it NAT64 = a  
NAT that sits between IPv6 clients and IPv4 servers) to conform to the  
BEHAVE requirements. However... One of these requirements is that  
mappings are endpoint independent. So if I talk to www.google.com with  
source port 49152, I don't get to also talk to www.yahoo.com using  
source port 49152.

Unless I'm mistaken, this basically allows the setup of an outgoing  
session to be an implicit reservation of the source port for  
subsequent incoming sessions, so peer-to-peer applications can work  
through the NAT without the need for an explicit hole punching  
mechanism.

The trouble with this is that it limits the number of active mappings  
per public IPv4 in a NAT to ~64k per transport protocol. In today's  
world, that's probably not a big issue, as IPv4 addresses are still in  
relative plentiful supply. So if you want to NAT a million people,  
it's generally not a big deal if you need to get something like 5000  
IPv4 addresses to do that. However, in the future this can easily  
change. Today, big ISPs request and receive blocks of hundreds of  
thousands to millions of IPv4 addresses. In 3 - 5 years, the supply of  
IPv4 addresses will be depleted, and getting new IPv4 addresses in  
those numbers will no longer be possible. Obviously most of the  
existing ISPs already have large amounts of IPv4 address so those can  
repurpose their existing addresses.

The trouble will be with new ISPs that grow fast. For them, being  
limited to 64k mappings per IPv4 addresses may be a significant issue.  
I'm not sure how many users can be supported with 64k port numbers,  
but I'm pretty sure the answer isn't "so many that it will never be an  
issue".

A few data points: with a BitTorrent download gives me 80 TCP sessions  
in ESTABLISHED, 7 in FIN_WAIT1 and 2 in TIME_WAIT.

The sad part is that only VERY few mappings will ever actually see  
incoming sessions that benefit from the endpoint independent behavior:  
most sessions are for client-server protocols. To be more precise:  
most sessions are for HTTP, which eats up TCP sessions at an  
incredible rate, especially considering today's web design practices.  
A visit to washingtonpost.com creates 17 TCP sessions. Strangely,  
clicking on a link a bit later even more at 28. For microsoft.com it's  
13 and 13, wikipedia.org 8. Then my RSS app refreshed its feeds and  
generated 50 sessions. Three IMAP counts hover at around 8 continous  
sessions. The TIME_WAIT state is shorter than I thought it would be  
(on my Mac) so I'd say that HTTP sessions stick around for 30 seconds,  
60 seconds at most. Still, that means that someone who is clicking on  
a link every 30 seconds can easily use up 10 port numbers on a  
continuous basis.

What I'm hoping for is that it would be possible to tighten the  
requirements such that we get closer to reserving ports for  
applications that really need reserved ports and get to reuse ports  
for client-server applications so that a BEHAVE-compliant NAT can  
support a much larger user base with the same number of public IPv4  
addresses as these addresses start to run out.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sat May 10 13:20:52 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E35313A69DE;
	Sat, 10 May 2008 13:20:52 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC97A3A69DE
	for <behave@core3.amsl.com>; Sat, 10 May 2008 13:20:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 DbYrDo9gkAQh for <behave@core3.amsl.com>;
	Sat, 10 May 2008 13:20:49 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id E8DB43A699F
	for <behave@ietf.org>; Sat, 10 May 2008 13:20:49 -0700 (PDT)
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 10 May 2008 13:20:47 -0700
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4AKKl3m025471; 
	Sat, 10 May 2008 13:20:47 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-4.cisco.com (8.13.8/8.13.8) with ESMTP id m4AKKkON001520;
	Sat, 10 May 2008 20:20:46 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Iljitsch van Beijnum'" <iljitsch@muada.com>, <behave@ietf.org>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
Date: Sat, 10 May 2008 13:20:46 -0700
Message-ID: <081d01c8b2db$54fa9770$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: AciyKQu2FmU1bJh+R9uskpmwJdZ3XwAscvDw
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=612; t=1210450847; x=1211314847;
	c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Scalability=20of=20endpoint=
	20independent=20mapping |Sender:=20;
	bh=LI6UjL76no3S6mmkkoQOCGbh1pbASTWzc6ZEvRNZNgY=;
	b=VBp092QApowPO9sFMNDjQtMW6uJbLnkZrOHB2A9b3Buky4O9hap8SncyN3
	8wpTsO7przVS7ApVZmU1gWZ8TwY04x6C1kpeCzZHPPpTB7FE2I8TiyAGP+H/
	yHLh7LIl3trD6fNAE+B7QcLmQl28JckiDcjzYpYZaARMb5lXRwZgo=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

 
> What I'm hoping for is that it would be possible to tighten the  
> requirements such that we get closer to reserving ports for  
> applications that really need reserved ports and get to reuse ports  
> for client-server applications so that a BEHAVE-compliant NAT can  
> support a much larger user base with the same number of public IPv4  
> addresses as these addresses start to run out.

I don't understand the relationship between endpoint independent mapping
and the desire to free up the ports earlier.   I think you are only 
really asking for the NAT's TCP TIME_WAIT to be short.

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sun May 11 06:48:33 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A31E928C1B8;
	Sun, 11 May 2008 06:48:33 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 31CAD28C1B3
	for <behave@core3.amsl.com>; Sun, 11 May 2008 06:48:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.881
X-Spam-Level: 
X-Spam-Status: No, score=-3.881 tagged_above=-999 required=5
	tests=[AWL=-0.119, BAYES_00=-2.599, RCVD_BAD_ID=2.837,
	RCVD_IN_DNSWL_MED=-4]
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 HMoNF1FftMUs for <behave@core3.amsl.com>;
	Sun, 11 May 2008 06:48:30 -0700 (PDT)
Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.176.132])
	by core3.amsl.com (Postfix) with ESMTP id 06D7C28C199
	for <behave@ietf.org>; Sun, 11 May 2008 06:48:29 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local 
	(91.45.217.87.dynamic.jazztel.es [87.217.45.91])by smtp02.uc3m.es
	(Postfix)
	with ESMTP id C20A639C8FA;Sun, 11 May 2008 15:48:24 +0200 (CEST)
Message-ID: <4826F926.80404@it.uc3m.es>
Date: Sun, 11 May 2008 15:48:22 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com> 
	<081d01c8b2db$54fa9770$c3f0200a@cisco.com>
In-Reply-To: <081d01c8b2db$54fa9770$c3f0200a@cisco.com>
X-imss-version: 2.050
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-16.1608 TC:1F TRN:46 TV:5.5.1026(15902.007)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi Dan,

I think Iljitsch is talking about the same scenario

Consider a host H1 behind a nat which has a single public address T.
Suppose H1 initiates a communications towards an external host H2 at port w.

So, packet from H1 to the NAT has, source (H1,v) and destination (H2,w)

Now, when the packet is received at the NAT is creates a mapping
(H1,v) <->(T,u) and the nat sends the packet with source (T,u) and =

destination (H2,w)

Now, suppose another host H3 initiates a communication toward a node H4 =

at port j.
The packet from H3 towards the nat has source (H3,i) and estiantion (H4,j)

when the packet from He reaches the NAT, does the NAT can crate a =

mapping (H3,i)<->(T,u)

As i understand it, if we want to have endpoint independent mapping, =

this is not possible (this is so, because if later on H1 sends a packet =

towards H4 at port j, and we want to use the same mapping H1 is already =

using, we would end up in a conflict)

So, this basically means, that when the mapping for H1 (H1,v) <->(T,u) =

is created in the NAT, the transport address (T,u) cannot be used for =

ANY other rmapping (cause needs to be reserved for future potential =

communications of H1 with other destiantions.

So basically with endpoint independent mappings, each internally =

initiated communication eats up one port of the nat, reducing the number =

of simultaneous communications the NAT can handle. If we had address =

dependent mapping, the mapping takes into account the destination =

address also, so even if you may need more than one mapping when the =

same source transport address is used for two different external =

destinations, the NAT does not needs to reserve the port exclusively for =

the internal source address, so it is likely that a better usage of port =

range of the nat is achieved.


I mean, this is the price we need to pay for endpoint independence

Am i missing something?

Regards, marcelo




Dan Wing escribi=F3:
>  =

>   =

>> What I'm hoping for is that it would be possible to tighten the  =

>> requirements such that we get closer to reserving ports for  =

>> applications that really need reserved ports and get to reuse ports  =

>> for client-server applications so that a BEHAVE-compliant NAT can  =

>> support a much larger user base with the same number of public IPv4  =

>> addresses as these addresses start to run out.
>>     =

>
> I don't understand the relationship between endpoint independent mapping
> and the desire to free up the ports earlier.   I think you are only =

> really asking for the NAT's TCP TIME_WAIT to be short.
>
> -d
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
>   =


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sun May 11 08:34:40 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C0DF628C1DF;
	Sun, 11 May 2008 08:34:40 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E419D28C1DF
	for <behave@core3.amsl.com>; Sun, 11 May 2008 08:34:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5
	tests=[AWL=-0.087, BAYES_00=-2.599, HELO_EQ_FR=0.35,
	J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3, SARE_MILLIONSOF=0.315]
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 Hb4qysoLAJsW for <behave@core3.amsl.com>;
	Sun, 11 May 2008 08:34:37 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id D415C28C1DA
	for <behave@ietf.org>; Sun, 11 May 2008 08:34:36 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 777603EA0F8;
	Sun, 11 May 2008 17:34:32 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 21E5D3EA0D9;
	Sun, 11 May 2008 17:34:32 +0200 (CEST)
Message-ID: <48271209.8060903@free.fr>
Date: Sun, 11 May 2008 17:34:33 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
In-Reply-To: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping - a
	proposal
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I FULLY SUPPORT the requirement of "reserving ports for
applications that really need reserved ports and get to reuse ports
for client-server applications".

This becomes more and more necessary as address mappings are more and =

more performed, or envisaged, within ISP infrastructures.


For this, the approach I see is as follows:
- NATs SHOULD do end-point INDEPENDENT mapping (that of "full cone" =

NATs) when packets that initiate addresss-port mappings indicate that =

this is needed.
- They MAY do end-point DEPENDENT mappings in all other case.
- They SHOULD do end-point DEPENDENT mappings wherever sparing use of =

public IPv4 addresses is desirable.

IMU, packets that indicate in a standard way a need for end-point =

independent mapping are those sent to:
- STUN and TURN servers (server port 1990, 1991 or 1992)
- Teredo servers (server port 3544)


Would this satisfy what you had in mind?

Regards.

R=E9mi



Iljitsch van Beijnum wrote :
> Hi all,
> =

> After being deprecated about a year ago, NAT-PT (network address =

> translation - protocol translation between IPv6 and IPv4) is again on
>  the table after discussions in v6ops.
> =

> Now obviously it makes sense for a NAT-PT (let me call it NAT64 =3D a
>  NAT that sits between IPv6 clients and IPv4 servers) to conform to
> the BEHAVE requirements. However... One of these requirements is that
>  mappings are endpoint independent. So if I talk to www.google.com
> with source port 49152, I don't get to also talk to www.yahoo.com
> using source port 49152.
> =

> Unless I'm mistaken, this basically allows the setup of an outgoing
>  session to be an implicit reservation of the source port for =

> subsequent incoming sessions, so peer-to-peer applications can work
>  through the NAT without the need for an explicit hole punching =

> mechanism.
> =

> The trouble with this is that it limits the number of active mappings
>  per public IPv4 in a NAT to ~64k per transport protocol. In today's
>  world, that's probably not a big issue, as IPv4 addresses are still
> in relative plentiful supply. So if you want to NAT a million people,
>  it's generally not a big deal if you need to get something like 5000
>  IPv4 addresses to do that. However, in the future this can easily =

> change. Today, big ISPs request and receive blocks of hundreds of =

> thousands to millions of IPv4 addresses. In 3 - 5 years, the supply
> of IPv4 addresses will be depleted, and getting new IPv4 addresses in
>  those numbers will no longer be possible. Obviously most of the =

> existing ISPs already have large amounts of IPv4 address so those can
>  repurpose their existing addresses.
> =

> The trouble will be with new ISPs that grow fast. For them, being =

> limited to 64k mappings per IPv4 addresses may be a significant
> issue. I'm not sure how many users can be supported with 64k port
> numbers, but I'm pretty sure the answer isn't "so many that it will
> never be an issue".
> =

> A few data points: with a BitTorrent download gives me 80 TCP
> sessions in ESTABLISHED, 7 in FIN_WAIT1 and 2 in TIME_WAIT.
> =

> The sad part is that only VERY few mappings will ever actually see =

> incoming sessions that benefit from the endpoint independent
> behavior: most sessions are for client-server protocols. To be more
> precise: most sessions are for HTTP, which eats up TCP sessions at an
>  incredible rate, especially considering today's web design
> practices. A visit to washingtonpost.com creates 17 TCP sessions.
> Strangely, clicking on a link a bit later even more at 28. For
> microsoft.com it's 13 and 13, wikipedia.org 8. Then my RSS app
> refreshed its feeds and generated 50 sessions. Three IMAP counts
> hover at around 8 continous sessions. The TIME_WAIT state is shorter
> than I thought it would be (on my Mac) so I'd say that HTTP sessions
> stick around for 30 seconds, 60 seconds at most. Still, that means
> that someone who is clicking on a link every 30 seconds can easily
> use up 10 port numbers on a continuous basis.
> =

> What I'm hoping for is that it would be possible to tighten the =

> requirements such that we get closer to reserving ports for =

> applications that really need reserved ports and get to reuse ports
>  for client-server applications so that a BEHAVE-compliant NAT can =

> support a much larger user base with the same number of public IPv4
>  addresses as these addresses start to run out. =

> _______________________________________________ Behave mailing list =

> Behave@ietf.org https://www.ietf.org/mailman/listinfo/behave
> =

> =


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sun May 11 14:49:14 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6D38B3A6812;
	Sun, 11 May 2008 14:49:14 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 945593A6B29
	for <behave@core3.amsl.com>; Sun, 11 May 2008 14:49:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.539
X-Spam-Level: 
X-Spam-Status: No, score=-6.539 tagged_above=-999 required=5 tests=[AWL=0.060, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 W3Sw2y7I-Cbn for <behave@core3.amsl.com>;
	Sun, 11 May 2008 14:49:11 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id A48B53A6812
	for <behave@ietf.org>; Sun, 11 May 2008 14:49:11 -0700 (PDT)
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 11 May 2008 14:49:08 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m4BLn8Al000928; 
	Sun, 11 May 2008 14:49:08 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4BLn7jw017349;
	Sun, 11 May 2008 21:49:08 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'marcelo bagnulo braun'" <marcelo@it.uc3m.es>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
	<081d01c8b2db$54fa9770$c3f0200a@cisco.com>
	<4826F926.80404@it.uc3m.es>
Date: Sun, 11 May 2008 14:49:07 -0700
Message-ID: <000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcizbbbQEd4EPxieRK26eCAUaIV3hwAQvPIg
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <4826F926.80404@it.uc3m.es>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3619; t=1210542548;
	x=1211406548; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Scalability=20of=20endpoint=
	20independent=20mapping |Sender:=20;
	bh=fATIWdz/x1i/HLB9FSCb2lg1jth+5semEx6Nb3WKplw=;
	b=nMoR5u3c/4KJsYwdgi3ulBWr6BvmXVUniu19LKu/SppKKlmEGbQFzS+xZY
	qg9CioXgLIvvyUro6nuvncFzhVUdxcr4C+hdutAEGsDjSI0XhpFtii1AFmr+
	Ez9tGPn8Ly;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Thanks for explaining.

A reasonable approach is for a NAT to wait until a TCP connection has been
established (3-way handshake completed), and then allow re-using that same
public TCP port for a new connection to another remote host.

-d


> -----Original Message-----
> From: marcelo bagnulo braun [mailto:marcelo@it.uc3m.es] =

> Sent: Sunday, May 11, 2008 6:48 AM
> To: Dan Wing
> Cc: 'Iljitsch van Beijnum'; behave@ietf.org
> Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
> =

> Hi Dan,
> =

> I think Iljitsch is talking about the same scenario
> =

> Consider a host H1 behind a nat which has a single public address T.
> Suppose H1 initiates a communications towards an external =

> host H2 at port w.
> =

> So, packet from H1 to the NAT has, source (H1,v) and =

> destination (H2,w)
> =

> Now, when the packet is received at the NAT is creates a mapping
> (H1,v) <->(T,u) and the nat sends the packet with source (T,u) and =

> destination (H2,w)
> =

> Now, suppose another host H3 initiates a communication toward =

> a node H4 =

> at port j.
> The packet from H3 towards the nat has source (H3,i) and =

> estiantion (H4,j)
> =

> when the packet from He reaches the NAT, does the NAT can crate a =

> mapping (H3,i)<->(T,u)
> =

> As i understand it, if we want to have endpoint independent mapping, =

> this is not possible (this is so, because if later on H1 =

> sends a packet =

> towards H4 at port j, and we want to use the same mapping H1 =

> is already =

> using, we would end up in a conflict)
> =

> So, this basically means, that when the mapping for H1 (H1,v) =

> <->(T,u) =

> is created in the NAT, the transport address (T,u) cannot be used for =

> ANY other rmapping (cause needs to be reserved for future potential =

> communications of H1 with other destiantions.
> =

> So basically with endpoint independent mappings, each internally =

> initiated communication eats up one port of the nat, reducing =

> the number =

> of simultaneous communications the NAT can handle. If we had address =

> dependent mapping, the mapping takes into account the destination =

> address also, so even if you may need more than one mapping when the =

> same source transport address is used for two different external =

> destinations, the NAT does not needs to reserve the port =

> exclusively for =

> the internal source address, so it is likely that a better =

> usage of port =

> range of the nat is achieved.
> =

> =

> I mean, this is the price we need to pay for endpoint independence
> =

> Am i missing something?
> =

> Regards, marcelo
> =

> =

> =

> =

> Dan Wing escribi=F3:
> >  =

> >   =

> >> What I'm hoping for is that it would be possible to tighten the  =

> >> requirements such that we get closer to reserving ports for  =

> >> applications that really need reserved ports and get to =

> reuse ports  =

> >> for client-server applications so that a BEHAVE-compliant NAT can  =

> >> support a much larger user base with the same number of =

> public IPv4  =

> >> addresses as these addresses start to run out.
> >>     =

> >
> > I don't understand the relationship between endpoint =

> independent mapping
> > and the desire to free up the ports earlier.   I think you are only =

> > really asking for the NAT's TCP TIME_WAIT to be short.
> >
> > -d
> >
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www.ietf.org/mailman/listinfo/behave
> >
> >   =

> =


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sun May 11 23:47:01 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DC4CE28C24D;
	Sun, 11 May 2008 23:47:00 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1480D28C24D
	for <behave@core3.amsl.com>; Sun, 11 May 2008 23:46:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.855
X-Spam-Level: 
X-Spam-Status: No, score=-5.855 tagged_above=-999 required=5 tests=[AWL=0.444, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 z0GskAdpquae for <behave@core3.amsl.com>;
	Sun, 11 May 2008 23:46:48 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 1088528C246
	for <behave@ietf.org>; Sun, 11 May 2008 23:46:45 -0700 (PDT)
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m4C6jdIx028315; Mon, 12 May 2008 01:46:31 -0500
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 12 May 2008 09:46:23 +0300
Received: from esdhcp041113.research.nokia.com ([172.21.41.113]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 12 May 2008 09:46:23 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: behave@ietf.org
Date: Mon, 12 May 2008 09:47:43 +0300
User-Agent: KMail/1.9.9
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
In-Reply-To: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805120947.44545.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 12 May 2008 06:46:23.0506 (UTC)
	FILETIME=[E4B17F20:01C8B3FB]
X-Nokia-AV: Clean
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Le Friday 09 May 2008 20:01:10 ext Iljitsch van Beijnum, vous avez =E9crit=
=A0:
> Now obviously it makes sense for a NAT-PT (let me call it NAT64 =3D a
> NAT that sits between IPv6 clients and IPv4 servers) to conform to the
> BEHAVE requirements. However... One of these requirements is that
> mappings are endpoint independent. So if I talk to www.google.com with
> source port 49152, I don't get to also talk to www.yahoo.com using
> source port 49152.
>
> Unless I'm mistaken, this basically allows the setup of an outgoing
> session to be an implicit reservation of the source port for
> subsequent incoming sessions, so peer-to-peer applications can work
> through the NAT without the need for an explicit hole punching
> mechanism.

No.

Whether hole punching is needed depends on the *filtering* behavior. Only i=
f =

the filtering is endpoint independent, then hole punching is not needed (bu=
t =

still a good idea if only for diagnostics). If filtering is endpoint =

dependent, hole punching is required. BEHAVE does not preclude either type =
of =

*filtering*.

BEHAVE requires endpoint independent *mapping* so that communication is =

possible between two peers when both are NAT'd. With endpoint dependent =

mapping (a.k.a. symmetric NATs), a peer needs to communicate to the other =

endpoint to determine its own mapping. In other words, both peers need to =

know the other one's mapping to learn their own - an obvious chicken-and-eg=
g =

deadlock.

> The trouble with this is that it limits the number of active mappings
> per public IPv4 in a NAT to ~64k per transport protocol.

I am well aware of that, but endpoint dependent mappings are such a hassle, =

that I think it would be a terrible idea to allow it. It would also break =

(old-style) STUN, Teredo and ICE/STUNbis.

-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 02:00:39 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 22E2B3A68B4;
	Mon, 12 May 2008 02:00:39 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0AE623A690A
	for <behave@core3.amsl.com>; Mon, 12 May 2008 02:00:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.949
X-Spam-Level: 
X-Spam-Status: No, score=-3.949 tagged_above=-999 required=5
	tests=[AWL=-0.187, BAYES_00=-2.599, RCVD_BAD_ID=2.837,
	RCVD_IN_DNSWL_MED=-4]
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 bzPM3hXvL+9Y for <behave@core3.amsl.com>;
	Mon, 12 May 2008 02:00:26 -0700 (PDT)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131])
	by core3.amsl.com (Postfix) with ESMTP id 958C03A67AA
	for <behave@ietf.org>; Mon, 12 May 2008 02:00:22 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (dummyhost23.it.uc3m.es 
	[163.117.139.42])by smtp01.uc3m.es (Postfix) with ESMTP id 735645EDF66;
	Mon, 12 May 2008 10:05:10 +0200 (CEST)
Message-ID: <4827FA33.8020201@it.uc3m.es>
Date: Mon, 12 May 2008 10:05:07 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com> 
	<081d01c8b2db$54fa9770$c3f0200a@cisco.com> <4826F926.80404@it.uc3m.es> 
	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>
In-Reply-To: <000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>
X-imss-version: 2.050
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-21.7148 TC:1F TRN:58 TV:5.5.1026(15904.005)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

but this breaks

   REQ-1:  A NAT MUST have an "Endpoint Independent Mapping" behavior
      for TCP.

 =

described in draft-ietf-behave-tcp-07.txt

doesn't it?


Dan Wing escribi=F3:
> Thanks for explaining.
>
> A reasonable approach is for a NAT to wait until a TCP connection has been
> established (3-way handshake completed), and then allow re-using that same
> public TCP port for a new connection to another remote host.
>
> -d
>
>
>   =

>> -----Original Message-----
>> From: marcelo bagnulo braun [mailto:marcelo@it.uc3m.es] =

>> Sent: Sunday, May 11, 2008 6:48 AM
>> To: Dan Wing
>> Cc: 'Iljitsch van Beijnum'; behave@ietf.org
>> Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
>>
>> Hi Dan,
>>
>> I think Iljitsch is talking about the same scenario
>>
>> Consider a host H1 behind a nat which has a single public address T.
>> Suppose H1 initiates a communications towards an external =

>> host H2 at port w.
>>
>> So, packet from H1 to the NAT has, source (H1,v) and =

>> destination (H2,w)
>>
>> Now, when the packet is received at the NAT is creates a mapping
>> (H1,v) <->(T,u) and the nat sends the packet with source (T,u) and =

>> destination (H2,w)
>>
>> Now, suppose another host H3 initiates a communication toward =

>> a node H4 =

>> at port j.
>> The packet from H3 towards the nat has source (H3,i) and =

>> estiantion (H4,j)
>>
>> when the packet from He reaches the NAT, does the NAT can crate a =

>> mapping (H3,i)<->(T,u)
>>
>> As i understand it, if we want to have endpoint independent mapping, =

>> this is not possible (this is so, because if later on H1 =

>> sends a packet =

>> towards H4 at port j, and we want to use the same mapping H1 =

>> is already =

>> using, we would end up in a conflict)
>>
>> So, this basically means, that when the mapping for H1 (H1,v) =

>> <->(T,u) =

>> is created in the NAT, the transport address (T,u) cannot be used for =

>> ANY other rmapping (cause needs to be reserved for future potential =

>> communications of H1 with other destiantions.
>>
>> So basically with endpoint independent mappings, each internally =

>> initiated communication eats up one port of the nat, reducing =

>> the number =

>> of simultaneous communications the NAT can handle. If we had address =

>> dependent mapping, the mapping takes into account the destination =

>> address also, so even if you may need more than one mapping when the =

>> same source transport address is used for two different external =

>> destinations, the NAT does not needs to reserve the port =

>> exclusively for =

>> the internal source address, so it is likely that a better =

>> usage of port =

>> range of the nat is achieved.
>>
>>
>> I mean, this is the price we need to pay for endpoint independence
>>
>> Am i missing something?
>>
>> Regards, marcelo
>>
>>
>>
>>
>> Dan Wing escribi=F3:
>>     =

>>>  =

>>>   =

>>>       =

>>>> What I'm hoping for is that it would be possible to tighten the  =

>>>> requirements such that we get closer to reserving ports for  =

>>>> applications that really need reserved ports and get to =

>>>>         =

>> reuse ports  =

>>     =

>>>> for client-server applications so that a BEHAVE-compliant NAT can  =

>>>> support a much larger user base with the same number of =

>>>>         =

>> public IPv4  =

>>     =

>>>> addresses as these addresses start to run out.
>>>>     =

>>>>         =

>>> I don't understand the relationship between endpoint =

>>>       =

>> independent mapping
>>     =

>>> and the desire to free up the ports earlier.   I think you are only =

>>> really asking for the NAT's TCP TIME_WAIT to be short.
>>>
>>> -d
>>>
>>> _______________________________________________
>>> Behave mailing list
>>> Behave@ietf.org
>>> https://www.ietf.org/mailman/listinfo/behave
>>>
>>>   =

>>>       =

>
>
>   =


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 02:01:36 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7D4DB3A67E5;
	Mon, 12 May 2008 02:01:36 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 32C533A67E5
	for <behave@core3.amsl.com>; Mon, 12 May 2008 02:01:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.571
X-Spam-Level: 
X-Spam-Status: No, score=-1.571 tagged_above=-999 required=5 tests=[AWL=0.378, 
	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 viXM+gby8zde for <behave@core3.amsl.com>;
	Mon, 12 May 2008 02:01:33 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id 6454B3A6829
	for <behave@ietf.org>; Mon, 12 May 2008 02:01:28 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id E91DC3EA131;
	Mon, 12 May 2008 11:01:08 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 7DDEB3EA0E4;
	Mon, 12 May 2008 11:01:07 +0200 (CEST)
Message-ID: <48280754.5010402@free.fr>
Date: Mon, 12 May 2008 11:01:08 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?=
 <remi.denis-courmont@nokia.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
	<48271209.8060903@free.fr>
	<200805120953.48263.remi.denis-courmont@nokia.com>
In-Reply-To: <200805120953.48263.remi.denis-courmont@nokia.com>
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping - a
	proposal
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

R=E9mi Denis-Courmont wrote :
> Le Sunday 11 May 2008 18:34:33 ext R=E9mi Despr=E9s, vous avez =E9crit :
>> For this, the approach I see is as follows:
>> - NATs SHOULD do end-point INDEPENDENT mapping (that of "full cone"
>> NATs) when packets that initiate addresss-port mappings indicate that
>> this is needed.
> =

> You are mixing *mapping* and *filtering*.

Can you be more specific, and indicate why this would NOT be right?
(I don't understand where the "mixing" takes place.)

> =

>> - They MAY do end-point DEPENDENT mappings in all other case.
>> - They SHOULD do end-point DEPENDENT mappings wherever sparing use of
>> public IPv4 addresses is desirable.
> =

>> IMU, packets that indicate in a standard way a need for end-point
>> independent mapping are those sent to:
>> - STUN and TURN servers (server port 1990, 1991 or 1992)
>> - Teredo servers (server port 3544)
> =

> Makes no sense to me. When doing say, RTP/RTCP, the port numbers are typi=
cally =

> dynamic, so this won't work - and that's what ICE typically deals with.
> Also, when both sides are NATted, obviously neither of them can use a fix=
ed =

> port. Hence, I believe your proposed scheme will fail terribly in the cur=
rent =

> world.

IMU:
- Connections that are established with ICE would work with my proposal =

as they did without it: the mapping for them having been established =

with a STUN port as initial server port, traversed NATs would do the =

desired "end-point independent" mapping.

- On the other hand, if client "C1", using its port "c1", calls an HTTP =

server at public address "S1" on port 80, and if another client "C2" =

behind a common NAT, using its port "c2", calls another HTTP server at =

public address "S2", then the NAT may use its same public address and =

port couple (Ni ni) for both connections.
Mappings for this would be:
   (C1-c1, S1-80, TCP) <--> (Ni-ni, S1-80, TCP)
   (C2-c2, S2-80, TCP) <--> (Ni-ni, S2-80, TCP)
or:
   (C1-c1, S1-80) <--> (Ni-ni, S1-80)
   (C2-c2, S2-80) <--> (Ni-ni, S2-80)
(Client C2 may be the same as C1.)

Regards.

R=E9mi
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 02:20:00 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4A46C3A684C;
	Mon, 12 May 2008 02:20:00 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 830BA3A682B
	for <behave@core3.amsl.com>; Mon, 12 May 2008 02:19:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.911
X-Spam-Level: 
X-Spam-Status: No, score=-5.911 tagged_above=-999 required=5 tests=[AWL=0.388, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 AmwhVBGBO4EO for <behave@core3.amsl.com>;
	Mon, 12 May 2008 02:19:57 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 7B2473A6782
	for <behave@ietf.org>; Mon, 12 May 2008 02:19:57 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m4C9G4Rk017685; Mon, 12 May 2008 04:17:31 -0500
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 12 May 2008 12:17:29 +0300
Received: from esdhcp041113.research.nokia.com ([172.21.41.113]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 12 May 2008 12:17:28 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: behave@ietf.org
Date: Mon, 12 May 2008 12:18:49 +0300
User-Agent: KMail/1.9.9
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
	<200805120953.48263.remi.denis-courmont@nokia.com>
	<48280754.5010402@free.fr>
In-Reply-To: <48280754.5010402@free.fr>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805121218.49884.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 12 May 2008 09:17:28.0702 (UTC)
	FILETIME=[FFF8A1E0:01C8B410]
X-Nokia-AV: Clean
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping - a
	proposal
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Le Monday 12 May 2008 12:01:08 ext R=E9mi Despr=E9s, vous avez =E9crit=A0:
> > Le Sunday 11 May 2008 18:34:33 ext R=E9mi Despr=E9s, vous avez =E9crit :
> >> For this, the approach I see is as follows:
> >> - NATs SHOULD do end-point INDEPENDENT mapping (that of "full cone"
> >> NATs) when packets that initiate addresss-port mappings indicate that
> >> this is needed.
> >
> > You are mixing *mapping* and *filtering*.
>
> Can you be more specific, and indicate why this would NOT be right?
> (I don't understand where the "mixing" takes place.)

A full cone NAT is a NAT with endpoint independent mapping *AND* filtering.

Many NATs do independent mapping yet are not at all full cone NATs.

> IMU:
> - Connections that are established with ICE would work with my proposal
> as they did without it: the mapping for them having been established
> with a STUN port as initial server port, traversed NATs would do the
> desired "end-point independent" mapping.

There is no obligation to use STUN binding discovery for ICE. For instance,=
 a =

client can do Binding Discovery using TURN (which has no fixed port number =

AFAIK).

And finally, there are not only IETF protocols in the peer-to-peer world.

Your proposal would break the long tail of peer-to-peer and/or gaming =

protocols. Recipe for a market failure, I'm afraid. Especially when it come=
s =

to the large ISPs which is precisely what this is all about.

-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 02:51:22 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 467F43A67AC;
	Mon, 12 May 2008 02:51:22 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7D6BF3A67AC
	for <behave@core3.amsl.com>; Mon, 12 May 2008 02:51:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.954
X-Spam-Level: 
X-Spam-Status: No, score=-5.954 tagged_above=-999 required=5 tests=[AWL=0.345, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 G5FyA1Cy+E5j for <behave@core3.amsl.com>;
	Mon, 12 May 2008 02:51:18 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 3EE053A6785
	for <behave@ietf.org>; Mon, 12 May 2008 02:51:18 -0700 (PDT)
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m4C9m0bN017265; Mon, 12 May 2008 04:48:39 -0500
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 12 May 2008 12:47:50 +0300
Received: from esdhcp041113.research.nokia.com ([172.21.41.113]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 12 May 2008 12:47:50 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: behave@ietf.org
Date: Mon, 12 May 2008 12:49:11 +0300
User-Agent: KMail/1.9.9
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>
	<4827FA33.8020201@it.uc3m.es>
In-Reply-To: <4827FA33.8020201@it.uc3m.es>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805121249.11441.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 12 May 2008 09:47:50.0319 (UTC)
	FILETIME=[3DBD53F0:01C8B415]
X-Nokia-AV: Clean
Cc: Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Le Monday 12 May 2008 11:05:07 ext marcelo bagnulo braun, vous avez =E9crit=
=A0:
> but this breaks
>
>    REQ-1:  A NAT MUST have an "Endpoint Independent Mapping" behavior
>       for TCP.
>
> described in draft-ietf-behave-tcp-07.txt
> doesn't it?

Yes, I think so too.

This does imply a limit the order of 1,000 users per IP address behind a =

BEHAVE-compliant translator, in comparison to the order of 10,000 behind =

an "aggressively" symmetric translator. Such is the cost of end-to-end =

communication (I don't dare to say end-to-end transparency here). As Iljits=
ch =

noted.

That's assuming well-mannered user applications. It is fairly trivial to mo=
unt =

a DoS against the ports range of a BEHAVE-compliant translator, unless a =

limited number of port allocations per-user is enforced.

As it happens, the BEHAVE requirements where written pretty much on purpose=
. =

They DO actually solve problems. I believe a certain number of applications =

benefit from BEHAVE-ish NATs, and matter to a large number of paying =

customers for large ISPs. In the western world, if these ISPs can allocate =

one IP per customer today, they should be able to allocate one IP per 500 =

customers in the foreseeable future.

Also, in managed networks, BEHAVE-compliance is probably not such a big dea=
l. =

There, you have firewalls and gateways. And peer-to-peer/end-to-end is not =

really aimed for. In fact, it's typically fought against.


Well, scalability may be a problem in IP-deprived areas. If it happens, BEH=
AVE =

will not be complied with. Too bad. But I believe "breaking" the current =

BEHAVE requirements would be even worse overall.

-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 02:55:48 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 811D13A684C;
	Mon, 12 May 2008 02:55:48 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5E7083A67AC
	for <behave@core3.amsl.com>; Mon, 12 May 2008 02:55:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.988
X-Spam-Level: 
X-Spam-Status: No, score=-3.988 tagged_above=-999 required=5
	tests=[AWL=-1.689, BAYES_00=-2.599, 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 ZNVi8nj-Ipvx for <behave@core3.amsl.com>;
	Mon, 12 May 2008 02:55:45 -0700 (PDT)
Received: from mgw-fb01.nokia.com (mgw-fb01.nokia.com [192.100.122.235])
	by core3.amsl.com (Postfix) with ESMTP id 511843A6785
	for <behave@ietf.org>; Mon, 12 May 2008 02:55:43 -0700 (PDT)
Received: from mgw-mx09.nokia.com ([192.100.105.134])
	by mgw-fb01.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m4C6vohL012580
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <behave@ietf.org>; Mon, 12 May 2008 09:57:52 +0300
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m4C6pwcp002580; Mon, 12 May 2008 01:52:33 -0500
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 12 May 2008 09:52:27 +0300
Received: from esdhcp041113.research.nokia.com ([172.21.41.113]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 12 May 2008 09:52:27 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: behave@ietf.org
Date: Mon, 12 May 2008 09:53:48 +0300
User-Agent: KMail/1.9.9
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
	<48271209.8060903@free.fr>
In-Reply-To: <48271209.8060903@free.fr>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805120953.48263.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 12 May 2008 06:52:27.0157 (UTC)
	FILETIME=[BD723C50:01C8B3FC]
X-Nokia-AV: Clean
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping - a
	proposal
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Le Sunday 11 May 2008 18:34:33 ext R=E9mi Despr=E9s, vous avez =E9crit=A0:
> For this, the approach I see is as follows:
> - NATs SHOULD do end-point INDEPENDENT mapping (that of "full cone"
> NATs) when packets that initiate addresss-port mappings indicate that
> this is needed.

You are mixing *mapping* and *filtering*.

> - They MAY do end-point DEPENDENT mappings in all other case.
> - They SHOULD do end-point DEPENDENT mappings wherever sparing use of
> public IPv4 addresses is desirable.

> IMU, packets that indicate in a standard way a need for end-point
> independent mapping are those sent to:
> - STUN and TURN servers (server port 1990, 1991 or 1992)
> - Teredo servers (server port 3544)

Makes no sense to me. When doing say, RTP/RTCP, the port numbers are typica=
lly =

dynamic, so this won't work - and that's what ICE typically deals with.
Also, when both sides are NATted, obviously neither of them can use a fixed =

port. Hence, I believe your proposed scheme will fail terribly in the curre=
nt =

world.

-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 03:21:49 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EAFC33A6810;
	Mon, 12 May 2008 03:21:49 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E6E6728C246
	for <behave@core3.amsl.com>; Mon, 12 May 2008 03:21:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.737
X-Spam-Level: 
X-Spam-Status: No, score=-3.737 tagged_above=-999 required=5
	tests=[AWL=-0.275, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_BAD_ID=2.837, RCVD_IN_DNSWL_MED=-4]
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 Qn3MpcHNiDzB for <behave@core3.amsl.com>;
	Mon, 12 May 2008 03:21:47 -0700 (PDT)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131])
	by core3.amsl.com (Postfix) with ESMTP id A74E43A6785
	for <behave@ietf.org>; Mon, 12 May 2008 03:21:46 -0700 (PDT)
Received: from dummyhost31.it.uc3m.es (dummyhost0.it.uc3m.es 
	[163.117.139.42])by smtp01.uc3m.es (Postfix) with ESMTP id A9E1F5EE250;
	Mon, 12 May 2008 12:17:11 +0200 (CEST)
Message-ID: <48281927.4020708@it.uc3m.es>
Date: Mon, 12 May 2008 12:17:11 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?=<remi.denis-courmont@nokia.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com> 
	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>
	<4827FA33.8020201@it.uc3m.es> 
	<200805121249.11441.remi.denis-courmont@nokia.com>
In-Reply-To: <200805121249.11441.remi.denis-courmont@nokia.com>
X-imss-version: 2.050
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-9.7975 TC:1F TRN:41 TV:5.5.1026(15904.006)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: behave@ietf.org, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi  Remi,

the question that comes next is: what happens when we run out of IPv4 =

addresses and all the world becomes (in a more or less manner) an =

IP-deprived area?

Regards, marcelo
PS: FWIW i also think that the endpoint independence is a requierement =

we must meet, but just want to make sure we all understand its cost



R=E9mi Denis-Courmont escribi=F3:
> Le Monday 12 May 2008 11:05:07 ext marcelo bagnulo braun, vous avez =E9cr=
it :
>   =

>> but this breaks
>>
>>    REQ-1:  A NAT MUST have an "Endpoint Independent Mapping" behavior
>>       for TCP.
>>
>> described in draft-ietf-behave-tcp-07.txt
>> doesn't it?
>>     =

>
> Yes, I think so too.
>
> This does imply a limit the order of 1,000 users per IP address behind a =

> BEHAVE-compliant translator, in comparison to the order of 10,000 behind =

> an "aggressively" symmetric translator. Such is the cost of end-to-end =

> communication (I don't dare to say end-to-end transparency here). As Ilji=
tsch =

> noted.
>
> That's assuming well-mannered user applications. It is fairly trivial to =
mount =

> a DoS against the ports range of a BEHAVE-compliant translator, unless a =

> limited number of port allocations per-user is enforced.
>
> As it happens, the BEHAVE requirements where written pretty much on purpo=
se. =

> They DO actually solve problems. I believe a certain number of applicatio=
ns =

> benefit from BEHAVE-ish NATs, and matter to a large number of paying =

> customers for large ISPs. In the western world, if these ISPs can allocat=
e =

> one IP per customer today, they should be able to allocate one IP per 500 =

> customers in the foreseeable future.
>
> Also, in managed networks, BEHAVE-compliance is probably not such a big d=
eal. =

> There, you have firewalls and gateways. And peer-to-peer/end-to-end is no=
t =

> really aimed for. In fact, it's typically fought against.
>
>
> Well, scalability may be a problem in IP-deprived areas. If it happens, B=
EHAVE =

> will not be complied with. Too bad. But I believe "breaking" the current =

> BEHAVE requirements would be even worse overall.
>
>   =


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 08:37:52 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B730B3A6AF1;
	Mon, 12 May 2008 08:37:52 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6F0AF3A68EE
	for <behave@core3.amsl.com>; Mon, 12 May 2008 08:37:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, 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 6q-b-gyHEKIm for <behave@core3.amsl.com>;
	Mon, 12 May 2008 08:37:48 -0700 (PDT)
Received: from mail.sipeerior.com (mail.sipeerior.com [128.239.5.131])
	by core3.amsl.com (Postfix) with ESMTP id C8F0428C134
	for <behave@ietf.org>; Mon, 12 May 2008 08:37:47 -0700 (PDT)
Received: from vuelta.lowekamp.home (ip68-230-194-34.rd.hr.cox.net
	[68.230.194.34])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.sipeerior.com (Postfix) with ESMTP id F21CA505B01;
	Mon, 12 May 2008 11:37:42 -0400 (EDT)
Message-ID: <48286442.8090503@sipeerior.com>
Date: Mon, 12 May 2008 11:37:38 -0400
From: Bruce Lowekamp <lowekamp@sipeerior.com>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?=
 <remi.denis-courmont@nokia.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
	<200805120947.44545.remi.denis-courmont@nokia.com>
In-Reply-To: <200805120947.44545.remi.denis-courmont@nokia.com>
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I agree.  And even if the hypothetical savings in the number of IPv4 =

addresses needed for NATs is realized, going to endpoint-dependent =

mapping would require every major ISP that deploys one of these things =

to deploy a number of TURN relays since their customers won't be able to =

connect directly with those behind similar NATs.  So you're trading a =

lot of bandwidth and machines deployed as relays for a savings of IP =

addresses.   If you were doing a full voip (or gaming or whatever) =

deployment, it isn't actually clear to me that you won't need to deploy =

as many relays  (with public IP addresses) as you theoretically saved by =

using a symmetric NAT.

Bruce


R=E9mi Denis-Courmont wrote:
> Le Friday 09 May 2008 20:01:10 ext Iljitsch van Beijnum, vous avez =E9cri=
t :
>> Now obviously it makes sense for a NAT-PT (let me call it NAT64 =3D a
>> NAT that sits between IPv6 clients and IPv4 servers) to conform to the
>> BEHAVE requirements. However... One of these requirements is that
>> mappings are endpoint independent. So if I talk to www.google.com with
>> source port 49152, I don't get to also talk to www.yahoo.com using
>> source port 49152.
>>
>> Unless I'm mistaken, this basically allows the setup of an outgoing
>> session to be an implicit reservation of the source port for
>> subsequent incoming sessions, so peer-to-peer applications can work
>> through the NAT without the need for an explicit hole punching
>> mechanism.
> =

> No.
> =

> Whether hole punching is needed depends on the *filtering* behavior. Only=
 if =

> the filtering is endpoint independent, then hole punching is not needed (=
but =

> still a good idea if only for diagnostics). If filtering is endpoint =

> dependent, hole punching is required. BEHAVE does not preclude either typ=
e of =

> *filtering*.
> =

> BEHAVE requires endpoint independent *mapping* so that communication is =

> possible between two peers when both are NAT'd. With endpoint dependent =

> mapping (a.k.a. symmetric NATs), a peer needs to communicate to the other =

> endpoint to determine its own mapping. In other words, both peers need to =

> know the other one's mapping to learn their own - an obvious chicken-and-=
egg =

> deadlock.
> =

>> The trouble with this is that it limits the number of active mappings
>> per public IPv4 in a NAT to ~64k per transport protocol.
> =

> I am well aware of that, but endpoint dependent mappings are such a hassl=
e, =

> that I think it would be a terrible idea to allow it. It would also break =

> (old-style) STUN, Teredo and ICE/STUNbis.
> =


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 08:39:40 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 684923A6AF6;
	Mon, 12 May 2008 08:39:40 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B79C43A6AF6
	for <behave@core3.amsl.com>; Mon, 12 May 2008 08:39:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level: 
X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5 tests=[AWL=0.347, 
	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 AYu--aFxMWyE for <behave@core3.amsl.com>;
	Mon, 12 May 2008 08:39:38 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id B4B043A69AB
	for <behave@ietf.org>; Mon, 12 May 2008 08:39:37 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 8DA913EA110;
	Mon, 12 May 2008 17:39:34 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id E3F4B3EA0C6;
	Mon, 12 May 2008 17:39:33 +0200 (CEST)
Message-ID: <482864B6.1030200@free.fr>
Date: Mon, 12 May 2008 17:39:34 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?=
 <remi.denis-courmont@nokia.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
	<200805120953.48263.remi.denis-courmont@nokia.com>
	<48280754.5010402@free.fr>
	<200805121218.49884.remi.denis-courmont@nokia.com>
In-Reply-To: <200805121218.49884.remi.denis-courmont@nokia.com>
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping - a
	proposal
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

R=E9mi Denis-Courmont wrote :
> Le Monday 12 May 2008 12:01:08 ext R=E9mi Despr=E9s, vous avez =E9crit :
>>> Le Sunday 11 May 2008 18:34:33 ext R=E9mi Despr=E9s, vous avez =E9crit :
>>>> For this, the approach I see is as follows:
>>>> - NATs SHOULD do end-point INDEPENDENT mapping (that of "full cone"
>>>> NATs) when packets that initiate addresss-port mappings indicate that
>>>> this is needed.
>>> You are mixing *mapping* and *filtering*.
>> Can you be more specific, and indicate why this would NOT be right?
>> (I don't understand where the "mixing" takes place.)
> =

> A full cone NAT is a NAT with endpoint independent mapping *AND* filterin=
g.

Thanks for the explanation.
My proposal should then avoid the reference to cone NATs.

(For your answer to be complete, can you indicate where I could have =

read your definition?)

>> IMU:
>> - Connections that are established with ICE would work with my proposal
>> as they did without it: the mapping for them having been established
>> with a STUN port as initial server port, traversed NATs would do the
>> desired "end-point independent" mapping.
> =

> There is no obligation to use STUN binding discovery for ICE. For instanc=
e, a =

> client can do Binding Discovery using TURN (which has no fixed port numbe=
r =

> AFAIK).
IMU, and according to draft-ietf-behave-turn-tcp-00, TURN servers use =

TURN specific requests, responses, attributes and response codes, but =

should use the same port number as STUN.

BUT see also the conclusion below, whereby this is no longer a concern.

> And finally, there are not only IETF protocols in the peer-to-peer world.
> =

> Your proposal would break the long tail of peer-to-peer and/or gaming =

> protocols. Recipe for a market failure, I'm afraid. =

The concern is of course legitimate.


CONCLUSION
In view of your remarks (thanks or them), my initial proposal can be =

improved, to become:

  1. NATs SHOULD do end-point INDEPENDENT mapping if packets that =

initiate addresss-port mappings don't have destination ports indicating =

that endpoint DEPENDENT mapping is acceptable.
  2. In general, NATs MAY do endpoint INDEPENDENT mapping if packets =

that initiate addresss-port mappings have destination ports indicating =

that endpoint DEPENDENT mapping is acceptable.
  3. Where sparing use of public IPv4 addresses is desirable, NATs =

SHOULD use endpoint DEPENDENT mapping if packets that initiate =

addresss-port mappings indicate that endpoint DEPENDENT mapping is =

acceptable.
  2. Destination port numbers that indicate that endpoint DEPENDENT =

mapping is acceptable are those of: HTTP, SMTP, POP3, NNTP, Telnet, SNMP =

(and a few others, list to be completed)


Regards.


R=E9mi

	=

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 08:59:30 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 95F1D3A695C;
	Mon, 12 May 2008 08:59:30 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 65FF73A6AEA
	for <behave@core3.amsl.com>; Mon, 12 May 2008 08:59:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.462
X-Spam-Level: 
X-Spam-Status: No, score=-3.462 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_BAD_ID=2.837,
	RCVD_IN_DNSWL_MED=-4]
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 taazMdjxw-wD for <behave@core3.amsl.com>;
	Mon, 12 May 2008 08:59:27 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133])
	by core3.amsl.com (Postfix) with ESMTP id DC2893A695C
	for <behave@ietf.org>; Mon, 12 May 2008 08:59:26 -0700 (PDT)
Received: from [163.117.140.211] (unknown [163.117.140.211])by 
	smtp03.uc3m.es (Postfix) with ESMTP id 5EB343BF009;Mon, 12 May 2008 
	17:58:49 +0200 (CEST)
Message-Id: <4D10220D-9E1A-45C4-A148-4B740073F4A2@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <48271209.8060903@free.fr>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 12 May 2008 17:58:49 +0200
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com> 
	<48271209.8060903@free.fr>
X-Mailer: Apple Mail (2.919.2)
X-imss-version: 2.050
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-6.4420 TC:1F TRN:33 TV:5.5.1026(15906.000)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping - a
	proposal
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 11 mei 2008, at 17:34, R=E9mi Despr=E9s wrote:

> I FULLY SUPPORT the requirement of "reserving ports for
> applications that really need reserved ports and get to reuse ports
> for client-server applications".

Excellent.

I see several others say "peer-to-peer is more important than  =

scalability", which is an artificial dichotomy: if we work a bit  =

harder we can have both.

> IMU, packets that indicate in a standard way a need for end-point  =

> independent mapping are those sent to:
> - STUN and TURN servers (server port 1990, 1991 or 1992)
> - Teredo servers (server port 3544)

> Would this satisfy what you had in mind?

No, because then only Teredo (which should never be used through NAT- =

PT, which is the part that I'm concerned about) and STUN/TURN have the  =

endpoint independent behavior, not the actual peer-to-peer application  =

protocols.

A more useful approach would be to assume that all protocols that use  =

a < 1024 well-known port number are client-server and don't need  =

endpoint independence. (Perhaps with a few exceptions.) The main thing  =

that this catches is web and mail, web uses many short lived sessions  =

and mail may use several long lived sessions. With these out of the  =

way endpoint independent mapping for the protocols on port numbers >  =

1023 shouldn't be too problematic.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 09:15:11 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9CAFA3A6B1A;
	Mon, 12 May 2008 09:15:11 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E327D3A6B02
	for <behave@core3.amsl.com>; Mon, 12 May 2008 09:15:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.629
X-Spam-Level: 
X-Spam-Status: No, score=-1.629 tagged_above=-999 required=5 tests=[AWL=0.320, 
	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 JHzdcwDZVae3 for <behave@core3.amsl.com>;
	Mon, 12 May 2008 09:15:05 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id E90403A6AEA
	for <behave@ietf.org>; Mon, 12 May 2008 09:15:04 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id EFE083EA13B;
	Mon, 12 May 2008 18:14:52 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 8387F3EA0C0;
	Mon, 12 May 2008 18:14:52 +0200 (CEST)
Message-ID: <48286CFD.1080204@free.fr>
Date: Mon, 12 May 2008 18:14:53 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>
	<200805121249.11441.remi.denis-courmont@nokia.com>
	<48281927.4020708@it.uc3m.es>
In-Reply-To: <48281927.4020708@it.uc3m.es>
Cc: behave@ietf.org, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

marcelo bagnulo braun wrote :
> Hi  Remi,
> =

> the question that comes next is: what happens when we run out of IPv4 =

> addresses and all the world becomes (in a more or less manner) an =

> IP-deprived area?
> =

> Regards, marcelo
> PS: FWIW i also think that the endpoint independence is a requierement =

> we must meet, but just want to make sure we all understand its cost

IMU, it is still possible to avoid the cost of endpoint independence in
cases where NATs can easily and safely detect that it isn't necessary.

My proposal for this, following R=E9mi Denis-Courmont's remarks, has become:

  1. NATs SHOULD do end-point INDEPENDENT mapping if packets that
initiate addresss-port mappings don't have destination ports indicating
that endpoint DEPENDENT mapping is acceptable.
  2. In general, NATs MAY also do endpoint INDEPENDENT mapping if
packets that initiate addresss-port mappings have destination ports
indicating that endpoint DEPENDENT mapping is acceptable.
  3. But, where sparing use of public IPv4 addresses is desirable, NATs
SHOULD use endpoint DEPENDENT mapping if packets that initiate
addresss-port mappings indicate that endpoint DEPENDENT mapping is
acceptable.
  2. Destination ports that indicate that endpoint DEPENDENT mapping is
acceptable are those of: HTTP, SMTP, POP3, NNTP, Telnet, SNMP (and a few
others, list to be completed)

So far, I don't see why this wouldn't work.

IMU, the saving on address-port consumption could be huge in view of =

examples given by Iljitsch in
http://www.ietf.org/mail-archive/web/behave/current/msg03821.html.


Regards.

R=E9mi

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 09:25:06 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F359D3A6872;
	Mon, 12 May 2008 09:25:05 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF5B63A6872
	for <behave@core3.amsl.com>; Mon, 12 May 2008 09:25:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 aTkRI9P+9mW3 for <behave@core3.amsl.com>;
	Mon, 12 May 2008 09:25:03 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 911A53A67EE
	for <behave@ietf.org>; Mon, 12 May 2008 09:25:03 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	2F36320FF7; Mon, 12 May 2008 18:23:58 +0200 (CEST)
X-AuditID: c1b4fb3e-ac995bb000004ec0-dc-48286f1ebd44
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	1AA3A20FE4; Mon, 12 May 2008 18:23:58 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 May 2008 18:23:54 +0200
Received: from [127.0.0.1] ([147.214.183.32]) by esealmw129.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 May 2008 18:23:53 +0200
Message-ID: <48286F19.5090707@ericsson.com>
Date: Mon, 12 May 2008 18:23:53 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <4810C3ED.7030901@ericsson.com>
In-Reply-To: <4810C3ED.7030901@ericsson.com>
X-Enigmail-Version: 0.95.6
X-OriginalArrivalTime: 12 May 2008 16:23:53.0971 (UTC)
	FILETIME=[91FADC30:01C8B44C]
X-Brightmail-Tracker: AAAAAA==
Cc: Behave WG <behave@ietf.org>, draft-ietf-behave-rfc3489bis@tools.ietf.org
Subject: Re: [BEHAVE] Consensus call on Adding "Client" attribute to STUN
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi,

I got all Yes, go for it and no against so I rule there to be consensus =

to add this attribute. Authors, please go ahead and add it.

Cheers

Magnus

Magnus Westerlund skrev:
> This is a one week+ consensus call (until the 5th of May) if the WG =

> thinks that STUN (draft-ietf-behave-rfc3489bis) shall be extended with =

> an additional attribute "Client" before publication.
> =

> With the general description along the lines of:
> =

>     X.Y CLIENT
> =

>     The client attribute contains a textual description of the software
>     being used by the client, including manufacturer and version number.
>     The attribute has no impact on operation of the protocol, and serves
>     only as a tool for diagnostic and debugging purposes.  The value of
>     CLIENT is variable length.  It MUST be a UTF-8 [RFC3629] encoded
>     sequence of less than 128 characters (which can be as long as 763
>     bytes).
> =

> And some Security Considerations on the risk for targeted attacks =

> against clients with this information. Plus other text needed to bring =

> it in consistently
> =

> The text is open for wordsmithing by the editors of the STUN spec.
> =

> Please indicate your position on adding this or not.
> =

> Cheers
> =

> Magnus Westerlund
> =

> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> F=E4r=F6gatan 6                | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
> =

> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> =



-- =


Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
F=E4r=F6gatan 6                | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 10:00:49 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 206213A6818;
	Mon, 12 May 2008 10:00:49 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4B7423A6AEA
	for <behave@core3.amsl.com>; Mon, 12 May 2008 10:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level: 
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 wOHbFopGHJzj for <behave@core3.amsl.com>;
	Mon, 12 May 2008 10:00:45 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id E07C83A67C1
	for <behave@ietf.org>; Mon, 12 May 2008 10:00:44 -0700 (PDT)
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-3.cisco.com with ESMTP; 12 May 2008 10:00:37 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m4CH0baK029281; 
	Mon, 12 May 2008 10:00:37 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4CH0aAj002023;
	Mon, 12 May 2008 17:00:36 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'marcelo bagnulo braun'" <marcelo@it.uc3m.es>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
	<081d01c8b2db$54fa9770$c3f0200a@cisco.com>
	<4826F926.80404@it.uc3m.es>
	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>
	<4827FA33.8020201@it.uc3m.es>
Date: Mon, 12 May 2008 10:00:36 -0700
Message-ID: <03cb01c8b451$b32583b0$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <4827FA33.8020201@it.uc3m.es>
Thread-Index: Aci0BuvdnjmO4jvGTa60gAHTSxUPxQASYdUw
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4744; t=1210611637;
	x=1211475637; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Scalability=20of=20endpoint=
	20independent=20mapping |Sender:=20;
	bh=R7BbNeRZSBiCuWqLb8HavesKL60bfK+nUXfQp+Hqyiw=;
	b=iqgecEZLuTDvilB9QXy1AvetqlpRAnHiJuUFvAXcY9Rtzv3YcBsp9R5wua
	K5oUBaMlmXhTMKViCJNOlhmiSBbS0cfQknVdjjiNuXJQVtSuvhj6RkatDt9w
	t2bj6vTylc;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

 =


> -----Original Message-----
> From: marcelo bagnulo braun [mailto:marcelo@it.uc3m.es] =

> Sent: Monday, May 12, 2008 1:05 AM
> To: Dan Wing
> Cc: 'Iljitsch van Beijnum'; behave@ietf.org
> Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
> =

> but this breaks
> =

>    REQ-1:  A NAT MUST have an "Endpoint Independent Mapping" behavior
>       for TCP.
> =

>  =

> described in draft-ietf-behave-tcp-07.txt
> =

> doesn't it?

Yes.

But does re-using the same public TCP port, after the 3-way handshake
completes, cause something to break?  It feels pretty safe to me.

-d


> Dan Wing escribi=F3:
> > Thanks for explaining.
> >
> > A reasonable approach is for a NAT to wait until a TCP =

> > connection has been
> > established (3-way handshake completed), and then allow =

> > re-using that same
> > public TCP port for a new connection to another remote host.
> >
> > -d
> >
> >
> >   =

> >> -----Original Message-----
> >> From: marcelo bagnulo braun [mailto:marcelo@it.uc3m.es] =

> >> Sent: Sunday, May 11, 2008 6:48 AM
> >> To: Dan Wing
> >> Cc: 'Iljitsch van Beijnum'; behave@ietf.org
> >> Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
> >>
> >> Hi Dan,
> >>
> >> I think Iljitsch is talking about the same scenario
> >>
> >> Consider a host H1 behind a nat which has a single public =

> address T.
> >> Suppose H1 initiates a communications towards an external =

> >> host H2 at port w.
> >>
> >> So, packet from H1 to the NAT has, source (H1,v) and =

> >> destination (H2,w)
> >>
> >> Now, when the packet is received at the NAT is creates a mapping
> >> (H1,v) <->(T,u) and the nat sends the packet with source (T,u) and =

> >> destination (H2,w)
> >>
> >> Now, suppose another host H3 initiates a communication toward =

> >> a node H4 =

> >> at port j.
> >> The packet from H3 towards the nat has source (H3,i) and =

> >> estiantion (H4,j)
> >>
> >> when the packet from He reaches the NAT, does the NAT can crate a =

> >> mapping (H3,i)<->(T,u)
> >>
> >> As i understand it, if we want to have endpoint =

> independent mapping, =

> >> this is not possible (this is so, because if later on H1 =

> >> sends a packet =

> >> towards H4 at port j, and we want to use the same mapping H1 =

> >> is already =

> >> using, we would end up in a conflict)
> >>
> >> So, this basically means, that when the mapping for H1 (H1,v) =

> >> <->(T,u) =

> >> is created in the NAT, the transport address (T,u) cannot =

> be used for =

> >> ANY other rmapping (cause needs to be reserved for future =

> potential =

> >> communications of H1 with other destiantions.
> >>
> >> So basically with endpoint independent mappings, each internally =

> >> initiated communication eats up one port of the nat, reducing =

> >> the number =

> >> of simultaneous communications the NAT can handle. If we =

> had address =

> >> dependent mapping, the mapping takes into account the destination =

> >> address also, so even if you may need more than one =

> mapping when the =

> >> same source transport address is used for two different external =

> >> destinations, the NAT does not needs to reserve the port =

> >> exclusively for =

> >> the internal source address, so it is likely that a better =

> >> usage of port =

> >> range of the nat is achieved.
> >>
> >>
> >> I mean, this is the price we need to pay for endpoint independence
> >>
> >> Am i missing something?
> >>
> >> Regards, marcelo
> >>
> >>
> >>
> >>
> >> Dan Wing escribi=F3:
> >>     =

> >>>  =

> >>>   =

> >>>       =

> >>>> What I'm hoping for is that it would be possible to tighten the  =

> >>>> requirements such that we get closer to reserving ports for  =

> >>>> applications that really need reserved ports and get to =

> >>>>         =

> >> reuse ports  =

> >>     =

> >>>> for client-server applications so that a =

> BEHAVE-compliant NAT can  =

> >>>> support a much larger user base with the same number of =

> >>>>         =

> >> public IPv4  =

> >>     =

> >>>> addresses as these addresses start to run out.
> >>>>     =

> >>>>         =

> >>> I don't understand the relationship between endpoint =

> >>>       =

> >> independent mapping
> >>     =

> >>> and the desire to free up the ports earlier.   I think =

> you are only =

> >>> really asking for the NAT's TCP TIME_WAIT to be short.
> >>>
> >>> -d
> >>>
> >>> _______________________________________________
> >>> Behave mailing list
> >>> Behave@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/behave
> >>>
> >>>   =

> >>>       =

> >
> >
> >   =

> =


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 10:16:03 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0845D3A6834;
	Mon, 12 May 2008 10:16:03 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 877403A6834
	for <behave@core3.amsl.com>; Mon, 12 May 2008 10:16:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, 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 jojAva6mtmTo for <behave@core3.amsl.com>;
	Mon, 12 May 2008 10:15:59 -0700 (PDT)
Received: from mail.sipeerior.com (mail.sipeerior.com [128.239.5.131])
	by core3.amsl.com (Postfix) with ESMTP id 8748D3A680A
	for <behave@ietf.org>; Mon, 12 May 2008 10:15:59 -0700 (PDT)
Received: from vuelta.local (unknown [128.239.5.147])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.sipeerior.com (Postfix) with ESMTP id DFE5B505B01;
	Mon, 12 May 2008 13:14:17 -0400 (EDT)
Message-ID: <48287AE5.5010005@sipeerior.com>
Date: Mon, 12 May 2008 13:14:13 -0400
From: Bruce Lowekamp <lowekamp@sipeerior.com>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es>
	<48286CFD.1080204@free.fr>
In-Reply-To: <48286CFD.1080204@free.fr>
Cc: behave@ietf.org, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

R=E9mi Despr=E9s wrote:
> marcelo bagnulo braun wrote :
>> Hi  Remi,
>>
>> the question that comes next is: what happens when we run out of IPv4 =

>> addresses and all the world becomes (in a more or less manner) an =

>> IP-deprived area?
>>
>> Regards, marcelo
>> PS: FWIW i also think that the endpoint independence is a requierement =

>> we must meet, but just want to make sure we all understand its cost
> =

> IMU, it is still possible to avoid the cost of endpoint independence in
> cases where NATs can easily and safely detect that it isn't necessary.
> =

> My proposal for this, following R=E9mi Denis-Courmont's remarks, has beco=
me:
> =


First, is this idea restricted to TCP?  The argument seems to make the =

most sense there.


>   1. NATs SHOULD do end-point INDEPENDENT mapping if packets that
> initiate addresss-port mappings don't have destination ports indicating
> that endpoint DEPENDENT mapping is acceptable.

Why make this a SHOULD?  This should be a MUST.  There's no point in =

writing a draft that requires nothing to be compliant with it.


>   2. In general, NATs MAY also do endpoint INDEPENDENT mapping if
> packets that initiate addresss-port mappings have destination ports
> indicating that endpoint DEPENDENT mapping is acceptable.

That's implicit in rule 1, regardless of whether it's SHOULD or MUST.

>   3. But, where sparing use of public IPv4 addresses is desirable, NATs
> SHOULD use endpoint DEPENDENT mapping if packets that initiate
> addresss-port mappings indicate that endpoint DEPENDENT mapping is
> acceptable.

would be better off saying MAY use dependent mapping in specific cases =

of well known TCP ports < 1024 if address conservation is desirable.

>   2. Destination ports that indicate that endpoint DEPENDENT mapping is
> acceptable are those of: HTTP, SMTP, POP3, NNTP, Telnet, SNMP (and a few
> others, list to be completed)
> =


I doubt most of these are a factor internet-wide other than HTTP, but =

certainly http, pop3, imap, and maybe snmp and ssh are the most common.


> So far, I don't see why this wouldn't work.

For well-known TCP services, I can't think of a strong argument that it =

wouldn't.  I still think this requires a lot more thought.


> =

> IMU, the saving on address-port consumption could be huge in view of =

> examples given by Iljitsch in
> http://www.ietf.org/mail-archive/web/behave/current/msg03821.html.
> =


Of course, the bit torrent example in that email is precisely the =

application that making this type of change is likely to break.  Should =

be OK with the well-known ports below 1024.  However, given that there's =

a common hack of running other protocols on port 80 just because port 80 =

tends not to be filtered, I'm confident this proposal would break some =

applications.  (but breaking that particular hack may not be the most =

evil thing ever done)

Bruce

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 10:32:17 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 91C863A680A;
	Mon, 12 May 2008 10:32:17 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EE3D63A680A
	for <behave@core3.amsl.com>; Mon, 12 May 2008 10:32:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.406
X-Spam-Level: 
X-Spam-Status: No, score=-6.406 tagged_above=-999 required=5
	tests=[AWL=-0.107, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
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 c3ZZcRmPNVSn for <behave@core3.amsl.com>;
	Mon, 12 May 2008 10:32:14 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id EAA313A67EE
	for <behave@ietf.org>; Mon, 12 May 2008 10:32:13 -0700 (PDT)
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 12 May 2008 10:30:41 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m4CHUfac004088; 
	Mon, 12 May 2008 10:30:41 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m4CHUeZb012616;
	Mon, 12 May 2008 17:30:40 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Bruce Lowekamp'" <lowekamp@sipeerior.com>,
	"=?iso-8859-1?Q?'R=E9mi_Denis-Courmont'?=" <remi.denis-courmont@nokia.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com><200805120947.44545.remi.denis-courmont@nokia.com>
	<48286442.8090503@sipeerior.com>
Date: Mon, 12 May 2008 10:30:40 -0700
Message-ID: <03f501c8b455$e65e2ad0$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <48286442.8090503@sipeerior.com>
Thread-Index: Aci0Rk1wrLv7p18GQXS1MgGJUG3HNQADJtuQ
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3598; t=1210613441;
	x=1211477441; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Scalability=20of=20endpoint=
	20independent=20mapping |Sender:=20;
	bh=d52VENjpH0g/Jcd/BQP/L2Taox4yss3dkpZMg0PXk+Y=;
	b=wR1ZOx9K1qnPfVx7JTHDij+vOxZKV5vzsQ/jAYFqFFlkvUFDZNcfoJF/67
	G8NQhr6R5NaI+Jg9Z+FlHooGHlR0M45KvqUzG3UsvddzPYvN5X/XLhfP5fbR
	cm0NeIup65;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

 =


> -----Original Message-----
> From: behave-bounces@ietf.org =

> [mailto:behave-bounces@ietf.org] On Behalf Of Bruce Lowekamp
> Sent: Monday, May 12, 2008 8:38 AM
> To: R=E9mi Denis-Courmont
> Cc: behave@ietf.org
> Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
> =

> I agree.  And even if the hypothetical savings in the number of IPv4 =

> addresses needed for NATs is realized, going to endpoint-dependent =

> mapping would require every major ISP that deploys one of =

> these things =

> to deploy a number of TURN relays since their customers won't =

> be able to =

> connect directly with those behind similar NATs.  So you're trading a =

> lot of bandwidth and machines deployed as relays for a savings of IP =

> addresses.   If you were doing a full voip (or gaming or whatever) =

> deployment, it isn't actually clear to me that you won't need =

> to deploy =

> as many relays  (with public IP addresses) as you =

> theoretically saved by using a symmetric NAT.

All of Iljitsch's examples were for TCP applications.  Thus, I assume
the primary concern is TCP port consumption (rather than UDP port
consumption).  TCP may well be easier to fix, anyway, as it has a 3-way
handshake after which no other host can send data into the TCP flow
anyway.

-d


> Bruce
> =

> =

> R=E9mi Denis-Courmont wrote:
> > Le Friday 09 May 2008 20:01:10 ext Iljitsch van Beijnum, =

> vous avez =E9crit :
> >> Now obviously it makes sense for a NAT-PT (let me call it NAT64 =3D a
> >> NAT that sits between IPv6 clients and IPv4 servers) to =

> conform to the
> >> BEHAVE requirements. However... One of these requirements is that
> >> mappings are endpoint independent. So if I talk to =

> www.google.com with
> >> source port 49152, I don't get to also talk to www.yahoo.com using
> >> source port 49152.
> >>
> >> Unless I'm mistaken, this basically allows the setup of an outgoing
> >> session to be an implicit reservation of the source port for
> >> subsequent incoming sessions, so peer-to-peer applications can work
> >> through the NAT without the need for an explicit hole punching
> >> mechanism.
> > =

> > No.
> > =

> > Whether hole punching is needed depends on the *filtering* =

> behavior. Only if =

> > the filtering is endpoint independent, then hole punching =

> is not needed (but =

> > still a good idea if only for diagnostics). If filtering is =

> endpoint =

> > dependent, hole punching is required. BEHAVE does not =

> preclude either type of =

> > *filtering*.
> > =

> > BEHAVE requires endpoint independent *mapping* so that =

> communication is =

> > possible between two peers when both are NAT'd. With =

> endpoint dependent =

> > mapping (a.k.a. symmetric NATs), a peer needs to =

> communicate to the other =

> > endpoint to determine its own mapping. In other words, both =

> peers need to =

> > know the other one's mapping to learn their own - an =

> obvious chicken-and-egg =

> > deadlock.
> > =

> >> The trouble with this is that it limits the number of =

> active mappings
> >> per public IPv4 in a NAT to ~64k per transport protocol.
> > =

> > I am well aware of that, but endpoint dependent mappings =

> are such a hassle, =

> > that I think it would be a terrible idea to allow it. It =

> would also break =

> > (old-style) STUN, Teredo and ICE/STUNbis.
> > =

> =

> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 10:35:05 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BEBEA3A68C2;
	Mon, 12 May 2008 10:35:05 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 131E43A68C2
	for <behave@core3.amsl.com>; Mon, 12 May 2008 10:35:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.393
X-Spam-Level: 
X-Spam-Status: No, score=-6.393 tagged_above=-999 required=5
	tests=[AWL=-0.094, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
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 vORlfCH-5Xx3 for <behave@core3.amsl.com>;
	Mon, 12 May 2008 10:35:02 -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 7C38A3A67EE
	for <behave@ietf.org>; Mon, 12 May 2008 10:35:02 -0700 (PDT)
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-2.cisco.com with ESMTP; 12 May 2008 10:32:44 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4CHWit7003308; 
	Mon, 12 May 2008 10:32:44 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m4CHWifV016425;
	Mon, 12 May 2008 17:32:44 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "=?iso-8859-1?Q?'R=E9mi_Denis-Courmont'?=" <remi.denis-courmont@nokia.com>,
	<behave@ietf.org>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>
	<4827FA33.8020201@it.uc3m.es>
	<200805121249.11441.remi.denis-courmont@nokia.com>
Date: Mon, 12 May 2008 10:32:44 -0700
Message-ID: <03f601c8b456$300ffb40$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <200805121249.11441.remi.denis-courmont@nokia.com>
Thread-Index: Aci0FWAeZlYjThXdSPe46zmZEQ7ZTgAPFR4g
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3676; t=1210613564;
	x=1211477564; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Scalability=20of=20endpoint=
	20independent=20mapping |Sender:=20;
	bh=NeyEJaX/4gALP0HGhtx4fmSLKOFkkuAEf02Bc0IsGas=;
	b=dxEn2GYcOE0Gpi5q+OzHf2cztVqcQaltMeRDf5Iob5CsxoVTkpPl9w7kTs
	BM0x66XrHxMM3z5xo1ZfKqrYDIXezt4XHzOZex8+j6hK7E9h+8vqa5fpoUzz
	A3TLdv/bUy1iEpcIoqtw8vhOVGSR7GtkUHVY6s+heP2ufq0qxbxXc=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

 =


> -----Original Message-----
> From: R=E9mi Denis-Courmont [mailto:remi.denis-courmont@nokia.com] =

> Sent: Monday, May 12, 2008 2:49 AM
> To: behave@ietf.org
> Cc: ext marcelo bagnulo braun; Dan Wing
> Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
> =

> Le Monday 12 May 2008 11:05:07 ext marcelo bagnulo braun, =

> vous avez =E9crit=A0:
> > but this breaks
> >
> >    REQ-1:  A NAT MUST have an "Endpoint Independent =

> Mapping" behavior
> >       for TCP.
> >
> > described in draft-ietf-behave-tcp-07.txt
> > doesn't it?
> =

> Yes, I think so too.
> =

> This does imply a limit the order of 1,000 users per IP =

> address behind a =

> BEHAVE-compliant translator, in comparison to the order of =

> 10,000 behind =

> an "aggressively" symmetric translator. Such is the cost of =

> end-to-end =

> communication (I don't dare to say end-to-end transparency =

> here). As Iljitsch =

> noted.
> =

> That's assuming well-mannered user applications. It is fairly =

> trivial to mount =

> a DoS against the ports range of a BEHAVE-compliant =

> translator, unless a =

> limited number of port allocations per-user is enforced.
> =

> As it happens, the BEHAVE requirements where written pretty =

> much on purpose. =

> They DO actually solve problems. I believe a certain number =

> of applications =

> benefit from BEHAVE-ish NATs, and matter to a large number of paying =

> customers for large ISPs. In the western world, if these ISPs =

> can allocate =

> one IP per customer today, they should be able to allocate =

> one IP per 500 =

> customers in the foreseeable future.

Waiting until the 3-way handshake completes still allows for TCP
simultaneous open (which is one of the big reasons for that BEHAVE
requirement), and still allows interesting ideas such as the TCP
anycast mechanism described on page 6 of RFC1546, which may not
have been implemented by anybody (due to firewalls and NATs and
TCP stacks not working well with it), but still it is something
that we should not unnecessarily break, either.  My proposal should
work fine with it.  That paragraph of RFC1546 reads:

   The solution to this problem is to only permit anycast addresses as
   the remote address of a TCP SYN segment (without the ACK bit set).  A
   TCP can then initiate a connection to an anycast address.  When the
   SYN-ACK is sent back by the host that received the anycast segment,
   the initiating TCP should replace the anycast address of its peer,
   with the address of the host returning the SYN-ACK.  (The initiating
   TCP can recognize the connection for which the SYN-ACK is destined by
   treating the anycast address as a wildcard address, which matches any
   incoming SYN-ACK segment with the correct destination port and
   address and source port, provided the SYN-ACK's full address,
   including source address, does not match another connection and the
   sequence numbers in the SYN-ACK are correct.)  This approach ensures
   that a TCP, after receiving the SYN-ACK is always communicating with
   only one host.

-d

> Also, in managed networks, BEHAVE-compliance is probably not =

> such a big deal. =

> There, you have firewalls and gateways. And =

> peer-to-peer/end-to-end is not =

> really aimed for. In fact, it's typically fought against.
> =

> =

> Well, scalability may be a problem in IP-deprived areas. If =

> it happens, BEHAVE =

> will not be complied with. Too bad. But I believe "breaking" =

> the current =

> BEHAVE requirements would be even worse overall.
> =

> -- =

> R=E9mi Denis-Courmont

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 10:47:55 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1EE093A688B;
	Mon, 12 May 2008 10:47:55 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C6F7D3A67E1
	for <behave@core3.amsl.com>; Mon, 12 May 2008 10:47:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.32
X-Spam-Level: 
X-Spam-Status: No, score=-1.32 tagged_above=-999 required=5 tests=[AWL=0.029, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_36=0.6,
	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 96jUGll2LjCS for <behave@core3.amsl.com>;
	Mon, 12 May 2008 10:47:52 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id A97B43A680A
	for <behave@ietf.org>; Mon, 12 May 2008 10:47:51 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 417AE3EA11C;
	Mon, 12 May 2008 19:47:35 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id C8FD83EA0D7;
	Mon, 12 May 2008 19:47:34 +0200 (CEST)
Message-ID: <482882B7.2030806@free.fr>
Date: Mon, 12 May 2008 19:47:35 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Bruce Lowekamp <lowekamp@sipeerior.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es>
	<48286CFD.1080204@free.fr> <48287AE5.5010005@sipeerior.com>
In-Reply-To: <48287AE5.5010005@sipeerior.com>
Cc: behave@ietf.org, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Bruce Lowekamp wrote :
> R=E9mi Despr=E9s wrote:

>> My proposal for this, following R=E9mi Denis-Courmont's remarks, has =

>> become:
>>
> =

> First, is this idea restricted to TCP?  The argument seems to make the =

> most sense there.

AFAIK, It doesn't need to be restricted to TCP, but even restricted to =

to TCP it could make a lot of good.

>>   1. NATs SHOULD do end-point INDEPENDENT mapping if packets that
>> initiate addresss-port mappings don't have destination ports indicating
>> that endpoint DEPENDENT mapping is acceptable.
> =

> Why make this a SHOULD?  This should be a MUST.  There's no point in =

> writing a draft that requires nothing to be compliant with it.

I guess you are right.
MUST seems better.


>>   2. In general, NATs MAY also do endpoint INDEPENDENT mapping if
>> packets that initiate addresss-port mappings have destination ports
>> indicating that endpoint DEPENDENT mapping is acceptable.
> =

> That's implicit in rule 1, regardless of whether it's SHOULD or MUST.

I agree that it is not necessary.


>>   3. But, where sparing use of public IPv4 addresses is desirable, NATs
>> SHOULD use endpoint DEPENDENT mapping if packets that initiate
>> addresss-port mappings indicate that endpoint DEPENDENT mapping is
>> acceptable.
> =

> would be better off saying MAY use dependent mapping in specific cases =

> of well known TCP ports < 1024 if address conservation is desirable.

Not sure what you mean.
IMU, no need to change, but may nedd more discussion.


>>   2. Destination ports that indicate that endpoint DEPENDENT mapping is
>> acceptable are those of: HTTP, SMTP, POP3, NNTP, Telnet, SNMP (and a few
>> others, list to be completed)
>>
> =

> I doubt most of these are a factor internet-wide other than HTTP, but =

> certainly http, pop3, imap, and maybe snmp and ssh are the most common.

>> So far, I don't see why this wouldn't work.
> =

> For well-known TCP services, I can't think of a strong argument that it =

> wouldn't.  I still think this requires a lot more thought.

I agree, but IMO that's worth it.


>> IMU, the saving on address-port consumption could be huge in view of =

>> examples given by Iljitsch in
>> http://www.ietf.org/mail-archive/web/behave/current/msg03821.html.
>>
> =

> Of course, the bit torrent example in that email is precisely the =

> application that making this type of change is likely to break.  Should =

> be OK with the well-known ports below 1024.  However, given that there's =

> a common hack of running other protocols on port 80 just because port 80 =

> tends not to be filtered, I'm confident this proposal would break some =

> applications.  (but breaking that particular hack may not be the most =

> evil thing ever done)
Finding how bit torrent would break, if it is, is beyond my current =

knowledge of how it works.
In particular, does it work across restricted cone NATs, and across =

symmetric NATs, and if yes how?


Thanks for your remarks.

BTW, I will be unable to read my emails from tonight to May 20.
If I don'answer quickly to further comments this will be the reason.

Regards.

R=E9mi













_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 12:36:37 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 37DED3A6944;
	Mon, 12 May 2008 12:36:37 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CE07C3A67C1
	for <behave@core3.amsl.com>; Mon, 12 May 2008 12:36:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.622
X-Spam-Level: 
X-Spam-Status: No, score=-1.622 tagged_above=-999 required=5 tests=[AWL=0.327, 
	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 Q+3SNPGEahVB for <behave@core3.amsl.com>;
	Mon, 12 May 2008 12:36:34 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id CFA183A6944
	for <behave@ietf.org>; Mon, 12 May 2008 12:36:33 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 52C523EA0DC;
	Mon, 12 May 2008 21:35:50 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id B81D23EA116;
	Mon, 12 May 2008 21:35:49 +0200 (CEST)
Message-ID: <48289C15.3000102@free.fr>
Date: Mon, 12 May 2008 21:35:49 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@gmail.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es>
	<48286CFD.1080204@free.fr> <48287AE5.5010005@sipeerior.com>
	<482882B7.2030806@free.fr>
	<145B7DFA-E397-4184-8FA6-3C255078509F@muada.com>
In-Reply-To: <145B7DFA-E397-4184-8FA6-3C255078509F@muada.com>
Cc: behave@ietf.org, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Iljitsch van Beijnum wrote :
> On 12 mei 2008, at 19:47, R=E9mi Despr=E9s wrote:

> the default BitTorrent ports are 6881-6889.
> =

>  you'd probably want BitTorrent to be on the list =

> of apps that forego endpoint independence or change the apps to reuse =

> the port.)

Agreed: unless a new fact is unveiled, the bit torrent range of ports =

6881-6889 would be one to be added to the list of those that address =

sparing NATs, in order to practice endpoint independent mapping where it =

doesn't hurt, have to recognize.

> Also, BitTorrent has good IPv4->IPv6 transition properties: as long as a =

> reasonable fraction of the peers is dual stack and they use the DHT, it =

> works because there is no need for every peer to talk to every other peer.
> =

>>> Should
>>> be OK with the well-known ports below 1024.  However, given that there's
>>> a common hack of running other protocols on port 80 just because port 80
>>> tends not to be filtered, I'm confident this proposal would break some
>>> applications.  (but breaking that particular hack may not be the most
>>> evil thing ever done)
> =

>> Finding how bit torrent would break, if it is, is beyond my current
>> knowledge of how it works.
>> In particular, does it work across restricted cone NATs, and across
>> symmetric NATs, and if yes how?
> =

> The main thing that BitTorrent needs to work efficiently is for a host =

> to be able to accept incoming TCP sessions. AFAIK, there is no out of =

> band mechanism to negotiate the setup of specific sessions, just the =

> distribution of addresses/ports on which prospective peers are =

> reachable. I.e., it doesn't support ICE.
It would be appreciated if someone with a thorough knowledge of bit =

torrent could help making sure we work with reality.

Thanks.

R=E9mi
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 12:52:58 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6691A3A68E0;
	Mon, 12 May 2008 12:52:58 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 648F628C28A
	for <behave@core3.amsl.com>; Mon, 12 May 2008 12:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, 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 eV4VHS7F-san for <behave@core3.amsl.com>;
	Mon, 12 May 2008 12:52:53 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.170])
	by core3.amsl.com (Postfix) with ESMTP id 43DC528C296
	for <behave@ietf.org>; Mon, 12 May 2008 12:52:53 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so2575203wfd.31
	for <behave@ietf.org>; Mon, 12 May 2008 12:52:26 -0700 (PDT)
Received: by 10.142.255.14 with SMTP id c14mr3417607wfi.296.1210621946736;
	Mon, 12 May 2008 12:52:26 -0700 (PDT)
Received: from ?192.168.2.4? ( [98.207.97.133])
	by mx.google.com with ESMTPS id 30sm1495557wfd.1.2008.05.12.12.52.24
	(version=SSLv3 cipher=RC4-MD5); Mon, 12 May 2008 12:52:25 -0700 (PDT)
Message-ID: <48289FF4.3030203@quinthar.com>
Date: Mon, 12 May 2008 12:52:20 -0700
From: David Barrett <dbarrett@quinthar.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080505)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es>	<48286CFD.1080204@free.fr>
	<48287AE5.5010005@sipeerior.com>	<482882B7.2030806@free.fr>	<145B7DFA-E397-4184-8FA6-3C255078509F@muada.com>
	<48289C15.3000102@free.fr>
In-Reply-To: <48289C15.3000102@free.fr>
Cc: behave@ietf.org, Dan Wing <dwing@cisco.com>,
	Iljitsch van Beijnum <iljitsch@gmail.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

R=E9mi Despr=E9s wrote:
> Iljitsch van Beijnum wrote :
>> On 12 mei 2008, at 19:47, R=E9mi Despr=E9s wrote:
> =

>> the default BitTorrent ports are 6881-6889.

I think the default depends on the BitTorrent client, and is perhaps =

even randomly selected by some clients.  For example, I'm using =

Transmission on Ubuntu and it's using 51413 for incoming TCP.

Also, the torrent protocol doesn't support NAT penetration at all: peers =

establish unsolicited TCP connections with other peers.  So if you can't =

accept incoming TCP you can only access the subset of peers that do -- =

NAT'd peers can't talk to other NAT'd peers at all, not even =

fullcone/fullcone.  (Unless one uses UPnP or manually establishes a port =

forward, that is.)

-david


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 13:06:29 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AF8B13A67C1;
	Mon, 12 May 2008 13:06:29 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0256F3A688B
	for <behave@core3.amsl.com>; Mon, 12 May 2008 13:06:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, 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 sxfxxq-UMugF for <behave@core3.amsl.com>;
	Mon, 12 May 2008 13:06:26 -0700 (PDT)
Received: from mail.sipeerior.com (mail.sipeerior.com [128.239.5.131])
	by core3.amsl.com (Postfix) with ESMTP id 0E9553A67A2
	for <behave@ietf.org>; Mon, 12 May 2008 13:06:26 -0700 (PDT)
Received: from vuelta.local (unknown [128.239.5.147])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.sipeerior.com (Postfix) with ESMTP id 7E5E2505B0B;
	Mon, 12 May 2008 16:06:23 -0400 (EDT)
Message-ID: <4828A33E.1080700@sipeerior.com>
Date: Mon, 12 May 2008 16:06:22 -0400
From: Bruce Lowekamp <lowekamp@sipeerior.com>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es>
	<48286CFD.1080204@free.fr> <48287AE5.5010005@sipeerior.com>
	<482882B7.2030806@free.fr>
	<145B7DFA-E397-4184-8FA6-3C255078509F@muada.com>
	<48289C15.3000102@free.fr>
In-Reply-To: <48289C15.3000102@free.fr>
Cc: behave@ietf.org, Dan Wing <dwing@cisco.com>,
	Iljitsch van Beijnum <iljitsch@gmail.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

R=E9mi Despr=E9s wrote:
> Iljitsch van Beijnum wrote :
>> On 12 mei 2008, at 19:47, R=E9mi Despr=E9s wrote:
> =

>> the default BitTorrent ports are 6881-6889.
>>
>>  you'd probably want BitTorrent to be on the list of apps that forego =

>> endpoint independence or change the apps to reuse the port.)
> =

> Agreed: unless a new fact is unveiled, the bit torrent range of ports =

> 6881-6889 would be one to be added to the list of those that address =

> sparing NATs, in order to practice endpoint independent mapping where it =

> doesn't hurt, have to recognize.
> =


Um, I'm confused.  Did you mean *dependent* mapping in that last =

sentence?  My understanding was that the proposal was to have a set of =

ports for which dependent mapping was acceptable (such as http).  Since =

6881-6889 are not one of those ports used by well-known safe protocols, =

they would of course have independent mapping.

I'm concerned that last paragraph is introducing a slippery slope.  One =

of the reasons to have behave-compliant NATs is so that every NAT =

doesn't have to be upgraded every time a new application comes out. =

Regardless of the ports current bittorrent applications are using now =

and regardless of whether they currently support ICE, a behave-compliant =

NAT should not break new applications.

I can see an argument that it might be OK to allow dependent mapping in =

a situation where it is known not to hurt applications (http).  But the =

default still needs to be independent mapping, otherwise applications break.



>> The main thing that BitTorrent needs to work efficiently is for a host =

>> to be able to accept incoming TCP sessions. AFAIK, there is no out of =

>> band mechanism to negotiate the setup of specific sessions, just the =

>> distribution of addresses/ports on which prospective peers are =

>> reachable. I.e., it doesn't support ICE.
> It would be appreciated if someone with a thorough knowledge of bit =

> torrent could help making sure we work with reality.

Somewhat, but the goal isn't to achieve compatibility with the 10 =

applications we happen to care about at the moment.  It's to make sure =

new applications can be developed that work on the internet.

Bruce
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 13:42:44 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AAD173A6B9C;
	Mon, 12 May 2008 13:42:44 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ACBDE3A6B1E
	for <behave@core3.amsl.com>; Mon, 12 May 2008 13:42:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.641
X-Spam-Level: 
X-Spam-Status: No, score=-1.641 tagged_above=-999 required=5 tests=[AWL=0.308, 
	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 7Rn9sAZ5odC7 for <behave@core3.amsl.com>;
	Mon, 12 May 2008 13:42:42 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id AC2003A6B9C
	for <behave@ietf.org>; Mon, 12 May 2008 13:42:41 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 1FC843EA118;
	Mon, 12 May 2008 22:42:39 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id B7F3C3EA0AE;
	Mon, 12 May 2008 22:42:38 +0200 (CEST)
Message-ID: <4828ABBE.9010201@free.fr>
Date: Mon, 12 May 2008 22:42:38 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Bruce Lowekamp <lowekamp@sipeerior.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es>
	<48286CFD.1080204@free.fr> <48287AE5.5010005@sipeerior.com>
	<482882B7.2030806@free.fr>
	<145B7DFA-E397-4184-8FA6-3C255078509F@muada.com>
	<48289C15.3000102@free.fr> <4828A33E.1080700@sipeerior.com>
In-Reply-To: <4828A33E.1080700@sipeerior.com>
Cc: behave@ietf.org, Dan Wing <dwing@cisco.com>,
	Iljitsch van Beijnum <iljitsch@gmail.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Bruce Lowekamp wrote :
> R=E9mi Despr=E9s wrote:

>> Agreed: unless a new fact is unveiled, the bit torrent range of ports =

>> 6881-6889 would be one to be added to the list of those that address =

>> sparing NATs, in order to practice endpoint independent mapping where =

>> it doesn't hurt, have to recognize.
>>
> =

> Um, I'm confused.  Did you mean *dependent* mapping in that last =

> sentence?

Yes, "dependent" was the right word. (Sorry for that.)

> My understanding was that the proposal was to have a set of =

> ports for which dependent mapping was acceptable (such as http).  Since =

> 6881-6889 are not one of those ports used by well-known safe protocols, =

> they would of course have independent mapping.

It seems to me that dependent mapping for bit torrent, if reasonably =

simple to ensure, must remain a goal.
If a host behind a shared NAT establishes many connections (with non =

natted peers since this is the case), it is very useful to avoid that =

each connection consumes a full address-port pair.
> =

> I'm concerned that last paragraph is introducing a slippery slope.  One =

> of the reasons to have behave-compliant NATs is so that every NAT =

> doesn't have to be upgraded every time a new application comes out. =

> Regardless of the ports current bittorrent applications are using now =

> and regardless of whether they currently support ICE, a behave-compliant =

> NAT should not break new applications.

An improved combination could be:
  - If the packet that initiates the mapping has a well known =

destination port (< 1024), then dependent mapping is restricted to a =

short list (HTTP plus a few others).
  - If the destination port is beyond 1023, then dependent mapping is =

freely practiced.

New applications for which INdependent mapping is required would have to =

use ports below 1024.

Other new applications would preferably use ports in the registered port =

range (1024 to 49151).


R=E9mi

* Sorry I won't be able to pursue this (interesting and hopefully =

productive) discussion for one week.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 13:52:53 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 004493A6BA3;
	Mon, 12 May 2008 13:52:53 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 99FE53A67C0
	for <behave@core3.amsl.com>; Mon, 12 May 2008 13:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, 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 WntrDownDIZC for <behave@core3.amsl.com>;
	Mon, 12 May 2008 13:52:49 -0700 (PDT)
Received: from mail.sipeerior.com (mail.sipeerior.com [128.239.5.131])
	by core3.amsl.com (Postfix) with ESMTP id A34CE3A6BA9
	for <behave@ietf.org>; Mon, 12 May 2008 13:52:49 -0700 (PDT)
Received: from vuelta.local (unknown [128.239.5.147])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.sipeerior.com (Postfix) with ESMTP id 7D7F9505B1B;
	Mon, 12 May 2008 16:52:44 -0400 (EDT)
Message-ID: <4828AE1B.9040901@sipeerior.com>
Date: Mon, 12 May 2008 16:52:43 -0400
From: Bruce Lowekamp <lowekamp@sipeerior.com>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es>
	<48286CFD.1080204@free.fr> <48287AE5.5010005@sipeerior.com>
	<482882B7.2030806@free.fr>
	<145B7DFA-E397-4184-8FA6-3C255078509F@muada.com>
	<48289C15.3000102@free.fr> <4828A33E.1080700@sipeerior.com>
	<4828ABBE.9010201@free.fr>
In-Reply-To: <4828ABBE.9010201@free.fr>
Cc: behave@ietf.org, Dan Wing <dwing@cisco.com>,
	Iljitsch van Beijnum <iljitsch@gmail.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

R=E9mi Despr=E9s wrote:
> Bruce Lowekamp wrote :
>> R=E9mi Despr=E9s wrote:
> =

>>> Agreed: unless a new fact is unveiled, the bit torrent range of ports =

>>> 6881-6889 would be one to be added to the list of those that address =

>>> sparing NATs, in order to practice endpoint independent mapping where =

>>> it doesn't hurt, have to recognize.
>>>
>>
>> Um, I'm confused.  Did you mean *dependent* mapping in that last =

>> sentence?
> =

> Yes, "dependent" was the right word. (Sorry for that.)
> =

>> My understanding was that the proposal was to have a set of ports for =

>> which dependent mapping was acceptable (such as http).  Since =

>> 6881-6889 are not one of those ports used by well-known safe =

>> protocols, they would of course have independent mapping.
> =

> It seems to me that dependent mapping for bit torrent, if reasonably =

> simple to ensure, must remain a goal.
> If a host behind a shared NAT establishes many connections (with non =

> natted peers since this is the case), it is very useful to avoid that =

> each connection consumes a full address-port pair.

Your proposed solution prevents anyone behind a nat from serving pieces =

of the file.  You then suggest that all of these connections are going =

to be with non-NATted peers, but your entire scenario is based on the =

idea that it's going to be needed in a time when IPv4 address space is =

completely exhausted and being reclaimed as ASes are converting to IPv6. =

   Which means that these non-NATed peers are going to be much scarcer =

than they are now.   Which means that you need to have peers behind NATs =

serving pieces.  Which means they need to have independent mapping.

So, no, bittorrent is exactly the application you DON'T want to have =

dependent mapping for.


>>
>> I'm concerned that last paragraph is introducing a slippery slope.  =

>> One of the reasons to have behave-compliant NATs is so that every NAT =

>> doesn't have to be upgraded every time a new application comes out. =

>> Regardless of the ports current bittorrent applications are using now =

>> and regardless of whether they currently support ICE, a =

>> behave-compliant NAT should not break new applications.
> =

> An improved combination could be:
>  - If the packet that initiates the mapping has a well known destination =

> port (< 1024), then dependent mapping is restricted to a short list =

> (HTTP plus a few others).
>  - If the destination port is beyond 1023, then dependent mapping is =

> freely practiced.
> =


no.  you can't make dependent mapping the default.  Why not just go full =

symmetric and break every application that tries to allow inbound =

connections?


> New applications for which INdependent mapping is required would have to =

> use ports below 1024.

Now that is asking for both port preservation and root privilege (on a =

lot of platforms) for p2p applications.


Bruce
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 14:06:52 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A7E4428C0E6;
	Mon, 12 May 2008 14:06:52 -0700 (PDT)
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 65534)
	id 61B3528C2A1; Mon, 12 May 2008 12:02:25 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Old-Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C71CF3A67C1
	for <behave@core3.amsl.com>; Mon, 12 May 2008 11:53:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, 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 9AOuuPNYXq38 for <behave@core3.amsl.com>;
	Mon, 12 May 2008 11:53:39 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159])
	by core3.amsl.com (Postfix) with ESMTP id 32BDC28C124
	for <behave@ietf.org>; Mon, 12 May 2008 11:53:37 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id d23so2047848fga.41
	for <behave@ietf.org>; Mon, 12 May 2008 11:52:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:cc:message-id:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer:from;
	bh=7ALZ2xZ1M423ZsTGDAhYUj+1kiXmbKhed2nJ6OCRyMM=;
	b=dZnzKDXAFlXS2DbzdkYkB+IJg3+87C8FB8XSV1ejsu93GNrSnpl+46yzkxwY6fOF2xStt6FurMnpUGA7I9nqEh5Uyd023g/rBrmaYUQB4rzchn/RM8DXxnrjgdFz1BUOVAQ04e6+5iYlPS5b8cM8AypXhmkvJ8v9uNXxhl36LBM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=cc:message-id:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer:from;
	b=WzBwWZKI2mQhyVnD4x9zR46Vd/TdiQhJtHjWVi7OX6T4hiqy0rfHLU9pCeeAwOLh5f/u2QNUyAVrA4al27JGy4jgozBwYXXvW8Dm18pxdsdFVpd5haPH4KqmLNNf4VKlYGBqlnX4exDPhEhuZcfeWpMWCqq1X0z5cLqgdhGYZcg=
Received: by 10.86.76.16 with SMTP id y16mr845609fga.36.1210618353234;
	Mon, 12 May 2008 11:52:33 -0700 (PDT)
Received: from ?192.168.2.13? ( [89.7.138.167])
	by mx.google.com with ESMTPS id d6sm7030399fga.2.2008.05.12.11.52.30
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Mon, 12 May 2008 11:52:32 -0700 (PDT)
Message-Id: <145B7DFA-E397-4184-8FA6-3C255078509F@muada.com>
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <482882B7.2030806@free.fr>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 12 May 2008 20:52:29 +0200
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es>
	<48286CFD.1080204@free.fr> <48287AE5.5010005@sipeerior.com>
	<482882B7.2030806@free.fr>
X-Mailer: Apple Mail (2.919.2)
From: Iljitsch van Beijnum <iljitsch@gmail.com>
X-TMDA-Confirmed: Mon, 12 May 2008 12:02:26 -0700
X-Mailman-Approved-At: Mon, 12 May 2008 14:06:51 -0700
Cc: behave@ietf.org, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 12 mei 2008, at 19:47, R=E9mi Despr=E9s wrote:

>>> IMU, the saving on address-port consumption could be huge in view of
>>> examples given by Iljitsch in
>>> http://www.ietf.org/mail-archive/web/behave/current/msg03821.html.

>> Of course, the bit torrent example in that email is precisely the
>> application that making this type of change is likely to break.

How?? Even assuming that the BitTorrent application uses endpoint  =

indepedent mapping as an implicit NAT hole punching technique (which I  =

haven't encountered, they usually use UPnP/NAT-PMP or manual mappings)  =

the default BitTorrent ports are 6881-6889.

(Note that because BitTorrent sets up A LOT of sessions (configurable,  =

but certainly dozens and more than 100 or 200 is possible) and keeps  =

trying to set up new sessions, it would use up endpoint independent  =

port numbers really fast so you'd probably want BitTorrent to be on  =

the list of apps that forego endpoint independence or change the apps  =

to reuse the port.)

Also, BitTorrent has good IPv4->IPv6 transition properties: as long as  =

a reasonable fraction of the peers is dual stack and they use the DHT,  =

it works because there is no need for every peer to talk to every  =

other peer.

>> Should
>> be OK with the well-known ports below 1024.  However, given that  =

>> there's
>> a common hack of running other protocols on port 80 just because  =

>> port 80
>> tends not to be filtered, I'm confident this proposal would break  =

>> some
>> applications.  (but breaking that particular hack may not be the most
>> evil thing ever done)

> Finding how bit torrent would break, if it is, is beyond my current
> knowledge of how it works.
> In particular, does it work across restricted cone NATs, and across
> symmetric NATs, and if yes how?

The main thing that BitTorrent needs to work efficiently is for a host  =

to be able to accept incoming TCP sessions. AFAIK, there is no out of  =

band mechanism to negotiate the setup of specific sessions, just the  =

distribution of addresses/ports on which prospective peers are  =

reachable. I.e., it doesn't support ICE.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 14:06:54 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EF0E83A685B;
	Mon, 12 May 2008 14:06:53 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B5EA328C29F
	for <behave@core3.amsl.com>; Mon, 12 May 2008 12:59:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075, 
	BAYES_00=-2.599]
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 WRHsWDDm8D8J for <behave@core3.amsl.com>;
	Mon, 12 May 2008 12:59:54 -0700 (PDT)
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184])
	by core3.amsl.com (Postfix) with ESMTP id 7784128C29C
	for <behave@ietf.org>; Mon, 12 May 2008 12:59:53 -0700 (PDT)
Received: by nf-out-0910.google.com with SMTP id f5so1169326nfh.39
	for <behave@ietf.org>; Mon, 12 May 2008 12:59:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer;
	bh=Pd5Zd32VDOA2vli9OgH74hOIXefzMYx+pI+9vd8yoAQ=;
	b=YFXbWkbi6vYA4nrEBfMLevnoaj6/Cm+44aSsSPMb7txldvweF0aF2H+C4eNnJR5k8dAjl1bZfwTPUdDhqteCCl46YUtfRJYhR5dMl7tR/GqTSYbBzIF7eZbPD0w0Ab7blvRwVAAqyr7l8vbjDshWczZOBPUV1Vh/cKeEk5HvgTQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer;
	b=BV4RTZvXv21x4eyZnbAw7zSrq9uY/TFkBx6S9gtW7/6GjDjiEiMi2HHUJLmgA7+pflThuzFg9kk0pZxu/5tZ4Q22woEObkDNbaeKC6Qc5bJ72Ec671CeOJmfwNB2N2CDuTGQVT5SxZHzZzxyOSD51j11SOAFaMotGvei0GLYkFU=
Received: by 10.86.76.16 with SMTP id y16mr14980771fga.60.1210622388142;
	Mon, 12 May 2008 12:59:48 -0700 (PDT)
Received: from ?192.168.2.13? ( [89.7.138.167])
	by mx.google.com with ESMTPS id 3sm7072370fge.3.2008.05.12.12.59.47
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Mon, 12 May 2008 12:59:47 -0700 (PDT)
Message-Id: <6DC78D1D-A04A-46F6-B08F-97DB97DE9260@gmail.com>
From: Iljitsch van Beijnum <iljitsch@gmail.com>
To: David Barrett <dbarrett@quinthar.com>
In-Reply-To: <48289FF4.3030203@quinthar.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 12 May 2008 21:59:45 +0200
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es>	<48286CFD.1080204@free.fr>
	<48287AE5.5010005@sipeerior.com>	<482882B7.2030806@free.fr>	<145B7DFA-E397-4184-8FA6-3C255078509F@muada.com>
	<48289C15.3000102@free.fr> <48289FF4.3030203@quinthar.com>
X-Mailer: Apple Mail (2.919.2)
X-Mailman-Approved-At: Mon, 12 May 2008 14:06:51 -0700
Cc: behave@ietf.org, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 12 mei 2008, at 21:52, David Barrett wrote:

>>> the default BitTorrent ports are 6881-6889.

> I think the default depends on the BitTorrent client, and is perhaps
> even randomly selected by some clients.  For example, I'm using
> Transmission on Ubuntu and it's using 51413 for incoming TCP.

It's very common to use non-standard ports. Some BitTorrent  
communities even block the default ports in an effort to obscure  
BitTorrent use against prying service provider eyes.

> Also, the torrent protocol doesn't support NAT penetration at all:  
> peers
> establish unsolicited TCP connections with other peers.  So if you  
> can't
> accept incoming TCP you can only access the subset of peers that do --
> NAT'd peers can't talk to other NAT'd peers at all, not even
> fullcone/fullcone.  (Unless one uses UPnP or manually establishes a  
> port
> forward, that is.)

Right. However, even with no NAT traversal BitTorrent works because  
there are enough peers that can accept incoming connections. It's just  
much faster if you set things up so that incoming connections work  
because you can talk to more peers and more easily to other peers.

(Please note that this message probably won't make it to the list.)
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 18:54:24 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 84CCC3A687E;
	Mon, 12 May 2008 18:54:24 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4866C3A687E
	for <behave@core3.amsl.com>; Mon, 12 May 2008 18:54:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.399
X-Spam-Level: 
X-Spam-Status: No, score=-6.399 tagged_above=-999 required=5
	tests=[AWL=-0.100, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
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 yS+1QKiKAOFS for <behave@core3.amsl.com>;
	Mon, 12 May 2008 18:54:21 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by core3.amsl.com (Postfix) with ESMTP id 8D32F3A6803
	for <behave@ietf.org>; Mon, 12 May 2008 18:54:21 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,476,1204531200"; d="scan'208";a="26555650"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-5.cisco.com with ESMTP; 12 May 2008 18:54:19 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m4D1sJUP026268; 
	Mon, 12 May 2008 18:54:19 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m4D1sJt9014903;
	Tue, 13 May 2008 01:54:19 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "=?iso-8859-1?Q?'R=E9mi_Despr=E9s'?=" <remi.despres@free.fr>,
	"'marcelo bagnulo braun'" <marcelo@it.uc3m.es>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com><000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es><200805121249.11441.remi.denis-courmont@nokia.com><48281927.4020708@it.uc3m.es>
	<48286CFD.1080204@free.fr>
Date: Mon, 12 May 2008 18:54:18 -0700
Message-ID: <001701c8b49c$41f03be0$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <48286CFD.1080204@free.fr>
Thread-Index: Aci0S1rcf5X3c+YsQiedOkl3S6MklQAUKXMg
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=373; t=1210643659; x=1211507659;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Scalability=20of=20endpoint=
	20independent=20mapping |Sender:=20;
	bh=9NzwBP83gNtMTIofw3PX3dstB68jcf87WHHxY+KnyFE=;
	b=lER8wV2TshQEKNi4JngK8LzEbJ/Yr/17UxQECg6cgNP4Q06uZ3jnalE+ON
	221tIPafuNWMvUaLWGgKdo9STo4bv760p6V63Y/a37tNdDmq/MlgS++irAnj
	00UktRmOoM;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

>   2. Destination ports that indicate that endpoint DEPENDENT 
> mapping is
> acceptable are those of: HTTP, SMTP, POP3, NNTP, Telnet, SNMP 
> (and a few
> others, list to be completed)
> 
> So far, I don't see why this wouldn't work.

It won't work because it will be impossible to reach closure on a finite set
of port numbers for this special behavior.

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 23:24:40 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC6443A6A29;
	Mon, 12 May 2008 23:24:40 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C27B43A6A29
	for <behave@core3.amsl.com>; Mon, 12 May 2008 23:24:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.835
X-Spam-Level: 
X-Spam-Status: No, score=-5.835 tagged_above=-999 required=5 tests=[AWL=0.464, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 7LJE6cMJDf8C for <behave@core3.amsl.com>;
	Mon, 12 May 2008 23:24:38 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id C46FA3A6859
	for <behave@ietf.org>; Mon, 12 May 2008 23:24:37 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m4D6Ng3F003102; Tue, 13 May 2008 09:23:52 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 13 May 2008 09:23:51 +0300
Received: from esdhcp041113.research.nokia.com ([172.21.41.113]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 13 May 2008 09:23:50 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: behave@ietf.org
Date: Tue, 13 May 2008 09:25:09 +0300
User-Agent: KMail/1.9.9
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
	<4827FA33.8020201@it.uc3m.es>
	<03cb01c8b451$b32583b0$c3f0200a@cisco.com>
In-Reply-To: <03cb01c8b451$b32583b0$c3f0200a@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805130925.10270.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 13 May 2008 06:23:50.0943 (UTC)
	FILETIME=[E8EA82F0:01C8B4C1]
X-Nokia-AV: Clean
Cc: ext Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Le Monday 12 May 2008 20:00:36 ext Dan Wing, vous avez =E9crit=A0:
> Yes.
>
> But does re-using the same public TCP port, after the 3-way handshake
> completes, cause something to break?  It feels pretty safe to me.

In theory, ICE-TCP as it currently is.
Whether this is a real issue is a different matter.

-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 12 23:29:35 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 119F23A6835;
	Mon, 12 May 2008 23:29:35 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D18593A6835
	for <behave@core3.amsl.com>; Mon, 12 May 2008 23:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.873
X-Spam-Level: 
X-Spam-Status: No, score=-5.873 tagged_above=-999 required=5 tests=[AWL=0.426, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 4OdSPiUg2s5C for <behave@core3.amsl.com>;
	Mon, 12 May 2008 23:29:33 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id A60CB3A67A5
	for <behave@ietf.org>; Mon, 12 May 2008 23:29:32 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m4D6RpMi022150; Tue, 13 May 2008 09:28:11 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 13 May 2008 09:28:08 +0300
Received: from esdhcp041113.research.nokia.com ([172.21.41.113]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 13 May 2008 09:28:08 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: "ext Dan Wing" <dwing@cisco.com>
Date: Tue, 13 May 2008 09:29:27 +0300
User-Agent: KMail/1.9.9
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
	<200805121249.11441.remi.denis-courmont@nokia.com>
	<03f601c8b456$300ffb40$c3f0200a@cisco.com>
In-Reply-To: <03f601c8b456$300ffb40$c3f0200a@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805130929.28070.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 13 May 2008 06:28:08.0549 (UTC)
	FILETIME=[82761150:01C8B4C2]
X-Nokia-AV: Clean
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Le Monday 12 May 2008 20:32:44 ext Dan Wing, vous avez =E9crit=A0:
> Waiting until the 3-way handshake completes still allows for TCP
> simultaneous open (which is one of the big reasons for that BEHAVE
> requirement), and still allows interesting ideas such as the TCP
> anycast mechanism described on page 6 of RFC1546, which may not
> have been implemented by anybody (due to firewalls and NATs and
> TCP stacks not working well with it), but still it is something
> that we should not unnecessarily break, either.  My proposal should
> work fine with it.  That paragraph of RFC1546 reads:

Waiting until the 3-way handshake does not break TCP-SO per se. But it brea=
ks =

TCP Binding Discovery, which renders TCP-SO pretty unusable. Or did I miss =

something?

-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May 13 00:47:20 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1665E3A6883;
	Tue, 13 May 2008 00:47:20 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9BCE13A6835
	for <behave@core3.amsl.com>; Tue, 13 May 2008 00:47:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.807
X-Spam-Level: 
X-Spam-Status: No, score=-3.807 tagged_above=-999 required=5
	tests=[AWL=-0.045, BAYES_00=-2.599, RCVD_BAD_ID=2.837,
	RCVD_IN_DNSWL_MED=-4]
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 ftIhgWieEsBX for <behave@core3.amsl.com>;
	Tue, 13 May 2008 00:47:17 -0700 (PDT)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131])
	by core3.amsl.com (Postfix) with ESMTP id 0C5613A67A5
	for <behave@ietf.org>; Tue, 13 May 2008 00:47:16 -0700 (PDT)
Received: from dummyhost0.it.uc3m.es (dummyhost15.it.uc3m.es 
	[163.117.139.42])by smtp01.uc3m.es (Postfix) with ESMTP id 1550F5F1F46;
	Tue, 13 May 2008 09:46:22 +0200 (CEST)
Message-ID: <4829474D.7060106@it.uc3m.es>
Date: Tue, 13 May 2008 09:46:21 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com> 
	<081d01c8b2db$54fa9770$c3f0200a@cisco.com> <4826F926.80404@it.uc3m.es> 
	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>
	<4827FA33.8020201@it.uc3m.es> 
	<03cb01c8b451$b32583b0$c3f0200a@cisco.com>
In-Reply-To: <03cb01c8b451$b32583b0$c3f0200a@cisco.com>
X-imss-version: 2.050
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-24.4638 TC:1F TRN:63 TV:5.5.1026(15906.005)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Dan Wing escribi=F3:
>  =

>
>   =

>> -----Original Message-----
>> From: marcelo bagnulo braun [mailto:marcelo@it.uc3m.es] =

>> Sent: Monday, May 12, 2008 1:05 AM
>> To: Dan Wing
>> Cc: 'Iljitsch van Beijnum'; behave@ietf.org
>> Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
>>
>> but this breaks
>>
>>    REQ-1:  A NAT MUST have an "Endpoint Independent Mapping" behavior
>>       for TCP.
>>
>>  =

>> described in draft-ietf-behave-tcp-07.txt
>>
>> doesn't it?
>>     =

>
> Yes.
>
> But does re-using the same public TCP port, after the 3-way handshake
> completes, cause something to break?  It feels pretty safe to me.
>   =

the connection will not break, agree
The problem i guess is that you will need to always use TURN relay to =

receive incoming TCP connections and that seems to be not the best option.

Having endpoint independent mappings for TCP would allow internal hosts =

to receive incoming communications without turn relay.


Regards, marcelo


> -d
>
>
>   =

>> Dan Wing escribi=F3:
>>     =

>>> Thanks for explaining.
>>>
>>> A reasonable approach is for a NAT to wait until a TCP =

>>> connection has been
>>> established (3-way handshake completed), and then allow =

>>> re-using that same
>>> public TCP port for a new connection to another remote host.
>>>
>>> -d
>>>
>>>
>>>   =

>>>       =

>>>> -----Original Message-----
>>>> From: marcelo bagnulo braun [mailto:marcelo@it.uc3m.es] =

>>>> Sent: Sunday, May 11, 2008 6:48 AM
>>>> To: Dan Wing
>>>> Cc: 'Iljitsch van Beijnum'; behave@ietf.org
>>>> Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
>>>>
>>>> Hi Dan,
>>>>
>>>> I think Iljitsch is talking about the same scenario
>>>>
>>>> Consider a host H1 behind a nat which has a single public =

>>>>         =

>> address T.
>>     =

>>>> Suppose H1 initiates a communications towards an external =

>>>> host H2 at port w.
>>>>
>>>> So, packet from H1 to the NAT has, source (H1,v) and =

>>>> destination (H2,w)
>>>>
>>>> Now, when the packet is received at the NAT is creates a mapping
>>>> (H1,v) <->(T,u) and the nat sends the packet with source (T,u) and =

>>>> destination (H2,w)
>>>>
>>>> Now, suppose another host H3 initiates a communication toward =

>>>> a node H4 =

>>>> at port j.
>>>> The packet from H3 towards the nat has source (H3,i) and =

>>>> estiantion (H4,j)
>>>>
>>>> when the packet from He reaches the NAT, does the NAT can crate a =

>>>> mapping (H3,i)<->(T,u)
>>>>
>>>> As i understand it, if we want to have endpoint =

>>>>         =

>> independent mapping, =

>>     =

>>>> this is not possible (this is so, because if later on H1 =

>>>> sends a packet =

>>>> towards H4 at port j, and we want to use the same mapping H1 =

>>>> is already =

>>>> using, we would end up in a conflict)
>>>>
>>>> So, this basically means, that when the mapping for H1 (H1,v) =

>>>> <->(T,u) =

>>>> is created in the NAT, the transport address (T,u) cannot =

>>>>         =

>> be used for =

>>     =

>>>> ANY other rmapping (cause needs to be reserved for future =

>>>>         =

>> potential =

>>     =

>>>> communications of H1 with other destiantions.
>>>>
>>>> So basically with endpoint independent mappings, each internally =

>>>> initiated communication eats up one port of the nat, reducing =

>>>> the number =

>>>> of simultaneous communications the NAT can handle. If we =

>>>>         =

>> had address =

>>     =

>>>> dependent mapping, the mapping takes into account the destination =

>>>> address also, so even if you may need more than one =

>>>>         =

>> mapping when the =

>>     =

>>>> same source transport address is used for two different external =

>>>> destinations, the NAT does not needs to reserve the port =

>>>> exclusively for =

>>>> the internal source address, so it is likely that a better =

>>>> usage of port =

>>>> range of the nat is achieved.
>>>>
>>>>
>>>> I mean, this is the price we need to pay for endpoint independence
>>>>
>>>> Am i missing something?
>>>>
>>>> Regards, marcelo
>>>>
>>>>
>>>>
>>>>
>>>> Dan Wing escribi=F3:
>>>>     =

>>>>         =

>>>>>  =

>>>>>   =

>>>>>       =

>>>>>           =

>>>>>> What I'm hoping for is that it would be possible to tighten the  =

>>>>>> requirements such that we get closer to reserving ports for  =

>>>>>> applications that really need reserved ports and get to =

>>>>>>         =

>>>>>>             =

>>>> reuse ports  =

>>>>     =

>>>>         =

>>>>>> for client-server applications so that a =

>>>>>>             =

>> BEHAVE-compliant NAT can  =

>>     =

>>>>>> support a much larger user base with the same number of =

>>>>>>         =

>>>>>>             =

>>>> public IPv4  =

>>>>     =

>>>>         =

>>>>>> addresses as these addresses start to run out.
>>>>>>     =

>>>>>>         =

>>>>>>             =

>>>>> I don't understand the relationship between endpoint =

>>>>>       =

>>>>>           =

>>>> independent mapping
>>>>     =

>>>>         =

>>>>> and the desire to free up the ports earlier.   I think =

>>>>>           =

>> you are only =

>>     =

>>>>> really asking for the NAT's TCP TIME_WAIT to be short.
>>>>>
>>>>> -d
>>>>>
>>>>> _______________________________________________
>>>>> Behave mailing list
>>>>> Behave@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/behave
>>>>>
>>>>>   =

>>>>>       =

>>>>>           =

>>>   =

>>>       =

>
>
>   =


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May 13 00:51:49 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C159128C27C;
	Tue, 13 May 2008 00:51:49 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ECEBC28C27C
	for <behave@core3.amsl.com>; Tue, 13 May 2008 00:51:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.799
X-Spam-Level: 
X-Spam-Status: No, score=-3.799 tagged_above=-999 required=5
	tests=[AWL=-0.037, BAYES_00=-2.599, RCVD_BAD_ID=2.837,
	RCVD_IN_DNSWL_MED=-4]
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 tJSaxBG+m60B for <behave@core3.amsl.com>;
	Tue, 13 May 2008 00:51:46 -0700 (PDT)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131])
	by core3.amsl.com (Postfix) with ESMTP id 75B9E3A6815
	for <behave@ietf.org>; Tue, 13 May 2008 00:51:46 -0700 (PDT)
Received: from dummyhost0.it.uc3m.es (dummyhost15.it.uc3m.es 
	[163.117.139.42])by smtp01.uc3m.es (Postfix) with ESMTP id 1F62A5F249D;
	Tue, 13 May 2008 09:50:44 +0200 (CEST)
Message-ID: <48294853.90201@it.uc3m.es>
Date: Tue, 13 May 2008 09:50:43 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com> 
	<081d01c8b2db$54fa9770$c3f0200a@cisco.com> <4826F926.80404@it.uc3m.es> 
	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com><4827FA33.8020201@it.uc3m.es>
	<03cb01c8b451$b32583b0$c3f0200a@cisco.com>
	<4829474D.7060106@it.uc3m.es>
In-Reply-To: <4829474D.7060106@it.uc3m.es>
X-imss-version: 2.050
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-28.4548 TC:1F TRN:66 TV:5.5.1026(15906.005)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

please disregard this message, i finally understood what Dan's point was.

sorry for the noise

Regards, marcelo


marcelo bagnulo braun escribi=F3:
> Dan Wing escribi=F3:
>   =

>>  =

>>
>>   =

>>     =

>>> -----Original Message-----
>>> From: marcelo bagnulo braun [mailto:marcelo@it.uc3m.es] =

>>> Sent: Monday, May 12, 2008 1:05 AM
>>> To: Dan Wing
>>> Cc: 'Iljitsch van Beijnum'; behave@ietf.org
>>> Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
>>>
>>> but this breaks
>>>
>>>    REQ-1:  A NAT MUST have an "Endpoint Independent Mapping" behavior
>>>       for TCP.
>>>
>>>  =

>>> described in draft-ietf-behave-tcp-07.txt
>>>
>>> doesn't it?
>>>     =

>>>       =

>> Yes.
>>
>> But does re-using the same public TCP port, after the 3-way handshake
>> completes, cause something to break?  It feels pretty safe to me.
>>   =

>>     =

> the connection will not break, agree
> The problem i guess is that you will need to always use TURN relay to =

> receive incoming TCP connections and that seems to be not the best option.
>
> Having endpoint independent mappings for TCP would allow internal hosts =

> to receive incoming communications without turn relay.
>
>
> Regards, marcelo
>
>
>   =

>> -d
>>
>>
>>   =

>>     =

>>> Dan Wing escribi=F3:
>>>     =

>>>       =

>>>> Thanks for explaining.
>>>>
>>>> A reasonable approach is for a NAT to wait until a TCP =

>>>> connection has been
>>>> established (3-way handshake completed), and then allow =

>>>> re-using that same
>>>> public TCP port for a new connection to another remote host.
>>>>
>>>> -d
>>>>
>>>>
>>>>   =

>>>>       =

>>>>         =

>>>>> -----Original Message-----
>>>>> From: marcelo bagnulo braun [mailto:marcelo@it.uc3m.es] =

>>>>> Sent: Sunday, May 11, 2008 6:48 AM
>>>>> To: Dan Wing
>>>>> Cc: 'Iljitsch van Beijnum'; behave@ietf.org
>>>>> Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
>>>>>
>>>>> Hi Dan,
>>>>>
>>>>> I think Iljitsch is talking about the same scenario
>>>>>
>>>>> Consider a host H1 behind a nat which has a single public =

>>>>>         =

>>>>>           =

>>> address T.
>>>     =

>>>       =

>>>>> Suppose H1 initiates a communications towards an external =

>>>>> host H2 at port w.
>>>>>
>>>>> So, packet from H1 to the NAT has, source (H1,v) and =

>>>>> destination (H2,w)
>>>>>
>>>>> Now, when the packet is received at the NAT is creates a mapping
>>>>> (H1,v) <->(T,u) and the nat sends the packet with source (T,u) and =

>>>>> destination (H2,w)
>>>>>
>>>>> Now, suppose another host H3 initiates a communication toward =

>>>>> a node H4 =

>>>>> at port j.
>>>>> The packet from H3 towards the nat has source (H3,i) and =

>>>>> estiantion (H4,j)
>>>>>
>>>>> when the packet from He reaches the NAT, does the NAT can crate a =

>>>>> mapping (H3,i)<->(T,u)
>>>>>
>>>>> As i understand it, if we want to have endpoint =

>>>>>         =

>>>>>           =

>>> independent mapping, =

>>>     =

>>>       =

>>>>> this is not possible (this is so, because if later on H1 =

>>>>> sends a packet =

>>>>> towards H4 at port j, and we want to use the same mapping H1 =

>>>>> is already =

>>>>> using, we would end up in a conflict)
>>>>>
>>>>> So, this basically means, that when the mapping for H1 (H1,v) =

>>>>> <->(T,u) =

>>>>> is created in the NAT, the transport address (T,u) cannot =

>>>>>         =

>>>>>           =

>>> be used for =

>>>     =

>>>       =

>>>>> ANY other rmapping (cause needs to be reserved for future =

>>>>>         =

>>>>>           =

>>> potential =

>>>     =

>>>       =

>>>>> communications of H1 with other destiantions.
>>>>>
>>>>> So basically with endpoint independent mappings, each internally =

>>>>> initiated communication eats up one port of the nat, reducing =

>>>>> the number =

>>>>> of simultaneous communications the NAT can handle. If we =

>>>>>         =

>>>>>           =

>>> had address =

>>>     =

>>>       =

>>>>> dependent mapping, the mapping takes into account the destination =

>>>>> address also, so even if you may need more than one =

>>>>>         =

>>>>>           =

>>> mapping when the =

>>>     =

>>>       =

>>>>> same source transport address is used for two different external =

>>>>> destinations, the NAT does not needs to reserve the port =

>>>>> exclusively for =

>>>>> the internal source address, so it is likely that a better =

>>>>> usage of port =

>>>>> range of the nat is achieved.
>>>>>
>>>>>
>>>>> I mean, this is the price we need to pay for endpoint independence
>>>>>
>>>>> Am i missing something?
>>>>>
>>>>> Regards, marcelo
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Dan Wing escribi=F3:
>>>>>     =

>>>>>         =

>>>>>           =

>>>>>>  =

>>>>>>   =

>>>>>>       =

>>>>>>           =

>>>>>>             =

>>>>>>> What I'm hoping for is that it would be possible to tighten the  =

>>>>>>> requirements such that we get closer to reserving ports for  =

>>>>>>> applications that really need reserved ports and get to =

>>>>>>>         =

>>>>>>>             =

>>>>>>>               =

>>>>> reuse ports  =

>>>>>     =

>>>>>         =

>>>>>           =

>>>>>>> for client-server applications so that a =

>>>>>>>             =

>>>>>>>               =

>>> BEHAVE-compliant NAT can  =

>>>     =

>>>       =

>>>>>>> support a much larger user base with the same number of =

>>>>>>>         =

>>>>>>>             =

>>>>>>>               =

>>>>> public IPv4  =

>>>>>     =

>>>>>         =

>>>>>           =

>>>>>>> addresses as these addresses start to run out.
>>>>>>>     =

>>>>>>>         =

>>>>>>>             =

>>>>>>>               =

>>>>>> I don't understand the relationship between endpoint =

>>>>>>       =

>>>>>>           =

>>>>>>             =

>>>>> independent mapping
>>>>>     =

>>>>>         =

>>>>>           =

>>>>>> and the desire to free up the ports earlier.   I think =

>>>>>>           =

>>>>>>             =

>>> you are only =

>>>     =

>>>       =

>>>>>> really asking for the NAT's TCP TIME_WAIT to be short.
>>>>>>
>>>>>> -d
>>>>>>
>>>>>> _______________________________________________
>>>>>> Behave mailing list
>>>>>> Behave@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/behave
>>>>>>
>>>>>>   =

>>>>>>       =

>>>>>>           =

>>>>>>             =

>>>>   =

>>>>       =

>>>>         =

>>   =

>>     =

>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
>   =


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May 13 06:40:33 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E0C383A68B6;
	Tue, 13 May 2008 06:40:33 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 047C13A68B6
	for <behave@core3.amsl.com>; Tue, 13 May 2008 06:40:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.494
X-Spam-Level: 
X-Spam-Status: No, score=-3.494 tagged_above=-999 required=5
	tests=[AWL=-0.332, BAYES_00=-2.599, J_CHICKENPOX_17=0.6,
	RCVD_BAD_ID=2.837, RCVD_IN_DNSWL_MED=-4]
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 posIWEms34iE for <behave@core3.amsl.com>;
	Tue, 13 May 2008 06:40:27 -0700 (PDT)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131])
	by core3.amsl.com (Postfix) with ESMTP id 10D1E3A6C11
	for <behave@ietf.org>; Tue, 13 May 2008 06:40:26 -0700 (PDT)
Received: from dummyhost0.it.uc3m.es (dummyhost1.it.uc3m.es 
	[163.117.139.42])by smtp01.uc3m.es (Postfix) with ESMTP id 055835F5F8C;
	Tue, 13 May 2008 15:22:38 +0200 (CEST)
Message-ID: <4829961D.6030105@it.uc3m.es>
Date: Tue, 13 May 2008 15:22:37 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com><200805120947.44
	545.remi.denis-courmont@nokia.com><48286442.8090503@sipeerior.com> 
	<03f501c8b455$e65e2ad0$c3f0200a@cisco.com>
In-Reply-To: <03f501c8b455$e65e2ad0$c3f0200a@cisco.com>
X-imss-version: 2.050
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-21.3092 TC:1F TRN:78 TV:5.5.1026(15906.007)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Dan Wing escribi=F3:
>  =

>
>   =

>> -----Original Message-----
>> From: behave-bounces@ietf.org =

>> [mailto:behave-bounces@ietf.org] On Behalf Of Bruce Lowekamp
>> Sent: Monday, May 12, 2008 8:38 AM
>> To: R=E9mi Denis-Courmont
>> Cc: behave@ietf.org
>> Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
>>
>> I agree.  And even if the hypothetical savings in the number of IPv4 =

>> addresses needed for NATs is realized, going to endpoint-dependent =

>> mapping would require every major ISP that deploys one of =

>> these things =

>> to deploy a number of TURN relays since their customers won't =

>> be able to =

>> connect directly with those behind similar NATs.  So you're trading a =

>> lot of bandwidth and machines deployed as relays for a savings of IP =

>> addresses.   If you were doing a full voip (or gaming or whatever) =

>> deployment, it isn't actually clear to me that you won't need =

>> to deploy =

>> as many relays  (with public IP addresses) as you =

>> theoretically saved by using a symmetric NAT.
>>     =

>
> All of Iljitsch's examples were for TCP applications.  Thus, I assume
> the primary concern is TCP port consumption (rather than UDP port
> consumption).  TCP may well be easier to fix, anyway, as it has a 3-way
> handshake after which no other host can send data into the TCP flow
> anyway.
>   =


but a different host could use the same destination and port address to =

establish a new TCP connection towards the internal host, if endpoint =

independent mapping is used, right?

I mean, consider the following scenario:
                                                   (163.1.1.1, 2000)+--+
                                                 +------------------|H2|
                         +-----+(16.1.1.1,5000)  |                  +--+
 +---+(10.1.1.1, 30000)  | NAT |-----------------+                 =

 | H1|-------------------|     |-----------------+
 +---+                   +-----+                 |                  +--+
                                                 +------------------|H3|
                                                     (23.1.1.1,8000)+--+
Now suppose H1 starts a communication with H2 and the NAT assigns =

(16.1.1.1,5000) to H1
the TCP connection is identified by [(16.1.1.1,5000),(163.1.1.1,2000)]
So, as you say, no other host can send packets toward that connection

However, if the NAT is doing e3ndpoint independent mapping, then H3 can =

actually initiate a new TCP connection towards 16.1.1.1,5000, using its =

own transport address (the new connection woudl be identified by =

[(23.1.1.1,8000),(16.1.1.1,5000)]

If we do not require endpoint independent mapping, then the only =

alternative would be to use a stun server to allow incoming =

communications towards H1

So, while i agree that nothing breaks, not requiring endpoint indepednet =

mapping requires, as people have been saying, the usage of a stun server =

for incoming communications.

Regards, marcelo


>  =

> -d
>
>
>   =

>> Bruce
>>
>>
>> R=E9mi Denis-Courmont wrote:
>>     =

>>> Le Friday 09 May 2008 20:01:10 ext Iljitsch van Beijnum, =

>>>       =

>> vous avez =E9crit :
>>     =

>>>> Now obviously it makes sense for a NAT-PT (let me call it NAT64 =3D a
>>>> NAT that sits between IPv6 clients and IPv4 servers) to =

>>>>         =

>> conform to the
>>     =

>>>> BEHAVE requirements. However... One of these requirements is that
>>>> mappings are endpoint independent. So if I talk to =

>>>>         =

>> www.google.com with
>>     =

>>>> source port 49152, I don't get to also talk to www.yahoo.com using
>>>> source port 49152.
>>>>
>>>> Unless I'm mistaken, this basically allows the setup of an outgoing
>>>> session to be an implicit reservation of the source port for
>>>> subsequent incoming sessions, so peer-to-peer applications can work
>>>> through the NAT without the need for an explicit hole punching
>>>> mechanism.
>>>>         =

>>> No.
>>>
>>> Whether hole punching is needed depends on the *filtering* =

>>>       =

>> behavior. Only if =

>>     =

>>> the filtering is endpoint independent, then hole punching =

>>>       =

>> is not needed (but =

>>     =

>>> still a good idea if only for diagnostics). If filtering is =

>>>       =

>> endpoint =

>>     =

>>> dependent, hole punching is required. BEHAVE does not =

>>>       =

>> preclude either type of =

>>     =

>>> *filtering*.
>>>
>>> BEHAVE requires endpoint independent *mapping* so that =

>>>       =

>> communication is =

>>     =

>>> possible between two peers when both are NAT'd. With =

>>>       =

>> endpoint dependent =

>>     =

>>> mapping (a.k.a. symmetric NATs), a peer needs to =

>>>       =

>> communicate to the other =

>>     =

>>> endpoint to determine its own mapping. In other words, both =

>>>       =

>> peers need to =

>>     =

>>> know the other one's mapping to learn their own - an =

>>>       =

>> obvious chicken-and-egg =

>>     =

>>> deadlock.
>>>
>>>       =

>>>> The trouble with this is that it limits the number of =

>>>>         =

>> active mappings
>>     =

>>>> per public IPv4 in a NAT to ~64k per transport protocol.
>>>>         =

>>> I am well aware of that, but endpoint dependent mappings =

>>>       =

>> are such a hassle, =

>>     =

>>> that I think it would be a terrible idea to allow it. It =

>>>       =

>> would also break =

>>     =

>>> (old-style) STUN, Teredo and ICE/STUNbis.
>>>
>>>       =

>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>>     =

>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
>   =


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May 13 07:29:48 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C26743A6C17;
	Tue, 13 May 2008 07:29:48 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1A0543A6C17
	for <behave@core3.amsl.com>; Tue, 13 May 2008 07:29:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
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 Wwu7rfxymLE3 for <behave@core3.amsl.com>;
	Tue, 13 May 2008 07:29:46 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157])
	by core3.amsl.com (Postfix) with ESMTP id 2FA9A3A6C13
	for <behave@ietf.org>; Tue, 13 May 2008 07:29:44 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id d23so2352618fga.41
	for <behave@ietf.org>; Tue, 13 May 2008 07:26:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer;
	bh=DM0vhOR1jDsQlS0cgjHUMpJDssj7zf5aX5xU3xVoAdQ=;
	b=R442MImfq7c7yFaNppueH4KZ5Zh0mq+ZCz9Z5vGeo25wKUfaeVbOoX67mLGnUmolOLndIbqlARWJmXlR02VVPqjFmZpr80n1wi2FZY0Qy7IVUwhdXXM5LdRqd56d+efa5Addapag7QLDlLeSqL4E3GE/cZOrDztGTV35LCjtYW4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer;
	b=ONqA/94jtzAF123pNERHyhFefZ8su8myf55a6CLK3eHc2VgmwyYOn8hwIUozNvJqHBOdPG8Mo6pzUM8t6T4KXRheL5+WLVbghoLD2dVBla6j15eqm3A1LgVnMmefRUtQ9zztLFYHsVxP5+TUxrdzyD3KhC8e2EV9bw1O6y94EPE=
Received: by 10.86.98.10 with SMTP id v10mr10996202fgb.39.1210685248228;
	Tue, 13 May 2008 06:27:28 -0700 (PDT)
Received: from ?163.117.140.211? ( [163.117.140.211])
	by mx.google.com with ESMTPS id 12sm7771877fgg.0.2008.05.13.06.27.27
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Tue, 13 May 2008 06:27:27 -0700 (PDT)
Message-Id: <03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>
From: Iljitsch van Beijnum <iljitsch@gmail.com>
To: Bruce Lowekamp <lowekamp@sipeerior.com>
In-Reply-To: <4828AE1B.9040901@sipeerior.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 13 May 2008 15:27:26 +0200
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es>
	<48286CFD.1080204@free.fr> <48287AE5.5010005@sipeerior.com>
	<482882B7.2030806@free.fr>
	<145B7DFA-E397-4184-8FA6-3C255078509F@muada.com>
	<48289C15.3000102@free.fr> <4828A33E.1080700@sipeerior.com>
	<4828ABBE.9010201@free.fr> <4828AE1B.9040901@sipeerior.com>
X-Mailer: Apple Mail (2.919.2)
Cc: behave@ietf.org, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 12 mei 2008, at 22:52, Bruce Lowekamp wrote:

>> It seems to me that dependent mapping for bit torrent, if reasonably
>> simple to ensure, must remain a goal.
>> If a host behind a shared NAT establishes many connections (with non
>> natted peers since this is the case), it is very useful to avoid that
>> each connection consumes a full address-port pair.

> Your proposed solution prevents anyone behind a nat from serving  
> pieces
> of the file.  You then suggest that all of these connections are going
> to be with non-NATted peers, but your entire scenario is based on the
> idea that it's going to be needed in a time when IPv4 address space is
> completely exhausted and being reclaimed as ASes are converting to  
> IPv6.
>   Which means that these non-NATed peers are going to be much scarcer
> than they are now.   Which means that you need to have peers behind  
> NATs
> serving pieces.  Which means they need to have independent mapping.

Note that both ends can both serve and receive, regardless of which  
end set up the session.

> So, no, bittorrent is exactly the application you DON'T want to have
> dependent mapping for.

The thing is, that all the BitTorrent clients that I'm aware of,  
exclusively rely on manual mappings, UPnP or NAT-PMP. They don't use  
any of the BEHAVE mechanisms.

Now with an ISP-operated NAT, UPnP and NAT-PMP aren't going to work  
because they need the NAT to be on the local subnet, AFAIK. Manual  
mappings isn't entirely impossible but I don't see this working too  
well in practice.

Now there are two possible ways forward: the BitTorrent clients start  
making use of endpoint independent mapping and stop using up large  
numbers of port numbers, OR they keep their current behavior but the  
NATs figure out a way to make sure that BitTorrent doesn't use  
endpoint independent mapping because this uses up too much port numbers.

A logical way forward would be for NATs to limit the number of ports  
that a single host can use up, and create a way to differentiate  
between applications that need endpoint independence and ones that  
don't. I think defining a small set of destination port number ranges  
for this would be the easiest solution.

>> An improved combination could be:
>> - If the packet that initiates the mapping has a well known  
>> destination
>> port (< 1024), then dependent mapping is restricted to a short list
>> (HTTP plus a few others).
>> - If the destination port is beyond 1023, then dependent mapping is
>> freely practiced.

> no.  you can't make dependent mapping the default.

Indeed. Make < 1024 endpoint dependent, this is is where the main  
offenders and most client-server apps reside. Then make everything  
else endpoint independent except maybe a small range somewhere for  
apps that don't need/want this but can't easily run on < 1024 ports.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May 13 07:57:43 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8005C3A6C2D;
	Tue, 13 May 2008 07:57:43 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1305C3A6C2B
	for <behave@core3.amsl.com>; Tue, 13 May 2008 07:57:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 qSRvOj7+++4b for <behave@core3.amsl.com>;
	Tue, 13 May 2008 07:57:39 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by core3.amsl.com (Postfix) with ESMTP id 5A2983A6C22
	for <behave@ietf.org>; Tue, 13 May 2008 07:57:39 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,480,1204531200"; d="scan'208";a="26692610"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-5.cisco.com with ESMTP; 13 May 2008 07:56:35 -0700
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m4DEuVB1029021; 
	Tue, 13 May 2008 07:56:31 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id m4DEuVIm016947;
	Tue, 13 May 2008 14:56:31 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'marcelo bagnulo braun'" <marcelo@it.uc3m.es>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
	<081d01c8b2db$54fa9770$c3f0200a@cisco.com>
	<4826F926.80404@it.uc3m.es>
	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>
	<4827FA33.8020201@it.uc3m.es>
	<03cb01c8b451$b32583b0$c3f0200a@cisco.com>
	<4829474D.7060106@it.uc3m.es>
Date: Tue, 13 May 2008 07:56:31 -0700
Message-ID: <014c01c8b509$87b4df10$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <4829474D.7060106@it.uc3m.es>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
thread-index: Aci0zYtkdAnCpDbzSIuV2ayJTLuBtwAO+ayQ
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=6563; t=1210690591;
	x=1211554591; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Scalability=20of=20endpoint=
	20independent=20mapping |Sender:=20;
	bh=8BjbOc73iSLAVEzacIyXoLhpKLPxPyBbkRwIQq3qWKw=;
	b=TuT2IfOpuJ+Bp4AXCMkR6tiiLCLRDaTCb7utrhr/OKsG6b57ET4xO6mv70
	Mr0/bvJzZ5jE62wN6M0yEGClGNykoq6OhRvJti0D553lj36OTDF+Ors+Knel
	3W+Zjr8xxW;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

 =


> -----Original Message-----
> From: marcelo bagnulo braun [mailto:marcelo@it.uc3m.es] =

> Sent: Tuesday, May 13, 2008 12:46 AM
> To: Dan Wing
> Cc: 'Iljitsch van Beijnum'; behave@ietf.org
> Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
> =

> Dan Wing escribi=F3:
> >  =

> >
> >   =

> >> -----Original Message-----
> >> From: marcelo bagnulo braun [mailto:marcelo@it.uc3m.es] =

> >> Sent: Monday, May 12, 2008 1:05 AM
> >> To: Dan Wing
> >> Cc: 'Iljitsch van Beijnum'; behave@ietf.org
> >> Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
> >>
> >> but this breaks
> >>
> >>    REQ-1:  A NAT MUST have an "Endpoint Independent =

> Mapping" behavior
> >>       for TCP.
> >>
> >>  =

> >> described in draft-ietf-behave-tcp-07.txt
> >>
> >> doesn't it?
> >>     =

> >
> > Yes.
> >
> > But does re-using the same public TCP port, after the 3-way =

> handshake
> > completes, cause something to break?  It feels pretty safe to me.
> >   =

> the connection will not break, agree
> The problem i guess is that you will need to always use TURN relay to =

> receive incoming TCP connections and that seems to be not the =

> best option.

I don't see TURN being needed with my idea.  I will write it up
in more detail and (as is often the case when I write things down
in detail) may find my idea is flawed.

-d


> Having endpoint independent mappings for TCP would allow =

> internal hosts =

> to receive incoming communications without turn relay.
> =

> =

> Regards, marcelo
> =

> =

> > -d
> >
> >
> >   =

> >> Dan Wing escribi=F3:
> >>     =

> >>> Thanks for explaining.
> >>>
> >>> A reasonable approach is for a NAT to wait until a TCP =

> >>> connection has been
> >>> established (3-way handshake completed), and then allow =

> >>> re-using that same
> >>> public TCP port for a new connection to another remote host.
> >>>
> >>> -d
> >>>
> >>>
> >>>   =

> >>>       =

> >>>> -----Original Message-----
> >>>> From: marcelo bagnulo braun [mailto:marcelo@it.uc3m.es] =

> >>>> Sent: Sunday, May 11, 2008 6:48 AM
> >>>> To: Dan Wing
> >>>> Cc: 'Iljitsch van Beijnum'; behave@ietf.org
> >>>> Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
> >>>>
> >>>> Hi Dan,
> >>>>
> >>>> I think Iljitsch is talking about the same scenario
> >>>>
> >>>> Consider a host H1 behind a nat which has a single public =

> >>>>         =

> >> address T.
> >>     =

> >>>> Suppose H1 initiates a communications towards an external =

> >>>> host H2 at port w.
> >>>>
> >>>> So, packet from H1 to the NAT has, source (H1,v) and =

> >>>> destination (H2,w)
> >>>>
> >>>> Now, when the packet is received at the NAT is creates a mapping
> >>>> (H1,v) <->(T,u) and the nat sends the packet with source =

> (T,u) and =

> >>>> destination (H2,w)
> >>>>
> >>>> Now, suppose another host H3 initiates a communication toward =

> >>>> a node H4 =

> >>>> at port j.
> >>>> The packet from H3 towards the nat has source (H3,i) and =

> >>>> estiantion (H4,j)
> >>>>
> >>>> when the packet from He reaches the NAT, does the NAT =

> can crate a =

> >>>> mapping (H3,i)<->(T,u)
> >>>>
> >>>> As i understand it, if we want to have endpoint =

> >>>>         =

> >> independent mapping, =

> >>     =

> >>>> this is not possible (this is so, because if later on H1 =

> >>>> sends a packet =

> >>>> towards H4 at port j, and we want to use the same mapping H1 =

> >>>> is already =

> >>>> using, we would end up in a conflict)
> >>>>
> >>>> So, this basically means, that when the mapping for H1 (H1,v) =

> >>>> <->(T,u) =

> >>>> is created in the NAT, the transport address (T,u) cannot =

> >>>>         =

> >> be used for =

> >>     =

> >>>> ANY other rmapping (cause needs to be reserved for future =

> >>>>         =

> >> potential =

> >>     =

> >>>> communications of H1 with other destiantions.
> >>>>
> >>>> So basically with endpoint independent mappings, each internally =

> >>>> initiated communication eats up one port of the nat, reducing =

> >>>> the number =

> >>>> of simultaneous communications the NAT can handle. If we =

> >>>>         =

> >> had address =

> >>     =

> >>>> dependent mapping, the mapping takes into account the =

> destination =

> >>>> address also, so even if you may need more than one =

> >>>>         =

> >> mapping when the =

> >>     =

> >>>> same source transport address is used for two different external =

> >>>> destinations, the NAT does not needs to reserve the port =

> >>>> exclusively for =

> >>>> the internal source address, so it is likely that a better =

> >>>> usage of port =

> >>>> range of the nat is achieved.
> >>>>
> >>>>
> >>>> I mean, this is the price we need to pay for endpoint =

> independence
> >>>>
> >>>> Am i missing something?
> >>>>
> >>>> Regards, marcelo
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> Dan Wing escribi=F3:
> >>>>     =

> >>>>         =

> >>>>>  =

> >>>>>   =

> >>>>>       =

> >>>>>           =

> >>>>>> What I'm hoping for is that it would be possible to =

> tighten the  =

> >>>>>> requirements such that we get closer to reserving ports for  =

> >>>>>> applications that really need reserved ports and get to =

> >>>>>>         =

> >>>>>>             =

> >>>> reuse ports  =

> >>>>     =

> >>>>         =

> >>>>>> for client-server applications so that a =

> >>>>>>             =

> >> BEHAVE-compliant NAT can  =

> >>     =

> >>>>>> support a much larger user base with the same number of =

> >>>>>>         =

> >>>>>>             =

> >>>> public IPv4  =

> >>>>     =

> >>>>         =

> >>>>>> addresses as these addresses start to run out.
> >>>>>>     =

> >>>>>>         =

> >>>>>>             =

> >>>>> I don't understand the relationship between endpoint =

> >>>>>       =

> >>>>>           =

> >>>> independent mapping
> >>>>     =

> >>>>         =

> >>>>> and the desire to free up the ports earlier.   I think =

> >>>>>           =

> >> you are only =

> >>     =

> >>>>> really asking for the NAT's TCP TIME_WAIT to be short.
> >>>>>
> >>>>> -d
> >>>>>
> >>>>> _______________________________________________
> >>>>> Behave mailing list
> >>>>> Behave@ietf.org
> >>>>> https://www.ietf.org/mailman/listinfo/behave
> >>>>>
> >>>>>   =

> >>>>>       =

> >>>>>           =

> >>>   =

> >>>       =

> >
> >
> >   =

> =


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May 13 08:26:12 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1C7933A67B7;
	Tue, 13 May 2008 08:26:12 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 348ED3A67AE
	for <behave@core3.amsl.com>; Tue, 13 May 2008 08:26:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 viamnM2+1st8 for <behave@core3.amsl.com>;
	Tue, 13 May 2008 08:26:09 -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 5A0423A67B7
	for <behave@ietf.org>; Tue, 13 May 2008 08:26:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,480,1204531200"; d="scan'208";a="46368476"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-2.cisco.com with ESMTP; 13 May 2008 08:25:38 -0700
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m4DFPbFY001591; 
	Tue, 13 May 2008 08:25:37 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id m4DFPaY5005941;
	Tue, 13 May 2008 15:25:37 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Iljitsch van Beijnum'" <iljitsch@gmail.com>,
	"'Bruce Lowekamp'" <lowekamp@sipeerior.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es><48286CFD.1080204@free.fr>
	<48287AE5.5010005@sipeerior.com><482882B7.2030806@free.fr><145B7DFA-E397-4184-8FA6-3C255078509F@muada.com><48289C15.3000102@free.fr>
	<4828A33E.1080700@sipeerior.com><4828ABBE.9010201@free.fr>
	<4828AE1B.9040901@sipeerior.com>
	<03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>
Date: Tue, 13 May 2008 08:25:36 -0700
Message-ID: <015801c8b50d$984b8eb0$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
thread-index: Aci1BdAMb1fKMuMtQs2Z5kmFRKMv/gABvmng
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2323; t=1210692337;
	x=1211556337; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Scalability=20of=20endpoint=
	20independent=20mapping |Sender:=20;
	bh=9ExodxHYuegkET3usqGZoJpMto8d9qt/rrOxza6h5A8=;
	b=LvHtoY89W4AYPgJnYL6PVMU4x369fQZF42kjAJ1nXnErtj0JjPNOCyYr0J
	51JgEdbJiEwMjdtiqCQjVaJumE0MdcPc9G/18PY6pz/04PZLlXxNtY0SWiAY
	wKRe4w3u9W;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


> The thing is, that all the BitTorrent clients that I'm aware of,  
> exclusively rely on manual mappings, UPnP or NAT-PMP. They don't use  
> any of the BEHAVE mechanisms. 
>
> Now with an ISP-operated NAT, UPnP and NAT-PMP aren't going to work  
> because they need the NAT to be on the local subnet, AFAIK.

Right.

It may be worth considering proxying UPnP or NAT-PMP into a 
address-port-borrowing-protocol -- so that the host still runs
UPnP/NAT-PMP and talks to its local router which (unbeknownst to
the host) operates an address-port-borrowing-protocol to the
ISP's big v4/v6 NAT-in-the-sky and returns a public v4 address 
to the host.

-d

> Manual  
> mappings isn't entirely impossible but I don't see this working too  
> well in practice.
> 
> Now there are two possible ways forward: the BitTorrent 
> clients start  
> making use of endpoint independent mapping and stop using up large  
> numbers of port numbers, OR they keep their current behavior but the  
> NATs figure out a way to make sure that BitTorrent doesn't use  
> endpoint independent mapping because this uses up too much 
> port numbers.
> 
> A logical way forward would be for NATs to limit the number of ports  
> that a single host can use up, and create a way to differentiate  
> between applications that need endpoint independence and ones that  
> don't. I think defining a small set of destination port 
> number ranges  
> for this would be the easiest solution.
> 
> >> An improved combination could be:
> >> - If the packet that initiates the mapping has a well known  
> >> destination
> >> port (< 1024), then dependent mapping is restricted to a short list
> >> (HTTP plus a few others).
> >> - If the destination port is beyond 1023, then dependent mapping is
> >> freely practiced.
> 
> > no.  you can't make dependent mapping the default.
> 
> Indeed. Make < 1024 endpoint dependent, this is is where the main  
> offenders and most client-server apps reside. Then make everything  
> else endpoint independent except maybe a small range somewhere for  
> apps that don't need/want this but can't easily run on < 1024 ports.
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May 13 08:43:03 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7F6FE3A6BEE;
	Tue, 13 May 2008 08:43:03 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 607E43A688D
	for <behave@core3.amsl.com>; Tue, 13 May 2008 08:43:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
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 w2iCcmHC4bBy for <behave@core3.amsl.com>;
	Tue, 13 May 2008 08:43:01 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156])
	by core3.amsl.com (Postfix) with ESMTP id 02B723A67AE
	for <behave@ietf.org>; Tue, 13 May 2008 08:43:00 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id d23so2380425fga.41
	for <behave@ietf.org>; Tue, 13 May 2008 08:40:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer;
	bh=nfep3RJtApQZi9mgkaVlHaTna349UAcK/nahuUfe3bE=;
	b=J3KASdPO2wFogWJ2SquSz8KVjUbc3IUhkoJ9gjQfYWTewQNDdwMOSqu0Qk18RoxLNOyYF+nVGchnbUym10lYFGstLbsS93uIPITWnjQ1elF3Bp/QVFEsTP1pUdj1CW8/B+En1OZVuM/Y4uKhPT4myKyvx0RbdgG95qq/MzG1FJ4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer;
	b=b9RY3FljtG+U04xQcI5XCY+VlbScRVyLVpz0BppOjxjQitsbijI/kYQQfz6n3ZtKzKLTbt14khWYpfT0HrCmAmJu3dSptnQCrVfkitH6vJt0J96zGMory5RcpNerwyrkNJmZEXmYuhxY0NU0JlMuNR/Fblq4wmLpdmOLBvvPsiE=
Received: by 10.86.70.11 with SMTP id s11mr16701406fga.71.1210693226154;
	Tue, 13 May 2008 08:40:26 -0700 (PDT)
Received: from ?163.117.140.211? ( [163.117.140.211])
	by mx.google.com with ESMTPS id e20sm7859054fga.7.2008.05.13.08.40.25
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Tue, 13 May 2008 08:40:25 -0700 (PDT)
Message-Id: <8EFD78D3-46EC-4BA5-9F9A-B6F471B9C01F@gmail.com>
From: Iljitsch van Beijnum <iljitsch@gmail.com>
To: "Dan Wing" <dwing@cisco.com>
In-Reply-To: <015801c8b50d$984b8eb0$c3f0200a@cisco.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 13 May 2008 17:40:24 +0200
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es><48286CFD.1080204@free.fr>
	<48287AE5.5010005@sipeerior.com><482882B7.2030806@free.fr><145B7DFA-E397-4184-8FA6-3C255078509F@muada.com><48289C15.3000102@free.fr>
	<4828A33E.1080700@sipeerior.com><4828ABBE.9010201@free.fr>
	<4828AE1B.9040901@sipeerior.com>
	<03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>
	<015801c8b50d$984b8eb0$c3f0200a@cisco.com>
X-Mailer: Apple Mail (2.919.2)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 13 mei 2008, at 17:25, Dan Wing wrote:

>> The thing is, that all the BitTorrent clients that I'm aware of,
>> exclusively rely on manual mappings, UPnP or NAT-PMP. They don't use
>> any of the BEHAVE mechanisms.

>> Now with an ISP-operated NAT, UPnP and NAT-PMP aren't going to work
>> because they need the NAT to be on the local subnet, AFAIK.

> Right.

> It may be worth considering proxying UPnP or NAT-PMP into a
> address-port-borrowing-protocol -- so that the host still runs
> UPnP/NAT-PMP and talks to its local router which (unbeknownst to
> the host) operates an address-port-borrowing-protocol to the
> ISP's big v4/v6 NAT-in-the-sky and returns a public v4 address
> to the host.

If my understanding of all the protocols in question is correct, it  
would even be possible for a UPnP/NAT-PMP proxy to connect to a STUN  
server and then pass on the port that the STUN server sees on to the  
application. If the NAT is then endpoint independent the application  
will be able to receive incoming sessions through the port/address in  
question.

Getting this to work for TCP is left as an exercise for the reader...
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May 13 08:53:04 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E0C773A67F7;
	Tue, 13 May 2008 08:53:04 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 699FD3A6C51
	for <behave@core3.amsl.com>; Tue, 13 May 2008 08:53:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Zz1L3LuYhtl4 for <behave@core3.amsl.com>;
	Tue, 13 May 2008 08:52:58 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 3E6D13A6C5A
	for <behave@ietf.org>; Tue, 13 May 2008 08:52:42 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,480,1204531200"; d="scan'208";a="33276436"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 13 May 2008 08:50:17 -0700
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4DFoHt1025232; 
	Tue, 13 May 2008 08:50:17 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-4.cisco.com (8.13.8/8.13.8) with ESMTP id m4DFoH0a025762;
	Tue, 13 May 2008 15:50:17 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Iljitsch van Beijnum'" <iljitsch@gmail.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es><48286CFD.1080204@free.fr>
	<48287AE5.5010005@sipeerior.com><482882B7.2030806@free.fr><145B7DFA-E397-4184-8FA6-3C255078509F@muada.com><48289C15.3000102@free.fr>
	<4828A33E.1080700@sipeerior.com><4828ABBE.9010201@free.fr>
	<4828AE1B.9040901@sipeerior.com>
	<03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>
	<015801c8b50d$984b8eb0$c3f0200a@cisco.com>
	<8EFD78D3-46EC-4BA5-9F9A-B6F471B9C01F@gmail.com>
Date: Tue, 13 May 2008 08:50:16 -0700
Message-ID: <018601c8b511$0a83a410$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <8EFD78D3-46EC-4BA5-9F9A-B6F471B9C01F@gmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
thread-index: Aci1D61/6n+Hz4bySnqG/Bt2+Jyz9QAAOfPQ
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2027; t=1210693817;
	x=1211557817; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Scalability=20of=20endpoint=
	20independent=20mapping |Sender:=20;
	bh=4sJ3cXZ0b7iEdCFOZDGctOl2IlwG9KZPujD6vstaoZM=;
	b=iX1NdDDxPE7vxx8lDWQ2hQ8sF5hDbvNaORFoeDIPHOo253QNg5AYD9xN+c
	smO5Ua4WOTxkpqmimJ0dTkoKhoXlCspx2WNvu8a836o08QclBd8fjIbewzIz
	syBqb23NmXCZ0cc41LtPZFBILgZoDfGI5ibIFjIiLm3tkj/Pfre24=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

 

> -----Original Message-----
> From: Iljitsch van Beijnum [mailto:iljitsch@gmail.com] 
> Sent: Tuesday, May 13, 2008 8:40 AM
> To: Dan Wing
> Cc: 'Bruce Lowekamp'; behave@ietf.org
> Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
> 
> On 13 mei 2008, at 17:25, Dan Wing wrote:
> 
> >> The thing is, that all the BitTorrent clients that I'm aware of,
> >> exclusively rely on manual mappings, UPnP or NAT-PMP. They 
> don't use
> >> any of the BEHAVE mechanisms.
> 
> >> Now with an ISP-operated NAT, UPnP and NAT-PMP aren't going to work
> >> because they need the NAT to be on the local subnet, AFAIK.
> 
> > Right.
> 
> > It may be worth considering proxying UPnP or NAT-PMP into a
> > address-port-borrowing-protocol -- so that the host still runs
> > UPnP/NAT-PMP and talks to its local router which (unbeknownst to
> > the host) operates an address-port-borrowing-protocol to the
> > ISP's big v4/v6 NAT-in-the-sky and returns a public v4 address
> > to the host.
> 
> If my understanding of all the protocols in question is correct, it  
> would even be possible for a UPnP/NAT-PMP proxy to connect to a STUN  
> server and then pass on the port that the STUN server sees on to the  
> application.

Mostly, yes.  The difficulty is that both UPnP and NAT-PMP require that
any public mapping be completely non-filtered by the router.  With
STUN, we have no way to know what kind of filtering or mapping behavior
the NAT will use.  Thus, if such a UPnP/NAT-PMP proxy merely used STUN, 
the NAT might not meet UPnP/NAT-PMP's requirements, and the 'legacy'
application would get a public IP address and port that does not work
like when it is behind a "real" UPnP/NAT-PMP-capable router on v4.

> If the NAT is then endpoint independent the application  
> will be able to receive incoming sessions through the 
> port/address in question.
> 
> Getting this to work for TCP is left as an exercise for the reader...

Heh.  A master of understatement.

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May 13 10:11:24 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0917B3A6BDD;
	Tue, 13 May 2008 10:11:23 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8F3E63A68F2
	for <behave@core3.amsl.com>; Tue, 13 May 2008 10:11:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, 
	BAYES_00=-2.599]
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 ZrRUxB72V2bb for <behave@core3.amsl.com>;
	Tue, 13 May 2008 10:11:14 -0700 (PDT)
Received: from mail.sipeerior.com (mail.sipeerior.com [128.239.5.131])
	by core3.amsl.com (Postfix) with ESMTP id B65163A6C4B
	for <behave@ietf.org>; Tue, 13 May 2008 10:11:13 -0700 (PDT)
Received: from vuelta.local (unknown [128.239.5.147])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.sipeerior.com (Postfix) with ESMTP id 89D8F505AA5;
	Tue, 13 May 2008 12:51:49 -0400 (EDT)
Message-ID: <4829C721.5010809@sipeerior.com>
Date: Tue, 13 May 2008 12:51:45 -0400
From: Bruce Lowekamp <lowekamp@sipeerior.com>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@gmail.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es>
	<48286CFD.1080204@free.fr> <48287AE5.5010005@sipeerior.com>
	<482882B7.2030806@free.fr>
	<145B7DFA-E397-4184-8FA6-3C255078509F@muada.com>
	<48289C15.3000102@free.fr> <4828A33E.1080700@sipeerior.com>
	<4828ABBE.9010201@free.fr> <4828AE1B.9040901@sipeerior.com>
	<03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>
In-Reply-To: <03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>
Cc: behave@ietf.org, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Iljitsch van Beijnum wrote:
> On 12 mei 2008, at 22:52, Bruce Lowekamp wrote:
> 
>>> It seems to me that dependent mapping for bit torrent, if reasonably
>>> simple to ensure, must remain a goal.
>>> If a host behind a shared NAT establishes many connections (with non
>>> natted peers since this is the case), it is very useful to avoid that
>>> each connection consumes a full address-port pair.
> 
>> Your proposed solution prevents anyone behind a nat from serving pieces
>> of the file.  You then suggest that all of these connections are going
>> to be with non-NATted peers, but your entire scenario is based on the
>> idea that it's going to be needed in a time when IPv4 address space is
>> completely exhausted and being reclaimed as ASes are converting to IPv6.
>>   Which means that these non-NATed peers are going to be much scarcer
>> than they are now.   Which means that you need to have peers behind NATs
>> serving pieces.  Which means they need to have independent mapping.
> 
> Note that both ends can both serve and receive, regardless of which end 
> set up the session.
> 
>> So, no, bittorrent is exactly the application you DON'T want to have
>> dependent mapping for.
> 
> The thing is, that all the BitTorrent clients that I'm aware of, 
> exclusively rely on manual mappings, UPnP or NAT-PMP. They don't use any 
> of the BEHAVE mechanisms.
> 
> Now with an ISP-operated NAT, UPnP and NAT-PMP aren't going to work 
> because they need the NAT to be on the local subnet, AFAIK. Manual 
> mappings isn't entirely impossible but I don't see this working too well 
> in practice.
> 

This is my concern.  If the scarce address scenario becomes more common, 
it seems like new techniques will be required, and that points toward 
needing the independent mappings.


> Now there are two possible ways forward: the BitTorrent clients start 
> making use of endpoint independent mapping and stop using up large 
> numbers of port numbers, OR they keep their current behavior but the 
> NATs figure out a way to make sure that BitTorrent doesn't use endpoint 
> independent mapping because this uses up too much port numbers.
> 

If NATs support indepdendent mapping and TCP-SO, there won't be a reason 
to allocate hundreds of ports.  If that solution works more reliably 
than others, it would be adopted by new software and also solve the 
scalability problem.


> A logical way forward would be for NATs to limit the number of ports 
> that a single host can use up, and create a way to differentiate between 
> applications that need endpoint independence and ones that don't. I 
> think defining a small set of destination port number ranges for this 
> would be the easiest solution.

I thought many existing NATs would either start sending RSTs or ignore 
new connections.  Don't know how common that behavior is, though.

Bruce



_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May 13 12:44:11 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BBC253A687F;
	Tue, 13 May 2008 12:44:11 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 65A1B3A687F
	for <behave@core3.amsl.com>; Tue, 13 May 2008 12:44:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050, 
	BAYES_00=-2.599]
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 n01mlf5nPcPj for <behave@core3.amsl.com>;
	Tue, 13 May 2008 12:44:08 -0700 (PDT)
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184])
	by core3.amsl.com (Postfix) with ESMTP id 1137B3A67A4
	for <behave@ietf.org>; Tue, 13 May 2008 12:44:07 -0700 (PDT)
Received: by nf-out-0910.google.com with SMTP id f5so1355070nfh.39
	for <behave@ietf.org>; Tue, 13 May 2008 12:41:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer;
	bh=xE3ZwS/hIQ7vTCUMAlrItpj1l+k0iC4qbNz7KnvI+kI=;
	b=dmVM2dFpMjtN8qKvikq0iClBjfav3oO3B6v3o2Eb5uOmOwSRhikp2BUTq9fyxOei+cslMF53UTNBi8CuSbhyGy0VvmjxtQFKhBP3BcvLdk0a2BoXJ5BG9rHMBEEJ2F9OmJAaW4q3w8ZCdjuSpNmFwiI0WZ/dNIZUzcrAdX+WINo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer;
	b=PV+oQR+pqyyggF8Sdd94fpUU6V2TiZsxAaLaSFgI6HVdvXgc7uaibooEn5CICc0Mou7cQ+aoTDRJ2cExMpbLO8EC770sivCQGNAS1E9EteS11YrWKXD2RpbnNc8fBGGVM9QWO3LI6eLqVK3ErDdM3Z9egQ/N18Wv1fY3ouy5t6E=
Received: by 10.210.125.13 with SMTP id x13mr108907ebc.88.1210707096661;
	Tue, 13 May 2008 12:31:36 -0700 (PDT)
Received: from ?192.168.2.13? ( [89.7.138.167])
	by mx.google.com with ESMTPS id b36sm375653ika.5.2008.05.13.12.31.35
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Tue, 13 May 2008 12:31:36 -0700 (PDT)
Message-Id: <2F594053-210D-49D6-A9C7-5245826854A1@gmail.com>
From: Iljitsch van Beijnum <iljitsch@gmail.com>
To: Dan Wing <dwing@cisco.com>,
 Bruce Lowekamp <lowekamp@sipeerior.com>
In-Reply-To: <018601c8b511$0a83a410$c3f0200a@cisco.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 13 May 2008 21:31:34 +0200
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es><48286CFD.1080204@free.fr>
	<48287AE5.5010005@sipeerior.com><482882B7.2030806@free.fr><145B7DFA-E397-4184-8FA6-3C255078509F@muada.com><48289C15.3000102@free.fr>
	<4828A33E.1080700@sipeerior.com><4828ABBE.9010201@free.fr>
	<4828AE1B.9040901@sipeerior.com>
	<03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>
	<015801c8b50d$984b8eb0$c3f0200a@cisco.com>
	<8EFD78D3-46EC-4BA5-9F9A-B6F471B9C01F@gmail.com>
	<018601c8b511$0a83a410$c3f0200a@cisco.com>
X-Mailer: Apple Mail (2.919.2)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 13 mei 2008, at 17:50, Dan Wing wrote:

>> If my understanding of all the protocols in question is correct, it
>> would even be possible for a UPnP/NAT-PMP proxy to connect to a STUN
>> server and then pass on the port that the STUN server sees on to the
>> application.

> Mostly, yes.  The difficulty is that both UPnP and NAT-PMP require  
> that
> any public mapping be completely non-filtered by the router.  With
> STUN, we have no way to know what kind of filtering or mapping  
> behavior
> the NAT will use.  Thus, if such a UPnP/NAT-PMP proxy merely used  
> STUN,
> the NAT might not meet UPnP/NAT-PMP's requirements, and the 'legacy'
> application would get a public IP address and port that does not work
> like when it is behind a "real" UPnP/NAT-PMP-capable router on v4.

Well, but this is a problem that can be fixed without protocol  
changes, so although it would be an issue in practice it's not a big  
deal as far as the IETF is concerned.

>> Getting this to work for TCP is left as an exercise for the reader...

> Heh.  A master of understatement.

Unless I'm missing something this should actually be fairly  
straightforward: just STUN for TCP + endpoint independent mapping.

On 13 mei 2008, at 18:51, Bruce Lowekamp wrote:

>> Now with an ISP-operated NAT, UPnP and NAT-PMP aren't going to work
>> because they need the NAT to be on the local subnet, AFAIK. Manual
>> mappings isn't entirely impossible but I don't see this working too  
>> well
>> in practice.

> This is my concern.  If the scarce address scenario becomes more  
> common,
> it seems like new techniques will be required, and that points toward
> needing the independent mappings.

I have no problem with giving the apps that need it independent  
mappings, we just need to figure out something to avoid applications  
from using up too many port numbers. As I wrote before, we can do this  
if we can recognize the most common client/server apps and give those  
endpoint dependent mappings.

And don't forget that even though IPv4 addresses may become scarce, we  
still have IPv6. Applications like BitTorrent can transition from IPv4  
to IPv6 very gracefully so I'm not worried about those.

>> Now there are two possible ways forward: the BitTorrent clients start
>> making use of endpoint independent mapping and stop using up large
>> numbers of port numbers, OR they keep their current behavior but the
>> NATs figure out a way to make sure that BitTorrent doesn't use  
>> endpoint
>> independent mapping because this uses up too much port numbers.

> If NATs support indepdendent mapping and TCP-SO, there won't be a  
> reason
> to allocate hundreds of ports.  If that solution works more reliably
> than others, it would be adopted by new software and also solve the
> scalability problem.

Right!

Note though that simultaneous open would probably hard to put into  
BitTorrent. Using an initial session as an implicit hole punch with  
endpoint independence would be easier.

Now we just need to fix HTTP/POP/IMAP...
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May 13 13:04:59 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CDCBD3A683B;
	Tue, 13 May 2008 13:04:59 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DCBC23A68DF
	for <behave@core3.amsl.com>; Tue, 13 May 2008 13:04:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 VHt8E3ruP-lt for <behave@core3.amsl.com>;
	Tue, 13 May 2008 13:04:44 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 89A003A6890
	for <behave@ietf.org>; Tue, 13 May 2008 13:04:44 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,480,1204531200"; d="scan'208";a="67514808"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 13 May 2008 12:41:38 -0700
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4DJfcOb024158; 
	Tue, 13 May 2008 12:41:38 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-4.cisco.com (8.13.8/8.13.8) with ESMTP id m4DJfbTe003618;
	Tue, 13 May 2008 19:41:38 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Iljitsch van Beijnum'" <iljitsch@gmail.com>,
	"'Bruce Lowekamp'" <lowekamp@sipeerior.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es><48286CFD.1080204@free.fr>
	<48287AE5.5010005@sipeerior.com><482882B7.2030806@free.fr><145B7DFA-E397-4184-8FA6-3C255078509F@muada.com><48289C15.3000102@free.fr>
	<4828A33E.1080700@sipeerior.com><4828ABBE.9010201@free.fr>
	<4828AE1B.9040901@sipeerior.com>
	<03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>
	<015801c8b50d$984b8eb0$c3f0200a@cisco.com>
	<8EFD78D3-46EC-4BA5-9F9A-B6F471B9C01F@gmail.com>
	<018601c8b511$0a83a410$c3f0200a@cisco.com>
	<2F594053-210D-49D6-A9C7-5245826854A1@gmail.com>
Date: Tue, 13 May 2008 12:41:37 -0700
Message-ID: <04fe01c8b531$5c086c60$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <2F594053-210D-49D6-A9C7-5245826854A1@gmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
thread-index: Aci1L/lBjw9cM3VzRlC8MHgrvUavuwAAO0EQ
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1594; t=1210707698;
	x=1211571698; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Scalability=20of=20endpoint=
	20independent=20mapping |Sender:=20;
	bh=1tTSL8Vt+CF0tHIRnKP2oN+EuUUR8OjZWYwTv0cO2zI=;
	b=ThMMkQXbLOIXKhzgLeVn9rRmS2bmsdrqXwo2sGud4s1M+geHJyt6lVlc3Q
	e7P+PK6JqRxwaHoKxSqdjeucf0EMmw2NKP7KHxpAss2ApNFqwtiCvYUTBlvf
	iYpKN39tD08rFJW8xEeLdDPg/kJQ0MsJZsfLbpGiORVdqll1mSNsA=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

> > Mostly, yes.  The difficulty is that both UPnP and NAT-PMP require  
> > that
> > any public mapping be completely non-filtered by the router.  With
> > STUN, we have no way to know what kind of filtering or mapping  
> > behavior
> > the NAT will use.  Thus, if such a UPnP/NAT-PMP proxy merely used  
> > STUN,
> > the NAT might not meet UPnP/NAT-PMP's requirements, and the 'legacy'
> > application would get a public IP address and port that 
> > does not work
> > like when it is behind a "real" UPnP/NAT-PMP-capable router on v4.
> 
> Well, but this is a problem that can be fixed without protocol  
> changes, so although it would be an issue in practice it's not a big  
> deal as far as the IETF is concerned.

Agreed.

> >> Getting this to work for TCP is left as an exercise for 
> >> the reader...
> 
> > Heh.  A master of understatement.
> 
> Unless I'm missing something this should actually be fairly  
> straightforward: just STUN for TCP + endpoint independent mapping.

STUN for TCP exists (draft-ietf-behave-rfc3489bis now specifies how
STUN-over-TCP works).  The trouble is, many NATs don't do endpoint
independent mapping for TCP.  See Saikat's results at 
http://nutss.gforge.cis.cornell.edu/stunt.php, for example.

Of course with NAT64 we could specify exactly how a NAT64 is supposed
to work and maybe bypass much of the problem that STUNT found with
existing NATs.  The difficulty persists if NAT64 needs to work
with today's off-the-shelf Linksys/Dlink/Belkin/etc. NAPTs that
everyone buys at the local computer store.  

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May 13 19:22:46 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0A12D3A682E;
	Tue, 13 May 2008 19:22:46 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 120A03A67A7
	for <behave@core3.amsl.com>; Tue, 13 May 2008 19:22:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.389
X-Spam-Level: 
X-Spam-Status: No, score=-2.389 tagged_above=-999 required=5 tests=[AWL=0.210, 
	BAYES_00=-2.599]
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 o+c+W+rsngaT for <behave@core3.amsl.com>;
	Tue, 13 May 2008 19:22:42 -0700 (PDT)
Received: from mail-06.primus.ca (mail9.primus.ca [216.254.141.176])
	by core3.amsl.com (Postfix) with ESMTP id 1D32F3A682E
	for <behave@ietf.org>; Tue, 13 May 2008 19:22:41 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-06.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1Jw6dA-0002Is-0l; Tue, 13 May 2008 22:22:13 -0400
Message-Id: <563A472D-30B9-45E9-8E2C-009CF1B4045F@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Behave WG <behave@ietf.org>
In-Reply-To: <04fe01c8b531$5c086c60$c3f0200a@cisco.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 13 May 2008 22:22:09 -0400
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es><48286CFD.1080204@free.fr>
	<48287AE5.5010005@sipeerior.com><482882B7.2030806@free.fr><145B7DFA-E397-4184-8FA6-3C255078509F@muada.com><48289C15.3000102@free.fr>
	<4828A33E.1080700@sipeerior.com><4828ABBE.9010201@free.fr>
	<4828AE1B.9040901@sipeerior.com>
	<03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>
	<015801c8b50d$984b8eb0$c3f0200a@cisco.com>
	<8EFD78D3-46EC-4BA5-9F9A-B6F471B9C01F@gmail.com>
	<018601c8b511$0a83a410$c3f0200a@cisco.com>
	<2F594053-210D-49D6-A9C7-5245826854A1@gmail.com>
	<04fe01c8b531$5c086c60$c3f0200a@cisco.com>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Cc: Iljitsch van Beijnum <iljitsch@gmail.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

If I understand things correctly, what Iljitsch is suggesting is not  
"address-dependent" mapping as I understand it. My understanding of  
"address-dependent" mapping is that a new transport address (on the  
public side of the NAT) is assigned by the NAT to every new  
destination. However, Iljitsch wants instead to re-use the same  
transport address for many different destinations.

Let me give an example.
Let A and B be two nodes on the private side of the NAT.
Let X and Y be two nodes on the public side of the NAT.
Let (T,t) be some transport address assigned to the public side of the  
NAT.

Now consider the following flows:
Private       Public
Node          Node
(A,a) ------> (X,x1)
(A,a) ------> (X,x2)
(A,a) ------> (Y,y1)
(B,b2) -----> (Y,y2)

- Endpoint-independent mapping would assign the same transport address  
to the first three, and a different transport addresses to the last one.
- Address-dependent mapping would assign the same transport address to  
the first two, and different transport addresses to the last two.
- Address-and-port-dependent mapping would assign different transport  
addresses to all of these.
- But what Iljitsch wants to do is to assign the same transport  
address (T,t) for all of these.
 From the NAT perspective, (T,t) can be used for all of these because,  
when the response comes back from the public node, the NAT can  
determine the private node to forward it to by which public node sent  
the packet. For example, it would have a rule that says: if the packet  
is destined for (T,t) and came from (X,x1), then change the  
destination address to (A,a).

I don't yet understand the implications of this, but I thought I  
should point it out.

- Philip

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May 13 23:35:58 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D3BB03A69F1;
	Tue, 13 May 2008 23:35:58 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EED543A697C
	for <behave@core3.amsl.com>; Tue, 13 May 2008 23:35:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.906
X-Spam-Level: 
X-Spam-Status: No, score=-5.906 tagged_above=-999 required=5 tests=[AWL=0.393, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 Ja2TegHcWWCG for <behave@core3.amsl.com>;
	Tue, 13 May 2008 23:35:55 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 2FFF63A6968
	for <behave@ietf.org>; Tue, 13 May 2008 23:35:55 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m4E6YVwu000837; Wed, 14 May 2008 01:34:58 -0500
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 14 May 2008 09:34:57 +0300
Received: from esdhcp04079.research.nokia.com ([172.21.40.79]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 14 May 2008 09:34:56 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: behave@ietf.org
Date: Wed, 14 May 2008 09:36:13 +0300
User-Agent: KMail/1.9.9
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
	<03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>
	<015801c8b50d$984b8eb0$c3f0200a@cisco.com>
In-Reply-To: <015801c8b50d$984b8eb0$c3f0200a@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805140936.14301.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 14 May 2008 06:34:56.0990 (UTC)
	FILETIME=[A052F7E0:01C8B58C]
X-Nokia-AV: Clean
Cc: ext Dan Wing <dwing@cisco.com>, 'Iljitsch van Beijnum' <iljitsch@gmail.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Le Tuesday 13 May 2008 18:25:36 ext Dan Wing, vous avez =E9crit=A0:
> It may be worth considering proxying UPnP or NAT-PMP into a
> address-port-borrowing-protocol -- so that the host still runs
> UPnP/NAT-PMP and talks to its local router which (unbeknownst to
> the host) operates an address-port-borrowing-protocol to the
> ISP's big v4/v6 NAT-in-the-sky and returns a public v4 address
> to the host.

Indeed, this could work for ISP-provisioned CPEs.

In fact, this may be a good thing to have *if* v4-v6-v4 actually happens.

-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May 14 00:11:11 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 693833A685A;
	Wed, 14 May 2008 00:11:11 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2F4C43A685A
	for <behave@core3.amsl.com>; Wed, 14 May 2008 00:11:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.395
X-Spam-Level: 
X-Spam-Status: No, score=-6.395 tagged_above=-999 required=5
	tests=[AWL=-0.096, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
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 5yAEUnxo3GNx for <behave@core3.amsl.com>;
	Wed, 14 May 2008 00:11:09 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 37E833A6830
	for <behave@ietf.org>; Wed, 14 May 2008 00:11:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,484,1204531200"; d="scan'208";a="98443140"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 14 May 2008 00:04:11 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m4E74BED022915; 
	Wed, 14 May 2008 00:04:11 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4E74Aa3026629;
	Wed, 14 May 2008 07:04:10 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "=?iso-8859-1?Q?'R=E9mi_Denis-Courmont'?=" <remi.denis-courmont@nokia.com>,
	<behave@ietf.org>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
	<03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>
	<015801c8b50d$984b8eb0$c3f0200a@cisco.com>
	<200805140936.14301.remi.denis-courmont@nokia.com>
Date: Wed, 14 May 2008 00:04:10 -0700
Message-ID: <00d401c8b590$b62cda50$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <200805140936.14301.remi.denis-courmont@nokia.com>
Thread-Index: Aci1jKWxcRkSePz6RseR+uoGrN+6sAAAw0DQ
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1398; t=1210748651;
	x=1211612651; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Scalability=20of=20endpoint=
	20independent=20mapping |Sender:=20;
	bh=s0Tlh+sLGWrkCeEIq55V9KJYNJi/ZCcN9SdVBPb7rvo=;
	b=GnjbX4quxqzLlYUcdA6iHftV4LEHRwOH/4zpkFHZuoZGTT1jH1qWlWzfYB
	3dq7qQ6RvVPj+AiFJTZMEfY9rcpPE4k681dBLiedzYJgEZtFbZuhfzasdCUK
	UVn5tfLnTn;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: 'Iljitsch van Beijnum' <iljitsch@gmail.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

> Le Tuesday 13 May 2008 18:25:36 ext Dan Wing, vous avez =E9crit=A0:
> > It may be worth considering proxying UPnP or NAT-PMP into a
> > address-port-borrowing-protocol -- so that the host still runs
> > UPnP/NAT-PMP and talks to its local router which (unbeknownst to
> > the host) operates an address-port-borrowing-protocol to the
> > ISP's big v4/v6 NAT-in-the-sky and returns a public v4 address
> > to the host.
> =

> Indeed, this could work for ISP-provisioned CPEs.

Sure, most users won't have a clue and will be happy to
just get a brand new, 189228GHz and 100Gbps wireless box with
blue LEDs from their ISP that "Just Works".

But if we standardize the protocol, this could be a service the =

ISP runs even with non-ISP-provisioned CPE.  It could be as simple =

as your ISP saying: "you can retain v4 access, as you have it =

today, for an additional $NNN/month.  Or you can get v6 access =

for the same price you're getting today; if you need to =

communicate with a v4 host, you can run such-and-such =

address-port-borrowing-protocol with our NAT64 box at <such-
and-such> IP address.  Your authentication credentials for =

accessing the NAT64 box are the same as the username/password
used for our other ISP-provided services (email, USENET, and =

PPPoE)."

> In fact, this may be a good thing to have *if* v4-v6-v4 =

> actually happens.

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May 14 01:51:57 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 62B583A6854;
	Wed, 14 May 2008 01:51:57 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 568DD3A6854
	for <behave@core3.amsl.com>; Wed, 14 May 2008 01:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
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 fbdr8JuxFFgE for <behave@core3.amsl.com>;
	Wed, 14 May 2008 01:51:53 -0700 (PDT)
Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.186])
	by core3.amsl.com (Postfix) with ESMTP id BECD03A6809
	for <behave@ietf.org>; Wed, 14 May 2008 01:51:52 -0700 (PDT)
Received: by fk-out-0910.google.com with SMTP id 18so2629973fkq.5
	for <behave@ietf.org>; Wed, 14 May 2008 01:51:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer;
	bh=m6+NYVMeRrvGTqKhzOPXpGd2laZ+44aMMzeUVTi30pQ=;
	b=RVMa7SPiQZMJjqr8mK6eLbtXtqug/95w69q5Jy/98Txgx/OYdSayz54RZzL878pCBBwaNq1vVfDMX9JRx+xd6953WdU0vd4szKkb5IisFV4MpImfTplOIsgW91V6Ts9PLirOCi6tcf8mS3GlHbJqJtz8oGgHLOU7JSkHlfyFuAU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer;
	b=awQ0a8c2xRbWXzG5qQcMZAr1TfXE1PiuvHmP73Fz0RT4q5/0oBM16Qcvfp/UCL0+uOdFrNOkdmHCh7OqBUE6Z7Pmk2YOVq8wCKznSyVT5+v61va1Jr3NTQL8z+gUi6DsI+1t9tXmZYf5Xe6wW39/3RRebNcGfksomi4EH3JrdMU=
Received: by 10.125.129.19 with SMTP id g19mr117732mkn.111.1210755063846;
	Wed, 14 May 2008 01:51:03 -0700 (PDT)
Received: from nirrti.it.uc3m.es ( [163.117.139.63])
	by mx.google.com with ESMTPS id j10sm1593721mue.6.2008.05.14.01.51.00
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Wed, 14 May 2008 01:51:01 -0700 (PDT)
Message-Id: <ABFE5321-6872-4B67-ADDE-7380F8DE0AD9@gmail.com>
From: Iljitsch van Beijnum <iljitsch@gmail.com>
To: Dan Wing <dwing@cisco.com>,
 Philip Matthews <philip_matthews@magma.ca>
In-Reply-To: <04fe01c8b531$5c086c60$c3f0200a@cisco.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 14 May 2008 10:50:57 +0200
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es><48286CFD.1080204@free.fr>
	<48287AE5.5010005@sipeerior.com><482882B7.2030806@free.fr><145B7DFA-E397-4184-8FA6-3C255078509F@muada.com><48289C15.3000102@free.fr>
	<4828A33E.1080700@sipeerior.com><4828ABBE.9010201@free.fr>
	<4828AE1B.9040901@sipeerior.com>
	<03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>
	<015801c8b50d$984b8eb0$c3f0200a@cisco.com>
	<8EFD78D3-46EC-4BA5-9F9A-B6F471B9C01F@gmail.com>
	<018601c8b511$0a83a410$c3f0200a@cisco.com>
	<2F594053-210D-49D6-A9C7-5245826854A1@gmail.com>
	<04fe01c8b531$5c086c60$c3f0200a@cisco.com>
X-Mailer: Apple Mail (2.919.2)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 13 mei 2008, at 21:41, Dan Wing wrote:

>> Unless I'm missing something this should actually be fairly
>> straightforward: just STUN for TCP + endpoint independent mapping.

> STUN for TCP exists (draft-ietf-behave-rfc3489bis now specifies how
> STUN-over-TCP works).

Excellent.

> Of course with NAT64 we could specify exactly how a NAT64 is supposed
> to work and maybe bypass much of the problem that STUNT found with
> existing NATs.

Right. The good thing here is that we're not constrained by hundreds  
of existing implementations that all behave differently. And existing  
CPEs can't work on the v6 side of a NAT64 universe anyway, so those  
aren't an issue at all.

I was thinking:

If an application wants to make use of endpoint independent mapping  
behavior by the NAT, wouldn't its first packets be towards a STUN(T)  
server? If we can detect this, providing endpoint independent behavior  
where it's needed and using endpoint dependent mappings everywhere  
else is easy.

For TCP, another option would be a TCP option in the SYN from the host  
to the STUNT server, or in the SYN/ACK from the STUNT server back to  
the host, this is probably easier to do than deep packet inspection to  
determine whether a random TCP session is used for STUNT.

On 14 mei 2008, at 4:22, Philip Matthews wrote:

> But what Iljitsch wants to do is to assign the same transport
> address (T,t) for all of these.
> From the NAT perspective, (T,t) can be used for all of these because,
> when the response comes back from the public node, the NAT can
> determine the private node to forward it to by which public node sent
> the packet. For example, it would have a rule that says: if the packet
> is destined for (T,t) and came from (X,x1), then change the
> destination address to (A,a).

I don't think I understand what you're trying to say, but I'm fairly  
sure it's not what I said. I don't think a single behavior applied to  
all sessions will give us both the peer-to-peer usability that we want  
and enough scalability.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May 14 02:11:05 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3AA1F3A683C;
	Wed, 14 May 2008 02:11:05 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 217393A68FA
	for <behave@core3.amsl.com>; Wed, 14 May 2008 02:10:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.307
X-Spam-Level: 
X-Spam-Status: No, score=-2.307 tagged_above=-999 required=5 tests=[AWL=0.292, 
	BAYES_00=-2.599]
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 aLDEbnCVOr6D for <behave@core3.amsl.com>;
	Wed, 14 May 2008 02:09:59 -0700 (PDT)
Received: from mail-06.primus.ca (mail9.primus.ca [216.254.141.176])
	by core3.amsl.com (Postfix) with ESMTP id B0F663A6823
	for <behave@ietf.org>; Wed, 14 May 2008 02:09:56 -0700 (PDT)
Received: from [216.13.42.68] (helo=[10.10.80.124])
	by mail-06.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1JwCyp-0002N6-2M; Wed, 14 May 2008 05:08:59 -0400
Message-Id: <4F985BCC-FEBA-4DFB-9291-C25415E7888E@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Iljitsch van Beijnum <iljitsch@gmail.com>
In-Reply-To: <ABFE5321-6872-4B67-ADDE-7380F8DE0AD9@gmail.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 14 May 2008 05:08:58 -0400
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es><48286CFD.1080204@free.fr>
	<48287AE5.5010005@sipeerior.com><482882B7.2030806@free.fr><145B7DFA-E397-4184-8FA6-3C255078509F@muada.com><48289C15.3000102@free.fr>
	<4828A33E.1080700@sipeerior.com><4828ABBE.9010201@free.fr>
	<4828AE1B.9040901@sipeerior.com>
	<03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>
	<015801c8b50d$984b8eb0$c3f0200a@cisco.com>
	<8EFD78D3-46EC-4BA5-9F9A-B6F471B9C01F@gmail.com>
	<018601c8b511$0a83a410$c3f0200a@cisco.com>
	<2F594053-210D-49D6-A9C7-5245826854A1@gmail.com>
	<04fe01c8b531$5c086c60$c3f0200a@cisco.com>
	<ABFE5321-6872-4B67-ADDE-7380F8DE0AD9@gmail.com>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.10.80.124]) [216.13.42.68]
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Wed, 14-May-08, at 04:50 , Iljitsch van Beijnum wrote:
>
>
> On 14 mei 2008, at 4:22, Philip Matthews wrote:
>
>> But what Iljitsch wants to do is to assign the same transport
>> address (T,t) for all of these.
>> From the NAT perspective, (T,t) can be used for all of these because,
>> when the response comes back from the public node, the NAT can
>> determine the private node to forward it to by which public node sent
>> the packet. For example, it would have a rule that says: if the  
>> packet
>> is destined for (T,t) and came from (X,x1), then change the
>> destination address to (A,a).
>
> I don't think I understand what you're trying to say, but I'm fairly
> sure it's not what I said. I don't think a single behavior applied to
> all sessions will give us both the peer-to-peer usability that we want
> and enough scalability.

Sure.
The proposal to do endpoint-independent mapping for some ports, and  
this new "transport-address-reuse" mapping for other ports seems  
interesting. I was just trying to point out that what you want is not  
address-dependent mapping (at least as I understand it), but some new  
mapping behavior that uses the same transport address for unrelated  
sessions.

- Philip


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May 14 09:41:22 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 046043A696A;
	Wed, 14 May 2008 09:41:22 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D87693A696A
	for <behave@core3.amsl.com>; Wed, 14 May 2008 09:40:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.539
X-Spam-Level: 
X-Spam-Status: No, score=-6.539 tagged_above=-999 required=5 tests=[AWL=0.060, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 agFueFvsdtSw for <behave@core3.amsl.com>;
	Wed, 14 May 2008 09:40:55 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 845F43A695D
	for <behave@ietf.org>; Wed, 14 May 2008 09:40:55 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,487,1204531200"; d="scan'208";a="98662519"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 14 May 2008 09:33:42 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m4EGXguo021003; 
	Wed, 14 May 2008 09:33:42 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4EGXgU7005948;
	Wed, 14 May 2008 16:33:42 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Iljitsch van Beijnum'" <iljitsch@gmail.com>,
	"'Philip Matthews'" <philip_matthews@magma.ca>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es><48286CFD.1080204@free.fr>
	<48287AE5.5010005@sipeerior.com><482882B7.2030806@free.fr><145B7DFA-E397-4184-8FA6-3C255078509F@muada.com><48289C15.3000102@free.fr>
	<4828A33E.1080700@sipeerior.com><4828ABBE.9010201@free.fr>
	<4828AE1B.9040901@sipeerior.com>
	<03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>
	<015801c8b50d$984b8eb0$c3f0200a@cisco.com>
	<8EFD78D3-46EC-4BA5-9F9A-B6F471B9C01F@gmail.com>
	<018601c8b511$0a83a410$c3f0200a@cisco.com>
	<2F594053-210D-49D6-A9C7-5245826854A1@gmail.com>
	<04fe01c8b531$5c086c60$c3f0200a@cisco.com>
	<ABFE5321-6872-4B67-ADDE-7380F8DE0AD9@gmail.com>
Date: Wed, 14 May 2008 09:33:41 -0700
Message-ID: <037601c8b5e0$4577f3d0$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <ABFE5321-6872-4B67-ADDE-7380F8DE0AD9@gmail.com>
Thread-Index: Aci1n6rMg5ogpHESQR23ZFjPkQylewAPUFyg
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2856; t=1210782822;
	x=1211646822; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Scalability=20of=20endpoint=
	20independent=20mapping |Sender:=20;
	bh=l2ouivWRDzzqpUt45lKuxBZeAqvjjpm9+U65XSD1CzY=;
	b=qhuRARZFaJU/8GFsGW9qkweyx03nvj2ZOoePHfHFJuOw01PZ4cYMZVyhjC
	dDS9lJJsEQhJOJY7NiOaCh8ums2szTJVtQX3ric1OnBzHQAHPU9GW1WKgfeP
	Mj7euhjoym;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

 =


> -----Original Message-----
> From: Iljitsch van Beijnum [mailto:iljitsch@gmail.com] =

> Sent: Wednesday, May 14, 2008 1:51 AM
> To: Dan Wing; Philip Matthews
> Cc: behave@ietf.org
> Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
> =

> On 13 mei 2008, at 21:41, Dan Wing wrote:
> =

> >> Unless I'm missing something this should actually be fairly
> >> straightforward: just STUN for TCP + endpoint independent mapping.
> =

> > STUN for TCP exists (draft-ietf-behave-rfc3489bis now specifies how
> > STUN-over-TCP works).
> =

> Excellent.
> =

> > Of course with NAT64 we could specify exactly how a NAT64 =

> is supposed
> > to work and maybe bypass much of the problem that STUNT found with
> > existing NATs.
> =

> Right. The good thing here is that we're not constrained by hundreds  =

> of existing implementations that all behave differently. And =

> existing  =

> CPEs can't work on the v6 side of a NAT64 universe anyway, so those  =

> aren't an issue at all.
> =

> I was thinking:
> =

> If an application wants to make use of endpoint independent mapping  =

> behavior by the NAT, wouldn't its first packets be towards a STUN(T)  =

> server? If we can detect this, providing endpoint independent =

> behavior  =

> where it's needed and using endpoint dependent mappings everywhere  =

> else is easy.

Someone else (R=E9mi Despr=E9s, I believe) had proposed doing that using
port numbers.  Doing it with port numbers would also be the first time =

that TCP behavior is different for different port numbers (the port =

1024 restriction does not change the behavior of TCP itself).  But
I see (below) that you are considering DPI rather than TCP port
numbers.

Another idea floating in my head is to use STUN-over-TCP to the =

NAT64's public IP address itself, which is trivial for the NAT64
to notice.  Essentially that is what is described in =

<http://tools.ietf.org/html/draft-wing-behave-nat-control-stun-usage-05>,
which is an expired draft.

> For TCP, another option would be a TCP option in the SYN from =

> the host to the STUNT server, or in the SYN/ACK from the STUNT =

> server back to the host, this is probably easier to do than deep =

> packet inspection to determine whether a random TCP session is =

> used for STUNT.

If the NAT64-aware box at the customer premise could make the decision
(somehow; I'm not sure how it could do that yet), the NAT64-aware box
could communicate the decision to the ISP's big NAT64-box-in-the-sky
using a simple-to-see trigger like that.

Unfortunately the application and host OS (Windows, OSX) couldn't set =

that TCP bit without changes to the TCP API and the TCP stack itself =

- which means an OS upgrade or, at minimum (if the vendors are =

motivated) an OS patch.

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May 14 10:15:58 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 36FE33A68A8;
	Wed, 14 May 2008 10:15:58 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C27C13A68A8
	for <behave@core3.amsl.com>; Wed, 14 May 2008 10:15:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.543
X-Spam-Level: 
X-Spam-Status: No, score=-6.543 tagged_above=-999 required=5 tests=[AWL=0.056, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 65C8PGJwunmB for <behave@core3.amsl.com>;
	Wed, 14 May 2008 10:15:52 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by core3.amsl.com (Postfix) with ESMTP id 3DA333A6837
	for <behave@ietf.org>; Wed, 14 May 2008 10:15:52 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,487,1204531200"; d="scan'208";a="26982804"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-5.cisco.com with ESMTP; 14 May 2008 10:15:14 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m4EHFEtE014816
	for <behave@ietf.org>; Wed, 14 May 2008 10:15:14 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m4EHFDf9012236
	for <behave@ietf.org>; Wed, 14 May 2008 17:15:14 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <behave@ietf.org>
Date: Wed, 14 May 2008 10:15:13 -0700
Message-ID: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Aci14hiZolNmytIpTjqh37p6kTtZcAAA8SNw
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=386; t=1210785314; x=1211649314;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20Dynamic=20Port=20Reuse |Sender:=20;
	bh=OR65nFmL6Up26UByMCNVqiwc1Wig+Ib/VTPNE62V3RU=;
	b=FKM3QrHkF6FoaFjnhPsfPRMLZgG6BUZRjODlCa6VS8cxIp41yj+cGPDWQx
	aAYZaWsy1llgBAvYpeu9st7nJdiWvd9RgQNmZ68IbeoCmby3ctYJqJSkew1V
	uwnnnwIIiP;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Subject: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

My strawman proposal is at:
http://tools.ietf.org/html/draft-wing-behave-dynamic-tcp-port-reuse-00 

Abstract:
  A strawman proposal is made to reduce public-facing TCP port use with
  large Network Address and Port Translators (NAPTs).  This proposal
  attempts to preserve emergent NAT traversal techniques.  It is
  anticipated that large NAPTs will be used for NAT64.

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May 14 10:23:50 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E0B753A68A8;
	Wed, 14 May 2008 10:23:50 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 318593A69D9
	for <behave@core3.amsl.com>; Wed, 14 May 2008 10:23:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level: 
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.038, 
	BAYES_00=-2.599]
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 L9joVgQjyZ0L for <behave@core3.amsl.com>;
	Wed, 14 May 2008 10:23:48 -0700 (PDT)
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173])
	by core3.amsl.com (Postfix) with ESMTP id C922A3A6813
	for <behave@ietf.org>; Wed, 14 May 2008 10:23:47 -0700 (PDT)
Received: by ug-out-1314.google.com with SMTP id u2so1366890uge.46
	for <behave@ietf.org>; Wed, 14 May 2008 10:22:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer;
	bh=Cnjga6aY8jAyHN8WVHSoSIthfdDVsIN6jZ4ePN3zztI=;
	b=dIuJ6+XqshT9IfDP/4JsPUdJcEf7oS5r++/lrsy/S76F0+EnM8MCNJr18R4z1IqhQ16rsVZT4687433CQzZV+19iCZgmrt6WGaXDYoXPU4HxMf5JaGJNj28QDkH1jb98x7xaxurYZeQLDsfHj9ODrWKEFnoaNTFT7PBj79zmgE4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer;
	b=bRpCosBD7xYRXzsNnkVp0rhLHh9RXUDu1TZB5Ga0DLekFcNbNnRmjdjHnLKql0JsuaRHrgxZNb7hfHlCjwMbK8kGSYCELzImq0hhwRHUcreF3BzSPcd5o5Xfq+ZHNDhnzqlJA5yHGkCToyz6GKylkRQxSHbRSwlGw4CermxxNKE=
Received: by 10.210.66.13 with SMTP id o13mr1189055eba.193.1210785757965;
	Wed, 14 May 2008 10:22:37 -0700 (PDT)
Received: from ?192.168.2.13? ( [89.7.138.167])
	by mx.google.com with ESMTPS id z40sm2328655ikz.7.2008.05.14.10.22.36
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Wed, 14 May 2008 10:22:37 -0700 (PDT)
Message-Id: <0AC1FB94-BF34-427E-8FA5-5222C67E2067@gmail.com>
From: Iljitsch van Beijnum <iljitsch@gmail.com>
To: "Dan Wing" <dwing@cisco.com>
In-Reply-To: <037601c8b5e0$4577f3d0$c3f0200a@cisco.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 14 May 2008 19:22:35 +0200
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es><48286CFD.1080204@free.fr>
	<48287AE5.5010005@sipeerior.com><482882B7.2030806@free.fr><145B7DFA-E397-4184-8FA6-3C255078509F@muada.com><48289C15.3000102@free.fr>
	<4828A33E.1080700@sipeerior.com><4828ABBE.9010201@free.fr>
	<4828AE1B.9040901@sipeerior.com>
	<03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>
	<015801c8b50d$984b8eb0$c3f0200a@cisco.com>
	<8EFD78D3-46EC-4BA5-9F9A-B6F471B9C01F@gmail.com>
	<018601c8b511$0a83a410$c3f0200a@cisco.com>
	<2F594053-210D-49D6-A9C7-5245826854A1@gmail.com>
	<04fe01c8b531$5c086c60$c3f0200a@cisco.com>
	<ABFE5321-6872-4B67-ADDE-7380F8DE0AD9@gmail.com>
	<037601c8b5e0$4577f3d0$c3f0200a@cisco.com>
X-Mailer: Apple Mail (2.919.2)
Cc: behave@ietf.org, 'Philip Matthews' <philip_matthews@magma.ca>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 14 mei 2008, at 18:33, Dan Wing wrote:

>> If an application wants to make use of endpoint independent mapping
>> behavior by the NAT, wouldn't its first packets be towards a STUN(T)
>> server? If we can detect this, providing endpoint independent
>> behavior where it's needed and using endpoint dependent mappings  =

>> everywhere
>> else is easy.

> Someone else (R=E9mi Despr=E9s, I believe) had proposed doing that using
> port numbers.  Doing it with port numbers would also be the first time
> that TCP behavior is different for different port numbers (the port
> 1024 restriction does not change the behavior of TCP itself).  But
> I see (below) that you are considering DPI rather than TCP port
> numbers.

I was.

If STUN always uses port 3478 then that's obviously a good way to  =

detect sessions towards a STUN server.

So if a host first contacts some random destination using source port  =

8000 and destination 3478, we know it's talking to a STUN server so we  =

need to make the mapping for source port 8000 address independent. But  =

if a session goes towards port 80 or what have you and the source port  =

isn't used in recent history by that host, we know the host doesn't  =

require endpoint independent mapping.

> Another idea floating in my head is to use STUN-over-TCP to the
> NAT64's public IP address itself, which is trivial for the NAT64
> to notice.

Yes, but how do hosts know to only use the NAT64's address as their  =

STUN server?

Don't STUN-aware applications use STUN servers that are preconfigured  =

by the application?

>> For TCP, another option would be a TCP option in the SYN from
>> the host to the STUNT server, or in the SYN/ACK from the STUNT
>> server back to the host, this is probably easier to do than deep
>> packet inspection to determine whether a random TCP session is
>> used for STUNT.

> If the NAT64-aware box at the customer premise could make the decision
> (somehow; I'm not sure how it could do that yet), the NAT64-aware box
> could communicate the decision to the ISP's big NAT64-box-in-the-sky
> using a simple-to-see trigger like that.

Right. Maybe add a router alert for good measure.  :-)

> Unfortunately the application and host OS (Windows, OSX) couldn't set
> that TCP bit without changes to the TCP API and the TCP stack itself
> - which means an OS upgrade or, at minimum (if the vendors are
> motivated) an OS patch.

Right, that's why I was thinking the option could also flow in the  =

direction from the STUN server to the NAT. Presumably, a STUN server  =

can more easily be set up to include such an option.

But if we can simply look for port 3478 that's a lot easier.

Iljitsch
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May 14 10:29:51 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DE05F3A686E;
	Wed, 14 May 2008 10:29:51 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BAE603A6819
	for <behave@core3.amsl.com>; Wed, 14 May 2008 10:29:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.546
X-Spam-Level: 
X-Spam-Status: No, score=-6.546 tagged_above=-999 required=5 tests=[AWL=0.053, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 rbQKHyqTUWeR for <behave@core3.amsl.com>;
	Wed, 14 May 2008 10:29:47 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id B20A63A6813
	for <behave@ietf.org>; Wed, 14 May 2008 10:29:47 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,487,1204531200"; d="scan'208";a="98687755"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 14 May 2008 10:29:09 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m4EHT9Z0031029; 
	Wed, 14 May 2008 10:29:09 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m4EHT9Sb008943;
	Wed, 14 May 2008 17:29:09 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Iljitsch van Beijnum'" <iljitsch@gmail.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es><48286CFD.1080204@free.fr>
	<48287AE5.5010005@sipeerior.com><482882B7.2030806@free.fr><145B7DFA-E397-4184-8FA6-3C255078509F@muada.com><48289C15.3000102@free.fr>
	<4828A33E.1080700@sipeerior.com><4828ABBE.9010201@free.fr>
	<4828AE1B.9040901@sipeerior.com>
	<03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>
	<015801c8b50d$984b8eb0$c3f0200a@cisco.com>
	<8EFD78D3-46EC-4BA5-9F9A-B6F471B9C01F@gmail.com>
	<018601c8b511$0a83a410$c3f0200a@cisco.com>
	<2F594053-210D-49D6-A9C7-5245826854A1@gmail.com>
	<04fe01c8b531$5c086c60$c3f0200a@cisco.com>
	<ABFE5321-6872-4B67-ADDE-7380F8DE0AD9@gmail.com>
	<037601c8b5e0$4577f3d0$c3f0200a@cisco.com>
	<0AC1FB94-BF34-427E-8FA5-5222C67E2067@gmail.com>
Date: Wed, 14 May 2008 10:29:09 -0700
Message-ID: <044701c8b5e8$04dbe860$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <0AC1FB94-BF34-427E-8FA5-5222C67E2067@gmail.com>
Thread-Index: Aci15x0UXu+PxHZVTxG+t52RgJOoUQAAEqFA
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3577; t=1210786149;
	x=1211650149; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Scalability=20of=20endpoint=
	20independent=20mapping |Sender:=20;
	bh=JQAt52lYEJbmaZezVastYQIDXE8LusQkVdMnjo/Llzo=;
	b=FxeZH4XL0yT+0QRkJW5b2SGzP8ElWXKS9dSyfDYjCspX9b88pjLl6ua8kQ
	PpHmvsBXGjaDWdUSyTI+UDArtqBa32WNs16Cv0r3+0XOzPIrPE+ECP3PENfj
	599mQqgTf0;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: behave@ietf.org, 'Philip Matthews' <philip_matthews@magma.ca>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

 =


> -----Original Message-----
> From: Iljitsch van Beijnum [mailto:iljitsch@gmail.com] =

> Sent: Wednesday, May 14, 2008 10:23 AM
> To: Dan Wing
> Cc: 'Philip Matthews'; behave@ietf.org
> Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
> =

> On 14 mei 2008, at 18:33, Dan Wing wrote:
> =

> >> If an application wants to make use of endpoint independent mapping
> >> behavior by the NAT, wouldn't its first packets be towards =

> a STUN(T)
> >> server? If we can detect this, providing endpoint independent
> >> behavior where it's needed and using endpoint dependent mappings  =

> >> everywhere
> >> else is easy.
> =

> > Someone else (R=E9mi Despr=E9s, I believe) had proposed doing that using
> > port numbers.  Doing it with port numbers would also be the =

> first time
> > that TCP behavior is different for different port numbers (the port
> > 1024 restriction does not change the behavior of TCP itself).  But
> > I see (below) that you are considering DPI rather than TCP port
> > numbers.
> =

> I was.
> =

> If STUN always uses port 3478 then that's obviously a good way to  =

> detect sessions towards a STUN server.
> =

> So if a host first contacts some random destination using =

> source port  =

> 8000 and destination 3478, we know it's talking to a STUN =

> server so we  =

> need to make the mapping for source port 8000 address =

> independent. But  =

> if a session goes towards port 80 or what have you and the =

> source port  =

> isn't used in recent history by that host, we know the host doesn't  =

> require endpoint independent mapping.
> =

> > Another idea floating in my head is to use STUN-over-TCP to the
> > NAT64's public IP address itself, which is trivial for the NAT64
> > to notice.
> =

> Yes, but how do hosts know to only use the NAT64's address as their  =

> STUN server?
> Don't STUN-aware applications use STUN servers that are =

> preconfigured by the application?

Yes, so you could configure that application so its STUN server is
the public IP address of the NAT64 box.  Or the application could
talk to any STUN server on the Internet and learn the IP address of
its NAT64 box (which is the mechanism described in =

draft-wing-behave-nat-control-stun-usage).

> >> For TCP, another option would be a TCP option in the SYN from
> >> the host to the STUNT server, or in the SYN/ACK from the STUNT
> >> server back to the host, this is probably easier to do than deep
> >> packet inspection to determine whether a random TCP session is
> >> used for STUNT.
> =

> > If the NAT64-aware box at the customer premise could make =

> > the decision
> > (somehow; I'm not sure how it could do that yet), the =

> > NAT64-aware box
> > could communicate the decision to the ISP's big NAT64-box-in-the-sky
> > using a simple-to-see trigger like that.
> =

> Right. Maybe add a router alert for good measure.  :-)

heh.

> > Unfortunately the application and host OS (Windows, OSX) =

> > couldn't set
> > that TCP bit without changes to the TCP API and the TCP stack itself
> > - which means an OS upgrade or, at minimum (if the vendors are
> > motivated) an OS patch.
> =

> Right, that's why I was thinking the option could also flow in the  =

> direction from the STUN server to the NAT. Presumably, a STUN server  =

> can more easily be set up to include such an option.
> =

> But if we can simply look for port 3478 that's a lot easier.

I am worried that could tie NAT64 too much to STUN.

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May 21 03:50:32 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CE2D13A6A0F;
	Wed, 21 May 2008 03:50:32 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 201F33A69A8
	for <behave@core3.amsl.com>; Wed, 21 May 2008 03:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 2YeD8GaUk5nF for <behave@core3.amsl.com>;
	Wed, 21 May 2008 03:50:31 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id 1A04528C1DC
	for <behave@ietf.org>; Wed, 21 May 2008 03:50:30 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m4LAoCoN029109 for <behave@ietf.org>; Wed, 21 May 2008 13:50:31 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 21 May 2008 13:49:42 +0300
Received: from esdhcp04158.research.nokia.com ([172.21.41.58]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 21 May 2008 13:49:42 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: behave@ietf.org
Date: Wed, 21 May 2008 13:49:42 +0300
User-Agent: KMail/1.9.9
References: <4810C3ED.7030901@ericsson.com> <48286F19.5090707@ericsson.com>
In-Reply-To: <48286F19.5090707@ericsson.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805211349.42900.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 21 May 2008 10:49:42.0447 (UTC)
	FILETIME=[600EDBF0:01C8BB30]
X-Nokia-AV: Clean
Subject: Re: [BEHAVE] Consensus call on Adding "Client" attribute to STUN
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Le Monday 12 May 2008 19:23:53 ext Magnus Westerlund, vous avez =E9crit=A0:
> I got all Yes, go for it and no against so I rule there to be consensus
> to add this attribute. Authors, please go ahead and add it.

By the way, which attribute number is to be requested for this? I'll update =

the test vectors when that's settled.

-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May 21 05:06:59 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9D2223A69E7;
	Wed, 21 May 2008 05:06:59 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9B9DF3A69E7
	for <behave@core3.amsl.com>; Wed, 21 May 2008 05:06:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.274
X-Spam-Level: 
X-Spam-Status: No, score=-6.274 tagged_above=-999 required=5 tests=[AWL=0.325, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 rbAErYc9eonp for <behave@core3.amsl.com>;
	Wed, 21 May 2008 05:06:52 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 611A93A699F
	for <behave@ietf.org>; Wed, 21 May 2008 05:06:51 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m4LC0gXh002907; Wed, 21 May 2008 07:06:50 -0500
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 21 May 2008 15:02:38 +0300
Received: from net-207.nrpn.net ([10.241.184.208]) by esebh102.NOE.Nokia.com
	over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 21 May 2008 15:02:37 +0300
Message-Id: <2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: ext Dan Wing <dwing@cisco.com>
In-Reply-To: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 21 May 2008 15:02:32 +0300
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>
X-Mailer: Apple Mail (2.919.2)
X-OriginalArrivalTime: 21 May 2008 12:02:37.0688 (UTC)
	FILETIME=[8FE7A780:01C8BB3A]
X-Nokia-AV: Clean
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi, Dan,

a few quick comments:

(1) Meta-comment: Why wouldn't large NAPT boxes simply use multiple  
public IP addresses to avoid running out of ports?

(2) I don't understand why ALGO-1 is claimed to support client/server  
cases well. Client/server communication is characterized by the server  
listening on a single well-known port. It's hence not possible to  
reuse the same source port on the NAPT for another connection, because  
that'd clash with an existing 5-tuple. ALGO-1 can only reuse source  
ports for connections to different services (on different destination  
ports), which is what Figure 1 shows.

(3) The changes to applications that ALGO-2 requires are more invasive  
than just signaling that UNSAF is being used, because applications may  
also need to change their transmission behavior to conform to the  
"hold time" the NAPT now uses. It's IMO problematic to assume any  
application or transport protocol changes will happen.

(4) Regarding cleanup for ALGO-2 and ALGO-3, you say that the NAT can  
start reusing the port if it sees FIN or RST or other shutdown  
indication (ICMP?). That is not sufficient. RFC793 and especially  
draft-ietf-tcpm-tcpsecure specify that for examples RSTs MUST be  
ignored if they don't satisfy certain validity checks. draft-ietf-tcpm- 
icmp-attacks discusses similar deployed validity checks on ICMPs.

Lars
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May 21 07:15:38 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4CB1028C111;
	Wed, 21 May 2008 07:15:38 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CEDEC28C0FA
	for <behave@core3.amsl.com>; Wed, 21 May 2008 07:15:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.349
X-Spam-Level: 
X-Spam-Status: No, score=-1.349 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_74=0.6,
	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 9Roa9fJnETD2 for <behave@core3.amsl.com>;
	Wed, 21 May 2008 07:15:32 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id 5E29028C111
	for <behave@ietf.org>; Wed, 21 May 2008 07:15:32 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id B54A93EA107;
	Wed, 21 May 2008 16:15:35 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 422083EA0B2;
	Wed, 21 May 2008 16:15:35 +0200 (CEST)
Message-ID: <48342E90.8050109@free.fr>
Date: Wed, 21 May 2008 16:15:44 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es><48286CFD.1080204@free.fr>	<48287AE5.5010005@sipeerior.com><482882B7.2030806@free.fr><145B7DFA-E397-4184-8FA6-3C255078509F@muada.com><48289C15.3000102@free.fr>	<4828A33E.1080700@sipeerior.com><4828ABBE.9010201@free.fr>	<4828AE1B.9040901@sipeerior.com>	<03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>	<015801c8b50d$984b8eb0$c3f0200a@cisco.com>	<8EFD78D3-46EC-4BA5-9F9A-B6F471B9C01F@gmail.com>	<018601c8b511$0a83a410$c3f0200a@cisco.com>	<2F594053-210D-49D6-A9C7-5245826854A1@gmail.com>	<04fe01c8b531$5c086c60$c3f0200a@cisco.com>	<ABFE5321-6872-4B67-ADDE-7380F8DE0AD9@gmail.com>
	<037601c8b5e0$4577f3d0$c3f0200a@cisco.com>
In-Reply-To: <037601c8b5e0$4577f3d0$c3f0200a@cisco.com>
Cc: behave@ietf.org, 'Philip Matthews' <philip_matthews@magma.ca>,
	'Iljitsch van Beijnum' <iljitsch@gmail.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Dan Wing wrote :
>  =

> =

>> -----Original Message-----
>> From: Iljitsch van Beijnum [mailto:iljitsch@gmail.com] =


>> I was thinking:
>>
>> If an application wants to make use of endpoint independent mapping  =

>> behavior by the NAT, wouldn't its first packets be towards a STUN(T)  =

>> server? If we can detect this, providing endpoint independent =

>> behavior  =

>> where it's needed and using endpoint dependent mappings everywhere  =

>> else is easy.
> =

> Someone else (R=E9mi Despr=E9s, I believe) had proposed doing that using
> port numbers.
Right.

AFAIK, this is still quite effective a solution, and IMU a really simple =

one:
It goes like this:

1. To be an *address-port sparing NAT*, a NAT MUST do mappings that are =

endpoint-dependent if initiated with external-host ports equal to 80 =

(HTTP) or in the range 6881-6889 (BitTorrent).


2. To be well behaved, a NAT  MUST do  mappings that are =

endpoint-independent if initiated with external-host ports in the =

1990-1992 range (STUN).

- This range is that of STUN, STUNT and TURN.
- As such, they are AFAIK those of the only IETF approved public address =

and port discovery mechanisms (if not, the rule has to be completed).
- STUN and TURN are used in paricular by ICE, the tool for SIP to =

operate across existing NATS, a major source of sessions needing =

endpoint-independent mapping).
- Note that, after discovery, ANY application, standard or proprietary, =

may use the reserved address&port couple.


3. NATs MAY also do mappings that are endpoint-independent if initiated =

with external-host ports known to be those of applications compatible =

with it (POP3, SMTP, IMAP, NNTP, Telnet, SNMP, IPsec over UDP...)

> Doing it with port numbers would also be the first time =

> that TCP behavior is different for different port numbers (the port =

> 1024 restriction does not change the behavior of TCP itself). =

IMU, there are no more differences between possible TCP behaviors with =

this approach than with NAT traversal (=3D> neither theoretical nor =

practical problem).


Regards.

R=E9mi
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May 21 11:09:08 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AFCF228C222;
	Wed, 21 May 2008 11:09:08 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C3CED28C220
	for <behave@core3.amsl.com>; Wed, 21 May 2008 11:09:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 qxDf4AXDvS3n for <behave@core3.amsl.com>;
	Wed, 21 May 2008 11:09:05 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 4D4F328C11A
	for <behave@ietf.org>; Wed, 21 May 2008 11:09:05 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,522,1204531200"; d="scan'208";a="70755525"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-3.cisco.com with ESMTP; 21 May 2008 11:09:09 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m4LI99iA030944; 
	Wed, 21 May 2008 11:09:09 -0700
Received: from dwingwxp01 (sjc-vpn3-17.cisco.com [10.21.64.17])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4LI993A028696;
	Wed, 21 May 2008 18:09:09 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Lars Eggert'" <lars.eggert@nokia.com>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>
	<2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>
Date: Wed, 21 May 2008 08:09:08 -1000
Message-ID: <0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Aci7OyzZ66ZnRvEFS5G38hd0vUwFzQAMPe6Q
In-Reply-To: <2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2878; t=1211393349;
	x=1212257349; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Dynamic=20Port=20Reuse
	|Sender:=20; bh=tIRQHA3jHMNMnMC2CYo8TOpvr+/R9seExA311jY5sh0=;
	b=Cn8h0GzgGbxgSEsjrD99Jjxu77V9mEvMbKOU67w8DEnPK45a0epcjCKA+Q
	nN1ec6kTewXA9o2QE47B5jeTMR0uIRcu15s5GNDwzhpkaghhmp4cRKDnJVpd
	YQaO2YNVsG;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

 

> -----Original Message-----
> From: Lars Eggert [mailto:lars.eggert@nokia.com] 
> Sent: Wednesday, May 21, 2008 2:03 AM
> To: ext Dan Wing
> Cc: behave@ietf.org
> Subject: Re: [BEHAVE] Dynamic Port Reuse
> 
> Hi, Dan,
> 
> a few quick comments:
> 
> (1) Meta-comment: Why wouldn't large NAPT boxes simply use multiple  
> public IP addresses to avoid running out of ports?

Sure, but that, too, has complications.  One that Greg Lebovitz 
mentioned at two different BEHAVE working group meetings is that
some HTTP servers, or their back-end software, was sensitive to
multiple connections from the same client arriving from different
IP addresses; it was suggested that the HTTP server's cookies
were tied to the client's IP address.

And the primary motivation for me to write this up was v4 address
conservation on the NAT64 box.

> (2) I don't understand why ALGO-1 is claimed to support 
> client/server  
> cases well. Client/server communication is characterized by 
> the server  
> listening on a single well-known port. It's hence not possible to  
> reuse the same source port on the NAPT for another 
> connection, because  
> that'd clash with an existing 5-tuple.
>
> ALGO-1 can only reuse source  
> ports for connections to different services (on different 
> destination  
> ports), which is what Figure 1 shows.

ALGO-1 can use the same source TCP port if the two TCP 
connections are going to two servers (e.g., www.cnn.com/80, 
www.ietf.org/80).

> (3) The changes to applications that ALGO-2 requires are more 
> invasive  
> than just signaling that UNSAF is being used, because 
> applications may  
> also need to change their transmission behavior to conform to the  
> "hold time" the NAPT now uses. It's IMO problematic to assume any  
> application or transport protocol changes will happen.

Everthing is a tradeoff.  Would extending the proposed timer from
30 seconds to 60 or 90 or 120 seconds reduce your concern?

Several other people have proposed using port numbers to decide if 
UNSAF was being used, under the assmption that TCP/80, TCP/110 
(POP3), etc., don't use UNSAF.  That is certainly another direction 
to pursue.  My concern with that mechanism is that it would create
the first instance where a NAT's behavior is radically different
based on the port number.

> (4) Regarding cleanup for ALGO-2 and ALGO-3, you say that the 
> NAT can  
> start reusing the port if it sees FIN or RST or other shutdown  
> indication (ICMP?). That is not sufficient. RFC793 and especially  
> draft-ietf-tcpm-tcpsecure specify that for examples RSTs MUST be  
> ignored if they don't satisfy certain validity checks. 
> draft-ietf-tcpm- 
> icmp-attacks discusses similar deployed validity checks on ICMPs.

Sure, I'll clean that up in a future version.  That's easy.

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May 21 20:24:59 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7ABBA3A689A;
	Wed, 21 May 2008 20:24:59 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 500EB3A689A
	for <behave@core3.amsl.com>; Wed, 21 May 2008 20:24:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.279
X-Spam-Level: 
X-Spam-Status: No, score=-5.279 tagged_above=-999 required=5 tests=[AWL=1.321, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 OAj5mS+aAYjS for <behave@core3.amsl.com>;
	Wed, 21 May 2008 20:24:56 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id AFFEB3A680D
	for <behave@ietf.org>; Wed, 21 May 2008 20:24:56 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,523,1204531200"; d="scan'208";a="102260755"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 21 May 2008 20:24:55 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4M3OtIO022210; 
	Wed, 21 May 2008 20:24:55 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4M3OthC019030;
	Thu, 22 May 2008 03:24:55 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 21 May 2008 20:24:54 -0700
Received: from [10.32.241.148] ([10.32.241.148]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 21 May 2008 20:24:54 -0700
Message-ID: <4834E78D.6000007@cisco.com>
Date: Wed, 21 May 2008 23:25:01 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11441.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es><48286CFD.1080204@free.fr>	<48287AE5.5010005@sipeerior.com><482882B7.2030806@free.fr><145B7DFA-E397-4184-8FA6-3C255078509F@muada.com><48289C15.3000102@free.fr>	<4828A33E.1080700@sipeerior.com><4828ABBE.9010201@free.fr>	<4828AE1B.9040901@sipeerior.com>	<03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>	<015801c8b50d$984b8eb0$c3f0200a@cisco.com>	<8EFD78D3-46EC-4BA5-9F9A-B6F471B9C01F@gmail.com>	<018601c8b511$0a83a410$c3f0200a@cisco.com>	<2F594053-210D-49D6-A9C7-5245826854A1@gmail.com>	<04fe01c8b531$5c086c60$c3f0200a@cisco.com>
	<563A472D-30B9-45E9-8E2C-009CF1B4045F@magma.ca>
In-Reply-To: <563A472D-30B9-45E9-8E2C-009CF1B4045F@magma.ca>
X-OriginalArrivalTime: 22 May 2008 03:24:54.0625 (UTC)
	FILETIME=[674A2510:01C8BBBB]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=7068; t=1211426695;
	x=1212290695; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20[BEHAVE]=20Scalability=20of=20endpoint=
	20independent=20mapping |Sender:=20;
	bh=bwiFwoKSzwOT4C+41VGPhZZ2Rk6On9iCqyHeg8OKj7g=;
	b=ZybCjEl0y2CoRoaYUEwS4b5T2gzrrVcFiiBA5bGWE6DrLnR7qicvMjCKlf
	rcLldBGSRKup/K4q8qX3tivDO1Pm3L3G91X+mRnuh0NlWH8E/yFV7j1fm90d
	2cO/uyJXfT5Y20dDvE5oLi44FQ3feYIuRBG69MOa+aBbyNZV34kuw=;
Authentication-Results: sj-dkim-1; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: Behave WG <behave@ietf.org>, Iljitsch van Beijnum <iljitsch@gmail.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Sorry for chiming in late here.

Philip is making a REALLY important point. This has NOTHING to do with 
with endpoint independent vs. endpoint dependent mapping. Iljitsch is 
raising issues about a currently undefined behavior that, frankly, 
fundamentally redefines the assumptions in RFC 4787.

RFC 4787 fundamentally assumes that NATs maintain mapping rules which 
translate one IP address and port to another IP address and port, and 
that this translation is a function ONLY of the address being 
translated. In particular, RFC 4787 assumes that, once a mapping is 
defined, a packet received on the external side of the NAT can be natted 
by looking up the destination IP/port in a table and translating it to 
the associated internal IP/port. Similarly in the reverse direction. 
That is, though the initial assignment of the mapping may be a function 
of the 5-tuple, the actual translation operation performed by the NAT is 
a function of the translated IP address and port ONLY.

What Iljitsch is suggesting is that:

1. this translation can be a function of the full 5-tuple, such that two 
packets received on the external interface, whose destination IP/ports 
are the same, but whose source IP/ports are different, can be mapped to 
different internal IP addresses and ports, and

2. the result is that two internal IP addresses and ports which are 
different can be translated to the same external IP address and port


That kind of behavior does not map to any of the existing mapping rules. 
  Lets look at all of them:

endpoint independent mapping:

          The NAT reuses the port mapping for subsequent packets sent
          from the same internal IP address and port (X:x) to any
          external IP address and port.  Specifically, X1':x1' equals
          X2':x2' for all values of Y2:y2.

This implies that two different internal transport addresses X:x and A:a 
cannot share the same mapping X1':x1'. So endpoint independent mapping 
'rules out' the case Iljitsch is talking about.

address-dependent mapping:

          The NAT reuses the port mapping for subsequent packets sent
          from the same internal IP address and port (X:x) to the same
          external IP address, regardless of the external port.
          Specifically, X1':x1' equals X2':x2' if and only if, Y2 equals
          Y1.


Well, this says nothing at all about the behavior of mappings across two 
different internal IP addresses and ports. Its only talking about the 
mappings from a single internal IP address and port (X:x).

address and port-dependent mapping:

  The NAT reuses the port mapping for subsequent packets sent
          from the same internal IP address and port (X:x) to the same
          external IP address and port while the mapping is still active.
          Specifically, X1':x1' equals X2':x2' if and only if, Y2:y2
          equals Y1:y1.

As above. Says nothing about the mappings as they relate to different IP 
addresses and ports.


So really, the model that is being suggested looks different than the 
figure in the Figure on page 6. Instead, we need to draw a picture that 
looks like this:


   Please view in a fixed-width font such as
                    Courier.










                                              E
           +------+                 +------+  x
           |  Y1  |                 |  Y2  |  t
           +--+---+                 +---+--+  e
              | Y1:y1            Y2:y2  |     r
              +----------+   +----------+     n
                         |   |                a
                 X1':x1' |   | X2':x2'        l
                      +--+---+-+
           ...........|   NAT  |...............
                      +--+---+-+              I
                         |   |                n
                         |   |                t
                         |   |                e
                  +------+   +------+         r
                  |                 |         n
                  |x1               |x2       a
               +-----+           +-----+      l
               | X1  |           | X2  |
               +-----+           +-----+


        From internal to external:

        X1':x1' = f(X1:x1,Y1:y1)
        X2':x2' = f(X2:x2,Y2:y2)


        From external to internal:

        X1:x2 = f(Y1:y1,X1':x1')
        X2:x2 = f(Y2:y2,X2':x2')


Note that, I believe this model would allow for mapping rules to be 
defined which still work well for p2p apps but give you the benefits of 
address and port reuse across different sessions, without needing to 
define rules based on what application is being used.

-Jonathan R.


Philip Matthews wrote:
> If I understand things correctly, what Iljitsch is suggesting is not  
> "address-dependent" mapping as I understand it. My understanding of  
> "address-dependent" mapping is that a new transport address (on the  
> public side of the NAT) is assigned by the NAT to every new  
> destination. However, Iljitsch wants instead to re-use the same  
> transport address for many different destinations.
> 
> Let me give an example.
> Let A and B be two nodes on the private side of the NAT.
> Let X and Y be two nodes on the public side of the NAT.
> Let (T,t) be some transport address assigned to the public side of the  
> NAT.
> 
> Now consider the following flows:
> Private       Public
> Node          Node
> (A,a) ------> (X,x1)
> (A,a) ------> (X,x2)
> (A,a) ------> (Y,y1)
> (B,b2) -----> (Y,y2)
> 
> - Endpoint-independent mapping would assign the same transport address  
> to the first three, and a different transport addresses to the last one.
> - Address-dependent mapping would assign the same transport address to  
> the first two, and different transport addresses to the last two.
> - Address-and-port-dependent mapping would assign different transport  
> addresses to all of these.
> - But what Iljitsch wants to do is to assign the same transport  
> address (T,t) for all of these.
>  From the NAT perspective, (T,t) can be used for all of these because,  
> when the response comes back from the public node, the NAT can  
> determine the private node to forward it to by which public node sent  
> the packet. For example, it would have a rule that says: if the packet  
> is destined for (T,t) and came from (X,x1), then change the  
> destination address to (A,a).
> 
> I don't yet understand the implications of this, but I thought I  
> should point it out.
> 
> - Philip
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   499 Thornall St.
Cisco Fellow                                   Edison, NJ 08837
Cisco, Voice Technology Group
jdrosen@cisco.com
http://www.jdrosen.net                         PHONE: (408) 902-3084
http://www.cisco.com
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May 21 20:41:21 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B1AE93A691B;
	Wed, 21 May 2008 20:41:21 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D6F563A68BE
	for <behave@core3.amsl.com>; Wed, 21 May 2008 20:41:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.789
X-Spam-Level: 
X-Spam-Status: No, score=-5.789 tagged_above=-999 required=5 tests=[AWL=0.510, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 18auSE6WgRWp for <behave@core3.amsl.com>;
	Wed, 21 May 2008 20:41:19 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id DC75F3A6838
	for <behave@ietf.org>; Wed, 21 May 2008 20:41:19 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,523,1204531200"; d="scan'208";a="71000087"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 21 May 2008 20:41:25 -0700
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4M3fPi3004568; 
	Wed, 21 May 2008 20:41:25 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-4.cisco.com (8.13.8/8.13.8) with ESMTP id m4M3fPL9000568;
	Thu, 22 May 2008 03:41:25 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 21 May 2008 20:41:06 -0700
Received: from [10.32.241.148] ([10.32.241.148]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 21 May 2008 20:41:06 -0700
Message-ID: <4834EB5A.8030300@cisco.com>
Date: Wed, 21 May 2008 23:41:14 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?=
 <remi.denis-courmont@nokia.com>
References: <4810C3ED.7030901@ericsson.com> <48286F19.5090707@ericsson.com>
	<200805211349.42900.remi.denis-courmont@nokia.com>
In-Reply-To: <200805211349.42900.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 22 May 2008 03:41:06.0934 (UTC)
	FILETIME=[AAD4B960:01C8BBBD]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=767; t=1211427685; x=1212291685;
	c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20[BEHAVE]=20Consensus=20call=20on=20Addi
	ng=20=22Client=22=20attribute=20to=20STUN |Sender:=20;
	bh=IQ+X3RhposIo4ALEa9+iJZXktaR8FS1wGOW7a5TOH7Q=;
	b=bfMZp9Mofdr68IoNHbw+06mM/mNydEZeFEeX6wq6bqOzrFrgWHSylPAjq9
	I26kSJmhvrUWpPps9ITEM4DiLv4dLIURmqmsdFezdVkZKoJbkWE14c0MJD95
	dj1ykDcPv38nExnWKPMlWoPO27tm8ng1/m4Vb13FCucE4J2N327XE=;
Authentication-Results: sj-dkim-1; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Consensus call on Adding "Client" attribute to STUN
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I'm about to start making edits. Once I put it in I'll post. FWIW, I =

also support this change.

-Jonathan R.

R=E9mi Denis-Courmont wrote:
> Le Monday 12 May 2008 19:23:53 ext Magnus Westerlund, vous avez =E9crit :
>> I got all Yes, go for it and no against so I rule there to be consensus
>> to add this attribute. Authors, please go ahead and add it.
> =

> By the way, which attribute number is to be requested for this? I'll upda=
te =

> the test vectors when that's settled.
> =


-- =

Jonathan D. Rosenberg, Ph.D.                   499 Thornall St.
Cisco Fellow                                   Edison, NJ 08837
Cisco, Voice Technology Group
jdrosen@cisco.com
http://www.jdrosen.net                         PHONE: (408) 902-3084
http://www.cisco.com
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed May 21 20:44:08 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 288B83A6889;
	Wed, 21 May 2008 20:44:08 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 85BD43A6821
	for <behave@core3.amsl.com>; Wed, 21 May 2008 20:44:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.109
X-Spam-Level: 
X-Spam-Status: No, score=-6.109 tagged_above=-999 required=5 tests=[AWL=0.490, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 SYRKm9R47h3c for <behave@core3.amsl.com>;
	Wed, 21 May 2008 20:44:06 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 7AA773A6889
	for <behave@ietf.org>; Wed, 21 May 2008 20:44:06 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,523,1204531200"; d="scan'208";a="102267388"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 21 May 2008 20:44:12 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4M3iCdg008663; 
	Wed, 21 May 2008 20:44:12 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4M3iCZY001844;
	Thu, 22 May 2008 03:44:12 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 21 May 2008 20:44:12 -0700
Received: from [10.32.241.148] ([10.32.241.148]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 21 May 2008 20:44:11 -0700
Message-ID: <4834EC13.1070707@cisco.com>
Date: Wed, 21 May 2008 23:44:19 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <200804220829.18682.simon.perreault@viagenie.ca>
	<2F15E765-DFF3-4F31-A9BD-2701E42A5360@magma.ca>
In-Reply-To: <2F15E765-DFF3-4F31-A9BD-2701E42A5360@magma.ca>
X-OriginalArrivalTime: 22 May 2008 03:44:11.0911 (UTC)
	FILETIME=[1915F970:01C8BBBE]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1605; t=1211427852;
	x=1212291852; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20[BEHAVE]=20Transaction=20lifetime
	|Sender:=20; bh=dfB7PmBbCe6tqNegeNy+8qeNejYL+a7QoxMfpQFA3y8=;
	b=kvFy2L6ITT4zxZEXiesOXLDNKJ0zQmCBCtwAvfEbOw6dzqcKeTsL2hvJEC
	BqKhVgkIMhq1YYGuILxEd02KjRvsfSMYdfCjN7/ezXU9H0OJfTYQyus4n2RR
	HY6LMsdriRqUpcRniTMVJuvKplYL26pCH/12j7kyUDdde/m2Uats4=;
Authentication-Results: sj-dkim-1; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Transaction lifetime
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Yup, its a bug. Fixed.

-Jonathan R.

Philip Matthews wrote:
> I think the right answer is "40 seconds".
> 
> In earlier versions of the draft, the last retransmission timer  
> expired in slightly under 10 seconds from the start of the  
> transaction. However, during IESG review, the retransmission timers  
> were lengthened and by default now expire slightly before 40 seconds.
> 
> - Philip
> 
> 
> On Tue, 22-Apr-08, at 08:29 , Simon Perreault wrote:
>> In [draft-ietf-behave-rfc3489bis-15], Section 7.3.1, there is the  
>> following
>> text:
>>
>>   If the request uses UDP transport and is a retransmission of a
>>   request for which the server has already generated a success  
>> response
>>   within the last 40 seconds, the server MUST retransmit the same
>>   success response.  One way for a server to do this is to remember  
>> all
>>   transaction IDs received over UDP and their corresponding responses
>>   in the last 10 seconds.
>>
>> So, which one is it? 40 or 10 seconds?
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>>
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   499 Thornall St.
Cisco Fellow                                   Edison, NJ 08837
Cisco, Voice Technology Group
jdrosen@cisco.com
http://www.jdrosen.net                         PHONE: (408) 902-3084
http://www.cisco.com
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu May 22 00:54:25 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5E92C28C1AD;
	Thu, 22 May 2008 00:54:25 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8B1DE28C1AD
	for <behave@core3.amsl.com>; Thu, 22 May 2008 00:54:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.411
X-Spam-Level: 
X-Spam-Status: No, score=-1.411 tagged_above=-999 required=5 tests=[AWL=0.538, 
	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 LTRcwQxcQd6P for <behave@core3.amsl.com>;
	Thu, 22 May 2008 00:54:23 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id A10EC28C117
	for <behave@ietf.org>; Thu, 22 May 2008 00:54:23 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id A0D933EA0CA
	for <behave@ietf.org>; Thu, 22 May 2008 09:54:28 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 433FB3EA11A
	for <behave@ietf.org>; Thu, 22 May 2008 09:54:28 +0200 (CEST)
Message-ID: <483526BD.1090308@free.fr>
Date: Thu, 22 May 2008 09:54:37 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Behave WG <behave@ietf.org>
Subject: [BEHAVE] Address-port sparing NATs - a proposal
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

This is a correction of the previous proposal in
http://www.ietf.org/mail-archive/web/behave/current/msg03875.html
where Teredo, included in earlier version, was (obviously) missing.

It also includes DNS as an application that can generate many transport =

connections and doesn't need endpoint-independent mapping.

The goal is to provide a practical answer to the (IMO very pertinent) =

concern expressed in =

http://www.ietf.org/mail-archive/web/behave/current/msg03821.html.


PROPOSAL:
1. A NAT, to be an *address-port sparing NAT*,  MUST do mappings that
are endpoint-dependent if initiated with external-host ports equal to 80
(HTTP), or equal to 53 (DNS), or in the range 6881-6889 (BitTorrent).

2. A NAT  MUST do  mappings that are endpoint-independent if initiated
with external-host ports in the 1990-1992 range (STUN) or equal to 3544
(Teredo).

3. NATs MAY also do mappings that are endpoint-independent if initiated
with external-host ports known to be those of applications compatible
with it (POP3, SMTP, IMAP, NNTP, Telnet, SNMP, IPsec over UDP...).



NOTES:
The range of STUN is also that of STUNT and TURN.

AFAIK, STUN and Teredo cover the NAT address-port discovery mechanisms =

endorsed by IETF (if not, the rule has to be completed).

After NAT address-port discovery, ANY application, that needed =

endpoint-independent mapping may use the reserved address-port couple.

RFC4787 says: "REQ-1:  A NAT MUST have an "Endpoint-Independent Mapping" =

behavior." but, formally, rule 2 above also says that NATs MUST have =

such a behavior. The new point is that it doesn't have it for ALL =

transports connections (with the effect that address-port couples are =

used sparingly).


R=E9mi
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu May 22 07:58:54 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3881E3A67EF;
	Thu, 22 May 2008 07:58:54 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 315CF28C13A
	for <behave@core3.amsl.com>; Thu, 22 May 2008 07:58:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.43
X-Spam-Level: 
X-Spam-Status: No, score=-6.43 tagged_above=-999 required=5 tests=[AWL=0.169, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 FxSOo7e5kIy6 for <behave@core3.amsl.com>;
	Thu, 22 May 2008 07:58:52 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id D089F3A63EC
	for <behave@ietf.org>; Thu, 22 May 2008 07:58:51 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m4MEwStv004181; Thu, 22 May 2008 17:58:54 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 22 May 2008 17:58:45 +0300
Received: from net-226.nrpn.net ([10.241.184.208]) by esebh102.NOE.Nokia.com
	over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 22 May 2008 17:58:43 +0300
Message-Id: <DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: ext Dan Wing <dwing@cisco.com>
In-Reply-To: <0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Thu, 22 May 2008 17:58:37 +0300
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>
	<2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>
	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>
X-Mailer: Apple Mail (2.919.2)
X-OriginalArrivalTime: 22 May 2008 14:58:44.0628 (UTC)
	FILETIME=[54B47D40:01C8BC1C]
X-Nokia-AV: Clean
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi,

On 2008-5-21, at 21:09, ext Dan Wing wrote:
>> (1) Meta-comment: Why wouldn't large NAPT boxes simply use multiple
>> public IP addresses to avoid running out of ports?
>
> Sure, but that, too, has complications.  One that Greg Lebovitz
> mentioned at two different BEHAVE working group meetings is that
> some HTTP servers, or their back-end software, was sensitive to
> multiple connections from the same client arriving from different
> IP addresses; it was suggested that the HTTP server's cookies
> were tied to the client's IP address.

OK, so to work around that bug, you'd need to map NAT clients to  
public addresses persistently, and you'd loose some multiplexing  
efficiency.

> And the primary motivation for me to write this up was v4 address
> conservation on the NAT64 box.

Understood, but are we really _that_ stressed for v4 space yet?

>> ALGO-1 can only reuse source
>> ports for connections to different services (on different
>> destination
>> ports), which is what Figure 1 shows.
>
> ALGO-1 can use the same source TCP port if the two TCP
> connections are going to two servers (e.g., www.cnn.com/80,
> www.ietf.org/80).

Sure, but that's equivalent to the above in that the 5-tuple is unique.

I think I misunderstood the "ALGO-1 should work very well for client/ 
server applications" part. ALGO-2 would actually better for (non- 
UNSAF) client/server apps, in the sense that it allows more  
multiplexing.

>> (3) The changes to applications that ALGO-2 requires are more
>> invasive
>> than just signaling that UNSAF is being used, because
>> applications may
>> also need to change their transmission behavior to conform to the
>> "hold time" the NAPT now uses. It's IMO problematic to assume any
>> application or transport protocol changes will happen.
>
> Everthing is a tradeoff.  Would extending the proposed timer from
> 30 seconds to 60 or 90 or 120 seconds reduce your concern?

No, because irrespective of what the hold time is, defining one is  
what can potentially be a problem, because the NAPT now assumes that  
if an app hasn't done X in time Y, it will never do so.

But given that NAPTs aren't behaving very consistently anyway, maybe  
the hold time won't matter. Someone should run some experiments :-)

> Several other people have proposed using port numbers to decide if
> UNSAF was being used, under the assmption that TCP/80, TCP/110
> (POP3), etc., don't use UNSAF.  That is certainly another direction
> to pursue.  My concern with that mechanism is that it would create
> the first instance where a NAT's behavior is radically different
> based on the port number.

Right. IMO that proposal goes counter to the idea behind BEHAVE, which  
is to make NATs more regularized. Having the NAPT act differently  
based on what port numbers are used actually makes their behavior more  
diverse instead of more regularized.

The key question is how a NAPT can accurately differentiate apps that  
use UNSAF from ones that don't, because that's the characteristic that  
can be used to drive more efficient connection multiplexing. You  
propose doing this based on the observable transmission behavior,  
Iljitsch/Remi have suggested doing it based on destination ports. Both  
have pros and cons. Do other options exist?

Lars

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu May 22 08:58:58 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2CD413A6BF7;
	Thu, 22 May 2008 08:58:58 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 942743A6BF9
	for <behave@core3.amsl.com>; Thu, 22 May 2008 08:58:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.486
X-Spam-Level: 
X-Spam-Status: No, score=-1.486 tagged_above=-999 required=5 tests=[AWL=0.463, 
	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 t0cSJB0LMLf6 for <behave@core3.amsl.com>;
	Thu, 22 May 2008 08:58:55 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id 91CBE3A6BE7
	for <behave@ietf.org>; Thu, 22 May 2008 08:58:55 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 8F8C93EA12F;
	Thu, 22 May 2008 17:59:02 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 462F73EA0AB;
	Thu, 22 May 2008 17:59:02 +0200 (CEST)
Message-ID: <4835984F.6080504@free.fr>
Date: Thu, 22 May 2008 17:59:11 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Lars Eggert <lars.eggert@nokia.com>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>
	<DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
In-Reply-To: <DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
Cc: behave@ietf.org, ext Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Lars Eggert wrote :

>> Several other people have proposed using port numbers to decide if
>> UNSAF was being used, under the assmption that TCP/80, TCP/110
>> (POP3), etc., don't use UNSAF.  That is certainly another direction
>> to pursue.  My concern with that mechanism is that it would create
>> the first instance where a NAT's behavior is radically different
>> based on the port number.
> =

> Right. IMO that proposal goes counter to the idea behind BEHAVE, which  =

> is to make NATs more regularized. Having the NAPT act differently  =

> based on what port numbers are used actually makes their behavior more  =

> diverse instead of more regularized.

IMU, using a new method to solve a problem that has not been solved yet =

is not per se a problem.

Also, isn't it true that all ALGs that identify applications based on =

port numbers, and act specifically based on that, have already =

introduced NAT behaviors that depend on port numbers?

Finally, trying to identify applications based on timings of established =

connections seems to me unnecessarily complex and unreliable, especially =

to solve a problem that is trivial if ports are used.

For more details on how port-based application identification can =

contribute to "regularize" NATs, at least those that have to  use =

addresses and ports sparingly:
http://www.ietf.org/mail-archive/web/behave/current/msg03880.html

R=E9mi
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu May 22 09:15:36 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6BC8E28C1B1;
	Thu, 22 May 2008 09:15:36 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1A57C28C1B8
	for <behave@core3.amsl.com>; Thu, 22 May 2008 09:15:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, 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 fupvGgqeh6fa for <behave@core3.amsl.com>;
	Thu, 22 May 2008 09:15:16 -0700 (PDT)
Received: from mail.sipeerior.com (mail.sipeerior.com [128.239.5.131])
	by core3.amsl.com (Postfix) with ESMTP id B35D928C18F
	for <behave@ietf.org>; Thu, 22 May 2008 09:15:16 -0700 (PDT)
Received: from vuelta.local (unknown [128.239.5.171])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.sipeerior.com (Postfix) with ESMTP id B1AFA505B01;
	Thu, 22 May 2008 12:05:28 -0400 (EDT)
Message-ID: <483599C0.4030009@sipeerior.com>
Date: Thu, 22 May 2008 12:05:20 -0400
From: Bruce Lowekamp <lowekamp@sipeerior.com>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
References: <483526BD.1090308@free.fr>
In-Reply-To: <483526BD.1090308@free.fr>
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Address-port sparing NATs - a proposal
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

This looks like it's going to break p2p apps if it's deployed.

R=E9mi Despr=E9s wrote:
> PROPOSAL:
> 1. A NAT, to be an *address-port sparing NAT*,  MUST do mappings that
> are endpoint-dependent if initiated with external-host ports equal to 80
> (HTTP), or equal to 53 (DNS), or in the range 6881-6889 (BitTorrent).

So including BitTorrent here makes sense in a world where there are tons =

of BitTorrent nodes that are publically accessible on the outside of =

your "address-port sparing NAT" that can be contacted.  However, =

mandating address-dependent mapping is absolutely the wrong solution if =

you are trying to allow these apps to continue to work as such NATs =

become more common.  You need to mandate independent mapping and support =

of TCP-SO for these to work.  Otherwise you come up with a temporary =

workaround that solves this particular problem only as long as this =

deployment is is rare, and then breaks the world as more of these =

appear, resulting in no one using 6881-6889 for p2p anything anymore.

Or is the proposal that enough current apps use those ports that making =

them endpoint-dependent solves the short-term problem and long-term the =

apps will migrate to using other ports and doing it in a NAT-friendly =

manner?

> =

> 2. A NAT  MUST do  mappings that are endpoint-independent if initiated
> with external-host ports in the 1990-1992 range (STUN) or equal to 3544
> (Teredo).

Where do these port numbers come from?  STUN is 3478 =

(http://tools.ietf.org/html/draft-ietf-behave-rfc3489bis-15#section-18.4), =

furthermore, my understanding is that the default port is essentially =

deprecated in favor of using SRV.

I guess this makes sense in a provider-based world where everyone relies =

on the STUN server provisioned for them, but in particular with a p2p =

world, a STUN server can run on any port. You can't identify an =

application that needs independent mapping based on its outbound port =

number.

You MIGHT be able to modify this rule to specify that endpoint =

independent mapping MUST be used for connections that begin with STUN =

requests, but I don't think this works for TCP connections since you =

have to assign the mapping before you see the data.


> =

> 3. NATs MAY also do mappings that are endpoint-independent if initiated
> with external-host ports known to be those of applications compatible
> with it (POP3, SMTP, IMAP, NNTP, Telnet, SNMP, IPsec over UDP...).
> =


Shouldn't this rule be MAY use mappings that are *endpoint-dependent* if =

initiated with (insert list of applications that will be fought about here)?


> RFC4787 says: "REQ-1:  A NAT MUST have an "Endpoint-Independent Mapping" =

> behavior." but, formally, rule 2 above also says that NATs MUST have =

> such a behavior. The new point is that it doesn't have it for ALL =

> transports connections (with the effect that address-port couples are =

> used sparingly).

I think it might be possible to specify some small set of destination =

ports for which dependent mapping is not harmful.  And realistically, =

this will eliminate tons of wasted ports.  But anything that breaks =

endpoint-independent mapping for other ports is just going to break tons =

of applications.

If the other major cause of port exhaustion is BitTorrent-type apps that =

open tons of connections, the right long-term solution is to make it =

easier to write apps that work using NAT-friendly techniques.  There are =

a bunch of short-term solutions for the existing apps.

Bruce
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu May 22 09:25:39 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B73013A6B23;
	Thu, 22 May 2008 09:25:39 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 889A73A68FF
	for <behave@core3.amsl.com>; Thu, 22 May 2008 09:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, 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 9as1R2DE5ZB4 for <behave@core3.amsl.com>;
	Thu, 22 May 2008 09:25:11 -0700 (PDT)
Received: from mail.sipeerior.com (mail.sipeerior.com [128.239.5.131])
	by core3.amsl.com (Postfix) with ESMTP id 036733A68B2
	for <behave@ietf.org>; Thu, 22 May 2008 09:25:11 -0700 (PDT)
Received: from vuelta.local (unknown [128.239.5.171])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.sipeerior.com (Postfix) with ESMTP id DEB3B505AA5;
	Thu, 22 May 2008 12:25:10 -0400 (EDT)
Message-ID: <48359E62.6050401@sipeerior.com>
Date: Thu, 22 May 2008 12:25:06 -0400
From: Bruce Lowekamp <lowekamp@sipeerior.com>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>	<DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
	<4835984F.6080504@free.fr>
In-Reply-To: <4835984F.6080504@free.fr>
Cc: behave@ietf.org, ext Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

R=E9mi Despr=E9s wrote:
> Lars Eggert wrote :
> =

>>> Several other people have proposed using port numbers to decide if
>>> UNSAF was being used, under the assmption that TCP/80, TCP/110
>>> (POP3), etc., don't use UNSAF.  That is certainly another direction
>>> to pursue.  My concern with that mechanism is that it would create
>>> the first instance where a NAT's behavior is radically different
>>> based on the port number.
>> Right. IMO that proposal goes counter to the idea behind BEHAVE, which  =

>> is to make NATs more regularized. Having the NAPT act differently  =

>> based on what port numbers are used actually makes their behavior more  =

>> diverse instead of more regularized.
> =

> IMU, using a new method to solve a problem that has not been solved yet =

> is not per se a problem.
> =

> Also, isn't it true that all ALGs that identify applications based on =

> port numbers, and act specifically based on that, have already =

> introduced NAT behaviors that depend on port numbers?
> =

> Finally, trying to identify applications based on timings of established =

> connections seems to me unnecessarily complex and unreliable, especially =

> to solve a problem that is trivial if ports are used.
> =

> For more details on how port-based application identification can =

> contribute to "regularize" NATs, at least those that have to  use =

> addresses and ports sparingly:
> http://www.ietf.org/mail-archive/web/behave/current/msg03880.html
> =


A P2P application would almost certainly have the characteristics =

required by Dan's algorithms.  Whereas it would almost certainly not =

have the port numbers the other proposal is looking for.

I could see a hybrid where a NAT can assume that connections to http, =

smtp, ssh are assumed to be compatible with endpoint-dependent mapping, =

but relying on a technique that assumes it can identify an application =

that requires independent mapping with a set of port numbers is doomed =

to failure.  It just can't work when other peers are behind there own =

nats, or in the presence of double natting.

Bruce
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu May 22 09:57:09 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 017653A68D6;
	Thu, 22 May 2008 09:57:09 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1E2893A67C1
	for <behave@core3.amsl.com>; Thu, 22 May 2008 09:56:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.579
X-Spam-Level: 
X-Spam-Status: No, score=-1.579 tagged_above=-999 required=5 tests=[AWL=0.370, 
	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 B8XSYh-ULsqO for <behave@core3.amsl.com>;
	Thu, 22 May 2008 09:56:46 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id 81FAD3A677C
	for <behave@ietf.org>; Thu, 22 May 2008 09:56:46 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id C0B8B3EA2B4;
	Thu, 22 May 2008 18:56:45 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 311603EA0E8;
	Thu, 22 May 2008 18:56:45 +0200 (CEST)
Message-ID: <4835A5D6.3040403@free.fr>
Date: Thu, 22 May 2008 18:56:54 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Bruce Lowekamp <lowekamp@sipeerior.com>
References: <483526BD.1090308@free.fr> <483599C0.4030009@sipeerior.com>
In-Reply-To: <483599C0.4030009@sipeerior.com>
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Address-port sparing NATs - a proposal
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Bruce Lowekamp wrote :
> This looks like it's going to break p2p apps if it's deployed.
> =

> R=E9mi Despr=E9s wrote:
>> PROPOSAL:
>> 1. A NAT, to be an *address-port sparing NAT*,  MUST do mappings that
>> are endpoint-dependent if initiated with external-host ports equal to 80
>> (HTTP), or equal to 53 (DNS), or in the range 6881-6889 (BitTorrent).
This is the essential part of the proposal.

> So including BitTorrent here makes sense in a world where there are tons =

> of BitTorrent nodes that are publically accessible on the outside of =

> your "address-port sparing NAT" that can be contacted.  However, =

> mandating address-dependent mapping is absolutely the wrong solution if =

> you are trying to allow these apps to continue to work as such NATs =

> become more common.  You need to mandate independent mapping and support =

> of TCP-SO for these to work.

Can yo be more explicit, or point to a reference?
(My knowledge of the problem you refer to - simultaneous opens with =

BitTorrent - is insufficient.)

>> 2. A NAT  MUST do  mappings that are endpoint-independent if initiated
>> with external-host ports in the 1990-1992 range (STUN) or equal to 3544
>> (Teredo).
> =

> Where do these port numbers come from?
In http://www.iana.org/assignments/port-numbers stun-p1 to stun-p2

> STUN is 3478 =

> (http://tools.ietf.org/html/draft-ietf-behave-rfc3489bis-15#section-18.4)=
, =

Right.
Thanks.


> furthermore, my understanding is that the default port is essentially =

> deprecated in favor of using SRV.
This seems indeed to be the case the case, for a reason I ignore.
It certainly does weaken the importance of this MUST.

> =

> I guess this makes sense in a provider-based world where everyone relies =

> on the STUN server provisioned for them, but in particular with a p2p =

> world, a STUN server can run on any port. You can't identify an =

> application that needs independent mapping based on its outbound port =

> number.
> =

> You MIGHT be able to modify this rule to specify that endpoint =

> independent mapping MUST be used for connections that begin with STUN =

> requests, but I don't think this works for TCP connections since you =

> have to assign the mapping before you see the data.
This point is unclear to me.
IMU, the mapping that is done for STUN is the one used for connections =

that justified using STUN.

> =

>>
>> 3. NATs MAY also do mappings that are endpoint-independent if initiated
>> with external-host ports known to be those of applications compatible
>> with it (POP3, SMTP, IMAP, NNTP, Telnet, SNMP, IPsec over UDP...).
>>
> =

> Shouldn't this rule be MAY use mappings that are *endpoint-dependent* if =

> initiated with (insert list of applications that will be fought about =

> here)?
YES
(Sorry for the typo.)


> =

>> RFC4787 says: "REQ-1:  A NAT MUST have an "Endpoint-Independent =

>> Mapping" behavior." but, formally, rule 2 above also says that NATs =

>> MUST have such a behavior. The new point is that it doesn't have it =

>> for ALL transports connections (with the effect that address-port =

>> couples are used sparingly).
> =

> I think it might be possible to specify some small set of destination =

> ports for which dependent mapping is not harmful.  And realistically, =

> this will eliminate tons of wasted ports.  But anything that breaks =

> endpoint-independent mapping for other ports is just going to break tons =

> of applications.
Following the discussion, I agree.
(But the question of whether BitTorrent ports need to be excluded from =

this list because of simultaneous TCP opens remains open for me with my =

current level of understanding.)

R=E9mi
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu May 22 11:14:06 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1DA1D3A6879;
	Thu, 22 May 2008 11:14:06 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 008D03A6940
	for <behave@core3.amsl.com>; Thu, 22 May 2008 11:13:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 wnFLTAc4DcjH for <behave@core3.amsl.com>;
	Thu, 22 May 2008 11:13:20 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 85CA63A68D0
	for <behave@ietf.org>; Thu, 22 May 2008 11:13:20 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,525,1204520400"; 
   d="scan'208";a="9056665"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 22 May 2008 14:13:19 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4MIDJ4Y031292; 
	Thu, 22 May 2008 14:13:19 -0400
Received: from dwingwxp01 (rtp-vpn6-344.cisco.com [10.82.249.89])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m4MIDHZU006822;
	Thu, 22 May 2008 18:13:18 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Lars Eggert'" <lars.eggert@nokia.com>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>
	<2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>
	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>
	<DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
Date: Thu, 22 May 2008 08:13:17 -1000
Message-ID: <09c701c8bc37$83bb4310$1496150a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Aci8HGIK7GZTURl2QfyIlPKXQRhsHgAGpmiw
In-Reply-To: <DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4208; t=1211479999;
	x=1212343999; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Dynamic=20Port=20Reuse
	|Sender:=20
	|To:=20=22'Lars=20Eggert'=22=20<lars.eggert@nokia.com>;
	bh=ARojq+Jx4yji5HRFJJIzZ4hpeYgBNpel+dS+oxlKoWo=;
	b=WLoLK3TaPuqyxJ7FtDQXeAkadLZVwI+aRXzM0YCEtYmGG27R6CiXBboLlw
	0GubGngfw4OVYxpXUBC0B2AHcO9/q9E6gubBweMGqPRJ2RqYZZF1pYr6q9Zr
	50zzB8k+Cu;
Authentication-Results: rtp-dkim-1; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

 

> -----Original Message-----
> From: Lars Eggert [mailto:lars.eggert@nokia.com] 
> Sent: Thursday, May 22, 2008 4:59 AM
> To: ext Dan Wing
> Cc: behave@ietf.org
> Subject: Re: [BEHAVE] Dynamic Port Reuse
> 
> Hi,
> 
> On 2008-5-21, at 21:09, ext Dan Wing wrote:
> >> (1) Meta-comment: Why wouldn't large NAPT boxes simply use multiple
> >> public IP addresses to avoid running out of ports?
> >
> > Sure, but that, too, has complications.  One that Greg Lebovitz
> > mentioned at two different BEHAVE working group meetings is that
> > some HTTP servers, or their back-end software, was sensitive to
> > multiple connections from the same client arriving from different
> > IP addresses; it was suggested that the HTTP server's cookies
> > were tied to the client's IP address.
> 
> OK, so to work around that bug, you'd need to map NAT clients to  
> public addresses persistently, and you'd loose some multiplexing  
> efficiency.
> 
> > And the primary motivation for me to write this up was v4 address
> > conservation on the NAT64 box.
> 
> Understood, but are we really _that_ stressed for v4 space yet?
> 
> >> ALGO-1 can only reuse source
> >> ports for connections to different services (on different
> >> destination
> >> ports), which is what Figure 1 shows.
> >
> > ALGO-1 can use the same source TCP port if the two TCP
> > connections are going to two servers (e.g., www.cnn.com/80,
> > www.ietf.org/80).
> 
> Sure, but that's equivalent to the above in that the 5-tuple 
> is unique.
> 
> I think I misunderstood the "ALGO-1 should work very well for client/ 
> server applications" part. ALGO-2 would actually better for (non- 
> UNSAF) client/server apps, in the sense that it allows more  
> multiplexing.
> 
> >> (3) The changes to applications that ALGO-2 requires are more
> >> invasive
> >> than just signaling that UNSAF is being used, because
> >> applications may
> >> also need to change their transmission behavior to conform to the
> >> "hold time" the NAPT now uses. It's IMO problematic to assume any
> >> application or transport protocol changes will happen.
> >
> > Everthing is a tradeoff.  Would extending the proposed timer from
> > 30 seconds to 60 or 90 or 120 seconds reduce your concern?
> 
> No, because irrespective of what the hold time is, defining one is  
> what can potentially be a problem, because the NAPT now assumes that  
> if an app hasn't done X in time Y, it will never do so.
> 
> But given that NAPTs aren't behaving very consistently anyway, maybe  
> the hold time won't matter. Someone should run some experiments :-)

The proposal is primarily for NAT64, so these would be new devices
that could -- if we specify the requirements adequately -- operate
with more consistency than today's NATs.

> > Several other people have proposed using port numbers to decide if
> > UNSAF was being used, under the assmption that TCP/80, TCP/110
> > (POP3), etc., don't use UNSAF.  That is certainly another direction
> > to pursue.  My concern with that mechanism is that it would create
> > the first instance where a NAT's behavior is radically different
> > based on the port number.
> 
> Right. IMO that proposal goes counter to the idea behind 
> BEHAVE, which  
> is to make NATs more regularized. Having the NAPT act differently  
> based on what port numbers are used actually makes their 
> behavior more  
> diverse instead of more regularized.
> 
> The key question is how a NAPT can accurately differentiate 
> apps that  
> use UNSAF from ones that don't, because that's the 
> characteristic that  
> can be used to drive more efficient connection multiplexing. You  
> propose doing this based on the observable transmission behavior,  
> Iljitsch/Remi have suggested doing it based on destination 
> ports. Both  
> have pros and cons. Do other options exist?

Those are the two proposals that I have seen.  I believe they
could reasonably be combined.  For example, from my perspective
with timers, I consider Iljitsch/Remi's proposal as using a 0-second 
timer for certain ports (e.g., TCP/80) and an infinite timer for other
ports.

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu May 22 11:21:45 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC8A63A6B0C;
	Thu, 22 May 2008 11:21:45 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AE88A3A6B0C
	for <behave@core3.amsl.com>; Thu, 22 May 2008 11:20:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5
	tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
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 DMRqELkk+S52 for <behave@core3.amsl.com>;
	Thu, 22 May 2008 11:20:49 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 688FC28C137
	for <behave@ietf.org>; Thu, 22 May 2008 11:20:49 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,525,1204520400"; 
   d="scan'208";a="9047974"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 22 May 2008 14:20:48 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m4MIKmkP012155; 
	Thu, 22 May 2008 14:20:48 -0400
Received: from dwingwxp01 (rtp-vpn6-344.cisco.com [10.82.249.89])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4MIKki6021277;
	Thu, 22 May 2008 18:20:47 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "=?iso-8859-1?Q?'R=E9mi_Despr=E9s'?=" <remi.despres@free.fr>,
	"'Lars Eggert'" <lars.eggert@nokia.com>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com><DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
	<4835984F.6080504@free.fr>
Date: Thu, 22 May 2008 08:20:46 -1000
Message-ID: <0a0a01c8bc38$8f5daa90$1496150a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Aci8JMpd8r1yY6xZS5u78Frqn42wBQAEthdg
In-Reply-To: <4835984F.6080504@free.fr>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2784; t=1211480448;
	x=1212344448; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Dynamic=20Port=20Reuse
	|Sender:=20
	|To:=20=22=3D?iso-8859-1?Q?'R=3DE9mi_Despr=3DE9s'?=3D=22=20
	<remi.despres@free.fr>,=0A=20=20=20=20=20=20=20=20=22'Lars=2
	0Eggert'=22=20<lars.eggert@nokia.com>;
	bh=Ot/lUnCBc81RtDD2tXYxBG/TIt7XFGVhV5tvXPmzWzg=;
	b=GJAJ0+TIQkkNeAj1i4VZUvg7Q7qQ4UUndJAXhadoGB1TJj4c8u80u1E9VQ
	HSgHJutkJTuLL7MvEPhM7usNYgel4FzrpD5DpJ6Kos1t7dAlKrPYG+u/cZxg
	RWQiHqXmA9;
Authentication-Results: rtp-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

 =


> -----Original Message-----
> From: behave-bounces@ietf.org =

> [mailto:behave-bounces@ietf.org] On Behalf Of R=E9mi Despr=E9s
> Sent: Thursday, May 22, 2008 5:59 AM
> To: Lars Eggert
> Cc: behave@ietf.org; ext Dan Wing
> Subject: Re: [BEHAVE] Dynamic Port Reuse
> =

> Lars Eggert wrote :
> =

> >> Several other people have proposed using port numbers to decide if
> >> UNSAF was being used, under the assmption that TCP/80, TCP/110
> >> (POP3), etc., don't use UNSAF.  That is certainly another direction
> >> to pursue.  My concern with that mechanism is that it would create
> >> the first instance where a NAT's behavior is radically different
> >> based on the port number.
> > =

> > Right. IMO that proposal goes counter to the idea behind =

> BEHAVE, which  =

> > is to make NATs more regularized. Having the NAPT act differently  =

> > based on what port numbers are used actually makes their =

> behavior more  =

> > diverse instead of more regularized.
> =

> IMU, using a new method to solve a problem that has not been =

> solved yet =

> is not per se a problem.
> =

> Also, isn't it true that all ALGs that identify applications based on =

> port numbers, and act specifically based on that, have already =

> introduced NAT behaviors that depend on port numbers?

The distinction is that IETF did not standardize ALGs -- even
though every vendor ships one (FTP-aware ALGs most especially).  I
believe the only references to ALGs are in informational documents.
I expect if I'm wrong, someone will be quick to reply.  :-)

> Finally, trying to identify applications based on timings of =

> established =

> connections seems to me unnecessarily complex and unreliable, =


Running a timer isn't too complex, and the NAPT knows about
new mappings that it needs to create when a new flow starts.

As to unreliable ...  Yes, it could be unreliable, but only
for those applications using UNSAF.  For client/server applications =

(e.g., HTTP), it is as reliable as using port numbers to decide the
NAPT's behavior.

> especially =

> to solve a problem that is trivial if ports are used.

I do agree that using ports is easier.  But I don't see how we
would create a list of such ports, or how an application would
know which ports have port-reuse and which ports have no-port-reuse.

-d


> For more details on how port-based application identification can =

> contribute to "regularize" NATs, at least those that have to  use =

> addresses and ports sparingly:
> http://www.ietf.org/mail-archive/web/behave/current/msg03880.html
> =

> R=E9mi
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu May 22 23:56:34 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 68B513A6C63;
	Thu, 22 May 2008 23:56:34 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6CA193A6C61
	for <behave@core3.amsl.com>; Thu, 22 May 2008 23:56:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5
	tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_24=0.6,
	MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 OHHzqqPdFobe for <behave@core3.amsl.com>;
	Thu, 22 May 2008 23:56:32 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 9297B3A6C60
	for <behave@ietf.org>; Thu, 22 May 2008 23:56:32 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m4N6ta84030367; Fri, 23 May 2008 01:56:25 -0500
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 23 May 2008 09:55:37 +0300
Received: from esdhcp04180.research.nokia.com ([172.21.41.80]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 23 May 2008 09:55:37 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: behave@ietf.org
Date: Fri, 23 May 2008 09:55:37 +0300
User-Agent: KMail/1.9.9
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>
In-Reply-To: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805230955.37501.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 23 May 2008 06:55:37.0644 (UTC)
	FILETIME=[01877EC0:01C8BCA2]
X-Nokia-AV: Clean
Cc: ext Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Le Wednesday 14 May 2008 20:15:13 ext Dan Wing, vous avez =E9crit=A0:
> My strawman proposal is at:
> http://tools.ietf.org/html/draft-wing-behave-dynamic-tcp-port-reuse-00
>
> Abstract:
>   A strawman proposal is made to reduce public-facing TCP port use with
>   large Network Address and Port Translators (NAPTs).  This proposal
>   attempts to preserve emergent NAT traversal techniques.  It is
>   anticipated that large NAPTs will be used for NAT64.

ALGO-1 as it stands might break TCP. A NAT must not reuse the same port num=
ber =

for a different internal IP:port typle, toward the same remote IP:port tupl=
e.

In any case, ALGO-1 breaks TCP-SO. I think the real issue is, whether =

TCP-SO/IPv4 really matters.... It would seem so unreliable that people will =

end up using UDP.

-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 00:37:37 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 55AA13A69AA;
	Fri, 23 May 2008 00:37:37 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A369C3A69AA
	for <behave@core3.amsl.com>; Fri, 23 May 2008 00:37:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.293
X-Spam-Level: 
X-Spam-Status: No, score=-6.293 tagged_above=-999 required=5 tests=[AWL=0.006, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 OvR4SlnwWiyv for <behave@core3.amsl.com>;
	Fri, 23 May 2008 00:37:36 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id E1C373A67A7
	for <behave@ietf.org>; Fri, 23 May 2008 00:37:35 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m4N7arex006813; Fri, 23 May 2008 02:37:26 -0500
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 23 May 2008 10:37:16 +0300
Received: from [192.168.255.2] ([10.241.184.208]) by esebh102.NOE.Nokia.com
	over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 23 May 2008 10:37:15 +0300
Message-Id: <F5356B94-213A-486F-9A93-7BDBB0D0BC51@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: =?ISO-8859-1?Q?ext_R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <4835984F.6080504@free.fr>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Fri, 23 May 2008 10:37:10 +0300
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>
	<DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
	<4835984F.6080504@free.fr>
X-Mailer: Apple Mail (2.919.2)
X-OriginalArrivalTime: 23 May 2008 07:37:15.0737 (UTC)
	FILETIME=[D2823C90:01C8BCA7]
X-Nokia-AV: Clean
Cc: behave@ietf.org, ext Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi,

On 2008-5-22, at 18:59, ext R=E9mi Despr=E9s wrote:
> Also, isn't it true that all ALGs that identify applications based  =

> on port numbers, and act specifically based on that, have already  =

> introduced NAT behaviors that depend on port numbers?

ALGs can't (only) depend on port numbers, because they also need to  =

parse the application protocol to do their job. So if I run telnet on  =

port 21 through a NAT, hopefully the FTP ALG implementor was smart  =

enough to not only look at the port number.

(It'd be interesting to know if the "better" NATs allow an  =

administrator to configure ALGs to monitor non-standard ports, too.)

> Finally, trying to identify applications based on timings of  =

> established connections seems to me unnecessarily complex and  =

> unreliable, especially to solve a problem that is trivial if ports  =

> are used.

Both current proposals have advantages and disadvantages, and the  =

tradeoffs need to be understood. I'm not a particular fan of using  =

either ports or timers - both are crufty - because I'm still  =

unconvinced that we actually need to solve this problem in the first  =

place. Anyone got data about how often NATs run out of binding entries  =

in situations where another IPv4 address isn't available?

Lars
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 01:17:47 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2F63E3A6BB0;
	Fri, 23 May 2008 01:17:47 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0FCB03A6996
	for <behave@core3.amsl.com>; Fri, 23 May 2008 01:17:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.641
X-Spam-Level: 
X-Spam-Status: No, score=-1.641 tagged_above=-999 required=5 tests=[AWL=0.308, 
	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 yPM7EzWY+udO for <behave@core3.amsl.com>;
	Fri, 23 May 2008 01:17:45 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id 586C93A6BB0
	for <behave@ietf.org>; Fri, 23 May 2008 01:17:45 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 3B4773EA0A7;
	Fri, 23 May 2008 10:17:44 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 09BD33EA0C1;
	Fri, 23 May 2008 10:17:43 +0200 (CEST)
Message-ID: <48367DB0.5010902@free.fr>
Date: Fri, 23 May 2008 10:17:52 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?=
 <remi.denis-courmont@nokia.com>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>
	<200805230955.37501.remi.denis-courmont@nokia.com>
In-Reply-To: <200805230955.37501.remi.denis-courmont@nokia.com>
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

R=E9mi Denis-Courmont  - Le 5/23/08 8:55 AM :

> In any case, ALGO-1 breaks TCP-SO. I think the real issue is, whether =

> TCP-SO/IPv4 really matters.... It would seem so unreliable that people wi=
ll =

> end up using UDP.
Is there a reference where the the nature and the scope of the alleged =

TCP-SO problem is identified?

RD



_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 01:33:30 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7335E3A6BBD;
	Fri, 23 May 2008 01:33:30 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A30E73A6BB0
	for <behave@core3.amsl.com>; Fri, 23 May 2008 01:33:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.149
X-Spam-Level: 
X-Spam-Status: No, score=-6.149 tagged_above=-999 required=5 tests=[AWL=0.150, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 aHFC6L7I7KDr for <behave@core3.amsl.com>;
	Fri, 23 May 2008 01:33:28 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id 922F63A6B95
	for <behave@ietf.org>; Fri, 23 May 2008 01:33:27 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m4N8XOrJ026735 for <behave@ietf.org>; Fri, 23 May 2008 11:33:24 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 23 May 2008 11:33:12 +0300
Received: from esdhcp04180.research.nokia.com ([172.21.41.80]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 23 May 2008 11:33:11 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: behave@ietf.org
Date: Fri, 23 May 2008 11:33:11 +0300
User-Agent: KMail/1.9.9
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>
	<200805230955.37501.remi.denis-courmont@nokia.com>
	<48367DB0.5010902@free.fr>
In-Reply-To: <48367DB0.5010902@free.fr>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805231133.11899.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 23 May 2008 08:33:11.0913 (UTC)
	FILETIME=[A2F20D90:01C8BCAF]
X-Nokia-AV: Clean
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Le Friday 23 May 2008 11:17:52 ext R=E9mi Despr=E9s, vous avez =E9crit=A0:
> R=E9mi Denis-Courmont  - Le 5/23/08 8:55 AM :
> > In any case, ALGO-1 breaks TCP-SO. I think the real issue is, whether
> > TCP-SO/IPv4 really matters.... It would seem so unreliable that people
> > will end up using UDP.
>
> Is there a reference where the the nature and the scope of the alleged
> TCP-SO problem is identified?

That would be the IETF70 and 71 proceedings of MMUSIC and BEHAVE.

-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 01:59:55 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4DF2F3A6C67;
	Fri, 23 May 2008 01:59:55 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0F5C23A6A79
	for <behave@core3.amsl.com>; Fri, 23 May 2008 01:59:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.685
X-Spam-Level: 
X-Spam-Status: No, score=-1.685 tagged_above=-999 required=5 tests=[AWL=0.264, 
	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 ZP0wEYJj0hfP for <behave@core3.amsl.com>;
	Fri, 23 May 2008 01:59:48 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id 51E7328C27B
	for <behave@ietf.org>; Fri, 23 May 2008 01:59:17 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id A7A6D3EA0F4;
	Fri, 23 May 2008 10:59:16 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 5A4C23EA0BD;
	Fri, 23 May 2008 10:59:16 +0200 (CEST)
Message-ID: <4836876D.4080907@free.fr>
Date: Fri, 23 May 2008 10:59:25 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Lars Eggert <lars.eggert@nokia.com>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>
	<DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
	<4835984F.6080504@free.fr>
	<F5356B94-213A-486F-9A93-7BDBB0D0BC51@nokia.com>
In-Reply-To: <F5356B94-213A-486F-9A93-7BDBB0D0BC51@nokia.com>
Cc: behave@ietf.org, ext Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Lars Eggert  - Le 5/23/08 9:37 AM :
  > On 2008-5-22, at 18:59, ext R=E9mi Despr=E9s wrote:
>> Also, isn't it true that all ALGs that identify applications based
>> on port numbers, and act specifically based on that, have already =

>> introduced NAT behaviors that depend on port numbers?
> =

> ALGs can't (only) depend on port numbers, because they also need to =

> parse the application protocol to do their job. So if I run telnet on
>  port 21 through a NAT, hopefully the FTP ALG implementor was smart =

> enough to not only look at the port number.
Although some ALGs may be activated depending on some data parsing, some =

(e.g. FTP) do depend IMU on port numbers to be activated.

This is enough IMO to consider that a different NAT behavior based on =

ports would not be new (which was the point under discussion).

Running Telnet on the port of FTP seems strange to me, and IMO should =

not justify to make NATs any more complex.


> (It'd be interesting to know if the "better" NATs allow an
> administrator to configure ALGs to monitor non-standard ports, too.)
> =

>> Finally, trying to identify applications based on timings of =

>> established connections seems to me unnecessarily complex and =

>> unreliable, especially to solve a problem that is trivial if ports
>> are used.
> =

> Both current proposals have advantages and disadvantages, and the =

> tradeoffs need to be understood. I'm not a particular fan of using =

> either ports or timers - both are crufty -
IMO, simplicity and reliability are the strong points in favor of ports =

vs timings.
So far, there is IMU no strong point in favor of timings.


> I'm still unconvinced that we actually need to solve this problem in
> the first place. Anyone got data about how often NATs run out of
> binding entries in situations where another IPv4 address isn't
> available?
The point is that more and more NATs are within ISP infrastructures. =

They are shared by potentially very large numbers of users, and may ahve =

to support huge numbers of UDP-TCP connections.

These NATs may in the future, in particular for the v4-v6 coexistence =

period, be replaced by  more scalable functions like those based on an =

address-port borrowing protocol (APBP). But the need to use sparingly =

address-port couples can only be mitigated, not suppressed.

If nothing else, susceptibility of these NATs, or APBP servers, to DOS =

attacks will strongly depend on their margin between available =

address-port couples and those that are normally used.

R=E9mi
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 02:53:10 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 723383A6C67;
	Fri, 23 May 2008 02:53:10 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9FB0F3A6C74
	for <behave@core3.amsl.com>; Fri, 23 May 2008 02:53:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.099
X-Spam-Level: 
X-Spam-Status: No, score=-6.099 tagged_above=-999 required=5
	tests=[AWL=-0.150, BAYES_00=-2.599, HELO_EQ_FR=0.35,
	MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 9h0mRH8OkUnl for <behave@core3.amsl.com>;
	Fri, 23 May 2008 02:53:08 -0700 (PDT)
Received: from mx2.nic.fr (mx2.nic.fr [192.134.4.11])
	by core3.amsl.com (Postfix) with ESMTP id CC5E13A6B95
	for <behave@ietf.org>; Fri, 23 May 2008 02:53:07 -0700 (PDT)
Received: from mx2.nic.fr (localhost [127.0.0.1])
	by mx2.nic.fr (Postfix) with SMTP id 430E41C014C;
	Fri, 23 May 2008 11:53:07 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163])
	by mx2.nic.fr (Postfix) with ESMTP id 3E0A81C0117;
	Fri, 23 May 2008 11:53:07 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.4.69])
	by relay2.nic.fr (Postfix) with ESMTP id 3238A58EBEA;
	Fri, 23 May 2008 11:53:07 +0200 (CEST)
Date: Fri, 23 May 2008 11:53:07 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Message-ID: <20080523095307.GA5142@nic.fr>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>
	<2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>
	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>
	<DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
	<4835984F.6080504@free.fr>
	<F5356B94-213A-486F-9A93-7BDBB0D0BC51@nokia.com>
	<4836876D.4080907@free.fr>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <4836876D.4080907@free.fr>
X-Operating-System: Debian GNU/Linux lenny/sid
X-Kernel: Linux 2.6.24-1-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.17+20080114 (2008-01-14)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Fri, May 23, 2008 at 10:59:25AM +0200,
 R=E9mi Despr=E9s <remi.despres@free.fr> wrote =

 a message of 58 lines which said:

> Running Telnet on the port of FTP seems strange to me, =


A more realistic example would be running SSH over port 443
(https). This is very common practice because many "Internet"
providers (for instance, in France, Orange/3GPP) allow access only to
a few ports such as 80 and 443.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 02:57:09 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5E58E3A6C68;
	Fri, 23 May 2008 02:57:09 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2FA6F3A6C68
	for <behave@core3.amsl.com>; Fri, 23 May 2008 02:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.718
X-Spam-Level: 
X-Spam-Status: No, score=-1.718 tagged_above=-999 required=5 tests=[AWL=0.231, 
	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 a3ouduijOdaY for <behave@core3.amsl.com>;
	Fri, 23 May 2008 02:57:07 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id 66EAE3A6851
	for <behave@ietf.org>; Fri, 23 May 2008 02:57:07 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id C4C153EA0C8;
	Fri, 23 May 2008 11:57:06 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 75BE83EA0BC;
	Fri, 23 May 2008 11:57:06 +0200 (CEST)
Message-ID: <483694FB.2060700@free.fr>
Date: Fri, 23 May 2008 11:57:15 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?=
 <remi.denis-courmont@nokia.com>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<200805230955.37501.remi.denis-courmont@nokia.com>	<48367DB0.5010902@free.fr>
	<200805231133.11899.remi.denis-courmont@nokia.com>
In-Reply-To: <200805231133.11899.remi.denis-courmont@nokia.com>
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

R=E9mi Denis-Courmont  - Le 5/23/08 10:33 AM :
>> Is there a reference where the the nature and the scope of the alleged
>> TCP-SO problem is identified?
> =

> That would be the IETF70 and 71 proceedings of MMUSIC and BEHAVE.
Thanks.

It clarifies IMU that the scope of the identified TCP-SO problem is that =

of applications that use ICE to traverse NATs.

These apllications are not subject to endpoint-dependent mapping with my =

proposal, now summarized as:
"endpoint-dependent mapping authorized iff the destination port of the =

packet that initiates the mapping is that of an application that =

supports it, i.e. FTP, DNS..."

Whether BitTorrent ports can be in the list is IMU still debated.

(The assumption is made that STUN connections of ICE are not done on =

ports of the FTP, DNS... list. But doing it would IMU be a very bad idea.)

RD



_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 03:22:34 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E2C7C3A6C71;
	Fri, 23 May 2008 03:22:34 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 97B5A3A6C7A
	for <behave@core3.amsl.com>; Fri, 23 May 2008 03:22:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.743
X-Spam-Level: 
X-Spam-Status: No, score=-1.743 tagged_above=-999 required=5 tests=[AWL=0.206, 
	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 ZL2rG6mID+14 for <behave@core3.amsl.com>;
	Fri, 23 May 2008 03:22:31 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id 86A573A6BB0
	for <behave@ietf.org>; Fri, 23 May 2008 03:22:31 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id BBA413EA104;
	Fri, 23 May 2008 12:22:30 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 871153EA0DF;
	Fri, 23 May 2008 12:22:30 +0200 (CEST)
Message-ID: <48369AEF.3000107@free.fr>
Date: Fri, 23 May 2008 12:22:39 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>
	<2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>
	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>
	<DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
	<4835984F.6080504@free.fr>
	<F5356B94-213A-486F-9A93-7BDBB0D0BC51@nokia.com>
	<4836876D.4080907@free.fr> <20080523095307.GA5142@nic.fr>
In-Reply-To: <20080523095307.GA5142@nic.fr>
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Stephane Bortzmeyer  - Le 5/23/08 11:53 AM :
> On Fri, May 23, 2008 at 10:59:25AM +0200,
>  R=E9mi Despr=E9s <remi.despres@free.fr> wrote =

>  a message of 58 lines which said:
> =

>> Running Telnet on the port of FTP seems strange to me, =

> =

> A more realistic example would be running SSH over port 443
> (https). This is very common practice because many "Internet"
> providers (for instance, in France, Orange/3GPP) allow access only to
> a few ports such as 80 and 443.
Thanks for the info.
SSH on HTTPS should not be problematic because IMU neither one needs an ALG.

A difficult case would be one where the port of an application that =

needs an ALG is used for an application that doesn't.

R=E9mi
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 03:57:09 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DA8A63A6C7B;
	Fri, 23 May 2008 03:57:09 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B9D113A6C7B
	for <behave@core3.amsl.com>; Fri, 23 May 2008 03:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.762
X-Spam-Level: 
X-Spam-Status: No, score=-3.762 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_BAD_ID=2.837, RCVD_IN_DNSWL_MED=-4]
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 Mf4jnHmR9ghT for <behave@core3.amsl.com>;
	Fri, 23 May 2008 03:57:07 -0700 (PDT)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131])
	by core3.amsl.com (Postfix) with ESMTP id 7CFBB3A69D4
	for <behave@ietf.org>; Fri, 23 May 2008 03:57:07 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (unknown 
	[163.117.203.43])by smtp01.uc3m.es (Postfix) with ESMTP id C550C635039;
	Fri, 23 May 2008 12:57:02 +0200 (CEST)
Message-ID: <48369C77.4000703@it.uc3m.es>
Date: Fri, 23 May 2008 12:29:11 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@cisco.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d
	74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11
	4	41.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es><48286CFD.
	10	80204@free.fr>	<48287AE5.5010005@sipeerior.com><482882B7.2030806@free.fr
	><1	45B7DFA-E397-4184-8FA6-3C255078509F@muada.com><48289C15.3000102@free.fr
	>	<4	828A33E.1080700@sipeerior.com><4828ABBE.9010201@free.fr>	<4828AE1B.904
	0901@	sipeerior.com>	<03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>	<0158
	01c8b5	0d$984b8eb0$c3f0200a@cisco.com>	<8EFD78D3-46EC-4BA5-9F9A-B6F471B9C01
	F@gmail	.com>	<018601c8b511$0a83a410$c3f0200a@cisco.com>	<2F594053-210D-49D
	6-A9C7-5	245826854A1@gmail.com>	<04fe01c8b531$5c086c60$c3f0200a@cisco.com><
	563A472D-30B9-45E9-8E2C-009CF1B4045F@magma.ca>
	<4834E78D.6000007@cisco.com>
In-Reply-To: <4834E78D.6000007@cisco.com>
X-imss-version: 2.050
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-24.4015 TC:1F TRN:47 TV:5.5.1026(15926.006)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: Behave WG <behave@ietf.org>, Philip Matthews <philip_matthews@magma.ca>,
	Iljitsch van Beijnum <iljitsch@gmail.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi,


Jonathan Rosenberg escribi=F3:
>    Please view in a fixed-width font such as
>                     Courier.
>
>
>
>
>
>
>
>
>
>
>                                               E
>            +------+                 +------+  x
>            |  Y1  |                 |  Y2  |  t
>            +--+---+                 +---+--+  e
>               | Y1:y1            Y2:y2  |     r
>               +----------+   +----------+     n
>                          |   |                a
>                  X1':x1' |   | X2':x2'        l
>                       +--+---+-+
>            ...........|   NAT  |...............
>                       +--+---+-+              I
>                          |   |                n
>                          |   |                t
>                          |   |                e
>                   +------+   +------+         r
>                   |                 |         n
>                   |x1               |x2       a
>                +-----+           +-----+      l
>                | X1  |           | X2  |
>                +-----+           +-----+
>
>
>         From internal to external:
>
>         X1':x1' =3D f(X1:x1,Y1:y1)
>         X2':x2' =3D f(X2:x2,Y2:y2)
>
>
>         From external to internal:
>
>         X1:x2 =3D f(Y1:y1,X1':x1')
>         X2:x2 =3D f(Y2:y2,X2':x2')
>
>
> Note that, I believe this model would allow for mapping rules to be =

> defined which still work well for p2p apps but give you the benefits of =

> address and port reuse across different sessions, without needing to =

> define rules based on what application is being used.
>
>   =

I am not sure i understand how would that be.
I mean, consider the following case (using your figure)
In this case we are reusing the transport address X'1,x'1, as was =

suggested, for both communications

                                              E
           +------+                 +------+  x
           |  Y1  |                 |  Y2  |  t
           +--+---+                 +---+--+  e
              | Y1:y1            Y2:y2  |     r
              +----------+   +----------+     n
                         |   |                a
                 X1':x1' |   | X1':x1'        l
                      +--+---+-+
           ...........|   NAT  |...............
                      +--+---+-+              I
                         |   |                n
                         |   |                t
                         |   |                e
                  +------+   +------+         r
                  |                 |         n
                  |x1               |x2       a
               +-----+           +-----+      l
               | X1  |           | X2  |
               +-----+           +-----+


        From internal to external:

        X1':x1' =3D f(X1:x1,Y1:y1)
        X1':x1' =3D f(X2:x2,Y2:y2)


        From external to internal:

        X1:x2 =3D f(Y1:y1,X1':x1')
        X2:x2 =3D f(Y2:y2,X2':x2')


So, now suppose that Y2:y2 wants to send packets toward X1,x1, how would =

he do that?
wouldn't that be a problem for p2p apps?
I mean, if the goal of X1 was to create a mpping so it can later on =

receive incoming communications through X'1,x'1, this would break that, =

right?

Regards, marcelo

> -Jonathan R.
>
>
> Philip Matthews wrote:
>   =

>> If I understand things correctly, what Iljitsch is suggesting is not  =

>> "address-dependent" mapping as I understand it. My understanding of  =

>> "address-dependent" mapping is that a new transport address (on the  =

>> public side of the NAT) is assigned by the NAT to every new  =

>> destination. However, Iljitsch wants instead to re-use the same  =

>> transport address for many different destinations.
>>
>> Let me give an example.
>> Let A and B be two nodes on the private side of the NAT.
>> Let X and Y be two nodes on the public side of the NAT.
>> Let (T,t) be some transport address assigned to the public side of the  =

>> NAT.
>>
>> Now consider the following flows:
>> Private       Public
>> Node          Node
>> (A,a) ------> (X,x1)
>> (A,a) ------> (X,x2)
>> (A,a) ------> (Y,y1)
>> (B,b2) -----> (Y,y2)
>>
>> - Endpoint-independent mapping would assign the same transport address  =

>> to the first three, and a different transport addresses to the last one.
>> - Address-dependent mapping would assign the same transport address to  =

>> the first two, and different transport addresses to the last two.
>> - Address-and-port-dependent mapping would assign different transport  =

>> addresses to all of these.
>> - But what Iljitsch wants to do is to assign the same transport  =

>> address (T,t) for all of these.
>>  From the NAT perspective, (T,t) can be used for all of these because,  =

>> when the response comes back from the public node, the NAT can  =

>> determine the private node to forward it to by which public node sent  =

>> the packet. For example, it would have a rule that says: if the packet  =

>> is destined for (T,t) and came from (X,x1), then change the  =

>> destination address to (A,a).
>>
>> I don't yet understand the implications of this, but I thought I  =

>> should point it out.
>>
>> - Philip
>>
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>>
>>     =

>
>   =



_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 03:57:13 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 139C628C1B2;
	Fri, 23 May 2008 03:57:13 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0C19428C1AE
	for <behave@core3.amsl.com>; Fri, 23 May 2008 03:57:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.612
X-Spam-Level: 
X-Spam-Status: No, score=-3.612 tagged_above=-999 required=5
	tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_BAD_ID=2.837, RCVD_IN_DNSWL_MED=-4]
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 hP3lTuTWQaxj for <behave@core3.amsl.com>;
	Fri, 23 May 2008 03:57:11 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133])
	by core3.amsl.com (Postfix) with ESMTP id D01DA28C1B2
	for <behave@ietf.org>; Fri, 23 May 2008 03:57:10 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (unknown 
	[163.117.203.43])by smtp03.uc3m.es (Postfix) with ESMTP id 94DE33C87CF;
	Fri, 23 May 2008 12:57:07 +0200 (CEST)
Message-ID: <48369D9C.8050208@it.uc3m.es>
Date: Fri, 23 May 2008 12:34:04 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
References: <483526BD.1090308@free.fr>
In-Reply-To: <483526BD.1090308@free.fr>
X-imss-version: 2.050
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-18.1562 TC:1F TRN:40 TV:5.5.1026(15926.006)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Address-port sparing NATs - a proposal
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi Remi,

i would change it in the following way:

PROPOSAL:
1. A NAT, to be an *address-port sparing NAT*,  MUST do mappings that
are address and port dependent if initiated with external-host ports equal =
to =

any well know port that does not requires endpoint independent behaviour (s=
uch as HTTP, DNS and so on).

2. A NAT  MUST do  mappings that are endpoint-independent for all the rest =
of the ports.


Bottom line, i think that the by default behaviour should be endpoint =

independent mapping and for some well know cases, we can save a lot if =

we do address and port dependent behaviour

Regards, marcelo


R=E9mi Despr=E9s escribi=F3:
> This is a correction of the previous proposal in
> http://www.ietf.org/mail-archive/web/behave/current/msg03875.html
> where Teredo, included in earlier version, was (obviously) missing.
>
> It also includes DNS as an application that can generate many transport =

> connections and doesn't need endpoint-independent mapping.
>
> The goal is to provide a practical answer to the (IMO very pertinent) =

> concern expressed in =

> http://www.ietf.org/mail-archive/web/behave/current/msg03821.html.
>
>
> PROPOSAL:
> 1. A NAT, to be an *address-port sparing NAT*,  MUST do mappings that
> are endpoint-dependent if initiated with external-host ports equal to 80
> (HTTP), or equal to 53 (DNS), or in the range 6881-6889 (BitTorrent).
>
> 2. A NAT  MUST do  mappings that are endpoint-independent if initiated
> with external-host ports in the 1990-1992 range (STUN) or equal to 3544
> (Teredo).
>
> 3. NATs MAY also do mappings that are endpoint-independent if initiated
> with external-host ports known to be those of applications compatible
> with it (POP3, SMTP, IMAP, NNTP, Telnet, SNMP, IPsec over UDP...).
>
>
>
> NOTES:
> The range of STUN is also that of STUNT and TURN.
>
> AFAIK, STUN and Teredo cover the NAT address-port discovery mechanisms =

> endorsed by IETF (if not, the rule has to be completed).
>
> After NAT address-port discovery, ANY application, that needed =

> endpoint-independent mapping may use the reserved address-port couple.
>
> RFC4787 says: "REQ-1:  A NAT MUST have an "Endpoint-Independent Mapping" =

> behavior." but, formally, rule 2 above also says that NATs MUST have =

> such a behavior. The new point is that it doesn't have it for ALL =

> transports connections (with the effect that address-port couples are =

> used sparingly).
>
>
> R=E9mi
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
>   =



_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 03:57:22 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4919128C217;
	Fri, 23 May 2008 03:57:22 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3433E28C1AE
	for <behave@core3.amsl.com>; Fri, 23 May 2008 03:57:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.687
X-Spam-Level: 
X-Spam-Status: No, score=-3.687 tagged_above=-999 required=5 tests=[AWL=0.075, 
	BAYES_00=-2.599, RCVD_BAD_ID=2.837, RCVD_IN_DNSWL_MED=-4]
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 alAO2fcZNEYG for <behave@core3.amsl.com>;
	Fri, 23 May 2008 03:57:15 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133])
	by core3.amsl.com (Postfix) with ESMTP id 90DDD28C11B
	for <behave@ietf.org>; Fri, 23 May 2008 03:57:15 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (unknown 
	[163.117.203.43])by smtp03.uc3m.es (Postfix) with ESMTP id D225B3C87E8;
	Fri, 23 May 2008 12:57:11 +0200 (CEST)
Message-ID: <4836A168.7000402@it.uc3m.es>
Date: Fri, 23 May 2008 12:50:16 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: Lars Eggert <lars.eggert@nokia.com>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com><2F0D498F-B9BC-4B53-A5
	70-281BC0D2CC91@nokia.com><0ac701c8bb6d$c4076ef0$a25b150a@cisco.com> 
	<DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
In-Reply-To: <DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
X-imss-version: 2.050
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-16.4875 TC:1F TRN:38 TV:5.5.1026(15926.006)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: behave@ietf.org, ext Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Lars Eggert escribi=F3:
>
>
> Right. IMO that proposal goes counter to the idea behind BEHAVE, which  =

> is to make NATs more regularized. Having the NAPT act differently  =

> based on what port numbers are used actually makes their behavior more  =

> diverse instead of more regularized.
>
> The key question is how a NAPT can accurately differentiate apps that  =

> use UNSAF from ones that don't, because that's the characteristic that  =

> can be used to drive more efficient connection multiplexing. You  =

> propose doing this based on the observable transmission behavior,  =

> Iljitsch/Remi have suggested doing it based on destination ports. Both  =

> have pros and cons. Do other options exist?
>
>   =

IMHO there is another important difference that is whether the default =

behaviour is endpoint independent or endpoint dependent.
In Iljitsch approach as i undrstood it, anything that does not uses the =

STUN ports is endpoint depedent. Default behaviour is then endpoint =

dependent mapping
A port approach could have a default endpoint indepedent behaviour =

except for those well know apps that are know to not require endpoint =

independent behaviour, like HTTP. (this could be similar to Remi =

approach, see my email to him)

In the timer approach, everything that does not benefits within the =

timeout is endpoint dependent. This is

imho, i think we are on the safe side if we only do endpoint depednent =

mappings for very well know widely deployed apps that don't use it. I =

mean, i don't think port 80 will be used in a different way anytime soon.

This would save quite some ports, cause they are the most widely used apps

All the rest should be endpoint independent, and we allow for future =

apps to benefit from the endpoint independency

Regards, marcelo
> Lars
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
>   =



_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 05:11:54 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 09FFF28C24F;
	Fri, 23 May 2008 05:11:54 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 520E328C1CE
	for <behave@core3.amsl.com>; Fri, 23 May 2008 05:11:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.764
X-Spam-Level: 
X-Spam-Status: No, score=-1.764 tagged_above=-999 required=5 tests=[AWL=0.185, 
	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 Q1IAllUsZuut for <behave@core3.amsl.com>;
	Fri, 23 May 2008 05:11:48 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id E545628C239
	for <behave@ietf.org>; Fri, 23 May 2008 05:11:47 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id BC5373EA0F3;
	Fri, 23 May 2008 14:11:46 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 7818B3EA0AA;
	Fri, 23 May 2008 14:11:46 +0200 (CEST)
Message-ID: <4836B48A.5000500@free.fr>
Date: Fri, 23 May 2008 14:11:54 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
References: <483526BD.1090308@free.fr> <48369D9C.8050208@it.uc3m.es>
In-Reply-To: <48369D9C.8050208@it.uc3m.es>
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Address-port sparing NATs - a proposal
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

marcelo bagnulo braun  - Le 5/23/08 12:34 PM :
> Hi Remi,
> =

> i would change it in the following way:
> =

> PROPOSAL:
> 1. A NAT, to be an *address-port sparing NAT*,  MUST do mappings that
> are address and port dependent if initiated with external-host ports =

> equal to any well know port that does not requires endpoint independent =

> behaviour (such as HTTP, DNS and so on).
Maybe it should be "wellknown *or registered* port".

Adding BitTorrent ports 6881 to 6889 (not registered yet, but well =

identified) could be very effective to spare address-port couples (to be =

confirmed... or invalidated).


> 2. A NAT  MUST do  mappings that are endpoint-independent for all the =

> rest of the ports.
> =

> =

> Bottom line, i think that the by default behaviour should be endpoint =

> independent mapping and for some well know cases, we can save a lot if =

> we do address and port dependent behaviour
Yes.
This I hope can be a consensus.


R=E9mi
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 08:12:46 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6D9AD28C2CF;
	Fri, 23 May 2008 08:12:46 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3AFBC28C2CF
	for <behave@core3.amsl.com>; Fri, 23 May 2008 08:12:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, 
	BAYES_00=-2.599]
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 v935An9J9trq for <behave@core3.amsl.com>;
	Fri, 23 May 2008 08:12:43 -0700 (PDT)
Received: from mail.sipeerior.com (mail.sipeerior.com [128.239.5.131])
	by core3.amsl.com (Postfix) with ESMTP id DF49328C2DB
	for <behave@ietf.org>; Fri, 23 May 2008 08:12:42 -0700 (PDT)
Received: from vuelta.local (unknown [128.239.5.147])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.sipeerior.com (Postfix) with ESMTP id 1688F505A99;
	Fri, 23 May 2008 11:12:42 -0400 (EDT)
Message-ID: <4836DEE5.4070901@sipeerior.com>
Date: Fri, 23 May 2008 11:12:37 -0400
From: Bruce Lowekamp <lowekamp@sipeerior.com>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>	<DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
	<09c701c8bc37$83bb4310$1496150a@cisco.com>
In-Reply-To: <09c701c8bc37$83bb4310$1496150a@cisco.com>
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Dan Wing wrote:
>>> Several other people have proposed using port numbers to decide if
>>> UNSAF was being used, under the assmption that TCP/80, TCP/110
>>> (POP3), etc., don't use UNSAF.  That is certainly another direction
>>> to pursue.  My concern with that mechanism is that it would create
>>> the first instance where a NAT's behavior is radically different
>>> based on the port number.
>> Right. IMO that proposal goes counter to the idea behind 
>> BEHAVE, which  
>> is to make NATs more regularized. Having the NAPT act differently  
>> based on what port numbers are used actually makes their 
>> behavior more  
>> diverse instead of more regularized.
>>
>> The key question is how a NAPT can accurately differentiate 
>> apps that  
>> use UNSAF from ones that don't, because that's the 
>> characteristic that  
>> can be used to drive more efficient connection multiplexing. You  
>> propose doing this based on the observable transmission behavior,  
>> Iljitsch/Remi have suggested doing it based on destination 
>> ports. Both  
>> have pros and cons. Do other options exist?
> 
> Those are the two proposals that I have seen.  I believe they
> could reasonably be combined.  For example, from my perspective
> with timers, I consider Iljitsch/Remi's proposal as using a 0-second 
> timer for certain ports (e.g., TCP/80) and an infinite timer for other
> ports.

I think my preference would be to specify endpoint-dependent mapping 
only on "known safe ports", but I do think that the timers option is an 
intriguing idea.

The only problem I have with the timers idea is that its success for p2p 
seems to be dependent on the number of external connections (through the 
NAT) required by the application.  Which I suspect means that if the NAT 
box is in front of only a few thousand machines, then most p2p apps 
would easily meet the timer requirement because their connections would 
cross the NAT.  But if the p2p application is part of an overlay that 
exists entirely (or almost entirely) behind the NAT, either because it's 
a local group or because the NAT is in front of an entire ISP, it seems 
to be less likely that the timer condition will be met.

Maybe the right way to combine these is to view the timer as a fallback 
condition.  So here's a new proposal:


An address-port sparing NAT MAY use endpoint dependent mapping for 
connections whose destination port specifies a known-compatible protocol 
(HTTP, SMTP, etc).  Otherwise, it MUST default to endpoint-independent 
mapping characteristics.  In the event of overload, where it is no 
longer able to preserve endpoint independent mapping for new 
connections, the NAT MAY apply the timer algorithm to prioritize which 
connections receive endpoint-dependent mapping.

(obviously the list of ports, definition of overload, and the timer 
algorithm need work)

Bruce
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 09:51:00 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 681A13A6B3B;
	Fri, 23 May 2008 09:51:00 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1988D3A6B3B
	for <behave@core3.amsl.com>; Fri, 23 May 2008 09:50:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.466
X-Spam-Level: *
X-Spam-Status: No, score=1.466 tagged_above=-999 required=5 tests=[AWL=-5.128, 
	BAYES_00=-2.599, FB_REM_PART=10.357, RCVD_BAD_ID=2.837,
	RCVD_IN_DNSWL_MED=-4]
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 CaAx22TyLY7e for <behave@core3.amsl.com>;
	Fri, 23 May 2008 09:50:58 -0700 (PDT)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131])
	by core3.amsl.com (Postfix) with ESMTP id F073C3A6A29
	for <behave@ietf.org>; Fri, 23 May 2008 09:50:57 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (unknown 
	[163.117.203.43])by smtp01.uc3m.es (Postfix) with ESMTP id C083B6375FE;
	Fri, 23 May 2008 18:50:50 +0200 (CEST)
Message-ID: <4836F52D.7030809@it.uc3m.es>
Date: Fri, 23 May 2008 18:47:41 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Bruce Lowekamp <lowekamp@sipeerior.com>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A
	570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>	<DF
	3	5AA43-736F-454A-A471-123DBE79274D@nokia.com><09c701c8bc37$83bb4310$1496150a@cisco.com>
	<4836DEE5.4070901@sipeerior.com>
In-Reply-To: <4836DEE5.4070901@sipeerior.com>
X-imss-version: 2.050
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-31.0755 TC:1F TRN:63 TV:5.5.1026(15928.000)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: behave@ietf.org, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Bruce Lowekamp escribi=F3:
> Dan Wing wrote:
>   =

>>>> Several other people have proposed using port numbers to decide if
>>>> UNSAF was being used, under the assmption that TCP/80, TCP/110
>>>> (POP3), etc., don't use UNSAF.  That is certainly another direction
>>>> to pursue.  My concern with that mechanism is that it would create
>>>> the first instance where a NAT's behavior is radically different
>>>> based on the port number.
>>>>         =

>>> Right. IMO that proposal goes counter to the idea behind =

>>> BEHAVE, which  =

>>> is to make NATs more regularized. Having the NAPT act differently  =

>>> based on what port numbers are used actually makes their =

>>> behavior more  =

>>> diverse instead of more regularized.
>>>
>>> The key question is how a NAPT can accurately differentiate =

>>> apps that  =

>>> use UNSAF from ones that don't, because that's the =

>>> characteristic that  =

>>> can be used to drive more efficient connection multiplexing. You  =

>>> propose doing this based on the observable transmission behavior,  =

>>> Iljitsch/Remi have suggested doing it based on destination =

>>> ports. Both  =

>>> have pros and cons. Do other options exist?
>>>       =

>> Those are the two proposals that I have seen.  I believe they
>> could reasonably be combined.  For example, from my perspective
>> with timers, I consider Iljitsch/Remi's proposal as using a 0-second =

>> timer for certain ports (e.g., TCP/80) and an infinite timer for other
>> ports.
>>     =

>
> I think my preference would be to specify endpoint-dependent mapping =

> only on "known safe ports", but I do think that the timers option is an =

> intriguing idea.
>
> The only problem I have with the timers idea is that its success for p2p =

> seems to be dependent on the number of external connections (through the =

> NAT) required by the application.  Which I suspect means that if the NAT =

> box is in front of only a few thousand machines, then most p2p apps =

> would easily meet the timer requirement because their connections would =

> cross the NAT.  But if the p2p application is part of an overlay that =

> exists entirely (or almost entirely) behind the NAT, either because it's =

> a local group or because the NAT is in front of an entire ISP, it seems =

> to be less likely that the timer condition will be met.
>
> Maybe the right way to combine these is to view the timer as a fallback =

> condition.  So here's a new proposal:
>
>
> An address-port sparing NAT MAY use endpoint dependent mapping for =

> connections whose destination port specifies a known-compatible protocol =

> (HTTP, SMTP, etc).  Otherwise, it MUST default to endpoint-independent =

> mapping characteristics.  In the event of overload, where it is no =

> longer able to preserve endpoint independent mapping for new =

> connections, the NAT MAY apply the timer algorithm to prioritize which =

> connections receive endpoint-dependent mapping.
>   =



I really don't like the last part. Essentially this would result in non =

deterministic behaviour, since a nat could be endpoint independet or =

endpoint dependent depending on the load and i think we must avoid that

I would simply keep the first two parts and remov the last one

regards, marcelo
> (obviously the list of ports, definition of overload, and the timer =

> algorithm need work)
>
> Bruce
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
>   =



_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 11:14:20 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AA83C28C2A1;
	Fri, 23 May 2008 11:14:20 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0C08528C2A1
	for <behave@core3.amsl.com>; Fri, 23 May 2008 11:14:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.679
X-Spam-Level: **
X-Spam-Status: No, score=2.679 tagged_above=-999 required=5 tests=[AWL=-5.079, 
	BAYES_00=-2.599, FB_REM_PART=10.357]
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 EMAGIV98Hr7w for <behave@core3.amsl.com>;
	Fri, 23 May 2008 11:14:19 -0700 (PDT)
Received: from mail.sipeerior.com (mail.sipeerior.com [128.239.5.131])
	by core3.amsl.com (Postfix) with ESMTP id F269B28C1B2
	for <behave@ietf.org>; Fri, 23 May 2008 11:14:18 -0700 (PDT)
Received: from vuelta.local (unknown [128.239.5.147])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.sipeerior.com (Postfix) with ESMTP id 71D20505A99;
	Fri, 23 May 2008 14:14:17 -0400 (EDT)
Message-ID: <48370975.8040307@sipeerior.com>
Date: Fri, 23 May 2008 14:14:13 -0400
From: Bruce Lowekamp <lowekamp@sipeerior.com>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A		570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>	<DF	3	5AA43-736F-454A-A471-123DBE79274D@nokia.com><09c701c8bc37$83bb4310$1496150a@cisco.com>
	<4836DEE5.4070901@sipeerior.com> <4836F52D.7030809@it.uc3m.es>
In-Reply-To: <4836F52D.7030809@it.uc3m.es>
Cc: behave@ietf.org, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

marcelo bagnulo braun wrote:
> Bruce Lowekamp escribi=F3:
>> Dan Wing wrote:
>>  =

>>>>> Several other people have proposed using port numbers to decide if
>>>>> UNSAF was being used, under the assmption that TCP/80, TCP/110
>>>>> (POP3), etc., don't use UNSAF.  That is certainly another direction
>>>>> to pursue.  My concern with that mechanism is that it would create
>>>>> the first instance where a NAT's behavior is radically different
>>>>> based on the port number.
>>>>>         =

>>>> Right. IMO that proposal goes counter to the idea behind BEHAVE, =

>>>> which  is to make NATs more regularized. Having the NAPT act =

>>>> differently  based on what port numbers are used actually makes =

>>>> their behavior more  diverse instead of more regularized.
>>>>
>>>> The key question is how a NAPT can accurately differentiate apps =

>>>> that  use UNSAF from ones that don't, because that's the =

>>>> characteristic that  can be used to drive more efficient connection =

>>>> multiplexing. You  propose doing this based on the observable =

>>>> transmission behavior,  Iljitsch/Remi have suggested doing it based =

>>>> on destination ports. Both  have pros and cons. Do other options exist?
>>>>       =

>>> Those are the two proposals that I have seen.  I believe they
>>> could reasonably be combined.  For example, from my perspective
>>> with timers, I consider Iljitsch/Remi's proposal as using a 0-second =

>>> timer for certain ports (e.g., TCP/80) and an infinite timer for other
>>> ports.
>>>     =

>>
>> I think my preference would be to specify endpoint-dependent mapping =

>> only on "known safe ports", but I do think that the timers option is =

>> an intriguing idea.
>>
>> The only problem I have with the timers idea is that its success for =

>> p2p seems to be dependent on the number of external connections =

>> (through the NAT) required by the application.  Which I suspect means =

>> that if the NAT box is in front of only a few thousand machines, then =

>> most p2p apps would easily meet the timer requirement because their =

>> connections would cross the NAT.  But if the p2p application is part =

>> of an overlay that exists entirely (or almost entirely) behind the =

>> NAT, either because it's a local group or because the NAT is in front =

>> of an entire ISP, it seems to be less likely that the timer condition =

>> will be met.
>>
>> Maybe the right way to combine these is to view the timer as a =

>> fallback condition.  So here's a new proposal:
>>
>>
>> An address-port sparing NAT MAY use endpoint dependent mapping for =

>> connections whose destination port specifies a known-compatible =

>> protocol (HTTP, SMTP, etc).  Otherwise, it MUST default to =

>> endpoint-independent mapping characteristics.  In the event of =

>> overload, where it is no longer able to preserve endpoint independent =

>> mapping for new connections, the NAT MAY apply the timer algorithm to =

>> prioritize which connections receive endpoint-dependent mapping.
>>   =

> =

> =

> I really don't like the last part. Essentially this would result in non =

> deterministic behaviour, since a nat could be endpoint independet or =

> endpoint dependent depending on the load and i think we must avoid that
> =

> I would simply keep the first two parts and remov the last one

Well, OK.  I don't really like the behavior much either and would prefer =

   to mandate endpoint-independent mapping all the time for all ports. =

  But removing the third part just leaves the behavior in the event of =

overload undefined.  That's not clearly better than specifying a =

not-too-terribly-evil thing to do in an overload scenario, is it?

Bruce
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 11:52:15 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 028103A6C6E;
	Fri, 23 May 2008 11:52:15 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8C47928C127
	for <behave@core3.amsl.com>; Fri, 23 May 2008 11:52:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.149
X-Spam-Level: 
X-Spam-Status: No, score=-6.149 tagged_above=-999 required=5
	tests=[AWL=-0.450, BAYES_00=-2.599, J_CHICKENPOX_24=0.6,
	MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 hk4ZG-iMqO4Q for <behave@core3.amsl.com>;
	Fri, 23 May 2008 11:52:13 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 4D7D03A6B79
	for <behave@ietf.org>; Fri, 23 May 2008 11:52:13 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,531,1204531200"; d="scan'208";a="103145222"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 23 May 2008 11:52:12 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m4NIqCGF027901; 
	Fri, 23 May 2008 11:52:12 -0700
Received: from dwingwxp01 ([10.21.75.175])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m4NIqBwq005658;
	Fri, 23 May 2008 18:52:12 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "=?iso-8859-1?Q?'R=E9mi_Denis-Courmont'?=" <remi.denis-courmont@nokia.com>,
	<behave@ietf.org>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>
	<200805230955.37501.remi.denis-courmont@nokia.com>
Date: Fri, 23 May 2008 08:52:12 -1000
Message-ID: <06db01c8bd06$1d17eda0$d8e9520a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Aci8oiHtziDmNtxnSAWN7xeMMcXcbQAYe9kg
In-Reply-To: <200805230955.37501.remi.denis-courmont@nokia.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1831; t=1211568732;
	x=1212432732; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Dynamic=20Port=20Reuse
	|Sender:=20; bh=B1x1KIlGW6SQzTIaGtyNG8I1b9CLHJSGtwYVp6LOhUI=;
	b=IvDN6ym9H8TeCZFncoIZzi0ym0EzsPrKA3kHPqzz+5rpK8LRN+vY6+8lo6
	iDMQkavpfbrKDyi22Y0ZaEoJW2/CsV8lB0wnVL01gRogAPbmOuninkR5PLUP
	cCHB9BIpS8;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

> -----Original Message-----
> From: R=E9mi Denis-Courmont [mailto:remi.denis-courmont@nokia.com] =

> Sent: Thursday, May 22, 2008 8:56 PM
> To: behave@ietf.org
> Cc: ext Dan Wing
> Subject: Re: [BEHAVE] Dynamic Port Reuse
> =

> Le Wednesday 14 May 2008 20:15:13 ext Dan Wing, vous avez =E9crit=A0:
> > My strawman proposal is at:
> > =

> http://tools.ietf.org/html/draft-wing-behave-dynamic-tcp-port-reuse-00
> >
> > Abstract:
> >   A strawman proposal is made to reduce public-facing TCP =

> >   port use with
> >   large Network Address and Port Translators (NAPTs).  This proposal
> >   attempts to preserve emergent NAT traversal techniques.  It is
> >   anticipated that large NAPTs will be used for NAT64.
> =

> ALGO-1 as it stands might break TCP. A NAT must not reuse the =

> same port number =

> for a different internal IP:port typle, toward the same =

> remote IP:port tuple.

The top of section 3 acknowledges that:

   With all algorithms proposed below, a new TCP connection from an
   internal host cannot re-use the same public TCP source port and
   address to the same remote destination port and address (i.e., you
   cannot use the same 5-tuple for a new connection).

> In any case, ALGO-1 breaks TCP-SO. I think the real issue is, whether =

> TCP-SO/IPv4 really matters.... It would seem so unreliable =

> that people will =

> end up using UDP.

ALGO-1 is only intended to work for "client/server applications", such
as SMTP, HTTP, POP3, IMAP, BitTorrtent, etc.  For those client/server =

applications, I do not believe we need TCP simultaneous open.

If you want TCP simultaneous open, you would need ALGO-2 or ALGO-3 which
are UNSAF-safe (that is, they work with UNSAF and ALGO-2 and ALGO-3 =

should work just fine with TCP simultaneous open).

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 12:16:40 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0DC523A6CCB;
	Fri, 23 May 2008 12:16:40 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F16073A6CCB
	for <behave@core3.amsl.com>; Fri, 23 May 2008 12:16:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.271
X-Spam-Level: 
X-Spam-Status: No, score=-1.271 tagged_above=-999 required=5
	tests=[AWL=-5.028, BAYES_00=-2.599, FB_REM_PART=10.357,
	RCVD_IN_DNSWL_MED=-4]
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 71GJNCIh2BDt for <behave@core3.amsl.com>;
	Fri, 23 May 2008 12:16:38 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 247553A6C6E
	for <behave@ietf.org>; Fri, 23 May 2008 12:16:38 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,531,1204531200"; d="scan'208";a="71806590"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 23 May 2008 12:16:37 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4NJGbBS004523; 
	Fri, 23 May 2008 12:16:37 -0700
Received: from dwingwxp01 ([10.21.75.175])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4NJGaQn012366;
	Fri, 23 May 2008 19:16:36 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Bruce Lowekamp'" <lowekamp@sipeerior.com>,
	"'marcelo bagnulo braun'" <marcelo@it.uc3m.es>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A		570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>	<DF	3	5AA43-736F-454A-A471-123DBE79274D@nokia.com><09c701c8bc37$83bb4310$1496150a@cisco.com><4836DEE5.4070901@sipeerior.com>
	<4836F52D.7030809@it.uc3m.es> <48370975.8040307@sipeerior.com>
Date: Fri, 23 May 2008 09:16:37 -1000
Message-ID: <0af801c8bd09$860355e0$d8e9520a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Aci9ANO7zCyP9tFTTUO2CUo0irKApAABvrQg
In-Reply-To: <48370975.8040307@sipeerior.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2479; t=1211570197;
	x=1212434197; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Dynamic=20Port=20Reuse
	|Sender:=20; bh=/JskgMmnSqetBXahKI7e3A6pzJAoEYj1CUrGdz2VxX4=;
	b=Nr6hbrUCT+zg/s6T58y97qSWRO5tmnhDDYHQ7d86uMea9O7BxkJTpmELqy
	VqIPUdKeyGuvNDxafGXbOUgsgGDDFwpPvb476q0MQzmAHLCh16VqtcRxgcs1
	CGVYMLSNAcNfHe6E3l5T475EHJOnq4SWE2jg/Ge81aYZruHPi39tc=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

> >> Maybe the right way to combine these is to view the timer as a 
> >> fallback condition.  So here's a new proposal:
> >>
> >>
> >> An address-port sparing NAT MAY use endpoint dependent mapping for 
> >> connections whose destination port specifies a known-compatible 
> >> protocol (HTTP, SMTP, etc).  Otherwise, it MUST default to 
> >> endpoint-independent mapping characteristics.  In the event of 
> >> overload, where it is no longer able to preserve endpoint 
> independent 
> >> mapping for new connections, the NAT MAY apply the timer 
> algorithm to 
> >> prioritize which connections receive endpoint-dependent mapping.
> >>   
> > 
> > 
> > I really don't like the last part. Essentially this would 
> result in non 
> > deterministic behaviour, since a nat could be endpoint 
> independet or 
> > endpoint dependent depending on the load and i think we 
> must avoid that
> > 
> > I would simply keep the first two parts and remov the last one
> 
> Well, OK.  I don't really like the behavior much either and 
> would prefer 
>    to mandate endpoint-independent mapping all the time for 
> all ports. 
>   But removing the third part just leaves the behavior in the 
> event of 
> overload undefined.  That's not clearly better than specifying a 
> not-too-terribly-evil thing to do in an overload scenario, is it?

Using port numbers is, itself, non-deterministic.  This is because
no two people will generate the same list ports that are safe to
re-use.  If ports are used, then in 3 years, as NAT64 vendors find
value in optimizing re-use of other port numbers, the vendors will
begin diverging which ports are re-used.

For example, here would be my list of ports that are safe to re-use:
TCP/80 (HTTP), TCP/110 (POP3), TCP/995 (POP3S), TCP/143 (IMAP), TCP/587
(SUBMIT), TCP/25 (SMTP), TCP/22 (SSH), TCP/21 (FTP), TCP/23 (TELNET),
TCP/7 (ECHO), TCP/9 (DISCARD), TCP/993 (IMAPS).

Are there non-IETF protocols that are used which would break with
port re-use?  That is, that use UNSAF or use TCP S-O?


As BitTorrent has not registered their ports with IANA, I'm not sure
what could be said in an IETF document about its ports other than 
some non-normative "and other ports that the NAT64 believes, to the
best of its knowledge, are used by client/server applications that
can safely have their TCP source ports re-used."  Which brings us
to specify non-deterministic behavior for such a NAT64.

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 14:27:33 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 348CE28C31E;
	Fri, 23 May 2008 14:27:33 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A852528C31B
	for <behave@core3.amsl.com>; Fri, 23 May 2008 14:27:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.042
X-Spam-Level: 
X-Spam-Status: No, score=-5.042 tagged_above=-999 required=5 tests=[AWL=1.257, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 A8zO6xf0QDsQ for <behave@core3.amsl.com>;
	Fri, 23 May 2008 14:27:30 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id C2A6F28C31D
	for <behave@ietf.org>; Fri, 23 May 2008 14:27:27 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,532,1204531200"; d="scan'208";a="103209927"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 23 May 2008 14:27:26 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m4NLRQ1A025749; 
	Fri, 23 May 2008 14:27:26 -0700
Received: from dwingwxp01 ([10.21.71.57])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m4NLRMhp025526;
	Fri, 23 May 2008 21:27:25 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "=?iso-8859-1?Q?'R=E9mi_Despr=E9s'?=" <remi.despres@free.fr>,
	"'Lars Eggert'" <lars.eggert@nokia.com>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>
	<DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
	<4835984F.6080504@free.fr>
	<F5356B94-213A-486F-9A93-7BDBB0D0BC51@nokia.com>
	<4836876D.4080907@free.fr>
Date: Fri, 23 May 2008 11:27:19 -1000
Message-ID: <0c9d01c8bd1b$ca3e8240$d8e9520a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Aci8s0yU3tTfloo0ReaEu7desyNTiAAXjWhA
In-Reply-To: <4836876D.4080907@free.fr>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=916; t=1211578046; x=1212442046;
	c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Dynamic=20Port=20Reuse
	|Sender:=20; bh=093u2ti0qbGnZa4MafnVr7WtdtknuPFCDKWd44js//Y=;
	b=s9ccCDST0inubnOhxi6o0bvvzUtLxTmG6DaQmQklpZOrFnUAIjKFtsnY+e
	ARbXkk6DJI3yMJCgNe/vgo/E0NG2WeVmJEgBJA2d1ef3J5Q6tg6guKT24Je8
	VNHeqopfUj;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

> IMO, simplicity and reliability are the strong points in 
> favor of ports vs timings.

Please build a list of ports, so we can talk about them specifically
instead of generally.

> So far, there is IMU no strong point in favor of timings.

The advantage of timing port re-use is self-learning and self-
adjusting to the needs of the TCP application.

Whether any of us consider that a 'strong point' is, I agree, a 
matter of debate.

...
> If nothing else, susceptibility of these NATs, or APBP 
> servers, to DOS 
> attacks will strongly depend on their margin between available 
> address-port couples and those that are normally used.

Yes, an ISP's NAT will certainly have to limit how many ports they 
allocate to any particular subscriber.  Even low-end home NATs
do this today (for all hosts behind the NAT) so they don't consume 
all of their memory with connection tables.

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 14:27:33 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 623AA28C324;
	Fri, 23 May 2008 14:27:33 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B87D028C31B
	for <behave@core3.amsl.com>; Fri, 23 May 2008 14:27:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.293
X-Spam-Level: 
X-Spam-Status: No, score=-5.293 tagged_above=-999 required=5 tests=[AWL=1.006, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 Mq5nX7w+4BdN for <behave@core3.amsl.com>;
	Fri, 23 May 2008 14:27:30 -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 E01C028C31E
	for <behave@ietf.org>; Fri, 23 May 2008 14:27:27 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,532,1204531200"; d="scan'208";a="49917490"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-2.cisco.com with ESMTP; 23 May 2008 14:27:27 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4NLRQLW010930; 
	Fri, 23 May 2008 14:27:26 -0700
Received: from dwingwxp01 ([10.21.71.57])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m4NLRMhq025526;
	Fri, 23 May 2008 21:27:26 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Lars Eggert'" <lars.eggert@nokia.com>,
	"=?iso-8859-1?Q?'ext_R=E9mi_Despr=E9s'?=" <remi.despres@free.fr>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>
	<DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
	<4835984F.6080504@free.fr>
	<F5356B94-213A-486F-9A93-7BDBB0D0BC51@nokia.com>
Date: Fri, 23 May 2008 11:27:19 -1000
Message-ID: <0c9e01c8bd1b$cab0f320$d8e9520a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Aci8p939Aio15r2ASOSMG/B67NWKWgAYgS2g
In-Reply-To: <F5356B94-213A-486F-9A93-7BDBB0D0BC51@nokia.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1622; t=1211578046;
	x=1212442046; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20need=20for=20port=20re-use=20[was=20Re=3A=20[BE
	HAVE]=20Dynamic=20Port=20Reuse] |Sender:=20;
	bh=/AczNfYpv3f412FidcrQpllnno0LTdiA78ad+fmod4g=;
	b=I85JjXQHv/TyU2I38dR2uAG9QQE35KGp2FbVm9NmkR9BDB/Wvbzp+jxXSr
	LbVPeEs6ECyXD6fiUyHBJzLRp6AEAEjvX27E7pGvpobr1MtRSzjDAEtEClmL
	9jnxYUPDki6BUrwbBFrZdUCmQ0g8W4BXLgiLXkGSC+7EQ4Bo1k+dc=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: behave@ietf.org
Subject: [BEHAVE] need for port re-use [was Re:  Dynamic Port Reuse]
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


> Both current proposals have advantages and disadvantages, and the  
> tradeoffs need to be understood. I'm not a particular fan of using  
> either ports or timers - both are crufty - because I'm still  
> unconvinced that we actually need to solve this problem in the first  
> place. Anyone got data about how often NATs run out of 
> binding entries  
> in situations where another IPv4 address isn't available?

For whatever it's worth:

Some University of Colorado researchers filled up their NAT's binding table,
unbeknownst to them: 
http://systems.cs.colorado.edu/mediawiki/index.php/Broadband_Network_Managemen
t

And I have done the same with my home NAT when using FTP to mirror the
Internet-Drafts archive (the separate FTP data connections consumed all of my
NAT's binding table entries).  My home NAT (a Linksys WRT54G with 3rd party
firmware) is configured to remember about 1000 UDP and TCP bindings.


The difference is that with NAT64, it isn't just yourself you would harm by
consuming all of the TCP ports on the NAT -- it is everyone else using that
NAT64 who cannot, now, obtain another TCP port.  The reason for NAT64 is to
avoid giving every subscriber their own IPv4 address and to get multiple
subscribers NATted to one IP address.  As Iljitsch described in the middle of
http://www.ietf.org/mail-archive/web/behave/current/msg03821.html, some
commonly-deployed applications and commonly-accessed Web 2.0 sites cause a lot
of TCP connections to be created, which reduces the number of subscribers an
ISP could expect to place behind a single IPv4 address.

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 14:33:26 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 628253A6CD3;
	Fri, 23 May 2008 14:33:26 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5EF643A6D09
	for <behave@core3.amsl.com>; Fri, 23 May 2008 14:33:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.949
X-Spam-Level: ***
X-Spam-Status: No, score=3.949 tagged_above=-999 required=5 tests=[AWL=-3.809, 
	BAYES_00=-2.599, FB_REM_PART=10.357]
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 plI6ZeHA8XUC for <behave@core3.amsl.com>;
	Fri, 23 May 2008 14:33:24 -0700 (PDT)
Received: from mail.sipeerior.com (mail.sipeerior.com [128.239.5.131])
	by core3.amsl.com (Postfix) with ESMTP id 3BAD13A6CD3
	for <behave@ietf.org>; Fri, 23 May 2008 14:33:24 -0700 (PDT)
Received: from vuelta.local (unknown [128.239.5.147])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.sipeerior.com (Postfix) with ESMTP id 5F7C3505A99;
	Fri, 23 May 2008 17:33:23 -0400 (EDT)
Message-ID: <4837381E.4040205@sipeerior.com>
Date: Fri, 23 May 2008 17:33:18 -0400
From: Bruce Lowekamp <lowekamp@sipeerior.com>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A		570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>	<DF	3	5AA43-736F-454A-A471-123DBE79274D@nokia.com><09c701c8bc37$83bb4310$1496150a@cisco.com><4836DEE5.4070901@sipeerior.com>
	<4836F52D.7030809@it.uc3m.es> <48370975.8040307@sipeerior.com>
	<0af801c8bd09$860355e0$d8e9520a@cisco.com>
In-Reply-To: <0af801c8bd09$860355e0$d8e9520a@cisco.com>
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Dan Wing wrote:
>>>> Maybe the right way to combine these is to view the timer as a 
>>>> fallback condition.  So here's a new proposal:
>>>>
>>>>
>>>> An address-port sparing NAT MAY use endpoint dependent mapping for 
>>>> connections whose destination port specifies a known-compatible 
>>>> protocol (HTTP, SMTP, etc).  Otherwise, it MUST default to 
>>>> endpoint-independent mapping characteristics.  In the event of 
>>>> overload, where it is no longer able to preserve endpoint 
>> independent 
>>>> mapping for new connections, the NAT MAY apply the timer 
>> algorithm to 
>>>> prioritize which connections receive endpoint-dependent mapping.
>>>>   
>>>
>>> I really don't like the last part. Essentially this would 
>> result in non 
>>> deterministic behaviour, since a nat could be endpoint 
>> independet or 
>>> endpoint dependent depending on the load and i think we 
>> must avoid that
>>> I would simply keep the first two parts and remov the last one
>> Well, OK.  I don't really like the behavior much either and 
>> would prefer 
>>    to mandate endpoint-independent mapping all the time for 
>> all ports. 
>>   But removing the third part just leaves the behavior in the 
>> event of 
>> overload undefined.  That's not clearly better than specifying a 
>> not-too-terribly-evil thing to do in an overload scenario, is it?
> 
> Using port numbers is, itself, non-deterministic.  This is because
> no two people will generate the same list ports that are safe to
> re-use.  If ports are used, then in 3 years, as NAT64 vendors find
> value in optimizing re-use of other port numbers, the vendors will
> begin diverging which ports are re-used.
> 
> For example, here would be my list of ports that are safe to re-use:
> TCP/80 (HTTP), TCP/110 (POP3), TCP/995 (POP3S), TCP/143 (IMAP), TCP/587
> (SUBMIT), TCP/25 (SMTP), TCP/22 (SSH), TCP/21 (FTP), TCP/23 (TELNET),
> TCP/7 (ECHO), TCP/9 (DISCARD), TCP/993 (IMAPS).
> 
> Are there non-IETF protocols that are used which would break with
> port re-use?  That is, that use UNSAF or use TCP S-O?
> 
> 
> As BitTorrent has not registered their ports with IANA, I'm not sure
> what could be said in an IETF document about its ports other than 
> some non-normative "and other ports that the NAT64 believes, to the
> best of its knowledge, are used by client/server applications that
> can safely have their TCP source ports re-used."  Which brings us
> to specify non-deterministic behavior for such a NAT64.

So does that leave anything other than telling the people interested in 
NAT64 scalability that the NATs need to be big enough to not suffer from 
port overload?  I disbelieve that it's ever going to be possible to do 
such a thing (one misbehaving application can consume an awful lot of 
ports).  I don't know whether I believe BEHAVE can have an impact on how 
vendors develop such a device, but it seems like specifying BCP that are 
more likely to not break the world than other behaviors is useful from 
an engineering point of view.

I agree that creating a lengthy list is probably an unending task.  (I 
would argue against including bittorrent in there.)  But I think there 
is a core of widely distributed applications that probably 99% of the 
people in the room would agree with.  Even if that list is only HTTP, 
SMTP, POP, SSH, and IMAP, it will help here.  It will probably needed to 
be updated every n years to keep it current (or IPv6 will be universally 
deployed and the list can be allowed to rus).

I wasn't trying to make the argument that using port numbers was 
deterministic, only that leaving overload behavior entirely unspecified 
seems likely to produce the kind of variety of broken behavior that 
motivated BEHAVE to be formed in the first place.  If the timer 
algorithm helps to allow a NAT to avoid imposing endpoint dependent 
mapping on EVERY application when it experiences high load, that's not 
too bad of a result.  That level of load IS going to happen.

Bruce

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 14:47:05 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8CDD23A6D0A;
	Fri, 23 May 2008 14:47:05 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A3B2B3A6D15
	for <behave@core3.amsl.com>; Fri, 23 May 2008 14:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.329
X-Spam-Level: 
X-Spam-Status: No, score=-6.329 tagged_above=-999 required=5 tests=[AWL=0.270, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 V9DY-2CxwX2v for <behave@core3.amsl.com>;
	Fri, 23 May 2008 14:46:59 -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 E761E3A6D0B
	for <behave@ietf.org>; Fri, 23 May 2008 14:46:59 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,532,1204531200"; d="scan'208";a="49922993"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-2.cisco.com with ESMTP; 23 May 2008 14:46:59 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m4NLkx2t003433; 
	Fri, 23 May 2008 14:46:59 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m4NLkxAq009598;
	Fri, 23 May 2008 21:46:59 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 23 May 2008 14:46:59 -0700
Received: from [10.32.241.148] ([10.32.241.148]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 23 May 2008 14:46:58 -0700
Message-ID: <48373B5B.3040306@cisco.com>
Date: Fri, 23 May 2008 17:47:07 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d		74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11	4	41.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es><48286CFD.	10	80204@free.fr>	<48287AE5.5010005@sipeerior.com><482882B7.2030806@free.fr	><1	45B7DFA-E397-4184-8FA6-3C255078509F@muada.com><48289C15.3000102@free.fr	>	<4	828A33E.1080700@sipeerior.com><4828ABBE.9010201@free.fr>	<4828AE1B.904	0901@	sipeerior.com>	<03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>	<0158	01c8b5	0d$984b8eb0$c3f0200a@cisco.com>	<8EFD78D3-46EC-4BA5-9F9A-B6F471B9C01	F@gmail	.com>	<018601c8b511$0a83a410$c3f0200a@cisco.com>	<2F594053-210D-49D	6-A9C7-5	245826854A1@gmail.com>	<04fe01c8b531$5c086c60$c3f0200a@cisco.com><	563A472D-30B9-45E9-8E2C-009CF1B4045F@magma.ca>
	<4834E78D.6000007@cisco.com> <48369C77.4000703@it.uc3m.es>
In-Reply-To: <48369C77.4000703@it.uc3m.es>
X-OriginalArrivalTime: 23 May 2008 21:46:59.0082 (UTC)
	FILETIME=[86F34EA0:01C8BD1E]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3955; t=1211579219;
	x=1212443219; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20[BEHAVE]=20Scalability=20of=20endpoint=
	20independent=20mapping |Sender:=20;
	bh=MQn7kPmdMPi6rKODJvbcxth0sfQH5A2ZayvVWWZY3LA=;
	b=fVuSuksPDIAbJvsjD+ItzCsesssvg+DrWzkOTgu0nRPpofmLbRa/FxWbl2
	En1GxLZxed2BHuT/esNtmpqL2V2ZzXUq2hJxj7xpelAK8NglJSlhcQrecNGT
	pVj7qj5AfT;
Authentication-Results: sj-dkim-2; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: Behave WG <behave@ietf.org>, Philip Matthews <philip_matthews@magma.ca>,
	Iljitsch van Beijnum <iljitsch@gmail.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

inline:

marcelo bagnulo braun wrote:
> Hi,

>>
>> Note that, I believe this model would allow for mapping rules to be 
>> defined which still work well for p2p apps but give you the benefits 
>> of address and port reuse across different sessions, without needing 
>> to define rules based on what application is being used.
>>
>>   
> I am not sure i understand how would that be.
> I mean, consider the following case (using your figure)
> In this case we are reusing the transport address X'1,x'1, as was 
> suggested, for both communications
> 
>                                              E
>           +------+                 +------+  x
>           |  Y1  |                 |  Y2  |  t
>           +--+---+                 +---+--+  e
>              | Y1:y1            Y2:y2  |     r
>              +----------+   +----------+     n
>                         |   |                a
>                 X1':x1' |   | X1':x1'        l
>                      +--+---+-+
>           ...........|   NAT  |...............
>                      +--+---+-+              I
>                         |   |                n
>                         |   |                t
>                         |   |                e
>                  +------+   +------+         r
>                  |                 |         n
>                  |x1               |x2       a
>               +-----+           +-----+      l
>               | X1  |           | X2  |
>               +-----+           +-----+
> 
> 
>        From internal to external:
> 
>        X1':x1' = f(X1:x1,Y1:y1)
>        X1':x1' = f(X2:x2,Y2:y2)
> 
> 
>        From external to internal:
> 
>        X1:x2 = f(Y1:y1,X1':x1')
>        X2:x2 = f(Y2:y2,X2':x2')
> 
> 
> So, now suppose that Y2:y2 wants to send packets toward X1,x1, how would 
> he do that?
> wouldn't that be a problem for p2p apps?
> I mean, if the goal of X1 was to create a mpping so it can later on 
> receive incoming communications through X'1,x'1, this would break that, 
> right?

Not if your NAT is also doing address and port restricted filtering.

So lets say, X1 sends to Y1. The NAT assigns the mapping (X1':x1',Y1:y1) 
-> X1:x1. Note that the mapping here now is from the full five tuple. So 
when Y1:y1 sends back, it gets passed to X1:x1. Of course, should Y2:y2 
send to X1':x1', there is no filter (and no mapping) so its dropped.

So now X2 sends to A1. Nat assigns the mapping (X1':x1',A1:a1) -> X2:x2. 
Note that the same external IP/port is assigned, but the mapping is for 
the full five-tuple which includes the target A1:a1.

Now X1 sends to a different host - Y2. The mapping (X1':x1',Y2:y2) is 
not currently assigned, so its assigned to X1:x1. Now, both a mapping 
and a filter are put into place. So now, Y2:y2 can send packets back to 
X1:x1. Note that, this looks EXACTLY like endpoint independent mapping, 
but we have shared the external IP/port across different internal hosts! 
The mapping can be shared and you can have behavior that appears like 
endpoint independent mapping, so long as there is no overlap in the 
TARGET addresses reached by each internal host. Remember, in this model 
of NAT, the peer IP and port is part of the index used to define the 
mapping.

It is true that you cannot guarantee mappings that are endpoint 
independent, but it can be made probabilistic with arbitrarily high 
confidence by trading off mapping reuse. That works extremely well with 
stuff like ICE which don't make assumptions and just work better as the 
percentage of endpoint independent natting increases.

-Jonathan R.


-- 
Jonathan D. Rosenberg, Ph.D.                   499 Thornall St.
Cisco Fellow                                   Edison, NJ 08837
Cisco, Voice Technology Group
jdrosen@cisco.com
http://www.jdrosen.net                         PHONE: (408) 902-3084
http://www.cisco.com
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 14:55:24 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2AE003A6D00;
	Fri, 23 May 2008 14:55:24 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6BA713A6D14
	for <behave@core3.amsl.com>; Fri, 23 May 2008 14:55:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.432
X-Spam-Level: 
X-Spam-Status: No, score=-0.432 tagged_above=-999 required=5
	tests=[AWL=-4.190, BAYES_00=-2.599, FB_REM_PART=10.357,
	RCVD_IN_DNSWL_MED=-4]
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 wL3zlEzVuCeo for <behave@core3.amsl.com>;
	Fri, 23 May 2008 14:55:22 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 654173A6D00
	for <behave@ietf.org>; Fri, 23 May 2008 14:55:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,532,1204531200"; d="scan'208";a="103222176"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 23 May 2008 14:55:21 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4NLtLKg015152; 
	Fri, 23 May 2008 14:55:21 -0700
Received: from dwingwxp01 ([10.21.71.57])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m4NLtLPB016602;
	Fri, 23 May 2008 21:55:21 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Bruce Lowekamp'" <lowekamp@sipeerior.com>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A		570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>	<DF	3	5AA43-736F-454A-A471-123DBE79274D@nokia.com><09c701c8bc37$83bb4310$1496150a@cisco.com><4836DEE5.4070901@sipeerior.com>
	<4836F52D.7030809@it.uc3m.es> <48370975.8040307@sipeerior.com>
	<0af801c8bd09$860355e0$d8e9520a@cisco.com>
	<4837381E.4040205@sipeerior.com>
Date: Fri, 23 May 2008 11:55:14 -1000
Message-ID: <004701c8bd1f$b08ebf00$3947150a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <4837381E.4040205@sipeerior.com>
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Aci9HKoQJVxOXRjVR7iXYycdlBo/CQAAaCrQ
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5876; t=1211579721;
	x=1212443721; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Dynamic=20Port=20Reuse
	|Sender:=20; bh=ouTeNAbSqLoutDjlJmRs2FXB7UiM4pgerSiZVA2G7Ng=;
	b=aw44tFhF4DneONT5+TvfMpLnivMPoURcq+2izvc7awdceLW0X69HTTFoPZ
	zfPJG9cE8zWOfkiPl0Hot143o+MOugCwyRu/NjBr34nEmkldw4q5PjhzjVOU
	3cXzUKUMC4YT0W8s8KoJpzPpEtx1LcR7a+InKN8H3Ud2gt5bHLQ+0=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

 

> -----Original Message-----
> From: Bruce Lowekamp [mailto:lowekamp@sipeerior.com] 
> Sent: Friday, May 23, 2008 11:33 AM
> To: Dan Wing
> Cc: 'marcelo bagnulo braun'; behave@ietf.org
> Subject: Re: [BEHAVE] Dynamic Port Reuse
> 
> Dan Wing wrote:
> >>>> Maybe the right way to combine these is to view the timer as a 
> >>>> fallback condition.  So here's a new proposal:
> >>>>
> >>>>
> >>>> An address-port sparing NAT MAY use endpoint dependent 
> mapping for 
> >>>> connections whose destination port specifies a known-compatible 
> >>>> protocol (HTTP, SMTP, etc).  Otherwise, it MUST default to 
> >>>> endpoint-independent mapping characteristics.  In the event of 
> >>>> overload, where it is no longer able to preserve endpoint 
> >> independent 
> >>>> mapping for new connections, the NAT MAY apply the timer 
> >> algorithm to 
> >>>> prioritize which connections receive endpoint-dependent mapping.
> >>>>   
> >>>
> >>> I really don't like the last part. Essentially this would 
> >> result in non 
> >>> deterministic behaviour, since a nat could be endpoint 
> >> independet or 
> >>> endpoint dependent depending on the load and i think we 
> >> must avoid that
> >>> I would simply keep the first two parts and remov the last one
> >> Well, OK.  I don't really like the behavior much either and 
> >> would prefer 
> >>    to mandate endpoint-independent mapping all the time for 
> >> all ports. 
> >>   But removing the third part just leaves the behavior in the 
> >> event of 
> >> overload undefined.  That's not clearly better than specifying a 
> >> not-too-terribly-evil thing to do in an overload scenario, is it?
> > 
> > Using port numbers is, itself, non-deterministic.  This is because
> > no two people will generate the same list ports that are safe to
> > re-use.  If ports are used, then in 3 years, as NAT64 vendors find
> > value in optimizing re-use of other port numbers, the vendors will
> > begin diverging which ports are re-used.
> > 
> > For example, here would be my list of ports that are safe to re-use:
> > TCP/80 (HTTP), TCP/110 (POP3), TCP/995 (POP3S), TCP/143 
> (IMAP), TCP/587
> > (SUBMIT), TCP/25 (SMTP), TCP/22 (SSH), TCP/21 (FTP), TCP/23 
> (TELNET),
> > TCP/7 (ECHO), TCP/9 (DISCARD), TCP/993 (IMAPS).
> > 
> > Are there non-IETF protocols that are used which would break with
> > port re-use?  That is, that use UNSAF or use TCP S-O?
> > 
> > 
> > As BitTorrent has not registered their ports with IANA, I'm not sure
> > what could be said in an IETF document about its ports other than 
> > some non-normative "and other ports that the NAT64 believes, to the
> > best of its knowledge, are used by client/server applications that
> > can safely have their TCP source ports re-used."  Which brings us
> > to specify non-deterministic behavior for such a NAT64.
> 
> So does that leave anything other than telling the people 
> interested in NAT64 scalability that the NATs need to be big 
> enough to not suffer from port overload?  I disbelieve that it's 
> ever going to be possible to do such a thing (one misbehaving 
> application can consume an awful lot of ports). 

Yes, of course the NAT needs to protect itself from such intential
or unintentional abuse.  As I said in another post (which is not
yet archived),

  > Yes, an ISP's NAT will certainly have to limit how many 
  > ports they allocate to any particular subscriber.  Even low-end 
  > home NATs do this today (for all hosts behind the NAT) so they 
  > don't consume all of their memory with connection tables.

> I don't know 
> whether I believe BEHAVE can have an impact on how 
> vendors develop such a device, but it seems like specifying 
> BCP that are 
> more likely to not break the world than other behaviors is 
> useful from an engineering point of view.

The IETF's view of IPv4 NATs has historically been see-no-evil, 
hear-no-evil, speak-no-evil:  there were no specifications and
thus the "desert bloomed" with literally dozens of different
NAT styles, NAT traversal mechanisms (ALGs and no ALGs, FTP PASV,
etc.), with no overall thought or plan to how it would work in
the end other than allowing the market to sort it out.

We have an opportunity to create a specification for NAT64 and
get out of this rut.

> I agree that creating a lengthy list is probably an unending 
> task.  (I 
> would argue against including bittorrent in there.)  But I 
> think there 
> is a core of widely distributed applications that probably 99% of the 
> people in the room would agree with.  Even if that list is only HTTP, 
> SMTP, POP, SSH, and IMAP, it will help here.  It will 
> probably needed to 
> be updated every n years to keep it current (or IPv6 will be 
> universally 
> deployed and the list can be allowed to rus).

Yes, we may well be successful in identifying some set of ports for
client/server applications.  

But are we sure there are no UNSAF applications or applications
that need TCP S-O which run on TCP/80?  Many applications do attempt
to run on TCP/80 in an effort to work through enterprise firewalls that 
only allow TCP/80 -- Cisco and other vendors have deployed IDS and
firewalls that inspect TCP/80 traffic in an effort to block such non-HTTP
applications.

> I wasn't trying to make the argument that using port numbers was 
> deterministic, only that leaving overload behavior entirely 
> unspecified 
> seems likely to produce the kind of variety of broken behavior that 
> motivated BEHAVE to be formed in the first place.  If the timer 
> algorithm helps to allow a NAT to avoid imposing endpoint dependent 
> mapping on EVERY application when it experiences high load, 
> that's not 
> too bad of a result.  That level of load IS going to happen.

-d

> Bruce
> 

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 15:00:40 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 277A828C323;
	Fri, 23 May 2008 15:00:40 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8087528C324
	for <behave@core3.amsl.com>; Fri, 23 May 2008 15:00:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.012
X-Spam-Level: 
X-Spam-Status: No, score=-5.012 tagged_above=-999 required=5 tests=[AWL=1.587, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 kvClQgwvtIS0 for <behave@core3.amsl.com>;
	Fri, 23 May 2008 15:00:37 -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 7E16728C323
	for <behave@ietf.org>; Fri, 23 May 2008 15:00:37 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,532,1204531200"; d="scan'208";a="49927022"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-2.cisco.com with ESMTP; 23 May 2008 15:00:37 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m4NM0aW6021235; 
	Fri, 23 May 2008 15:00:36 -0700
Received: from dwingwxp01 ([10.21.71.57])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m4NM0aAD021035;
	Fri, 23 May 2008 22:00:36 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Jonathan Rosenberg'" <jdrosen@cisco.com>,
	"'marcelo bagnulo braun'" <marcelo@it.uc3m.es>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d		74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.11	4	41.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es><48286CFD.	10	80204@free.fr>	<48287AE5.5010005@sipeerior.com><482882B7.2030806@free.fr	><1	45B7DFA-E397-4184-8FA6-3C255078509F@muada.com><48289C15.3000102@free.fr	>	<4	828A33E.1080700@sipeerior.com><4828ABBE.9010201@free.fr>	<4828AE1B.904	0901@	sipeerior.com>	<03C87756-203A-496A-A348-1D0FE15F60F6@gmail.com>	<0158	01c8b5	0d$984b8eb0$c3f0200a@cisco.com>	<8EFD78D3-46EC-4BA5-9F9A-B6F471B9C01	F@gmail	.com>	<018601c8b511$0a83a410$c3f0200a@cisco.com>	<2F594053-210D-49D	6-A9C7-5	245826854A1@gmail.com>	<04fe01c8b531$5c086c60$c3f0200a@cisco.com><	563A472D-30B9-45E9-8E2C-009CF1B4045F@magma.ca><4834E78D.6000007@cisco.com>
	<48369C77.4000703@it.uc3m.es> <48373B5B.3040306@cisco.com>
Date: Fri, 23 May 2008 12:00:32 -1000
Message-ID: <004b01c8bd20$6c519c30$3947150a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <48373B5B.3040306@cisco.com>
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Aci9HplhmyGkaz0UQoGSZ4x+lBkzFQAAb5ng
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4764; t=1211580036;
	x=1212444036; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Scalability=20of=20endpoint=
	20independent=20mapping |Sender:=20;
	bh=gq0fSstjZxUJBRPB+alQkvtJqhQVKCrT5uWxoNBV34w=;
	b=DKxM554/Yn89vyxZwgPdLVJFn6vIniDCvUs/2b5avrtKulUbF2oK/zy3WT
	SZ73y1dFOEy13xd9dlZgn5SnxrL2lWHbq72+M0UGOdCMF90K+XZP1OqyNIrd
	mHV1vb4FLm;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: 'Behave WG' <behave@ietf.org>, 'Philip Matthews' <philip_matthews@magma.ca>,
	'Iljitsch van Beijnum' <iljitsch@gmail.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

 

> -----Original Message-----
> From: behave-bounces@ietf.org 
> [mailto:behave-bounces@ietf.org] On Behalf Of Jonathan Rosenberg
> Sent: Friday, May 23, 2008 11:47 AM
> To: marcelo bagnulo braun
> Cc: Behave WG; Philip Matthews; Iljitsch van Beijnum
> Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
> 
> inline:
> 
> marcelo bagnulo braun wrote:
> > Hi,
> 
> >>
> >> Note that, I believe this model would allow for mapping 
> rules to be 
> >> defined which still work well for p2p apps but give you 
> the benefits 
> >> of address and port reuse across different sessions, 
> without needing 
> >> to define rules based on what application is being used.
> >>
> >>   
> > I am not sure i understand how would that be.
> > I mean, consider the following case (using your figure)
> > In this case we are reusing the transport address X'1,x'1, as was 
> > suggested, for both communications
> > 
> >                                              E
> >           +------+                 +------+  x
> >           |  Y1  |                 |  Y2  |  t
> >           +--+---+                 +---+--+  e
> >              | Y1:y1            Y2:y2  |     r
> >              +----------+   +----------+     n
> >                         |   |                a
> >                 X1':x1' |   | X1':x1'        l
> >                      +--+---+-+
> >           ...........|   NAT  |...............
> >                      +--+---+-+              I
> >                         |   |                n
> >                         |   |                t
> >                         |   |                e
> >                  +------+   +------+         r
> >                  |                 |         n
> >                  |x1               |x2       a
> >               +-----+           +-----+      l
> >               | X1  |           | X2  |
> >               +-----+           +-----+
> > 
> > 
> >        From internal to external:
> > 
> >        X1':x1' = f(X1:x1,Y1:y1)
> >        X1':x1' = f(X2:x2,Y2:y2)
> > 
> > 
> >        From external to internal:
> > 
> >        X1:x2 = f(Y1:y1,X1':x1')
> >        X2:x2 = f(Y2:y2,X2':x2')
> > 
> > 
> > So, now suppose that Y2:y2 wants to send packets toward 
> X1,x1, how would 
> > he do that?
> > wouldn't that be a problem for p2p apps?
> > I mean, if the goal of X1 was to create a mpping so it can later on 
> > receive incoming communications through X'1,x'1, this would 
> break that, 
> > right?
> 
> Not if your NAT is also doing address and port restricted filtering.
> 
> So lets say, X1 sends to Y1. The NAT assigns the mapping 
> (X1':x1',Y1:y1) 
> -> X1:x1. Note that the mapping here now is from the full 
> five tuple. So 
> when Y1:y1 sends back, it gets passed to X1:x1. Of course, 
> should Y2:y2 
> send to X1':x1', there is no filter (and no mapping) so its dropped.
> 
> So now X2 sends to A1. Nat assigns the mapping 
> (X1':x1',A1:a1) -> X2:x2. 
> Note that the same external IP/port is assigned, but the 
> mapping is for 
> the full five-tuple which includes the target A1:a1.
> 
> Now X1 sends to a different host - Y2. The mapping (X1':x1',Y2:y2) is 
> not currently assigned, so its assigned to X1:x1. Now, both a mapping 
> and a filter are put into place. So now, Y2:y2 can send 
> packets back to 
> X1:x1. Note that, this looks EXACTLY like endpoint 
> independent mapping, 
> but we have shared the external IP/port across different 
> internal hosts! 
> The mapping can be shared and you can have behavior that appears like 
> endpoint independent mapping, so long as there is no overlap in the 
> TARGET addresses reached by each internal host. Remember, in 
> this model 
> of NAT, the peer IP and port is part of the index used to define the 
> mapping.

You described ALGO-1 from draft-wing-behave-dynamic-tcp-port-reuse-00.

-d

> It is true that you cannot guarantee mappings that are endpoint 
> independent, but it can be made probabilistic with arbitrarily high 
> confidence by trading off mapping reuse. That works extremely 
> well with 
> stuff like ICE which don't make assumptions and just work 
> better as the 
> percentage of endpoint independent natting increases.
> 
> -Jonathan R.
> 
> 
> -- 
> Jonathan D. Rosenberg, Ph.D.                   499 Thornall St.
> Cisco Fellow                                   Edison, NJ 08837
> Cisco, Voice Technology Group
> jdrosen@cisco.com
> http://www.jdrosen.net                         PHONE: (408) 902-3084
> http://www.cisco.com
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri May 23 15:03:46 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B42AC28C323;
	Fri, 23 May 2008 15:03:46 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 603FC28C31D
	for <behave@core3.amsl.com>; Fri, 23 May 2008 15:03:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.061
X-Spam-Level: 
X-Spam-Status: No, score=-5.061 tagged_above=-999 required=5 tests=[AWL=1.238, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 IEgDD740QtP9 for <behave@core3.amsl.com>;
	Fri, 23 May 2008 15:03:41 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 22D9228C325
	for <behave@ietf.org>; Fri, 23 May 2008 15:03:37 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,532,1204531200"; d="scan'208";a="71872248"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 23 May 2008 15:03:36 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m4NM3aYa026289; 
	Fri, 23 May 2008 15:03:36 -0700
Received: from dwingwxp01 ([10.21.71.57])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4NM3ZJJ011575;
	Fri, 23 May 2008 22:03:36 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "=?iso-8859-1?Q?'R=E9mi_Despr=E9s'?=" <remi.despres@free.fr>,
	"=?iso-8859-1?Q?'R=E9mi_Denis-Courmont'?=" <remi.denis-courmont@nokia.com>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com><200805230955.37501.remi.denis-courmont@nokia.com>
	<48367DB0.5010902@free.fr>
Date: Fri, 23 May 2008 12:03:31 -1000
Message-ID: <004c01c8bd20$d73c3730$3947150a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <48367DB0.5010902@free.fr>
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Aci8rXxA78qs4yyiRN6CG/IGeFFzbAAczx0Q
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=361; t=1211580216; x=1212444216;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Dynamic=20Port=20Reuse
	|Sender:=20; bh=LMYuK8QgOHGV+5DaauAChLs6E2y7bF3WkOXbtxg2HTg=;
	b=rRWUJcVM5ACt46E6zTJ6bR4RFoymBcrF8At/yy7EsJFtJOBo+VF9i/pnBA
	oD4umIehPJ9QRqpEWwPar+KsPUq9G4i/IdIlevT6iegbmP5GDmsKjam2fp/L
	6BLSMJZR7p;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

> > In any case, ALGO-1 breaks TCP-SO. I think the real issue 
> > is, whether 
> > TCP-SO/IPv4 really matters.... It would seem so unreliable 
> > that people will end up using UDP.
>
> Is there a reference where the the nature and the scope of 
> the alleged TCP-SO problem is identified?

See http://saikat.guha.cc/paper.php?id=imc05-guha:tcp

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sat May 24 03:46:26 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0D8C23A69DF;
	Sat, 24 May 2008 03:46:26 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4D1073A69DF
	for <behave@core3.amsl.com>; Sat, 24 May 2008 03:46:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.43
X-Spam-Level: 
X-Spam-Status: No, score=-2.43 tagged_above=-999 required=5 tests=[AWL=1.332, 
	BAYES_00=-2.599, RCVD_BAD_ID=2.837, RCVD_IN_DNSWL_MED=-4]
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 zQ5oqHUqXVtX for <behave@core3.amsl.com>;
	Sat, 24 May 2008 03:46:23 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133])
	by core3.amsl.com (Postfix) with ESMTP id 04B003A69C7
	for <behave@ietf.org>; Sat, 24 May 2008 03:46:21 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (unknown 
	[163.117.203.43])by smtp03.uc3m.es (Postfix) with ESMTP id 6703A3C84AE;
	Sat, 24 May 2008 12:46:11 +0200 (CEST)
Message-ID: <4837EF3A.2050705@it.uc3m.es>
Date: Sat, 24 May 2008 12:34:34 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@cisco.com>
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>	<000201c8b3b0$d
	74ccdd0$c3f0200a@cisco.com>	<4827FA33.8020201@it.uc3m.es>	<200805121249.
	1	1	4	41.remi.denis-courmont@nokia.com>	<48281927.4020708@it.uc3m.es><48286
	CF	D.	10	80204@free.fr>	<48287AE5.5010005@sipeerior.com><482882B7.2030806@f
	ree	.fr	><1	45B7DFA-E397-4184-8FA6-3C255078509F@muada.com><48289C15.3000102
	@fre	e.fr	>	<4	828A33E.1080700@sipeerior.com><4828ABBE.9010201@free.fr>	<48
	28AE1	B.904	0901@	sipeerior.com>	<03C87756-203A-496A-A348-1D0FE15F60F6@gmai
	l.com>		<0158	01c8b5	0d$984b8eb0$c3f0200a@cisco.com>	<8EFD78D3-46EC-4BA5-9F
	9A-B6F4	71B9C01	F@gmail	.com>	<018601c8b511$0a83a410$c3f0200a@cisco.com>	<2
	F594053-	210D-49D	6-A9C7-5	245826854A1@gmail.com>	<04fe01c8b531$5c086c60$c3
	f0200a@ci	sco.com><	563A472D-30B9-45E9-8E2C-009CF1B4045F@magma.ca> 
	<4834E78D.6000007@cisco.com> <48369C77.4000703@it.uc3m.es> 
	<48373B5B.3040306@cisco.com>
In-Reply-To: <48373B5B.3040306@cisco.com>
X-imss-version: 2.050
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-18.2382 TC:1F TRN:52 TV:5.5.1026(15928.006)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: Behave WG <behave@ietf.org>, Philip Matthews <philip_matthews@magma.ca>,
	Iljitsch van Beijnum <iljitsch@gmail.com>
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Jonathan Rosenberg escribi=F3:
> inline:
>
> marcelo bagnulo braun wrote:
>> Hi,
>
>>>
>>> Note that, I believe this model would allow for mapping rules to be =

>>> defined which still work well for p2p apps but give you the benefits =

>>> of address and port reuse across different sessions, without needing =

>>> to define rules based on what application is being used.
>>>
>>>   =

>> I am not sure i understand how would that be.
>> I mean, consider the following case (using your figure)
>> In this case we are reusing the transport address X'1,x'1, as was =

>> suggested, for both communications
>>
>>                                              E
>>           +------+                 +------+  x
>>           |  Y1  |                 |  Y2  |  t
>>           +--+---+                 +---+--+  e
>>              | Y1:y1            Y2:y2  |     r
>>              +----------+   +----------+     n
>>                         |   |                a
>>                 X1':x1' |   | X1':x1'        l
>>                      +--+---+-+
>>           ...........|   NAT  |...............
>>                      +--+---+-+              I
>>                         |   |                n
>>                         |   |                t
>>                         |   |                e
>>                  +------+   +------+         r
>>                  |                 |         n
>>                  |x1               |x2       a
>>               +-----+           +-----+      l
>>               | X1  |           | X2  |
>>               +-----+           +-----+
>>
>>
>>        From internal to external:
>>
>>        X1':x1' =3D f(X1:x1,Y1:y1)
>>        X1':x1' =3D f(X2:x2,Y2:y2)
>>
>>
>>        From external to internal:
>>
>>        X1:x2 =3D f(Y1:y1,X1':x1')
>>        X2:x2 =3D f(Y2:y2,X2':x2')
>>
>>
>> So, now suppose that Y2:y2 wants to send packets toward X1,x1, how =

>> would he do that?
>> wouldn't that be a problem for p2p apps?
>> I mean, if the goal of X1 was to create a mpping so it can later on =

>> receive incoming communications through X'1,x'1, this would break =

>> that, right?
>
> Not if your NAT is also doing address and port restricted filtering.

but this is NOT recommended according to the behave requirements, right?
I mean, endpoint independent filters are recommended and if more =

stringent filtering is needed, then address dependent filtering is =

recommended, but never address and port dependent filtering, right?
>
> So lets say, X1 sends to Y1. The NAT assigns the mapping =

> (X1':x1',Y1:y1) -> X1:x1. Note that the mapping here now is from the =

> full five tuple. So when Y1:y1 sends back, it gets passed to X1:x1. Of =

> course, should Y2:y2 send to X1':x1', there is no filter (and no =

> mapping) so its dropped.
>
> So now X2 sends to A1. Nat assigns the mapping (X1':x1',A1:a1) -> =

> X2:x2. Note that the same external IP/port is assigned, but the =

> mapping is for the full five-tuple which includes the target A1:a1.
>
> Now X1 sends to a different host - Y2. The mapping (X1':x1',Y2:y2) is =

> not currently assigned, so its assigned to X1:x1. Now, both a mapping =

> and a filter are put into place. So now, Y2:y2 can send packets back =

> to X1:x1. Note that, this looks EXACTLY like endpoint independent =

> mapping, but we have shared the external IP/port across different =

> internal hosts! =

> The mapping can be shared and you can have behavior that appears like =

> endpoint independent mapping, so long as there is no overlap in the =

> TARGET addresses reached by each internal host. =


right, but having the same target host doesn't seems to be a rare =

situation... imagine the target is google.com at port 80

So with this scheme, you can achieve something similar to endpoint =

indepednet mapping with address and port filtering as long as the target =

transport addresses don't collide.

My concerns are:
- target addresses are very likely to collide
- address and port filtering is not recommended by behave requirements =

and both recommended behaviours, i.e. endpoint independent filtering and =

address dependent filtering cannot be achieved

am i missing something?


> Remember, in this model of NAT, the peer IP and port is part of the =

> index used to define the mapping.
>
> It is true that you cannot guarantee mappings that are endpoint =

> independent, but it can be made probabilistic with arbitrarily high =

> confidence by trading off mapping reuse. =


that i don't understand... what do you mean that you can make it =

probabilistic with arbitrarily high confidence? You mean that you assume =

a uniform distribution of the target transport addresses?



> That works extremely well with stuff like ICE which don't make =

> assumptions and just work better as the percentage of endpoint =

> independent natting increases.
>
right, but as i see it, there are two different efforts being done in =

the nat world. One is to have tools like ICE which work no matter how =

bad is the nat behaviour and the other one is to try to get nats to =

behave in a reasonable way.

I understand that this discussion belongs to th first kind of effort, =

where we try to make nats behave reasonably

Regards, marcelo

> -Jonathan R.
>
>


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sat May 24 03:46:38 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 375C83A6A0B;
	Sat, 24 May 2008 03:46:38 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D5C473A69C7
	for <behave@core3.amsl.com>; Sat, 24 May 2008 03:46:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.482
X-Spam-Level: **
X-Spam-Status: No, score=2.482 tagged_above=-999 required=5 tests=[AWL=-4.113, 
	BAYES_00=-2.599, FB_REM_PART=10.357, RCVD_BAD_ID=2.837,
	RCVD_IN_DNSWL_MED=-4]
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 ULq+3z0rJQF3 for <behave@core3.amsl.com>;
	Sat, 24 May 2008 03:46:32 -0700 (PDT)
Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.176.132])
	by core3.amsl.com (Postfix) with ESMTP id 5C9033A6AC0
	for <behave@ietf.org>; Sat, 24 May 2008 03:46:32 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (unknown 
	[163.117.203.43])by smtp02.uc3m.es (Postfix) with ESMTP id 0F7CC39D169;
	Sat, 24 May 2008 12:46:25 +0200 (CEST)
Message-ID: <4837F171.7030001@it.uc3m.es>
Date: Sat, 24 May 2008 12:44:01 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Bruce Lowekamp <lowekamp@sipeerior.com>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A
	570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>	<
	D	F	3	5AA43-736F-454A-A471-123DBE79274D@nokia.com><09c701c8bc37$83bb4310$14
	96	150a@cisco.com> <4836DEE5.4070901@sipeerior.com> 
	<4836F52D.7030809@it.uc3m.es> <48370975.8040307@sipeerior.com>
In-Reply-To: <48370975.8040307@sipeerior.com>
X-imss-version: 2.050
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-16.3785 TC:1F TRN:23 TV:5.5.1026(15928.006)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: behave@ietf.org, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Bruce Lowekamp escribi=F3:
>
>>>
>>>
>>> An address-port sparing NAT MAY use endpoint dependent mapping for =

>>> connections whose destination port specifies a known-compatible =

>>> protocol (HTTP, SMTP, etc).  Otherwise, it MUST default to =

>>> endpoint-independent mapping characteristics.  In the event of =

>>> overload, where it is no longer able to preserve endpoint =

>>> independent mapping for new connections, the NAT MAY apply the timer =

>>> algorithm to prioritize which connections receive endpoint-dependent =

>>> mapping.
>>>   =

>>
>>
>> I really don't like the last part. Essentially this would result in =

>> non deterministic behaviour, since a nat could be endpoint independet =

>> or endpoint dependent depending on the load and i think we must avoid =

>> that
>>
>> I would simply keep the first two parts and remov the last one
>
> Well, OK.  I don't really like the behavior much either and would =

> prefer   to mandate endpoint-independent mapping all the time for all =

> ports.  But removing the third part just leaves the behavior in the =

> event of overload undefined.  That's not clearly better than =

> specifying a not-too-terribly-evil thing to do in an overload =

> scenario, is it?

For me in case of overloading, packets are discarded and an error
message is sent back to the sender.

I mean, i rather that things fail deterministically rather than work in
an unpredictable way

regards, marcelo




_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sat May 24 03:46:48 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 66DE03A69C7;
	Sat, 24 May 2008 03:46:48 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1D5653A69C7
	for <behave@core3.amsl.com>; Sat, 24 May 2008 03:46:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[AWL=1.751, 
	BAYES_00=-2.599, RCVD_BAD_ID=2.837, RCVD_IN_DNSWL_MED=-4]
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 XEi3ppPSQLSx for <behave@core3.amsl.com>;
	Sat, 24 May 2008 03:46:46 -0700 (PDT)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131])
	by core3.amsl.com (Postfix) with ESMTP id A901928C0D6
	for <behave@ietf.org>; Sat, 24 May 2008 03:46:45 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (unknown 
	[163.117.203.43])by smtp01.uc3m.es (Postfix) with ESMTP id 59A33639863;
	Sat, 24 May 2008 12:46:36 +0200 (CEST)
Message-ID: <4837F17D.8040304@it.uc3m.es>
Date: Sat, 24 May 2008 12:44:13 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A
	570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com><DF3
	5	AA43-736F-454A-A471-123DBE79274D@nokia.com><4835984F.6080504@free.fr><F53
	56B94-213A-486F-9A93-7BDBB0D0BC51@nokia.com> 
	<0c9e01c8bd1b$cab0f320$d8e9520a@cisco.com>
In-Reply-To: <0c9e01c8bd1b$cab0f320$d8e9520a@cisco.com>
X-imss-version: 2.050
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-13.4265 TC:1F TRN:52 TV:5.5.1026(15928.006)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] need for port re-use [was Re:  Dynamic Port Reuse]
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Dan Wing escribi=F3:
>> Both current proposals have advantages and disadvantages, and the  =

>> tradeoffs need to be understood. I'm not a particular fan of using  =

>> either ports or timers - both are crufty - because I'm still  =

>> unconvinced that we actually need to solve this problem in the first  =

>> place. Anyone got data about how often NATs run out of =

>> binding entries  =

>> in situations where another IPv4 address isn't available?
>>     =

>
> For whatever it's worth:
>
> Some University of Colorado researchers filled up their NAT's binding tab=
le,
> unbeknownst to them: =

> http://systems.cs.colorado.edu/mediawiki/index.php/Broadband_Network_Mana=
gemen
> t
>
> And I have done the same with my home NAT when using FTP to mirror the
> Internet-Drafts archive (the separate FTP data connections consumed all o=
f my
> NAT's binding table entries).  My home NAT (a Linksys WRT54G with 3rd par=
ty
> firmware) is configured to remember about 1000 UDP and TCP bindings.
>
>
> The difference is that with NAT64, it isn't just yourself you would harm =
by
> consuming all of the TCP ports on the NAT -- it is everyone else using th=
at
> NAT64 who cannot, now, obtain another TCP port.  The reason for NAT64 is =
to
> avoid giving every subscriber their own IPv4 address and to get multiple
> subscribers NATted to one IP address.  As Iljitsch described in the middl=
e of
> http://www.ietf.org/mail-archive/web/behave/current/msg03821.html, some
> commonly-deployed applications and commonly-accessed Web 2.0 sites cause =
a lot
> of TCP connections to be created, which reduces the number of subscribers=
 an
> ISP could expect to place behind a single IPv4 address.
>
>   =


right, but you can deal with this, if you have more public IPv4 addresses.

The problem will be critical when we run out of v4 addresses

the question is whether we should deal with this problem now or wait
till later (when we run out of v4 addresses and there is no clear uptake
of the v6 protocol and we are really into deep trouble)

Regards, marcelo



> -d
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
>   =




_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sat May 24 03:46:59 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9F73E3A69F2;
	Sat, 24 May 2008 03:46:59 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AED6028C0F2
	for <behave@core3.amsl.com>; Sat, 24 May 2008 03:46:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.917
X-Spam-Level: **
X-Spam-Status: No, score=2.917 tagged_above=-999 required=5 tests=[AWL=-3.677, 
	BAYES_00=-2.599, FB_REM_PART=10.357, RCVD_BAD_ID=2.837,
	RCVD_IN_DNSWL_MED=-4]
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 sEKYWBEKEbUh for <behave@core3.amsl.com>;
	Sat, 24 May 2008 03:46:57 -0700 (PDT)
Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.176.132])
	by core3.amsl.com (Postfix) with ESMTP id 8710428C0E2
	for <behave@ietf.org>; Sat, 24 May 2008 03:46:57 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (unknown 
	[163.117.203.43])by smtp02.uc3m.es (Postfix) with ESMTP id 890E939D15C;
	Sat, 24 May 2008 12:46:48 +0200 (CEST)
Message-ID: <4837F199.6040909@it.uc3m.es>
Date: Sat, 24 May 2008 12:44:41 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A
	570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>	<
	D	F	3	5AA43-736F-454A-A471-123DBE79274D@nokia.com><09c701c8bc37$83bb4310$14
	96	150a@cisco.com><4836DEE5.4070901@sipeerior.com> 
	<4836F52D.7030809@it.uc3m.es> <48370975.8040307@sipeerior.com> 
	<0af801c8bd09$860355e0$d8e9520a@cisco.com>
In-Reply-To: <0af801c8bd09$860355e0$d8e9520a@cisco.com>
X-imss-version: 2.050
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-16.2835 TC:1F TRN:40 TV:5.5.1026(15928.006)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Dan Wing escribi=F3:
>>>> Maybe the right way to combine these is to view the timer as a =

>>>> fallback condition.  So here's a new proposal:
>>>>
>>>>
>>>> An address-port sparing NAT MAY use endpoint dependent mapping for =

>>>> connections whose destination port specifies a known-compatible =

>>>> protocol (HTTP, SMTP, etc).  Otherwise, it MUST default to =

>>>> endpoint-independent mapping characteristics.  In the event of =

>>>> overload, where it is no longer able to preserve endpoint =

>>>>         =

>> independent =

>>     =

>>>> mapping for new connections, the NAT MAY apply the timer =

>>>>         =

>> algorithm to =

>>     =

>>>> prioritize which connections receive endpoint-dependent mapping.
>>>>   =

>>>>         =

>>> I really don't like the last part. Essentially this would =

>>>       =

>> result in non =

>>     =

>>> deterministic behaviour, since a nat could be endpoint =

>>>       =

>> independet or =

>>     =

>>> endpoint dependent depending on the load and i think we =

>>>       =

>> must avoid that
>>     =

>>> I would simply keep the first two parts and remov the last one
>>>       =

>> Well, OK.  I don't really like the behavior much either and =

>> would prefer =

>>    to mandate endpoint-independent mapping all the time for =

>> all ports. =

>>   But removing the third part just leaves the behavior in the =

>> event of =

>> overload undefined.  That's not clearly better than specifying a =

>> not-too-terribly-evil thing to do in an overload scenario, is it?
>>     =

>
> Using port numbers is, itself, non-deterministic.  This is because
> no two people will generate the same list ports that are safe to
> re-use.  If ports are used, then in 3 years, as NAT64 vendors find
> value in optimizing re-use of other port numbers, the vendors will
> begin diverging which ports are re-used.
>
>   =


but this goes beyond what we can do i guess

i mean, all what the ietf can do is to produce a spec. If people don't
follow the spec, then we are out of luck.

Having a list like the one you mention below in a RFC would result in
deterministic behaviour, if people implement it as specified.

I do agree that it is not very attractive to open that door cause it
would tempt implementers to do it for other ports

In general i think that all options for port reuse are bad cause the
reduce flexibility assuming some form of application behaviour.

Regards, marcelo

> For example, here would be my list of ports that are safe to re-use:
> TCP/80 (HTTP), TCP/110 (POP3), TCP/995 (POP3S), TCP/143 (IMAP), TCP/587
> (SUBMIT), TCP/25 (SMTP), TCP/22 (SSH), TCP/21 (FTP), TCP/23 (TELNET),
> TCP/7 (ECHO), TCP/9 (DISCARD), TCP/993 (IMAPS).
>
> Are there non-IETF protocols that are used which would break with
> port re-use?  That is, that use UNSAF or use TCP S-O?
>
>
> As BitTorrent has not registered their ports with IANA, I'm not sure
> what could be said in an IETF document about its ports other than =

> some non-normative "and other ports that the NAT64 believes, to the
> best of its knowledge, are used by client/server applications that
> can safely have their TCP source ports re-used."  Which brings us
> to specify non-deterministic behavior for such a NAT64.
>
> -d
>
>
>   =




_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sat May 24 07:40:51 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 635F43A68EB;
	Sat, 24 May 2008 07:40:51 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 916B13A68EB
	for <behave@core3.amsl.com>; Sat, 24 May 2008 07:40:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
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 NJRwk9c-6qFr for <behave@core3.amsl.com>;
	Sat, 24 May 2008 07:40:49 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id D5BDC3A68A7
	for <behave@ietf.org>; Sat, 24 May 2008 07:40:48 -0700 (PDT)
Received: from [192.168.2.13] (static-167-138-7-89.ipcom.comunitel.net
	[89.7.138.167] (may be forged)) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m4OEeFHP005243
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Sat, 24 May 2008 16:40:30 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <E9485E99-1E7A-486A-AC5C-A1F26319731B@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Sat, 24 May 2008 16:40:23 +0200
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>
	<2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>
	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>
	<DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
X-Mailer: Apple Mail (2.919.2)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 22 mei 2008, at 16:58, Lars Eggert wrote:

>> And the primary motivation for me to write this up was v4 address
>> conservation on the NAT64 box.

> Understood, but are we really _that_ stressed for v4 space yet?

In a word: yes.

The IETF process is such that it's unrealistic to expect to go from  
initial discussion through rough consensus to RFC publication in less  
than two years. Then the vendors need some time to implement the RFC  
and the operators to deploy the new hard/software.

According to http://www.potaroo.net/tools/ipv4/ we are scheduled to  
run out of IPv4 addresses in november 2011.

> Right. IMO that proposal goes counter to the idea behind BEHAVE, which
> is to make NATs more regularized. Having the NAPT act differently
> based on what port numbers are used actually makes their behavior more
> diverse instead of more regularized.

Unfortunately, if we want scalability we can't afford to do the right  
thing under all circumstances. Defining under which circumstances we  
will be doing the right thing and under which circumstances we won't  
seems like a good second choice. More so than things like timing,  
destination port is relatively easy to change and easy to determine by  
everyone involved.

> The key question is how a NAPT can accurately differentiate apps that
> use UNSAF from ones that don't, because that's the characteristic that
> can be used to drive more efficient connection multiplexing. You
> propose doing this based on the observable transmission behavior,
> Iljitsch/Remi have suggested doing it based on destination ports. Both
> have pros and cons. Do other options exist?

An interesting observation is that in order to make use of endpoint  
independent mappings, a host needs to run STUN. So if the first  
session on a new port number is STUN then we know we need endpoint  
independent mapping. If it isn't, then we very likely don't.

Another option would be to dynamically correlate destination ports  
that a host is communicating with with the use of ephemeral source  
ports. Once a certain level of consistency is observed, it would then  
be possible to use endpoint dependent/independent mapping for  
destination ports in subsequent sessions.

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sat May 24 07:44:37 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7AE083A69A4;
	Sat, 24 May 2008 07:44:37 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 67D2E3A67B5
	for <behave@core3.amsl.com>; Sat, 24 May 2008 07:44:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
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 HG1mHoSLCi9v for <behave@core3.amsl.com>;
	Sat, 24 May 2008 07:44:35 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 60E2D3A6812
	for <behave@ietf.org>; Sat, 24 May 2008 07:44:35 -0700 (PDT)
Received: from [192.168.2.13] (static-167-138-7-89.ipcom.comunitel.net
	[89.7.138.167] (may be forged)) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m4OEiGaa005305
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Sat, 24 May 2008 16:44:17 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <F65F8495-E695-488C-8D23-9BB9AB33AF3F@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Dan Wing <dwing@cisco.com>
In-Reply-To: <004701c8bd1f$b08ebf00$3947150a@cisco.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Sat, 24 May 2008 16:44:23 +0200
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A		570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>	<DF	3	5AA43-736F-454A-A471-123DBE79274D@nokia.com><09c701c8bc37$83bb4310$1496150a@cisco.com><4836DEE5.4070901@sipeerior.com>
	<4836F52D.7030809@it.uc3m.es> <48370975.8040307@sipeerior.com>
	<0af801c8bd09$860355e0$d8e9520a@cisco.com>
	<4837381E.4040205@sipeerior.com>
	<004701c8bd1f$b08ebf00$3947150a@cisco.com>
X-Mailer: Apple Mail (2.919.2)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 23 mei 2008, at 23:55, Dan Wing wrote:

> Yes, we may well be successful in identifying some set of ports for
> client/server applications.

As long as we can identify the ones that use up many ports in practice  
we should be in reasonable shape, there is no need to make an  
exhaustive list.

> But are we sure there are no UNSAF applications or applications
> that need TCP S-O which run on TCP/80?  Many applications do attempt
> to run on TCP/80 in an effort to work through enterprise firewalls  
> that
> only allow TCP/80 -- Cisco and other vendors have deployed IDS and
> firewalls that inspect TCP/80 traffic in an effort to block such non- 
> HTTP
> applications.

[Being new to this group I have no idea what "UNSAF" is or where I  
need to go to find out... A pointer please?]

If both ends are hampered in this way they can't communicate even with  
simultaneous open. I'm also guessing that anyone being this  
restrictive won't be prepared to receive incoming sessions so endpoint  
independence is of no use.

And of course throwing away 65535 perfectly good ports doesn't really  
help scalability.

If people are really determined to shoot themselves in the foot  
there's not much we can do.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sat May 24 08:10:15 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 933303A696A;
	Sat, 24 May 2008 08:10:15 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4ED213A696A
	for <behave@core3.amsl.com>; Sat, 24 May 2008 08:10:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
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 R6Ejt93qLi0z for <behave@core3.amsl.com>;
	Sat, 24 May 2008 08:10:12 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 762FD3A68F5
	for <behave@ietf.org>; Sat, 24 May 2008 08:10:10 -0700 (PDT)
Received: from [192.168.2.13] (static-167-138-7-89.ipcom.comunitel.net
	[89.7.138.167] (may be forged)) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m4OF9sTu005768
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Sat, 24 May 2008 17:09:54 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <7B1BBA9C-493B-416F-B02B-B67D5E513EA4@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Bruce Lowekamp <lowekamp@sipeerior.com>
In-Reply-To: <483599C0.4030009@sipeerior.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Sat, 24 May 2008 17:10:01 +0200
References: <483526BD.1090308@free.fr> <483599C0.4030009@sipeerior.com>
X-Mailer: Apple Mail (2.919.2)
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Address-port sparing NATs - a proposal
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 22 mei 2008, at 18:05, Bruce Lowekamp wrote:

>> PROPOSAL:
>> 1. A NAT, to be an *address-port sparing NAT*,  MUST do mappings that
>> are endpoint-dependent if initiated with external-host ports equal  
>> to 80
>> (HTTP), or equal to 53 (DNS), or in the range 6881-6889 (BitTorrent).

> So including BitTorrent here makes sense in a world where there are  
> tons
> of BitTorrent nodes that are publically accessible on the outside of
> your "address-port sparing NAT" that can be contacted.  However,
> mandating address-dependent mapping is absolutely the wrong solution  
> if
> you are trying to allow these apps to continue to work as such NATs
> become more common.  You need to mandate independent mapping and  
> support
> of TCP-SO for these to work.

Aside: it seems to me that with some extra work it would be possible  
to make simultaneous open to work without having endpoint independent  
mapping in the general case.

> Otherwise you come up with a temporary
> workaround that solves this particular problem only as long as this
> deployment is is rare, and then breaks the world as more of these
> appear, resulting in no one using 6881-6889 for p2p anything anymore.

Note that it is EXTREMELY common to use ports outside this range for  
BitTorrent, to the point that some people even refuse to talk to you  
if you use the default ports.

Also note that the BitTorrent tracker only distributes IP addresses  
and port number for peers to other peers. So adding simultaneous open  
capability to BitTorrent would require changes to the protocol so that  
trackers can facilitate the communication of the parameters and timing  
between the two parties involved. (There's also a DHT extension to  
BitTorrent but I don't know how that handles this.)

BitTorrent is the worst offender that I know of when it comes to using  
up port numbers: the protocol uses at least a few dozen and upto  
hundreds of ports, keeping sessions open for a long time but also  
continuously setting up new sessions, which often fails so the session  
ends up in SYN_SENT and/or TIME_WAIT states for significant periods of  
time.

So BitTorrent the way it is now must absolutely not receive full  
endpoint independence for each session.

However, it should be possible to change implementations so they use  
the same source port for all their sessions, and use STUN to find out  
what that port number looks like as seen from the outside. If the NAT  
then allows incoming sessions on that same port number BitTorrent can  
work without changes to the protocol and only using a single port  
number.

It should even be possible to create shim UPnP and NAT-PMP  
implementations (the protocols that BitTorrent applications generally  
use today to get through NAT) that send up a session to a STUNT server  
to open up a port and then return that port to the application.

So the improved BitTorrent implementations would take advantage of  
endpoint independence and not cause scalabiliy issues. The trouble  
would be telling the difference between old and new implementations.

Last but not least, BitTorrent has very little trouble migrating to  
IPv6, because unlike protocols like SIP, there is no need for every  
peer to be able to talk to every other peer. As long as at least a few  
peers are dual stack, having v4-only and v6-only peers is not a problem.

> Or is the proposal that enough current apps use those ports that  
> making
> them endpoint-dependent solves the short-term problem and long-term  
> the
> apps will migrate to using other ports and doing it in a NAT-friendly
> manner?

That seems reasonable. Or migrate to IPv6.

> I guess this makes sense in a provider-based world where everyone  
> relies
> on the STUN server provisioned for them, but in particular with a p2p
> world, a STUN server can run on any port. You can't identify an
> application that needs independent mapping based on its outbound port
> number.

For NAT64 we could specify that a STUN server is part of the NAT64  
functionality. The part that I don't understand, though, is how  
clients learn addresses for STUN servers.

> You MIGHT be able to modify this rule to specify that endpoint
> independent mapping MUST be used for connections that begin with STUN
> requests, but I don't think this works for TCP connections since you
> have to assign the mapping before you see the data.

I don't understand?

> I think it might be possible to specify some small set of destination
> ports for which dependent mapping is not harmful.  And realistically,
> this will eliminate tons of wasted ports.

That would be a very good start.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sat May 24 08:47:03 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 73BEC3A6A44;
	Sat, 24 May 2008 08:47:03 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F19D63A6A42
	for <behave@core3.amsl.com>; Sat, 24 May 2008 08:47:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.801
X-Spam-Level: 
X-Spam-Status: No, score=-1.801 tagged_above=-999 required=5 tests=[AWL=1.961, 
	BAYES_00=-2.599, RCVD_BAD_ID=2.837, RCVD_IN_DNSWL_MED=-4]
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 RiUZGPqSho3a for <behave@core3.amsl.com>;
	Sat, 24 May 2008 08:47:02 -0700 (PDT)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131])
	by core3.amsl.com (Postfix) with ESMTP id B2CE23A699E
	for <behave@ietf.org>; Sat, 24 May 2008 08:47:01 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (unknown 
	[163.117.203.43])by smtp01.uc3m.es (Postfix) with ESMTP id E39F9634C41;
	Sat, 24 May 2008 17:46:54 +0200 (CEST)
Message-ID: <48383867.3020303@it.uc3m.es>
Date: Sat, 24 May 2008 17:46:47 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com><2F0D498F-B9BC-4B53-A5
	70-281BC0D2CC91@nokia.com><0ac701c8bb6d$c4076ef0$a25b150a@cisco.com><DF35A
	A43-736F-454A-A471-123DBE79274D@nokia.com> 
	<E9485E99-1E7A-486A-AC5C-A1F26319731B@muada.com>
In-Reply-To: <E9485E99-1E7A-486A-AC5C-A1F26319731B@muada.com>
X-imss-version: 2.050
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-24.7395 TC:1F TRN:61 TV:5.5.1026(15928.007)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Iljitsch van Beijnum escribi=F3:
>
> Unfortunately, if we want scalability we can't afford to do the right  =

> thing under all circumstances. =


well you can, this is called IPv6
I mean, NATs are endpoint independent and if you need more addresses,
you should use IPv6

that's one way of doing it

Of course the question then is if the IETF has enough strength to
support such approach, cause if not people would start building nats
that do port sparing in they way they see fit, and we end up in the
worst scenario

> Defining under which circumstances we  =

> will be doing the right thing and under which circumstances we won't  =

> seems like a good second choice. More so than things like timing,  =

> destination port is relatively easy to change and easy to determine by  =

> everyone involved.
>
>   =

>> The key question is how a NAPT can accurately differentiate apps that
>> use UNSAF from ones that don't, because that's the characteristic that
>> can be used to drive more efficient connection multiplexing. You
>> propose doing this based on the observable transmission behavior,
>> Iljitsch/Remi have suggested doing it based on destination ports. Both
>> have pros and cons. Do other options exist?
>>     =

>
> An interesting observation is that in order to make use of endpoint  =

> independent mappings, a host needs to run STUN. =


This is not the case actually

One way of using endpoint indepednecy is to use stun

There are other ways to do this

For instance, applications can do nat traversal themselves and they
don't use stun. I guess VOIP apps already do this. This is perfeclty ok
and the architecture should support that

> So if the first  =

> session on a new port number is STUN then we know we need endpoint  =

> independent mapping. If it isn't, then we very likely don't.
>
>   =

That's again assuming some application bhaviour (as in the other approaches)

In this case, you assume that application will use STUN for nat traversal

AFAIK, the ietf is not imposing stun as the only mean to traverse NATs
and doing application layer nat travrsal is a valid optiuon, that would
be render more complicated if we do this

Bottom line, hardcoding in the architecture application behaviour is a
bad idea.


So far all the proposal we have hardcode some for of behaviour:
- the timer approach hardcode the application behaviour that the
incoming communication will occur within a given timeout
- the port approach hardcode the application behaviour that certain
applications that use certain ports do not need endpoint independence
- the stun approach you mention above hardcode the application behaviour
that application only use stun for nat traversal

The question is which one of these seems like the strongest assumption

IMHO, assuming that in TCP port 80 will be used only for http and that
http will not require endpoint independence seems a reasonable =

assumption, and doing this for very well know ports would save tons of =

wasted ports and sems a reasonable tradeoff to me


> Another option would be to dynamically correlate destination ports  =

> that a host is communicating with with the use of ephemeral source  =

> ports. Once a certain level of consistency is observed, it would then  =

> be possible to use endpoint dependent/independent mapping for  =

> destination ports in subsequent sessions.
>   =


how would you do that?

Regards, marcelo


> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
>   =



_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sun May 25 08:19:41 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DA65E3A6A68;
	Sun, 25 May 2008 08:19:41 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D86593A6ABB
	for <behave@core3.amsl.com>; Sun, 25 May 2008 08:19:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.836
X-Spam-Level: 
X-Spam-Status: No, score=-2.836 tagged_above=-999 required=5
	tests=[AWL=-0.237, BAYES_00=-2.599]
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 lxdJVBVYzaGk for <behave@core3.amsl.com>;
	Sun, 25 May 2008 08:19:39 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 837C43A6A68
	for <behave@ietf.org>; Sun, 25 May 2008 08:19:39 -0700 (PDT)
Received: from [192.168.2.13] (static-167-138-7-89.ipcom.comunitel.net
	[89.7.138.167] (may be forged)) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m4PFJIl7025711
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Sun, 25 May 2008 17:19:19 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <E72E87E1-4CB2-4A15-9C4F-E115166489F7@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
In-Reply-To: <48383867.3020303@it.uc3m.es>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Sun, 25 May 2008 17:19:27 +0200
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com><2F0D498F-B9BC-4B53-A5
	70-281BC0D2CC91@nokia.com><0ac701c8bb6d$c4076ef0$a25b150a@cisco.com><DF35A
	A43-736F-454A-A471-123DBE79274D@nokia.com>
	<E9485E99-1E7A-486A-AC5C-A1F26319731B@muada.com>
	<48383867.3020303@it.uc3m.es>
X-Mailer: Apple Mail (2.919.2)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 24 mei 2008, at 17:46, marcelo bagnulo braun wrote:

>> Unfortunately, if we want scalability we can't afford to do the  
>> right  thing under all circumstances.

> well you can, this is called IPv6
> I mean, NATs are endpoint independent and if you need more addresses,
> you should use IPv6

I was of course speaking within the context of using NAT(64).

As you know, I've argued before that supporting peer-to-peer  
applications in NAT64 is unnecessary because those applications can be  
run over IPv6.

If we can get rough consensus on that we can then specify endpoint  
dependent mapping for NAT64 and there is no scalability issue.

Note that there are two types of peer-to-peer applications: the ones  
where each peer must be able to communicate with any given other peer  
(like in VoIP, where you want to be able to call everyone) and the  
ones where there is no requirement that every two peers can  
communicate, as long as every peer can communicate with a reasonably  
sized subset of all peers and there is some overlap between the  
subsets. (I.e., with BitTorrent if 45% of the peers is v4, 45% is v6  
and 10% is dual stack everyone will be able to complete the download.)

For VoIP-type applications migration to IPv6 is hard, for BitTorrent- 
type applications it's easy.

> Of course the question then is if the IETF has enough strength to
> support such approach, cause if not people would start building nats
> that do port sparing in they way they see fit, and we end up in the
> worst scenario

I don't necessarily agree that this is the worst scenario. The worst  
scenario is that users can't run their applications. If we can't make  
that happen 100% of the time we should at least maximize the chances  
of things working. Consistently not working is the worst case  
scenario, even though inconsistently working a small fraction of the  
time is more frustrating.  :-)

>> An interesting observation is that in order to make use of  
>> endpoint  independent mappings, a host needs to run STUN.

> This is not the case actually

> One way of using endpoint indepednecy is to use stun

> There are other ways to do this

> For instance, applications can do nat traversal themselves and they
> don't use stun. I guess VOIP apps already do this. This is perfeclty  
> ok
> and the architecture should support that

Right. On the other hand, if we can make a solution that works well  
and scales well but only if applications use STUN I'll take that over  
the situation where things either don't work well or don't scale well  
because we don't want to force people to use STUN. Same thing for  
building in port-dependent behavior.

> Bottom line, hardcoding in the architecture application behaviour is a
> bad idea.

What we're doing here isn't architecture, it's hacks to make things  
work.

If you want a clean architecture, use IPv6 with provider aggregatable  
addresses and no firewalling. Then you get full end-to-end and  
scalability. Unfortunately, people seem to value other things above  
those two aspects.

> So far all the proposal we have hardcode some for of behaviour:
> - the timer approach hardcode the application behaviour that the
> incoming communication will occur within a given timeout
> - the port approach hardcode the application behaviour that certain
> applications that use certain ports do not need endpoint independence
> - the stun approach you mention above hardcode the application  
> behaviour
> that application only use stun for nat traversal

Another option would be to use a TCP option to indicate that endpoint  
independent mapping is required. However, getting clients to put  
options into TCP headers is probably a hard thing to do within a  
reasonable timeframe. But maybe it's doable to make STUNT and SIP  
servers and BitTorrent trackers etc do this on the SYN/ACK rather than  
having the client do it on the SYN.

> IMHO, assuming that in TCP port 80 will be used only for http and that
> http will not require endpoint independence seems a reasonable  
> assumption, and doing this for very well know ports would save tons  
> of wasted ports and sems a reasonable tradeoff to me

Agree.

>> Another option would be to dynamically correlate destination ports   
>> that a host is communicating with with the use of ephemeral source   
>> ports. Once a certain level of consistency is observed, it would  
>> then  be possible to use endpoint dependent/independent mapping  
>> for  destination ports in subsequent sessions.

> how would you do that?

Well, if you see an internal host set up 20 sessions towards port 80  
for different external systems and use a different source port each  
time it's a reasonable guess that new sessions towards port 80 don't  
need endpoint independence.

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sun May 25 23:22:27 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BA0CA3A6B25;
	Sun, 25 May 2008 23:22:27 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1D99E3A6B4E
	for <behave@core3.amsl.com>; Sun, 25 May 2008 23:22:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.781
X-Spam-Level: 
X-Spam-Status: No, score=-1.781 tagged_above=-999 required=5 tests=[AWL=0.168, 
	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 YbGSzf0VnT2L for <behave@core3.amsl.com>;
	Sun, 25 May 2008 23:22:18 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id 5E7C33A6B25
	for <behave@ietf.org>; Sun, 25 May 2008 23:22:18 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 59DED3EA0D5;
	Mon, 26 May 2008 08:22:19 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 116243EA0D3;
	Mon, 26 May 2008 08:22:18 +0200 (CEST)
Message-ID: <483A5722.4060607@free.fr>
Date: Mon, 26 May 2008 08:22:26 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Lars Eggert <lars.eggert@nokia.com>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>
	<DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
In-Reply-To: <DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
Cc: behave@ietf.org, ext Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Lars Eggert  - Le 5/22/08 4:58 PM :

> The key question is how a NAPT can accurately differentiate apps that  =

> use UNSAF from ones that don't, because that's the characteristic that  =

> can be used to drive more efficient connection multiplexing. You  =

> propose doing this based on the observable transmission behavior,  =

> Iljitsch/Remi have suggested doing it based on destination ports. Both  =

> have pros and cons. Do other options exist?
For an exact record of who did what:
- Iljitsch van Beijnium introduced the  *requirement* in details
(http://www.ietf.org/mail-archive/web/behave/current/msg03824.html)
- I introduced the principle of destination ports in "packets that =

initiate addresss-port mappings" indicate whether endpoint independent =

mapping is needed or not.
(http://www.ietf.org/mail-archive/web/behave/current/msg03824.html)
- Bruce Lowekamp introduced the principle that endpoint independent =

mapping remain the default behavior, endpoint depenency being limited to =

mappings where initial destination ports indicate its possibility.
(http://www.ietf.org/mail-archive/web/behave/current/msg03845.html)

Pros and cons are still being debated;
Also debated is whether BitTorrent ports as initial destination ports =

indicate that endpoint dependency is possible (if yes, the saving on =

address-port consumption can be huge).

Regards.

R=E9mi Despr=E9s
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sun May 25 23:29:59 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5657F3A6B39;
	Sun, 25 May 2008 23:29:59 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C33873A6B5A
	for <behave@core3.amsl.com>; Sun, 25 May 2008 23:29:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.899
X-Spam-Level: 
X-Spam-Status: No, score=-5.899 tagged_above=-999 required=5
	tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_24=0.6,
	MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 QFEGsHBlrxfQ for <behave@core3.amsl.com>;
	Sun, 25 May 2008 23:29:52 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id 123043A6B39
	for <behave@ietf.org>; Sun, 25 May 2008 23:29:51 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m4Q6TQXC019184 for <behave@ietf.org>; Mon, 26 May 2008 09:29:51 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 26 May 2008 09:29:10 +0300
Received: from esdhcp041120.research.nokia.com ([172.21.41.120]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 26 May 2008 09:29:10 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: behave@ietf.org
Date: Mon, 26 May 2008 09:29:14 +0300
User-Agent: KMail/1.9.9
References: <8EC5CF03-6800-464B-8424-A196E1FA0901@muada.com>
	<48373B5B.3040306@cisco.com> <4837EF3A.2050705@it.uc3m.es>
In-Reply-To: <4837EF3A.2050705@it.uc3m.es>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805260929.14711.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 26 May 2008 06:29:10.0792 (UTC)
	FILETIME=[CEEE5880:01C8BEF9]
X-Nokia-AV: Clean
Subject: Re: [BEHAVE] Scalability of endpoint independent mapping
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Le Saturday 24 May 2008 13:34:34 ext marcelo bagnulo braun, vous avez =E9cr=
it=A0:
> >> So, now suppose that Y2:y2 wants to send packets toward X1,x1, how
> >> would he do that?
> >> wouldn't that be a problem for p2p apps?
> >> I mean, if the goal of X1 was to create a mpping so it can later on
> >> receive incoming communications through X'1,x'1, this would break
> >> that, right?
> >
> > Not if your NAT is also doing address and port restricted filtering.
>
> but this is NOT recommended according to the behave requirements, right?
> I mean, endpoint independent filters are recommended and if more
> stringent filtering is needed, then address dependent filtering is
> recommended, but never address and port dependent filtering, right?

In real life, there are a number of applications still using "legacy" STUN =
or =

similar techniques, i.e. unilateral NAT traversal. ICE is bilateral, =

but/hence a lot trickier and invasive to implement.

It would be a mistake to assume that everything will use ICE. In fact, supp=
ort =

for legacy applications is one of the use-case for protocol translation, is =

it not?

(...)
> My concerns are:
> - target addresses are very likely to collide

Yep. Many clients may likely have many AJAX-et-al connections to the same =

GMail IP:port each. I think there is no way around it, without changing how =

TCP works. In other words, the number of concurrent connections per NAT IP =

addresses times NAT ports to a single (web)server is a ONE. No matter what =

algorithm you are using for port allocation.

> - address and port filtering is not recommended by behave requirements
> and both recommended behaviours, i.e. endpoint independent filtering and
> address dependent filtering cannot be achieved

BEHAVE does NOT recommend which _filtering_ to use. Independent filtering i=
s =

recommended _if_ application-transparency is to be favored.


-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sun May 25 23:34:50 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1E7483A6964;
	Sun, 25 May 2008 23:34:50 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 51AF73A6964
	for <behave@core3.amsl.com>; Sun, 25 May 2008 23:34:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.149
X-Spam-Level: 
X-Spam-Status: No, score=-6.149 tagged_above=-999 required=5 tests=[AWL=0.150, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 eY2xZ34pUWaL for <behave@core3.amsl.com>;
	Sun, 25 May 2008 23:34:48 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id 423793A68DB
	for <behave@ietf.org>; Sun, 25 May 2008 23:34:48 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m4Q6YbsY024118; Mon, 26 May 2008 09:34:46 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 26 May 2008 09:34:30 +0300
Received: from esdhcp041120.research.nokia.com ([172.21.41.120]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 26 May 2008 09:34:29 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: behave@ietf.org
Date: Mon, 26 May 2008 09:34:33 +0300
User-Agent: KMail/1.9.9
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>
	<004701c8bd1f$b08ebf00$3947150a@cisco.com>
	<F65F8495-E695-488C-8D23-9BB9AB33AF3F@muada.com>
In-Reply-To: <F65F8495-E695-488C-8D23-9BB9AB33AF3F@muada.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805260934.33777.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 26 May 2008 06:34:29.0792 (UTC)
	FILETIME=[8D11E200:01C8BEFA]
X-Nokia-AV: Clean
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Le Saturday 24 May 2008 17:44:23 ext Iljitsch van Beijnum, vous avez =E9cri=
t=A0:
> [Being new to this group I have no idea what "UNSAF" is or where I
> need to go to find out... A pointer please?]

RFC3424.

-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 26 01:30:49 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A0BF828C141;
	Mon, 26 May 2008 01:30:49 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7229F3A6B81
	for <behave@core3.amsl.com>; Mon, 26 May 2008 01:30:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.348
X-Spam-Level: 
X-Spam-Status: No, score=-5.348 tagged_above=-999 required=5 tests=[AWL=1.251, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 6+NwCVMWYNgy for <behave@core3.amsl.com>;
	Mon, 26 May 2008 01:30:47 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id BBF3B28C136
	for <behave@ietf.org>; Mon, 26 May 2008 01:30:47 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,541,1204531200"; d="scan'208";a="103976213"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 26 May 2008 01:30:49 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m4Q8Unq0023952; 
	Mon, 26 May 2008 01:30:49 -0700
Received: from dwingwxp01 ([10.21.76.57])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m4Q8UlIN021775;
	Mon, 26 May 2008 08:30:48 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'marcelo bagnulo braun'" <marcelo@it.uc3m.es>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>	<D	F	3	5AA43-736F-454A-A471-123DBE79274D@nokia.com><09c701c8bc37$83bb4310$1496	150a@cisco.com><4836DEE5.4070901@sipeerior.com>
	<4836F52D.7030809@it.uc3m.es> <48370975.8040307@sipeerior.com>
	<0af801c8bd09$860355e0$d8e9520a@cisco.com>
	<4837F199.6040909@it.uc3m.es>
Date: Sun, 25 May 2008 22:30:47 -1000
Message-ID: <01e201c8bf0a$cd622a80$394c150a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Aci9i33gRn966Y6NTv6hraCBfmUXHQBfwoSg
In-Reply-To: <4837F199.6040909@it.uc3m.es>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=425; t=1211790649; x=1212654649;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20Dynamic=20Port=20Reuse
	|Sender:=20; bh=pnDord/OTKgwf5165lu2o/oiaEaBviix6NYEW1h6ITU=;
	b=haq3Z3Z2gRpfrIWdyEkU27wDorf/obQebe898kfU0hYsRwl/qQz6fIV0s9
	LogKPe5zPR7KSLlwoFwYn99ky+rQ3ov2CumcqjAuDI3+Bp+RkJz2GTAGgBw9
	fjml9OWxDd;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

...
> In general i think that all options for port reuse are bad cause the
> reduce flexibility assuming some form of application behaviour.

Good point.  And to keep it on everyone's mind, IPv4 NAPTs did something
similar:  they introduced IP address reuse which -- as we all know too well --
worked great with assumed application behavior (client/server UDP and TCP
applications work pretty well with NAPTs).

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 26 01:32:04 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5EA5128C137;
	Mon, 26 May 2008 01:32:04 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6DFF928C116
	for <behave@core3.amsl.com>; Mon, 26 May 2008 01:32:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.298
X-Spam-Level: 
X-Spam-Status: No, score=-6.298 tagged_above=-999 required=5 tests=[AWL=0.001, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 cWooESV21aww for <behave@core3.amsl.com>;
	Mon, 26 May 2008 01:32:02 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id 05BCB28C167
	for <behave@ietf.org>; Mon, 26 May 2008 01:31:43 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m4Q8VGZ0004116; Mon, 26 May 2008 11:31:40 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 26 May 2008 11:31:39 +0300
Received: from [192.168.2.172] ([10.241.184.208]) by esebh102.NOE.Nokia.com
	over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 26 May 2008 11:31:38 +0300
Message-Id: <9ECD366F-EE6A-47E6-A06C-A980F16868D3@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: =?ISO-8859-1?Q?ext_R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <4836876D.4080907@free.fr>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 26 May 2008 11:31:32 +0300
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>
	<DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
	<4835984F.6080504@free.fr>
	<F5356B94-213A-486F-9A93-7BDBB0D0BC51@nokia.com>
	<4836876D.4080907@free.fr>
X-Mailer: Apple Mail (2.919.2)
X-OriginalArrivalTime: 26 May 2008 08:31:39.0298 (UTC)
	FILETIME=[EAFB6020:01C8BF0A]
X-Nokia-AV: Clean
Cc: behave@ietf.org, ext Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi,

On 2008-5-23, at 11:59, ext R=E9mi Despr=E9s wrote:
> Lars Eggert  - Le 5/23/08 9:37 AM :
>> Both current proposals have advantages and disadvantages, and the  =

>> tradeoffs need to be understood. I'm not a particular fan of using  =

>> either ports or timers - both are crufty -
> IMO, simplicity and reliability are the strong points in favor of  =

> ports vs timings.
> So far, there is IMU no strong point in favor of timings.

I understand that you have a clear preference, but I don't, so I'll  =

not continue this argument here.

>> I'm still unconvinced that we actually need to solve this problem in
>> the first place. Anyone got data about how often NATs run out of
>> binding entries in situations where another IPv4 address isn't
>> available?
> The point is that more and more NATs are within ISP infrastructures.  =

> They are shared by potentially very large numbers of users, and may  =

> ahve to support huge numbers of UDP-TCP connections.

Understood. But my question is *why* do you think that ISP-run NATs  =

will quickly run out of IPv4 addresses? Because we don't have a  =

problem with NAT scalability as long as there are IPv4 addresses to  =

throw at the problem. And due to the multiplexing the NAT provides,  =

we'll need significantly fewer public IPv4 addresses than one per user  =

(which is what we currently have without a NAT64) for the NAT. (Unless  =

you assume that each user will end up having 65K active connections.)

> If nothing else, susceptibility of these NATs, or APBP servers, to  =

> DOS attacks will strongly depend on their margin between available  =

> address-port couples and those that are normally used.

I don't quite parse this sentence, but if it's saying that more a  =

efficient connection multiplexing is a security mechanism, I disagree.  =

All it does is buy you a little more breathing room.

Lars
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 26 01:32:16 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B58923A6B3A;
	Mon, 26 May 2008 01:32:16 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D746728C15E
	for <behave@core3.amsl.com>; Mon, 26 May 2008 01:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.795
X-Spam-Level: 
X-Spam-Status: No, score=-1.795 tagged_above=-999 required=5 tests=[AWL=0.154, 
	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 bS7hYGA0JNxE for <behave@core3.amsl.com>;
	Mon, 26 May 2008 01:32:15 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id 7F0A83A6A9B
	for <behave@ietf.org>; Mon, 26 May 2008 01:32:14 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 321163EA103
	for <behave@ietf.org>; Mon, 26 May 2008 10:32:16 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 0340F3EA0CA
	for <behave@ietf.org>; Mon, 26 May 2008 10:32:15 +0200 (CEST)
Message-ID: <483A7598.4030408@free.fr>
Date: Mon, 26 May 2008 10:32:24 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Behave WG <behave@ietf.org>
Subject: [BEHAVE] Degree of compatibility of BitTorrent with
	endpoint-independent mapping?
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

There seems to be no doubt that BitTorrent is a major source of =

consumption of address-port couples in NATs.

No disagreement either, it seems, that if endpoint-dependent mapping =

could be allowed in NATs for a large subset of BitTorrent connections, =

this would nicely mitigate the risk of address-port exhaustion in NATs =

where such risk exists.

Then the following questions are IMHO relevant:

1. Are many BitTorrent connections established with a 6881-6889 =

destination port in their first packet?
(YES IMU, but an expert would be better placed to tell.)

2. Is there a risk of simultenous open (TCP-SO) on these connections?
(NO IMU, but idem)

3. Independently of 1. and 2., is there a technical objection to
*NATs MAY use endpoint-dependent mapping IF AND ONLY IF destination =

ports of packets that trigger mappings are endorsed by IETF as =

compatible with such mapping*?
(NO IMU)

NOTE that the *MAY* in the sentence is such that some suppliers MAY keep =

forever an "endpoint-independent mapping for all" behavior.
They MAY also choose just a few initial ports of the list for =

endpoint-dependent mapping, and remain indefinitely like that, even if =

many more ports become endorsed in the list.

Here is a first (short) list that, if endorsed, could IMU do a lot of good:
HTTP, HTTPS, DNS, POP3, IMAP, SNMP... and BitTorrent if anwers

Regards.

R=E9mi
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 26 01:38:51 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 291DC3A6B3A;
	Mon, 26 May 2008 01:38:51 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B77C03A6B3A
	for <behave@core3.amsl.com>; Mon, 26 May 2008 01:38:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.448
X-Spam-Level: 
X-Spam-Status: No, score=-6.448 tagged_above=-999 required=5 tests=[AWL=0.151, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 mLTVMqA5-Ei0 for <behave@core3.amsl.com>;
	Mon, 26 May 2008 01:38:48 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id 739D83A6AAF
	for <behave@ietf.org>; Mon, 26 May 2008 01:38:48 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m4Q8cHMx021258; Mon, 26 May 2008 11:38:47 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 26 May 2008 11:38:30 +0300
Received: from [192.168.2.172] ([10.241.184.208]) by esebh102.NOE.Nokia.com
	over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 26 May 2008 11:38:30 +0300
Message-Id: <011AF26D-87D8-4F4D-9974-B74C6590F8CB@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: ext Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <E9485E99-1E7A-486A-AC5C-A1F26319731B@muada.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 26 May 2008 11:38:24 +0300
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>
	<2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>
	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>
	<DF35AA43-736F-454A-A471-123DBE79274D@nokia.com>
	<E9485E99-1E7A-486A-AC5C-A1F26319731B@muada.com>
X-Mailer: Apple Mail (2.919.2)
X-OriginalArrivalTime: 26 May 2008 08:38:30.0386 (UTC)
	FILETIME=[E0026D20:01C8BF0B]
X-Nokia-AV: Clean
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi,

On 2008-5-24, at 17:40, ext Iljitsch van Beijnum wrote:
> On 22 mei 2008, at 16:58, Lars Eggert wrote:
>
>>> And the primary motivation for me to write this up was v4 address
>>> conservation on the NAT64 box.
>
>> Understood, but are we really _that_ stressed for v4 space yet?
>
> In a word: yes.
>
> The IETF process is such that it's unrealistic to expect to go from  
> initial discussion through rough consensus to RFC publication in  
> less than two years. Then the vendors need some time to implement  
> the RFC and the operators to deploy the new hard/software.
>
> According to http://www.potaroo.net/tools/ipv4/ we are scheduled to  
> run out of IPv4 addresses in november 2011.

sure, but we might be able to free up IPv4 addresses that so far have  
been allocated to end users and use them to support the NAT64 boxes.  
Unless users end up having 65K connections active, the NAT will be  
more efficient at multiplexing, and there'll be a win.

I'm curious to know if you'd think that this scenario isn't realistic?

Lars
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 26 03:14:45 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5E59E3A6B74;
	Mon, 26 May 2008 03:14:45 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EA15B3A6B74
	for <behave@core3.amsl.com>; Mon, 26 May 2008 03:14:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.807
X-Spam-Level: 
X-Spam-Status: No, score=-1.807 tagged_above=-999 required=5 tests=[AWL=0.142, 
	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 9AimAcKGPLcG for <behave@core3.amsl.com>;
	Mon, 26 May 2008 03:14:43 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id 24E463A6A41
	for <behave@ietf.org>; Mon, 26 May 2008 03:14:43 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 5B4CB3EA101;
	Mon, 26 May 2008 12:14:44 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id EF6E53EA0D2;
	Mon, 26 May 2008 12:14:43 +0200 (CEST)
Message-ID: <483A8D9C.2080907@free.fr>
Date: Mon, 26 May 2008 12:14:52 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>	<2F0D498F-B9BC-4B53-A570-281BC0D2CC91@nokia.com>	<0ac701c8bb6d$c4076ef0$a25b150a@cisco.com>	<D	F	3	5AA43-736F-454A-A471-123DBE79274D@nokia.com><09c701c8bc37$83bb4310$1496	150a@cisco.com><4836DEE5.4070901@sipeerior.com>	<4836F52D.7030809@it.uc3m.es>
	<48370975.8040307@sipeerior.com>	<0af801c8bd09$860355e0$d8e9520a@cisco.com>	<4837F199.6040909@it.uc3m.es>
	<01e201c8bf0a$cd622a80$394c150a@cisco.com>
In-Reply-To: <01e201c8bf0a$cd622a80$394c150a@cisco.com>
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Dan Wing  - Le 5/26/08 10:30 AM :
> ...
>> In general i think that all options for port reuse are bad cause the
>> reduce flexibility assuming some form of application behaviour.
> =

> Good point.  And to keep it on everyone's mind, IPv4 NAPTs did something
> similar:  they introduced IP address reuse which -- as we all know too we=
ll --
> worked great with assumed application behavior (client/server UDP and TCP
> applications work pretty well with NAPTs).

IMU, the whole point of standardization is to obtain more compatibility, =

or to achieve more scalability, or to gain more security, or etc., =

accepting for this to reduce flexibility (in a well chosen manner). It =

has to be a trade-off.

In the particular case, the only consequence of the last proposal =

(leaving BitTorrent aside for the time being) is as follows:
If you use an HTTP, HTTPS, DNS, POP3, IMAP, or SNMP server port for =

something else than HTTP, HTTPS, DNS, POP3, IMAP, or SNMP (which =

obviously is not recommended) you should better make sure this is not =

precisely for one of the few applications that need endpoint-independent =

mapping.

BTW, it would be nice to know which applications need endpoint =

independent mapping other that those that start with STUN-SUNT-TURN-ICE =

  (which go together), and with Teredo?

R=E9mi


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 26 03:21:35 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DF7AE28C0F6;
	Mon, 26 May 2008 03:21:35 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A0CAE28C0F6
	for <behave@core3.amsl.com>; Mon, 26 May 2008 03:21:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.179
X-Spam-Level: 
X-Spam-Status: No, score=-6.179 tagged_above=-999 required=5 tests=[AWL=0.120, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 Lj3nAd+uFZWL for <behave@core3.amsl.com>;
	Mon, 26 May 2008 03:21:34 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id 8EC493A6B7A
	for <behave@ietf.org>; Mon, 26 May 2008 03:21:33 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m4QALBTQ029915 for <behave@ietf.org>; Mon, 26 May 2008 13:21:33 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 26 May 2008 13:21:13 +0300
Received: from esdhcp041120.research.nokia.com ([172.21.41.120]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 26 May 2008 13:21:13 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia Devices R&D
To: behave@ietf.org
Date: Mon, 26 May 2008 13:21:17 +0300
User-Agent: KMail/1.9.9
References: <03f801c8b5e6$12d6ed40$c3f0200a@cisco.com>
	<01e201c8bf0a$cd622a80$394c150a@cisco.com>
	<483A8D9C.2080907@free.fr>
In-Reply-To: <483A8D9C.2080907@free.fr>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200805261321.17582.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 26 May 2008 10:21:13.0698 (UTC)
	FILETIME=[39A13420:01C8BF1A]
X-Nokia-AV: Clean
Subject: Re: [BEHAVE] Dynamic Port Reuse
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Le Monday 26 May 2008 13:14:52 ext R=E9mi Despr=E9s, vous avez =E9crit=A0:
> BTW, it would be nice to know which applications need endpoint
> independent mapping other that those that start with STUN-SUNT-TURN-ICE
>   (which go together), and with Teredo?

Many video games and a bunch of VoIP/conferencing applications using many =

different non-IETF protocols.

-- =

R=E9mi Denis-Courmont
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 26 08:56:29 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D00143A6BC4;
	Mon, 26 May 2008 08:56:29 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 757DD3A6BB4
	for <behave@core3.amsl.com>; Mon, 26 May 2008 08:56:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.699
X-Spam-Level: 
X-Spam-Status: No, score=-109.699 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_41=0.6, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 gHwySJJtqVT7 for <behave@core3.amsl.com>;
	Mon, 26 May 2008 08:56:27 -0700 (PDT)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215])
	by core3.amsl.com (Postfix) with ESMTP id 5D6DA3A69A0
	for <behave@ietf.org>; Mon, 26 May 2008 08:56:27 -0700 (PDT)
Received: from tk1-exhub-c102.redmond.corp.microsoft.com (157.54.46.186) by
	TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with
	Microsoft
	SMTP Server (TLS) id 8.1.240.5; Mon, 26 May 2008 08:56:29 -0700
Received: from tk5-exmlt-w602.wingroup.windeploy.ntdev.microsoft.com
	(157.54.18.33) by tk1-exhub-c102.redmond.corp.microsoft.com
	(157.54.46.186)
	with Microsoft SMTP Server id 8.1.240.5; Mon, 26 May 2008 08:56:29 -0700
Received: from NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com
	([fe80::8de9:51a2:cd62:f122]) by
	tk5-exmlt-w602.wingroup.windeploy.ntdev.microsoft.com ([157.54.18.33])
	with mapi; Mon, 26 May 2008 08:56:57 -0700
From: Christian Huitema <huitema@windows.microsoft.com>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>, Behave WG
	<behave@ietf.org>
Date: Mon, 26 May 2008 08:56:24 -0700
Thread-Topic: [BEHAVE] Address-port sparing NATs - a proposal
Thread-Index: Aci74RUPmaobX8scRx+SYJamSsashADZWdoQ
Message-ID: <8EFB68EAE061884A8517F2A755E8B60A0A9D1807B0@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
References: <483526BD.1090308@free.fr>
In-Reply-To: <483526BD.1090308@free.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Subject: Re: [BEHAVE] Address-port sparing NATs - a proposal
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

> PROPOSAL:
> 1. A NAT, to be an *address-port sparing NAT*,  MUST do mappings that
> are endpoint-dependent if initiated with external-host ports equal to 80
> (HTTP), or equal to 53 (DNS), or in the range 6881-6889 (BitTorrent).
>
> 2. A NAT  MUST do  mappings that are endpoint-independent if initiated
> with external-host ports in the 1990-1992 range (STUN) or equal to 3544
> (Teredo).
>
> 3. NATs MAY also do mappings that are endpoint-independent if initiated
> with external-host ports known to be those of applications compatible
> with it (POP3, SMTP, IMAP, NNTP, Telnet, SNMP, IPsec over UDP...).

Reserving port 3544 for Teredo will not help. Teredo uses port 3544 for rendezvous with the Teredo server, but then uses a random port number for the actual packet transmission. If you want Teredo to work, the best way is to assume endpoint independent mapping for all UDP connections.

Note that endpoint independent mapping is not the only way to enable NAT traversal. Fundamentally, the requirement for NAT traversal is that the endpoints can somehow predict the behavior of the NAT. Assuming that the NAT performs five-tuple matching, there are many ways to solve this problem. For example, NAT could use a "collision resolution" strategy, as follow:

1) Given a request to map A-B-p-a-b, try first the port preservation behavior, C-B-p-a-b
2) If the tuple is taken, try an overflow port C-B-p-x(1)-b, where x = hash(A,B,p,a,b,iteration), with "iteration" set to 1 for the first iteration
3) If the result of the first iteration is also already in use, try x(2)= hash(A,B,p,a,b,iteration=2), etc.

If the tuple space is reasonably sparse, this works quickly. If the end-points know the hash function, they can try pinging ports a, X(1), .. X(n), eventually getting a connection.

-- Christian Huitema


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 26 09:35:06 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3E18C3A6AE6;
	Mon, 26 May 2008 09:35:06 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 82C613A69A0
	for <behave@core3.amsl.com>; Mon, 26 May 2008 09:35:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.817
X-Spam-Level: 
X-Spam-Status: No, score=-1.817 tagged_above=-999 required=5 tests=[AWL=0.132, 
	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 MLhEQO-VxCkk for <behave@core3.amsl.com>;
	Mon, 26 May 2008 09:35:03 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id A96E13A6B8B
	for <behave@ietf.org>; Mon, 26 May 2008 09:35:03 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id DB7E73EA0FF;
	Mon, 26 May 2008 18:35:05 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id DC0F63EA193;
	Mon, 26 May 2008 18:35:04 +0200 (CEST)
Message-ID: <483AE6C0.7070003@free.fr>
Date: Mon, 26 May 2008 18:35:12 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Christian Huitema <huitema@windows.microsoft.com>
References: <483526BD.1090308@free.fr>
	<8EFB68EAE061884A8517F2A755E8B60A0A9D1807B0@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <8EFB68EAE061884A8517F2A755E8B60A0A9D1807B0@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Address-port sparing NATs - a proposal
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Christian Huitema  - Le 5/26/08 5:56 PM :
> Reserving port 3544 for Teredo will not help. Teredo uses port 3544
> for rendezvous with the Teredo server, but then uses a random port
> number for the actual packet transmission. If you want Teredo to
> work, the best way is to assume endpoint independent mapping for all
> UDP connections.
The proposal as it is now would IMU solve this problem.

Extracts from =

http://www.ietf.org/mail-archive/web/behave/current/msg03926.html :
- "NATs MAY use endpoint-dependent mapping IF AND ONLY IF destination =

ports of packets that trigger mappings are endorsed by IETF as =

compatible with such mapping3

- Here is a first (short) list that, if endorsed, could IMU do a lot of =

good:
HTTP, HTTPS, DNS, POP3, IMAP, SNMP... and BitTorrent if anwers"

R=E9mi
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon May 26 18:32:13 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C75E93A6B8F;
	Mon, 26 May 2008 18:32:13 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 097B83A6921
	for <behave@core3.amsl.com>; Mon, 26 May 2008 18:32:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, 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 saGTAj+8Af1b for <behave@core3.amsl.com>;
	Mon, 26 May 2008 18:32:11 -0700 (PDT)
Received: from mail.sipeerior.com (mail.sipeerior.com [128.239.5.131])
	by core3.amsl.com (Postfix) with ESMTP id 020D33A6B8F
	for <behave@ietf.org>; Mon, 26 May 2008 18:32:10 -0700 (PDT)
Received: from vuelta.local (ip68-230-194-34.rd.hr.cox.net [68.230.194.34])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.sipeerior.com (Postfix) with ESMTP id D626E505B01;
	Mon, 26 May 2008 21:32:13 -0400 (EDT)
Message-ID: <483B649A.4030307@sipeerior.com>
Date: Mon, 26 May 2008 21:32:10 -0400
From: Bruce Lowekamp <lowekamp@sipeerior.com>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
References: <483A7598.4030408@free.fr>
In-Reply-To: <483A7598.4030408@free.fr>
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Degree of compatibility of BitTorrent
 with	endpoint-independent mapping?
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


I think there are major differences between BitTorrent applications as =

they exist now and as they would have to exist if NATs become even more =

common.

To the best of my knowledge (and I have not studied BitTorrent =

implementations extensively), they don't try to make any allowances for =

NAT behavior because there are enough hosts for which that is not an =

issue that the applications work if they try enough connections.

If NATs become even more common than they are now, BitTorrent =

applications may need to do more NAT traversal, so then TCP-SO would be =

more important.

However, regardless of that, I don't think that
- all BitTorrent applications use a particular range of ports
or
- only BitTorrent applications use those ports
or
- there is reason to believe that 5 years from now BitTorrent will be =

the common agreed use of those ports

so I don't think the BitTorrent ports are a good candidate for being a =

special case (if any are).

Currently, I think if BitTorrent applications opening ports is too big =

of a problem, I think rate limiting or per-host limiting the number of =

new connections accepted (as many nats already do) is the right solution.

Bruce


R=E9mi Despr=E9s wrote:
> There seems to be no doubt that BitTorrent is a major source of =

> consumption of address-port couples in NATs.
> =

> No disagreement either, it seems, that if endpoint-dependent mapping =

> could be allowed in NATs for a large subset of BitTorrent connections, =

> this would nicely mitigate the risk of address-port exhaustion in NATs =

> where such risk exists.
> =

> Then the following questions are IMHO relevant:
> =

> 1. Are many BitTorrent connections established with a 6881-6889 =

> destination port in their first packet?
> (YES IMU, but an expert would be better placed to tell.)
> =

> 2. Is there a risk of simultenous open (TCP-SO) on these connections?
> (NO IMU, but idem)
> =

> 3. Independently of 1. and 2., is there a technical objection to
> *NATs MAY use endpoint-dependent mapping IF AND ONLY IF destination =

> ports of packets that trigger mappings are endorsed by IETF as =

> compatible with such mapping*?
> (NO IMU)
> =

> NOTE that the *MAY* in the sentence is such that some suppliers MAY keep =

> forever an "endpoint-independent mapping for all" behavior.
> They MAY also choose just a few initial ports of the list for =

> endpoint-dependent mapping, and remain indefinitely like that, even if =

> many more ports become endorsed in the list.
> =

> Here is a first (short) list that, if endorsed, could IMU do a lot of goo=
d:
> HTTP, HTTPS, DNS, POP3, IMAP, SNMP... and BitTorrent if anwers
> =

> Regards.
> =

> R=E9mi
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> =


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May 27 00:31:05 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 148643A68C2;
	Tue, 27 May 2008 00:31:05 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6458C3A6B4B
	for <behave@core3.amsl.com>; Tue, 27 May 2008 00:31:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.526
X-Spam-Level: 
X-Spam-Status: No, score=-1.526 tagged_above=-999 required=5
	tests=[AWL=-0.177, BAYES_00=-2.599, HELO_EQ_FR=0.35,
	J_CHICKENPOX_31=0.6, 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 HSKtV27Ru4u6 for <behave@core3.amsl.com>;
	Tue, 27 May 2008 00:30:56 -0700 (PDT)
Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30])
	by core3.amsl.com (Postfix) with ESMTP id 5428F3A67B2
	for <behave@ietf.org>; Tue, 27 May 2008 00:30:56 -0700 (PDT)
Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp4-g19.free.fr (Postfix) with ESMTP id F269D3EA132;
	Tue, 27 May 2008 09:30:59 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp4-g19.free.fr (Postfix) with ESMTP id 9B94D3EA133;
	Tue, 27 May 2008 09:30:59 +0200 (CEST)
Message-ID: <483BB8BB.4080306@free.fr>
Date: Tue, 27 May 2008 09:31:07 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Bruce Lowekamp <lowekamp@sipeerior.com>
References: <483A7598.4030408@free.fr> <483B649A.4030307@sipeerior.com>
In-Reply-To: <483B649A.4030307@sipeerior.com>
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Degree of compatibility of BitTorrent
 with	endpoint-independent mapping?
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Thanks for the detailed answer.
More comments below.


Bruce Lowekamp  - Le 5/27/08 3:32 AM :

> To the best of my knowledge (and I have not studied BitTorrent =

> implementations extensively), they don't try to make any allowances for =

> NAT behavior because there are enough hosts for which that is not an =

> issue that the applications work if they try enough connections.
>
> If NATs become even more common than they are now, BitTorrent =

> applications may need to do more NAT traversal, so then TCP-SO would be =

> more important.

I am not a BitTorrent expert either but, IMU, a host behind a NAT can =

act, as far as BitTorrent is concerned, as though it would NOT be behind =

a NAT.

It suffices to activate the Port Mapping function of the NAT so that =

incoming connections on BitTorrent ports 6881-6889 go to this host.

Provided enough users do it, BiTorrent still works even if all users are =

behind NATs.

Also, to the best of my knowledge, BotTorrent works without any TCP-SO.

> =

> However, regardless of that, I don't think that
> - all BitTorrent applications use a particular range of ports

For the proposal at hand to be useful, it is not necessary that ALL  do it.
A significant proportion of them is sufficient.

> or
> - only BitTorrent applications use those ports

So far,I have heard of no other application using these ports,  but I =

undrestand that there might be be some.

Should they exist, I doubt that, in addition to their using one of the =

nine BitTorrent ports, they would NEED endpoint-independent mapping.

In any case, if they exist, they should be fixed, or at least documented =

so that their case can be examined.

> or

> - there is reason to believe that 5 years from now BitTorrent will be =

> the common agreed use of those ports

I don't see why you believe that BitTorrent ports should be used also =

for other applications.

Besides, in 5 years from now, I do hope that BitTorrent, like many other =

applications will use IPv6, withoiut any NAT.

> so I don't think the BitTorrent ports are a good candidate for being a =

> special case (if any are).
> =

> Currently, I think if BitTorrent applications opening ports is too big =

> of a problem, I think rate limiting or per-host limiting the number of =

> new connections accepted (as many nats already do) is the right solution.

If "per-host limiting the number of new connections" is seen as =

necessary, this IMO strongly reinforces the point that IETF must PERMIT =

a sparing use of address port couples, in particular for applications =

that use a lot of them. (The point is not to make it mandatory.)



R=E9mi






> R=E9mi Despr=E9s wrote:
>> There seems to be no doubt that BitTorrent is a major source of =

>> consumption of address-port couples in NATs.
>>
>> No disagreement either, it seems, that if endpoint-dependent mapping =

>> could be allowed in NATs for a large subset of BitTorrent connections, =

>> this would nicely mitigate the risk of address-port exhaustion in NATs =

>> where such risk exists.
>>
>> Then the following questions are IMHO relevant:
>>
>> 1. Are many BitTorrent connections established with a 6881-6889 =

>> destination port in their first packet?
>> (YES IMU, but an expert would be better placed to tell.)
>>
>> 2. Is there a risk of simultenous open (TCP-SO) on these connections?
>> (NO IMU, but idem)
>>
>> 3. Independently of 1. and 2., is there a technical objection to
>> *NATs MAY use endpoint-dependent mapping IF AND ONLY IF destination =

>> ports of packets that trigger mappings are endorsed by IETF as =

>> compatible with such mapping*?
>> (NO IMU)
>>
>> NOTE that the *MAY* in the sentence is such that some suppliers MAY =

>> keep forever an "endpoint-independent mapping for all" behavior.
>> They MAY also choose just a few initial ports of the list for =

>> endpoint-dependent mapping, and remain indefinitely like that, even if =

>> many more ports become endorsed in the list.
>>
>> Here is a first (short) list that, if endorsed, could IMU do a lot of =

>> good:
>> HTTP, HTTPS, DNS, POP3, IMAP, SNMP... and BitTorrent if anwers
>>
>> Regards.
>>
>> R=E9mi
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>>
> =

> =

> =


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue May 27 21:52:01 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 355D43A686D;
	Tue, 27 May 2008 21:52:01 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 76D433A686D
	for <behave@core3.amsl.com>; Tue, 27 May 2008 21:52:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.555
X-Spam-Level: 
X-Spam-Status: No, score=-6.555 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044,
	RCVD_IN_DNSWL_MED=-4]
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 05ILKxt-QKF6 for <behave@core3.amsl.com>;
	Tue, 27 May 2008 21:51:59 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [83.149.65.1])
	by core3.amsl.com (Postfix) with ESMTP id 4643D3A67E2
	for <behave@ietf.org>; Tue, 27 May 2008 21:51:59 -0700 (PDT)
Received: from 110.97.w.lacnicxi.nic.br (110.97.w.lacnicxi.nic.br
	[189.76.97.110]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m4S4o2e0042072
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Wed, 28 May 2008 06:50:30 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <B8652316-DB67-4E29-BA48-2425F241534D@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Bruce Lowekamp <lowekamp@sipeerior.com>
In-Reply-To: <483B649A.4030307@sipeerior.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 27 May 2008 21:08:09 -0300
References: <483A7598.4030408@free.fr> <483B649A.4030307@sipeerior.com>
X-Mailer: Apple Mail (2.919.2)
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Degree of compatibility of BitTorrent
	with	endpoint-independent mapping?
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 26 mei 2008, at 22:32, Bruce Lowekamp wrote:

> To the best of my knowledge (and I have not studied BitTorrent
> implementations extensively), they don't try to make any allowances  
> for
> NAT behavior because there are enough hosts for which that is not an
> issue that the applications work if they try enough connections.

No, that's not exactly true. In practice, you get much lower download  
speeds with BitTorrent if you can't accept incoming connections. So  
(some) clients implement UPnP and NAT-PMP to open up ports for  
incoming sessions in the NAT, if present. It's also very common for  
BitTorrent users to set up a mapping manually.

So BitTorrent does often use NAT traversal, just not with any of the  
mechanisms that the IETF is familiar with.  :-)

> If NATs become even more common than they are now, BitTorrent
> applications may need to do more NAT traversal, so then TCP-SO would  
> be
> more important.

I don't see simultaneous open happen for BitTorrent very soon. They  
may switch to UDP instead.

> so I don't think the BitTorrent ports are a good candidate for being a
> special case (if any are).

> Currently, I think if BitTorrent applications opening ports is too big
> of a problem, I think rate limiting or per-host limiting the number of
> new connections accepted (as many nats already do) is the right  
> solution.

IMO, that needs to happen regardless. But that doesn't address the  
exact same issues as port-dependent behavior. The two could be  
complimentary.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


