
From nobody Fri Mar  2 12:34:30 2018
Return-Path: <brandon.williams@akamai.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC85A127369 for <tram@ietfa.amsl.com>; Fri,  2 Mar 2018 12:34:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oS5htoFT4PMz for <tram@ietfa.amsl.com>; Fri,  2 Mar 2018 12:34:26 -0800 (PST)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4983126C25 for <tram@ietf.org>; Fri,  2 Mar 2018 12:34:26 -0800 (PST)
Received: from pps.filterd (m0122332.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w22KX4LD028704; Fri, 2 Mar 2018 20:34:26 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=subject : to : references : from : message-id : date : mime-version : in-reply-to : content-type : content-transfer-encoding; s=jan2016.eng; bh=49mW1OrXGBHYK1MVeio9ATqgFduK68lR0xyYcsej+hc=; b=cnDFJ2YKugl/ulYtmQO2n9Zp4Tpiy2wRvs7+PUUva35PGuxgGdMq0vO0Lj7pgbNc7sVe lwTvgfBA8IcZXugFxpWndsgy9is6zbi0h1GruS6fZ9PZfk8deqlRjc5a6hSAiHOxef9t cdlxOngpjnBvpfIERN59q/VP1AiJAli+9X0JaQxu09q3qcvdbnXOkP5TRrRZcShV2C2U GzsOjOnxLa/52cnT8ORk76cRYtlfxLhoaakVRgXJdqXx0F/yG6JG2oS3tTh5IaavlZlM 9ll+aHGEoubR2a2e/m24j28NXf1zPZCBtCsmKdW9H3k/kYSvLQ0L1gwuAXATTTmbEySS aw== 
Received: from prod-mail-ppoint3 ([96.6.114.86]) by mx0a-00190b01.pphosted.com with ESMTP id 2gew2kat6t-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 02 Mar 2018 20:34:26 +0000
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w22KPsJT032585; Fri, 2 Mar 2018 15:34:25 -0500
Received: from prod-mail-relay14.akamai.com ([172.27.17.39]) by prod-mail-ppoint3.akamai.com with ESMTP id 2gb491asx0-1; Fri, 02 Mar 2018 15:34:25 -0500
Received: from [172.28.118.62] (bowill.kendall.corp.akamai.com [172.28.118.62]) by prod-mail-relay14.akamai.com (Postfix) with ESMTP id 25EC2830EA; Fri,  2 Mar 2018 20:34:25 +0000 (GMT)
To: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>, "tram@ietf.org" <tram@ietf.org>
References: <151938010105.22640.16447250160507291406@ietfa.amsl.com> <BN6PR16MB142504A97AEBFBC54708BEEDEACC0@BN6PR16MB1425.namprd16.prod.outlook.com>
From: Brandon Williams <brandon.williams@akamai.com>
Message-ID: <62535408-3911-0b3c-a19c-d2fe3a7dfcff@akamai.com>
Date: Fri, 2 Mar 2018 15:34:24 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <BN6PR16MB142504A97AEBFBC54708BEEDEACC0@BN6PR16MB1425.namprd16.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-02_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803020241
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-02_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803020242
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/rdShpa85V3mPnlnbmszMaJ3N4lA>
Subject: Re: [tram] I-D Action: draft-ietf-tram-turnbis-14.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2018 20:34:29 -0000

This all looks good to me, and idnits is happy with the changs too :-)

I would like to see a thumbs up from Marc, who had the only other 
outstanding comments. Once he affirms, I think we're good to go.

Thanks!

--Brandon

On 02/23/2018 05:03 AM, Konda, Tirumaleswar Reddy wrote:
> This revision addresses comments from Brandon.
> 
> Cheers,
> -Tiru
> 
>> -----Original Message-----
>> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of internet-
>> drafts@ietf.org
>> Sent: Friday, February 23, 2018 3:32 PM
>> To: i-d-announce@ietf.org
>> Cc: tram@ietf.org
>> Subject: [tram] I-D Action: draft-ietf-tram-turnbis-14.txt
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> This draft is a work item of the TURN Revised and Modernized WG of the
>> IETF.
>>
>>          Title           : Traversal Using Relays around NAT (TURN): Relay Extensions
>> to Session Traversal Utilities for NAT (STUN)
>>          Authors         : Tirumaleswar Reddy
>>                            Alan Johnston
>>                            Philip Matthews
>>                            Jonathan Rosenberg
>> 	Filename        : draft-ietf-tram-turnbis-14.txt
>> 	Pages           : 83
>> 	Date            : 2018-02-23
>>
>> Abstract:
>>     If a host is located behind a NAT, then in certain situations it can
>>     be impossible for that host to communicate directly with other hosts
>>     (peers).  In these situations, it is necessary for the host to use
>>     the services of an intermediate node that acts as a communication
>>     relay.  This specification defines a protocol, called TURN (Traversal
>>     Using Relays around NAT), that allows the host to control the
>>     operation of the relay and to exchange packets with its peers using
>>     the relay.  TURN differs from some other relay control protocols in
>>     that it allows a client to communicate with multiple peers using a
>>     single relay address.
>>
>>     The TURN protocol was designed to be used as part of the ICE
>>     (Interactive Connectivity Establishment) approach to NAT traversal,
>>     though it also can be used without ICE.
>>
>>     This document obsoletes RFC 5766 and RFC 6156.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-tram-turnbis/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-tram-turnbis-14
>> https://datatracker.ietf.org/doc/html/draft-ietf-tram-turnbis-14
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-tram-turnbis-14
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> tram mailing list
>> tram@ietf.org
>> https://www.ietf.org/mailman/listinfo/tram
> 
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram
> 


From nobody Fri Mar  2 13:16:44 2018
Return-Path: <petithug@acm.org>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99D45124239 for <tram@ietfa.amsl.com>; Fri,  2 Mar 2018 13:16:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.442
X-Spam-Level: 
X-Spam-Status: No, score=-0.442 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4gx8gkWrtrHS for <tram@ietfa.amsl.com>; Fri,  2 Mar 2018 13:16:41 -0800 (PST)
Received: from implementers.org (unknown [IPv6:2001:4b98:dc0:45:216:3eff:fe7f:7abd]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BA1B12025C for <tram@ietf.org>; Fri,  2 Mar 2018 13:16:41 -0800 (PST)
Received: from [IPv6:2601:648:8301:730f:b138:267a:383f:dbfc] (unknown [IPv6:2601:648:8301:730f:b138:267a:383f:dbfc]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 2E306AE814; Fri,  2 Mar 2018 22:16:37 +0100 (CET)
To: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>, "tram@ietf.org" <tram@ietf.org>
References: <65c75449-152c-1ce7-7c81-460ca589d9f0@acm.org> <DM5PR16MB17881ABD54B89E14F0291C56EA4C0@DM5PR16MB1788.namprd16.prod.outlook.com> <ea84bcf9-19b6-5492-383b-18e2bc5a93bf@acm.org> <DM5PR16MB178859E2018148DBAD51635EEAF20@DM5PR16MB1788.namprd16.prod.outlook.com>
From: Marc Petit-Huguenin <petithug@acm.org>
Message-ID: <46fdf931-eb0c-c4fe-9c01-4a066134abfb@acm.org>
Date: Fri, 2 Mar 2018 13:16:35 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <DM5PR16MB178859E2018148DBAD51635EEAF20@DM5PR16MB1788.namprd16.prod.outlook.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="IpY8H68KI7IFsTiNGPsdoRBdXhZEvnLnP"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/Emle4-uPQ-37lrWZJ5R_NSsCC_Q>
Subject: Re: [tram] Review of dual allocation in TURNbis-11
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2018 21:16:43 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--IpY8H68KI7IFsTiNGPsdoRBdXhZEvnLnP
Content-Type: multipart/mixed; boundary="fWb8MMrCBpDitUEpqIqdbMmrx2xv2Mjvu";
 protected-headers="v1"
From: Marc Petit-Huguenin <petithug@acm.org>
To: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>,
 "tram@ietf.org" <tram@ietf.org>
Message-ID: <46fdf931-eb0c-c4fe-9c01-4a066134abfb@acm.org>
Subject: Re: [tram] Review of dual allocation in TURNbis-11
References: <65c75449-152c-1ce7-7c81-460ca589d9f0@acm.org>
 <DM5PR16MB17881ABD54B89E14F0291C56EA4C0@DM5PR16MB1788.namprd16.prod.outlook.com>
 <ea84bcf9-19b6-5492-383b-18e2bc5a93bf@acm.org>
 <DM5PR16MB178859E2018148DBAD51635EEAF20@DM5PR16MB1788.namprd16.prod.outlook.com>
In-Reply-To: <DM5PR16MB178859E2018148DBAD51635EEAF20@DM5PR16MB1788.namprd16.prod.outlook.com>

--fWb8MMrCBpDitUEpqIqdbMmrx2xv2Mjvu
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

As suggested by Brandon, I reviewed turnbis-14 for the modifications agre=
ed on below, and found some discrepancies.  See inline.

On 02/09/2018 04:51 AM, Konda, Tirumaleswar Reddy wrote:
>> -----Original Message-----
>> From: Marc Petit-Huguenin [mailto:petithug@acm.org]
>> Sent: Sunday, October 22, 2017 9:38 PM
>> To: Konda, Tirumaleswar Reddy
>> <TirumaleswarReddy_Konda@McAfee.com>; tram@ietf.org
>> Subject: Re: [tram] Review of dual allocation in TURNbis-11
>>
>> Inline.
>>
>> On 10/16/2017 07:14 PM, Konda, Tirumaleswar Reddy wrote:
>>> Thanks Marc for the detailed review, Please see inline
>>>
>>>> -----Original Message-----
>>>> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Marc Petit-
>>>> Huguenin
>>>> Sent: Saturday, October 14, 2017 12:59 AM
>>>> To: tram@ietf.org
>>>> Subject: [tram] Review of dual allocation in TURNbis-11
>>>>

[snip]

>>>
>>>>
>>>> - Section 6.2
>>>>
>>>> I would suggest to make ADDRESS-ERROR-CODE more generic by
>> renaming
>>>> it as WARNING-CODE and use the same format than for ERROR-CODE.
>> Then
>>>> allocate a new error code for that specific warning.  I would sugges=
t
>>>> to request the 0x8009 codepoint for that attribute.
>>>
>>> I don't understand the need to change ADDRESS-ERROR-CODE !
>>
>> To make it more generic and reusable in future specifications.
>=20
> ADDRESS-ERROR-CODE cannot use the same format as ERROR-CODE, ADDRESS-ER=
ROR-CODE signals the IP address family for which the warning is generated=
 + all the fields in the ERROR-CODE.=20
>=20
>>
>>>
>>>>
>>>> Also I think we needs two different warnings, one that states that
>>>> dual allocation is not available in a TURNbis server, but both
>>>> protocols are available, and another that says that dual allocation
>>>> failed because one of the two protocols is not available.  This is t=
o
>>>> let the client know that it is useless to try another allocation for=
 the
>> missing protocol.
>>>
>>> I don't get the reason for two different warnings.
>>
>> A server may support both IPv6 and IPv4 allocations and not support du=
al
>> allocation, in which case the client can do a second allocation for th=
e IPv6
>> relayed address.
>=20
> If the server does not support dual allocation but supports both IPv6 a=
nd IPv4 allocations, it will only allocate the IPv4 relayed address and n=
ot will not return ADDRESS-ERROR-CODE in the response, the client will kn=
ow the server does not understand the ADDITIONAL-ADDRESS-FAMILY attribute=
 (ADDITIONAL-ADDRESS-FAMILY is a comprehension-optional attribute).=20
>=20
>>
>> Alternatively the server may not support IPv6 at all, in which case th=
e second
>> allocation will fail and was unnecessary.
>=20
> ADDRESS-ERROR-CODE signals both unsupported IP address type (0x02 (IPv6=
 address family)) and the reason for failure (440 (unsupported address fa=
mily)).=20
>=20
> Cheers,
> -Tiru
>=20
>>
>> Using two different warnings permits to know if the second allocation =
will
>> succeed or not.
>>
>>>
>>>>
>>>> What is the policy when reserving the next port with the EVEN-PORT
>>>> attribute in a dual allocation, but one of them fails to find a pair=

>>>> of subsequent ports available?
>>>
>>> It's discussed in section 6.1
>>>
>>> <snip>
>>>    Clients MUST NOT
>>>    include ADDITIONAL-ADDRESS-FAMILY attribute in a Allocate request
>>>    that contains an EVEN-PORT attribute with the R bit set to 1.
>>> </snip>
>>>
>>>>
>>>> It is not said that the Allocate successful response must contain tw=
o
>>>> XRAs after a successful dual allocation.
>>>
>>> Good point, Updated draft.

I cannot find this update in turn-14.

>>>
>>>>
>>>> I would also suggest to add some text that says that when a TURNbis
>>>> server sends an Allocate success response, it must always send the
>>>> XRAs in the same order than the RAFs were sent.  So in case the
>>>> server sends back by mistake two XRAs, the first one matches the one=

>> requested by the client.

Did not get answer to that and did not see it in turn-14.

>>>>
>>>> The bullet list at the end needs also to be fixed for dual allocatio=
n.
>>>
>>> Agreed, fixed.
>>>
>>>>
>>>> - Section 6.3
>>>>
>>>> Here's too, the text needs to be updated for the dual allocation cas=
e.
>>>
>>>
>>> Yup, updated.
>>>

Same, there is no update since -11 in section 7.3 (formerly 6.3)

--=20
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: https://marc.petit-huguenin.org
Profile: https://www.linkedin.com/in/petithug


--fWb8MMrCBpDitUEpqIqdbMmrx2xv2Mjvu--

--IpY8H68KI7IFsTiNGPsdoRBdXhZEvnLnP
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEBSI+IuCHU8MsI1GjKcRFldZqfsQFAlqZvzMACgkQKcRFldZq
fsRhxRAAuXxiqNS7SEwDEKnr6xhgtEmk/yYHRjraBseP+aBlCW0yWgO3jrH8/bC9
Mzc/8HvWZkJil74KYDu3cMJFtz31UpFc5c3eIh60uYPTvURLJx9mibbhyJfhsTJn
qleSOe8wYysSysc8KHpLKDBJ0F6L8opm/VxrrW473G3HFw8FOtaddsbUWHYiuOTA
+RF2Kbo9UxPIebWmBmlDoI1ervCH8W0PQyNA8PB31bVVCV8UjCUIURjclTb7og8K
aWbxj2PFvrGIqZOTQLmBcfKFVYc0jw3GyhjhXsMuKCWX+FJGdT+HXG5+RV2/SUSG
UikeeuiQw61W4ohuyen5xy9JpKaSo2yJRtXC4o37a8bjkUufx154bkTf1Ek054A5
tIj9Vk18krzsic5EXXABoejjxezzGNuRpyEcfy/3L9lrnSnDXeNWkyMcQJQ7lsF0
Qgp2DrKojCaPlMbpJAkjjCoAdQBfdXyzU9NgktR9XwMQhj95NwtMt9XHR7oidFj1
1mtb8GqPv8TPNOZqsX+nbYADu5TlB4GjvB37CsIH1CthpO9Xz1SOaaE55CbpAnj1
DYm8suk38258Vr2DXrQwDrrrB54VML/jIL0s04vNNOvS85HkCofM8+/wFf8h75hC
JV1FVvHq76W2YbFr4o1rfam7PWilGH71UxdxKyjv/A+De0PiC1c=
=H8uM
-----END PGP SIGNATURE-----

--IpY8H68KI7IFsTiNGPsdoRBdXhZEvnLnP--


From nobody Fri Mar  2 13:33:56 2018
Return-Path: <petithug@acm.org>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2520120227 for <tram@ietfa.amsl.com>; Fri,  2 Mar 2018 13:33:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.442
X-Spam-Level: 
X-Spam-Status: No, score=-0.442 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sVkBB-Fb1FSW for <tram@ietfa.amsl.com>; Fri,  2 Mar 2018 13:33:52 -0800 (PST)
Received: from implementers.org (unknown [92.243.22.217]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EB321200E5 for <tram@ietf.org>; Fri,  2 Mar 2018 13:33:52 -0800 (PST)
Received: from [IPv6:2601:648:8301:730f:b138:267a:383f:dbfc] (unknown [IPv6:2601:648:8301:730f:b138:267a:383f:dbfc]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 2175FAE814; Fri,  2 Mar 2018 22:33:49 +0100 (CET)
To: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>, "tram@ietf.org" <tram@ietf.org>
References: <325ddd79-ef98-c8ce-de50-1ef3878cd433@acm.org> <DM5PR16MB17882606F7602CEE66009903EAF20@DM5PR16MB1788.namprd16.prod.outlook.com> <c7716d08-f265-9ce9-ed2a-513ea0ddade6@acm.org> <DM5PR16MB1788777DA4671DD256BBE230EAF20@DM5PR16MB1788.namprd16.prod.outlook.com>
From: Marc Petit-Huguenin <petithug@acm.org>
Message-ID: <d496aa92-6c68-53f4-efca-34ac2880cfbc@acm.org>
Date: Fri, 2 Mar 2018 13:33:48 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <DM5PR16MB1788777DA4671DD256BBE230EAF20@DM5PR16MB1788.namprd16.prod.outlook.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="8i7WYX3y9rPsrDofusTkfVvS9mPLRZ4s8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/EINRn8dHF1FtSNFt-FvwnF0a100>
Subject: Re: [tram] Review of TURNbis-11
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2018 21:33:54 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--8i7WYX3y9rPsrDofusTkfVvS9mPLRZ4s8
Content-Type: multipart/mixed; boundary="eT14sjNk4gDqm1D6xwwAFjCHRf5HddF00";
 protected-headers="v1"
From: Marc Petit-Huguenin <petithug@acm.org>
To: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>,
 "tram@ietf.org" <tram@ietf.org>
Message-ID: <d496aa92-6c68-53f4-efca-34ac2880cfbc@acm.org>
Subject: Re: [tram] Review of TURNbis-11
References: <325ddd79-ef98-c8ce-de50-1ef3878cd433@acm.org>
 <DM5PR16MB17882606F7602CEE66009903EAF20@DM5PR16MB1788.namprd16.prod.outlook.com>
 <c7716d08-f265-9ce9-ed2a-513ea0ddade6@acm.org>
 <DM5PR16MB1788777DA4671DD256BBE230EAF20@DM5PR16MB1788.namprd16.prod.outlook.com>
In-Reply-To: <DM5PR16MB1788777DA4671DD256BBE230EAF20@DM5PR16MB1788.namprd16.prod.outlook.com>

--eT14sjNk4gDqm1D6xwwAFjCHRf5HddF00
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

As suggested by Brandon, I reviewed turnbis-14 for the modifications agre=
ed on below, and found one discrepancy.  See inline.

On 02/09/2018 05:45 AM, Konda, Tirumaleswar Reddy wrote:
>> -----Original Message-----
>> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Marc Petit-
>> Huguenin
>> Sent: Friday, February 9, 2018 6:54 PM
>> To: Konda, Tirumaleswar Reddy
>> <TirumaleswarReddy_Konda@McAfee.com>; tram@ietf.org
>> Subject: Re: [tram] Review of TURNbis-11
>>
>> Hi,
>>
>> My responses inline.
>>
>> On 02/09/2018 03:53 AM, Konda, Tirumaleswar Reddy wrote:
>>> Hi Marc,
>>>
>>> Please see inline
>>>
>>>> -----Original Message-----
>>>> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Marc Petit-
>>>> Huguenin
>>>> Sent: Sunday, October 22, 2017 10:16 PM
>>>> To: tram@ietf.org
>>>> Subject: [tram] Review of TURNbis-11
>>>>
>>>> This is the second part of my review of TURNbis-11, i.e. everything
>>>> but the dual allocation part.
>>>>
>>>> - Section 2.1, last paragraph:
>>>>
>>>> May be a reference to RFC 5764 and RFC 7983 can be useful here.  Sam=
e
>>>> in section 4, second paragraph and following.  Same at the beginning=

>>>> of section 11.  Again in section 11.6 (if multiplexed, the message i=
n
>>>> the reserved range is not necessarily discarded).
>>>
>>> Even if the same host transport address is used for other protocols,
>> incoming packets to the TURN channel can be identified by just examini=
ng
>> the source address of the packet.
>>> May be I am missing something, I did not get a problem ?
>>
>> It was just an attempt to make TURN implementers aware of the demux
>> issues.
>=20
> Got it, added the following line:
> The algorithm of demultiplexing packets received from
> multiple protocols is discussed in [RFC7983].
>=20
>>
>>>
>>>>
>>>> - Section 2.2, first paragraph:
>>>>
>>>> I think that an informative reference to RFC 7635 may be useful
>>>> there, as alternative to the STUN authentication mechanism.
>>>
>>> Yes, updated.
>>>
>>>>
>>>> - Section 2.9:
>>>>
>>>> The whole 2.9 section and subsections looks normative and so should
>>>> be moved after section 3, perhaps on their own top level section.
>>>
>>> Done.
>>>
>>>>
>>>> - Section 4, 4th paragraph:
>>>>
>>>> I would replace "For each allocation..." by "For each Allocate
>>>> request...", because of the dual allocation feature.
>>>
>>> Fixed.
>>>
>>>>
>>>> - Section 4, 12th paragraph:
>>>>
>>>> Should make clear clear that UDP covers also DTLS.
>>>
>>> Yes, updated.

I cannot find this update in turn-14.

>>>
>>>>
>>>> - Section 6.1, 2nd paragraph:
>>>>
>>>> If the port is multiplexed with other protocols (RTP, WebRtc, etc..)=

>>>> then it has to reuse an existing socket.  The document should explai=
n this.
>>>
>>> It's already covered in Section 2.1 (last paragraph).
>>>
>>>>
>>>> - Section 6.2, 3th paragraph:
>>>>
>>>> Is it time to recommend DTLS instead of UDP?  In that case we need t=
o
>>>> make DTLS mandatory in section 4 paragraph 11 (and I support that
>> change).
>>>
>>> No, DTLS has both advantages (e.g. dictionary attack)  and disadvanta=
ges
>> (e.g. double encryption of application data).
>>
>> OK.
>>
>>>
>>>>
>>>> - Section 6.4, second bullet:
>>>>
>>>> Replace "...SRV procedures)." with "...DNS resolution procedures)."
>>>
>>> Any specific reason for the replacement ?
>>
>> This is to not exclude NPATR procedures (RFC 5928).
>=20
> Updated second bullet.
>=20
> Cheers,
> -Tiru
>=20
>>
>>>
>>>>
>>>> - Sections 14, 15 and 16:
>>>>
>>>> These are no longer new methods and attributes.  See also the next
>>>> comment.
>>>
>>> Fixed.
>>>
>>>>
>>>> - Section 19:
>>>>
>>>> Here you need to update the existing methods, attributes and error
>>>> code so the IANA registries point to the RFC-to-be, then you request=

>>>> allocation for the new attributes.  See section 17 of STUNbis on a
>>>> way to do that (that was done following a discussion with the IANA
>> representative at an IETF meeting).
>>>
>>> Thanks, updated draft.
>>>
>>>>
>>>> Note that ICMP should be comprehension-mandatory, not optional, as
>> we
>>>> do not want an old client to reject a Data indication with an ICMP a=
ttribute.
>>>
>>> If the indication contains unknown comprehension-required attributes,=
 the
>> behavior is the indication is discarded and processing ceases.
>>>
>>>>
>>>> Also, I do not know what this SendErr method is.
>>>
>>> Removed SendErr (stale entry from a previous version of the draft).
>>>
>>>>
>>>>
>>>> Nits
>>>> ----
>>>>
>>>> Section 1:
>>>>
>>>> s/connection to the Internet ./connection to the Internet./
>>>>
>>>> Section 2.4, first paragraph:
>>>>
>>>> The text switches between the words "mechanisms" and "way".  Choose
>>>> one.
>>>>
>>>> Section 6.2, item 8:
>>>>
>>>> s/ADDITIONAL- ADDRESS-FAMILY/ADDITIONAL-ADDRESS-FAMILY/
>>>>
>>>> Section 12.1, "Preferred Behavior"
>>>>
>>>> s/Label Field[RFC3697]/Label Field [RFC3697]/
>>>>
>>>> Section 21:
>>>>
>>>> s/ADDRESS-ERRR-CODE/ADDRESS-ERR-CODE/
>>>>
>>>> Section 22:
>>>>
>>>> s/orginal/original/
>>>
>>> Thanks, fixed all above nits.
>>>

--=20
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: https://marc.petit-huguenin.org
Profile: https://www.linkedin.com/in/petithug


--eT14sjNk4gDqm1D6xwwAFjCHRf5HddF00--

--8i7WYX3y9rPsrDofusTkfVvS9mPLRZ4s8
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEBSI+IuCHU8MsI1GjKcRFldZqfsQFAlqZwzwACgkQKcRFldZq
fsTx3hAAuCghLhxBMCQ75nrcavjlkI7pgY05GWOSqbGYCfmQbRxThZ+16rB+FPGo
kBekudmcOUn8qGObPnv33wCEpj4DhS77OQnoAzvPEO4zpyvqsyukniYs9foEnem4
8P1LVY4SR7vEnwM0D1Hu+Zwy5I3I7C5zpZgJPui2oeUULsNfA4gflT30Bw7LPvS2
5u3+TwpKzEKKVlVFnBCP9a+EXwbf8l41f7j4DVjchnL61XaJpCdmQttadHTCIayP
7y8s9ueBSzSLZJ1lR9WNIDD7kaSTGO7ybTOaahC0pQTLsJO9mAXggVdL4cFY7fAT
mw/duXzqU4Llcg/E++15NZNrZr0TBXBi8WxhzFjniaEm5jHO6KA0lzkTUWgmpgEV
sXP8OjlUZbg3nKsqmoDnZnKVIpb4A1uS6/3Uv6RmuBtWX3ffn58SUExRIyvOrN16
b8Hq4doX2+brOrTBMDZP6vXTDIC6p1f/S7Ox9+pQLc4bd2EoGHrNh60qIvaqlS+Z
OJxC4qgluGp8oz9gtRSIlgSxiUF5Jw2vf+HHAsjfPKLFLA02FP1uN1QjXG2njCLU
tz7eDV6GpvDzcDrZdENTemga9l7j1mNS4NzV2GACJdcTleUREuMB4Xtx0wXWj+fI
TZ2CEC0T++FWu5tKmyPkHByj8EYP5svgJc69o1PVLv9eiSrIQ9M=
=pGU4
-----END PGP SIGNATURE-----

--8i7WYX3y9rPsrDofusTkfVvS9mPLRZ4s8--


From nobody Sat Mar  3 07:42:33 2018
Return-Path: <petithug@acm.org>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FF09124B18 for <tram@ietfa.amsl.com>; Sat,  3 Mar 2018 07:42:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.441
X-Spam-Level: 
X-Spam-Status: No, score=-0.441 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eYI9MzGyUTrK for <tram@ietfa.amsl.com>; Sat,  3 Mar 2018 07:42:29 -0800 (PST)
Received: from implementers.org (unknown [IPv6:2001:4b98:dc0:45:216:3eff:fe7f:7abd]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35F3C1200F1 for <tram@ietf.org>; Sat,  3 Mar 2018 07:42:29 -0800 (PST)
Received: from [IPv6:2601:648:8301:730f:b138:267a:383f:dbfc] (unknown [IPv6:2601:648:8301:730f:b138:267a:383f:dbfc]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 51D27AE8D9; Sat,  3 Mar 2018 16:42:26 +0100 (CET)
To: "Asveren, Tolga" <tasveren@rbbn.com>, "Gonzalo Salgueiro (gsalguei@cisco.com)" <gsalguei@cisco.com>, "tram@ietf.org" <tram@ietf.org>
References: <CY4PR03MB316039CC07807621C64AFE39A5C90@CY4PR03MB3160.namprd03.prod.outlook.com>
From: Marc Petit-Huguenin <petithug@acm.org>
Message-ID: <10ce3dde-2401-dc4f-e231-13678f6494d1@acm.org>
Date: Sat, 3 Mar 2018 07:42:23 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CY4PR03MB316039CC07807621C64AFE39A5C90@CY4PR03MB3160.namprd03.prod.outlook.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="wVrMZrybkg8uGWVuCytAzzM8vaYcrURJ7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/ZSRty7XPKIdvrAGClQiHLwDoytw>
Subject: Re: [tram] draft-ietf-tram-stun-pmtud-06 review
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2018 15:42:31 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--wVrMZrybkg8uGWVuCytAzzM8vaYcrURJ7
Content-Type: multipart/mixed; boundary="RD8OExxOWmf9PhcNnuDYqza6aaioASB09";
 protected-headers="v1"
From: Marc Petit-Huguenin <petithug@acm.org>
To: "Asveren, Tolga" <tasveren@rbbn.com>,
 "Gonzalo Salgueiro (gsalguei@cisco.com)" <gsalguei@cisco.com>,
 "tram@ietf.org" <tram@ietf.org>
Message-ID: <10ce3dde-2401-dc4f-e231-13678f6494d1@acm.org>
Subject: Re: [tram] draft-ietf-tram-stun-pmtud-06 review
References: <CY4PR03MB316039CC07807621C64AFE39A5C90@CY4PR03MB3160.namprd03.prod.outlook.com>
In-Reply-To: <CY4PR03MB316039CC07807621C64AFE39A5C90@CY4PR03MB3160.namprd03.prod.outlook.com>

--RD8OExxOWmf9PhcNnuDYqza6aaioASB09
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Thanks for the review, please see inline.

As the cutoff is Monday afternoon, I'll publish -07 just after sending th=
is email.

On 02/17/2018 09:40 PM, Asveren, Tolga wrote:
> Marc, Gonzalo,
>=20
> Some comments/questions for draft-ietf-tram-stun-pmtud-06:
>=20
> i- 4.
>=20
>   Implementations supporting this specification MUST implement the
>    server side of both the Simple Probing mechanism (Section 4.1) and
>    the Complete Probing mechanism (Section 4.2).
>    Implementations supporting this specification MUST implement the
>    client side of the Complete Probing mechanism.  They MAY implement
>    the client side of the Simple Probing mechanism.
>=20
> I don't see the rationale behind mandating this behavior. Such semantic=
s in general are taken care of in the context of a capability negotiation=
 mechanism, which this document does not specify. As it stands right now,=
 I think this is best left to local policy and bilateral agreements and I=
 would suggest not to use anything stronger than "RECOMMEND".

It took me some time to remember why that was the case.  IIRC, one of the=
 reasons of doing this is because of the implicit probe support in sectio=
n 5.2.  Because there is no explicit signaling there, we need the server =
side (which was previously the client side) to be ready to respond to bot=
h Simple and Complete Probing.  Hence the "server must do both, client ch=
oose what they want to do" rule.

The other reason is that if we let implementers choose, then Complete Pro=
bing - which is the correct way of doing probing - will never be used.

>=20
> ii- 4.1
> DF bit set over UDP.
> =3D=3D>
> DF bit in IP Header.
> Right?  (the same in 4.2)

Not really, the Probe Request is still sent over UDP, so I changed the te=
xt to that (twice):

 The Simple Probing mechanism is implemented by sending a Probe
 Request with a PADDING [RFC5780] attribute over UDP with the DF bit
 set in the IP header.  A router on the path to the server can reject
 this request with an ICMP message or drop it.

 The Complete Probing mechanism is implemented by sending one or more
 Probe Indications with a PADDING attribute over UDP with the DF bit
 set in the IP header followed by a Report Request to the same server.

>=20
> iii- 4.1.1
> A client MUST NOT send a probe if it does not have knowledge that the
>    server supports this specification.  This is done either by external=

>    signalling or by a mechanism specific to the UDP protocol to which
>    PMTUD capabilities are added or by one of the mechanisms specified i=
n
>    Section 5.
> I suggest adding text for possible use of local policy/bilateral agreem=
ents for this purpose.

I am not sure what to add to what is said.  Do you have text to suggest?

>=20
> iv-  4.2
> Some protocols may already have a way of identifying each individual
>    UDP packet, in which case these identifiers SHOULD be used in the
>    IDENTIFIERS attribute of the Report Response.
> What is meant here as "some protocols"? Are you referring  to what is c=
arried as payload of UDP or what is used below UDP?

The former.  I changed the text to "application layer protocols:"

>=20
> v- 4.2
> In the first packet identification mechanism, the server computes a
>    checksum over each packet received and sends back to the sender the
>    list of checksums ordered chronologically.  The client compares this=

>    list to its own list of checksums.
> What if there are two probes with the same checksum right after each ot=
her and one of them is lost? How can client disambiguate such a case in  =
the response?

I am not sure to get the problem here.  The sender keeps a chronologicall=
y ordered list of the checksums of the sent packets (data and probes), so=
 in that case there is a sequence of two identical checksums in that list=
=2E  The server sends back a list of checksums, but with only one of that=
 value (or even 0).  The loss can be detected.

>=20
> v- 7
> The Simple Probing mechanism may be used without authentication
>    because this usage by itself cannot trigger an amplification attack
>    because the Probe Response is smaller than the Probe Request.
> Isn't the same true for Sum(Probe Requests) > (Report Response)?

I think that mechanism was set following a review that was worried about =
amplification attack.  We have the simple probe mechanism without authent=
ication to keep the barrier to entry very low, i.e. the minimum required =
implementation possible.

Security expert can chime in.

>=20
> vii- nit
> =3D=3D The copyright year in the IETF Trust and authors Copyright Line =
does not
>      match the current year
>=20
>   -- The document date (September 1, 2017) is 169 days in the past.  Is=
 this
>      intentional?

Will be upgraded with the next publication.

--=20
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: https://marc.petit-huguenin.org
Profile: https://www.linkedin.com/in/petithug


--RD8OExxOWmf9PhcNnuDYqza6aaioASB09--

--wVrMZrybkg8uGWVuCytAzzM8vaYcrURJ7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEBSI+IuCHU8MsI1GjKcRFldZqfsQFAlqawmAACgkQKcRFldZq
fsTmgw/9Fa/oVMbFaFpZCDn/euiEMUEGsuimXSOs0+mw2c0xG0oCcIbCMzBtIG7Z
TNcEtNp3bUvcj8hzKeSward4erFy+IG2WfYR02mlOKx53osNWJ0n72BAJctfWSLk
UTm7r8+/qf89B7Rc7i8Mupokrrp/az4iv2O3pD0ZQbYFnpvx/7oYSL/7CIzIDvsa
LgFnVijiMCw84XeIFHTA0nxmITYC7PdirbJ9jxQWpHz6YrbLyu/G3k7BUNKeV8OR
CeCpD5PAIDF2fGkQijBqzZ2jQVwHb9up0DEb70WSgGAEA3rh8gfVRo2owInyY3E+
OQMX+8xkvzGPQO7ZhtV0NRj7WAn6ZmArAYHRS2IXisLGyZAIp7fn8Vvks/AGhqKa
g/qm/o+MopNBOfdURDN1dtqLKDR7oyhKZOCij0+6VCI72kPWQKz4TM3OmuLBIJ3S
oRQDBMveuYzmNQxY86NNf6nrpAvy8xzf6ZuNLrVBd1MOCX/cU1PDpdcnX62vJCg2
eHdD6uu9am8Kq9JpmV5AWqPKtIPce8lHyhzswtVxnRY7xYLO2ShHb1oF/SJ44L/A
RMZKhRrLcXRse0Ximsyekdkd+0a153L2A9e6jd3dGmfa9F2mZ6fN9nZNEiaa1jc0
r6nzNcMpQpaYWeDm0L7hxgm2TTrK0yOeYQj0mgRhjTcK5UuQIlA=
=mSS8
-----END PGP SIGNATURE-----

--wVrMZrybkg8uGWVuCytAzzM8vaYcrURJ7--


From nobody Sat Mar  3 07:46:24 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tram@ietf.org
Delivered-To: tram@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 02A171200F1; Sat,  3 Mar 2018 07:46:23 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: tram@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.73.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152009198294.8270.17354350637769432008@ietfa.amsl.com>
Date: Sat, 03 Mar 2018 07:46:23 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/f_3ghRbZR3NBdSaVwxnI1bWct54>
Subject: [tram] I-D Action: draft-ietf-tram-stun-pmtud-07.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2018 15:46:23 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the TURN Revised and Modernized WG of the IETF.

        Title           : Path MTU Discovery Using Session Traversal Utilities for NAT (STUN)
        Authors         : Marc Petit-Huguenin
                          Gonzalo Salgueiro
	Filename        : draft-ietf-tram-stun-pmtud-07.txt
	Pages           : 17
	Date            : 2018-03-03

Abstract:
   This document describes a Session Traversal Utilities for NAT (STUN)
   Usage for Path MTU Discovery (PMTUD) between a client and a server.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tram-stun-pmtud/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-tram-stun-pmtud-07
https://datatracker.ietf.org/doc/html/draft-ietf-tram-stun-pmtud-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-tram-stun-pmtud-07


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Sun Mar  4 04:50:51 2018
Return-Path: <TirumaleswarReddy_Konda@mcafee.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28AC412AF83 for <tram@ietfa.amsl.com>; Sun,  4 Mar 2018 04:50:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mcafee.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AK0zK7eIUwro for <tram@ietfa.amsl.com>; Sun,  4 Mar 2018 04:50:29 -0800 (PST)
Received: from DNVWSMAILOUT1.mcafee.com (dnvwsmailout1.mcafee.com [161.69.31.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAC5612D779 for <tram@ietf.org>; Sun,  4 Mar 2018 04:50:28 -0800 (PST)
X-NAI-Header: Modified by McAfee Email Gateway (5500)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mcafee.com; s=s_mcafee; t=1520167828; h=From: To:Subject:Thread-Topic:Thread-Index:Date: Message-ID:References:In-Reply-To:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: dlp-product:dlp-version:dlp-reaction:authentication-results: x-originating-ip:x-ms-publictraffictype:x-microsoft-exchange-diagnostics: x-ms-exchange-antispam-srfa-diagnostics:x-ms-office365-filtering-correlation-id: x-microsoft-antispam:x-ms-traffictypediagnostic: x-microsoft-antispam-prvs:x-exchange-antispam-report-test: x-exchange-antispam-report-cfa-test:x-forefront-prvs: x-forefront-antispam-report:received-spf:x-microsoft-antispam-message-info: spamdiagnosticoutput:spamdiagnosticmetadata: Content-Type:Content-Transfer-Encoding:MIME-Version: X-MS-Exchange-CrossTenant-Network-Message-Id: X-MS-Exchange-CrossTenant-originalarrivaltime: X-MS-Exchange-CrossTenant-fromentityheader: X-MS-Exchange-CrossTenant-id:X-MS-Exchange-Transport-CrossTenantHeadersStamped: X-OriginatorOrg:X-NAI-Spam-Flag:X-NAI-Spam-Threshold: X-NAI-Spam-Score:X-NAI-Spam-Version; bh=b UUMlyADf+ZTIkj+3ae8dBf+fcRytWxNRMQU/Dqw0b o=; b=Rrk0owOFBn3xZHLYVhb6FZTywSq/2UY4o3XNVoSZtGZO iudwU8fCqk8wNTIYiRvaNLgnUm30BRDLEtJNDM0rM3GraTXMMK l5tbDfV7Mng2Gk0Kg1n5iNO8xDev5OopeGjOlsJHAb+f/qO9dE TGQWDoCfzcf5T2bQMe10tmP5qpg=
Received: from DNVEXAPP1N05.corpzone.internalzone.com (unknown [10.44.48.89]) by DNVWSMAILOUT1.mcafee.com with smtp (TLS: TLSv1/SSLv3,256bits,ECDHE-RSA-AES256-SHA384) id 1c82_be2f_7392b191_fec0_466e_b34a_ff4f9a8895d9; Sun, 04 Mar 2018 06:50:27 -0600
Received: from DNVEXUSR1N11.corpzone.internalzone.com (10.44.48.84) by DNVEXAPP1N05.corpzone.internalzone.com (10.44.48.89) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Sun, 4 Mar 2018 05:50:26 -0700
Received: from DNVEXAPP1N05.corpzone.internalzone.com (10.44.48.89) by DNVEXUSR1N11.corpzone.internalzone.com (10.44.48.84) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Sun, 4 Mar 2018 05:50:25 -0700
Received: from DNVO365EDGE2.corpzone.internalzone.com (10.44.176.74) by DNVEXAPP1N05.corpzone.internalzone.com (10.44.48.89) with Microsoft SMTP Server (TLS) id 15.0.1347.2 via Frontend Transport; Sun, 4 Mar 2018 05:50:25 -0700
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (10.44.176.241) by edge.mcafee.com (10.44.176.74) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Sun, 4 Mar 2018 05:50:24 -0700
Received: from BN6PR16MB1425.namprd16.prod.outlook.com (10.172.207.19) by BN6PR16MB1699.namprd16.prod.outlook.com (10.172.28.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.548.13; Sun, 4 Mar 2018 12:50:23 +0000
Received: from BN6PR16MB1425.namprd16.prod.outlook.com ([10.172.207.19]) by BN6PR16MB1425.namprd16.prod.outlook.com ([10.172.207.19]) with mapi id 15.20.0548.014; Sun, 4 Mar 2018 12:50:23 +0000
From: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>
To: Marc Petit-Huguenin <petithug@acm.org>, "tram@ietf.org" <tram@ietf.org>
Thread-Topic: [tram] Review of TURNbis-11
Thread-Index: AQHTS1VEMV/cplA80E+CbiTeE9FOmaOcXoOggABdRYCAAAT7EIAhhN4AgAKSMoA=
Date: Sun, 4 Mar 2018 12:50:23 +0000
Message-ID: <BN6PR16MB14253E401210DF0235668335EADB0@BN6PR16MB1425.namprd16.prod.outlook.com>
References: <325ddd79-ef98-c8ce-de50-1ef3878cd433@acm.org> <DM5PR16MB17882606F7602CEE66009903EAF20@DM5PR16MB1788.namprd16.prod.outlook.com> <c7716d08-f265-9ce9-ed2a-513ea0ddade6@acm.org> <DM5PR16MB1788777DA4671DD256BBE230EAF20@DM5PR16MB1788.namprd16.prod.outlook.com> <d496aa92-6c68-53f4-efca-34ac2880cfbc@acm.org>
In-Reply-To: <d496aa92-6c68-53f4-efca-34ac2880cfbc@acm.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 11.0.200.100
dlp-reaction: no-action
authentication-results: spf=none (sender IP is ) smtp.mailfrom=TirumaleswarReddy_Konda@McAfee.com; 
x-originating-ip: [122.167.17.10]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR16MB1699; 7:KqPSAHs2wGbyqA3Ya2C7i4Voah7y0jVi2tw6EbX2enuAMhs2H9u5pwbuYzS9B0TR1980DpklV1zjCTZHjqrMZBLChAMn7wOwM4jqp28eLk6gkPTA899EETmVV0hd2SbmAYyu3aPitG/WjRG/fU89sfTx9ggzwfoEJKHf5EZLsC0Jdcffef9ejKP1GMFDVuzlmQsq5xpyKzQKsK6jdqHBfkDAzAW0OSshZUUqfiEdk6XV3LW15NuYhyzAqUZz4a6k
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 003d3c42-017a-4c7b-29bf-08d581ce7f07
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:BN6PR16MB1699; 
x-ms-traffictypediagnostic: BN6PR16MB1699:
x-microsoft-antispam-prvs: <BN6PR16MB16993BA5DD3E9D1751AD3CB6EADB0@BN6PR16MB1699.namprd16.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(788757137089)(128460861657000)(213716511872227)(81160342030619)(123452027830198);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040501)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(10201501046)(3231220)(944501244)(52105095)(6041288)(20161123562045)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123560045)(6072148)(201708071742011); SRVR:BN6PR16MB1699; BCL:0; PCL:0; RULEID:; SRVR:BN6PR16MB1699; 
x-forefront-prvs: 060166847D
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(39380400002)(39830400003)(366004)(346002)(376002)(51444003)(13464003)(252514010)(199004)(189003)(32952001)(229853002)(6246003)(966005)(93886005)(97736004)(99286004)(55016002)(478600001)(305945005)(7736002)(6436002)(6116002)(2950100002)(80792005)(3846002)(110136005)(53936002)(6306002)(2501003)(14454004)(76176011)(3660700001)(9686003)(72206003)(74316002)(7696005)(45080400002)(59450400001)(81166006)(81156014)(8676002)(26005)(2906002)(102836004)(316002)(86362001)(8936002)(6506007)(186003)(53546011)(106356001)(3280700002)(5660300001)(2900100001)(66066001)(105586002)(77096007)(33656002)(68736007)(25786009)(85282002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR16MB1699; H:BN6PR16MB1425.namprd16.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: McAfee.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: rprYmiLh1rioQ/HtiE5dRCHYI/tM/io1JoFXQ1NbN/volIIbD6+vM9/HlWnybybjM805IUbYS/hAOC6jBMoTo/ywyLFxWMMXTEdaRf7VrEXynxYsd6ZJV0vpxLKYFmp/UgS6sxYQ+qjDtZ1qN1AB/KunGSxKWHXBCicCHAJFgVQv6bG/krilLzJZFcEXJgZUxVwGL5DnQJgYCM3PjVL1/RO14kpUucpfVI8kOPYNx6e690+iZNwlobI1LHTN4GdIBtVdzfx8lEm7BFAqgakLB4TBePzENYNSpZ90J1TCG2XRworUVMtrEX5fIRAAIXY/TirY+qVQb6bFTvb+IRDgzQ==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 003d3c42-017a-4c7b-29bf-08d581ce7f07
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Mar 2018 12:50:23.5965 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4943e38c-6dd4-428c-886d-24932bc2d5de
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR16MB1699
X-OriginatorOrg: mcafee.com
X-NAI-Spam-Flag: NO
X-NAI-Spam-Threshold: 15
X-NAI-Spam-Score: 0
X-NAI-Spam-Version: 2.3.0.9418 : core <6234> : inlines <6449> : streams <1780501> : uri <2602170>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/X7UOsBw-Zn5GDyYpQJQZM_qJMzI>
Subject: Re: [tram] Review of TURNbis-11
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Mar 2018 12:50:38 -0000

VGhhbmtzIE1hcmMsIGZpeGVkIHRoZSBkaXNjcmVwYW5jeS4NCg0KLVRpcnUNCg0KPiAtLS0tLU9y
aWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBNYXJjIFBldGl0LUh1Z3VlbmluIFttYWlsdG86
cGV0aXRodWdAYWNtLm9yZ10NCj4gU2VudDogU2F0dXJkYXksIE1hcmNoIDMsIDIwMTggMzowNCBB
TQ0KPiBUbzogS29uZGEsIFRpcnVtYWxlc3dhciBSZWRkeQ0KPiA8VGlydW1hbGVzd2FyUmVkZHlf
S29uZGFATWNBZmVlLmNvbT47IHRyYW1AaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IFt0cmFtXSBS
ZXZpZXcgb2YgVFVSTmJpcy0xMQ0KPiANCj4gQXMgc3VnZ2VzdGVkIGJ5IEJyYW5kb24sIEkgcmV2
aWV3ZWQgdHVybmJpcy0xNCBmb3IgdGhlIG1vZGlmaWNhdGlvbnMgYWdyZWVkDQo+IG9uIGJlbG93
LCBhbmQgZm91bmQgb25lIGRpc2NyZXBhbmN5LiAgU2VlIGlubGluZS4NCj4gDQo+IE9uIDAyLzA5
LzIwMTggMDU6NDUgQU0sIEtvbmRhLCBUaXJ1bWFsZXN3YXIgUmVkZHkgd3JvdGU6DQo+ID4+IC0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4+IEZyb206IHRyYW0gW21haWx0bzp0cmFtLWJv
dW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBNYXJjIFBldGl0LQ0KPiA+PiBIdWd1ZW5pbg0K
PiA+PiBTZW50OiBGcmlkYXksIEZlYnJ1YXJ5IDksIDIwMTggNjo1NCBQTQ0KPiA+PiBUbzogS29u
ZGEsIFRpcnVtYWxlc3dhciBSZWRkeQ0KPiA+PiA8VGlydW1hbGVzd2FyUmVkZHlfS29uZGFATWNB
ZmVlLmNvbT47IHRyYW1AaWV0Zi5vcmcNCj4gPj4gU3ViamVjdDogUmU6IFt0cmFtXSBSZXZpZXcg
b2YgVFVSTmJpcy0xMQ0KPiA+Pg0KPiA+PiBIaSwNCj4gPj4NCj4gPj4gTXkgcmVzcG9uc2VzIGlu
bGluZS4NCj4gPj4NCj4gPj4gT24gMDIvMDkvMjAxOCAwMzo1MyBBTSwgS29uZGEsIFRpcnVtYWxl
c3dhciBSZWRkeSB3cm90ZToNCj4gPj4+IEhpIE1hcmMsDQo+ID4+Pg0KPiA+Pj4gUGxlYXNlIHNl
ZSBpbmxpbmUNCj4gPj4+DQo+ID4+Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPj4+
PiBGcm9tOiB0cmFtIFttYWlsdG86dHJhbS1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2Yg
TWFyYyBQZXRpdC0NCj4gPj4+PiBIdWd1ZW5pbg0KPiA+Pj4+IFNlbnQ6IFN1bmRheSwgT2N0b2Jl
ciAyMiwgMjAxNyAxMDoxNiBQTQ0KPiA+Pj4+IFRvOiB0cmFtQGlldGYub3JnDQo+ID4+Pj4gU3Vi
amVjdDogW3RyYW1dIFJldmlldyBvZiBUVVJOYmlzLTExDQo+ID4+Pj4NCj4gPj4+PiBUaGlzIGlz
IHRoZSBzZWNvbmQgcGFydCBvZiBteSByZXZpZXcgb2YgVFVSTmJpcy0xMSwgaS5lLiBldmVyeXRo
aW5nDQo+ID4+Pj4gYnV0IHRoZSBkdWFsIGFsbG9jYXRpb24gcGFydC4NCj4gPj4+Pg0KPiA+Pj4+
IC0gU2VjdGlvbiAyLjEsIGxhc3QgcGFyYWdyYXBoOg0KPiA+Pj4+DQo+ID4+Pj4gTWF5IGJlIGEg
cmVmZXJlbmNlIHRvIFJGQyA1NzY0IGFuZCBSRkMgNzk4MyBjYW4gYmUgdXNlZnVsIGhlcmUuDQo+
ID4+Pj4gU2FtZSBpbiBzZWN0aW9uIDQsIHNlY29uZCBwYXJhZ3JhcGggYW5kIGZvbGxvd2luZy4g
IFNhbWUgYXQgdGhlDQo+ID4+Pj4gYmVnaW5uaW5nIG9mIHNlY3Rpb24gMTEuICBBZ2FpbiBpbiBz
ZWN0aW9uIDExLjYgKGlmIG11bHRpcGxleGVkLA0KPiA+Pj4+IHRoZSBtZXNzYWdlIGluIHRoZSBy
ZXNlcnZlZCByYW5nZSBpcyBub3QgbmVjZXNzYXJpbHkgZGlzY2FyZGVkKS4NCj4gPj4+DQo+ID4+
PiBFdmVuIGlmIHRoZSBzYW1lIGhvc3QgdHJhbnNwb3J0IGFkZHJlc3MgaXMgdXNlZCBmb3Igb3Ro
ZXIgcHJvdG9jb2xzLA0KPiA+PiBpbmNvbWluZyBwYWNrZXRzIHRvIHRoZSBUVVJOIGNoYW5uZWwg
Y2FuIGJlIGlkZW50aWZpZWQgYnkganVzdA0KPiA+PiBleGFtaW5pbmcgdGhlIHNvdXJjZSBhZGRy
ZXNzIG9mIHRoZSBwYWNrZXQuDQo+ID4+PiBNYXkgYmUgSSBhbSBtaXNzaW5nIHNvbWV0aGluZywg
SSBkaWQgbm90IGdldCBhIHByb2JsZW0gPw0KPiA+Pg0KPiA+PiBJdCB3YXMganVzdCBhbiBhdHRl
bXB0IHRvIG1ha2UgVFVSTiBpbXBsZW1lbnRlcnMgYXdhcmUgb2YgdGhlIGRlbXV4DQo+ID4+IGlz
c3Vlcy4NCj4gPg0KPiA+IEdvdCBpdCwgYWRkZWQgdGhlIGZvbGxvd2luZyBsaW5lOg0KPiA+IFRo
ZSBhbGdvcml0aG0gb2YgZGVtdWx0aXBsZXhpbmcgcGFja2V0cyByZWNlaXZlZCBmcm9tIG11bHRp
cGxlDQo+ID4gcHJvdG9jb2xzIGlzIGRpc2N1c3NlZCBpbiBbUkZDNzk4M10uDQo+ID4NCj4gPj4N
Cj4gPj4+DQo+ID4+Pj4NCj4gPj4+PiAtIFNlY3Rpb24gMi4yLCBmaXJzdCBwYXJhZ3JhcGg6DQo+
ID4+Pj4NCj4gPj4+PiBJIHRoaW5rIHRoYXQgYW4gaW5mb3JtYXRpdmUgcmVmZXJlbmNlIHRvIFJG
QyA3NjM1IG1heSBiZSB1c2VmdWwNCj4gPj4+PiB0aGVyZSwgYXMgYWx0ZXJuYXRpdmUgdG8gdGhl
IFNUVU4gYXV0aGVudGljYXRpb24gbWVjaGFuaXNtLg0KPiA+Pj4NCj4gPj4+IFllcywgdXBkYXRl
ZC4NCj4gPj4+DQo+ID4+Pj4NCj4gPj4+PiAtIFNlY3Rpb24gMi45Og0KPiA+Pj4+DQo+ID4+Pj4g
VGhlIHdob2xlIDIuOSBzZWN0aW9uIGFuZCBzdWJzZWN0aW9ucyBsb29rcyBub3JtYXRpdmUgYW5k
IHNvIHNob3VsZA0KPiA+Pj4+IGJlIG1vdmVkIGFmdGVyIHNlY3Rpb24gMywgcGVyaGFwcyBvbiB0
aGVpciBvd24gdG9wIGxldmVsIHNlY3Rpb24uDQo+ID4+Pg0KPiA+Pj4gRG9uZS4NCj4gPj4+DQo+
ID4+Pj4NCj4gPj4+PiAtIFNlY3Rpb24gNCwgNHRoIHBhcmFncmFwaDoNCj4gPj4+Pg0KPiA+Pj4+
IEkgd291bGQgcmVwbGFjZSAiRm9yIGVhY2ggYWxsb2NhdGlvbi4uLiIgYnkgIkZvciBlYWNoIEFs
bG9jYXRlDQo+ID4+Pj4gcmVxdWVzdC4uLiIsIGJlY2F1c2Ugb2YgdGhlIGR1YWwgYWxsb2NhdGlv
biBmZWF0dXJlLg0KPiA+Pj4NCj4gPj4+IEZpeGVkLg0KPiA+Pj4NCj4gPj4+Pg0KPiA+Pj4+IC0g
U2VjdGlvbiA0LCAxMnRoIHBhcmFncmFwaDoNCj4gPj4+Pg0KPiA+Pj4+IFNob3VsZCBtYWtlIGNs
ZWFyIGNsZWFyIHRoYXQgVURQIGNvdmVycyBhbHNvIERUTFMuDQo+ID4+Pg0KPiA+Pj4gWWVzLCB1
cGRhdGVkLg0KPiANCj4gSSBjYW5ub3QgZmluZCB0aGlzIHVwZGF0ZSBpbiB0dXJuLTE0Lg0KPiAN
Cj4gPj4+DQo+ID4+Pj4NCj4gPj4+PiAtIFNlY3Rpb24gNi4xLCAybmQgcGFyYWdyYXBoOg0KPiA+
Pj4+DQo+ID4+Pj4gSWYgdGhlIHBvcnQgaXMgbXVsdGlwbGV4ZWQgd2l0aCBvdGhlciBwcm90b2Nv
bHMgKFJUUCwgV2ViUnRjLA0KPiA+Pj4+IGV0Yy4uKSB0aGVuIGl0IGhhcyB0byByZXVzZSBhbiBl
eGlzdGluZyBzb2NrZXQuICBUaGUgZG9jdW1lbnQgc2hvdWxkDQo+IGV4cGxhaW4gdGhpcy4NCj4g
Pj4+DQo+ID4+PiBJdCdzIGFscmVhZHkgY292ZXJlZCBpbiBTZWN0aW9uIDIuMSAobGFzdCBwYXJh
Z3JhcGgpLg0KPiA+Pj4NCj4gPj4+Pg0KPiA+Pj4+IC0gU2VjdGlvbiA2LjIsIDN0aCBwYXJhZ3Jh
cGg6DQo+ID4+Pj4NCj4gPj4+PiBJcyBpdCB0aW1lIHRvIHJlY29tbWVuZCBEVExTIGluc3RlYWQg
b2YgVURQPyAgSW4gdGhhdCBjYXNlIHdlIG5lZWQNCj4gPj4+PiB0byBtYWtlIERUTFMgbWFuZGF0
b3J5IGluIHNlY3Rpb24gNCBwYXJhZ3JhcGggMTEgKGFuZCBJIHN1cHBvcnQNCj4gPj4+PiB0aGF0
DQo+ID4+IGNoYW5nZSkuDQo+ID4+Pg0KPiA+Pj4gTm8sIERUTFMgaGFzIGJvdGggYWR2YW50YWdl
cyAoZS5nLiBkaWN0aW9uYXJ5IGF0dGFjaykgIGFuZA0KPiA+Pj4gZGlzYWR2YW50YWdlcw0KPiA+
PiAoZS5nLiBkb3VibGUgZW5jcnlwdGlvbiBvZiBhcHBsaWNhdGlvbiBkYXRhKS4NCj4gPj4NCj4g
Pj4gT0suDQo+ID4+DQo+ID4+Pg0KPiA+Pj4+DQo+ID4+Pj4gLSBTZWN0aW9uIDYuNCwgc2Vjb25k
IGJ1bGxldDoNCj4gPj4+Pg0KPiA+Pj4+IFJlcGxhY2UgIi4uLlNSViBwcm9jZWR1cmVzKS4iIHdp
dGggIi4uLkROUyByZXNvbHV0aW9uIHByb2NlZHVyZXMpLiINCj4gPj4+DQo+ID4+PiBBbnkgc3Bl
Y2lmaWMgcmVhc29uIGZvciB0aGUgcmVwbGFjZW1lbnQgPw0KPiA+Pg0KPiA+PiBUaGlzIGlzIHRv
IG5vdCBleGNsdWRlIE5QQVRSIHByb2NlZHVyZXMgKFJGQyA1OTI4KS4NCj4gPg0KPiA+IFVwZGF0
ZWQgc2Vjb25kIGJ1bGxldC4NCj4gPg0KPiA+IENoZWVycywNCj4gPiAtVGlydQ0KPiA+DQo+ID4+
DQo+ID4+Pg0KPiA+Pj4+DQo+ID4+Pj4gLSBTZWN0aW9ucyAxNCwgMTUgYW5kIDE2Og0KPiA+Pj4+
DQo+ID4+Pj4gVGhlc2UgYXJlIG5vIGxvbmdlciBuZXcgbWV0aG9kcyBhbmQgYXR0cmlidXRlcy4g
IFNlZSBhbHNvIHRoZSBuZXh0DQo+ID4+Pj4gY29tbWVudC4NCj4gPj4+DQo+ID4+PiBGaXhlZC4N
Cj4gPj4+DQo+ID4+Pj4NCj4gPj4+PiAtIFNlY3Rpb24gMTk6DQo+ID4+Pj4NCj4gPj4+PiBIZXJl
IHlvdSBuZWVkIHRvIHVwZGF0ZSB0aGUgZXhpc3RpbmcgbWV0aG9kcywgYXR0cmlidXRlcyBhbmQg
ZXJyb3INCj4gPj4+PiBjb2RlIHNvIHRoZSBJQU5BIHJlZ2lzdHJpZXMgcG9pbnQgdG8gdGhlIFJG
Qy10by1iZSwgdGhlbiB5b3UNCj4gPj4+PiByZXF1ZXN0IGFsbG9jYXRpb24gZm9yIHRoZSBuZXcg
YXR0cmlidXRlcy4gIFNlZSBzZWN0aW9uIDE3IG9mDQo+ID4+Pj4gU1RVTmJpcyBvbiBhIHdheSB0
byBkbyB0aGF0ICh0aGF0IHdhcyBkb25lIGZvbGxvd2luZyBhIGRpc2N1c3Npb24NCj4gPj4+PiB3
aXRoIHRoZSBJQU5BDQo+ID4+IHJlcHJlc2VudGF0aXZlIGF0IGFuIElFVEYgbWVldGluZykuDQo+
ID4+Pg0KPiA+Pj4gVGhhbmtzLCB1cGRhdGVkIGRyYWZ0Lg0KPiA+Pj4NCj4gPj4+Pg0KPiA+Pj4+
IE5vdGUgdGhhdCBJQ01QIHNob3VsZCBiZSBjb21wcmVoZW5zaW9uLW1hbmRhdG9yeSwgbm90IG9w
dGlvbmFsLCBhcw0KPiA+PiB3ZQ0KPiA+Pj4+IGRvIG5vdCB3YW50IGFuIG9sZCBjbGllbnQgdG8g
cmVqZWN0IGEgRGF0YSBpbmRpY2F0aW9uIHdpdGggYW4gSUNNUA0KPiBhdHRyaWJ1dGUuDQo+ID4+
Pg0KPiA+Pj4gSWYgdGhlIGluZGljYXRpb24gY29udGFpbnMgdW5rbm93biBjb21wcmVoZW5zaW9u
LXJlcXVpcmVkDQo+ID4+PiBhdHRyaWJ1dGVzLCB0aGUNCj4gPj4gYmVoYXZpb3IgaXMgdGhlIGlu
ZGljYXRpb24gaXMgZGlzY2FyZGVkIGFuZCBwcm9jZXNzaW5nIGNlYXNlcy4NCj4gPj4+DQo+ID4+
Pj4NCj4gPj4+PiBBbHNvLCBJIGRvIG5vdCBrbm93IHdoYXQgdGhpcyBTZW5kRXJyIG1ldGhvZCBp
cy4NCj4gPj4+DQo+ID4+PiBSZW1vdmVkIFNlbmRFcnIgKHN0YWxlIGVudHJ5IGZyb20gYSBwcmV2
aW91cyB2ZXJzaW9uIG9mIHRoZSBkcmFmdCkuDQo+ID4+Pg0KPiA+Pj4+DQo+ID4+Pj4NCj4gPj4+
PiBOaXRzDQo+ID4+Pj4gLS0tLQ0KPiA+Pj4+DQo+ID4+Pj4gU2VjdGlvbiAxOg0KPiA+Pj4+DQo+
ID4+Pj4gcy9jb25uZWN0aW9uIHRvIHRoZSBJbnRlcm5ldCAuL2Nvbm5lY3Rpb24gdG8gdGhlIElu
dGVybmV0Li8NCj4gPj4+Pg0KPiA+Pj4+IFNlY3Rpb24gMi40LCBmaXJzdCBwYXJhZ3JhcGg6DQo+
ID4+Pj4NCj4gPj4+PiBUaGUgdGV4dCBzd2l0Y2hlcyBiZXR3ZWVuIHRoZSB3b3JkcyAibWVjaGFu
aXNtcyIgYW5kICJ3YXkiLg0KPiBDaG9vc2UNCj4gPj4+PiBvbmUuDQo+ID4+Pj4NCj4gPj4+PiBT
ZWN0aW9uIDYuMiwgaXRlbSA4Og0KPiA+Pj4+DQo+ID4+Pj4gcy9BRERJVElPTkFMLSBBRERSRVNT
LUZBTUlMWS9BRERJVElPTkFMLUFERFJFU1MtRkFNSUxZLw0KPiA+Pj4+DQo+ID4+Pj4gU2VjdGlv
biAxMi4xLCAiUHJlZmVycmVkIEJlaGF2aW9yIg0KPiA+Pj4+DQo+ID4+Pj4gcy9MYWJlbCBGaWVs
ZFtSRkMzNjk3XS9MYWJlbCBGaWVsZCBbUkZDMzY5N10vDQo+ID4+Pj4NCj4gPj4+PiBTZWN0aW9u
IDIxOg0KPiA+Pj4+DQo+ID4+Pj4gcy9BRERSRVNTLUVSUlItQ09ERS9BRERSRVNTLUVSUi1DT0RF
Lw0KPiA+Pj4+DQo+ID4+Pj4gU2VjdGlvbiAyMjoNCj4gPj4+Pg0KPiA+Pj4+IHMvb3JnaW5hbC9v
cmlnaW5hbC8NCj4gPj4+DQo+ID4+PiBUaGFua3MsIGZpeGVkIGFsbCBhYm92ZSBuaXRzLg0KPiA+
Pj4NCj4gDQo+IC0tDQo+IE1hcmMgUGV0aXQtSHVndWVuaW4NCj4gRW1haWw6IG1hcmNAcGV0aXQt
aHVndWVuaW4ub3JnDQo+IEJsb2c6IGh0dHBzOi8vbWFyYy5wZXRpdC1odWd1ZW5pbi5vcmcNCj4g
UHJvZmlsZTogaHR0cHM6Ly93d3cubGlua2VkaW4uY29tL2luL3BldGl0aHVnDQoNCg==


From nobody Sun Mar  4 05:31:31 2018
Return-Path: <TirumaleswarReddy_Konda@mcafee.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 918E81270AC for <tram@ietfa.amsl.com>; Sun,  4 Mar 2018 05:31:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mcafee.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xWWvEy1IpXU9 for <tram@ietfa.amsl.com>; Sun,  4 Mar 2018 05:31:27 -0800 (PST)
Received: from DNVWSMAILOUT1.mcafee.com (dnvwsmailout1.mcafee.com [161.69.31.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A6961270AB for <tram@ietf.org>; Sun,  4 Mar 2018 05:31:27 -0800 (PST)
X-NAI-Header: Modified by McAfee Email Gateway (5500)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mcafee.com; s=s_mcafee; t=1520170286; h=From: To:Subject:Thread-Topic:Thread-Index:Date: Message-ID:References:In-Reply-To:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: dlp-product:dlp-version:dlp-reaction:authentication-results: x-originating-ip:x-ms-publictraffictype:x-microsoft-exchange-diagnostics: x-ms-exchange-antispam-srfa-diagnostics:x-ms-office365-filtering-correlation-id: x-microsoft-antispam:x-ms-traffictypediagnostic: x-microsoft-antispam-prvs:x-exchange-antispam-report-test: x-exchange-antispam-report-cfa-test:x-forefront-prvs: x-forefront-antispam-report:received-spf:x-microsoft-antispam-message-info: spamdiagnosticoutput:spamdiagnosticmetadata: Content-Type:Content-Transfer-Encoding:MIME-Version: X-MS-Exchange-CrossTenant-Network-Message-Id: X-MS-Exchange-CrossTenant-originalarrivaltime: X-MS-Exchange-CrossTenant-fromentityheader: X-MS-Exchange-CrossTenant-id:X-MS-Exchange-Transport-CrossTenantHeadersStamped: X-OriginatorOrg:X-NAI-Spam-Flag:X-NAI-Spam-Level: X-NAI-Spam-Threshold:X-NAI-Spam-Score:X-NAI-Spam-Version; bh=tATePjRhHMUMdtluIwchtW8Pxt0c5wU5igulvo 4LpOc=; b=oR80RojKtk03X+TQue8sUstIw1yWNynUg4xaRZQ7 0AMZBwWd43njO+w6ZMNX8zgEXo90gXwVVNIqbQW92cRRoQYEzM unWyniukmMfK3wbNz5B5azaaBOh9cJTGUKh+ZbGLi7Ebs01qo9 1Hu6W2z+Qx6kDce/JeodpJ9PDhHIcK4=
Received: from DNVEXAPP1N06.corpzone.internalzone.com (unknown [10.44.48.90]) by DNVWSMAILOUT1.mcafee.com with smtp (TLS: TLSv1/SSLv3,256bits,ECDHE-RSA-AES256-SHA384) id 1c87_2776_695c9ad8_bd48_430f_b1a6_c9b7e9a6bb1f; Sun, 04 Mar 2018 07:31:25 -0600
Received: from DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) by DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Sun, 4 Mar 2018 06:30:26 -0700
Received: from DNVEX10N01.corpzone.internalzone.com (10.44.82.192) by DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) with Microsoft SMTP Server (TLS) id 15.0.1347.2 via Frontend Transport; Sun, 4 Mar 2018 06:30:26 -0700
Received: from DNVO365EDGE1.corpzone.internalzone.com (10.44.176.66) by DNVEX10N01.corpzone.internalzone.com (10.44.82.192) with Microsoft SMTP Server (TLS) id 14.3.361.1; Sun, 4 Mar 2018 06:30:25 -0700
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (10.44.176.242) by edge.mcafee.com (10.44.176.66) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Sun, 4 Mar 2018 06:30:20 -0700
Received: from BN6PR16MB1425.namprd16.prod.outlook.com (10.172.207.19) by BN6PR16MB1393.namprd16.prod.outlook.com (10.172.207.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.548.13; Sun, 4 Mar 2018 13:30:24 +0000
Received: from BN6PR16MB1425.namprd16.prod.outlook.com ([10.172.207.19]) by BN6PR16MB1425.namprd16.prod.outlook.com ([10.172.207.19]) with mapi id 15.20.0548.014; Sun, 4 Mar 2018 13:30:24 +0000
From: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>
To: Marc Petit-Huguenin <petithug@acm.org>, "tram@ietf.org" <tram@ietf.org>
Thread-Topic: [tram] Review of dual allocation in TURNbis-11
Thread-Index: AQHTRFmkTUXySTsG3EGzRBQMWeAaDaLmPU1QgAnZ7oCArKMPEIAhlH+AgAKYzOA=
Date: Sun, 4 Mar 2018 13:30:23 +0000
Message-ID: <BN6PR16MB142530705DF3F28C07FAC9A2EADB0@BN6PR16MB1425.namprd16.prod.outlook.com>
References: <65c75449-152c-1ce7-7c81-460ca589d9f0@acm.org> <DM5PR16MB17881ABD54B89E14F0291C56EA4C0@DM5PR16MB1788.namprd16.prod.outlook.com> <ea84bcf9-19b6-5492-383b-18e2bc5a93bf@acm.org> <DM5PR16MB178859E2018148DBAD51635EEAF20@DM5PR16MB1788.namprd16.prod.outlook.com> <46fdf931-eb0c-c4fe-9c01-4a066134abfb@acm.org>
In-Reply-To: <46fdf931-eb0c-c4fe-9c01-4a066134abfb@acm.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 11.0.200.100
dlp-reaction: no-action
authentication-results: spf=none (sender IP is ) smtp.mailfrom=TirumaleswarReddy_Konda@McAfee.com; 
x-originating-ip: [122.167.17.10]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR16MB1393; 6:89mHMikyxc6f7ULiZYBkNArU7xOoSkUmjGwvyHRfi1kOqLg0ufS6qNNWDmh1hg6VFGWn2J2Va5sOIlpWp8bTHdvPoqrKV5iUYeX6wPPc6n6phmvPiMNWnEBztU9nmJZMwJ6EPTsZKUHRJiypevo31cr3Eo/LDzJeXeSuUHSRdZCl0t+uCjYBOncPMYc0WrKr5h9eVJVasVXk7LNqALUmfLnESL8U84/LMoP74+vTB1J5+7SNoCtrur4lziEw7or7xvG/JWf4TTZ/bVX4ZrUM7KzNvgFvbtJq6FIO95AFHfpRyejE327Z/L0H244Na+8UNlStVnFmmRBCssIRoHTHXNtZ9R560j+xv8S2eTNauUMIzllDY4xiPBzR1Oc9WNjO; 5:nZJJX7x3/OgcD38EkPc/2oUPqiPLU8AqkUFOWeiwM7EVL3pJiRSW7HF9rcn+fgSbbFG/eojlqil2czXkhJrsmVKNdePJCnkLZHoIiJDZ356+GgXl0C6wWYPyEUBQl9FS8EFhs9gTEL4Iqq7BASO2geWjFU5Y438ozRXpABVTAE0=; 24:IE3tbkyRGjswo5spMkyeVehKsqdQsP72i+KHWbvSoOpT9W7gpjrcJFG3cuB3jawE/PgjtKKGfS9SWJrCNAmIyDdMuLlrWg2PEr5o/EyC8BI=; 7:B3hPf+a7OMIVn/u7QF1SHKOV24FizNNB0skjNKYluFJ6RziW8G0lk3z0b4qn2p6VQ7rXQe1ISVfFz6vwqWlfWKWhCzFLRahCZKOx8a77Lzx8s11LstoOXYHBWebAKeCeKXIEhvkcmJ0QTV2/BhvK2OwuHCKbWEihRnRNrXwEYZmRU14PiK3v9F3IehRnmkyMCi41430L71ll1sqnBvJDw7tZargAEFhpGdUnWf7o9wegN1Js/QO68OuaZLYXX4xL
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: dac69ac6-71ba-443e-2b20-08d581d415bf
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603307)(7153060)(7193020); SRVR:BN6PR16MB1393; 
x-ms-traffictypediagnostic: BN6PR16MB1393:
x-microsoft-antispam-prvs: <BN6PR16MB1393C84C4EC1F7681E9F1342EADB0@BN6PR16MB1393.namprd16.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(128460861657000)(213716511872227)(81160342030619)(123452027830198);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040501)(2401047)(5005006)(8121501046)(10201501046)(3231220)(944501244)(52105095)(3002001)(93006095)(93001095)(6041288)(20161123558120)(20161123562045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(6072148)(201708071742011); SRVR:BN6PR16MB1393; BCL:0; PCL:0; RULEID:; SRVR:BN6PR16MB1393; 
x-forefront-prvs: 060166847D
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(39850400004)(39380400002)(346002)(376002)(366004)(13464003)(189003)(199004)(32952001)(252514010)(105586002)(97736004)(3280700002)(80792005)(55016002)(81156014)(3846002)(6116002)(2501003)(305945005)(106356001)(2950100002)(7696005)(229853002)(7736002)(53936002)(5660300001)(99286004)(6246003)(8676002)(316002)(66066001)(86362001)(76176011)(74316002)(81166006)(6436002)(33656002)(186003)(14454004)(93886005)(478600001)(8936002)(966005)(3660700001)(6506007)(53546011)(68736007)(6306002)(2900100001)(72206003)(25786009)(110136005)(102836004)(9686003)(26005)(59450400001)(45080400002)(77096007)(2906002)(85282002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR16MB1393; H:BN6PR16MB1425.namprd16.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: McAfee.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: iH/5qTiXdD2iBi26L+X7ynIUkUuLLzzK6gyPGZFc1Neil4KhyJSG3iRqRlwGXnlkcwqCkuGrs6xwjMw/LwYbRNyi3I6T0qSzTMoe6UbNyluBdonmHedhUYChZzHgWQaibBcsNf6OfcH98krUPJb2e8z32J19ZOFP/VbkWUos26bgRx4HKSXhOiNLMxnrtucTbgcMGGOYRXUGtUOXXmyLzZ4wrk3v/WEKGEOB5yX3Kuxwzdm5XDA/tg7Bs/qSGLvalKK9gBSeEyl9/ddrJaULv1zQC3bruhXQko+KQx1Ghqk4OTCA478HI0TKOLzd7JC5HuEQWLefq5Qp4nZhN1PqHA==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: dac69ac6-71ba-443e-2b20-08d581d415bf
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Mar 2018 13:30:23.8974 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4943e38c-6dd4-428c-886d-24932bc2d5de
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR16MB1393
X-OriginatorOrg: mcafee.com
X-NAI-Spam-Flag: NO
X-NAI-Spam-Level: 
X-NAI-Spam-Threshold: 15
X-NAI-Spam-Score: 0.1
X-NAI-Spam-Version: 2.3.0.9418 : core <6234> : inlines <6449> : streams <1780501> : uri <2602170>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/D0ePo8F4JTIpnP9u0Bh471zY1YI>
Subject: Re: [tram] Review of dual allocation in TURNbis-11
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Mar 2018 13:31:29 -0000

SGkgTWFyYywNCg0KUGxlYXNlIHNlZSBpbmxpbmUNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2Ut
LS0tLQ0KPiBGcm9tOiBNYXJjIFBldGl0LUh1Z3VlbmluIFttYWlsdG86cGV0aXRodWdAYWNtLm9y
Z10NCj4gU2VudDogU2F0dXJkYXksIE1hcmNoIDMsIDIwMTggMjo0NyBBTQ0KPiBUbzogS29uZGEs
IFRpcnVtYWxlc3dhciBSZWRkeQ0KPiA8VGlydW1hbGVzd2FyUmVkZHlfS29uZGFATWNBZmVlLmNv
bT47IHRyYW1AaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IFt0cmFtXSBSZXZpZXcgb2YgZHVhbCBh
bGxvY2F0aW9uIGluIFRVUk5iaXMtMTENCj4gDQo+IEFzIHN1Z2dlc3RlZCBieSBCcmFuZG9uLCBJ
IHJldmlld2VkIHR1cm5iaXMtMTQgZm9yIHRoZSBtb2RpZmljYXRpb25zIGFncmVlZA0KPiBvbiBi
ZWxvdywgYW5kIGZvdW5kIHNvbWUgZGlzY3JlcGFuY2llcy4gIFNlZSBpbmxpbmUuDQo+IA0KPiBP
biAwMi8wOS8yMDE4IDA0OjUxIEFNLCBLb25kYSwgVGlydW1hbGVzd2FyIFJlZGR5IHdyb3RlOg0K
PiA+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+PiBGcm9tOiBNYXJjIFBldGl0LUh1
Z3VlbmluIFttYWlsdG86cGV0aXRodWdAYWNtLm9yZ10NCj4gPj4gU2VudDogU3VuZGF5LCBPY3Rv
YmVyIDIyLCAyMDE3IDk6MzggUE0NCj4gPj4gVG86IEtvbmRhLCBUaXJ1bWFsZXN3YXIgUmVkZHkN
Cj4gPj4gPFRpcnVtYWxlc3dhclJlZGR5X0tvbmRhQE1jQWZlZS5jb20+OyB0cmFtQGlldGYub3Jn
DQo+ID4+IFN1YmplY3Q6IFJlOiBbdHJhbV0gUmV2aWV3IG9mIGR1YWwgYWxsb2NhdGlvbiBpbiBU
VVJOYmlzLTExDQo+ID4+DQo+ID4+IElubGluZS4NCj4gPj4NCj4gPj4gT24gMTAvMTYvMjAxNyAw
NzoxNCBQTSwgS29uZGEsIFRpcnVtYWxlc3dhciBSZWRkeSB3cm90ZToNCj4gPj4+IFRoYW5rcyBN
YXJjIGZvciB0aGUgZGV0YWlsZWQgcmV2aWV3LCBQbGVhc2Ugc2VlIGlubGluZQ0KPiA+Pj4NCj4g
Pj4+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+Pj4+IEZyb206IHRyYW0gW21haWx0
bzp0cmFtLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBNYXJjIFBldGl0LQ0KPiA+Pj4+
IEh1Z3VlbmluDQo+ID4+Pj4gU2VudDogU2F0dXJkYXksIE9jdG9iZXIgMTQsIDIwMTcgMTI6NTkg
QU0NCj4gPj4+PiBUbzogdHJhbUBpZXRmLm9yZw0KPiA+Pj4+IFN1YmplY3Q6IFt0cmFtXSBSZXZp
ZXcgb2YgZHVhbCBhbGxvY2F0aW9uIGluIFRVUk5iaXMtMTENCj4gPj4+Pg0KPiANCj4gW3NuaXBd
DQo+IA0KPiA+Pj4NCj4gPj4+Pg0KPiA+Pj4+IC0gU2VjdGlvbiA2LjINCj4gPj4+Pg0KPiA+Pj4+
IEkgd291bGQgc3VnZ2VzdCB0byBtYWtlIEFERFJFU1MtRVJST1ItQ09ERSBtb3JlIGdlbmVyaWMg
YnkNCj4gPj4gcmVuYW1pbmcNCj4gPj4+PiBpdCBhcyBXQVJOSU5HLUNPREUgYW5kIHVzZSB0aGUg
c2FtZSBmb3JtYXQgdGhhbiBmb3IgRVJST1ItQ09ERS4NCj4gPj4gVGhlbg0KPiA+Pj4+IGFsbG9j
YXRlIGEgbmV3IGVycm9yIGNvZGUgZm9yIHRoYXQgc3BlY2lmaWMgd2FybmluZy4gIEkgd291bGQN
Cj4gPj4+PiBzdWdnZXN0IHRvIHJlcXVlc3QgdGhlIDB4ODAwOSBjb2RlcG9pbnQgZm9yIHRoYXQg
YXR0cmlidXRlLg0KPiA+Pj4NCj4gPj4+IEkgZG9uJ3QgdW5kZXJzdGFuZCB0aGUgbmVlZCB0byBj
aGFuZ2UgQUREUkVTUy1FUlJPUi1DT0RFICENCj4gPj4NCj4gPj4gVG8gbWFrZSBpdCBtb3JlIGdl
bmVyaWMgYW5kIHJldXNhYmxlIGluIGZ1dHVyZSBzcGVjaWZpY2F0aW9ucy4NCj4gPg0KPiA+IEFE
RFJFU1MtRVJST1ItQ09ERSBjYW5ub3QgdXNlIHRoZSBzYW1lIGZvcm1hdCBhcyBFUlJPUi1DT0RF
LA0KPiBBRERSRVNTLUVSUk9SLUNPREUgc2lnbmFscyB0aGUgSVAgYWRkcmVzcyBmYW1pbHkgZm9y
IHdoaWNoIHRoZSB3YXJuaW5nIGlzDQo+IGdlbmVyYXRlZCArIGFsbCB0aGUgZmllbGRzIGluIHRo
ZSBFUlJPUi1DT0RFLg0KPiA+DQo+ID4+DQo+ID4+Pg0KPiA+Pj4+DQo+ID4+Pj4gQWxzbyBJIHRo
aW5rIHdlIG5lZWRzIHR3byBkaWZmZXJlbnQgd2FybmluZ3MsIG9uZSB0aGF0IHN0YXRlcyB0aGF0
DQo+ID4+Pj4gZHVhbCBhbGxvY2F0aW9uIGlzIG5vdCBhdmFpbGFibGUgaW4gYSBUVVJOYmlzIHNl
cnZlciwgYnV0IGJvdGgNCj4gPj4+PiBwcm90b2NvbHMgYXJlIGF2YWlsYWJsZSwgYW5kIGFub3Ro
ZXIgdGhhdCBzYXlzIHRoYXQgZHVhbCBhbGxvY2F0aW9uDQo+ID4+Pj4gZmFpbGVkIGJlY2F1c2Ug
b25lIG9mIHRoZSB0d28gcHJvdG9jb2xzIGlzIG5vdCBhdmFpbGFibGUuICBUaGlzIGlzDQo+ID4+
Pj4gdG8gbGV0IHRoZSBjbGllbnQga25vdyB0aGF0IGl0IGlzIHVzZWxlc3MgdG8gdHJ5IGFub3Ro
ZXIgYWxsb2NhdGlvbg0KPiA+Pj4+IGZvciB0aGUNCj4gPj4gbWlzc2luZyBwcm90b2NvbC4NCj4g
Pj4+DQo+ID4+PiBJIGRvbid0IGdldCB0aGUgcmVhc29uIGZvciB0d28gZGlmZmVyZW50IHdhcm5p
bmdzLg0KPiA+Pg0KPiA+PiBBIHNlcnZlciBtYXkgc3VwcG9ydCBib3RoIElQdjYgYW5kIElQdjQg
YWxsb2NhdGlvbnMgYW5kIG5vdCBzdXBwb3J0DQo+ID4+IGR1YWwgYWxsb2NhdGlvbiwgaW4gd2hp
Y2ggY2FzZSB0aGUgY2xpZW50IGNhbiBkbyBhIHNlY29uZCBhbGxvY2F0aW9uDQo+ID4+IGZvciB0
aGUgSVB2NiByZWxheWVkIGFkZHJlc3MuDQo+ID4NCj4gPiBJZiB0aGUgc2VydmVyIGRvZXMgbm90
IHN1cHBvcnQgZHVhbCBhbGxvY2F0aW9uIGJ1dCBzdXBwb3J0cyBib3RoIElQdjYgYW5kDQo+IElQ
djQgYWxsb2NhdGlvbnMsIGl0IHdpbGwgb25seSBhbGxvY2F0ZSB0aGUgSVB2NCByZWxheWVkIGFk
ZHJlc3MgYW5kIG5vdCB3aWxsIG5vdA0KPiByZXR1cm4gQUREUkVTUy1FUlJPUi1DT0RFIGluIHRo
ZSByZXNwb25zZSwgdGhlIGNsaWVudCB3aWxsIGtub3cgdGhlDQo+IHNlcnZlciBkb2VzIG5vdCB1
bmRlcnN0YW5kIHRoZSBBRERJVElPTkFMLUFERFJFU1MtRkFNSUxZIGF0dHJpYnV0ZQ0KPiAoQURE
SVRJT05BTC1BRERSRVNTLUZBTUlMWSBpcyBhIGNvbXByZWhlbnNpb24tb3B0aW9uYWwgYXR0cmli
dXRlKS4NCj4gPg0KPiA+Pg0KPiA+PiBBbHRlcm5hdGl2ZWx5IHRoZSBzZXJ2ZXIgbWF5IG5vdCBz
dXBwb3J0IElQdjYgYXQgYWxsLCBpbiB3aGljaCBjYXNlDQo+ID4+IHRoZSBzZWNvbmQgYWxsb2Nh
dGlvbiB3aWxsIGZhaWwgYW5kIHdhcyB1bm5lY2Vzc2FyeS4NCj4gPg0KPiA+IEFERFJFU1MtRVJS
T1ItQ09ERSBzaWduYWxzIGJvdGggdW5zdXBwb3J0ZWQgSVAgYWRkcmVzcyB0eXBlICgweDAyDQo+
IChJUHY2IGFkZHJlc3MgZmFtaWx5KSkgYW5kIHRoZSByZWFzb24gZm9yIGZhaWx1cmUgKDQ0MCAo
dW5zdXBwb3J0ZWQgYWRkcmVzcw0KPiBmYW1pbHkpKS4NCj4gPg0KPiA+IENoZWVycywNCj4gPiAt
VGlydQ0KPiA+DQo+ID4+DQo+ID4+IFVzaW5nIHR3byBkaWZmZXJlbnQgd2FybmluZ3MgcGVybWl0
cyB0byBrbm93IGlmIHRoZSBzZWNvbmQgYWxsb2NhdGlvbg0KPiA+PiB3aWxsIHN1Y2NlZWQgb3Ig
bm90Lg0KPiA+Pg0KPiA+Pj4NCj4gPj4+Pg0KPiA+Pj4+IFdoYXQgaXMgdGhlIHBvbGljeSB3aGVu
IHJlc2VydmluZyB0aGUgbmV4dCBwb3J0IHdpdGggdGhlIEVWRU4tUE9SVA0KPiA+Pj4+IGF0dHJp
YnV0ZSBpbiBhIGR1YWwgYWxsb2NhdGlvbiwgYnV0IG9uZSBvZiB0aGVtIGZhaWxzIHRvIGZpbmQg
YQ0KPiA+Pj4+IHBhaXIgb2Ygc3Vic2VxdWVudCBwb3J0cyBhdmFpbGFibGU/DQo+ID4+Pg0KPiA+
Pj4gSXQncyBkaXNjdXNzZWQgaW4gc2VjdGlvbiA2LjENCj4gPj4+DQo+ID4+PiA8c25pcD4NCj4g
Pj4+ICAgIENsaWVudHMgTVVTVCBOT1QNCj4gPj4+ICAgIGluY2x1ZGUgQURESVRJT05BTC1BRERS
RVNTLUZBTUlMWSBhdHRyaWJ1dGUgaW4gYSBBbGxvY2F0ZSByZXF1ZXN0DQo+ID4+PiAgICB0aGF0
IGNvbnRhaW5zIGFuIEVWRU4tUE9SVCBhdHRyaWJ1dGUgd2l0aCB0aGUgUiBiaXQgc2V0IHRvIDEu
DQo+ID4+PiA8L3NuaXA+DQo+ID4+Pg0KPiA+Pj4+DQo+ID4+Pj4gSXQgaXMgbm90IHNhaWQgdGhh
dCB0aGUgQWxsb2NhdGUgc3VjY2Vzc2Z1bCByZXNwb25zZSBtdXN0IGNvbnRhaW4NCj4gPj4+PiB0
d28gWFJBcyBhZnRlciBhIHN1Y2Nlc3NmdWwgZHVhbCBhbGxvY2F0aW9uLg0KPiA+Pj4NCj4gPj4+
IEdvb2QgcG9pbnQsIFVwZGF0ZWQgZHJhZnQuDQo+IA0KPiBJIGNhbm5vdCBmaW5kIHRoaXMgdXBk
YXRlIGluIHR1cm4tMTQuDQoNClRoaXMgY29tbWVudCBpcyBwYXJ0aWFsbHkgYWRkcmVzc2VkIGlu
IC0xMiByZXZpc2lvbiwgc3RlcCA5IChpbiBTZWN0aW9uIDYuMiBpbiAtMTIgcmV2aXNpb24gYW5k
IFNlY3Rpb24gNy4yIGluIC0xNCByZXZpc2lvbikgaXMgdXBkYXRlZCB0byBkaXNjdXNzIGR1YWwg
YWxsb2NhdGlvbi4gDQo8c25pcD4NCklmIHRoZSBzZXJ2ZXIgY2FuIGZ1bGx5IG1lZXQNCnRoZSBy
ZXF1ZXN0LCB0aGVuIHRoZSBzZXJ2ZXIgYWxsb2NhdGVzIG9uZSBJUHY0IGFuZCBvbmUgSVB2Ng0K
cmVsYXkgYWRkcmVzcywgYW5kIHJldHVybnMgYW4gQWxsb2NhdGUgc3VjY2VzcyByZXNwb25zZQ0K
Y29udGFpbmluZyB0aGUgcmVsYXllZCB0cmFuc3BvcnQgYWRkcmVzc2VzIGFzc2lnbmVkIHRvIHRo
ZSBkdWFsDQphbGxvY2F0aW9uLg0KPC9zbmlwPg0KDQpORVc6DQpJZiB0aGUgc2VydmVyIGNhbiBm
dWxseSBtZWV0DQp0aGUgcmVxdWVzdCwgdGhlbiB0aGUgc2VydmVyIGFsbG9jYXRlcyBvbmUgSVB2
NCBhbmQgb25lIElQdjYNCnJlbGF5IGFkZHJlc3MsIGFuZCByZXR1cm5zIGFuIEFsbG9jYXRlIHN1
Y2Nlc3MgcmVzcG9uc2UNCmNvbnRhaW5pbmcgdGhlIHJlbGF5ZWQgdHJhbnNwb3J0IGFkZHJlc3Nl
cyBhc3NpZ25lZCB0byB0aGUgZHVhbA0KYWxsb2NhdGlvbiBpbiB0d28gWE9SLVJFTEFZRUQtQURE
UkVTUyBhdHRyaWJ1dGVzLg0KDQo+IA0KPiA+Pj4NCj4gPj4+Pg0KPiA+Pj4+IEkgd291bGQgYWxz
byBzdWdnZXN0IHRvIGFkZCBzb21lIHRleHQgdGhhdCBzYXlzIHRoYXQgd2hlbiBhIFRVUk5iaXMN
Cj4gPj4+PiBzZXJ2ZXIgc2VuZHMgYW4gQWxsb2NhdGUgc3VjY2VzcyByZXNwb25zZSwgaXQgbXVz
dCBhbHdheXMgc2VuZCB0aGUNCj4gPj4+PiBYUkFzIGluIHRoZSBzYW1lIG9yZGVyIHRoYW4gdGhl
IFJBRnMgd2VyZSBzZW50LiAgU28gaW4gY2FzZSB0aGUNCj4gPj4+PiBzZXJ2ZXIgc2VuZHMgYmFj
ayBieSBtaXN0YWtlIHR3byBYUkFzLCB0aGUgZmlyc3Qgb25lIG1hdGNoZXMgdGhlDQo+ID4+Pj4g
b25lDQo+ID4+IHJlcXVlc3RlZCBieSB0aGUgY2xpZW50Lg0KPiANCj4gRGlkIG5vdCBnZXQgYW5z
d2VyIHRvIHRoYXQgYW5kIGRpZCBub3Qgc2VlIGl0IGluIHR1cm4tMTQuDQoNCkkgZGlkIG5vdCBn
ZXQgdGhpcyBjb21tZW50LiBJZiBhIHJlcXVlc3QgY29udGFpbnMgYm90aCBSRVFVRVNURUQtQURE
UkVTUy1GQU1JTFkgYW5kIEFERElUSU9OQUwtQUREUkVTUy1GQU1JTFkgYXR0cmlidXRlcywgdGhl
IHJlcXVlc3QgaXMgcmVqZWN0ZWQgYnkgdGhlIHNlcnZlci4gRnVydGhlciwgb25seSBJUHY2IGFk
ZHJlc3MgZmFtaWx5IGlzIGFsbG93ZWQgaW4gdGhlIA0KQURESVRJT05BTC1BRERSRVNTLUZBTUlM
WSBhdHRyaWJ1dGUuDQoNCg0KPiANCj4gPj4+Pg0KPiA+Pj4+IFRoZSBidWxsZXQgbGlzdCBhdCB0
aGUgZW5kIG5lZWRzIGFsc28gdG8gYmUgZml4ZWQgZm9yIGR1YWwgYWxsb2NhdGlvbi4NCj4gPj4+
DQo+ID4+PiBBZ3JlZWQsIGZpeGVkLg0KPiA+Pj4NCj4gPj4+Pg0KPiA+Pj4+IC0gU2VjdGlvbiA2
LjMNCj4gPj4+Pg0KPiA+Pj4+IEhlcmUncyB0b28sIHRoZSB0ZXh0IG5lZWRzIHRvIGJlIHVwZGF0
ZWQgZm9yIHRoZSBkdWFsIGFsbG9jYXRpb24gY2FzZS4NCj4gPj4+DQo+ID4+Pg0KPiA+Pj4gWXVw
LCB1cGRhdGVkLg0KPiA+Pj4NCj4gDQo+IFNhbWUsIHRoZXJlIGlzIG5vIHVwZGF0ZSBzaW5jZSAt
MTEgaW4gc2VjdGlvbiA3LjMgKGZvcm1lcmx5IDYuMykNCg0KVGhpcyBjb21tZW50IGlzIGFkZHJl
c3NlZCBpbiAtMTIgcmV2aXNpb24gaXRzZWxmLCB0aGUgdXBkYXRlZCB0ZXh0IHVzZXMgInJlbGF5
ZWQgdHJhbnNwb3J0IGFkZHJlc3Mgb3IgYWRkcmVzc2VzIiBhbmQgIiBhZGRyZXNzIGZhbWlseSBv
ciBmYW1pbGllcyIgdG8gZGlzY3VzcyB0aGUgDQpkdWFsIGFsbG9jYXRpb24gY2FzZS4NCg0KQ2hl
ZXJzLA0KLVRpcnUNCg0KPiANCj4gLS0NCj4gTWFyYyBQZXRpdC1IdWd1ZW5pbg0KPiBFbWFpbDog
bWFyY0BwZXRpdC1odWd1ZW5pbi5vcmcNCj4gQmxvZzogaHR0cHM6Ly9tYXJjLnBldGl0LWh1Z3Vl
bmluLm9yZw0KPiBQcm9maWxlOiBodHRwczovL3d3dy5saW5rZWRpbi5jb20vaW4vcGV0aXRodWcN
Cg0K


From nobody Sun Mar  4 07:03:23 2018
Return-Path: <tasveren@rbbn.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ED5E124E15 for <tram@ietfa.amsl.com>; Sun,  4 Mar 2018 07:03:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.111
X-Spam-Level: 
X-Spam-Status: No, score=-4.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=sonusnetworks.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1VpJyrFJHOeS for <tram@ietfa.amsl.com>; Sun,  4 Mar 2018 07:03:18 -0800 (PST)
Received: from us-smtp-delivery-181.mimecast.com (us-smtp-delivery-181.mimecast.com [63.128.21.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A2EE1243F6 for <tram@ietf.org>; Sun,  4 Mar 2018 07:03:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=SonusNetworks.onmicrosoft.com; s=selector1-rbbn-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=qzzvSseOmlql+vqos/GKS9LHxdnl5FEstBXxPiNXkms=; b=OeBIvyJQyf8nvuFhpDgcr7kjICh1YKUEdq8u7/L/8sMefle0Zl7OvZ8CdBhKX/uQXOpnMfzeADYujQdLDD/OvrGHQMBQq97f3Lc14EId7k83HSe4vftKR/tWy3tC/HZK1PkgAGbUOK5jyiAF5ozj2GFpoRETAyylXqHPhO1kR2c=
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02lp0051.outbound.protection.outlook.com [207.46.163.51]) (Using TLS) by us-smtp-1.mimecast.com with ESMTP id us-mta-236-iagJI-A-PNSW-vzydsmt1w-1; Sun, 04 Mar 2018 10:03:15 -0500
Received: from CY4PR03MB3160.namprd03.prod.outlook.com (10.171.245.165) by CY4PR03MB2999.namprd03.prod.outlook.com (10.175.117.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.548.13; Sun, 4 Mar 2018 15:03:12 +0000
Received: from CY4PR03MB3160.namprd03.prod.outlook.com ([fe80::34a3:3001:f444:3072]) by CY4PR03MB3160.namprd03.prod.outlook.com ([fe80::34a3:3001:f444:3072%13]) with mapi id 15.20.0548.014; Sun, 4 Mar 2018 15:03:12 +0000
From: "Asveren, Tolga" <tasveren@rbbn.com>
To: Marc Petit-Huguenin <petithug@acm.org>, "Gonzalo Salgueiro (gsalguei@cisco.com)" <gsalguei@cisco.com>, "tram@ietf.org" <tram@ietf.org>
Thread-Topic: [tram] draft-ietf-tram-stun-pmtud-06 review
Thread-Index: AdOoeuWqoyIVbPnJTkKqVXoa0q8HIQKi1NCAACzPOKA=
Date: Sun, 4 Mar 2018 15:03:12 +0000
Message-ID: <CY4PR03MB3160D0E46134CF10AE7CBAF4A5DB0@CY4PR03MB3160.namprd03.prod.outlook.com>
References: <CY4PR03MB316039CC07807621C64AFE39A5C90@CY4PR03MB3160.namprd03.prod.outlook.com> <10ce3dde-2401-dc4f-e231-13678f6494d1@acm.org>
In-Reply-To: <10ce3dde-2401-dc4f-e231-13678f6494d1@acm.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [73.29.251.142]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR03MB2999; 7:ILWi+qelu7Fpi4OtfNKXg4IqoQ7HMOECmLA80uFRoGvqEPSvFSVTz+tf9iaO7zTx3HX1FAcSuDgI/IFK/A6+q9MGtZ4CrBtbRfli3L8dlFZ5xYR215jIAKpvJspK8/tpmJ7ddMcl18GOtzeovnE3b0VOX4AyaNMwYMhh8t5HDxrDkhubtPUhPMTI8aDuMoX3MwCkWqpKaQgGoHHiM2Zq9kWLIxyOLLDp9Z0X9Y7sqiXjRMD4+SB9BOWl0977HjeL; 20:VpIfGrfviZ5egyEhgzw9JNfdW4PNZur4qef2ntkyVpJ4VP0vV/cD6h1BO2egYDQAvPOTS25B3uDjPjrpr+DV9nJRw/R6hdZ0svxBvdqhACicr8dMM+Q7D98sODMDgzYdho3OQCT6yS/wi7+JkjXZ1DVWewFLfnkOzRYM3WNmb90=
x-ms-office365-filtering-correlation-id: 02ae865f-7876-42fc-ac3f-08d581e10cfd
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603307)(7153060)(7193020); SRVR:CY4PR03MB2999; 
x-ms-traffictypediagnostic: CY4PR03MB2999:
x-microsoft-antispam-prvs: <CY4PR03MB299966441D1ACB5A386A2E5EA5DB0@CY4PR03MB2999.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(192374486261705)(128460861657000)(95692535739014)(213716511872227)(81160342030619);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040501)(2401047)(5005006)(8121501046)(3002001)(3231220)(944501244)(52105095)(93006095)(93001095)(10201501046)(6041288)(20161123558120)(20161123562045)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(6072148)(201708071742011); SRVR:CY4PR03MB2999; BCL:0; PCL:0; RULEID:; SRVR:CY4PR03MB2999; 
x-forefront-prvs: 060166847D
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(39850400004)(376002)(39380400002)(366004)(396003)(13464003)(199004)(189003)(252514010)(51444003)(51914003)(229853002)(3660700001)(5660300001)(3280700002)(6246003)(33656002)(86362001)(55016002)(316002)(6436002)(68736007)(53936002)(478600001)(6306002)(110136005)(53546011)(59450400001)(9686003)(7736002)(102836004)(74316002)(305945005)(6506007)(99286004)(26005)(186003)(2900100001)(2950100002)(966005)(14454004)(97736004)(6116002)(45080400002)(105586002)(106356001)(3846002)(2906002)(25786009)(7696005)(76176011)(81156014)(8676002)(66066001)(8936002)(2501003)(5250100002)(81166006); DIR:OUT; SFP:1101; SCL:1; SRVR:CY4PR03MB2999; H:CY4PR03MB3160.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; LANG:en; 
x-microsoft-antispam-message-info: MLD5HqqKTR2ARojUmE2lIK1EJmvbOGJYOD48B8WtUjfrXEm1MYivx1A+rss/DMDahrzYVP7TIOlygMhC1Ap3NwalYojViUYEuWaQ4/GfiYBiazZMtz1HphyhKrHqfir7GCEYFaw36TERC5/zeTeS+CKvUSMci726qJMXFZ6+/Cvx2GN9j6swUa6nAzcOsd6sWhUe0UgODkthD7cD4v/ZoJG+g5xGYdgZA4B1YxJxSHXAvgNQnWiGtQTe8JeiUiFaexvaCqlFzy2QQkVUEQZEdve+CW3U+/1gA09HpjFhv1vmaMUcT/2ToBgF4S0wtg0QXhx/8yfKQyaqrCEWCoIygA==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-OriginatorOrg: rbbn.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 02ae865f-7876-42fc-ac3f-08d581e10cfd
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Mar 2018 15:03:12.7587 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 29a671dc-ed7e-4a54-b1e5-8da1eb495dc3
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR03MB2999
X-MC-Unique: iagJI-A-PNSW-vzydsmt1w-1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/WWJZuY1BFspb4HZ2KPymQDxFEpo>
Subject: Re: [tram] draft-ietf-tram-stun-pmtud-06 review
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Mar 2018 15:03:21 -0000

SGkgTWFyYywNCg0KUGxlYXNlIHNlZSBpbmxpbmUgZm9yIGNvbW1lbnRzL2Fuc3dlcnMvcXVlc3Rp
b25zLg0KDQpUaGFua3MsDQpUb2xnYQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJv
bTogTWFyYyBQZXRpdC1IdWd1ZW5pbiA8cGV0aXRodWdAYWNtLm9yZz4gDQpTZW50OiBTYXR1cmRh
eSwgTWFyY2ggMywgMjAxOCAxMDo0MiBBTQ0KVG86IEFzdmVyZW4sIFRvbGdhIDx0YXN2ZXJlbkBy
YmJuLmNvbT47IEdvbnphbG8gU2FsZ3VlaXJvIChnc2FsZ3VlaUBjaXNjby5jb20pIDxnc2FsZ3Vl
aUBjaXNjby5jb20+OyB0cmFtQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW3RyYW1dIGRyYWZ0LWll
dGYtdHJhbS1zdHVuLXBtdHVkLTA2IHJldmlldw0KDQpUaGFua3MgZm9yIHRoZSByZXZpZXcsIHBs
ZWFzZSBzZWUgaW5saW5lLg0KDQpBcyB0aGUgY3V0b2ZmIGlzIE1vbmRheSBhZnRlcm5vb24sIEkn
bGwgcHVibGlzaCAtMDcganVzdCBhZnRlciBzZW5kaW5nIHRoaXMgZW1haWwuDQoNCk9uIDAyLzE3
LzIwMTggMDk6NDAgUE0sIEFzdmVyZW4sIFRvbGdhIHdyb3RlOg0KPiBNYXJjLCBHb256YWxvLA0K
PiANCj4gU29tZSBjb21tZW50cy9xdWVzdGlvbnMgZm9yIGRyYWZ0LWlldGYtdHJhbS1zdHVuLXBt
dHVkLTA2Og0KPiANCj4gaS0gNC4NCj4gDQo+ICAgSW1wbGVtZW50YXRpb25zIHN1cHBvcnRpbmcg
dGhpcyBzcGVjaWZpY2F0aW9uIE1VU1QgaW1wbGVtZW50IHRoZQ0KPiAgICBzZXJ2ZXIgc2lkZSBv
ZiBib3RoIHRoZSBTaW1wbGUgUHJvYmluZyBtZWNoYW5pc20gKFNlY3Rpb24gNC4xKSBhbmQNCj4g
ICAgdGhlIENvbXBsZXRlIFByb2JpbmcgbWVjaGFuaXNtIChTZWN0aW9uIDQuMikuDQo+ICAgIElt
cGxlbWVudGF0aW9ucyBzdXBwb3J0aW5nIHRoaXMgc3BlY2lmaWNhdGlvbiBNVVNUIGltcGxlbWVu
dCB0aGUNCj4gICAgY2xpZW50IHNpZGUgb2YgdGhlIENvbXBsZXRlIFByb2JpbmcgbWVjaGFuaXNt
LiAgVGhleSBNQVkgaW1wbGVtZW50DQo+ICAgIHRoZSBjbGllbnQgc2lkZSBvZiB0aGUgU2ltcGxl
IFByb2JpbmcgbWVjaGFuaXNtLg0KPiANCj4gSSBkb24ndCBzZWUgdGhlIHJhdGlvbmFsZSBiZWhp
bmQgbWFuZGF0aW5nIHRoaXMgYmVoYXZpb3IuIFN1Y2ggc2VtYW50aWNzIGluIGdlbmVyYWwgYXJl
IHRha2VuIGNhcmUgb2YgaW4gdGhlIGNvbnRleHQgb2YgYSBjYXBhYmlsaXR5IG5lZ290aWF0aW9u
IG1lY2hhbmlzbSwgd2hpY2ggdGhpcyBkb2N1bWVudCBkb2VzIG5vdCBzcGVjaWZ5LiBBcyBpdCBz
dGFuZHMgcmlnaHQgbm93LCBJIHRoaW5rIHRoaXMgaXMgYmVzdCBsZWZ0IHRvIGxvY2FsIHBvbGlj
eSBhbmQgYmlsYXRlcmFsIGFncmVlbWVudHMgYW5kIEkgd291bGQgc3VnZ2VzdCBub3QgdG8gdXNl
IGFueXRoaW5nIHN0cm9uZ2VyIHRoYW4gIlJFQ09NTUVORCIuDQoNCkl0IHRvb2sgbWUgc29tZSB0
aW1lIHRvIHJlbWVtYmVyIHdoeSB0aGF0IHdhcyB0aGUgY2FzZS4gIElJUkMsIG9uZSBvZiB0aGUg
cmVhc29ucyBvZiBkb2luZyB0aGlzIGlzIGJlY2F1c2Ugb2YgdGhlIGltcGxpY2l0IHByb2JlIHN1
cHBvcnQgaW4gc2VjdGlvbiA1LjIuICBCZWNhdXNlIHRoZXJlIGlzIG5vIGV4cGxpY2l0IHNpZ25h
bGluZyB0aGVyZSwgd2UgbmVlZCB0aGUgc2VydmVyIHNpZGUgKHdoaWNoIHdhcyBwcmV2aW91c2x5
IHRoZSBjbGllbnQgc2lkZSkgdG8gYmUgcmVhZHkgdG8gcmVzcG9uZCB0byBib3RoIFNpbXBsZSBh
bmQgQ29tcGxldGUgUHJvYmluZy4gIEhlbmNlIHRoZSAic2VydmVyIG11c3QgZG8gYm90aCwgY2xp
ZW50IGNob29zZSB3aGF0IHRoZXkgd2FudCB0byBkbyIgcnVsZS4NCg0KVGhlIG90aGVyIHJlYXNv
biBpcyB0aGF0IGlmIHdlIGxldCBpbXBsZW1lbnRlcnMgY2hvb3NlLCB0aGVuIENvbXBsZXRlIFBy
b2JpbmcgLSB3aGljaCBpcyB0aGUgY29ycmVjdCB3YXkgb2YgZG9pbmcgcHJvYmluZyAtIHdpbGwg
bmV2ZXIgYmUgdXNlZC4NCltUT0xHQV0gSWYgY2xpZW50IGRvZXMgbm90IGdldCByZXBsaWVzIGZv
ciBhIG1lY2hhbmlzbSBpdCBTSE9VTEQgdHJ5IHRoZSBvdGhlciBvbmUuIEhvbmVzdGx5IEkgZG9u
4oCZdCBzZWUgYSBjb21wZWxsaW5nIHJlYXNvbiB0byBtYW5kYXRlIGFueXRoaW5nIG9uIHRoZSBz
ZXJ2ZXIgc2lkZS4gVGhlcmUgaXMgbm8gbmVnb3RpYXRpb24gbWVjaGFuaXNtIGFuZCB0aGF0IGNh
buKAmXQgYmUgZW5mb3JjZWQgb24gcHJvdG9jb2wgbGV2ZWwgYW55aG93LiBJIHN1Z2dlc3QgdG8g
dXNlIFJFQ09NTU5FRCBmb3Igc2VydmVyIGFuZCBhZGQgYSBzZW50ZW5jZSBmb3IgY2xpZW50IGJl
aGF2aW9yIHRoYXQgaXQgU0hPVUxEIHRyeSB0aGUgb3RoZXIgbWVjaGFuaXNtIGlmIG9uZSBkb2Vz
IG5vdCBnZXQgYW55IHJlcGxpZXMgYXQgYWxsLg0KDQo+IA0KPiBpaS0gNC4xDQo+IERGIGJpdCBz
ZXQgb3ZlciBVRFAuDQo+ID09Pg0KPiBERiBiaXQgaW4gSVAgSGVhZGVyLg0KPiBSaWdodD8gICh0
aGUgc2FtZSBpbiA0LjIpDQoNCk5vdCByZWFsbHksIHRoZSBQcm9iZSBSZXF1ZXN0IGlzIHN0aWxs
IHNlbnQgb3ZlciBVRFAsIHNvIEkgY2hhbmdlZCB0aGUgdGV4dCB0byB0aGF0ICh0d2ljZSk6DQoN
CiBUaGUgU2ltcGxlIFByb2JpbmcgbWVjaGFuaXNtIGlzIGltcGxlbWVudGVkIGJ5IHNlbmRpbmcg
YSBQcm9iZSAgUmVxdWVzdCB3aXRoIGEgUEFERElORyBbUkZDNTc4MF0gYXR0cmlidXRlIG92ZXIg
VURQIHdpdGggdGhlIERGIGJpdCAgc2V0IGluIHRoZSBJUCBoZWFkZXIuICBBIHJvdXRlciBvbiB0
aGUgcGF0aCB0byB0aGUgc2VydmVyIGNhbiByZWplY3QgIHRoaXMgcmVxdWVzdCB3aXRoIGFuIElD
TVAgbWVzc2FnZSBvciBkcm9wIGl0Lg0KDQogVGhlIENvbXBsZXRlIFByb2JpbmcgbWVjaGFuaXNt
IGlzIGltcGxlbWVudGVkIGJ5IHNlbmRpbmcgb25lIG9yIG1vcmUgIFByb2JlIEluZGljYXRpb25z
IHdpdGggYSBQQURESU5HIGF0dHJpYnV0ZSBvdmVyIFVEUCB3aXRoIHRoZSBERiBiaXQgIHNldCBp
biB0aGUgSVAgaGVhZGVyIGZvbGxvd2VkIGJ5IGEgUmVwb3J0IFJlcXVlc3QgdG8gdGhlIHNhbWUg
c2VydmVyLg0KW1RPTEdBXSBMb29rcyBnb29kLCBJIGp1c3Qgd2FudGVkIHRvIG1ha2Ugc3VyZSBh
Ym91dCB0aGUgIkRGIGJpdCBpbiBJUCBoZWFkZXIiIHBhcnQuDQoNCj4gDQo+IGlpaS0gNC4xLjEN
Cj4gQSBjbGllbnQgTVVTVCBOT1Qgc2VuZCBhIHByb2JlIGlmIGl0IGRvZXMgbm90IGhhdmUga25v
d2xlZGdlIHRoYXQgdGhlDQo+ICAgIHNlcnZlciBzdXBwb3J0cyB0aGlzIHNwZWNpZmljYXRpb24u
ICBUaGlzIGlzIGRvbmUgZWl0aGVyIGJ5IGV4dGVybmFsDQo+ICAgIHNpZ25hbGxpbmcgb3IgYnkg
YSBtZWNoYW5pc20gc3BlY2lmaWMgdG8gdGhlIFVEUCBwcm90b2NvbCB0byB3aGljaA0KPiAgICBQ
TVRVRCBjYXBhYmlsaXRpZXMgYXJlIGFkZGVkIG9yIGJ5IG9uZSBvZiB0aGUgbWVjaGFuaXNtcyBz
cGVjaWZpZWQgaW4NCj4gICAgU2VjdGlvbiA1Lg0KPiBJIHN1Z2dlc3QgYWRkaW5nIHRleHQgZm9y
IHBvc3NpYmxlIHVzZSBvZiBsb2NhbCBwb2xpY3kvYmlsYXRlcmFsIGFncmVlbWVudHMgZm9yIHRo
aXMgcHVycG9zZS4NCg0KSSBhbSBub3Qgc3VyZSB3aGF0IHRvIGFkZCB0byB3aGF0IGlzIHNhaWQu
ICBEbyB5b3UgaGF2ZSB0ZXh0IHRvIHN1Z2dlc3Q/DQpbVE9MR0FdIE1heWJlIGJ5IGp1c3QgYWRk
aW5nIHNvbWV0aGluZyBsaWtlOg0KIkluZm9ybWF0aW9uIGFib3V0IGNsaWVudC9zZXJ2ZXIgc3Vw
cG9ydCBmb3IgdGhpcyBzcGVjaWZpY2F0aW9uLCBmb3IgZXhhbXBsZSwgY291bGQgYmUgYmFzZWQg
b24gbG9jYWwgcG9saWN5IGFuZCBiaWxhdGVyYWwgYWdyZWVtZW50cyBhbW9uZyByZWxldmFudCBv
cmdhbml6YXRpb25zLiINCg0KPiANCj4gaXYtICA0LjINCj4gU29tZSBwcm90b2NvbHMgbWF5IGFs
cmVhZHkgaGF2ZSBhIHdheSBvZiBpZGVudGlmeWluZyBlYWNoIGluZGl2aWR1YWwNCj4gICAgVURQ
IHBhY2tldCwgaW4gd2hpY2ggY2FzZSB0aGVzZSBpZGVudGlmaWVycyBTSE9VTEQgYmUgdXNlZCBp
biB0aGUNCj4gICAgSURFTlRJRklFUlMgYXR0cmlidXRlIG9mIHRoZSBSZXBvcnQgUmVzcG9uc2Uu
DQo+IFdoYXQgaXMgbWVhbnQgaGVyZSBhcyAic29tZSBwcm90b2NvbHMiPyBBcmUgeW91IHJlZmVy
cmluZyAgdG8gd2hhdCBpcyBjYXJyaWVkIGFzIHBheWxvYWQgb2YgVURQIG9yIHdoYXQgaXMgdXNl
ZCBiZWxvdyBVRFA/DQoNClRoZSBmb3JtZXIuICBJIGNoYW5nZWQgdGhlIHRleHQgdG8gImFwcGxp
Y2F0aW9uIGxheWVyIHByb3RvY29sczoiDQpbVE9MR0FdIFRoYW5rcy4NCg0KPiANCj4gdi0gNC4y
DQo+IEluIHRoZSBmaXJzdCBwYWNrZXQgaWRlbnRpZmljYXRpb24gbWVjaGFuaXNtLCB0aGUgc2Vy
dmVyIGNvbXB1dGVzIGENCj4gICAgY2hlY2tzdW0gb3ZlciBlYWNoIHBhY2tldCByZWNlaXZlZCBh
bmQgc2VuZHMgYmFjayB0byB0aGUgc2VuZGVyIHRoZQ0KPiAgICBsaXN0IG9mIGNoZWNrc3VtcyBv
cmRlcmVkIGNocm9ub2xvZ2ljYWxseS4gIFRoZSBjbGllbnQgY29tcGFyZXMgdGhpcw0KPiAgICBs
aXN0IHRvIGl0cyBvd24gbGlzdCBvZiBjaGVja3N1bXMuDQo+IFdoYXQgaWYgdGhlcmUgYXJlIHR3
byBwcm9iZXMgd2l0aCB0aGUgc2FtZSBjaGVja3N1bSByaWdodCBhZnRlciBlYWNoIG90aGVyIGFu
ZCBvbmUgb2YgdGhlbSBpcyBsb3N0PyBIb3cgY2FuIGNsaWVudCBkaXNhbWJpZ3VhdGUgc3VjaCBh
IGNhc2UgaW4gIHRoZSByZXNwb25zZT8NCg0KSSBhbSBub3Qgc3VyZSB0byBnZXQgdGhlIHByb2Js
ZW0gaGVyZS4gIFRoZSBzZW5kZXIga2VlcHMgYSBjaHJvbm9sb2dpY2FsbHkgb3JkZXJlZCBsaXN0
IG9mIHRoZSBjaGVja3N1bXMgb2YgdGhlIHNlbnQgcGFja2V0cyAoZGF0YSBhbmQgcHJvYmVzKSwg
c28gaW4gdGhhdCBjYXNlIHRoZXJlIGlzIGEgc2VxdWVuY2Ugb2YgdHdvIGlkZW50aWNhbCBjaGVj
a3N1bXMgaW4gdGhhdCBsaXN0LiAgVGhlIHNlcnZlciBzZW5kcyBiYWNrIGEgbGlzdCBvZiBjaGVj
a3N1bXMsIGJ1dCB3aXRoIG9ubHkgb25lIG9mIHRoYXQgdmFsdWUgKG9yIGV2ZW4gMCkuICBUaGUg
bG9zcyBjYW4gYmUgZGV0ZWN0ZWQuDQpbVE9MR0FdIExvc3MgY2FuIGJlIGRldGVjdGVkIGJ1dCB3
aGljaCBvbmUgaXMgbG9zdD8NCg0KUHJvYmUtbiAgKGNoZWNrc3VtLUEpDQpQcm9iZS1uKzEgKGNo
ZWNrc3VtLUEpDQoNCk9ubHkgYSBzaW5nbGUgcmVwbHkgZm9yIChjaGVja3N1bS1BKSBpcyByZWNl
aXZlZC4NCg0KSXMgUHJvYmUtbiBvciBQcm9iZS1uKzEgbG9zdD8NCg0KPiANCj4gdi0gNw0KPiBU
aGUgU2ltcGxlIFByb2JpbmcgbWVjaGFuaXNtIG1heSBiZSB1c2VkIHdpdGhvdXQgYXV0aGVudGlj
YXRpb24NCj4gICAgYmVjYXVzZSB0aGlzIHVzYWdlIGJ5IGl0c2VsZiBjYW5ub3QgdHJpZ2dlciBh
biBhbXBsaWZpY2F0aW9uIGF0dGFjaw0KPiAgICBiZWNhdXNlIHRoZSBQcm9iZSBSZXNwb25zZSBp
cyBzbWFsbGVyIHRoYW4gdGhlIFByb2JlIFJlcXVlc3QuDQo+IElzbid0IHRoZSBzYW1lIHRydWUg
Zm9yIFN1bShQcm9iZSBSZXF1ZXN0cykgPiAoUmVwb3J0IFJlc3BvbnNlKT8NCg0KSSB0aGluayB0
aGF0IG1lY2hhbmlzbSB3YXMgc2V0IGZvbGxvd2luZyBhIHJldmlldyB0aGF0IHdhcyB3b3JyaWVk
IGFib3V0IGFtcGxpZmljYXRpb24gYXR0YWNrLiAgV2UgaGF2ZSB0aGUgc2ltcGxlIHByb2JlIG1l
Y2hhbmlzbSB3aXRob3V0IGF1dGhlbnRpY2F0aW9uIHRvIGtlZXAgdGhlIGJhcnJpZXIgdG8gZW50
cnkgdmVyeSBsb3csIGkuZS4gdGhlIG1pbmltdW0gcmVxdWlyZWQgaW1wbGVtZW50YXRpb24gcG9z
c2libGUuDQoNClNlY3VyaXR5IGV4cGVydCBjYW4gY2hpbWUgaW4uDQpbVE9MR0FdIEkgdGhpbmsg
dGhhdCB3b3VsZCBiZSBnb29kLiBXaG8gd291bGQgYmUgdGhhdD8NCg0KPiANCj4gdmlpLSBuaXQN
Cj4gPT0gVGhlIGNvcHlyaWdodCB5ZWFyIGluIHRoZSBJRVRGIFRydXN0IGFuZCBhdXRob3JzIENv
cHlyaWdodCBMaW5lIGRvZXMgbm90DQo+ICAgICAgbWF0Y2ggdGhlIGN1cnJlbnQgeWVhcg0KPiAN
Cj4gICAtLSBUaGUgZG9jdW1lbnQgZGF0ZSAoU2VwdGVtYmVyIDEsIDIwMTcpIGlzIDE2OSBkYXlz
IGluIHRoZSBwYXN0LiAgSXMgdGhpcw0KPiAgICAgIGludGVudGlvbmFsPw0KDQpXaWxsIGJlIHVw
Z3JhZGVkIHdpdGggdGhlIG5leHQgcHVibGljYXRpb24uDQpbVE9MR0FdIFRoYW5rcy4NCg0KLS0N
Ck1hcmMgUGV0aXQtSHVndWVuaW4NCkVtYWlsOiBtYXJjQHBldGl0LWh1Z3VlbmluLm9yZw0KQmxv
ZzogaHR0cHM6Ly9tYXJjLnBldGl0LWh1Z3VlbmluLm9yZw0KUHJvZmlsZTogaHR0cHM6Ly93d3cu
bGlua2VkaW4uY29tL2luL3BldGl0aHVnDQoNCg==


From nobody Sun Mar  4 09:06:07 2018
Return-Path: <karl@ingate.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D2191200F1 for <tram@ietfa.amsl.com>; Sun,  4 Mar 2018 09:06:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.021
X-Spam-Level: 
X-Spam-Status: No, score=-1.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MSGID_MULTIPLE_AT=1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ingate.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fBTFJqeOjYnl for <tram@ietfa.amsl.com>; Sun,  4 Mar 2018 09:06:01 -0800 (PST)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0078.outbound.protection.outlook.com [104.47.2.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11F6B1200B9 for <tram@ietf.org>; Sun,  4 Mar 2018 09:06:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ingate.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=IVrwqmVgVGogF9bQIrBoTn8MGfUzl3iZ+J8VitHYvdw=; b=Yz1Zmi8YrSixUIrjr+56iQlFGMUwGO982ShL0/W9/yYEfZa8EoOHFJRXxkhzh2ZoPetAHKEphrUOdUeNBZEXlzRTUjjMRjQNjlqfaJazVFVm5+xgND41C3v+Wv+IM3Z1uMt/D26ywzAugA5xJ+K+0WyMFoPINKQTc5mhzCGRLYc=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=karl@ingate.com; 
Received: from Kallei7 (90.229.133.175) by HE1PR01MB1833.eurprd01.prod.exchangelabs.com (2a01:111:e400:7bc0::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.548.13; Sun, 4 Mar 2018 17:05:55 +0000
From: "Karl Stahl" <karl.stahl@ingate.com>
To: "'Marc Petit-Huguenin'" <petithug@acm.org>, "'Konda, Tirumaleswar Reddy'" <TirumaleswarReddy_Konda@McAfee.com>, <tram@ietf.org>
References: <65c75449-152c-1ce7-7c81-460ca589d9f0@acm.org> <DM5PR16MB17881ABD54B89E14F0291C56EA4C0@DM5PR16MB1788.namprd16.prod.outlook.com> <ea84bcf9-19b6-5492-383b-18e2bc5a93bf@acm.org> <DM5PR16MB178859E2018148DBAD51635EEAF20@DM5PR16MB1788.namprd16.prod.outlook.com> <46fdf931-eb0c-c4fe-9c01-4a066134abfb@acm.org>
In-Reply-To: <46fdf931-eb0c-c4fe-9c01-4a066134abfb@acm.org>
Date: Sun, 4 Mar 2018 18:05:50 +0100
Message-ID: <025201d3b3db$0e182730$2a487590$@stahl@ingate.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdOya8decTsiW1d1Tsip9jDRarERagBTRx7A
Content-Language: sv
X-Originating-IP: [90.229.133.175]
X-ClientProxiedBy: AM5PR0701CA0015.eurprd07.prod.outlook.com (2603:10a6:203:51::25) To HE1PR01MB1833.eurprd01.prod.exchangelabs.com (2a01:111:e400:7bc0::23)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: e44ad68f-a377-43cc-c78b-08d581f231f9
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(5600026)(4604075)(2017052603307)(7153060)(7193020); SRVR:HE1PR01MB1833; 
X-Microsoft-Exchange-Diagnostics: 1; HE1PR01MB1833; 3:qaJRr3vgn+3e9+5tSMN60I7J/QWZFhirJ5dDJWloVUpRTOqgeoXaeQ57IkcSE2gSWKIBLbuYpDD4aZCIrbvYkeea4Yn9Dcx5Ennw4YjCDcRI3a92FzomomrxYQ3W5GELRtNKzTIPusXP/qd1yhkGIvB+rKH4PbU1H66nnzGOPzuf4OrJtDi4aChBSvrxDi41ZdVadstrC8z2oySiH4aEXixwkLpovYY5gmFhBDeDEfX2sLInMxd038bArKSsdEne; 25:0xokr2gJ1hpm00wjJDxcAgHA4HGWPldZiLB2ShyuSUFuUZzfalaLvlVyXVt5UuyWL0QmzmM0DXM7fNERLdqwuRuzST1DcAI+k7mJuoL0PNM63/j47GeZF1/4xfVx97MrGAaQFpRd2Tf6I1vi0aJmAjIcvnvOPPm1MB+FbTvqPQZpdzzCjY7U/+TOpo9zSAzzc/ee8tPwYlowCrS7w0HqB9VMJQ6DYUK/O4W4WHzMteZavUh6OWnXA1l/w7u8nbJrc5Y4+tOLdbtFkn14oLWoTqy5aTz6uRJLy5B/pZhISm5GUhgYkUznXxqdA8xqOnHDYnPrgNkMzcRmR0cBmC3jqw==; 31:q3yCo4PXgn0xipaev0hJS/FnTzFXeoBEFiy8sDj2QwUNU1VtPa9jPUiMMJeYqdZA8d6UJGMUW9e/jVfZSfohAkAHndDjuzPUCgJypP4buB7etDvKxJPPVlTS26yGp8FXpU3Ooie4TOGdNKE673JixuFCb1PUT660U3HXjlWTBaKGN6G4HpMWSb11+GuKUGHne+LuL8zESwGr31e/xVMk9F9tA3WdI7MOvQVdYj7fgHw=
X-MS-TrafficTypeDiagnostic: HE1PR01MB1833:
X-Microsoft-Antispam-PRVS: <HE1PR01MB1833164E54AE38C6E87EB93DB1DB0@HE1PR01MB1833.eurprd01.prod.exchangelabs.com>
X-Exchange-Antispam-Report-Test: UriScan:(158342451672863)(128460861657000)(213716511872227)(81160342030619)(123452027830198);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(8121501046)(5005006)(3231220)(944501244)(52105095)(3002001)(10201501046)(93006095)(93001095)(6041288)(2016111802025)(20161123560045)(20161123564045)(20161123562045)(20161123558120)(6072148)(6043046)(201708071742011); SRVR:HE1PR01MB1833; BCL:0; PCL:0; RULEID:; SRVR:HE1PR01MB1833; 
X-Microsoft-Exchange-Diagnostics: 1; HE1PR01MB1833; 4:9wwu6wnw5hOtDSf4OlYp3LUW9tg3EveoHs7z/5Ewf/kWUhabpmMRYmWYThEzrRzDQBRZ0m+vHsxSLjnd5CqjVIaQ38dsDCYJ+HaoDEAYr4jVooAIwDYy/T6veJQQ0esw5U7W/vnEkvTnxsw6S1rq8nfro6dfzIpHSoJSdFmpdL2rQsJocuyqlbBk+IgSsmGStCzIx35DE4lTaY+V1h/bkW59799nLH+r8Bje4stYUVkZO0DQGbRb2vyvWnXflDwXna/4ahaAYEPI+DSMfwAU0HTiO8cATfBamJjoBUIr6vONrS7LM+CpdDjCpiRwdoMyPWZKhCy0dhFaYtWvRTTAsxsxtm+rznQwPPy5UKdLeddaJnON1ZZdwpcgfZn9paCaUDTPpIgld2NeoJOFkNlnj3yF6BhCisgI+z1jXGtmWo+m5LXl/iiloRw3v/GS1JaO
X-Forefront-PRVS: 060166847D
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(396003)(39380400002)(376002)(346002)(39830400003)(366004)(38534002)(52084003)(13464003)(199004)(189003)(252514010)(3846002)(8936002)(1420700001)(81166006)(81156014)(8746002)(6116002)(61296003)(50466002)(105586002)(52116002)(6486002)(50226002)(68736007)(316002)(110136005)(93886005)(66066001)(106356001)(44736005)(47776003)(61793004)(6306002)(9686003)(97736004)(53936002)(8676002)(23676004)(6496006)(76176011)(14726001)(2906002)(5820100001)(5660300001)(26005)(305945005)(33896004)(7736002)(84116003)(478600001)(96836002)(966005)(25786009)(59450400001)(186003)(16526019)(36756003)(6666003)(386003)(2950100002)(45080400002)(53546011)(102836004)(2101003); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR01MB1833; H:Kallei7; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: ingate.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtIRTFQUjAxTUIxODMzOzIzOktwRVlIRm4rRzNXUnZwcjZFWTcrbS9sbkwv?= =?utf-8?B?b2hkai9WOFI3dEZuYjVPYnRiQUl5US9TSGt5S0NhVWRjVGVKeTFURXVMZUV5?= =?utf-8?B?amlmbWxEUFpFSzdtdHZpbUxSeUUrMjZaalNxS0M3YmsrazJNb0I0dU9zZ2tl?= =?utf-8?B?dk9MSUpJOU43MFFNV29oSEdINVBKOHZnd0krYll0cGxnejBlTWVqdnNzV1Ro?= =?utf-8?B?TVlNU0Ewd2ZXTDk4bE5KNFNpdmxYSi91K21YOWZiWVl5UHlXN3g3WjVUR2RQ?= =?utf-8?B?RkpGOEFBNkNTZDhwbk1Dc1ZzVnM5N1gxMGZPQkRhTU1yeEtJL1NaaTIveTdC?= =?utf-8?B?WVFsWlpWL1B1aTkzLzgybDN3WmsxUzZ2R29rVjh5aFJMS1hzVU0wS0FPUU1B?= =?utf-8?B?VWJVSFduQ0U0bFdBUjhMT2FtTXVFa1JHaXBLTVNFY3JLRGl5RHZuYy8zSUFp?= =?utf-8?B?R3hsTTVIM3JUMVhybEZMNUZPMGR0T253VzlRZ0s0VXhEMThNamRNTzgrSmpJ?= =?utf-8?B?dTdJYVFTeGlEa28waUFQWmtKdG42V3JvYzFGbjhYUDFCQktpTXRXMGczV01E?= =?utf-8?B?bEdQVExEZlgxby9xRnBwaWd3TXk4bXh6KzcxWEhrQTJJRktVNktXM3M4UFpO?= =?utf-8?B?MWFHSUIwMFRzeGVIMi9TL3FmZDhISmF4cFRFSHlHN0pKVHlxYk14U0RpVmp2?= =?utf-8?B?WG1Sa283L1ppb0hkeGdZbWFyWGNXNVYwZHBxaXhxcDV2dEpjQ1RzR2tjTGJW?= =?utf-8?B?eWljeFl6WTVWcWwzbDlOWmlSb3N1WCtabFp4VlB3R1hDVUVpU3JZRWx6UFBJ?= =?utf-8?B?TUNxQ1ZJY003eEYvZ1ZnNysveTdPVVQrQlR0aGFSc09ELzBEMzdwakxqUTNE?= =?utf-8?B?TFE3dzMyRXYzM1grVkRqWHA0eFhYVXA3SGpiYlhnejI3bld4YWNxZEYySUEr?= =?utf-8?B?L1ZVNkxPU3FSY0pkRW9Rc0Y5aFdlUHdIKzhoMHlmNFo1RkV6ZEFEdTVVMnVy?= =?utf-8?B?bWgvL2o2L2IvTVdxeUJZcFBJcEhIQkNsTE5XU01MdlYrOVB6VW1maW5URmNu?= =?utf-8?B?TXRVV1R6YjdRLy9PbG5FbytzeEpqWGx1dmRRVmlyN2ozZ2lVSTBDTHVPb3M5?= =?utf-8?B?a1lVcjFERElmRHVmaUFjb3dZbkFmMUtWY2c2R2RoSzBGYVF5L0ZNUk80ZlI2?= =?utf-8?B?TEV0ZE9KMVdVZklyZmJremhGRGxQYm9yS1Rmb2pVK3JuTEVCM2JRYjdTdVpp?= =?utf-8?B?QkpSWGN5ajljSHNpNG5qYnhaT3drVDFLalJ0K3I1V3lKRmNDR25BQnllVkVC?= =?utf-8?B?RDlBMUFiRSs2N2IvK2hrdnlEaEpMdkowbWJqbnh5bHI2dU5ETFRYWml6OXVk?= =?utf-8?B?KzJadnd0Y0NWcGUwdDlSdDkwekM3Qlo5SGhLZGJUZGczbTl5eGNaNVBiT2g3?= =?utf-8?B?bS9DVGE3VDFEdkZvMkJFaUZkVEJSTEY4dXk1ZzBsT1UzR1RITXRqMzcxTXVo?= =?utf-8?B?UGIyckl2Z2VXWWcvQ0NwZEc0VnpDYVhMQjA5Smw3cHNuWjhLV0pWM3ZianZx?= =?utf-8?B?cHlpaHZMMXV0SnVDYU50b25rS1l1QWhpdFN2d05Zakx3VHZta1FueERsT00z?= =?utf-8?B?NWNyRzRZYzVwcEQ3SVlNdlhCandaZWRQTUxzKy9vRlVtVG1xRHJSOUdVTzMr?= =?utf-8?B?ZXFDdzI2WnFpNDhIRDR1bFJUUU13dEJXb0tkL0dEQWRYanROV09zQTZaZERq?= =?utf-8?B?KzFhTjlLcm04MHZJUVhjcUpzK3JTR1V4STNwU3BQMWFMQ2lOYlB0T0lGWDhB?= =?utf-8?B?OE1WQ3FPWnd3OEtXWFhJRnBqWDBlOU5aV205RWMrWndRUVFWT3pPMGkvVHhl?= =?utf-8?B?Q2twbldzN0c4azR3d1lJb01TREdLWmFSUy8yanRPYS9lK1RYYi82N0ppdFpm?= =?utf-8?B?c0dzUWl4SDYzNFpIMlpqdG4yL2RCTUxtMGRzWFk0SFdvOGc0SzhvT1R5RCtn?= =?utf-8?B?TnJCM3pXSXhTMDRNSGpmWERiVXlhVnFEdzBkWStVMHZwbGJ6bHhEbWI3ekhF?= =?utf-8?Q?UNv0=3D?=
X-Microsoft-Antispam-Message-Info: 8KcmXsB7ZLAsbWqwXTTOBuSB197eQkFr+BlkmIMXjKa8GTmj2I2jg+0sBJHQvcHOkgu/CnHcdyAljWMaA2mvZBjzTn0/60PIP7gnGPk+lJnBnzBcKKW5ryrgW4bISCGdfF7xUI9+d11yCEbYF7uGQQv6mwl0WScIN2S7y2H7L5BJK8itIdH7KNxXneAI6D9O
X-Microsoft-Exchange-Diagnostics: 1; HE1PR01MB1833; 6:+WHbmpTPb4iEhzpa+TXAXPiBsOax9CQRX42J/lssF1WvwBpXVX7dgiOYbFKK3d/scW62y63sAvvgk/+WhZ7cyXAX9SEMoY91TYwLC4JzKOdFylOumbDLg53MmjfXbOpxLhO/U/42aXsDl6c/NUBKH5mrEi2ME2oC9d3XWJK8XzPDa+jDh5/GbLHs/OkKhBM1Hk0ZwzwDLqmVfkGPgVQ/f58BE5wjhi/47GLpzARM0tu5997emBbSBkpx1hC4w71qj+zcUbecyLOeB3z8ZntIH6EsUbY2lAqFIKKj+MFcQezu7k2ebflmFcvWaGtrcL73cQO5Wyxvpg57htwXuFnHJdcYLreE/NPvxmlA1NMbYKM=; 5:JEroGdUdParfez7TbrAHuGpjq9SOmWzH2igckPUjN2Jr9VHbQ/xn/6wLsGMxFej537Ig0q8CFImwphdqpQcrWq883gfDtAM3A6VAbzx333R6UVF+VdtPI9mZ2rczFHDjs3juWkJQvIYDZ+Ws/xVYoQUUOne6w2yA/RaXGrz1470=; 24:pc9xbweLao3KwTxh6QTcPSQXiuirTn3br29Acg79y42JUmFOr/b+LO1Qexsay5t16gd7EHilP8gnHkrIJgj+o/fdJOrfMtZv05e4G6uPTww=; 7:CQqdXXSxcGVZ1qacQ+8h2hWFTbIsLz58Qu/2Lk3t7T4TNHfjSHpG6ppi8AatpMV1VPJidCDwxtt9Ojcmp3VIbO+YTQ/dtBi0x5VQaJaUXiQgJbxyfqPHP/2Ztcfk6zhAaJGrAhcEdbougTRIELyD6yoQiwKdMbriHFaQMUpmhyKWrrw252ff1mEC4lMLX1goveHXPh4cPI5JM9aWd7CQyvYjftPmLSxRbTt4BaJzJHCM6lirT5LHVQiedLK1R/Ik
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: ingate.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 04 Mar 2018 17:05:55.7533 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: e44ad68f-a377-43cc-c78b-08d581f231f9
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: c3eda49a-3ed0-46c6-8a9e-d0d8ce3d2fae
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR01MB1833
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/chVocnM1LgVFXDseC4tDKeHWVGA>
Subject: Re: [tram] Review of dual allocation in TURNbis-11
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Mar 2018 17:06:04 -0000

Hi,

When we now have "dual allocation" into this draft
(I see on page 26: "If the client wishes to obtain one IPv6 and one IPv4 =
relayed transport address then it includes an ADDITIONAL-ADDRESS-FAMILY =
transport address then it")
can we not generalize that further and allow MORE THAN ONE relayed =
transport address (of any family) in response to an allocation?

I mean that a TURN server could have several relay interfaces at =
different IP-addresses into different networks - not just the Internet, =
but also a VoIP (higher quality) network e.g. by some triple play =
service provider, an IMS network or some branch office network.

I think this is specifically important for network provided/auto =
discovered turn servers (application provided turn servers could instead =
just list several turn servers).

I saw someone snipped this about "SINGLE relayed transport address per =
allocation request"
> > https://tools.ietf.org/html/rfc6156#section-3
> > <snip>
> >
> >    TURN servers allocate a single relayed transport address per
> >    allocation request.  Therefore, Allocate requests cannot carry =
more
> >    than one REQUESTED-ADDRESS-FAMILY attribute.  Consequently, a =
client
> >    that wishes to allocate more than one relayed transport address =
at a
> >    TURN server (e.g., an IPv4 and an IPv6 address) needs to perform
> >    several allocation requests (one allocation request per relayed
> >    transport address).
> > </snip>

but if that is remedied now, it seems like a small step to generalize so =
we can get multiple relayed transport addresses from one allocate =
request?

/Karl

PS: I also saw one small inconsistency when browsing through.

On page 26:=20
"7.2.  Receiving an Allocate Request

   When the server receives an Allocate request, it performs the
   following checks:

   1.   The server MUST require that the request be authenticated..."

Without mentioning (making exception from the MUST) that authentication =
may not be required (which is already mentioned on page 17:
"2.9.  Happy Eyeballs for TURN
...

   o  For clear text UDP, send TURN Allocate requests to both IP address
      families as discussed in [RFC8305], without authentication
      information. If the TURN server requires authentication, it will
      send back a 401 unauthenticated response and the TURN client uses
      the first UDP connection on which a 401 error response is
      received.  If a 401 error response is received from both IP
      address families then the TURN client can silently abandon the UDP
      connection on the IP address family with lower precedence.  If the
      TURN server does not require authentication (as described in
      Section 9 of [RFC8155]), it is possible for both Allocate requests
      to succeed."

-----Ursprungligt meddelande-----
Fr=C3=A5n: tram [mailto:tram-bounces@ietf.org] F=C3=B6r Marc =
Petit-Huguenin
Skickat: den 2 mars 2018 22:17
Till: Konda, Tirumaleswar Reddy; tram@ietf.org
=C3=84mne: Re: [tram] Review of dual allocation in TURNbis-11

As suggested by Brandon, I reviewed turnbis-14 for the modifications =
agreed on below, and found some discrepancies.  See inline.

On 02/09/2018 04:51 AM, Konda, Tirumaleswar Reddy wrote:
>> -----Original Message-----
>> From: Marc Petit-Huguenin [mailto:petithug@acm.org]
>> Sent: Sunday, October 22, 2017 9:38 PM
>> To: Konda, Tirumaleswar Reddy
>> <TirumaleswarReddy_Konda@McAfee.com>; tram@ietf.org
>> Subject: Re: [tram] Review of dual allocation in TURNbis-11
>>
>> Inline.
>>
>> On 10/16/2017 07:14 PM, Konda, Tirumaleswar Reddy wrote:
>>> Thanks Marc for the detailed review, Please see inline
>>>
>>>> -----Original Message-----
>>>> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Marc Petit-
>>>> Huguenin
>>>> Sent: Saturday, October 14, 2017 12:59 AM
>>>> To: tram@ietf.org
>>>> Subject: [tram] Review of dual allocation in TURNbis-11
>>>>

[snip]

>>>
>>>>
>>>> - Section 6.2
>>>>
>>>> I would suggest to make ADDRESS-ERROR-CODE more generic by
>> renaming
>>>> it as WARNING-CODE and use the same format than for ERROR-CODE.
>> Then
>>>> allocate a new error code for that specific warning.  I would =
suggest
>>>> to request the 0x8009 codepoint for that attribute.
>>>
>>> I don't understand the need to change ADDRESS-ERROR-CODE !
>>
>> To make it more generic and reusable in future specifications.
>=20
> ADDRESS-ERROR-CODE cannot use the same format as ERROR-CODE, =
ADDRESS-ERROR-CODE signals the IP address family for which the warning =
is generated + all the fields in the ERROR-CODE.=20
>=20
>>
>>>
>>>>
>>>> Also I think we needs two different warnings, one that states that
>>>> dual allocation is not available in a TURNbis server, but both
>>>> protocols are available, and another that says that dual allocation
>>>> failed because one of the two protocols is not available.  This is =
to
>>>> let the client know that it is useless to try another allocation =
for the
>> missing protocol.
>>>
>>> I don't get the reason for two different warnings.
>>
>> A server may support both IPv6 and IPv4 allocations and not support =
dual
>> allocation, in which case the client can do a second allocation for =
the IPv6
>> relayed address.
>=20
> If the server does not support dual allocation but supports both IPv6 =
and IPv4 allocations, it will only allocate the IPv4 relayed address and =
not will not return ADDRESS-ERROR-CODE in the response, the client will =
know the server does not understand the ADDITIONAL-ADDRESS-FAMILY =
attribute (ADDITIONAL-ADDRESS-FAMILY is a comprehension-optional =
attribute).=20
>=20
>>
>> Alternatively the server may not support IPv6 at all, in which case =
the second
>> allocation will fail and was unnecessary.
>=20
> ADDRESS-ERROR-CODE signals both unsupported IP address type (0x02 =
(IPv6 address family)) and the reason for failure (440 (unsupported =
address family)).=20
>=20
> Cheers,
> -Tiru
>=20
>>
>> Using two different warnings permits to know if the second allocation =
will
>> succeed or not.
>>
>>>
>>>>
>>>> What is the policy when reserving the next port with the EVEN-PORT
>>>> attribute in a dual allocation, but one of them fails to find a =
pair
>>>> of subsequent ports available?
>>>
>>> It's discussed in section 6.1
>>>
>>> <snip>
>>>    Clients MUST NOT
>>>    include ADDITIONAL-ADDRESS-FAMILY attribute in a Allocate request
>>>    that contains an EVEN-PORT attribute with the R bit set to 1.
>>> </snip>
>>>
>>>>
>>>> It is not said that the Allocate successful response must contain =
two
>>>> XRAs after a successful dual allocation.
>>>
>>> Good point, Updated draft.

I cannot find this update in turn-14.

>>>
>>>>
>>>> I would also suggest to add some text that says that when a TURNbis
>>>> server sends an Allocate success response, it must always send the
>>>> XRAs in the same order than the RAFs were sent.  So in case the
>>>> server sends back by mistake two XRAs, the first one matches the =
one
>> requested by the client.

Did not get answer to that and did not see it in turn-14.

>>>>
>>>> The bullet list at the end needs also to be fixed for dual =
allocation.
>>>
>>> Agreed, fixed.
>>>
>>>>
>>>> - Section 6.3
>>>>
>>>> Here's too, the text needs to be updated for the dual allocation =
case.
>>>
>>>
>>> Yup, updated.
>>>

Same, there is no update since -11 in section 7.3 (formerly 6.3)

--=20
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: https://marc.petit-huguenin.org
Profile: https://www.linkedin.com/in/petithug



From nobody Mon Mar  5 02:48:13 2018
Return-Path: <TirumaleswarReddy_Konda@mcafee.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40DD712D87D for <tram@ietfa.amsl.com>; Mon,  5 Mar 2018 02:48:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level: 
X-Spam-Status: No, score=-4.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mcafee.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DzOQDfSlDHVP for <tram@ietfa.amsl.com>; Mon,  5 Mar 2018 02:48:03 -0800 (PST)
Received: from DNVWSMAILOUT1.mcafee.com (dnvwsmailout1.mcafee.com [161.69.31.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9470B12D77E for <tram@ietf.org>; Mon,  5 Mar 2018 02:48:03 -0800 (PST)
X-NAI-Header: Modified by McAfee Email Gateway (5500)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mcafee.com; s=s_mcafee; t=1520246871; h=From: To:Subject:Thread-Topic:Thread-Index:Date: Message-ID:References:In-Reply-To:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: dlp-product:dlp-version:dlp-reaction:authentication-results: x-originating-ip:x-ms-publictraffictype:x-microsoft-exchange-diagnostics: x-ms-exchange-antispam-srfa-diagnostics:x-ms-office365-filtering-correlation-id: x-microsoft-antispam:x-ms-traffictypediagnostic: x-microsoft-antispam-prvs:x-exchange-antispam-report-test: x-exchange-antispam-report-cfa-test:x-forefront-prvs: x-forefront-antispam-report:received-spf:x-microsoft-antispam-message-info: spamdiagnosticoutput:spamdiagnosticmetadata: Content-Type:Content-Transfer-Encoding:MIME-Version: X-MS-Exchange-CrossTenant-Network-Message-Id: X-MS-Exchange-CrossTenant-originalarrivaltime: X-MS-Exchange-CrossTenant-fromentityheader: X-MS-Exchange-CrossTenant-id:X-MS-Exchange-Transport-CrossTenantHeadersStamped: X-OriginatorOrg:X-NAI-Spam-Flag:X-NAI-Spam-Threshold: X-NAI-Spam-Score:X-NAI-Spam-Version; bh=8 RyZUhHZccX6k9VyNzHkNuwSM4b4mjkYwrqEZnCm4+ E=; b=dgfKGuR2jGKU4utEYYdHcn9u5TSlhOnfYZ5ULhXPCq7f UNybhKZ2+oMADBN0ggJB+5vEqSrGwwqQ5ZPk0lh+UrzhR/Ld7D CQi/XN/Tx/eLe2lj76Uuw4P62IMXAYjwyHQf7257+rEZS1Mtg2 vRfx2RMqy0R/U5mVuvwhhNXb4h4=
Received: from DNVEXAPP1N06.corpzone.internalzone.com (DNVEXAPP1N06.corpzone.internalzone.com [10.44.48.90]) by DNVWSMAILOUT1.mcafee.com with smtp (TLS: TLSv1/SSLv3,256bits,ECDHE-RSA-AES256-SHA384) id 357c_0e42_cfe36e2b_1719_4680_b108_3be122706e0e; Mon, 05 Mar 2018 04:47:50 -0600
Received: from DNVEXUSR1N08.corpzone.internalzone.com (10.44.48.81) by DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Mon, 5 Mar 2018 03:47:26 -0700
Received: from DNVO365EDGE2.corpzone.internalzone.com (10.44.176.74) by DNVEXUSR1N08.corpzone.internalzone.com (10.44.48.81) with Microsoft SMTP Server (TLS) id 15.0.1347.2 via Frontend Transport; Mon, 5 Mar 2018 03:47:26 -0700
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (10.44.176.243) by edge.mcafee.com (10.44.176.74) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Mon, 5 Mar 2018 03:47:25 -0700
Received: from BN6PR16MB1425.namprd16.prod.outlook.com (10.172.207.19) by BN6PR16MB1858.namprd16.prod.outlook.com (10.172.29.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.548.13; Mon, 5 Mar 2018 10:47:24 +0000
Received: from BN6PR16MB1425.namprd16.prod.outlook.com ([10.172.207.19]) by BN6PR16MB1425.namprd16.prod.outlook.com ([10.172.207.19]) with mapi id 15.20.0548.016; Mon, 5 Mar 2018 10:47:24 +0000
From: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>
To: Karl Stahl <karl.stahl@ingate.com>, 'Marc Petit-Huguenin' <petithug@acm.org>, "tram@ietf.org" <tram@ietf.org>
Thread-Topic: [tram] Review of dual allocation in TURNbis-11
Thread-Index: AQHTRFmkTUXySTsG3EGzRBQMWeAaDaLmPU1QgAnZ7oCArKMPEIAhlH+AgALemwCAARktMA==
Date: Mon, 5 Mar 2018 10:47:24 +0000
Message-ID: <BN6PR16MB1425C15E7BA5D10DB86AA41DEADA0@BN6PR16MB1425.namprd16.prod.outlook.com>
References: <65c75449-152c-1ce7-7c81-460ca589d9f0@acm.org> <DM5PR16MB17881ABD54B89E14F0291C56EA4C0@DM5PR16MB1788.namprd16.prod.outlook.com> <ea84bcf9-19b6-5492-383b-18e2bc5a93bf@acm.org> <DM5PR16MB178859E2018148DBAD51635EEAF20@DM5PR16MB1788.namprd16.prod.outlook.com> <46fdf931-eb0c-c4fe-9c01-4a066134abfb@acm.org> <025201d3b3db$0e182730$2a487590$@stahl@ingate.com>
In-Reply-To: <025201d3b3db$0e182730$2a487590$@stahl@ingate.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 11.0.200.100
dlp-reaction: no-action
authentication-results: spf=none (sender IP is ) smtp.mailfrom=TirumaleswarReddy_Konda@McAfee.com; 
x-originating-ip: [103.245.47.20]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR16MB1858; 6:9fihfkYKVK1SUmJJ6rFOM2Qvg8zsgptDUH+8XA3sSLxL+Kxl8449B9OiH9/pdfjIQTw+OYQvgMoB+wrwD6DoqxIWnlmOKsyAG7UVgaTxUkKimL8cvrczAXlkP1JGwcEXTBJ2BrTj5wx0bySR1J1hiqTv/lCWg6LhdrXpkj7NLSo4KDe+bG7y5Zs7QetgQFmZgTCvknNpsilJGi+Wtv9nllWMmh7InDEyQbDTZoQBySeqoNFqx2Kj0zMDwId5+Z77cxK8bauFEnMJxf9L6ee2GMj+h+6JQqzdG4JtzuYEghtVB8IbvzXPu93rAzI/NkMoMAFz1NtnKsrO8P3MeEcaySLoGP6xoTnHbSMYF103OUmWRNO6sAkkMUSDoDKTn2Pa; 5:/CGU0fxvTuK+R476K9zeVz5Dcuw++JwNZImhzXhiWupgK8ANthUFhrOCcaRWg1TJ7zjWqRG6S7OJ4SLbydirJXTV50aYQAjeVlun3KPS7Suk61GYyzDCn3XvEbNI7R5W+gHRpAO2xP7s8/AVxEEMeQSq7H56kRNKT87i2WUQ4Ck=; 24:lHrL+ujBKh1IPCje2VfkoJMBh9UWcug7xJBtG8L/b8jWM5GmVZxNC8KMMX5JGdYLuWDDEdMuKASDRSfNSgnx6CVEHURdop4KD+zWPa9RSbM=; 7:YQYX9OHUHvQDSzEzs4BVmSpa2XW9FxbypAM7TEip9NJzKSfLYI5U64+kHbK7uNdx7R43+kmSBZW7/gzmku2dZZOsOD869y93EiH+6uu6xN6JAOwG0mvPxWJ2Cdo/wLC/rM1GSOkyA+PajiYp30NxNWViJ0ihSK1wNb2lu8uLj992u7Nxm06RHD4OsizdKYqAO99q5SWEirC01C7/S8O4+AgurBATN6nB1VQ9nRleXYJCcImF3K+zKt6rBx1FQhUY
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 89ec1d20-1e88-4ea4-f0f2-08d582867af4
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:BN6PR16MB1858; 
x-ms-traffictypediagnostic: BN6PR16MB1858:
x-microsoft-antispam-prvs: <BN6PR16MB1858C28AC92A412102D030CBEADA0@BN6PR16MB1858.namprd16.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(192374486261705)(128460861657000)(213716511872227)(81160342030619)(123452027830198);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040501)(2401047)(8121501046)(5005006)(93006095)(93001095)(3231220)(944501244)(52105095)(10201501046)(3002001)(6041288)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123562045)(20161123558120)(20161123560045)(6072148)(201708071742011); SRVR:BN6PR16MB1858; BCL:0; PCL:0; RULEID:; SRVR:BN6PR16MB1858; 
x-forefront-prvs: 06022AA85F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39850400004)(396003)(39380400002)(366004)(346002)(376002)(38534002)(189003)(199004)(252514010)(13464003)(32952001)(45080400002)(6436002)(33656002)(3846002)(966005)(8936002)(53936002)(186003)(3280700002)(93886005)(561944003)(316002)(2900100001)(25786009)(72206003)(68736007)(6306002)(478600001)(81156014)(9686003)(76176011)(110136005)(7696005)(14454004)(81166006)(2906002)(229853002)(6246003)(6116002)(55016002)(99286004)(74316002)(53546011)(106356001)(6506007)(105586002)(8676002)(7736002)(2501003)(77096007)(26005)(97736004)(305945005)(66066001)(5660300001)(80792005)(59450400001)(2950100002)(86362001)(3660700001)(102836004)(85282002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR16MB1858; H:BN6PR16MB1425.namprd16.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: McAfee.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: HHtGwEqNJzjyzhIjILYgsDjksNXqTfgwFJYn4G2KAXmW8IySMB8UDmjjo7w9CUZMV7eLiUOabzYltg9lr4vP9aELcd+8gtNuc7PpXk9ecNpVfq1w/irFFDqS19sGiU3jgDmjr4hszHoP3SWGP6Ql3YPhuRpzgZowqK0CnZpvKkozOwmpoqBVHSTZjjsyaU9OS0ZZlJzhMKXs/0+jsuJjZ2nsgsIupBTHWjOjhdg/rX7nYWBnHs6ngi9JqTwS6Eboy7fWj4A0AboYBaLes4Fgml59b/9fiWZ0jOtcZSmWqAQz67gMHTr5+PDM0cO0GEOON1wYRIMyERGnNlkwOYHUFg==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 89ec1d20-1e88-4ea4-f0f2-08d582867af4
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Mar 2018 10:47:24.2425 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4943e38c-6dd4-428c-886d-24932bc2d5de
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR16MB1858
X-OriginatorOrg: mcafee.com
X-NAI-Spam-Flag: NO
X-NAI-Spam-Threshold: 15
X-NAI-Spam-Score: 0
X-NAI-Spam-Version: 2.3.0.9418 : core <6234> : inlines <6449> : streams <1780513> : uri <2602246>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/mVnH0vZTUwwprJqy3uHlRIS1zto>
Subject: Re: [tram] Review of dual allocation in TURNbis-11
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2018 10:48:12 -0000

VGhhbmtzIEthcmwuIEkgaGF2ZSBmaXhlZCB0aGUgaW5jb25zaXN0ZW5jeS4NCg0KTkVXOg0KICAg
MS4gICBUaGUgc2VydmVyIFNIT1VMRCByZXF1aXJlIHRoYXQgdGhlIHJlcXVlc3QgYmUgYXV0aGVu
dGljYXRlZC4NCiAgICAgICAgVGhlIGF1dGhlbnRpY2F0aW9uIG9mIHRoZSByZXF1ZXN0IGlzIG9w
dGlvbmFsIHRvIGFsbG93IFRVUk4NCiAgICAgICAgc2VydmVycyBwcm92aWRlZCBieSB0aGUgbG9j
YWwgb3IgYWNjZXNzIG5ldHdvcmsgdG8gYWNjZXB0DQogICAgICAgIEFsbG9jYXRpb24gcmVxdWVz
dHMgZnJvbSBuZXcgYW5kL29yIGd1ZXN0IHVzZXJzIGluIHRoZSBuZXR3b3JrDQogICAgICAgIHdo
byBkbyBub3QgbmVjZXNzYXJpbHkgcG9zc2VzcyBsb25nIHRlcm0gY3JlZGVudGlhbHMgZm9yIFNU
VU4NCiAgICAgICAgYXV0aGVudGljYXRpb24gYW5kIGl0cyBzZWN1cml0eSBpbXBsaWNhdGlvbnMg
YXJlIGRpc2N1c3NlZCBpbg0KICAgICAgICBbUkZDODE1NV0uICBJZiB0aGUgcmVxdWVzdCBpcyBh
dXRoZW50aWNhdGVkLCB0aGUgYXV0aGVudGljYXRpb24NCiAgICAgICAgTVVTVCBiZSBkb25lIHVz
aW5nIHRoZSBsb25nLXRlcm0gY3JlZGVudGlhbCBtZWNoYW5pc20gb2YNCiAgICAgICAgW0ktRC5p
ZXRmLXRyYW0tc3R1bmJpc10gdW5sZXNzIHRoZSBjbGllbnQgYW5kIHNlcnZlciBhZ3JlZSB0bw0K
ICAgICAgICB1c2UgYW5vdGhlciBtZWNoYW5pc20gdGhyb3VnaCBzb21lIHByb2NlZHVyZSBvdXRz
aWRlIHRoZSBzY29wZQ0KICAgICAgICBvZiB0aGlzIGRvY3VtZW50Lg0KDQpXRyBoYXMgZGlzY3Vz
c2VkIGFuZCBhZ3JlZWQgb25seSBvbiBkdWFsIGFsbG9jYXRpb24gYW5kIHlvdXIgcHJvcG9zYWwg
dG8gcmV0dXJuIG11bHRpcGxlIHJlbGF5ZWQgdHJhbnNwb3J0IGFkZHJlc3NlcyBvZiB0aGUgc2Ft
ZSBmYW1pbHkgaXMgbmV3IHdvcmsgYW5kIHRoZSBuZWVkIGZvciB0aGlzIGVuaGFuY2VtZW50IG5l
ZWRzIHRvIGJlIGRpc2N1c3NlZCBhbmQgYWdyZWVkIGluIHRoZSBXRy4NCkEgbmV3IGRyYWZ0IGxv
b2tzIG1vcmUgc3VpdGFibGUgdG8gZGlzY3VzcyB0aGlzIGVuaGFuY2VtZW50Lg0KDQotVGlydQ0K
DQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IEthcmwgU3RhaGwgW21haWx0
bzprYXJsLnN0YWhsQGluZ2F0ZS5jb21dDQo+IFNlbnQ6IFN1bmRheSwgTWFyY2ggNCwgMjAxOCAx
MDozNiBQTQ0KPiBUbzogJ01hcmMgUGV0aXQtSHVndWVuaW4nIDxwZXRpdGh1Z0BhY20ub3JnPjsg
S29uZGEsIFRpcnVtYWxlc3dhciBSZWRkeQ0KPiA8VGlydW1hbGVzd2FyUmVkZHlfS29uZGFATWNB
ZmVlLmNvbT47IHRyYW1AaWV0Zi5vcmcNCj4gU3ViamVjdDogU1Y6IFt0cmFtXSBSZXZpZXcgb2Yg
ZHVhbCBhbGxvY2F0aW9uIGluIFRVUk5iaXMtMTENCj4gDQo+IEhpLA0KPiANCj4gV2hlbiB3ZSBu
b3cgaGF2ZSAiZHVhbCBhbGxvY2F0aW9uIiBpbnRvIHRoaXMgZHJhZnQgKEkgc2VlIG9uIHBhZ2Ug
MjY6ICJJZiB0aGUNCj4gY2xpZW50IHdpc2hlcyB0byBvYnRhaW4gb25lIElQdjYgYW5kIG9uZSBJ
UHY0IHJlbGF5ZWQgdHJhbnNwb3J0IGFkZHJlc3MgdGhlbg0KPiBpdCBpbmNsdWRlcyBhbiBBRERJ
VElPTkFMLUFERFJFU1MtRkFNSUxZIHRyYW5zcG9ydCBhZGRyZXNzIHRoZW4gaXQiKSBjYW4NCj4g
d2Ugbm90IGdlbmVyYWxpemUgdGhhdCBmdXJ0aGVyIGFuZCBhbGxvdyBNT1JFIFRIQU4gT05FIHJl
bGF5ZWQgdHJhbnNwb3J0DQo+IGFkZHJlc3MgKG9mIGFueSBmYW1pbHkpIGluIHJlc3BvbnNlIHRv
IGFuIGFsbG9jYXRpb24/DQo+IA0KPiBJIG1lYW4gdGhhdCBhIFRVUk4gc2VydmVyIGNvdWxkIGhh
dmUgc2V2ZXJhbCByZWxheSBpbnRlcmZhY2VzIGF0IGRpZmZlcmVudCBJUC0NCj4gYWRkcmVzc2Vz
IGludG8gZGlmZmVyZW50IG5ldHdvcmtzIC0gbm90IGp1c3QgdGhlIEludGVybmV0LCBidXQgYWxz
byBhIFZvSVANCj4gKGhpZ2hlciBxdWFsaXR5KSBuZXR3b3JrIGUuZy4gYnkgc29tZSB0cmlwbGUg
cGxheSBzZXJ2aWNlIHByb3ZpZGVyLCBhbiBJTVMNCj4gbmV0d29yayBvciBzb21lIGJyYW5jaCBv
ZmZpY2UgbmV0d29yay4NCj4gDQo+IEkgdGhpbmsgdGhpcyBpcyBzcGVjaWZpY2FsbHkgaW1wb3J0
YW50IGZvciBuZXR3b3JrIHByb3ZpZGVkL2F1dG8gZGlzY292ZXJlZA0KPiB0dXJuIHNlcnZlcnMg
KGFwcGxpY2F0aW9uIHByb3ZpZGVkIHR1cm4gc2VydmVycyBjb3VsZCBpbnN0ZWFkIGp1c3QgbGlz
dCBzZXZlcmFsDQo+IHR1cm4gc2VydmVycykuDQo+IA0KPiBJIHNhdyBzb21lb25lIHNuaXBwZWQg
dGhpcyBhYm91dCAiU0lOR0xFIHJlbGF5ZWQgdHJhbnNwb3J0IGFkZHJlc3MgcGVyDQo+IGFsbG9j
YXRpb24gcmVxdWVzdCINCj4gPiA+IGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM2MTU2
I3NlY3Rpb24tMw0KPiA+ID4gPHNuaXA+DQo+ID4gPg0KPiA+ID4gICAgVFVSTiBzZXJ2ZXJzIGFs
bG9jYXRlIGEgc2luZ2xlIHJlbGF5ZWQgdHJhbnNwb3J0IGFkZHJlc3MgcGVyDQo+ID4gPiAgICBh
bGxvY2F0aW9uIHJlcXVlc3QuICBUaGVyZWZvcmUsIEFsbG9jYXRlIHJlcXVlc3RzIGNhbm5vdCBj
YXJyeSBtb3JlDQo+ID4gPiAgICB0aGFuIG9uZSBSRVFVRVNURUQtQUREUkVTUy1GQU1JTFkgYXR0
cmlidXRlLiAgQ29uc2VxdWVudGx5LCBhDQo+IGNsaWVudA0KPiA+ID4gICAgdGhhdCB3aXNoZXMg
dG8gYWxsb2NhdGUgbW9yZSB0aGFuIG9uZSByZWxheWVkIHRyYW5zcG9ydCBhZGRyZXNzIGF0IGEN
Cj4gPiA+ICAgIFRVUk4gc2VydmVyIChlLmcuLCBhbiBJUHY0IGFuZCBhbiBJUHY2IGFkZHJlc3Mp
IG5lZWRzIHRvIHBlcmZvcm0NCj4gPiA+ICAgIHNldmVyYWwgYWxsb2NhdGlvbiByZXF1ZXN0cyAo
b25lIGFsbG9jYXRpb24gcmVxdWVzdCBwZXIgcmVsYXllZA0KPiA+ID4gICAgdHJhbnNwb3J0IGFk
ZHJlc3MpLg0KPiA+ID4gPC9zbmlwPg0KPiANCj4gYnV0IGlmIHRoYXQgaXMgcmVtZWRpZWQgbm93
LCBpdCBzZWVtcyBsaWtlIGEgc21hbGwgc3RlcCB0byBnZW5lcmFsaXplIHNvIHdlIGNhbg0KPiBn
ZXQgbXVsdGlwbGUgcmVsYXllZCB0cmFuc3BvcnQgYWRkcmVzc2VzIGZyb20gb25lIGFsbG9jYXRl
IHJlcXVlc3Q/DQo+IA0KPiAvS2FybA0KPiANCj4gUFM6IEkgYWxzbyBzYXcgb25lIHNtYWxsIGlu
Y29uc2lzdGVuY3kgd2hlbiBicm93c2luZyB0aHJvdWdoLg0KPiANCj4gT24gcGFnZSAyNjoNCj4g
IjcuMi4gIFJlY2VpdmluZyBhbiBBbGxvY2F0ZSBSZXF1ZXN0DQo+IA0KPiAgICBXaGVuIHRoZSBz
ZXJ2ZXIgcmVjZWl2ZXMgYW4gQWxsb2NhdGUgcmVxdWVzdCwgaXQgcGVyZm9ybXMgdGhlDQo+ICAg
IGZvbGxvd2luZyBjaGVja3M6DQo+IA0KPiAgICAxLiAgIFRoZSBzZXJ2ZXIgTVVTVCByZXF1aXJl
IHRoYXQgdGhlIHJlcXVlc3QgYmUgYXV0aGVudGljYXRlZC4uLiINCj4gDQo+IFdpdGhvdXQgbWVu
dGlvbmluZyAobWFraW5nIGV4Y2VwdGlvbiBmcm9tIHRoZSBNVVNUKSB0aGF0IGF1dGhlbnRpY2F0
aW9uDQo+IG1heSBub3QgYmUgcmVxdWlyZWQgKHdoaWNoIGlzIGFscmVhZHkgbWVudGlvbmVkIG9u
IHBhZ2UgMTc6DQo+ICIyLjkuICBIYXBweSBFeWViYWxscyBmb3IgVFVSTg0KPiAuLi4NCj4gDQo+
ICAgIG8gIEZvciBjbGVhciB0ZXh0IFVEUCwgc2VuZCBUVVJOIEFsbG9jYXRlIHJlcXVlc3RzIHRv
IGJvdGggSVAgYWRkcmVzcw0KPiAgICAgICBmYW1pbGllcyBhcyBkaXNjdXNzZWQgaW4gW1JGQzgz
MDVdLCB3aXRob3V0IGF1dGhlbnRpY2F0aW9uDQo+ICAgICAgIGluZm9ybWF0aW9uLiBJZiB0aGUg
VFVSTiBzZXJ2ZXIgcmVxdWlyZXMgYXV0aGVudGljYXRpb24sIGl0IHdpbGwNCj4gICAgICAgc2Vu
ZCBiYWNrIGEgNDAxIHVuYXV0aGVudGljYXRlZCByZXNwb25zZSBhbmQgdGhlIFRVUk4gY2xpZW50
IHVzZXMNCj4gICAgICAgdGhlIGZpcnN0IFVEUCBjb25uZWN0aW9uIG9uIHdoaWNoIGEgNDAxIGVy
cm9yIHJlc3BvbnNlIGlzDQo+ICAgICAgIHJlY2VpdmVkLiAgSWYgYSA0MDEgZXJyb3IgcmVzcG9u
c2UgaXMgcmVjZWl2ZWQgZnJvbSBib3RoIElQDQo+ICAgICAgIGFkZHJlc3MgZmFtaWxpZXMgdGhl
biB0aGUgVFVSTiBjbGllbnQgY2FuIHNpbGVudGx5IGFiYW5kb24gdGhlIFVEUA0KPiAgICAgICBj
b25uZWN0aW9uIG9uIHRoZSBJUCBhZGRyZXNzIGZhbWlseSB3aXRoIGxvd2VyIHByZWNlZGVuY2Uu
ICBJZiB0aGUNCj4gICAgICAgVFVSTiBzZXJ2ZXIgZG9lcyBub3QgcmVxdWlyZSBhdXRoZW50aWNh
dGlvbiAoYXMgZGVzY3JpYmVkIGluDQo+ICAgICAgIFNlY3Rpb24gOSBvZiBbUkZDODE1NV0pLCBp
dCBpcyBwb3NzaWJsZSBmb3IgYm90aCBBbGxvY2F0ZSByZXF1ZXN0cw0KPiAgICAgICB0byBzdWNj
ZWVkLiINCj4gDQo+IC0tLS0tVXJzcHJ1bmdsaWd0IG1lZGRlbGFuZGUtLS0tLQ0KPiBGcsOlbjog
dHJhbSBbbWFpbHRvOnRyYW0tYm91bmNlc0BpZXRmLm9yZ10gRsO2ciBNYXJjIFBldGl0LUh1Z3Vl
bmluDQo+IFNraWNrYXQ6IGRlbiAyIG1hcnMgMjAxOCAyMjoxNw0KPiBUaWxsOiBLb25kYSwgVGly
dW1hbGVzd2FyIFJlZGR5OyB0cmFtQGlldGYub3JnDQo+IMOEbW5lOiBSZTogW3RyYW1dIFJldmll
dyBvZiBkdWFsIGFsbG9jYXRpb24gaW4gVFVSTmJpcy0xMQ0KPiANCj4gQXMgc3VnZ2VzdGVkIGJ5
IEJyYW5kb24sIEkgcmV2aWV3ZWQgdHVybmJpcy0xNCBmb3IgdGhlIG1vZGlmaWNhdGlvbnMgYWdy
ZWVkDQo+IG9uIGJlbG93LCBhbmQgZm91bmQgc29tZSBkaXNjcmVwYW5jaWVzLiAgU2VlIGlubGlu
ZS4NCj4gDQo+IE9uIDAyLzA5LzIwMTggMDQ6NTEgQU0sIEtvbmRhLCBUaXJ1bWFsZXN3YXIgUmVk
ZHkgd3JvdGU6DQo+ID4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4+IEZyb206IE1h
cmMgUGV0aXQtSHVndWVuaW4gW21haWx0bzpwZXRpdGh1Z0BhY20ub3JnXQ0KPiA+PiBTZW50OiBT
dW5kYXksIE9jdG9iZXIgMjIsIDIwMTcgOTozOCBQTQ0KPiA+PiBUbzogS29uZGEsIFRpcnVtYWxl
c3dhciBSZWRkeQ0KPiA+PiA8VGlydW1hbGVzd2FyUmVkZHlfS29uZGFATWNBZmVlLmNvbT47IHRy
YW1AaWV0Zi5vcmcNCj4gPj4gU3ViamVjdDogUmU6IFt0cmFtXSBSZXZpZXcgb2YgZHVhbCBhbGxv
Y2F0aW9uIGluIFRVUk5iaXMtMTENCj4gPj4NCj4gPj4gSW5saW5lLg0KPiA+Pg0KPiA+PiBPbiAx
MC8xNi8yMDE3IDA3OjE0IFBNLCBLb25kYSwgVGlydW1hbGVzd2FyIFJlZGR5IHdyb3RlOg0KPiA+
Pj4gVGhhbmtzIE1hcmMgZm9yIHRoZSBkZXRhaWxlZCByZXZpZXcsIFBsZWFzZSBzZWUgaW5saW5l
DQo+ID4+Pg0KPiA+Pj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4+Pj4gRnJvbTog
dHJhbSBbbWFpbHRvOnRyYW0tYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIE1hcmMgUGV0
aXQtDQo+ID4+Pj4gSHVndWVuaW4NCj4gPj4+PiBTZW50OiBTYXR1cmRheSwgT2N0b2JlciAxNCwg
MjAxNyAxMjo1OSBBTQ0KPiA+Pj4+IFRvOiB0cmFtQGlldGYub3JnDQo+ID4+Pj4gU3ViamVjdDog
W3RyYW1dIFJldmlldyBvZiBkdWFsIGFsbG9jYXRpb24gaW4gVFVSTmJpcy0xMQ0KPiA+Pj4+DQo+
IA0KPiBbc25pcF0NCj4gDQo+ID4+Pg0KPiA+Pj4+DQo+ID4+Pj4gLSBTZWN0aW9uIDYuMg0KPiA+
Pj4+DQo+ID4+Pj4gSSB3b3VsZCBzdWdnZXN0IHRvIG1ha2UgQUREUkVTUy1FUlJPUi1DT0RFIG1v
cmUgZ2VuZXJpYyBieQ0KPiA+PiByZW5hbWluZw0KPiA+Pj4+IGl0IGFzIFdBUk5JTkctQ09ERSBh
bmQgdXNlIHRoZSBzYW1lIGZvcm1hdCB0aGFuIGZvciBFUlJPUi1DT0RFLg0KPiA+PiBUaGVuDQo+
ID4+Pj4gYWxsb2NhdGUgYSBuZXcgZXJyb3IgY29kZSBmb3IgdGhhdCBzcGVjaWZpYyB3YXJuaW5n
LiAgSSB3b3VsZA0KPiA+Pj4+IHN1Z2dlc3QgdG8gcmVxdWVzdCB0aGUgMHg4MDA5IGNvZGVwb2lu
dCBmb3IgdGhhdCBhdHRyaWJ1dGUuDQo+ID4+Pg0KPiA+Pj4gSSBkb24ndCB1bmRlcnN0YW5kIHRo
ZSBuZWVkIHRvIGNoYW5nZSBBRERSRVNTLUVSUk9SLUNPREUgIQ0KPiA+Pg0KPiA+PiBUbyBtYWtl
IGl0IG1vcmUgZ2VuZXJpYyBhbmQgcmV1c2FibGUgaW4gZnV0dXJlIHNwZWNpZmljYXRpb25zLg0K
PiA+DQo+ID4gQUREUkVTUy1FUlJPUi1DT0RFIGNhbm5vdCB1c2UgdGhlIHNhbWUgZm9ybWF0IGFz
IEVSUk9SLUNPREUsDQo+IEFERFJFU1MtRVJST1ItQ09ERSBzaWduYWxzIHRoZSBJUCBhZGRyZXNz
IGZhbWlseSBmb3Igd2hpY2ggdGhlIHdhcm5pbmcgaXMNCj4gZ2VuZXJhdGVkICsgYWxsIHRoZSBm
aWVsZHMgaW4gdGhlIEVSUk9SLUNPREUuDQo+ID4NCj4gPj4NCj4gPj4+DQo+ID4+Pj4NCj4gPj4+
PiBBbHNvIEkgdGhpbmsgd2UgbmVlZHMgdHdvIGRpZmZlcmVudCB3YXJuaW5ncywgb25lIHRoYXQg
c3RhdGVzIHRoYXQNCj4gPj4+PiBkdWFsIGFsbG9jYXRpb24gaXMgbm90IGF2YWlsYWJsZSBpbiBh
IFRVUk5iaXMgc2VydmVyLCBidXQgYm90aA0KPiA+Pj4+IHByb3RvY29scyBhcmUgYXZhaWxhYmxl
LCBhbmQgYW5vdGhlciB0aGF0IHNheXMgdGhhdCBkdWFsIGFsbG9jYXRpb24NCj4gPj4+PiBmYWls
ZWQgYmVjYXVzZSBvbmUgb2YgdGhlIHR3byBwcm90b2NvbHMgaXMgbm90IGF2YWlsYWJsZS4gIFRo
aXMgaXMNCj4gPj4+PiB0byBsZXQgdGhlIGNsaWVudCBrbm93IHRoYXQgaXQgaXMgdXNlbGVzcyB0
byB0cnkgYW5vdGhlciBhbGxvY2F0aW9uDQo+ID4+Pj4gZm9yIHRoZQ0KPiA+PiBtaXNzaW5nIHBy
b3RvY29sLg0KPiA+Pj4NCj4gPj4+IEkgZG9uJ3QgZ2V0IHRoZSByZWFzb24gZm9yIHR3byBkaWZm
ZXJlbnQgd2FybmluZ3MuDQo+ID4+DQo+ID4+IEEgc2VydmVyIG1heSBzdXBwb3J0IGJvdGggSVB2
NiBhbmQgSVB2NCBhbGxvY2F0aW9ucyBhbmQgbm90IHN1cHBvcnQNCj4gPj4gZHVhbCBhbGxvY2F0
aW9uLCBpbiB3aGljaCBjYXNlIHRoZSBjbGllbnQgY2FuIGRvIGEgc2Vjb25kIGFsbG9jYXRpb24N
Cj4gPj4gZm9yIHRoZSBJUHY2IHJlbGF5ZWQgYWRkcmVzcy4NCj4gPg0KPiA+IElmIHRoZSBzZXJ2
ZXIgZG9lcyBub3Qgc3VwcG9ydCBkdWFsIGFsbG9jYXRpb24gYnV0IHN1cHBvcnRzIGJvdGggSVB2
NiBhbmQNCj4gSVB2NCBhbGxvY2F0aW9ucywgaXQgd2lsbCBvbmx5IGFsbG9jYXRlIHRoZSBJUHY0
IHJlbGF5ZWQgYWRkcmVzcyBhbmQgbm90IHdpbGwgbm90DQo+IHJldHVybiBBRERSRVNTLUVSUk9S
LUNPREUgaW4gdGhlIHJlc3BvbnNlLCB0aGUgY2xpZW50IHdpbGwga25vdyB0aGUNCj4gc2VydmVy
IGRvZXMgbm90IHVuZGVyc3RhbmQgdGhlIEFERElUSU9OQUwtQUREUkVTUy1GQU1JTFkgYXR0cmli
dXRlDQo+IChBRERJVElPTkFMLUFERFJFU1MtRkFNSUxZIGlzIGEgY29tcHJlaGVuc2lvbi1vcHRp
b25hbCBhdHRyaWJ1dGUpLg0KPiA+DQo+ID4+DQo+ID4+IEFsdGVybmF0aXZlbHkgdGhlIHNlcnZl
ciBtYXkgbm90IHN1cHBvcnQgSVB2NiBhdCBhbGwsIGluIHdoaWNoIGNhc2UNCj4gPj4gdGhlIHNl
Y29uZCBhbGxvY2F0aW9uIHdpbGwgZmFpbCBhbmQgd2FzIHVubmVjZXNzYXJ5Lg0KPiA+DQo+ID4g
QUREUkVTUy1FUlJPUi1DT0RFIHNpZ25hbHMgYm90aCB1bnN1cHBvcnRlZCBJUCBhZGRyZXNzIHR5
cGUgKDB4MDINCj4gKElQdjYgYWRkcmVzcyBmYW1pbHkpKSBhbmQgdGhlIHJlYXNvbiBmb3IgZmFp
bHVyZSAoNDQwICh1bnN1cHBvcnRlZCBhZGRyZXNzDQo+IGZhbWlseSkpLg0KPiA+DQo+ID4gQ2hl
ZXJzLA0KPiA+IC1UaXJ1DQo+ID4NCj4gPj4NCj4gPj4gVXNpbmcgdHdvIGRpZmZlcmVudCB3YXJu
aW5ncyBwZXJtaXRzIHRvIGtub3cgaWYgdGhlIHNlY29uZCBhbGxvY2F0aW9uDQo+ID4+IHdpbGwg
c3VjY2VlZCBvciBub3QuDQo+ID4+DQo+ID4+Pg0KPiA+Pj4+DQo+ID4+Pj4gV2hhdCBpcyB0aGUg
cG9saWN5IHdoZW4gcmVzZXJ2aW5nIHRoZSBuZXh0IHBvcnQgd2l0aCB0aGUgRVZFTi1QT1JUDQo+
ID4+Pj4gYXR0cmlidXRlIGluIGEgZHVhbCBhbGxvY2F0aW9uLCBidXQgb25lIG9mIHRoZW0gZmFp
bHMgdG8gZmluZCBhDQo+ID4+Pj4gcGFpciBvZiBzdWJzZXF1ZW50IHBvcnRzIGF2YWlsYWJsZT8N
Cj4gPj4+DQo+ID4+PiBJdCdzIGRpc2N1c3NlZCBpbiBzZWN0aW9uIDYuMQ0KPiA+Pj4NCj4gPj4+
IDxzbmlwPg0KPiA+Pj4gICAgQ2xpZW50cyBNVVNUIE5PVA0KPiA+Pj4gICAgaW5jbHVkZSBBRERJ
VElPTkFMLUFERFJFU1MtRkFNSUxZIGF0dHJpYnV0ZSBpbiBhIEFsbG9jYXRlIHJlcXVlc3QNCj4g
Pj4+ICAgIHRoYXQgY29udGFpbnMgYW4gRVZFTi1QT1JUIGF0dHJpYnV0ZSB3aXRoIHRoZSBSIGJp
dCBzZXQgdG8gMS4NCj4gPj4+IDwvc25pcD4NCj4gPj4+DQo+ID4+Pj4NCj4gPj4+PiBJdCBpcyBu
b3Qgc2FpZCB0aGF0IHRoZSBBbGxvY2F0ZSBzdWNjZXNzZnVsIHJlc3BvbnNlIG11c3QgY29udGFp
bg0KPiA+Pj4+IHR3byBYUkFzIGFmdGVyIGEgc3VjY2Vzc2Z1bCBkdWFsIGFsbG9jYXRpb24uDQo+
ID4+Pg0KPiA+Pj4gR29vZCBwb2ludCwgVXBkYXRlZCBkcmFmdC4NCj4gDQo+IEkgY2Fubm90IGZp
bmQgdGhpcyB1cGRhdGUgaW4gdHVybi0xNC4NCj4gDQo+ID4+Pg0KPiA+Pj4+DQo+ID4+Pj4gSSB3
b3VsZCBhbHNvIHN1Z2dlc3QgdG8gYWRkIHNvbWUgdGV4dCB0aGF0IHNheXMgdGhhdCB3aGVuIGEg
VFVSTmJpcw0KPiA+Pj4+IHNlcnZlciBzZW5kcyBhbiBBbGxvY2F0ZSBzdWNjZXNzIHJlc3BvbnNl
LCBpdCBtdXN0IGFsd2F5cyBzZW5kIHRoZQ0KPiA+Pj4+IFhSQXMgaW4gdGhlIHNhbWUgb3JkZXIg
dGhhbiB0aGUgUkFGcyB3ZXJlIHNlbnQuICBTbyBpbiBjYXNlIHRoZQ0KPiA+Pj4+IHNlcnZlciBz
ZW5kcyBiYWNrIGJ5IG1pc3Rha2UgdHdvIFhSQXMsIHRoZSBmaXJzdCBvbmUgbWF0Y2hlcyB0aGUN
Cj4gPj4+PiBvbmUNCj4gPj4gcmVxdWVzdGVkIGJ5IHRoZSBjbGllbnQuDQo+IA0KPiBEaWQgbm90
IGdldCBhbnN3ZXIgdG8gdGhhdCBhbmQgZGlkIG5vdCBzZWUgaXQgaW4gdHVybi0xNC4NCj4gDQo+
ID4+Pj4NCj4gPj4+PiBUaGUgYnVsbGV0IGxpc3QgYXQgdGhlIGVuZCBuZWVkcyBhbHNvIHRvIGJl
IGZpeGVkIGZvciBkdWFsIGFsbG9jYXRpb24uDQo+ID4+Pg0KPiA+Pj4gQWdyZWVkLCBmaXhlZC4N
Cj4gPj4+DQo+ID4+Pj4NCj4gPj4+PiAtIFNlY3Rpb24gNi4zDQo+ID4+Pj4NCj4gPj4+PiBIZXJl
J3MgdG9vLCB0aGUgdGV4dCBuZWVkcyB0byBiZSB1cGRhdGVkIGZvciB0aGUgZHVhbCBhbGxvY2F0
aW9uIGNhc2UuDQo+ID4+Pg0KPiA+Pj4NCj4gPj4+IFl1cCwgdXBkYXRlZC4NCj4gPj4+DQo+IA0K
PiBTYW1lLCB0aGVyZSBpcyBubyB1cGRhdGUgc2luY2UgLTExIGluIHNlY3Rpb24gNy4zIChmb3Jt
ZXJseSA2LjMpDQo+IA0KPiAtLQ0KPiBNYXJjIFBldGl0LUh1Z3VlbmluDQo+IEVtYWlsOiBtYXJj
QHBldGl0LWh1Z3VlbmluLm9yZw0KPiBCbG9nOiBodHRwczovL21hcmMucGV0aXQtaHVndWVuaW4u
b3JnDQo+IFByb2ZpbGU6IGh0dHBzOi8vd3d3LmxpbmtlZGluLmNvbS9pbi9wZXRpdGh1Zw0KPiAN
Cg0K


From nobody Mon Mar  5 09:07:34 2018
Return-Path: <petithug@acm.org>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17D1C12EB8F; Mon,  5 Mar 2018 09:07:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.441
X-Spam-Level: 
X-Spam-Status: No, score=-0.441 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oKFfSNYfOkQF; Mon,  5 Mar 2018 09:06:59 -0800 (PST)
Received: from implementers.org (unknown [92.243.22.217]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A142312EB5F; Mon,  5 Mar 2018 09:06:44 -0800 (PST)
Received: from [IPv6:2601:648:8301:730f:b85e:a711:a0c4:7650] (unknown [IPv6:2601:648:8301:730f:b85e:a711:a0c4:7650]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 75CD6AE8D9; Mon,  5 Mar 2018 18:06:41 +0100 (CET)
From: Marc Petit-Huguenin <petithug@acm.org>
To: Dale Worley <worley@ariadne.com>, gen-art@ietf.org
Cc: draft-ietf-tram-stunbis.all@ietf.org, ietf@ietf.org, tram@ietf.org
References: <151906144357.18629.1445621426796368031@ietfa.amsl.com>
Message-ID: <99f8564f-bcff-0f8b-cf32-8ab3c7692bb8@acm.org>
Date: Mon, 5 Mar 2018 09:06:38 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <151906144357.18629.1445621426796368031@ietfa.amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="EOaH01Yjg9GoCq4kpYwfGBWL8NF5lBcCe"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/gL_exG3xJGmvZP1_YKU02vyo1QU>
Subject: Re: [tram] Genart last call review of draft-ietf-tram-stunbis-15
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2018 17:07:12 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--EOaH01Yjg9GoCq4kpYwfGBWL8NF5lBcCe
Content-Type: multipart/mixed; boundary="bnGBxACVfkCKHH6Lmj0gj4EK1q1mSUJ1O";
 protected-headers="v1"
From: Marc Petit-Huguenin <petithug@acm.org>
To: Dale Worley <worley@ariadne.com>, gen-art@ietf.org
Cc: draft-ietf-tram-stunbis.all@ietf.org, ietf@ietf.org, tram@ietf.org
Message-ID: <99f8564f-bcff-0f8b-cf32-8ab3c7692bb8@acm.org>
Subject: Re: [tram] Genart last call review of draft-ietf-tram-stunbis-15
References: <151906144357.18629.1445621426796368031@ietfa.amsl.com>
In-Reply-To: <151906144357.18629.1445621426796368031@ietfa.amsl.com>

--bnGBxACVfkCKHH6Lmj0gj4EK1q1mSUJ1O
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Thanks for the thorough review, please see inline.

I'll publish -16 today before the cut-off.

On 02/19/2018 09:30 AM, Dale Worley wrote:
> Reviewer: Dale Worley
> Review result: Ready with Issues
>=20
> I am the assigned Gen-ART reviewer for this draft.  The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> Document:  draft-ietf-tram-stunbis-15
> Reviewer:  Dale R. Worley
> Review Date:  2018-02-19
> IETF LC End Date:  2018-02-20
> IESG Telechat date:  [unknown]
>=20
> Summary:
>=20
>        This draft is on the right track but has open issues, described
>        in the review.
>=20
> Overall, the draft is quite well organized and well written.  But
> there are a number of open issues that have substantial technical
> content.  I suspect that the intended design does not have these
> issues, and the issues that I see are just where the text hasn't been
> fully updated to match the intended design.
>=20
> Dale
>=20
> ----------------------------------------------------------------------
>=20
> There is an issue that shows up in several placeqs:  The NAT may
> forward the request using an IP family that is different from the IP
> family that it received the request using.  This means that the
> "source IP family of the request" may depend on whether one is
> speaking of the client or the server.  The draft is cognizant of this,
> and mentions its consequences in sections 6.3.3 and 12.  But this also
> has consequences for ALTERNATE-SERVER:  Section 14.15 says "The IP
> address family MUST be identical to that of the source IP address of
> the request." even though that family might not be usable by the
> client.  The draft doesn't seem to explicitly say that this comes from
> address-switching by the NAT.  It would help if there was a
> higher-level discussion of this matter, pointing to the various
> consequences.

I agree that some high-level text on this is needed, not just because of =
the usage of STUNbis as a Binding server (in section 12), but also to pro=
vide some guidelines to other STUN Usages (e.g. TURN).

Unfortunately I am running out of time before the cut-off so I am going t=
o publish without additional text addressing that concern, and will prepa=
re something for the next version.

>=20
> The text contains these references to SHA algorithms (that it does not
> itself define).  Some should be corrected:
>=20
>     HMAC-SHA1
>     HMAC-SHA-1
> should be HMAC-SHA1 per RFC 2104
>     HMAC-SHA256
>     HMAC-SHA-256
> should be HMAC-SHA256 per RFC 6151, but HMAC-SHA-256 per RFC 6151!
>     SHA1
>     SHA-1
> It appears that the proper name of this function is SHA-1.
>     SHA256
>     SHA-256
> NIST calls this algorithm SHA-256.

Fixed.

>=20
> 3.  Terminology
>=20
> This section needs to be updated to reference RFC 8174.

Already reported and fixed.

>=20
> 4.  Definitions
>=20
> Although the definitions of STUN Client and STUN Server mention that
> they receive responses and requests (respectively), they don't mention
> that they also receive indications.

Fixed.

>=20
> 5.  STUN Message Structure
>=20
>    All STUN messages MUST start with a 20-byte header followed by zero
>    or more Attributes.
>=20
> It would be clearer, I think, to say "All STUN messages comprise a
> 20-byte header followed by zero or more Attributes."

Applied.

>=20
> 6.2.2.  Sending over TCP or TLS-over-TCP
>=20
>    The client MAY send multiple transactions over a single TCP (or TLS-=

>    over-TCP) connection, and it MAY send another request before
>    receiving a response to the previous.
>=20
> s/the previous./the previous request./

Fixed.

>=20
> This section should also state whether or not a server is allowed to
> provide responses in a different order than it received the requests,
> if it receives further requests before sending a response.

This section talks about the sending side, so I do not think we should mi=
x server side stuff in there.

So I added the following paragraph at the end of section 6.3.1.2:

  The server is allowed to send responses in a different order than it
  received the requests.

>=20
>    o   if multiplexing other application protocols over that port, has
>        finished using that other application, and
>=20
> s/that other application/that other protocol/

Applied.

>=20
> 6.3.4.  Processing an Error Response
>=20
>     o  If the error code is 300 through 399, the client SHOULD consider=

>        the transaction as failed unless the ALTERNATE-SERVER extension =
is
>        being used.  See Section 10.
>=20
> This syntax binds "section 10" to the entire preceding sentence, whose
> topic is error codes 300-399, whereas "section 10" only applies to
> ALTERNATE-SERVER.  A better syntax would be
>=20
>     o  If the error code is 300 through 399, the client SHOULD consider=

>        the transaction as failed unless the ALTERNATE-SERVER extension
>        (Section 10) is being used.

Applied.

>=20
> 9.2.  Long-Term Credential Mechanism
>=20
>    Note that the long-term credential mechanism cannot be used to
>    protect indications, since indications cannot be challenged.  Usages=

>    utilizing indications must either use a short-term credential or omi=
t
>    authentication and message integrity for them.
>=20
> Alternatively, if there has been a recent request transaction between
> the client and the server, then a nonce have been established, and an
> indication can be sent securely using the long-term mechanism.
> (Although there is no mechanism for signaling if the nonce has become
> stale.)  It seems to me plausible that some usage may wish to exploit
> this possibility.

The consequence of doing this is that indications (most likely TURN indic=
ations carrying data) may be lost because the nonce either expired or was=
 invalidated on the server side ("Servers can invalidate nonces in order =
to provide additional security.").  A specific STUN Usage may find a way =
to mitigate the issue for the former reason (e.g. adding a way for the cl=
ient to know the nonce lifetime, and so be sure that a transaction is exe=
cuted before that time), but mitigation for the latter are more complex (=
sending an indication in the reverse direction to signal the invalidation=
?).  We can just say that future usages will have to figure that out, but=
 that seems a bit perilous.

So I'd like to hear from the WG on that.  Meanwhile I am deferring action=
 on that comment.

>=20
> 9.2.1.  Bid Down Attack Prevention
>=20
>    To indicate that it supports this specification, a server MUST
>    prepend the NONCE attribute value with the character string composed=

>    of "obMatJos2" concatenated with the Base64 [RFC4648] encoding of th=
e
>    24 bit STUN Security Features as defined in Section 17.1.
>=20
> It might be informative to note that the encoding of the security
> features is always four characters long:
> s/the Base64 [RFC4648] encoding/the (4 character) Base64 [RFC4648] enco=
ding/

Applied.

>=20
> 9.2.2.  HMAC Key
>=20
>    The structure of the key when used with long-term credentials
>    facilitates deployment in systems that also utilize SIP.  Typically,=

>    SIP systems utilizing SIP's digest authentication mechanism do not
>    actually store the password in the database.
>=20
> Presumably there should be an explicit reference [RFC3261] here.

Added.

>=20
> 9.2.3.  Forming a Request
>=20
> This section defines "first request from the client to the server" as
> being "identified by its IP address and port".  However in section
> 9.2.3.1, "the server" is "identified by hostname, if the DNS
> procedures of Section 8 are used, else IP address if not".  These are
> not the same, and presumably need to be aligned on the correct
> definition.  (And perhaps one section can simply refer to the
> definition in the other section.)  Alternatively, they may be intended
> to be different, in which case the text needs to be clarified and also
> warn the reader.

That text was already in RFC 5389, but I agree that it needs to be fixed.=


I removed the text in 9.2.3.1, and used it as replacement in 9.2.3:

 9.2.3.  Forming a Request

  There are two cases when forming a request.  In the first case, this
  is the first request from the client to the server (as identified by
  hostname, if the DNS procedures of Section 8 are used, else IP
  address if not). =20

  [...]

 9.2.3.1.  First Request

  If the client has not completed a successful request/response
  transaction with the server, it MUST omit the USERNAME, USERHASH,

>=20
> 9.2.3.1.  First Request
>=20
>    In other words, the very first request is sent [...]
>=20
> It seems better style to omit "very", given that "first request" has a
> specific meaning.

Removed.

>=20
> 9.2.4.  Receiving a Request
>=20
>       The
>       server MUST ensure that the same NONCE cannot be selected for
>       clients that use different source IP addresses, different source
>       ports, or both different source IP addresses and source ports.
>=20
> It seems clearer to phrase this condition "The server MUST NOT choose
> the same NONCE for two requests unless they have the same source IP
> address and port."

That's far better.

Applied.

>=20
>    o  If the NONCE attribute starts with the "nonce cookie" with the
>       STUN Security Feature "Password algorithm" bit set to 1 but
>       PASSWORD-ALGORITHMS does not match the value sent in the response=

>       that sent this NONCE, then the server MUST generate an error
>       response with an error code of 400 (Bad Request).
>=20
>    o  If the NONCE attribute starts with the "nonce cookie" with the
>       STUN Security Feature "Password algorithm" bit set to 1 but the
>       request contains neither PASSWORD-ALGORITHMS nor PASSWORD-
>       ALGORITHM, then the request is processed as though PASSWORD-
>       ALGORITHM were MD5 (Note that if the original PASSWORD-ALGORITHMS=

>       attribute did not contain MD5, this will result in a 400 Bad
>       Request in a later step below).
>=20
>    o  If the NONCE attribute starts with the "nonce cookie" with the
>       STUN Security Feature "Password algorithm" bit set to 1 but only
>       one of PASSWORD-ALGORITHM or PASSWORD-ALGORITHMS is present, then=

>       the server MUST generate an error response with an error code of
>       400 (Bad Request).
>=20
>    o  If the NONCE attribute starts with the "nonce cookie" with the
>       STUN Security Feature "Password algorithm" bit set to 1 but
>       PASSWORD-ALGORITHM does not match one of the entries in PASSWORD-=

>       ALGORITHMS, then the server MUST generate an error response with
>       an error code of 400 (Bad Request).
>=20
> Given these cases all include one long condition, it seems like it
> would be clearer if they were grouped and the condition factored out:
>=20
>    o  If the NONCE attribute starts with the "nonce cookie" with the
>       STUN Security Feature "Password algorithm" bit set to 1, the
>       server performs these checks in the order specified:
> 							     =20
>       *  If PASSWORD-ALGORITHMS does not match the value sent in the re=
sponse
> 	 that sent this NONCE, then the server MUST generate an error
> 	 response with an error code of 400 (Bad Request).
>=20
>       *  If the request contains neither PASSWORD-ALGORITHMS nor PASSWO=
RD-
> 	 ALGORITHM, then the request is processed as though PASSWORD-
> 	 ALGORITHM were MD5 (Note that if the original PASSWORD-ALGORITHMS
> 	 attribute did not contain MD5, this will result in a 400 Bad
> 	 Request in a later step below).
>=20
>       *  If=20
> 	 only one of PASSWORD-ALGORITHM or PASSWORD-ALGORITHMS is present, the=
n
> 	 the server MUST generate an error response with an error code of
> 	 400 (Bad Request).
>=20
>       *  If PASSWORD-ALGORITHM does not match one of the entries in PAS=
SWORD-
> 	 ALGORITHMS, then the server MUST generate an error response with
> 	 an error code of 400 (Bad Request).
>=20
> This could be further shortened and clarified by using the negation of
> the condition we desire:
>=20
>    o  If the NONCE attribute starts with the "nonce cookie" with the
>       STUN Security Feature "Password algorithm" bit set to 1, the
>       server performs these checks in the order specified:
> 							     =20
>       *  If the request contains neither PASSWORD-ALGORITHMS nor PASSWO=
RD-
> 	 ALGORITHM, then the request is processed as though PASSWORD-
> 	 ALGORITHM were MD5 (Note that if the original PASSWORD-ALGORITHMS
> 	 attribute did not contain MD5, this will result in a 400 Bad
> 	 Request in a later step below).
>=20
>       *  Otherwise, unless (1) PASSWORD-ALGORITHM and
> 	 PASSWORD-ALGORITHMS are both present, (2) PASSWORD-ALGORITHMS
> 	 matches the value sent in the response that sent this NONCE,
> 	 and (3) PASSWORD-ALGORITHM matches one of the entries in
> 	 PASSWORD-ALGORITHMS, the server MUST generate an error
> 	 response with an error code of 400 (Bad Request).
>=20
> --

Also far better that the original.

Applied.

>=20
>       Servers can
>       invalidate nonces in order to provide additional security.
>=20
> It's not clear what "invalidate" means here.  The text has been
> talking about nonces expiring, which suggests that it is not a process
> that the server actively causes at the time the nonce becomes invalid,
> but "invalidate" suggests that the server causes it at the moment of
> invalidation.

It is an action by the operator of the server that immediately shorten th=
e lifetime of the nonce and will trigger the allocation of a new nonce.  =
To align the terminology with RFC 7009, I changed the word "invalidate" t=
o "revoke".

>=20
>       See Section 4.3 of [RFC7616] for guidelines.
>=20
> There is no section 4.3 in RFC 7616.

Already reported and fixed.

>=20
> 9.2.5.  Receiving a Response
>=20
>    If the test succeeds and the "nonce cookie" has
>    the STUN Security Feature "Username anonymity" bit set to 1 but no
>    USERHASH attribute is present, then the client MUST NOT retry the
>    request with a new transaction.
>=20
> I can find no reference to the server sending USERHASH in a response,
> so I don't understand what this means.  I think what was intended is
> "... is set to 1, then the client MUST NOT retry the request using the
> USERHASH attribute."  But that requirement seems to be stated in the
> next paragraph:
>=20
>    If the response is an error response with an error code of 401
>    (Unauthenticated), the client SHOULD retry the request with a new
>    transaction.  [...]
>    If the "nonce cookie" was present and had
>    the STUN Security Feature "Username anonymity" bit set to 1 then the=

>    USERHASH attribute MUST be used, else the USERNAME attribute MUST be=

>    used.

It looks like a bad case of copy and paste.  I removed the sentence altog=
ether.

>=20
> --
>=20
>    For all other responses, if the NONCE attribute
>    starts with the "nonce cookie" with the STUN Security Feature "User
>    anonymity" bit set to 1 but USERHASH is not present, the response
>    MUST be ignored.
>=20
> As above.

Also removed.

>=20
> The above texts suggest that there is, or was, an intention that the
> server would reflect back the USERHASH value in responses.  But
> checking all the mentions of "USERHASH", I can find no text saying
> that USERHASH will ever appear in responses.  This design decision
> needs to be verified and the text updated correspondingly.

USERHASH is a replacement for USERNAME so it should never appear in a res=
ponse.

The copy and paste mistake is probably because I forgot at the time that =
the "Username anonymity" and the "Password algorithms" are not exactly sy=
mmetrical. The latter requires in a response to be accompanied with a PAS=
SWORD-ALGORITHMS attribute, whereas the former does not require any addit=
ional attribute.

>=20
>    If the response is an error response with an error code of 400, and
>    does not contains either MESSAGE-INTEGRITY or MESSAGE-INTEGRITY-
>    SHA256 attribute then the response MUST be discarded, as if it was
>    never received.  This means that retransmits, if applicable, will
>    continue.
>=20
> Some responses generated according to this specification will not pass
> the above check.  E.g., from section 9.2.4 item 2:
>=20
>    o  If the message contains a MESSAGE-INTEGRITY or a MESSAGE-
>       INTEGRITY-SHA256 attribute, but is missing either the USERNAME or=

>       USERHASH, REALM, or NONCE attribute, the server MUST generate an
>       error response with an error code of 400 (Bad Request).  This
>       response SHOULD NOT include a USERNAME, USERHASH, NONCE, or REALM=
=2E
>       The response cannot contain a MESSAGE-INTEGRITY or MESSAGE-
>       INTEGRITY-SHA256 attribute, as the attributes required to generat=
e
>       them are missing.
>=20
> How does the client effectively receive the error response in this
> situation?

When the transaction times out.  RFC 5389 does something similar.

See my email in the TRAM mailing-list on 12/20/2016 10:26 AM PT "More iss=
ues with RFC 5389".

But it took me a few hours to remember why that was done like this, so I =
added a note:

 Note:  In that case the 400 will never reach the application,
    resulting in a timeout.

>=20
> 10.  ALTERNATE-SERVER Mechanism
>=20
> To be clearer, the first paragraph should mention that the
> ALTERNATE-SERVER attribute carries an IP address, not a domain name
> (see section 14.15).  In particular, that disambiguates the test for
> "same server" in the last paragraph.

Added.

>=20
>    The error response
>    message MAY be authenticated; however, there are uses cases for
>    ALTERNATE-SERVER where authentication of the response is not possibl=
e
>    or practical.
>=20
> s/uses cases/use cases/

Fixed.

>=20
>    If the client has been redirected to a
>    server on which it has already tried this request within the last
>    five minutes, [...]
>=20
> It is a little more formal to say "to a server to which it has already
> sent this request ...".

Applied.

>=20
> 11.  Backwards Compatibility with RFC 3489
>=20
>    Any STUN request or indication
>    without the magic cookie (see Section 6 of [RFC5389]) over DTLS MUST=

>    always result in an error.
>=20
> The meaning is clear, but in this document, "error" seems to be
> limited to error responses.  Perhaps better is:
>=20
>    Any STUN request or indication
>    without the magic cookie (see Section 6 of [RFC5389]) over DTLS MUST=

>    be considered invalid: requests MUST generate error responses and
>    indications MUST be ignored.

Applied

>=20
> Also, what error code should be used?

I chose 500, the text now look like this:

 In addition to the backward compatibility already described in
 Section 12 of [RFC5389], DTLS MUST NOT be used with [RFC3489] (also
 referred to as "classic STUN").  Any STUN request or indication
 without the magic cookie (see Section 6 of [RFC5389]) over DTLS MUST
 be considered invalid: all requests MUST generate a "500 Server
 Error" error response and indications MUST be ignored.

>=20
> 13.  STUN Usages
>=20
>    A usage would also define:
>=20
> I'm sure you don't want to use the subjunctive mood here, so perhaps
> s/would/will/.  OTOH, you might want to s/would/must/, or "A usage
> also defines:" to parallel the first sentence of the paragraph.

I used "A usage also defines:"

>=20
> 14.  STUN Attributes
>=20
> Note that there is an important ordering restriction on attributes:
> the attributes MESSAGE-INTEGRITY, MESSAGE-INTEGRITY-SHA256, and
> FINGERPRINT must, if present, appear finally and in that order.  There
> also seems to be a rule that any attributes which follow one of these
> attributes in violation of that rule MUST be ignored.
>=20
> This is described in those attribute definitions, but it's a global
> constraint in the use of attributes, and I think should be pointed out
> at this level of the specification.
>=20
> I'm nervous about the "must be ignored" rule, as it becomes a little
> complicated to do the processing right in all cases.  Perhaps it would
> be better to declare that any such violation invalidates the message
> instead?

The situation in RFC 5389:

1. Paragraph 3 of section 15 states that only the first occurence of an a=
ttribute needs to be processed and any duplicate MAY be ignored.  Thus op=
ening the possibility of multiple occurrence of the same attribute type (=
which is now used in TURN to receive multiple XOR-RELAYED-ADDRESS attribu=
tes).

Notice that there is nothing that says the multiple occurrences must be c=
onsecutive.

2. Paragraph 1 of section 15.4 states that all attributes following MESSA=
GE-INTEGRITY must be ignored, at the exception of the FINGERPRINT attribu=
te.

3. Paragraph 1 of section 15.5 states that the FINGERPRINT attribute MUST=
 be the last attribute.

Now STUNbis uses (2) to its advantage by redefining that meaning, saying =
that a compliant implementation of STUNbis looks for a MESSAGE-INTEGRITY-=
265 after the MESSAGE-INTEGGRITY.  That's what makes both versions work w=
ith each other.

We need to keep the "must be ignored" rule because when MESSAGE-INTEGRITY=
-265 will be close to be broken, we will release STUNter that will add an=
other MESSAGE-INTEGRITY-XXX attribute (that's how we do HMAC agility).  I=
f we invalidate the message then a future upgrade will not be possible.

>=20
> 14.3.  USERNAME
>=20
>    The value of USERNAME is a variable-length value. =20
>=20
> This doesn't actually say what the value is.  Better:
>=20
>    The value of USERNAME is a variable-length value containing the
>    authentication username.

Applied.

>=20
> 14.5.  MESSAGE-INTEGRITY
>=20
>    Since it uses the SHA1 hash, the HMAC will be
>    at 20 bytes.
>=20
> I think "at" should be omitted.

Removed.

>=20
>    The text used as input to HMAC is the STUN message, including the
>    header, up to and including the attribute preceding the MESSAGE-
>    INTEGRITY attribute.  With the exception of the MESSAGE-INTEGRITY-
>    SHA256 and FINGERPRINT attributes, which appear after MESSAGE-
>    INTEGRITY, agents MUST ignore all other attributes that follow
>    MESSAGE-INTEGRITY.
>=20
> This paragraph is troublesome.  The matter of attribute ordering is
> discussed above under section 14.  But the description of calculating
> the MAC disagrees with the description in the fourth paragraph.  My
> suspicion is that the fourth paragraph is correct.  My choice would be
> to omit this paragraph and leave its topics to be dealt with
> elsewhere.

I think that there is two issues here.  First is that the fact that agent=
s MUST ignore everything but the MESSAGE-INTEGRITY-SHA256 and FINGERPRINT=
 is irrelevant to the MESSAGE-INTEGRITY attribute.  I moved that sentence=
 to the end of section 9 as this is common behavior for all authenticatio=
n schemes:

  Note that agents MUST ignore all attributes that follow MESSAGE-
  INTEGRITY, with the exception of the MESSAGE-INTEGRITY-SHA256 and
  FINGERPRINT attributes.  Similarly agents MUST ignore all attributes
  that follow the MESSAGE-INTEGRITY-SHA256 attribute if the MESSAGE-
  INTEGRITY attribute is not present, with the exception of the
  FINGERPRINT attribute.

The second issue is that the fact that the input text stops at the end of=
 the preceding attribute is not in the following paragraph.  See next ans=
wer for that.

>=20
>    Based on the rules above, the hash used to construct MESSAGE-
>    INTEGRITY includes the length field from the STUN message header.
>    Prior to performing the hash, the MESSAGE-INTEGRITY attribute MUST b=
e
>    inserted into the message (with dummy content).  The length MUST the=
n
>    be set to point to the length of the message up to, and including,
>    the MESSAGE-INTEGRITY attribute itself, but excluding any attributes=

>    after it.  Once the computation is performed, the value of the
>    MESSAGE-INTEGRITY attribute can be filled in, and the value of the
>    length in the STUN header can be set to its correct value -- the
>    length of the entire message.  Similarly, when validating the
>    MESSAGE-INTEGRITY, the length field should be adjusted to point to
>    the end of the MESSAGE-INTEGRITY attribute prior to calculating the
>    HMAC.  Such adjustment is necessary when attributes, such as
>    FINGERPRINT, appear after MESSAGE-INTEGRITY.
>=20
> I would rephrase this slightly, borrowing from the second paragraph:
>=20
>    The text used as input to HMAC is the STUN message, up to and
>    including the MESSAGE-INTEGRITY attribute.  The length field of the
>    STUN message header is adjusted to point to the end of the
>    MESSAGE-INTEGRITY attribute.  The value of the MESSAGE-INTEGRITY
>    attribute is set to the dummy value ***.
>=20
>    Once the computation is performed, the value of the
>    MESSAGE-INTEGRITY attribute is filled in, and the value of the
>    length in the STUN header is set to its correct value -- the
>    length of the entire message.  Similarly, when validating the
>    MESSAGE-INTEGRITY, the length field must be adjusted to point to
>    the end of the MESSAGE-INTEGRITY attribute and the value of the
>    attribute set to ***  prior to calculating the
>    HMAC.  Such adjustment is necessary when attributes, such as
>    FINGERPRINT, appear after MESSAGE-INTEGRITY.

No, the input is up to and including the attribute *preceding* the MESSAG=
E-INTEGRITY attribute.  The message attribute is only counted when calcul=
ating the length in the header (yeah, that's really confusing, but we had=
 RFC 5769 to help).

So I reused your text, modified accordingly.  I also completely removed t=
he second paragraph and added a reference to RFC 5769:

  The text used as input to HMAC is the STUN message, up to and
  including the attribute preceding the MESSAGE-INTEGRITY attribute.
  The length field of the STUN message header is adjusted to point to
  the end of the MESSAGE-INTEGRITY attribute.  The value of the
  MESSAGE-INTEGRITY attribute is set to a dummy value.

  Once the computation is performed, the value of the MESSAGE-INTEGRITY
  attribute is filled in, and the value of the length in the STUN
  header is set to its correct value -- the length of the entire
  message.  Similarly, when validating the MESSAGE-INTEGRITY, the
  length field in the STUN header must be adjusted to point to the end
  of the MESSAGE-INTEGRITY attribute prior to calculating the HMAC over
  the STUN message, up to and including the attribute preceding the
  MESSAGE-INTEGRITY attribute.  Such adjustment is necessary when
  attributes, such as FINGERPRINT and MESSAGE-INTEGRITY-SHA256, appear
  after MESSAGE-INTEGRITY.  See also [RFC5769] for examples of such
  calculations.

>=20
> Also, the text doesn't specify what the "dummy content" is!

As explained above the content of the MESSAGE-INTEGRITY is not used when =
computing the hash, so the content itself is irrelevant.

>=20
> 14.6.  MESSAGE-INTEGRITY-SHA256
>=20
> This section has the same problems regarding the HMAC calculation as
> section 14.5.

I removed the second paragraph altogether and rewrote the last paragraph =
to mirror the new text in MESSAGE-INTEGRITY:

  The text used as input to HMAC is the STUN message, up to and
  including the attribute preceding the MESSAGE-INTEGRITY-SHA256
  attribute.  The length field of the STUN message header is adjusted
  to point to the end of the MESSAGE-INTEGRITY-SHA256 attribute.  The
  value of the MESSAGE-INTEGRITY-SHA256 attribute is set to a dummy
  value.

  Once the computation is performed, the value of the MESSAGE-
  INTEGRITY-SHA256 attribute is filled in, and the value of the length
  in the STUN header is set to its correct value -- the length of the
  entire message.  Similarly, when validating the MESSAGE-INTEGRITY-
  SHA256, the length field in the STUN header must be adjusted to point
  to the end of the MESSAGE-INTEGRITY-SHA256 attribute prior to
  calculating the HMAC over the STUN message, up to and including the
  attribute preceding the MESSAGE-INTEGRITY-SHA256 attribute.  Such
  adjustment is necessary when attributes, such as FINGERPRINT, appear
  after MESSAGE-INTEGRITY-SHA256.  See also Appendix B.1 for examples
  of such calculations.

>=20
> The discussion of truncation seems to assume that the reader already
> fully understands the concept.  Better would be to explain it
> explicitly, since that doesn't take more words:
>=20
>    The MESSAGE-INTEGRITY-SHA256 attribute can be present in any STUN
>    message type.  The MESSAGE-INTEGRITY-SHA256 attribute contains an
>    initial portion of the HMAC-SHA-256 [RFC2104] of the STUN message.
>    The value will be at most 32 bytes and MUST be a positive multiple
>    of 4 bytes.  The value must be the full 32 bytes unless the STUN
>    usage explicitly specifies that truncation is allowed.  Usages may
>    specify a minimum length longer than 4 bytes.

The text now reads:

  The MESSAGE-INTEGRITY-SHA256 attribute contains an HMAC-SHA256
  [RFC2104] of the STUN message.  The MESSAGE-INTEGRITY-SHA256
  attribute can be present in any STUN message type.  The MESSAGE-
  INTEGRITY-SHA256 attribute contains an initial portion of the HMAC-
  SHA-256 [RFC2104] of the STUN message.  The value will be at most 32
  bytes and MUST be a positive multiple of 4 bytes.  The HMAC MUST NOT
  be truncated below a minimum size of 16 bytes.  The value must be the
  full 32 bytes unless the STUN Usage explicitly specifies that
  truncation is allowed.  STUN Usages may specify a minimum length
  longer than 4 bytes.

>=20
> 14.7.  FINGERPRINT
>=20
>    The FINGERPRINT attribute MAY be present in all STUN messages.  The
>    value of the attribute is computed as the CRC-32 of the STUN message=

>    up to (but excluding) the FINGERPRINT attribute itself, [...]
>=20
> Note that unlike the MESSAGE-INTEGRITY attributes, the FINGERPRINT
> calculation does not prepare the text by adjusting the Length field of
> the header.  Verify that this is what is intended and perhaps mention
> it explicitly.

That is how it works in RFC 5389, so we should not change it.  Note that =
the fact that the field is not updated is implicit with the fact that FIN=
GERPRINT MUST be the last one (second paragraph)
and that the fourth paragraph states that "[the length field in the STUN =
header] must be correct and include the CRC attribute as part of the mess=
age length, prior to computation of the CRC."

I updated the whole section to take in account MESSAGE-INTEGRITY-SHA256.

>=20
>    [...] up to (but excluding) the FINGERPRINT attribute itself, XOR'ed=
 with
>    the 32-bit value 0x5354554e (the XOR helps in cases where an
>    application packet is also using CRC-32 in it).
>=20
> This is awkward.  Perhaps unpack it into:
>=20
>    The value of the attribute is computed as the CRC-32 of the STUN
>    message up to (but excluding) the FINGERPRINT attribute itself,
>    XOR'ed with the 32-bit value 0x5354554e.  (The XOR operation
>    ensures that the FINGERPRINT test will not report a false positive
>    on a packet containing a CRC-32 generated by an application
>    protocol.)

Applied.

>=20
> 14.8.  ERROR-CODE
>=20
>    The Reserved bits SHOULD be 0, and are for alignment on 32-bit
>    boundaries.  Receivers MUST ignore these bits.  The Class represents=

>    the hundreds digit of the error code.  The value MUST be between 3
>    and 6.  The Number represents the error code modulo 100, and its
>    value MUST be between 0 and 99.
>=20
> How is Number encoded?  I suspect that binary is intended, but it is
> an 8-bit field holding a two-digit decimal number, and so might
> plausibly be encoded as two nibbles containing the two digits.

Right.  New text:

  The Reserved bits SHOULD be 0, and are for alignment on 32-bit
  boundaries.  Receivers MUST ignore these bits.  The Class represents
  the hundreds digit of the error code.  The value MUST be between 3
  and 6.  The Number represents the binary encoding of the error code
  modulo 100, and its value MUST be between 0 and 99.

>=20
> 14.9.  REALM
>=20
>    Presence in certain
>    error responses indicates that the server wishes the client to use a=

>    long-term credential for authentication.
>=20
> I think you mean s/a long-term credential/a long-term credential in
> that realm/.

Applied.

>=20
> 14.10.  NONCE
>=20
>    Note that this means that the NONCE attribute will not contain
>    actual quote characters.
>=20
> More exactly, "will not contain the surrounding quote characters".

Applied.

>=20
> But some thought should be given to using the same wording in 14.9 and
> 14.10.
>=20
> 14.11.  PASSWORD-ALGORITHMS
>=20
>    The parameters start with the actual length of the
>    parameters as a 16-bit value, followed by the parameters that are
>    specific to each algorithm.
>=20
> "actual length" should be "length (prior to padding)".

Applied.

>=20
> 14.12.  PASSWORD-ALGORITHM
>=20
>    The parameters starts with the actual length of the
>    parameters as a 16-bit value, followed by the parameters that are
>    specific to the algorithm.
>=20
> "actual length" should be "length (prior to padding)".

Applied.

>=20
> 15.1.2.  Inside Attacks
>=20
>    Fortunately, STUN
>    requests can be processed statelessly by a server, making such
>    attacks hard to launch.
>=20
> Actually, such attacks are easy to launch, but "hard to launch
> effectively".

Applied.

>=20
>    This attack is mitigated by ingress source address filtering.
>=20
> I would help to explain who is filtering and on what basis to
> implement this mitigation.

This text did not change since RFC 5389 so I am reluctant to update it.

>=20
> 15.2.4.  Attack IV: Eavesdropping
>=20
>    In this attack, the attacker forces the client to use a reflexive
>    address that routes to itself.
>=20
> "itself" usually refers to the subject of the verb in its clause,
> which is "address".  But I think "attacker" is intended, in which case
> you can phrase it "that routes to the attacker itself".

See above.

>=20
> 17.1.  STUN Security Features Registry
>=20
>    New Security Features are assigned by a Standard Action [RFC8126].
>=20
> s/Standard Action/Standards Action/ per RFC 8u126 section 4.9.

Applied.

>=20
> 17.3.2.  New Attributes
>=20
>    0xXXXX: PASSSORD-ALGORITHMS
>=20
> s/PASSSORD/PASSWORD/

Applied.

>=20
> 17.5.  Password Algorithm Registry
>=20
> I think you want to title this registry "Stun password algorithm regist=
ry".

Applied, with "STUN" instead of "Stun".

>=20
> 17.6.  STUN UDP and TCP Port Numbers
>=20
> This section should state that it is updating "Service Name and
> Transport Protocol Port Number Registry".

Applied.

>=20
> 18.  Changes since RFC 5389
>=20
> The following items should contain proper references to the mentioned R=
FCs:
>=20
>    o  Added support for DTLS-over-UDP (RFC 6347).
>=20
>    o  Aligned the RTO calculation with RFC 6298.
>=20
>    o  Added support for STUN URI (RFC 7064).
>=20
>    o  Updated the PRECIS support to RFC 8265.

Done.

>=20
> [END]
>=20
>=20

--=20
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: https://marc.petit-huguenin.org
Profile: https://www.linkedin.com/in/petithug




--bnGBxACVfkCKHH6Lmj0gj4EK1q1mSUJ1O--

--EOaH01Yjg9GoCq4kpYwfGBWL8NF5lBcCe
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEBSI+IuCHU8MsI1GjKcRFldZqfsQFAlqdeR8ACgkQKcRFldZq
fsTIFxAAq2eBzT/7Edft2oGFupf0w9mmG9mSMm0ynOk8W0CE/3hCstAvhJp70EWG
lQ9/ugQy/iZAz2jjeM1xPk5ZTkmItzsdEFRt5cAGhAlsJFa/S1z/s3j0/WGpZMop
U3D5sacx4+AKEJJHYIkH/mVezwUKSab88wY73irgnMZU7PMoDSMcI5hze2TTVrgi
CGoMe1Yyt66pnYN6JRvVcpWEqOgvFD9T/TGBCPBxJ8GZKTMjDj5KLzeM6a6D/12Y
SR/MGbPfL2e6NqZgG9SnFEkD0fMKkjl8vcbIw6QEIXLamFhBdoNO/pr3AHgbyMVO
Sldp3rTGXetgqT5kPsCtZVY8gXV8XaGRQo/IZEEtZX0A9wMXa+iZSby+SP0PJaTD
IkYU5lZdnZzlCmKGpaaIiSHH4RjjC2FSSoQiGR12/s9wxy2UBqXJlsSSH2UVSfUJ
gApfbMCInRDuGccfLFuP393IN1HBC+phBqfTHQxH3T3roFVb52J6ExHq6A7WR5Uj
P4UG2Xz7xCIr738KJXMlV2tSb9nIvLDhuZLmF0XfI/vqdVHdMi/97thnq+dxXCxv
4Dw51TgEG1BD4zf8KmxHMVu+sIVxLZku7bAf1ZjH0Y6X0a6O82TtBHMJwm5hsghL
6zbniMghGS9FexsDwKyd0K9q6ZAd8MlZZOAY9nE6Kq003XlvDX4=
=haUC
-----END PGP SIGNATURE-----

--EOaH01Yjg9GoCq4kpYwfGBWL8NF5lBcCe--


From nobody Mon Mar  5 12:28:25 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tram@ietf.org
Delivered-To: tram@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 88A731204DA; Mon,  5 Mar 2018 12:28:07 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: tram@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.74.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152028168753.31759.6745052042882127599@ietfa.amsl.com>
Date: Mon, 05 Mar 2018 12:28:07 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/X3ozso2HeII1hTuT-EWJXI0NCzA>
Subject: [tram] I-D Action: draft-ietf-tram-stunbis-16.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2018 20:28:07 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the TURN Revised and Modernized WG of the IETF.

        Title           : Session Traversal Utilities for NAT (STUN)
        Authors         : Marc Petit-Huguenin
                          Gonzalo Salgueiro
                          Jonathan Rosenberg
                          Dan Wing
                          Rohan Mahy
                          Philip Matthews
	Filename        : draft-ietf-tram-stunbis-16.txt
	Pages           : 70
	Date            : 2018-03-05

Abstract:
   Session Traversal Utilities for NAT (STUN) is a protocol that serves
   as a tool for other protocols in dealing with Network Address
   Translator (NAT) traversal.  It can be used by an endpoint to
   determine the IP address and port allocated to it by a NAT.  It can
   also be used to check connectivity between two endpoints, and as a
   keep-alive protocol to maintain NAT bindings.  STUN works with many
   existing NATs, and does not require any special behavior from them.

   STUN is not a NAT traversal solution by itself.  Rather, it is a tool
   to be used in the context of a NAT traversal solution.

   This document obsoletes RFC 5389.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tram-stunbis/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-tram-stunbis-16
https://datatracker.ietf.org/doc/html/draft-ietf-tram-stunbis-16

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-tram-stunbis-16


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Fri Mar  9 04:35:37 2018
Return-Path: <karl@ingate.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F41F126C26 for <tram@ietfa.amsl.com>; Fri,  9 Mar 2018 04:35:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.02
X-Spam-Level: 
X-Spam-Status: No, score=-1.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MSGID_MULTIPLE_AT=1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ingate.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mbmE9OzuqzQL for <tram@ietfa.amsl.com>; Fri,  9 Mar 2018 04:35:34 -0800 (PST)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0059.outbound.protection.outlook.com [104.47.1.59]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96DF51205F0 for <tram@ietf.org>; Fri,  9 Mar 2018 04:35:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ingate.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=xE9xg0+Iw4KdGaJ9lFyZ/ZvOkiOMtADFBsvFEuLhIMM=; b=RMcftwuva9OHTWGFEJ1KfXUpJx5I7a7TY//HT2l/KkN8ai56P6weME28MMcCSX71pch3IW52fgrtnXPcg/NZAYJsOtmkUALH6B+5mu6Qs2WtP3Zl10kVnbjng9Bt4FPJwhUZxFkpMRlWOK1/WRkq9vseWOQCaGlwwnyVDpLks0I=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=karl@ingate.com; 
Received: from Kallei7 (90.229.133.175) by HE1PR01MB1835.eurprd01.prod.exchangelabs.com (2a01:111:e400:7bc0::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.567.14; Fri, 9 Mar 2018 12:35:25 +0000
From: "Karl Stahl" <karl.stahl@ingate.com>
To: "'Konda, Tirumaleswar Reddy'" <TirumaleswarReddy_Konda@McAfee.com>, "'Marc Petit-Huguenin'" <petithug@acm.org>, <tram@ietf.org>
References: <65c75449-152c-1ce7-7c81-460ca589d9f0@acm.org> <DM5PR16MB17881ABD54B89E14F0291C56EA4C0@DM5PR16MB1788.namprd16.prod.outlook.com> <ea84bcf9-19b6-5492-383b-18e2bc5a93bf@acm.org> <DM5PR16MB178859E2018148DBAD51635EEAF20@DM5PR16MB1788.namprd16.prod.outlook.com> <46fdf931-eb0c-c4fe-9c01-4a066134abfb@acm.org> <025201d3b3db$0e182730$2a487590$@stahl@ingate.com> <BN6PR16MB1425C15E7BA5D10DB86AA41DEADA0@BN6PR16MB1425.namprd16.prod.outlook.com>
In-Reply-To: <BN6PR16MB1425C15E7BA5D10DB86AA41DEADA0@BN6PR16MB1425.namprd16.prod.outlook.com>
Date: Fri, 9 Mar 2018 13:35:19 +0100
Message-ID: <00a401d3b7a3$1785e700$4691b500$@stahl@ingate.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHTRFmkTUXySTsG3EGzRBQMWeAaDaLmPU1QgAnZ7oCArKMPEIAhlH+AgALemwCAARktMIAGN45g
Content-Language: sv
X-Originating-IP: [90.229.133.175]
X-ClientProxiedBy: AM4PR08CA0065.eurprd08.prod.outlook.com (2603:10a6:205:2::36) To HE1PR01MB1835.eurprd01.prod.exchangelabs.com (2a01:111:e400:7bc0::25)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: f0aa6061-e6fb-4de7-bccb-08d585ba3cbb
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(5600026)(4604075)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(2017052603328)(7153060)(7193020); SRVR:HE1PR01MB1835; 
X-Microsoft-Exchange-Diagnostics: 1; HE1PR01MB1835; 3:2TBQdOvNNAPScd7iocOOJs7KFpFmn9o6vKtAADelrVnWQgg9vF0n1gYg5cdNzpZlKL1UqPkr428iLdvmwN/WuxWCATPrYz+aAbBEYv711EOCx/UoKwTbsFxSqbLHmz7Y9ZfhRlzRxTcpYcOxlnh0gJVDEUyOGyBl1C95/Vu1wy5GgKCYp3hI9BmZscJjPb4Yi4I5hYeauY2fjm/BWG3mGZU53kw5Lw0Hde7Qa1dTXOUd3ivjJ5zTdCFisI5DOJcd; 25:gYO7YCM61SnXx0dg3h8N3fnIcNlhgHM/cVbgH9/UzYZdP7yYXrOGg6HPMZ4idiuzuS4PoCI8nTZEUqRF0EQLRJ7bdJ0eDj33hk3C8gdbxlLWtkXYWUnM8RbIe4lu+yw84+L9a9SM3jKjyiNSKR7733Qe1pLhv94pJ29wJsVNR+bfXSlkpvk9gdQ5239EKyftWgfBB87NrZIg3d+oHlv9KYsNWkAAuVhkA4hN2EvwBI+54sci9XW2XPqNcFDbIFXeG1VUuARHTmLyCEdbIAIQt28CGN0bzkSyQ/fWQVQvuiZny20q98JFv2ss2w9fQTsHRA2tGIAdvKohpg1F+M95Qw==; 31:i3vtUwQBH4Sp25aNBYCjswmLcLDuVDuoLqwFWBeKGetQIERxo9kjaILBlI3AbUBaKKUIGqx/E++3uuh6RWWH3gJ2LenHh+eZvDzVDKU1dVvOkkJJgNuX1hsj+78cCG5VtbrhhBXB3vivtD9K9lsgQRq8753kuAmGPjIpfm3KpL+97bzPBGs1zBzkM0dSkFgOfjkSjqb9IN+MIXNyKq0DLZUKYYHVdEmBUbzh+Ea8El0=
X-MS-TrafficTypeDiagnostic: HE1PR01MB1835:
X-Microsoft-Antispam-PRVS: <HE1PR01MB18350306A92B06CCAE800847B1DE0@HE1PR01MB1835.eurprd01.prod.exchangelabs.com>
X-Exchange-Antispam-Report-Test: UriScan:(158342451672863)(213716511872227)(123452027830198); 
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(3231220)(944501244)(52105095)(93006095)(93001095)(10201501046)(3002001)(6041310)(2016111802025)(20161123560045)(20161123562045)(20161123564045)(20161123558120)(6072148)(6043046)(201708071742011); SRVR:HE1PR01MB1835; BCL:0; PCL:0; RULEID:; SRVR:HE1PR01MB1835; 
X-Microsoft-Exchange-Diagnostics: 1; HE1PR01MB1835; 4:chgYud3YtsXtp8frc6xq2Tiyv5yskO7EtWib4lLIMUlcdYFE3gkeHGKdfn9mWNmVAFONMv06iSF2oH8afygERKCWqfsk98zDS4WGC7yvDmryPrK0tKlCtW2IMqhkiqEjnapN92T9/f+n4wzJ35dAel1RYoRFohXEaL9N7S9yTCnRcVYcP1z8ICLDhQ+9cEOG6olhSQC2ufWKzPIY5NVws2+gOoEIhdGxaN5JkH+teJD227SrxewXXk0i/TxwVDtF6OCc+xyC3AYvPrN74b3ZotokTkQGPIPbc5/IqvpYVFcJ2pBTE+9byD3hKrj9FkBzLE0vpzSc0TGQuwBAdb23uyhArEscTj/9VkJ8jlQOvlORS08PpXlirilSSs266PiJ
X-Forefront-PRVS: 0606BBEB39
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(39380400002)(346002)(366004)(376002)(39830400003)(396003)(38534002)(13464003)(199004)(189003)(50466002)(68736007)(61793004)(6306002)(9686003)(6666003)(2950100002)(52116002)(23676004)(76176011)(7736002)(66066001)(47776003)(305945005)(1420700001)(8746002)(8676002)(6496006)(97736004)(81166006)(6116002)(2906002)(81156014)(1857600001)(50226002)(53936002)(84116003)(14726001)(3846002)(8936002)(26005)(386003)(478600001)(53546011)(96836002)(33896004)(39060400002)(561944003)(5820100001)(186003)(106356001)(102836004)(59450400001)(44736005)(5660300001)(61296003)(316002)(25786009)(6486002)(36756003)(105586002)(110136005)(16526019)(966005)(93886005)(21314002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR01MB1835; H:Kallei7; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: ingate.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtIRTFQUjAxTUIxODM1OzIzOjRudFdXVlJFWGIvMjVnVmJVTEVkSytyTVZl?= =?utf-8?B?M3Y0ck9LNU9YaFN0STlHUXZRVzFGUCtONjFHeGJuY3hNcDhhSE1iK1NtNkcz?= =?utf-8?B?a0V3ZjVQQnA1eUZzS2JGMHh3MjFjcGpzV3VnbGZLaForNXdqRVYwV3QzaTM5?= =?utf-8?B?SmFPMitSQkIxNWJpQnYxYk1ua0N0M1lFNUpON3hmZ2Q4bU5Ia1VacWJNVG9w?= =?utf-8?B?aHRkUEJ3NHVVZkVsNFNCcnE2ZkhjSkpxR0w5QVJKWnpvdFhOMUEvUUptVlNr?= =?utf-8?B?S3JqRmc3M09Bd3pZTFg2enNGb1VLeEwyVWU2Mm5razU2M1h0YUdNdnFkTXB3?= =?utf-8?B?YWNjVzlSVTl6T1dXbHhHODJzV2l5LzdwT05nNmc1RHZuR04wRnVnL1ZEcEN5?= =?utf-8?B?L0FrNmpybEVMQzB4TVdOc1NFenZwZWJ2a3RwaTdDMkdNTzJiV2srNWJFdFlM?= =?utf-8?B?REIxNlZXOXZvQnlEN3NvTEJsdWFkaW9MNGVIYVZURG8ySTZJN2Q3TitaZ0Zq?= =?utf-8?B?cWJWeG94Ly80ak9xUDhJVWJqOE81S3lOY1ZGNEdHRUI4VUdDbDJkdjI1ZEdE?= =?utf-8?B?Zlg0aFdGSmFobElDWXJpejQvQWdiR0pyRUtmb2xzZDZhbW8xa0dUMkhtQ2VS?= =?utf-8?B?WXpkV2Q3VEc5c1cySUpWUFh5QUpsQ1dtcGk0cCs1SmlJVGlHeGJuWklnTVpa?= =?utf-8?B?YTlGcGVvVWMwdWNIWjViQ2FQa3krWDJaa2QvSllaeFN4ZE5KbjBrT0FWa0JB?= =?utf-8?B?LzR2SWhMWjlpaVVOTmNFaElVNjk4ZkZxU0lqUUlBS25tZUZFdEtRRTlnNUNJ?= =?utf-8?B?Zlp5eHU4dEV4VGk5QmNDdkw0L3c0L1Z6T2xOM0RHRE5OeUZOQjJ0dy9yaURl?= =?utf-8?B?WlcwWnUyZFlrdGJZL1F5eFlmL0FUK0MxMFd1emVrRiswcWNlMHVVTk9oMXRC?= =?utf-8?B?SHRWT0Q3NGFDaDVseGcxWitzWDZKeUUyblRSaGVaSVRTbEsvUVR0V0dUVHFQ?= =?utf-8?B?SHBGYTZKanpscmlLYk1YSzFYOW1JLzRwZGsvVXp1bWx4RXQralJ5Qm4zZUVm?= =?utf-8?B?Y2VKM0xVUzBRSkxCcGJSTE1icnoxNlBmKzVUenZEVFd5MlNzZDRBZXB2WU9k?= =?utf-8?B?OEZmMENJL3hSMGozNCtyOTROQmxrcWdPbE9XdDVQczZ0bEk3NU5jbGlnenFU?= =?utf-8?B?MHlRZ0p2K29ZQW5JK1QrdUI1YUhwNlJvL3NLU2JldnpadTJoSEEya0ROQWl3?= =?utf-8?B?UGcwTEhIVkJMZ3A2TW9kTStJZkJibkw4RG9BU0lUTWhVcU8zRlMwT1dISUx3?= =?utf-8?B?YmZXS3c2ajBBSExtTC9JNHdPWktYR1J0ZWgvbjlNVWJlMjhZRnRyTzgyTDlh?= =?utf-8?B?a2prRVdycWJRdTlFb29jL0lUUFlTcTFnT1ZKZ0ZkWS9oN05zMWpQUGtKblcz?= =?utf-8?B?YzJySy94Y0tmcnlvTk5sYzJmUS9OZkQrT0c4RjQxa1ZmdnQ2OXRnOFFVSW5t?= =?utf-8?B?OTBORU55QVJ6cFNkeCtZVXFEekE3ODZJTTAyNnAzS1o3V1lYc2p3WUcrVEFP?= =?utf-8?B?bUxZMHRmQlJpVnJKYlo4RmwxQXl5TThoaE9ZUGh4Q2hTQ1RZZWJUNkRKQURq?= =?utf-8?B?dmlBb3k4Rm9YSkswbmVlRFRlRmJDZXZtbFova3BibFAvVzRra1dVOVNGOVU0?= =?utf-8?B?eHpOdURIdk15VG01SEJUSXNuUGNIWnhoaTZKWDdwMFk0OUhwM3EyekN0V0VE?= =?utf-8?B?YVhDbWxHWXpjblNCZ1UxVnRyUVBjOFEybXQweGdQWVZIVHV2QzFKK0ZEN01E?= =?utf-8?B?VDQvSlg5SWozOGZRek9uYUFTZmNGZU5aenA0OW5taS8xQlVPTGNSR2ltZ2Uw?= =?utf-8?B?MDBVdkNTRmRmVzVPQzZwaUMzNStNVnJzMzZ1YWJCeGltamFDcThvUll0dkFa?= =?utf-8?B?SC9oMzBPSHI5T0pZQXZEcUpqakJXMGRPMnd2RnlkTnhiUHRJbFJnMkozWnN3?= =?utf-8?B?ZXlQQVlXcm93Ni9SL1ZUTjNXLzdRbmFNbnVDZ0wwSmZGVHNBbXZORkE0Vk9G?= =?utf-8?Q?oQYw=3D?=
X-Microsoft-Antispam-Message-Info: NLWf3scwSJVM/Ea8d7Ehuhiye7MB9PSHKJvE/H7DKNYUtJGNv6MWk9T61D5nIGjMQSh1Im3Q7l8QTX62D/zbeIJK6v1G/C189DTORvxnbb+CgRJJ7BRc19ZSNLumQIqLSN0XjdLjAlxHBOl9b0Js2GBnnNws2woWx6ulZGg+bBi2Rv09lcqOCYQ4Xlsw2XNu
X-Microsoft-Exchange-Diagnostics: 1; HE1PR01MB1835; 6:pPlh+YQ6ngXXNekG4gsSBZDOoGT5o/f5OZjoP1HOUCvAc96eVu+hjWxqQPkiM1/+wTMHJUvyO3rtjGw2D4D23P2ThocZ7Qdw+GuyQrO9244UHw/+kDXWVx4uUGz727af7srQUZ3AA87RssGBS3hsDedwotW22LSsozSPWnxpZ0f+vYQcBt5GHT7O0iS1JwlEehH9p4ihhuZxrieQTcKL970dEsBoErjKs/lhArDl7DUMwJ+Ris2UdrbIIoqouV1po2t61dvasumjSwVz4eSyvQ6FTMrwmaXayGNMlpb7edZKqJdBX0rushOsOP2/AjfarQAPIZI42tAlatiBqZVirR72ncXpTkOIjojv0rUqnv0=; 5:f8imBsFITC/500KYaYop+ENM8H+z506WdfLs7tk48iLh9Ol39I8kdPQ81VQhFzJQuwmuFemDYKVZdq2tka0HPl4wqWpDUEJRzt+KCCSkXGMYEodkTG7f8mrRrgAvl3WJBgKCJ4QNawI+rss57hpFm9VNhMQNzD/DUE1fcqyEMf4=; 24:n1UAQtQL5+fEnietKcO9/IV9/+NesZX+l7gCxtTQHuUmwPXvE9z+GIOXvFIrcWO9Jptia3ohYXEuBBotDJPCa/D+buLo8TALfs7hodyZES0=; 7:2bj/yOsZlsw2isW2WvVM9/LP7LJk2jPEhB1B44V5GJ/WzOVmoPyP7vVpgPaz3FVU8cyZwor1rHdVWgD0g9wgsdwY5wa71Gfei3Zbf7tL1tDoFgqIPQ6dwzEKogajFhPe0id65R0ifqvHGsgUl03xh/ZvHCgCB1nmwewsn6/Aod15uC+jT7R5MaH6UKwtunEJrLRUMtEF+itGyWfW9MhrghucgSUc6aQTEPCXuiqs7/C47tAapfwRcWrgs1wqLPE2
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: ingate.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 09 Mar 2018 12:35:25.9015 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: f0aa6061-e6fb-4de7-bccb-08d585ba3cbb
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: c3eda49a-3ed0-46c6-8a9e-d0d8ce3d2fae
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR01MB1835
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/VXvow2TUmeb1_ov6utir9rI9KX4>
Subject: [tram]  Extend dual allocation to multiple in TURNbis
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2018 12:35:36 -0000

Allowing a turn allocation to return multiple relayed transport =
addresses, beyond ONE IPv4 and ONE IPv6 (which may sit on the same or on =
different interfaces/network segments), seems like very small step now =
when the dual allocation was put in place in this draft. We certainly =
need it (some reasons below) if TURN is going to be used where needed =
and we cannot wait for any additional draft.

Seems like it is sufficient to extent this table (found in draft 14) =
with 3 new values (as shown):=20

16.  STUN Attributes

   This STUN extension defines the following attributes:

     0x000C: CHANNEL-NUMBER
     0x000D: LIFETIME
     0x0010: Reserved (was BANDWIDTH)
     0x0012: XOR-PEER-ADDRESS
     0x0013: DATA
     0x0016: XOR-RELAYED-ADDRESS
     0x0017: REQUESTED-ADDRESS-FAMILY
     0x0018: EVEN-PORT
     0x0019: REQUESTED-TRANSPORT
     0x001A: DONT-FRAGMENT
     0x0021: Reserved (was TIMER-VAL)
     0x0022: RESERVATION-TOKEN
     TBD-CA: ADDITIONAL-ADDRESS-FAMILY
ADDITIONAL-ADDRESS-ALL
ADDITIONAL-ADDRESS-ALLV4
ADDITIONAL-ADDRESS-ALLV6
     TBD-CA: ADDRESS-ERROR-CODE
     TBD-CA: ICMP

Actually, browsing through the draft for ADDITIONAL-ADDRESS-FAMILY, very =
little text seems to be added for generalization to  =
ADDITIONAL-ADDRESS-xxx. Almost everything applies to =
ADDITIONAL-ADDRESS-xxx and can be reused.

ADDITIONAL-ADDRESS-ALL should be the default for any modern TURN client. =


Check! - We need this now.

Thanks,
Karl


-----Ursprungligt meddelande-----
Fr=C3=A5n: Konda, Tirumaleswar Reddy =
[mailto:TirumaleswarReddy_Konda@McAfee.com]=20
Skickat: den 5 mars 2018 11:47
Till: Karl Stahl; 'Marc Petit-Huguenin'; tram@ietf.org
=C3=84mne: RE: [tram] Review of dual allocation in TURNbis-11

...

WG has discussed and agreed only on dual allocation and your proposal to =
return multiple relayed transport addresses of the same family is new =
work and the need for this enhancement needs to be discussed and agreed =
in the WG.
A new draft looks more suitable to discuss this enhancement.

-Tiru

> -----Original Message-----
> From: Karl Stahl [mailto:karl.stahl@ingate.com]
> Sent: Sunday, March 4, 2018 10:36 PM
> To: 'Marc Petit-Huguenin' <petithug@acm.org>; Konda, Tirumaleswar =
Reddy
> <TirumaleswarReddy_Konda@McAfee.com>; tram@ietf.org
> Subject: SV: [tram] Review of dual allocation in TURNbis-11
>=20
> Hi,
>=20
> When we now have "dual allocation" into this draft (I see on page 26: =
"If the
> client wishes to obtain one IPv6 and one IPv4 relayed transport =
address then
> it includes an ADDITIONAL-ADDRESS-FAMILY transport address then it") =
can
> we not generalize that further and allow MORE THAN ONE relayed =
transport
> address (of any family) in response to an allocation?
>=20
> I mean that a TURN server could have several relay interfaces at =
different IP-
> addresses into different networks - not just the Internet, but also a =
VoIP
> (higher quality) network e.g. by some triple play service provider, an =
IMS
> network or some branch office network.
>=20
> I think this is specifically important for network provided/auto =
discovered
> turn servers (application provided turn servers could instead just =
list several
> turn servers).
>=20
> I saw someone snipped this about "SINGLE relayed transport address per
> allocation request"
> > > https://tools.ietf.org/html/rfc6156#section-3
> > > <snip>
> > >
> > >    TURN servers allocate a single relayed transport address per
> > >    allocation request.  Therefore, Allocate requests cannot carry =
more
> > >    than one REQUESTED-ADDRESS-FAMILY attribute.  Consequently, a
> client
> > >    that wishes to allocate more than one relayed transport address =
at a
> > >    TURN server (e.g., an IPv4 and an IPv6 address) needs to =
perform
> > >    several allocation requests (one allocation request per relayed
> > >    transport address).
> > > </snip>
>=20
> but if that is remedied now, it seems like a small step to generalize =
so we can
> get multiple relayed transport addresses from one allocate request?
>=20
> /Karl



**** Left a few clips from "[tram] Review of dual allocation in =
TURNbis-11" thread
> >
> > If the server does not support dual allocation but supports both =
IPv6 and
> IPv4 allocations, it will only allocate the IPv4 relayed address and =
not will not
> return ADDRESS-ERROR-CODE in the response, the client will know the
> server does not understand the ADDITIONAL-ADDRESS-FAMILY attribute
> (ADDITIONAL-ADDRESS-FAMILY is a comprehension-optional attribute).


> >> Using two different warnings permits to know if the second =
allocation
> >> will succeed or not.
> >>



From nobody Fri Mar  9 13:14:58 2018
Return-Path: <brandon.williams@akamai.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C8211270FC for <tram@ietfa.amsl.com>; Fri,  9 Mar 2018 13:14:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g7jVlyANqt4n for <tram@ietfa.amsl.com>; Fri,  9 Mar 2018 13:14:55 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75B6B124F57 for <tram@ietf.org>; Fri,  9 Mar 2018 13:14:55 -0800 (PST)
Received: from pps.filterd (m0122330.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w29LDHxs020538; Fri, 9 Mar 2018 21:14:53 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=subject : to : references : from : message-id : date : mime-version : in-reply-to : content-type : content-transfer-encoding; s=jan2016.eng; bh=XHVDb4QIet8rlLpVsxOsIfQbCp4JJSXu/QFqQbr4Vjo=; b=oDay3Wcx6679ICPuP0odhLZDkZvlea3VYq8gJDH6XIeuvpXxTRqqYx/zMmh7q1Rf1Wse J8WuouLh09sfhOQ5SdKqgQI1mYXZQhtySRVF4VppeCFQhghsLmY/JXYmicmtwPBixGT9 9fIw22qIz7byvH4eTgdlghG9nFYps73mS23Dy6XWA0KbvpxJD1f9QY1mc0zfcPbdLJP/ NIhZWFSR0pP9OsWC82ce+e0dyJXO7wExmNzdTludcmNWbdaxkGNVG6COZ2tJOF16yhxb dGYavTP7qnIJfdANK0zR5eJXRoaBrtTddq4uJ7xcyl0CE6QV1k8BmXTuXih6aiZ9j2gk ug== 
Received: from prod-mail-ppoint3 ([96.6.114.86]) by mx0b-00190b01.pphosted.com with ESMTP id 2gkvnbgs32-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 09 Mar 2018 21:14:53 +0000
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w29LBHPS002106; Fri, 9 Mar 2018 16:14:52 -0500
Received: from prod-mail-relay14.akamai.com ([172.27.17.39]) by prod-mail-ppoint3.akamai.com with ESMTP id 2gfqx1hh12-1; Fri, 09 Mar 2018 16:14:52 -0500
Received: from [172.28.118.62] (bowill.kendall.corp.akamai.com [172.28.118.62]) by prod-mail-relay14.akamai.com (Postfix) with ESMTP id 0E12184693; Fri,  9 Mar 2018 21:14:52 +0000 (GMT)
To: Karl Stahl <karl.stahl@ingate.com>, "'Konda, Tirumaleswar Reddy'" <TirumaleswarReddy_Konda@McAfee.com>, 'Marc Petit-Huguenin' <petithug@acm.org>, tram@ietf.org
References: <65c75449-152c-1ce7-7c81-460ca589d9f0@acm.org> <DM5PR16MB17881ABD54B89E14F0291C56EA4C0@DM5PR16MB1788.namprd16.prod.outlook.com> <ea84bcf9-19b6-5492-383b-18e2bc5a93bf@acm.org> <DM5PR16MB178859E2018148DBAD51635EEAF20@DM5PR16MB1788.namprd16.prod.outlook.com> <46fdf931-eb0c-c4fe-9c01-4a066134abfb@acm.org> <025201d3b3db$0e182730$2a487590$@stahl@ingate.com> <BN6PR16MB1425C15E7BA5D10DB86AA41DEADA0@BN6PR16MB1425.namprd16.prod.outlook.com> <00a401d3b7a3$1785e700$4691b500$@stahl@ingate.com>
From: Brandon Williams <brandon.williams@akamai.com>
Message-ID: <30c7b7d7-554c-bf46-293e-bc9e71df026b@akamai.com>
Date: Fri, 9 Mar 2018 16:14:49 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <00a401d3b7a3$1785e700$4691b500$@stahl@ingate.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-09_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803090251
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-09_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803090251
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/s772_Si7i-CViUcaTCLmQ3LSX_I>
Subject: Re: [tram] Extend dual allocation to multiple in TURNbis
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2018 21:14:57 -0000

I agree with Tiru that opening up turnbis for such a change at this 
stage is not the right approach. The WG has broad consensus already on 
the scope of turnbis, and multiple addresses of each family type is not 
part of that scope.

--Brandon

On 03/09/2018 07:35 AM, Karl Stahl wrote:
> Allowing a turn allocation to return multiple relayed transport addresses, beyond ONE IPv4 and ONE IPv6 (which may sit on the same or on different interfaces/network segments), seems like very small step now when the dual allocation was put in place in this draft. We certainly need it (some reasons below) if TURN is going to be used where needed and we cannot wait for any additional draft.
> 
> Seems like it is sufficient to extent this table (found in draft 14) with 3 new values (as shown):
> 
> 16.  STUN Attributes
> 
>     This STUN extension defines the following attributes:
> 
>       0x000C: CHANNEL-NUMBER
>       0x000D: LIFETIME
>       0x0010: Reserved (was BANDWIDTH)
>       0x0012: XOR-PEER-ADDRESS
>       0x0013: DATA
>       0x0016: XOR-RELAYED-ADDRESS
>       0x0017: REQUESTED-ADDRESS-FAMILY
>       0x0018: EVEN-PORT
>       0x0019: REQUESTED-TRANSPORT
>       0x001A: DONT-FRAGMENT
>       0x0021: Reserved (was TIMER-VAL)
>       0x0022: RESERVATION-TOKEN
>       TBD-CA: ADDITIONAL-ADDRESS-FAMILY
> ADDITIONAL-ADDRESS-ALL
> ADDITIONAL-ADDRESS-ALLV4
> ADDITIONAL-ADDRESS-ALLV6
>       TBD-CA: ADDRESS-ERROR-CODE
>       TBD-CA: ICMP
> 
> Actually, browsing through the draft for ADDITIONAL-ADDRESS-FAMILY, very little text seems to be added for generalization to  ADDITIONAL-ADDRESS-xxx. Almost everything applies to ADDITIONAL-ADDRESS-xxx and can be reused.
> 
> ADDITIONAL-ADDRESS-ALL should be the default for any modern TURN client.
> 
> Check! - We need this now.
> 
> Thanks,
> Karl
> 
> 
> -----Ursprungligt meddelande-----
> FrÃ¥n: Konda, Tirumaleswar Reddy [mailto:TirumaleswarReddy_Konda@McAfee.com]
> Skickat: den 5 mars 2018 11:47
> Till: Karl Stahl; 'Marc Petit-Huguenin'; tram@ietf.org
> Ã„mne: RE: [tram] Review of dual allocation in TURNbis-11
> 
> ...
> 
> WG has discussed and agreed only on dual allocation and your proposal to return multiple relayed transport addresses of the same family is new work and the need for this enhancement needs to be discussed and agreed in the WG.
> A new draft looks more suitable to discuss this enhancement.
> 
> -Tiru
> 
>> -----Original Message-----
>> From: Karl Stahl [mailto:karl.stahl@ingate.com]
>> Sent: Sunday, March 4, 2018 10:36 PM
>> To: 'Marc Petit-Huguenin' <petithug@acm.org>; Konda, Tirumaleswar Reddy
>> <TirumaleswarReddy_Konda@McAfee.com>; tram@ietf.org
>> Subject: SV: [tram] Review of dual allocation in TURNbis-11
>>
>> Hi,
>>
>> When we now have "dual allocation" into this draft (I see on page 26: "If the
>> client wishes to obtain one IPv6 and one IPv4 relayed transport address then
>> it includes an ADDITIONAL-ADDRESS-FAMILY transport address then it") can
>> we not generalize that further and allow MORE THAN ONE relayed transport
>> address (of any family) in response to an allocation?
>>
>> I mean that a TURN server could have several relay interfaces at different IP-
>> addresses into different networks - not just the Internet, but also a VoIP
>> (higher quality) network e.g. by some triple play service provider, an IMS
>> network or some branch office network.
>>
>> I think this is specifically important for network provided/auto discovered
>> turn servers (application provided turn servers could instead just list several
>> turn servers).
>>
>> I saw someone snipped this about "SINGLE relayed transport address per
>> allocation request"
>>>> https://tools.ietf.org/html/rfc6156#section-3
>>>> <snip>
>>>>
>>>>     TURN servers allocate a single relayed transport address per
>>>>     allocation request.  Therefore, Allocate requests cannot carry more
>>>>     than one REQUESTED-ADDRESS-FAMILY attribute.  Consequently, a
>> client
>>>>     that wishes to allocate more than one relayed transport address at a
>>>>     TURN server (e.g., an IPv4 and an IPv6 address) needs to perform
>>>>     several allocation requests (one allocation request per relayed
>>>>     transport address).
>>>> </snip>
>>
>> but if that is remedied now, it seems like a small step to generalize so we can
>> get multiple relayed transport addresses from one allocate request?
>>
>> /Karl
> 
> 
> 
> **** Left a few clips from "[tram] Review of dual allocation in TURNbis-11" thread
>>>
>>> If the server does not support dual allocation but supports both IPv6 and
>> IPv4 allocations, it will only allocate the IPv4 relayed address and not will not
>> return ADDRESS-ERROR-CODE in the response, the client will know the
>> server does not understand the ADDITIONAL-ADDRESS-FAMILY attribute
>> (ADDITIONAL-ADDRESS-FAMILY is a comprehension-optional attribute).
> 
> 
>>>> Using two different warnings permits to know if the second allocation
>>>> will succeed or not.
>>>>
> 
> 
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram
> 


From nobody Fri Mar  9 13:17:02 2018
Return-Path: <brandon.williams@akamai.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECF80124F57 for <tram@ietfa.amsl.com>; Fri,  9 Mar 2018 13:16:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id srdY-IeOh8GO for <tram@ietfa.amsl.com>; Fri,  9 Mar 2018 13:16:57 -0800 (PST)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C7C21270FC for <tram@ietf.org>; Fri,  9 Mar 2018 13:16:57 -0800 (PST)
Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.16.0.22/8.16.0.22) with SMTP id w29LDKmf029250; Fri, 9 Mar 2018 21:16:47 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=subject : to : references : from : message-id : date : mime-version : in-reply-to : content-type : content-transfer-encoding; s=jan2016.eng; bh=jKarQAEy0UTcvQ/i/rEBLGjBEV25tEkNy+WcCvH2Aew=; b=AIb2QN2SIzl7iyfwNWFNYqpQFGly2ZV1wqIBakK41mLgmTEMxEGwduaQVbnbDvyAsqdB wq9TxIPd/Td48Ac+pKAtTe17udOd1ReBijXOujU3J9kZ2vcJRMeR213iBCFPazcF4wqs hp4ojgkwPx6sSyLqT7JNRwXPXWeG5P8CNcdcWExcU8uvDUYq/1mtcLyneK4ksF9K4vWh LcVcScOim/temS+2skJg1zeBYxC6KIf4MBtjg+++t/HizjVthZI0nDwYqgP+m55DuanY pXp0TmCo277fTf2Bl6c5dodnfnMxSrDjW8qMqb6kgfR8oYeoGVWyVfq9epoozojjOFkC CQ== 
Received: from prod-mail-ppoint4 ([96.6.114.87]) by m0050095.ppops.net-00190b01. with ESMTP id 2gke67uc97-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 09 Mar 2018 21:16:47 +0000
Received: from pps.filterd (prod-mail-ppoint4.akamai.com [127.0.0.1]) by prod-mail-ppoint4.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w29LFqqD002562; Fri, 9 Mar 2018 16:16:46 -0500
Received: from prod-mail-relay14.akamai.com ([172.27.17.39]) by prod-mail-ppoint4.akamai.com with ESMTP id 2gfqx11gs0-1; Fri, 09 Mar 2018 16:16:46 -0500
Received: from [172.28.118.62] (bowill.kendall.corp.akamai.com [172.28.118.62]) by prod-mail-relay14.akamai.com (Postfix) with ESMTP id C82CD84668; Fri,  9 Mar 2018 21:16:45 +0000 (GMT)
To: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>, Karl Stahl <karl.stahl@ingate.com>, 'Marc Petit-Huguenin' <petithug@acm.org>, "tram@ietf.org" <tram@ietf.org>
References: <65c75449-152c-1ce7-7c81-460ca589d9f0@acm.org> <DM5PR16MB17881ABD54B89E14F0291C56EA4C0@DM5PR16MB1788.namprd16.prod.outlook.com> <ea84bcf9-19b6-5492-383b-18e2bc5a93bf@acm.org> <DM5PR16MB178859E2018148DBAD51635EEAF20@DM5PR16MB1788.namprd16.prod.outlook.com> <46fdf931-eb0c-c4fe-9c01-4a066134abfb@acm.org> <025201d3b3db$0e182730$2a487590$@stahl@ingate.com> <BN6PR16MB1425C15E7BA5D10DB86AA41DEADA0@BN6PR16MB1425.namprd16.prod.outlook.com>
From: Brandon Williams <brandon.williams@akamai.com>
Message-ID: <a97551ca-4852-1272-ceae-2eb5e9b26520@akamai.com>
Date: Fri, 9 Mar 2018 16:16:42 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <BN6PR16MB1425C15E7BA5D10DB86AA41DEADA0@BN6PR16MB1425.namprd16.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-09_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803090252
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-09_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803090251
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/P5L4qJTZmYtw7-c1RYA-qfoE5Sk>
Subject: Re: [tram] Review of dual allocation in TURNbis-11
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2018 21:17:00 -0000

This change looks good to me.

Karl, Do you agree that it addresses the inconsistency you previously 
mentioned?

--Brandon

On 03/05/2018 05:47 AM, Konda, Tirumaleswar Reddy wrote:
> Thanks Karl. I have fixed the inconsistency.
> 
> NEW:
>     1.   The server SHOULD require that the request be authenticated.
>          The authentication of the request is optional to allow TURN
>          servers provided by the local or access network to accept
>          Allocation requests from new and/or guest users in the network
>          who do not necessarily possess long term credentials for STUN
>          authentication and its security implications are discussed in
>          [RFC8155].  If the request is authenticated, the authentication
>          MUST be done using the long-term credential mechanism of
>          [I-D.ietf-tram-stunbis] unless the client and server agree to
>          use another mechanism through some procedure outside the scope
>          of this document.
> 
> WG has discussed and agreed only on dual allocation and your proposal to return multiple relayed transport addresses of the same family is new work and the need for this enhancement needs to be discussed and agreed in the WG.
> A new draft looks more suitable to discuss this enhancement.
> 
> -Tiru
> 
>> -----Original Message-----
>> From: Karl Stahl [mailto:karl.stahl@ingate.com]
>> Sent: Sunday, March 4, 2018 10:36 PM
>> To: 'Marc Petit-Huguenin' <petithug@acm.org>; Konda, Tirumaleswar Reddy
>> <TirumaleswarReddy_Konda@McAfee.com>; tram@ietf.org
>> Subject: SV: [tram] Review of dual allocation in TURNbis-11
>>
>> Hi,
>>
>> When we now have "dual allocation" into this draft (I see on page 26: "If the
>> client wishes to obtain one IPv6 and one IPv4 relayed transport address then
>> it includes an ADDITIONAL-ADDRESS-FAMILY transport address then it") can
>> we not generalize that further and allow MORE THAN ONE relayed transport
>> address (of any family) in response to an allocation?
>>
>> I mean that a TURN server could have several relay interfaces at different IP-
>> addresses into different networks - not just the Internet, but also a VoIP
>> (higher quality) network e.g. by some triple play service provider, an IMS
>> network or some branch office network.
>>
>> I think this is specifically important for network provided/auto discovered
>> turn servers (application provided turn servers could instead just list several
>> turn servers).
>>
>> I saw someone snipped this about "SINGLE relayed transport address per
>> allocation request"
>>>> https://tools.ietf.org/html/rfc6156#section-3
>>>> <snip>
>>>>
>>>>     TURN servers allocate a single relayed transport address per
>>>>     allocation request.  Therefore, Allocate requests cannot carry more
>>>>     than one REQUESTED-ADDRESS-FAMILY attribute.  Consequently, a
>> client
>>>>     that wishes to allocate more than one relayed transport address at a
>>>>     TURN server (e.g., an IPv4 and an IPv6 address) needs to perform
>>>>     several allocation requests (one allocation request per relayed
>>>>     transport address).
>>>> </snip>
>>
>> but if that is remedied now, it seems like a small step to generalize so we can
>> get multiple relayed transport addresses from one allocate request?
>>
>> /Karl
>>
>> PS: I also saw one small inconsistency when browsing through.
>>
>> On page 26:
>> "7.2.  Receiving an Allocate Request
>>
>>     When the server receives an Allocate request, it performs the
>>     following checks:
>>
>>     1.   The server MUST require that the request be authenticated..."
>>
>> Without mentioning (making exception from the MUST) that authentication
>> may not be required (which is already mentioned on page 17:
>> "2.9.  Happy Eyeballs for TURN
>> ...
>>
>>     o  For clear text UDP, send TURN Allocate requests to both IP address
>>        families as discussed in [RFC8305], without authentication
>>        information. If the TURN server requires authentication, it will
>>        send back a 401 unauthenticated response and the TURN client uses
>>        the first UDP connection on which a 401 error response is
>>        received.  If a 401 error response is received from both IP
>>        address families then the TURN client can silently abandon the UDP
>>        connection on the IP address family with lower precedence.  If the
>>        TURN server does not require authentication (as described in
>>        Section 9 of [RFC8155]), it is possible for both Allocate requests
>>        to succeed."
>>
>> -----Ursprungligt meddelande-----
>> FrÃ¥n: tram [mailto:tram-bounces@ietf.org] FÃ¶r Marc Petit-Huguenin
>> Skickat: den 2 mars 2018 22:17
>> Till: Konda, Tirumaleswar Reddy; tram@ietf.org
>> Ã„mne: Re: [tram] Review of dual allocation in TURNbis-11
>>
>> As suggested by Brandon, I reviewed turnbis-14 for the modifications agreed
>> on below, and found some discrepancies.  See inline.
>>
>> On 02/09/2018 04:51 AM, Konda, Tirumaleswar Reddy wrote:
>>>> -----Original Message-----
>>>> From: Marc Petit-Huguenin [mailto:petithug@acm.org]
>>>> Sent: Sunday, October 22, 2017 9:38 PM
>>>> To: Konda, Tirumaleswar Reddy
>>>> <TirumaleswarReddy_Konda@McAfee.com>; tram@ietf.org
>>>> Subject: Re: [tram] Review of dual allocation in TURNbis-11
>>>>
>>>> Inline.
>>>>
>>>> On 10/16/2017 07:14 PM, Konda, Tirumaleswar Reddy wrote:
>>>>> Thanks Marc for the detailed review, Please see inline
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Marc Petit-
>>>>>> Huguenin
>>>>>> Sent: Saturday, October 14, 2017 12:59 AM
>>>>>> To: tram@ietf.org
>>>>>> Subject: [tram] Review of dual allocation in TURNbis-11
>>>>>>
>>
>> [snip]
>>
>>>>>
>>>>>>
>>>>>> - Section 6.2
>>>>>>
>>>>>> I would suggest to make ADDRESS-ERROR-CODE more generic by
>>>> renaming
>>>>>> it as WARNING-CODE and use the same format than for ERROR-CODE.
>>>> Then
>>>>>> allocate a new error code for that specific warning.  I would
>>>>>> suggest to request the 0x8009 codepoint for that attribute.
>>>>>
>>>>> I don't understand the need to change ADDRESS-ERROR-CODE !
>>>>
>>>> To make it more generic and reusable in future specifications.
>>>
>>> ADDRESS-ERROR-CODE cannot use the same format as ERROR-CODE,
>> ADDRESS-ERROR-CODE signals the IP address family for which the warning is
>> generated + all the fields in the ERROR-CODE.
>>>
>>>>
>>>>>
>>>>>>
>>>>>> Also I think we needs two different warnings, one that states that
>>>>>> dual allocation is not available in a TURNbis server, but both
>>>>>> protocols are available, and another that says that dual allocation
>>>>>> failed because one of the two protocols is not available.  This is
>>>>>> to let the client know that it is useless to try another allocation
>>>>>> for the
>>>> missing protocol.
>>>>>
>>>>> I don't get the reason for two different warnings.
>>>>
>>>> A server may support both IPv6 and IPv4 allocations and not support
>>>> dual allocation, in which case the client can do a second allocation
>>>> for the IPv6 relayed address.
>>>
>>> If the server does not support dual allocation but supports both IPv6 and
>> IPv4 allocations, it will only allocate the IPv4 relayed address and not will not
>> return ADDRESS-ERROR-CODE in the response, the client will know the
>> server does not understand the ADDITIONAL-ADDRESS-FAMILY attribute
>> (ADDITIONAL-ADDRESS-FAMILY is a comprehension-optional attribute).
>>>
>>>>
>>>> Alternatively the server may not support IPv6 at all, in which case
>>>> the second allocation will fail and was unnecessary.
>>>
>>> ADDRESS-ERROR-CODE signals both unsupported IP address type (0x02
>> (IPv6 address family)) and the reason for failure (440 (unsupported address
>> family)).
>>>
>>> Cheers,
>>> -Tiru
>>>
>>>>
>>>> Using two different warnings permits to know if the second allocation
>>>> will succeed or not.
>>>>
>>>>>
>>>>>>
>>>>>> What is the policy when reserving the next port with the EVEN-PORT
>>>>>> attribute in a dual allocation, but one of them fails to find a
>>>>>> pair of subsequent ports available?
>>>>>
>>>>> It's discussed in section 6.1
>>>>>
>>>>> <snip>
>>>>>     Clients MUST NOT
>>>>>     include ADDITIONAL-ADDRESS-FAMILY attribute in a Allocate request
>>>>>     that contains an EVEN-PORT attribute with the R bit set to 1.
>>>>> </snip>
>>>>>
>>>>>>
>>>>>> It is not said that the Allocate successful response must contain
>>>>>> two XRAs after a successful dual allocation.
>>>>>
>>>>> Good point, Updated draft.
>>
>> I cannot find this update in turn-14.
>>
>>>>>
>>>>>>
>>>>>> I would also suggest to add some text that says that when a TURNbis
>>>>>> server sends an Allocate success response, it must always send the
>>>>>> XRAs in the same order than the RAFs were sent.  So in case the
>>>>>> server sends back by mistake two XRAs, the first one matches the
>>>>>> one
>>>> requested by the client.
>>
>> Did not get answer to that and did not see it in turn-14.
>>
>>>>>>
>>>>>> The bullet list at the end needs also to be fixed for dual allocation.
>>>>>
>>>>> Agreed, fixed.
>>>>>
>>>>>>
>>>>>> - Section 6.3
>>>>>>
>>>>>> Here's too, the text needs to be updated for the dual allocation case.
>>>>>
>>>>>
>>>>> Yup, updated.
>>>>>
>>
>> Same, there is no update since -11 in section 7.3 (formerly 6.3)
>>
>> --
>> Marc Petit-Huguenin
>> Email: marc@petit-huguenin.org
>> Blog: https://marc.petit-huguenin.org
>> Profile: https://www.linkedin.com/in/petithug
>>
> 
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram
> 

-- 
Brandon Williams; Chief Architect
Cloud Networking; Akamai Technologies Inc.


From nobody Fri Mar  9 13:20:05 2018
Return-Path: <brandon.williams@akamai.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DADD127873 for <tram@ietfa.amsl.com>; Fri,  9 Mar 2018 13:20:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g6euLg21pS0K for <tram@ietfa.amsl.com>; Fri,  9 Mar 2018 13:20:02 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0DF7124F57 for <tram@ietf.org>; Fri,  9 Mar 2018 13:20:01 -0800 (PST)
Received: from pps.filterd (m0122330.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w29LHceK005938; Fri, 9 Mar 2018 21:20:00 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=subject : to : references : from : message-id : date : mime-version : in-reply-to : content-type : content-transfer-encoding; s=jan2016.eng; bh=uOXBO9w2TJSwu5oUzuHsmfLXDd4wgZjhLEyAr4NARdc=; b=IH7eCQ15VWSljvNio/+SdEwjs7j8zo1hpMl946o8Feo8JmBv9RJ1lwZDHpMcQZEPcvTG DTwyJsXGH73icZOz6m77x5b/Tn9KfomBvlxezrzCkdOpLaUahGjKpcm3//YLXNpgpKSH BpZ0XUfm7jBQ4Fp3xd95ihvh//pQ/k2+1J2SVNnWbBTuyM0tJ6MaG6ZmPLp7hdMbQPNT 2FjnMYy5mGes8Lo9ycY01yjqAHgWVKiTRjx9GQS4sHmLDGQgua9WgyYX8W0pw3/zLdHJ YMQpk/wF6pgyogkj8w0iSW5ujjJRzVQYRJTKUybCp2ZA39bbikWsHOp89BAGtlr3TpzK lQ== 
Received: from prod-mail-ppoint3 ([96.6.114.86]) by mx0b-00190b01.pphosted.com with ESMTP id 2gkvnbgsd9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 09 Mar 2018 21:19:59 +0000
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w29LFoqO005371; Fri, 9 Mar 2018 16:19:59 -0500
Received: from prod-mail-relay15.akamai.com ([172.27.17.40]) by prod-mail-ppoint3.akamai.com with ESMTP id 2gfqx1hhdp-1; Fri, 09 Mar 2018 16:19:58 -0500
Received: from [172.28.118.62] (bowill.kendall.corp.akamai.com [172.28.118.62]) by prod-mail-relay15.akamai.com (Postfix) with ESMTP id 9FD6120090; Fri,  9 Mar 2018 21:19:58 +0000 (GMT)
To: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>, Marc Petit-Huguenin <petithug@acm.org>, "tram@ietf.org" <tram@ietf.org>
References: <65c75449-152c-1ce7-7c81-460ca589d9f0@acm.org> <DM5PR16MB17881ABD54B89E14F0291C56EA4C0@DM5PR16MB1788.namprd16.prod.outlook.com> <ea84bcf9-19b6-5492-383b-18e2bc5a93bf@acm.org> <DM5PR16MB178859E2018148DBAD51635EEAF20@DM5PR16MB1788.namprd16.prod.outlook.com> <46fdf931-eb0c-c4fe-9c01-4a066134abfb@acm.org> <BN6PR16MB142530705DF3F28C07FAC9A2EADB0@BN6PR16MB1425.namprd16.prod.outlook.com>
From: Brandon Williams <brandon.williams@akamai.com>
Message-ID: <5942ccf6-aae5-667e-de4d-e54dd7ffa138@akamai.com>
Date: Fri, 9 Mar 2018 16:19:55 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <BN6PR16MB142530705DF3F28C07FAC9A2EADB0@BN6PR16MB1425.namprd16.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-09_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803090252
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-09_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803090252
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/fHcca0G9lr5RuBu7usxFBeclBRQ>
Subject: Re: [tram] Review of dual allocation in TURNbis-11
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2018 21:20:04 -0000

Hi Marc,

Tiru had one response and one question below. Any thoughts?

--Brandon

On 03/04/2018 08:30 AM, Konda, Tirumaleswar Reddy wrote:
> Hi Marc,
> 
> Please see inline
> 
>> -----Original Message-----
>> From: Marc Petit-Huguenin [mailto:petithug@acm.org]
>> Sent: Saturday, March 3, 2018 2:47 AM
>> To: Konda, Tirumaleswar Reddy
>> <TirumaleswarReddy_Konda@McAfee.com>; tram@ietf.org
>> Subject: Re: [tram] Review of dual allocation in TURNbis-11
>>
>> As suggested by Brandon, I reviewed turnbis-14 for the modifications agreed
>> on below, and found some discrepancies.  See inline.
>>
>> On 02/09/2018 04:51 AM, Konda, Tirumaleswar Reddy wrote:
>>>> -----Original Message-----
>>>> From: Marc Petit-Huguenin [mailto:petithug@acm.org]
>>>> Sent: Sunday, October 22, 2017 9:38 PM
>>>> To: Konda, Tirumaleswar Reddy
>>>> <TirumaleswarReddy_Konda@McAfee.com>; tram@ietf.org
>>>> Subject: Re: [tram] Review of dual allocation in TURNbis-11
>>>>
>>>> Inline.
>>>>
>>>> On 10/16/2017 07:14 PM, Konda, Tirumaleswar Reddy wrote:
>>>>> Thanks Marc for the detailed review, Please see inline
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Marc Petit-
>>>>>> Huguenin
>>>>>> Sent: Saturday, October 14, 2017 12:59 AM
>>>>>> To: tram@ietf.org
>>>>>> Subject: [tram] Review of dual allocation in TURNbis-11
>>>>>>
>>
>> [snip]
>>
>>>>>
>>>>>>
>>>>>> - Section 6.2
>>>>>>
>>>>>> I would suggest to make ADDRESS-ERROR-CODE more generic by
>>>> renaming
>>>>>> it as WARNING-CODE and use the same format than for ERROR-CODE.
>>>> Then
>>>>>> allocate a new error code for that specific warning.  I would
>>>>>> suggest to request the 0x8009 codepoint for that attribute.
>>>>>
>>>>> I don't understand the need to change ADDRESS-ERROR-CODE !
>>>>
>>>> To make it more generic and reusable in future specifications.
>>>
>>> ADDRESS-ERROR-CODE cannot use the same format as ERROR-CODE,
>> ADDRESS-ERROR-CODE signals the IP address family for which the warning is
>> generated + all the fields in the ERROR-CODE.
>>>
>>>>
>>>>>
>>>>>>
>>>>>> Also I think we needs two different warnings, one that states that
>>>>>> dual allocation is not available in a TURNbis server, but both
>>>>>> protocols are available, and another that says that dual allocation
>>>>>> failed because one of the two protocols is not available.  This is
>>>>>> to let the client know that it is useless to try another allocation
>>>>>> for the
>>>> missing protocol.
>>>>>
>>>>> I don't get the reason for two different warnings.
>>>>
>>>> A server may support both IPv6 and IPv4 allocations and not support
>>>> dual allocation, in which case the client can do a second allocation
>>>> for the IPv6 relayed address.
>>>
>>> If the server does not support dual allocation but supports both IPv6 and
>> IPv4 allocations, it will only allocate the IPv4 relayed address and not will not
>> return ADDRESS-ERROR-CODE in the response, the client will know the
>> server does not understand the ADDITIONAL-ADDRESS-FAMILY attribute
>> (ADDITIONAL-ADDRESS-FAMILY is a comprehension-optional attribute).
>>>
>>>>
>>>> Alternatively the server may not support IPv6 at all, in which case
>>>> the second allocation will fail and was unnecessary.
>>>
>>> ADDRESS-ERROR-CODE signals both unsupported IP address type (0x02
>> (IPv6 address family)) and the reason for failure (440 (unsupported address
>> family)).
>>>
>>> Cheers,
>>> -Tiru
>>>
>>>>
>>>> Using two different warnings permits to know if the second allocation
>>>> will succeed or not.
>>>>
>>>>>
>>>>>>
>>>>>> What is the policy when reserving the next port with the EVEN-PORT
>>>>>> attribute in a dual allocation, but one of them fails to find a
>>>>>> pair of subsequent ports available?
>>>>>
>>>>> It's discussed in section 6.1
>>>>>
>>>>> <snip>
>>>>>     Clients MUST NOT
>>>>>     include ADDITIONAL-ADDRESS-FAMILY attribute in a Allocate request
>>>>>     that contains an EVEN-PORT attribute with the R bit set to 1.
>>>>> </snip>
>>>>>
>>>>>>
>>>>>> It is not said that the Allocate successful response must contain
>>>>>> two XRAs after a successful dual allocation.
>>>>>
>>>>> Good point, Updated draft.
>>
>> I cannot find this update in turn-14.
> 
> This comment is partially addressed in -12 revision, step 9 (in Section 6.2 in -12 revision and Section 7.2 in -14 revision) is updated to discuss dual allocation.
> <snip>
> If the server can fully meet
> the request, then the server allocates one IPv4 and one IPv6
> relay address, and returns an Allocate success response
> containing the relayed transport addresses assigned to the dual
> allocation.
> </snip>
> 
> NEW:
> If the server can fully meet
> the request, then the server allocates one IPv4 and one IPv6
> relay address, and returns an Allocate success response
> containing the relayed transport addresses assigned to the dual
> allocation in two XOR-RELAYED-ADDRESS attributes.
> 
>>
>>>>>
>>>>>>
>>>>>> I would also suggest to add some text that says that when a TURNbis
>>>>>> server sends an Allocate success response, it must always send the
>>>>>> XRAs in the same order than the RAFs were sent.  So in case the
>>>>>> server sends back by mistake two XRAs, the first one matches the
>>>>>> one
>>>> requested by the client.
>>
>> Did not get answer to that and did not see it in turn-14.
> 
> I did not get this comment. If a request contains both REQUESTED-ADDRESS-FAMILY and ADDITIONAL-ADDRESS-FAMILY attributes, the request is rejected by the server. Further, only IPv6 address family is allowed in the
> ADDITIONAL-ADDRESS-FAMILY attribute.
> 
> 
>>
>>>>>>
>>>>>> The bullet list at the end needs also to be fixed for dual allocation.
>>>>>
>>>>> Agreed, fixed.
>>>>>
>>>>>>
>>>>>> - Section 6.3
>>>>>>
>>>>>> Here's too, the text needs to be updated for the dual allocation case.
>>>>>
>>>>>
>>>>> Yup, updated.
>>>>>
>>
>> Same, there is no update since -11 in section 7.3 (formerly 6.3)
> 
> This comment is addressed in -12 revision itself, the updated text uses "relayed transport address or addresses" and " address family or families" to discuss the
> dual allocation case.
> 
> Cheers,
> -Tiru
> 
>>
>> --
>> Marc Petit-Huguenin
>> Email: marc@petit-huguenin.org
>> Blog: https://marc.petit-huguenin.org
>> Profile: https://www.linkedin.com/in/petithug
> 
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram
> 

-- 
Brandon Williams; Chief Architect
Cloud Networking; Akamai Technologies Inc.


From nobody Fri Mar  9 13:21:42 2018
Return-Path: <brandon.williams@akamai.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 593E6124F57 for <tram@ietfa.amsl.com>; Fri,  9 Mar 2018 13:21:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PvoaJEdUDOuE for <tram@ietfa.amsl.com>; Fri,  9 Mar 2018 13:21:37 -0800 (PST)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 785E31270FC for <tram@ietf.org>; Fri,  9 Mar 2018 13:21:37 -0800 (PST)
Received: from pps.filterd (m0122332.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w29LHS3r015834; Fri, 9 Mar 2018 21:21:36 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=subject : to : references : from : message-id : date : mime-version : in-reply-to : content-type : content-transfer-encoding; s=jan2016.eng; bh=91WfFK3PgFcmg7j+Nyuq3hxxnO3WcsOeWJPT2vj9brc=; b=gJEbngj1hy1hVGxzzUEizO9k2cqG8pPO+HRlbl7LUGPSPLCKaJsfZyOFEZzEI1+axbn6 M1BvO/2vFsPnynzlr6ED7KBGiliZ79B5KQiZwedgyQ8ur49mTas6iUY+XTnQILH5y0wI LvVmB9qbvi4HyNK/x2NdPHrzInGW5fQSrQ4W9lv67w/Mo0ms0v/BMVVfDhS7iiDWX5xK yq8EoI/QegNqRooVupUGrf1E8jQy7cBQDzqlchJkI7smuKy/27ki1QMlb0jGauYo116C ggzwTY5P6mdl1/l56CeLX04RU8dzRjKTSannQ5vrXZ9iFGhbJrI3bEljjAIVdA+EKXgk IA== 
Received: from prod-mail-ppoint3 ([96.6.114.86]) by mx0a-00190b01.pphosted.com with ESMTP id 2gj42mtjqj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 09 Mar 2018 21:21:36 +0000
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w29LL2OR008927; Fri, 9 Mar 2018 16:21:35 -0500
Received: from prod-mail-relay15.akamai.com ([172.27.17.40]) by prod-mail-ppoint3.akamai.com with ESMTP id 2gfqx1hhgn-1; Fri, 09 Mar 2018 16:21:35 -0500
Received: from [172.28.118.62] (bowill.kendall.corp.akamai.com [172.28.118.62]) by prod-mail-relay15.akamai.com (Postfix) with ESMTP id D8E7D20067; Fri,  9 Mar 2018 21:21:34 +0000 (GMT)
To: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>, Marc Petit-Huguenin <petithug@acm.org>, "tram@ietf.org" <tram@ietf.org>
References: <325ddd79-ef98-c8ce-de50-1ef3878cd433@acm.org> <DM5PR16MB17882606F7602CEE66009903EAF20@DM5PR16MB1788.namprd16.prod.outlook.com> <c7716d08-f265-9ce9-ed2a-513ea0ddade6@acm.org> <DM5PR16MB1788777DA4671DD256BBE230EAF20@DM5PR16MB1788.namprd16.prod.outlook.com> <d496aa92-6c68-53f4-efca-34ac2880cfbc@acm.org> <BN6PR16MB14253E401210DF0235668335EADB0@BN6PR16MB1425.namprd16.prod.outlook.com>
From: Brandon Williams <brandon.williams@akamai.com>
Message-ID: <90a0b73d-b441-5275-147f-a1449ed46989@akamai.com>
Date: Fri, 9 Mar 2018 16:21:31 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <BN6PR16MB14253E401210DF0235668335EADB0@BN6PR16MB1425.namprd16.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-09_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803090253
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-09_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803090252
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/1eo_08yjv6AA9LWBOdp58hKwYWg>
Subject: Re: [tram] Review of TURNbis-11
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2018 21:21:39 -0000

Hi Marc,

Does the fix look OK to you now?

Thanks,
--Brandon

On 03/04/2018 07:50 AM, Konda, Tirumaleswar Reddy wrote:
> Thanks Marc, fixed the discrepancy.
> 
> -Tiru
> 
>> -----Original Message-----
>> From: Marc Petit-Huguenin [mailto:petithug@acm.org]
>> Sent: Saturday, March 3, 2018 3:04 AM
>> To: Konda, Tirumaleswar Reddy
>> <TirumaleswarReddy_Konda@McAfee.com>; tram@ietf.org
>> Subject: Re: [tram] Review of TURNbis-11
>>
>> As suggested by Brandon, I reviewed turnbis-14 for the modifications agreed
>> on below, and found one discrepancy.  See inline.
>>
>> On 02/09/2018 05:45 AM, Konda, Tirumaleswar Reddy wrote:
>>>> -----Original Message-----
>>>> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Marc Petit-
>>>> Huguenin
>>>> Sent: Friday, February 9, 2018 6:54 PM
>>>> To: Konda, Tirumaleswar Reddy
>>>> <TirumaleswarReddy_Konda@McAfee.com>; tram@ietf.org
>>>> Subject: Re: [tram] Review of TURNbis-11
>>>>
>>>> Hi,
>>>>
>>>> My responses inline.
>>>>
>>>> On 02/09/2018 03:53 AM, Konda, Tirumaleswar Reddy wrote:
>>>>> Hi Marc,
>>>>>
>>>>> Please see inline
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Marc Petit-
>>>>>> Huguenin
>>>>>> Sent: Sunday, October 22, 2017 10:16 PM
>>>>>> To: tram@ietf.org
>>>>>> Subject: [tram] Review of TURNbis-11
>>>>>>
>>>>>> This is the second part of my review of TURNbis-11, i.e. everything
>>>>>> but the dual allocation part.
>>>>>>
>>>>>> - Section 2.1, last paragraph:
>>>>>>
>>>>>> May be a reference to RFC 5764 and RFC 7983 can be useful here.
>>>>>> Same in section 4, second paragraph and following.  Same at the
>>>>>> beginning of section 11.  Again in section 11.6 (if multiplexed,
>>>>>> the message in the reserved range is not necessarily discarded).
>>>>>
>>>>> Even if the same host transport address is used for other protocols,
>>>> incoming packets to the TURN channel can be identified by just
>>>> examining the source address of the packet.
>>>>> May be I am missing something, I did not get a problem ?
>>>>
>>>> It was just an attempt to make TURN implementers aware of the demux
>>>> issues.
>>>
>>> Got it, added the following line:
>>> The algorithm of demultiplexing packets received from multiple
>>> protocols is discussed in [RFC7983].
>>>
>>>>
>>>>>
>>>>>>
>>>>>> - Section 2.2, first paragraph:
>>>>>>
>>>>>> I think that an informative reference to RFC 7635 may be useful
>>>>>> there, as alternative to the STUN authentication mechanism.
>>>>>
>>>>> Yes, updated.
>>>>>
>>>>>>
>>>>>> - Section 2.9:
>>>>>>
>>>>>> The whole 2.9 section and subsections looks normative and so should
>>>>>> be moved after section 3, perhaps on their own top level section.
>>>>>
>>>>> Done.
>>>>>
>>>>>>
>>>>>> - Section 4, 4th paragraph:
>>>>>>
>>>>>> I would replace "For each allocation..." by "For each Allocate
>>>>>> request...", because of the dual allocation feature.
>>>>>
>>>>> Fixed.
>>>>>
>>>>>>
>>>>>> - Section 4, 12th paragraph:
>>>>>>
>>>>>> Should make clear clear that UDP covers also DTLS.
>>>>>
>>>>> Yes, updated.
>>
>> I cannot find this update in turn-14.
>>
>>>>>
>>>>>>
>>>>>> - Section 6.1, 2nd paragraph:
>>>>>>
>>>>>> If the port is multiplexed with other protocols (RTP, WebRtc,
>>>>>> etc..) then it has to reuse an existing socket.  The document should
>> explain this.
>>>>>
>>>>> It's already covered in Section 2.1 (last paragraph).
>>>>>
>>>>>>
>>>>>> - Section 6.2, 3th paragraph:
>>>>>>
>>>>>> Is it time to recommend DTLS instead of UDP?  In that case we need
>>>>>> to make DTLS mandatory in section 4 paragraph 11 (and I support
>>>>>> that
>>>> change).
>>>>>
>>>>> No, DTLS has both advantages (e.g. dictionary attack)  and
>>>>> disadvantages
>>>> (e.g. double encryption of application data).
>>>>
>>>> OK.
>>>>
>>>>>
>>>>>>
>>>>>> - Section 6.4, second bullet:
>>>>>>
>>>>>> Replace "...SRV procedures)." with "...DNS resolution procedures)."
>>>>>
>>>>> Any specific reason for the replacement ?
>>>>
>>>> This is to not exclude NPATR procedures (RFC 5928).
>>>
>>> Updated second bullet.
>>>
>>> Cheers,
>>> -Tiru
>>>
>>>>
>>>>>
>>>>>>
>>>>>> - Sections 14, 15 and 16:
>>>>>>
>>>>>> These are no longer new methods and attributes.  See also the next
>>>>>> comment.
>>>>>
>>>>> Fixed.
>>>>>
>>>>>>
>>>>>> - Section 19:
>>>>>>
>>>>>> Here you need to update the existing methods, attributes and error
>>>>>> code so the IANA registries point to the RFC-to-be, then you
>>>>>> request allocation for the new attributes.  See section 17 of
>>>>>> STUNbis on a way to do that (that was done following a discussion
>>>>>> with the IANA
>>>> representative at an IETF meeting).
>>>>>
>>>>> Thanks, updated draft.
>>>>>
>>>>>>
>>>>>> Note that ICMP should be comprehension-mandatory, not optional, as
>>>> we
>>>>>> do not want an old client to reject a Data indication with an ICMP
>> attribute.
>>>>>
>>>>> If the indication contains unknown comprehension-required
>>>>> attributes, the
>>>> behavior is the indication is discarded and processing ceases.
>>>>>
>>>>>>
>>>>>> Also, I do not know what this SendErr method is.
>>>>>
>>>>> Removed SendErr (stale entry from a previous version of the draft).
>>>>>
>>>>>>
>>>>>>
>>>>>> Nits
>>>>>> ----
>>>>>>
>>>>>> Section 1:
>>>>>>
>>>>>> s/connection to the Internet ./connection to the Internet./
>>>>>>
>>>>>> Section 2.4, first paragraph:
>>>>>>
>>>>>> The text switches between the words "mechanisms" and "way".
>> Choose
>>>>>> one.
>>>>>>
>>>>>> Section 6.2, item 8:
>>>>>>
>>>>>> s/ADDITIONAL- ADDRESS-FAMILY/ADDITIONAL-ADDRESS-FAMILY/
>>>>>>
>>>>>> Section 12.1, "Preferred Behavior"
>>>>>>
>>>>>> s/Label Field[RFC3697]/Label Field [RFC3697]/
>>>>>>
>>>>>> Section 21:
>>>>>>
>>>>>> s/ADDRESS-ERRR-CODE/ADDRESS-ERR-CODE/
>>>>>>
>>>>>> Section 22:
>>>>>>
>>>>>> s/orginal/original/
>>>>>
>>>>> Thanks, fixed all above nits.
>>>>>
>>
>> --
>> Marc Petit-Huguenin
>> Email: marc@petit-huguenin.org
>> Blog: https://marc.petit-huguenin.org
>> Profile: https://www.linkedin.com/in/petithug
> 
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram
> 


From nobody Fri Mar  9 13:50:21 2018
Return-Path: <linuxwolf+ietf@outer-planes.net>
X-Original-To: tram@ietf.org
Delivered-To: tram@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 06BB01242F7; Fri,  9 Mar 2018 13:50:10 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Matthew Miller <linuxwolf+ietf@outer-planes.net>
To: <secdir@ietf.org>
Cc: draft-ietf-tram-stunbis.all@ietf.org, ietf@ietf.org, tram@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.74.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152063220998.11155.12669577501214588133@ietfa.amsl.com>
Date: Fri, 09 Mar 2018 13:50:10 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/0qyDBLBc-hFkKzB0XqbmOt33d18>
Subject: [tram] Secdir last call review of draft-ietf-tram-stunbis-16
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2018 21:50:10 -0000

Reviewer: Matthew Miller
Review result: Has Issues

[ I realize how unfortunate it is this arrives well past last call.
I beg forgiveness and ask that you accept the comments as you would
have if they arrived on time. ]

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should
treat these comments just like any other last call comments.

Document: draft-ietf-stunbis-16
Reviewer: Matthew A. Miller
Review Date: 2018-03-07
IETF LC End Date: 2018-02-20
IESG Telechat date: 2018-04-05

Summary:  This document obsoletes 5389, adding some protection to
downgrade attacks against message integrity usage, as well
incorporating DTLS (over UDP).

The document is mostly ready, but there are a couple of issues I
have.

Major Issues: N/A

Minor Issues:

* I am wondering why a more robust password algorithm (key derivation
function) was not defined (e.g., HKDF-SHA-256) instead of or in addition
to, a simple salted "SHA-256" hash.  Some amount of parameterization is
accounted for in the PASSWORD-ALGORITHM/S attributes.  I think it is
perfectly fair and appropriate to take this issue as "asking for a quick
rationale (that maybe ought to be highlighted better in the document)"
over "use a real key derivation function".

* The description for 17.5.1. "MD5" list the key size as 20 bytes, but the
hash length of MD5 is 16 bytes (128 bits).  I think this is merely a typo,
since the purpose appears to be for backwards compatibility with existing
systems.

* Both 17.5.1.1. "MD5" Section 9.2.2. "HMAC Key" (long-term credential)
and Section appear to define the same functional algorithm, but with subtle
syntax differences.  As far as I can tell, they are actually the same
algorithm; would it not be acceptable to have Section 9.2.2 point to
Section 17.5.1.1 for the algorithm description?



From nobody Sun Mar 11 05:35:18 2018
Return-Path: <petithug@acm.org>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A762120724 for <tram@ietfa.amsl.com>; Sun, 11 Mar 2018 05:35:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.442
X-Spam-Level: 
X-Spam-Status: No, score=-0.442 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G9TQwpGNgEsB for <tram@ietfa.amsl.com>; Sun, 11 Mar 2018 05:35:15 -0700 (PDT)
Received: from implementers.org (unknown [92.243.22.217]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F11C71201FA for <tram@ietf.org>; Sun, 11 Mar 2018 05:35:14 -0700 (PDT)
Received: from [IPv6:2601:648:8301:730f:ac0b:c7cc:59a:561f] (unknown [IPv6:2601:648:8301:730f:ac0b:c7cc:59a:561f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 0082EAE8D9; Sun, 11 Mar 2018 13:35:11 +0100 (CET)
To: "Asveren, Tolga" <tasveren@rbbn.com>, "Gonzalo Salgueiro (gsalguei@cisco.com)" <gsalguei@cisco.com>, "tram@ietf.org" <tram@ietf.org>
References: <CY4PR03MB316039CC07807621C64AFE39A5C90@CY4PR03MB3160.namprd03.prod.outlook.com> <10ce3dde-2401-dc4f-e231-13678f6494d1@acm.org> <CY4PR03MB3160D0E46134CF10AE7CBAF4A5DB0@CY4PR03MB3160.namprd03.prod.outlook.com>
From: Marc Petit-Huguenin <petithug@acm.org>
Message-ID: <a7726725-5c60-c284-9249-29e67b6a8d7f@acm.org>
Date: Sun, 11 Mar 2018 05:35:08 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CY4PR03MB3160D0E46134CF10AE7CBAF4A5DB0@CY4PR03MB3160.namprd03.prod.outlook.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="2Va8gN6hXiGxrkdeSGbpp4mgR92NYfJ16"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/35DuDk51LXMH0eu6k5PILE82q5c>
Subject: Re: [tram] draft-ietf-tram-stun-pmtud-06 review
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Mar 2018 12:35:17 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--2Va8gN6hXiGxrkdeSGbpp4mgR92NYfJ16
Content-Type: multipart/mixed; boundary="v5iUlbJ4PEeejWKwgRvWeCvMZ0ONgGhjN";
 protected-headers="v1"
From: Marc Petit-Huguenin <petithug@acm.org>
To: "Asveren, Tolga" <tasveren@rbbn.com>,
 "Gonzalo Salgueiro (gsalguei@cisco.com)" <gsalguei@cisco.com>,
 "tram@ietf.org" <tram@ietf.org>
Message-ID: <a7726725-5c60-c284-9249-29e67b6a8d7f@acm.org>
Subject: Re: [tram] draft-ietf-tram-stun-pmtud-06 review
References: <CY4PR03MB316039CC07807621C64AFE39A5C90@CY4PR03MB3160.namprd03.prod.outlook.com>
 <10ce3dde-2401-dc4f-e231-13678f6494d1@acm.org>
 <CY4PR03MB3160D0E46134CF10AE7CBAF4A5DB0@CY4PR03MB3160.namprd03.prod.outlook.com>
In-Reply-To: <CY4PR03MB3160D0E46134CF10AE7CBAF4A5DB0@CY4PR03MB3160.namprd03.prod.outlook.com>

--v5iUlbJ4PEeejWKwgRvWeCvMZ0ONgGhjN
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

See inline.

On 03/04/2018 07:03 AM, Asveren, Tolga wrote:
> Hi Marc,
>=20
> Please see inline for comments/answers/questions.
>=20
> Thanks,
> Tolga
>=20
> -----Original Message-----
> From: Marc Petit-Huguenin <petithug@acm.org>=20
> Sent: Saturday, March 3, 2018 10:42 AM
> To: Asveren, Tolga <tasveren@rbbn.com>; Gonzalo Salgueiro (gsalguei@cis=
co.com) <gsalguei@cisco.com>; tram@ietf.org
> Subject: Re: [tram] draft-ietf-tram-stun-pmtud-06 review
>=20
> Thanks for the review, please see inline.
>=20
> As the cutoff is Monday afternoon, I'll publish -07 just after sending =
this email.
>=20
> On 02/17/2018 09:40 PM, Asveren, Tolga wrote:
>> Marc, Gonzalo,
>>
>> Some comments/questions for draft-ietf-tram-stun-pmtud-06:
>>
>> i- 4.
>>
>>   Implementations supporting this specification MUST implement the
>>    server side of both the Simple Probing mechanism (Section 4.1) and
>>    the Complete Probing mechanism (Section 4.2).
>>    Implementations supporting this specification MUST implement the
>>    client side of the Complete Probing mechanism.  They MAY implement
>>    the client side of the Simple Probing mechanism.
>>
>> I don't see the rationale behind mandating this behavior. Such semanti=
cs in general are taken care of in the context of a capability negotiatio=
n mechanism, which this document does not specify. As it stands right now=
, I think this is best left to local policy and bilateral agreements and =
I would suggest not to use anything stronger than "RECOMMEND".
>=20
> It took me some time to remember why that was the case.  IIRC, one of t=
he reasons of doing this is because of the implicit probe support in sect=
ion 5.2.  Because there is no explicit signaling there, we need the serve=
r side (which was previously the client side) to be ready to respond to b=
oth Simple and Complete Probing.  Hence the "server must do both, client =
choose what they want to do" rule.
>=20
> The other reason is that if we let implementers choose, then Complete P=
robing - which is the correct way of doing probing - will never be used.
> [TOLGA] If client does not get replies for a mechanism it SHOULD try th=
e other one. Honestly I don=E2=80=99t see a compelling reason to mandate =
anything on the server side. There is no negotiation mechanism and that c=
an=E2=80=99t be enforced on protocol level anyhow. I suggest to use RECOM=
MNED for server and add a sentence for client behavior that it SHOULD try=
 the other mechanism if one does not get any replies at all.

No, not making the Complete Probing mandatory in the server removes the c=
ompliance with RFC 4821, which is the whole point of this document.  If p=
eople do not want compliance with RFC 4821, they just have to not impleme=
nt that RFC-to-be.

After Complete Probing is implemented on the server side, it's easy to ad=
d Simple Probing, so making it mandatory too does not add much burden on =
the implementer.

But if you insist of making the server support as RECOMMEND, then I'll sp=
lit the RFC-to-be in two RFCs, one for Complete Probing and compliance wi=
th RFC 4821, and the other for Simple Probing.

>=20
>>
>> ii- 4.1
>> DF bit set over UDP.
>> =3D=3D>
>> DF bit in IP Header.
>> Right?  (the same in 4.2)
>=20
> Not really, the Probe Request is still sent over UDP, so I changed the =
text to that (twice):
>=20
>  The Simple Probing mechanism is implemented by sending a Probe  Reques=
t with a PADDING [RFC5780] attribute over UDP with the DF bit  set in the=
 IP header.  A router on the path to the server can reject  this request =
with an ICMP message or drop it.
>=20
>  The Complete Probing mechanism is implemented by sending one or more  =
Probe Indications with a PADDING attribute over UDP with the DF bit  set =
in the IP header followed by a Report Request to the same server.
> [TOLGA] Looks good, I just wanted to make sure about the "DF bit in IP =
header" part.
>=20
>>
>> iii- 4.1.1
>> A client MUST NOT send a probe if it does not have knowledge that the
>>    server supports this specification.  This is done either by externa=
l
>>    signalling or by a mechanism specific to the UDP protocol to which
>>    PMTUD capabilities are added or by one of the mechanisms specified =
in
>>    Section 5.
>> I suggest adding text for possible use of local policy/bilateral agree=
ments for this purpose.
>=20
> I am not sure what to add to what is said.  Do you have text to suggest=
?
> [TOLGA] Maybe by just adding something like:
> "Information about client/server support for this specification, for ex=
ample, could be based on local policy and bilateral agreements among rele=
vant organizations."

See above.

>=20
>>
>> iv-  4.2
>> Some protocols may already have a way of identifying each individual
>>    UDP packet, in which case these identifiers SHOULD be used in the
>>    IDENTIFIERS attribute of the Report Response.
>> What is meant here as "some protocols"? Are you referring  to what is =
carried as payload of UDP or what is used below UDP?
>=20
> The former.  I changed the text to "application layer protocols:"
> [TOLGA] Thanks.
>=20
>>
>> v- 4.2
>> In the first packet identification mechanism, the server computes a
>>    checksum over each packet received and sends back to the sender the=

>>    list of checksums ordered chronologically.  The client compares thi=
s
>>    list to its own list of checksums.
>> What if there are two probes with the same checksum right after each o=
ther and one of them is lost? How can client disambiguate such a case in =
 the response?
>=20
> I am not sure to get the problem here.  The sender keeps a chronologica=
lly ordered list of the checksums of the sent packets (data and probes), =
so in that case there is a sequence of two identical checksums in that li=
st.  The server sends back a list of checksums, but with only one of that=
 value (or even 0).  The loss can be detected.
> [TOLGA] Loss can be detected but which one is lost?
>=20
> Probe-n  (checksum-A)
> Probe-n+1 (checksum-A)
>=20
> Only a single reply for (checksum-A) is received.

Replies are only for the Simple Probing mechanism, a mechanism that does =
not need to identify UDP packets.

>=20
> Is Probe-n or Probe-n+1 lost?

If the same probe is sent multiple times but some are dropped then we kno=
w that, we just do not know exactly which one.

The whole point of this is to separate the packets drops because of a net=
work condition (which should not affect the PMTU) from the the packets dr=
ops because of an oversized packet, which does not require to know exactl=
y which packet was dropped, as they are all dropped.  Note that two probe=
s with different lengths will have different checksum, so we can isolate =
exactly what probe was rejected and why.

That said, RFC 4821 leaves the client free to implement whatever algorith=
m it want, so there may be some future algorithm that could use the knowl=
edge of exactly which packet was dropped.  IN that case the future RFC th=
at will describe how to recognize the UDP packets for a specific protocol=
 will just have to choose a method that permits to differentiate individu=
al packets in the Report response.

>=20
>>
>> v- 7
>> The Simple Probing mechanism may be used without authentication
>>    because this usage by itself cannot trigger an amplification attack=

>>    because the Probe Response is smaller than the Probe Request.
>> Isn't the same true for Sum(Probe Requests) > (Report Response)?
>=20
> I think that mechanism was set following a review that was worried abou=
t amplification attack.  We have the simple probe mechanism without authe=
ntication to keep the barrier to entry very low, i.e. the minimum require=
d implementation possible.
>=20
> Security expert can chime in.
> [TOLGA] I think that would be good. Who would be that?
>=20
>>
>> vii- nit
>> =3D=3D The copyright year in the IETF Trust and authors Copyright Line=
 does not
>>      match the current year
>>
>>   -- The document date (September 1, 2017) is 169 days in the past.  I=
s this
>>      intentional?
>=20
> Will be upgraded with the next publication.
> [TOLGA] Thanks.
>=20

--=20
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: https://marc.petit-huguenin.org
Profile: https://www.linkedin.com/in/petithug


--v5iUlbJ4PEeejWKwgRvWeCvMZ0ONgGhjN--

--2Va8gN6hXiGxrkdeSGbpp4mgR92NYfJ16
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEBSI+IuCHU8MsI1GjKcRFldZqfsQFAlqlIn0ACgkQKcRFldZq
fsStZg//Yk1ZRLi0YttzoT2CDRhhB5xo5CrogntphV3nv4YEdrZ0a5qAe/lU/mGL
huq5kajYSgJkYzOrFLcRP5AulY00HpNlKozh/r2RxVBzY7Pj8+tD8LNefgmPi6VJ
2D0ulRhVB+k5PFqv8//6vfavYcEkl4GIjU8mHf9S7UMcJXydg104oH9x5atDxORZ
pyEDotYZTf5ifG+tesiizdSJFd4Cjq3zye5+wiCPEXv6mV52lM4NHKCJsimVbcWI
zEP0E6vAOMx3APPcyVS9PK80df1ETTFVeDK0gGkT9Ebb/AybYX21BIKb1wkgKDTH
deMcK/hk6EMAJdGWHbRkufnDht0jNM5E9bltmpflzKwOsr+bgf5R3DRxFgUzjhDF
9vIANKbL3Dj7DmjAKMb2xvAZLtghiEgd/MkG3obQuycJpl/ZLUYgO00b9EZl6ieI
CoWQ/91YXLmDF122GFpFbC/rd/Fytno4YYR9NrNn8+dtyOJ6NdB7gczw85W4KH4q
YZQ47u2/U1GoMwzIWKj06Kyl7hOTGABvsc3mG5JFnZ6RwhQo93znzgVVPduzY86x
rP9+qc59B5PtbB5YnhS6afZ9DQSOuHUJGKb5g+GxbjB4eQ2XjkWa3AG4nPfghfo7
rNUcacKW0uKMQSg/ftF+UHAdIN2vVC8W3PDQtGUCEHCwSCViY+8=
=4Etm
-----END PGP SIGNATURE-----

--2Va8gN6hXiGxrkdeSGbpp4mgR92NYfJ16--


From nobody Sun Mar 11 05:46:03 2018
Return-Path: <petithug@acm.org>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5758212D77C for <tram@ietfa.amsl.com>; Sun, 11 Mar 2018 05:45:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.442
X-Spam-Level: 
X-Spam-Status: No, score=-0.442 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8JfijpPj0uIo for <tram@ietfa.amsl.com>; Sun, 11 Mar 2018 05:45:57 -0700 (PDT)
Received: from implementers.org (unknown [92.243.22.217]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40EC31201FA for <tram@ietf.org>; Sun, 11 Mar 2018 05:45:57 -0700 (PDT)
Received: from [IPv6:2601:648:8301:730f:ac0b:c7cc:59a:561f] (unknown [IPv6:2601:648:8301:730f:ac0b:c7cc:59a:561f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 62879AE8D9; Sun, 11 Mar 2018 13:45:55 +0100 (CET)
To: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>, "tram@ietf.org" <tram@ietf.org>
References: <65c75449-152c-1ce7-7c81-460ca589d9f0@acm.org> <DM5PR16MB17881ABD54B89E14F0291C56EA4C0@DM5PR16MB1788.namprd16.prod.outlook.com> <ea84bcf9-19b6-5492-383b-18e2bc5a93bf@acm.org> <DM5PR16MB178859E2018148DBAD51635EEAF20@DM5PR16MB1788.namprd16.prod.outlook.com> <46fdf931-eb0c-c4fe-9c01-4a066134abfb@acm.org> <BN6PR16MB142530705DF3F28C07FAC9A2EADB0@BN6PR16MB1425.namprd16.prod.outlook.com>
From: Marc Petit-Huguenin <petithug@acm.org>
Message-ID: <6c8962b4-ad44-eeb0-6334-bf496619eaee@acm.org>
Date: Sun, 11 Mar 2018 05:45:53 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <BN6PR16MB142530705DF3F28C07FAC9A2EADB0@BN6PR16MB1425.namprd16.prod.outlook.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="V1JlKIE1CC07zyfJ4FHA5KlOkXmFlQR6v"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/dxXcKFznY4IRsN6nri9dLlQDafs>
Subject: Re: [tram] Review of dual allocation in TURNbis-11
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Mar 2018 12:46:01 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--V1JlKIE1CC07zyfJ4FHA5KlOkXmFlQR6v
Content-Type: multipart/mixed; boundary="XW7xzv6y1O7KTyWsUD3WbWPWvHhdXb3XL";
 protected-headers="v1"
From: Marc Petit-Huguenin <petithug@acm.org>
To: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>,
 "tram@ietf.org" <tram@ietf.org>
Message-ID: <6c8962b4-ad44-eeb0-6334-bf496619eaee@acm.org>
Subject: Re: [tram] Review of dual allocation in TURNbis-11
References: <65c75449-152c-1ce7-7c81-460ca589d9f0@acm.org>
 <DM5PR16MB17881ABD54B89E14F0291C56EA4C0@DM5PR16MB1788.namprd16.prod.outlook.com>
 <ea84bcf9-19b6-5492-383b-18e2bc5a93bf@acm.org>
 <DM5PR16MB178859E2018148DBAD51635EEAF20@DM5PR16MB1788.namprd16.prod.outlook.com>
 <46fdf931-eb0c-c4fe-9c01-4a066134abfb@acm.org>
 <BN6PR16MB142530705DF3F28C07FAC9A2EADB0@BN6PR16MB1425.namprd16.prod.outlook.com>
In-Reply-To: <BN6PR16MB142530705DF3F28C07FAC9A2EADB0@BN6PR16MB1425.namprd16.prod.outlook.com>

--XW7xzv6y1O7KTyWsUD3WbWPWvHhdXb3XL
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Inline.

On 03/04/2018 05:30 AM, Konda, Tirumaleswar Reddy wrote:
> Hi Marc,
>=20
> Please see inline
>=20
>> -----Original Message-----
>> From: Marc Petit-Huguenin [mailto:petithug@acm.org]
>> Sent: Saturday, March 3, 2018 2:47 AM
>> To: Konda, Tirumaleswar Reddy
>> <TirumaleswarReddy_Konda@McAfee.com>; tram@ietf.org
>> Subject: Re: [tram] Review of dual allocation in TURNbis-11
>>
>> As suggested by Brandon, I reviewed turnbis-14 for the modifications a=
greed
>> on below, and found some discrepancies.  See inline.
>>
>> On 02/09/2018 04:51 AM, Konda, Tirumaleswar Reddy wrote:
>>>> -----Original Message-----
>>>> From: Marc Petit-Huguenin [mailto:petithug@acm.org]
>>>> Sent: Sunday, October 22, 2017 9:38 PM
>>>> To: Konda, Tirumaleswar Reddy
>>>> <TirumaleswarReddy_Konda@McAfee.com>; tram@ietf.org
>>>> Subject: Re: [tram] Review of dual allocation in TURNbis-11
>>>>
>>>> Inline.
>>>>
>>>> On 10/16/2017 07:14 PM, Konda, Tirumaleswar Reddy wrote:
>>>>> Thanks Marc for the detailed review, Please see inline
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Marc Petit-=

>>>>>> Huguenin
>>>>>> Sent: Saturday, October 14, 2017 12:59 AM
>>>>>> To: tram@ietf.org
>>>>>> Subject: [tram] Review of dual allocation in TURNbis-11
>>>>>>
>>
>> [snip]
>>
>>>>>
>>>>>>
>>>>>> - Section 6.2
>>>>>>
>>>>>> I would suggest to make ADDRESS-ERROR-CODE more generic by
>>>> renaming
>>>>>> it as WARNING-CODE and use the same format than for ERROR-CODE.
>>>> Then
>>>>>> allocate a new error code for that specific warning.  I would
>>>>>> suggest to request the 0x8009 codepoint for that attribute.
>>>>>
>>>>> I don't understand the need to change ADDRESS-ERROR-CODE !
>>>>
>>>> To make it more generic and reusable in future specifications.
>>>
>>> ADDRESS-ERROR-CODE cannot use the same format as ERROR-CODE,
>> ADDRESS-ERROR-CODE signals the IP address family for which the warning=
 is
>> generated + all the fields in the ERROR-CODE.
>>>
>>>>
>>>>>
>>>>>>
>>>>>> Also I think we needs two different warnings, one that states that=

>>>>>> dual allocation is not available in a TURNbis server, but both
>>>>>> protocols are available, and another that says that dual allocatio=
n
>>>>>> failed because one of the two protocols is not available.  This is=

>>>>>> to let the client know that it is useless to try another allocatio=
n
>>>>>> for the
>>>> missing protocol.
>>>>>
>>>>> I don't get the reason for two different warnings.
>>>>
>>>> A server may support both IPv6 and IPv4 allocations and not support
>>>> dual allocation, in which case the client can do a second allocation=

>>>> for the IPv6 relayed address.
>>>
>>> If the server does not support dual allocation but supports both IPv6=
 and
>> IPv4 allocations, it will only allocate the IPv4 relayed address and n=
ot will not
>> return ADDRESS-ERROR-CODE in the response, the client will know the
>> server does not understand the ADDITIONAL-ADDRESS-FAMILY attribute
>> (ADDITIONAL-ADDRESS-FAMILY is a comprehension-optional attribute).
>>>
>>>>
>>>> Alternatively the server may not support IPv6 at all, in which case
>>>> the second allocation will fail and was unnecessary.
>>>
>>> ADDRESS-ERROR-CODE signals both unsupported IP address type (0x02
>> (IPv6 address family)) and the reason for failure (440 (unsupported ad=
dress
>> family)).
>>>
>>> Cheers,
>>> -Tiru
>>>
>>>>
>>>> Using two different warnings permits to know if the second allocatio=
n
>>>> will succeed or not.
>>>>
>>>>>
>>>>>>
>>>>>> What is the policy when reserving the next port with the EVEN-PORT=

>>>>>> attribute in a dual allocation, but one of them fails to find a
>>>>>> pair of subsequent ports available?
>>>>>
>>>>> It's discussed in section 6.1
>>>>>
>>>>> <snip>
>>>>>    Clients MUST NOT
>>>>>    include ADDITIONAL-ADDRESS-FAMILY attribute in a Allocate reques=
t
>>>>>    that contains an EVEN-PORT attribute with the R bit set to 1.
>>>>> </snip>
>>>>>
>>>>>>
>>>>>> It is not said that the Allocate successful response must contain
>>>>>> two XRAs after a successful dual allocation.
>>>>>
>>>>> Good point, Updated draft.
>>
>> I cannot find this update in turn-14.
>=20
> This comment is partially addressed in -12 revision, step 9 (in Section=
 6.2 in -12 revision and Section 7.2 in -14 revision) is updated to discu=
ss dual allocation.=20
> <snip>
> If the server can fully meet
> the request, then the server allocates one IPv4 and one IPv6
> relay address, and returns an Allocate success response
> containing the relayed transport addresses assigned to the dual
> allocation.
> </snip>
>=20
> NEW:
> If the server can fully meet
> the request, then the server allocates one IPv4 and one IPv6
> relay address, and returns an Allocate success response
> containing the relayed transport addresses assigned to the dual
> allocation in two XOR-RELAYED-ADDRESS attributes.

OK.

>=20
>>
>>>>>
>>>>>>
>>>>>> I would also suggest to add some text that says that when a TURNbi=
s
>>>>>> server sends an Allocate success response, it must always send the=

>>>>>> XRAs in the same order than the RAFs were sent.  So in case the
>>>>>> server sends back by mistake two XRAs, the first one matches the
>>>>>> one
>>>> requested by the client.
>>
>> Did not get answer to that and did not see it in turn-14.
>=20
> I did not get this comment. If a request contains both REQUESTED-ADDRES=
S-FAMILY and ADDITIONAL-ADDRESS-FAMILY attributes, the request is rejecte=
d by the server. Further, only IPv6 address family is allowed in the=20
> ADDITIONAL-ADDRESS-FAMILY attribute.
>=20

No, my request was to ask that in case of dual allocation the address tha=
t is selected following the ADDITIONAL-ADDRESS-FAMILY attribute is insert=
ed after the address selected by the REQUESTED-ADDRESS-FAMILY attribute i=
n the response.

So if the order in the request is:

REQUESTED-ADDRESS-FAMILY for ipv4
ADDITIONAL-ADDRESS-FAMILY for ipv6

then the response contains

XOR-RELAYED-ADDRESS for ipv4
XOR-RELAYED-ADDRESS for ipv6

This is a corner case (if the server misbehave, the client still works), =
so I am OK with this request ignored.

>=20
>>
>>>>>>
>>>>>> The bullet list at the end needs also to be fixed for dual allocat=
ion.
>>>>>
>>>>> Agreed, fixed.
>>>>>
>>>>>>
>>>>>> - Section 6.3
>>>>>>
>>>>>> Here's too, the text needs to be updated for the dual allocation c=
ase.
>>>>>
>>>>>
>>>>> Yup, updated.
>>>>>
>>
>> Same, there is no update since -11 in section 7.3 (formerly 6.3)
>=20
> This comment is addressed in -12 revision itself, the updated text uses=
 "relayed transport address or addresses" and " address family or familie=
s" to discuss the=20
> dual allocation case.
>=20

OK.

--=20
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: https://marc.petit-huguenin.org
Profile: https://www.linkedin.com/in/petithug


--XW7xzv6y1O7KTyWsUD3WbWPWvHhdXb3XL--

--V1JlKIE1CC07zyfJ4FHA5KlOkXmFlQR6v
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEBSI+IuCHU8MsI1GjKcRFldZqfsQFAlqlJQEACgkQKcRFldZq
fsSvNQ//Qi0OuN1Rnaj3TywKbbiW7/fSdQZKdhnDFHP2A0zJBFkoOy3bdrfelSSU
2zP0g78Xsgh0hKO+qNDYHbr/AD5Tc/JN2ZieKodwzjrwMmEhqWyPoLgTcfwu9CcR
GEXGCv0ofWYjrJDx1YGq1lgZo7DEgDmZ/QZTft2lXbJJlmHp9avqU3od75va9br1
DF4/kx9pOMq0niS/SB0fDi93UWQM9I+e8XV7+Cy0I5TDQ/sHZm9LBO1X8znBEgrd
7Sk2gbbxGEBtDQ/UlLgPzOcAdq5pFagJUKwW3fQoe83AKTl34DLhnqkm7cZF8qWi
YC5fJFAASQjKA5Y7XpjJd45DHWlCLpbzf7uELdDWYWzK05/obrWpeZIAiiRRrPmk
gTm9n9svuyK/C+h+fXexzFyjc060kaKqeCSd7awTp7CZi3+PTymM6MT+ajA3HAwj
c+UcxL11CFqYsL0l4dhXQrE9vzjY15fR4yHamFnmjkIErxl9jV3MkwF9Uf1wMJC+
tVKxutNI0+vYFUg0Dc4L0AIP6XtLAXfetqP6nWFDzSnoChmDo2GS3puDgW6M2DIf
qi0p5cdSMsIyNI4eX7QzjvQsEcA4GU6UUi+l5fUlAUyowGSEUz4rRWjdETm3nhRq
CbpsuVT2VdQxNYbGa116cK7LB0aLHrPwxNmRqY0yoRIbu1qBBjQ=
=qZ97
-----END PGP SIGNATURE-----

--V1JlKIE1CC07zyfJ4FHA5KlOkXmFlQR6v--


From nobody Sun Mar 11 06:26:52 2018
Return-Path: <marc@petit-huguenin.org>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EC0B124217; Sun, 11 Mar 2018 06:26:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.108
X-Spam-Level: 
X-Spam-Status: No, score=-1.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FmzwIaQTRuzg; Sun, 11 Mar 2018 06:26:48 -0700 (PDT)
Received: from implementers.org (unknown [IPv6:2001:4b98:dc0:45:216:3eff:fe7f:7abd]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEC0A126D05; Sun, 11 Mar 2018 06:26:47 -0700 (PDT)
Received: from [IPv6:2601:648:8301:730f:ac0b:c7cc:59a:561f] (unknown [IPv6:2601:648:8301:730f:ac0b:c7cc:59a:561f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 55028AE8D9; Sun, 11 Mar 2018 14:26:45 +0100 (CET)
To: Noriyuki Torii <torii0573@gmail.com>, draft-ietf-tram-stunbis@ietf.org
Cc: tram@ietf.org
References: <CABEjbRJjU2LVb0iDkBavpSxtw-+PowvsyDdg9hhvwX+Gi9Awzw@mail.gmail.com>
From: Marc Petit-Huguenin <marc@petit-huguenin.org>
Message-ID: <9b5529b3-5d0d-e6a6-9481-a947a890acc3@petit-huguenin.org>
Date: Sun, 11 Mar 2018 06:26:42 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CABEjbRJjU2LVb0iDkBavpSxtw-+PowvsyDdg9hhvwX+Gi9Awzw@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="V9Ok67EScuVCJXFQcDQH2Phq5672i5Vuv"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/DFlHrJaeZNFArPZRsc_gjhG2FYI>
Subject: Re: [tram] draft-ietf-tram-stunbis
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Mar 2018 13:26:49 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--V9Ok67EScuVCJXFQcDQH2Phq5672i5Vuv
Content-Type: multipart/mixed; boundary="iDQdhRVkLqaXVyAkOlJYrfX8BgL00roaL";
 protected-headers="v1"
From: Marc Petit-Huguenin <marc@petit-huguenin.org>
To: Noriyuki Torii <torii0573@gmail.com>, draft-ietf-tram-stunbis@ietf.org
Cc: tram@ietf.org
Message-ID: <9b5529b3-5d0d-e6a6-9481-a947a890acc3@petit-huguenin.org>
Subject: Re: draft-ietf-tram-stunbis
References: <CABEjbRJjU2LVb0iDkBavpSxtw-+PowvsyDdg9hhvwX+Gi9Awzw@mail.gmail.com>
In-Reply-To: <CABEjbRJjU2LVb0iDkBavpSxtw-+PowvsyDdg9hhvwX+Gi9Awzw@mail.gmail.com>

--iDQdhRVkLqaXVyAkOlJYrfX8BgL00roaL
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Hi,

Thanks for the review, please see inline.

Note that the draft submission tool will reopen on 2018-03-18, so no new =
version of this draft will be published before that.

On 03/07/2018 04:10 AM, Noriyuki Torii wrote:
> To whom it may concern.
>=20
> I'm Noriyuki Torii. I have red the updated I-D of STUNbis-16 and found
> some issues would like to be shared.
>=20
> Hope this may help for improvement.
>=20
> - Section 9.1.1 and 9.2.2 defines the HMAC key calculation based on som=
e
>   elements such that the password, username and realm.
>   Sections say those elements should be proccessed using OpaqueString
> profile
>   defined in RFC8265.
>=20
>   On the other hand, RFC8265 says in its "Changes from RFC 7613" that
>      "Removed UTF-8 as a mandatory encoding, because that is a matter
>       for the application."
>=20
>   So, the specification of applied encoding for those elements on
> calculating
>   HMAC key is up to STUNbis document.
>=20
>   Please note that username and realm have the applied encoding
> specification
>   as UTF-8 in its corresponding STUN attribute description.
>   (please see section 14.3 and 14.9)
>   But the password doesn't have such a description, therefore some care=
 need
>   to be taken.

Section 9.1.1 and 9.2.2 now have the following text:

   For short-term credentials the HMAC key is defined as follow:

                       key =3D OpaqueString(password)

   where the OpaqueString profile is defined in [RFC8265].  The encoding
   used is UTF-8 [RFC3629].

[...]

   For long-term credentials that do not use a different algorithm, as
   specified by the PASSWORD-ALGORITHM attribute, the key is 16 bytes:

  key =3D MD5(username ":" OpaqueString(realm) ":" OpaqueString(password)=
)

   Where MD5 is defined in [RFC1321] and the OpaqueString profile is
   defined in [RFC8265].  The encoding used is UTF-8 [RFC3629].

>=20
> - Section 14.6 mentions to the HMAC truncation, but as far as I read, I=

>   couldn't precisely find out the minimum byte of length of the HMAC.
>=20
>   From my understandings, minimum length
>   maybe 16 because
>   > The HMAC MUST NOT be truncated below a minimum size of 16 bytes.
>=20
>   OR
>   maybe 8 because
>   > The value (snip) MUST be a positive multiple of 4 bytes
>     AND
>   > STUN Usages may specify a minimum length longer than 4 bytes.
>=20
>   Here above I conceived "longer than (but not equal to) 4 bytes".
>   IMHO, some clarification will be preferable.

I removed the last sentence of the paragraph, which did not make sense.

>=20
> - There are some occurence such like
>    > a UTF-8 [RFC3629] encoded
>    > sequence of less than 128 characters (which can be as long as 509
>    > bytes when encoding them or 763 bytes when decoding them).
>=20
>    The sentence inside parenthesis have off-by-one error.
>    To be exact,
>=20
>    (which can be less than 509 bytes when encoding them or 763 bytes
>    when decoding them)
>=20
>    or alternatively
>=20
>    (which can be as long as 508 bytes when encoding them or 762 bytes
>    when decoding them)

I gave you an answer to that last time, but you did not responded to it. =
 Again, here's the email that justify these values:

https://www.ietf.org/mail-archive/web/behave/current/msg02535.html

Please give arguments why that answer is wrong.

>=20
> - In Section 9.2.4, there are some typoes.
>   Unnecessary extra white space such that "PASSWORD- ALGORITHM".

Fixed.

>=20
> - At page 40, bizzare (perhaps unintended) page break occurs.

Fixed.

--=20
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: https://marc.petit-huguenin.org
Profile: https://www.linkedin.com/in/petithug


--iDQdhRVkLqaXVyAkOlJYrfX8BgL00roaL--

--V9Ok67EScuVCJXFQcDQH2Phq5672i5Vuv
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEBSI+IuCHU8MsI1GjKcRFldZqfsQFAlqlLpMACgkQKcRFldZq
fsQveBAA2NYJasQKm+U1vxG9fiD7PMSYBNkxrcIKzbF4/68WHF5H6OHWpJzVfLx0
/mXPfpc6B32ccX89NXMZsGnHyN34q2Qa2ET9HSBlM7wvYYugipwl81ERaHIQJme7
sQHPcyH5iawniM8a5zdlMM9wAsjjZR1xoNT5iQDJsk2xJUxsEXt5yMkhmFKwNasV
OBXhpiBGvn1Yugbr53osSvTUwtvPwkBWmtkWEjPcaSbriELFkxQdP2z2JruFs6/M
S3KEthmw2qzHvRkJoe2n3R/HYkmKuP33yK3WSAIiqlPi0AutJLt19TmfbwwOxKa7
kYAd5PrWvBGCnlolBvUi2DAfzAqviJ45xGPKYLVdpM9rzx/GUC8mXgeEq8VjybOV
MK/O5RV9/Ys+Tmx5AAnxCkA8aOSGo6Q9m9m3Kkde6A4bu3LY0nKOdvb9Av/j1424
L24WoqgUnTyCAYlvjtX2B0eTwEDTBMn0D67J1uyHeDgDxwFcZLIWr8eM6mABBlUj
i5o2YKGeHExvCyq5S7nbg8qHq2mHgJGS7NXqCopTD3JFMfuzEZED0FHESsYQflwR
ysxA7fj0lf3OFHT9m3gFjtUn0rXR2c2L3rqkcMSYtd4pEgq6NzbtrpWoJVYx6nny
KOzV5GqWQ9fnBJVYreNgpoSbXGgpPqXTrUsHTInroRDCOe0//0Q=
=zpJY
-----END PGP SIGNATURE-----

--V9Ok67EScuVCJXFQcDQH2Phq5672i5Vuv--


From nobody Sun Mar 11 06:30:01 2018
Return-Path: <petithug@acm.org>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58983126D05 for <tram@ietfa.amsl.com>; Sun, 11 Mar 2018 06:30:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.442
X-Spam-Level: 
X-Spam-Status: No, score=-0.442 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L9xSyLEmbHuR for <tram@ietfa.amsl.com>; Sun, 11 Mar 2018 06:29:58 -0700 (PDT)
Received: from implementers.org (unknown [92.243.22.217]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48EAA124217 for <tram@ietf.org>; Sun, 11 Mar 2018 06:29:58 -0700 (PDT)
Received: from [IPv6:2601:648:8301:730f:ac0b:c7cc:59a:561f] (unknown [IPv6:2601:648:8301:730f:ac0b:c7cc:59a:561f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 5ADB6AE8D9; Sun, 11 Mar 2018 14:29:56 +0100 (CET)
To: Brandon Williams <brandon.williams@akamai.com>, "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>, "tram@ietf.org" <tram@ietf.org>
References: <325ddd79-ef98-c8ce-de50-1ef3878cd433@acm.org> <DM5PR16MB17882606F7602CEE66009903EAF20@DM5PR16MB1788.namprd16.prod.outlook.com> <c7716d08-f265-9ce9-ed2a-513ea0ddade6@acm.org> <DM5PR16MB1788777DA4671DD256BBE230EAF20@DM5PR16MB1788.namprd16.prod.outlook.com> <d496aa92-6c68-53f4-efca-34ac2880cfbc@acm.org> <BN6PR16MB14253E401210DF0235668335EADB0@BN6PR16MB1425.namprd16.prod.outlook.com> <90a0b73d-b441-5275-147f-a1449ed46989@akamai.com>
From: Marc Petit-Huguenin <petithug@acm.org>
Message-ID: <a20f120b-acc7-12f4-7f44-273bc2ad2fa9@acm.org>
Date: Sun, 11 Mar 2018 06:29:54 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <90a0b73d-b441-5275-147f-a1449ed46989@akamai.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="htskh29k3aRmAlab8JvQDqluZlQH33hOO"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/3D_roX_OuRwoEJhY1pMEHZliyRk>
Subject: Re: [tram] Review of TURNbis-11
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Mar 2018 13:30:00 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--htskh29k3aRmAlab8JvQDqluZlQH33hOO
Content-Type: multipart/mixed; boundary="pQfIw1eiLXyvuJXcliPnPxBfM2vzHjeK0";
 protected-headers="v1"
From: Marc Petit-Huguenin <petithug@acm.org>
To: Brandon Williams <brandon.williams@akamai.com>,
 "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>,
 "tram@ietf.org" <tram@ietf.org>
Message-ID: <a20f120b-acc7-12f4-7f44-273bc2ad2fa9@acm.org>
Subject: Re: [tram] Review of TURNbis-11
References: <325ddd79-ef98-c8ce-de50-1ef3878cd433@acm.org>
 <DM5PR16MB17882606F7602CEE66009903EAF20@DM5PR16MB1788.namprd16.prod.outlook.com>
 <c7716d08-f265-9ce9-ed2a-513ea0ddade6@acm.org>
 <DM5PR16MB1788777DA4671DD256BBE230EAF20@DM5PR16MB1788.namprd16.prod.outlook.com>
 <d496aa92-6c68-53f4-efca-34ac2880cfbc@acm.org>
 <BN6PR16MB14253E401210DF0235668335EADB0@BN6PR16MB1425.namprd16.prod.outlook.com>
 <90a0b73d-b441-5275-147f-a1449ed46989@akamai.com>
In-Reply-To: <90a0b73d-b441-5275-147f-a1449ed46989@akamai.com>

--pQfIw1eiLXyvuJXcliPnPxBfM2vzHjeK0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 03/09/2018 01:21 PM, Brandon Williams wrote:
> Hi Marc,
>=20
> Does the fix look OK to you now?

Yes, thanks.

>=20
> Thanks,
> --Brandon
>=20
> On 03/04/2018 07:50 AM, Konda, Tirumaleswar Reddy wrote:
>> Thanks Marc, fixed the discrepancy.
>>
>> -Tiru
>>
>>> -----Original Message-----
>>> From: Marc Petit-Huguenin [mailto:petithug@acm.org]
>>> Sent: Saturday, March 3, 2018 3:04 AM
>>> To: Konda, Tirumaleswar Reddy
>>> <TirumaleswarReddy_Konda@McAfee.com>; tram@ietf.org
>>> Subject: Re: [tram] Review of TURNbis-11
>>>
>>> As suggested by Brandon, I reviewed turnbis-14 for the modifications =
agreed
>>> on below, and found one discrepancy.=C2=A0 See inline.
>>>
>>> On 02/09/2018 05:45 AM, Konda, Tirumaleswar Reddy wrote:
>>>>> -----Original Message-----
>>>>> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Marc Petit-
>>>>> Huguenin
>>>>> Sent: Friday, February 9, 2018 6:54 PM
>>>>> To: Konda, Tirumaleswar Reddy
>>>>> <TirumaleswarReddy_Konda@McAfee.com>; tram@ietf.org
>>>>> Subject: Re: [tram] Review of TURNbis-11
>>>>>
>>>>> Hi,
>>>>>
>>>>> My responses inline.
>>>>>
>>>>> On 02/09/2018 03:53 AM, Konda, Tirumaleswar Reddy wrote:
>>>>>> Hi Marc,
>>>>>>
>>>>>> Please see inline
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Marc Petit=
-
>>>>>>> Huguenin
>>>>>>> Sent: Sunday, October 22, 2017 10:16 PM
>>>>>>> To: tram@ietf.org
>>>>>>> Subject: [tram] Review of TURNbis-11
>>>>>>>
>>>>>>> This is the second part of my review of TURNbis-11, i.e. everythi=
ng
>>>>>>> but the dual allocation part.
>>>>>>>
>>>>>>> - Section 2.1, last paragraph:
>>>>>>>
>>>>>>> May be a reference to RFC 5764 and RFC 7983 can be useful here.
>>>>>>> Same in section 4, second paragraph and following.=C2=A0 Same at =
the
>>>>>>> beginning of section 11.=C2=A0 Again in section 11.6 (if multiple=
xed,
>>>>>>> the message in the reserved range is not necessarily discarded).
>>>>>>
>>>>>> Even if the same host transport address is used for other protocol=
s,
>>>>> incoming packets to the TURN channel can be identified by just
>>>>> examining the source address of the packet.
>>>>>> May be I am missing something, I did not get a problem ?
>>>>>
>>>>> It was just an attempt to make TURN implementers aware of the demux=

>>>>> issues.
>>>>
>>>> Got it, added the following line:
>>>> The algorithm of demultiplexing packets received from multiple
>>>> protocols is discussed in [RFC7983].
>>>>
>>>>>
>>>>>>
>>>>>>>
>>>>>>> - Section 2.2, first paragraph:
>>>>>>>
>>>>>>> I think that an informative reference to RFC 7635 may be useful
>>>>>>> there, as alternative to the STUN authentication mechanism.
>>>>>>
>>>>>> Yes, updated.
>>>>>>
>>>>>>>
>>>>>>> - Section 2.9:
>>>>>>>
>>>>>>> The whole 2.9 section and subsections looks normative and so shou=
ld
>>>>>>> be moved after section 3, perhaps on their own top level section.=

>>>>>>
>>>>>> Done.
>>>>>>
>>>>>>>
>>>>>>> - Section 4, 4th paragraph:
>>>>>>>
>>>>>>> I would replace "For each allocation..." by "For each Allocate
>>>>>>> request...", because of the dual allocation feature.
>>>>>>
>>>>>> Fixed.
>>>>>>
>>>>>>>
>>>>>>> - Section 4, 12th paragraph:
>>>>>>>
>>>>>>> Should make clear clear that UDP covers also DTLS.
>>>>>>
>>>>>> Yes, updated.
>>>
>>> I cannot find this update in turn-14.
>>>
>>>>>>
>>>>>>>
>>>>>>> - Section 6.1, 2nd paragraph:
>>>>>>>
>>>>>>> If the port is multiplexed with other protocols (RTP, WebRtc,
>>>>>>> etc..) then it has to reuse an existing socket.=C2=A0 The documen=
t should
>>> explain this.
>>>>>>
>>>>>> It's already covered in Section 2.1 (last paragraph).
>>>>>>
>>>>>>>
>>>>>>> - Section 6.2, 3th paragraph:
>>>>>>>
>>>>>>> Is it time to recommend DTLS instead of UDP?=C2=A0 In that case w=
e need
>>>>>>> to make DTLS mandatory in section 4 paragraph 11 (and I support
>>>>>>> that
>>>>> change).
>>>>>>
>>>>>> No, DTLS has both advantages (e.g. dictionary attack)=C2=A0 and
>>>>>> disadvantages
>>>>> (e.g. double encryption of application data).
>>>>>
>>>>> OK.
>>>>>
>>>>>>
>>>>>>>
>>>>>>> - Section 6.4, second bullet:
>>>>>>>
>>>>>>> Replace "...SRV procedures)." with "...DNS resolution procedures)=
=2E"
>>>>>>
>>>>>> Any specific reason for the replacement ?
>>>>>
>>>>> This is to not exclude NPATR procedures (RFC 5928).
>>>>
>>>> Updated second bullet.
>>>>
>>>> Cheers,
>>>> -Tiru
>>>>
>>>>>
>>>>>>
>>>>>>>
>>>>>>> - Sections 14, 15 and 16:
>>>>>>>
>>>>>>> These are no longer new methods and attributes.=C2=A0 See also th=
e next
>>>>>>> comment.
>>>>>>
>>>>>> Fixed.
>>>>>>
>>>>>>>
>>>>>>> - Section 19:
>>>>>>>
>>>>>>> Here you need to update the existing methods, attributes and erro=
r
>>>>>>> code so the IANA registries point to the RFC-to-be, then you
>>>>>>> request allocation for the new attributes.=C2=A0 See section 17 o=
f
>>>>>>> STUNbis on a way to do that (that was done following a discussion=

>>>>>>> with the IANA
>>>>> representative at an IETF meeting).
>>>>>>
>>>>>> Thanks, updated draft.
>>>>>>
>>>>>>>
>>>>>>> Note that ICMP should be comprehension-mandatory, not optional, a=
s
>>>>> we
>>>>>>> do not want an old client to reject a Data indication with an ICM=
P
>>> attribute.
>>>>>>
>>>>>> If the indication contains unknown comprehension-required
>>>>>> attributes, the
>>>>> behavior is the indication is discarded and processing ceases.
>>>>>>
>>>>>>>
>>>>>>> Also, I do not know what this SendErr method is.
>>>>>>
>>>>>> Removed SendErr (stale entry from a previous version of the draft)=
=2E
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Nits
>>>>>>> ----
>>>>>>>
>>>>>>> Section 1:
>>>>>>>
>>>>>>> s/connection to the Internet ./connection to the Internet./
>>>>>>>
>>>>>>> Section 2.4, first paragraph:
>>>>>>>
>>>>>>> The text switches between the words "mechanisms" and "way".
>>> Choose
>>>>>>> one.
>>>>>>>
>>>>>>> Section 6.2, item 8:
>>>>>>>
>>>>>>> s/ADDITIONAL- ADDRESS-FAMILY/ADDITIONAL-ADDRESS-FAMILY/
>>>>>>>
>>>>>>> Section 12.1, "Preferred Behavior"
>>>>>>>
>>>>>>> s/Label Field[RFC3697]/Label Field [RFC3697]/
>>>>>>>
>>>>>>> Section 21:
>>>>>>>
>>>>>>> s/ADDRESS-ERRR-CODE/ADDRESS-ERR-CODE/
>>>>>>>
>>>>>>> Section 22:
>>>>>>>
>>>>>>> s/orginal/original/
>>>>>>
>>>>>> Thanks, fixed all above nits.
>>>>>>



--=20
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: https://marc.petit-huguenin.org
Profile: https://www.linkedin.com/in/petithug


--pQfIw1eiLXyvuJXcliPnPxBfM2vzHjeK0--

--htskh29k3aRmAlab8JvQDqluZlQH33hOO
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEBSI+IuCHU8MsI1GjKcRFldZqfsQFAlqlL1IACgkQKcRFldZq
fsSB9g//WMrpXvLsthtO4JJuIIh1rqCgsJO/Go8UiyFqBmciajFlQg5OiDEiOiVs
vKC49FHiWw39ArAbD++qorbREiQtdSH1Sn8uPaDGcxZnagN8IOKY/9wKeLV/8a9k
zIENo3R77MId406jxcWqVaMSvkueLdSe1qDXEmZhXt0s4Q5ilPJf01QRVQgf+UqQ
3c/N1PkgF2eoV26IvXUwrjDvLF5gkuS3W8HJnypgUELMY16CxxP8cQGkOZUyx0W0
/YPCL4OOlb6yZ9u/qQ9RX/1VuatTR1olXp1NC12mRwZ3IvPC6E89Mi5xp+moCLAv
/qJRWRUTD2P6oKXaxCbtZbh7gBVhjfjdCxpsZQGaktsANcu+KX/TVLdbnnIkrgZY
szfrNXj9mkexf6z8tgRFGXVCUmRF7sPDOl18DlyuBobbTgmkKUAfM2ZbfGCoWyym
fzguz41ht2f4XlPJOWVnLORw0htiaO2GTBbBg57ekge31KrfLhZ618+QgK/DIvRV
NWn6B7wacnzjw0djGC0eIQfPY+wQ1Jg/s9AV33M3woWZEwxmNY2N3F7Vx5jtnQ9c
tgjw5sCiiJzvHMUae96OeBHseeuyruQH/pvELUb3U/Su1MsV5Xe+s7S1FT6xXMYo
py4qGYSDke7YcAxXRi1Sc6zLAYX0Ik88K5THC+1B53SMA1IWJ64=
=0+rz
-----END PGP SIGNATURE-----

--htskh29k3aRmAlab8JvQDqluZlQH33hOO--


From nobody Sun Mar 11 06:40:40 2018
Return-Path: <tasveren@rbbn.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F38CA126D05 for <tram@ietfa.amsl.com>; Sun, 11 Mar 2018 06:40:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.491
X-Spam-Level: 
X-Spam-Status: No, score=-2.491 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=sonusnetworks.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 37usmCNdvI9I for <tram@ietfa.amsl.com>; Sun, 11 Mar 2018 06:40:34 -0700 (PDT)
Received: from us-smtp-delivery-181.mimecast.com (us-smtp-delivery-181.mimecast.com [216.205.24.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1F361201FA for <tram@ietf.org>; Sun, 11 Mar 2018 06:40:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=SonusNetworks.onmicrosoft.com; s=selector1-rbbn-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=wQnVsAt1nqAMxwWvlCxYa3tNEL1WlqyR3eiTgqq9ma0=; b=hjEX2KZh4wBFHKQJSvRs514j6H2dUYbEk2DecdDxw0iwQexz32tyeo/I4ZGvRQN1X6M2ExB+ifRYeEvmAZqFTa5JNrnIS3+4m+lB3j33QUlWwghUHeCgE815iw9iHPgMtzeRS7RGf887uPLacCVP/UvybLmdTzpPgXBDFZcqCNI=
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03lp0017.outbound.protection.outlook.com [216.32.181.17]) (Using TLS) by us-smtp-1.mimecast.com with ESMTP id us-mta-201-Thlaci7NPLu1n4vOod0nug-1; Sun, 11 Mar 2018 09:40:30 -0400
Received: from CY4PR03MB3160.namprd03.prod.outlook.com (10.171.245.165) by CY4PR03MB2487.namprd03.prod.outlook.com (10.168.165.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.548.13; Sun, 11 Mar 2018 13:40:24 +0000
Received: from CY4PR03MB3160.namprd03.prod.outlook.com ([fe80::34a3:3001:f444:3072]) by CY4PR03MB3160.namprd03.prod.outlook.com ([fe80::34a3:3001:f444:3072%13]) with mapi id 15.20.0548.021; Sun, 11 Mar 2018 13:40:24 +0000
From: "Asveren, Tolga" <tasveren@rbbn.com>
To: Marc Petit-Huguenin <petithug@acm.org>, "Gonzalo Salgueiro (gsalguei@cisco.com)" <gsalguei@cisco.com>, "tram@ietf.org" <tram@ietf.org>
Thread-Topic: [tram] draft-ietf-tram-stun-pmtud-06 review
Thread-Index: AdOoeuWqoyIVbPnJTkKqVXoa0q8HIQKi1NCAACzPOKABXvt2AAACPF6Q
Date: Sun, 11 Mar 2018 13:40:24 +0000
Message-ID: <CY4PR03MB316053DB4B75FCF6A9619233A5DC0@CY4PR03MB3160.namprd03.prod.outlook.com>
References: <CY4PR03MB316039CC07807621C64AFE39A5C90@CY4PR03MB3160.namprd03.prod.outlook.com> <10ce3dde-2401-dc4f-e231-13678f6494d1@acm.org> <CY4PR03MB3160D0E46134CF10AE7CBAF4A5DB0@CY4PR03MB3160.namprd03.prod.outlook.com> <a7726725-5c60-c284-9249-29e67b6a8d7f@acm.org>
In-Reply-To: <a7726725-5c60-c284-9249-29e67b6a8d7f@acm.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [73.29.251.142]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR03MB2487; 7:MqV2U+c0a6UO7jolDPwjZgQPQrV9lMawEFqzqE0junboXOH9JTVD8hMwFI8l8RzGSsgIUqcpzdVQyaeC/IVSgMYPc3JiX+0bcmSDMw/bicw/VA3zd7CezT4T3+9yokYoJLSuwbQjZjlxbCbKv5wTFxAU/nvvBGWh5ZVtwe+ExFZjLe6T/bSn3sgLE44IDt6L/Mr82oAdxD0TSp/GbO/bLxgzOq3U8GTMfbsp13B5qyKY4ep9e/TIMi29tqlK/06/; 20:tO81a7QgpsY2n70Ije6moXshBy6CW/Rp3x8shYH3T86iQzNRXp7Dz/ryvTli0xw+qaa2olwZxQALYE7oJUD6kaF/lAjTQa6Bo6d9Enm+qlxf7AkCXVKNBjLXOnzBBv4nz5XvX/RE5l7Xkh3HzESwqXnAlIrVugyEpygy0Ywsoj0=
x-ms-office365-filtering-correlation-id: 7735767e-77a5-441f-dc23-08d58755a4c7
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:CY4PR03MB2487; 
x-ms-traffictypediagnostic: CY4PR03MB2487:
x-microsoft-antispam-prvs: <CY4PR03MB2487711D0447679116A60EC0A5DC0@CY4PR03MB2487.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(192374486261705)(128460861657000)(95692535739014)(213716511872227)(81160342030619);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3002001)(93006095)(93001095)(10201501046)(3231220)(944501244)(52105095)(6041310)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123560045)(20161123558120)(6072148)(201708071742011); SRVR:CY4PR03MB2487; BCL:0; PCL:0; RULEID:; SRVR:CY4PR03MB2487; 
x-forefront-prvs: 0608DEDB67
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39850400004)(366004)(396003)(376002)(39380400002)(346002)(189003)(199004)(51444003)(252514010)(13464003)(51914003)(478600001)(966005)(5660300001)(229853002)(45080400002)(102836004)(74316002)(68736007)(186003)(26005)(8936002)(93886005)(3660700001)(59450400001)(106356001)(33656002)(81156014)(305945005)(8676002)(81166006)(2950100002)(6506007)(53546011)(7736002)(2906002)(6116002)(3846002)(86362001)(99286004)(66066001)(97736004)(3280700002)(2900100001)(7696005)(76176011)(110136005)(6246003)(2501003)(105586002)(316002)(5250100002)(6436002)(6306002)(55016002)(9686003)(25786009)(14454004)(53936002); DIR:OUT; SFP:1101; SCL:1; SRVR:CY4PR03MB2487; H:CY4PR03MB3160.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
x-microsoft-antispam-message-info: M14oe7cuf+lqLyQAdKplrpyUhThGvi6eQmNkzg3bGJMPdS9ipg5mRVC/zvfPd5ZCZ+jIoAo+xLCcCY94KMmMcOL0pMKlJdOdJ8sOUvayLl9pdIcqetFVcSuFs+UxlxvoCZQ6jSomFc+xE1rtvOxnNa3tUDWDRSr58j3AGfbDubDR2tZXrHue2hR9thczdf7nHaqriLzCllUcQUp5zGOq/FovM6w54qj+t9LnssqRTV36KPBdP3NwxWeW47Ayg8BzkMvu/uigHhaEiOt9HRwTCslZsMJ1ZvZYnVhpTQLNP306dddUl5h+SJ+PHl6B8Sw8rVseHQ984Y2uO2QeDkr6CQ==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-OriginatorOrg: rbbn.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 7735767e-77a5-441f-dc23-08d58755a4c7
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Mar 2018 13:40:24.8387 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 29a671dc-ed7e-4a54-b1e5-8da1eb495dc3
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR03MB2487
X-MC-Unique: Thlaci7NPLu1n4vOod0nug-1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/_jYAfaFIBUWGc1W53Y8SiePvcWs>
Subject: Re: [tram] draft-ietf-tram-stun-pmtud-06 review
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Mar 2018 13:40:38 -0000

TWFyYywNCg0KVGhhbmtzIGZvciB0aGUgZXhwbGFuYXRpb25zL2Fuc3dlcnMuIEkgYW0gaGFwcHkg
d2l0aCB0aGUgY3VycmVudCB2ZXJzaW9uIGJhc2VkIHRoZXNlLiBJIGRvbuKAmXQgdGhpbmsgYW55
IGNoYW5nZXMgYXJlIG5lZWRlZCBhbmQgSSBkb27igJl0IGhhdmUgZnVydGhlciBjb21tZW50cy4N
Cg0KVGhhbmtzLA0KVG9sZ2ENCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IE1h
cmMgUGV0aXQtSHVndWVuaW4gPHBldGl0aHVnQGFjbS5vcmc+IA0KU2VudDogU3VuZGF5LCBNYXJj
aCAxMSwgMjAxOCA4OjM1IEFNDQpUbzogQXN2ZXJlbiwgVG9sZ2EgPHRhc3ZlcmVuQHJiYm4uY29t
PjsgR29uemFsbyBTYWxndWVpcm8gKGdzYWxndWVpQGNpc2NvLmNvbSkgPGdzYWxndWVpQGNpc2Nv
LmNvbT47IHRyYW1AaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbdHJhbV0gZHJhZnQtaWV0Zi10cmFt
LXN0dW4tcG10dWQtMDYgcmV2aWV3DQoNClNlZSBpbmxpbmUuDQoNCk9uIDAzLzA0LzIwMTggMDc6
MDMgQU0sIEFzdmVyZW4sIFRvbGdhIHdyb3RlOg0KPiBIaSBNYXJjLA0KPiANCj4gUGxlYXNlIHNl
ZSBpbmxpbmUgZm9yIGNvbW1lbnRzL2Fuc3dlcnMvcXVlc3Rpb25zLg0KPiANCj4gVGhhbmtzLA0K
PiBUb2xnYQ0KPiANCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogTWFyYyBQ
ZXRpdC1IdWd1ZW5pbiA8cGV0aXRodWdAYWNtLm9yZz4gDQo+IFNlbnQ6IFNhdHVyZGF5LCBNYXJj
aCAzLCAyMDE4IDEwOjQyIEFNDQo+IFRvOiBBc3ZlcmVuLCBUb2xnYSA8dGFzdmVyZW5AcmJibi5j
b20+OyBHb256YWxvIFNhbGd1ZWlybyAoZ3NhbGd1ZWlAY2lzY28uY29tKSA8Z3NhbGd1ZWlAY2lz
Y28uY29tPjsgdHJhbUBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogW3RyYW1dIGRyYWZ0LWlldGYt
dHJhbS1zdHVuLXBtdHVkLTA2IHJldmlldw0KPiANCj4gVGhhbmtzIGZvciB0aGUgcmV2aWV3LCBw
bGVhc2Ugc2VlIGlubGluZS4NCj4gDQo+IEFzIHRoZSBjdXRvZmYgaXMgTW9uZGF5IGFmdGVybm9v
biwgSSdsbCBwdWJsaXNoIC0wNyBqdXN0IGFmdGVyIHNlbmRpbmcgdGhpcyBlbWFpbC4NCj4gDQo+
IE9uIDAyLzE3LzIwMTggMDk6NDAgUE0sIEFzdmVyZW4sIFRvbGdhIHdyb3RlOg0KPj4gTWFyYywg
R29uemFsbywNCj4+DQo+PiBTb21lIGNvbW1lbnRzL3F1ZXN0aW9ucyBmb3IgZHJhZnQtaWV0Zi10
cmFtLXN0dW4tcG10dWQtMDY6DQo+Pg0KPj4gaS0gNC4NCj4+DQo+PiAgIEltcGxlbWVudGF0aW9u
cyBzdXBwb3J0aW5nIHRoaXMgc3BlY2lmaWNhdGlvbiBNVVNUIGltcGxlbWVudCB0aGUNCj4+ICAg
IHNlcnZlciBzaWRlIG9mIGJvdGggdGhlIFNpbXBsZSBQcm9iaW5nIG1lY2hhbmlzbSAoU2VjdGlv
biA0LjEpIGFuZA0KPj4gICAgdGhlIENvbXBsZXRlIFByb2JpbmcgbWVjaGFuaXNtIChTZWN0aW9u
IDQuMikuDQo+PiAgICBJbXBsZW1lbnRhdGlvbnMgc3VwcG9ydGluZyB0aGlzIHNwZWNpZmljYXRp
b24gTVVTVCBpbXBsZW1lbnQgdGhlDQo+PiAgICBjbGllbnQgc2lkZSBvZiB0aGUgQ29tcGxldGUg
UHJvYmluZyBtZWNoYW5pc20uICBUaGV5IE1BWSBpbXBsZW1lbnQNCj4+ICAgIHRoZSBjbGllbnQg
c2lkZSBvZiB0aGUgU2ltcGxlIFByb2JpbmcgbWVjaGFuaXNtLg0KPj4NCj4+IEkgZG9uJ3Qgc2Vl
IHRoZSByYXRpb25hbGUgYmVoaW5kIG1hbmRhdGluZyB0aGlzIGJlaGF2aW9yLiBTdWNoIHNlbWFu
dGljcyBpbiBnZW5lcmFsIGFyZSB0YWtlbiBjYXJlIG9mIGluIHRoZSBjb250ZXh0IG9mIGEgY2Fw
YWJpbGl0eSBuZWdvdGlhdGlvbiBtZWNoYW5pc20sIHdoaWNoIHRoaXMgZG9jdW1lbnQgZG9lcyBu
b3Qgc3BlY2lmeS4gQXMgaXQgc3RhbmRzIHJpZ2h0IG5vdywgSSB0aGluayB0aGlzIGlzIGJlc3Qg
bGVmdCB0byBsb2NhbCBwb2xpY3kgYW5kIGJpbGF0ZXJhbCBhZ3JlZW1lbnRzIGFuZCBJIHdvdWxk
IHN1Z2dlc3Qgbm90IHRvIHVzZSBhbnl0aGluZyBzdHJvbmdlciB0aGFuICJSRUNPTU1FTkQiLg0K
PiANCj4gSXQgdG9vayBtZSBzb21lIHRpbWUgdG8gcmVtZW1iZXIgd2h5IHRoYXQgd2FzIHRoZSBj
YXNlLiAgSUlSQywgb25lIG9mIHRoZSByZWFzb25zIG9mIGRvaW5nIHRoaXMgaXMgYmVjYXVzZSBv
ZiB0aGUgaW1wbGljaXQgcHJvYmUgc3VwcG9ydCBpbiBzZWN0aW9uIDUuMi4gIEJlY2F1c2UgdGhl
cmUgaXMgbm8gZXhwbGljaXQgc2lnbmFsaW5nIHRoZXJlLCB3ZSBuZWVkIHRoZSBzZXJ2ZXIgc2lk
ZSAod2hpY2ggd2FzIHByZXZpb3VzbHkgdGhlIGNsaWVudCBzaWRlKSB0byBiZSByZWFkeSB0byBy
ZXNwb25kIHRvIGJvdGggU2ltcGxlIGFuZCBDb21wbGV0ZSBQcm9iaW5nLiAgSGVuY2UgdGhlICJz
ZXJ2ZXIgbXVzdCBkbyBib3RoLCBjbGllbnQgY2hvb3NlIHdoYXQgdGhleSB3YW50IHRvIGRvIiBy
dWxlLg0KPiANCj4gVGhlIG90aGVyIHJlYXNvbiBpcyB0aGF0IGlmIHdlIGxldCBpbXBsZW1lbnRl
cnMgY2hvb3NlLCB0aGVuIENvbXBsZXRlIFByb2JpbmcgLSB3aGljaCBpcyB0aGUgY29ycmVjdCB3
YXkgb2YgZG9pbmcgcHJvYmluZyAtIHdpbGwgbmV2ZXIgYmUgdXNlZC4NCj4gW1RPTEdBXSBJZiBj
bGllbnQgZG9lcyBub3QgZ2V0IHJlcGxpZXMgZm9yIGEgbWVjaGFuaXNtIGl0IFNIT1VMRCB0cnkg
dGhlIG90aGVyIG9uZS4gSG9uZXN0bHkgSSBkb27igJl0IHNlZSBhIGNvbXBlbGxpbmcgcmVhc29u
IHRvIG1hbmRhdGUgYW55dGhpbmcgb24gdGhlIHNlcnZlciBzaWRlLiBUaGVyZSBpcyBubyBuZWdv
dGlhdGlvbiBtZWNoYW5pc20gYW5kIHRoYXQgY2Fu4oCZdCBiZSBlbmZvcmNlZCBvbiBwcm90b2Nv
bCBsZXZlbCBhbnlob3cuIEkgc3VnZ2VzdCB0byB1c2UgUkVDT01NTkVEIGZvciBzZXJ2ZXIgYW5k
IGFkZCBhIHNlbnRlbmNlIGZvciBjbGllbnQgYmVoYXZpb3IgdGhhdCBpdCBTSE9VTEQgdHJ5IHRo
ZSBvdGhlciBtZWNoYW5pc20gaWYgb25lIGRvZXMgbm90IGdldCBhbnkgcmVwbGllcyBhdCBhbGwu
DQoNCk5vLCBub3QgbWFraW5nIHRoZSBDb21wbGV0ZSBQcm9iaW5nIG1hbmRhdG9yeSBpbiB0aGUg
c2VydmVyIHJlbW92ZXMgdGhlIGNvbXBsaWFuY2Ugd2l0aCBSRkMgNDgyMSwgd2hpY2ggaXMgdGhl
IHdob2xlIHBvaW50IG9mIHRoaXMgZG9jdW1lbnQuICBJZiBwZW9wbGUgZG8gbm90IHdhbnQgY29t
cGxpYW5jZSB3aXRoIFJGQyA0ODIxLCB0aGV5IGp1c3QgaGF2ZSB0byBub3QgaW1wbGVtZW50IHRo
YXQgUkZDLXRvLWJlLg0KDQpBZnRlciBDb21wbGV0ZSBQcm9iaW5nIGlzIGltcGxlbWVudGVkIG9u
IHRoZSBzZXJ2ZXIgc2lkZSwgaXQncyBlYXN5IHRvIGFkZCBTaW1wbGUgUHJvYmluZywgc28gbWFr
aW5nIGl0IG1hbmRhdG9yeSB0b28gZG9lcyBub3QgYWRkIG11Y2ggYnVyZGVuIG9uIHRoZSBpbXBs
ZW1lbnRlci4NCg0KQnV0IGlmIHlvdSBpbnNpc3Qgb2YgbWFraW5nIHRoZSBzZXJ2ZXIgc3VwcG9y
dCBhcyBSRUNPTU1FTkQsIHRoZW4gSSdsbCBzcGxpdCB0aGUgUkZDLXRvLWJlIGluIHR3byBSRkNz
LCBvbmUgZm9yIENvbXBsZXRlIFByb2JpbmcgYW5kIGNvbXBsaWFuY2Ugd2l0aCBSRkMgNDgyMSwg
YW5kIHRoZSBvdGhlciBmb3IgU2ltcGxlIFByb2JpbmcuDQoNCj4gDQo+Pg0KPj4gaWktIDQuMQ0K
Pj4gREYgYml0IHNldCBvdmVyIFVEUC4NCj4+ID09Pg0KPj4gREYgYml0IGluIElQIEhlYWRlci4N
Cj4+IFJpZ2h0PyAgKHRoZSBzYW1lIGluIDQuMikNCj4gDQo+IE5vdCByZWFsbHksIHRoZSBQcm9i
ZSBSZXF1ZXN0IGlzIHN0aWxsIHNlbnQgb3ZlciBVRFAsIHNvIEkgY2hhbmdlZCB0aGUgdGV4dCB0
byB0aGF0ICh0d2ljZSk6DQo+IA0KPiAgVGhlIFNpbXBsZSBQcm9iaW5nIG1lY2hhbmlzbSBpcyBp
bXBsZW1lbnRlZCBieSBzZW5kaW5nIGEgUHJvYmUgIFJlcXVlc3Qgd2l0aCBhIFBBRERJTkcgW1JG
QzU3ODBdIGF0dHJpYnV0ZSBvdmVyIFVEUCB3aXRoIHRoZSBERiBiaXQgIHNldCBpbiB0aGUgSVAg
aGVhZGVyLiAgQSByb3V0ZXIgb24gdGhlIHBhdGggdG8gdGhlIHNlcnZlciBjYW4gcmVqZWN0ICB0
aGlzIHJlcXVlc3Qgd2l0aCBhbiBJQ01QIG1lc3NhZ2Ugb3IgZHJvcCBpdC4NCj4gDQo+ICBUaGUg
Q29tcGxldGUgUHJvYmluZyBtZWNoYW5pc20gaXMgaW1wbGVtZW50ZWQgYnkgc2VuZGluZyBvbmUg
b3IgbW9yZSAgUHJvYmUgSW5kaWNhdGlvbnMgd2l0aCBhIFBBRERJTkcgYXR0cmlidXRlIG92ZXIg
VURQIHdpdGggdGhlIERGIGJpdCAgc2V0IGluIHRoZSBJUCBoZWFkZXIgZm9sbG93ZWQgYnkgYSBS
ZXBvcnQgUmVxdWVzdCB0byB0aGUgc2FtZSBzZXJ2ZXIuDQo+IFtUT0xHQV0gTG9va3MgZ29vZCwg
SSBqdXN0IHdhbnRlZCB0byBtYWtlIHN1cmUgYWJvdXQgdGhlICJERiBiaXQgaW4gSVAgaGVhZGVy
IiBwYXJ0Lg0KPiANCj4+DQo+PiBpaWktIDQuMS4xDQo+PiBBIGNsaWVudCBNVVNUIE5PVCBzZW5k
IGEgcHJvYmUgaWYgaXQgZG9lcyBub3QgaGF2ZSBrbm93bGVkZ2UgdGhhdCB0aGUNCj4+ICAgIHNl
cnZlciBzdXBwb3J0cyB0aGlzIHNwZWNpZmljYXRpb24uICBUaGlzIGlzIGRvbmUgZWl0aGVyIGJ5
IGV4dGVybmFsDQo+PiAgICBzaWduYWxsaW5nIG9yIGJ5IGEgbWVjaGFuaXNtIHNwZWNpZmljIHRv
IHRoZSBVRFAgcHJvdG9jb2wgdG8gd2hpY2gNCj4+ICAgIFBNVFVEIGNhcGFiaWxpdGllcyBhcmUg
YWRkZWQgb3IgYnkgb25lIG9mIHRoZSBtZWNoYW5pc21zIHNwZWNpZmllZCBpbg0KPj4gICAgU2Vj
dGlvbiA1Lg0KPj4gSSBzdWdnZXN0IGFkZGluZyB0ZXh0IGZvciBwb3NzaWJsZSB1c2Ugb2YgbG9j
YWwgcG9saWN5L2JpbGF0ZXJhbCBhZ3JlZW1lbnRzIGZvciB0aGlzIHB1cnBvc2UuDQo+IA0KPiBJ
IGFtIG5vdCBzdXJlIHdoYXQgdG8gYWRkIHRvIHdoYXQgaXMgc2FpZC4gIERvIHlvdSBoYXZlIHRl
eHQgdG8gc3VnZ2VzdD8NCj4gW1RPTEdBXSBNYXliZSBieSBqdXN0IGFkZGluZyBzb21ldGhpbmcg
bGlrZToNCj4gIkluZm9ybWF0aW9uIGFib3V0IGNsaWVudC9zZXJ2ZXIgc3VwcG9ydCBmb3IgdGhp
cyBzcGVjaWZpY2F0aW9uLCBmb3IgZXhhbXBsZSwgY291bGQgYmUgYmFzZWQgb24gbG9jYWwgcG9s
aWN5IGFuZCBiaWxhdGVyYWwgYWdyZWVtZW50cyBhbW9uZyByZWxldmFudCBvcmdhbml6YXRpb25z
LiINCg0KU2VlIGFib3ZlLg0KDQo+IA0KPj4NCj4+IGl2LSAgNC4yDQo+PiBTb21lIHByb3RvY29s
cyBtYXkgYWxyZWFkeSBoYXZlIGEgd2F5IG9mIGlkZW50aWZ5aW5nIGVhY2ggaW5kaXZpZHVhbA0K
Pj4gICAgVURQIHBhY2tldCwgaW4gd2hpY2ggY2FzZSB0aGVzZSBpZGVudGlmaWVycyBTSE9VTEQg
YmUgdXNlZCBpbiB0aGUNCj4+ICAgIElERU5USUZJRVJTIGF0dHJpYnV0ZSBvZiB0aGUgUmVwb3J0
IFJlc3BvbnNlLg0KPj4gV2hhdCBpcyBtZWFudCBoZXJlIGFzICJzb21lIHByb3RvY29scyI/IEFy
ZSB5b3UgcmVmZXJyaW5nICB0byB3aGF0IGlzIGNhcnJpZWQgYXMgcGF5bG9hZCBvZiBVRFAgb3Ig
d2hhdCBpcyB1c2VkIGJlbG93IFVEUD8NCj4gDQo+IFRoZSBmb3JtZXIuICBJIGNoYW5nZWQgdGhl
IHRleHQgdG8gImFwcGxpY2F0aW9uIGxheWVyIHByb3RvY29sczoiDQo+IFtUT0xHQV0gVGhhbmtz
Lg0KPiANCj4+DQo+PiB2LSA0LjINCj4+IEluIHRoZSBmaXJzdCBwYWNrZXQgaWRlbnRpZmljYXRp
b24gbWVjaGFuaXNtLCB0aGUgc2VydmVyIGNvbXB1dGVzIGENCj4+ICAgIGNoZWNrc3VtIG92ZXIg
ZWFjaCBwYWNrZXQgcmVjZWl2ZWQgYW5kIHNlbmRzIGJhY2sgdG8gdGhlIHNlbmRlciB0aGUNCj4+
ICAgIGxpc3Qgb2YgY2hlY2tzdW1zIG9yZGVyZWQgY2hyb25vbG9naWNhbGx5LiAgVGhlIGNsaWVu
dCBjb21wYXJlcyB0aGlzDQo+PiAgICBsaXN0IHRvIGl0cyBvd24gbGlzdCBvZiBjaGVja3N1bXMu
DQo+PiBXaGF0IGlmIHRoZXJlIGFyZSB0d28gcHJvYmVzIHdpdGggdGhlIHNhbWUgY2hlY2tzdW0g
cmlnaHQgYWZ0ZXIgZWFjaCBvdGhlciBhbmQgb25lIG9mIHRoZW0gaXMgbG9zdD8gSG93IGNhbiBj
bGllbnQgZGlzYW1iaWd1YXRlIHN1Y2ggYSBjYXNlIGluICB0aGUgcmVzcG9uc2U/DQo+IA0KPiBJ
IGFtIG5vdCBzdXJlIHRvIGdldCB0aGUgcHJvYmxlbSBoZXJlLiAgVGhlIHNlbmRlciBrZWVwcyBh
IGNocm9ub2xvZ2ljYWxseSBvcmRlcmVkIGxpc3Qgb2YgdGhlIGNoZWNrc3VtcyBvZiB0aGUgc2Vu
dCBwYWNrZXRzIChkYXRhIGFuZCBwcm9iZXMpLCBzbyBpbiB0aGF0IGNhc2UgdGhlcmUgaXMgYSBz
ZXF1ZW5jZSBvZiB0d28gaWRlbnRpY2FsIGNoZWNrc3VtcyBpbiB0aGF0IGxpc3QuICBUaGUgc2Vy
dmVyIHNlbmRzIGJhY2sgYSBsaXN0IG9mIGNoZWNrc3VtcywgYnV0IHdpdGggb25seSBvbmUgb2Yg
dGhhdCB2YWx1ZSAob3IgZXZlbiAwKS4gIFRoZSBsb3NzIGNhbiBiZSBkZXRlY3RlZC4NCj4gW1RP
TEdBXSBMb3NzIGNhbiBiZSBkZXRlY3RlZCBidXQgd2hpY2ggb25lIGlzIGxvc3Q/DQo+IA0KPiBQ
cm9iZS1uICAoY2hlY2tzdW0tQSkNCj4gUHJvYmUtbisxIChjaGVja3N1bS1BKQ0KPiANCj4gT25s
eSBhIHNpbmdsZSByZXBseSBmb3IgKGNoZWNrc3VtLUEpIGlzIHJlY2VpdmVkLg0KDQpSZXBsaWVz
IGFyZSBvbmx5IGZvciB0aGUgU2ltcGxlIFByb2JpbmcgbWVjaGFuaXNtLCBhIG1lY2hhbmlzbSB0
aGF0IGRvZXMgbm90IG5lZWQgdG8gaWRlbnRpZnkgVURQIHBhY2tldHMuDQoNCj4gDQo+IElzIFBy
b2JlLW4gb3IgUHJvYmUtbisxIGxvc3Q/DQoNCklmIHRoZSBzYW1lIHByb2JlIGlzIHNlbnQgbXVs
dGlwbGUgdGltZXMgYnV0IHNvbWUgYXJlIGRyb3BwZWQgdGhlbiB3ZSBrbm93IHRoYXQsIHdlIGp1
c3QgZG8gbm90IGtub3cgZXhhY3RseSB3aGljaCBvbmUuDQoNClRoZSB3aG9sZSBwb2ludCBvZiB0
aGlzIGlzIHRvIHNlcGFyYXRlIHRoZSBwYWNrZXRzIGRyb3BzIGJlY2F1c2Ugb2YgYSBuZXR3b3Jr
IGNvbmRpdGlvbiAod2hpY2ggc2hvdWxkIG5vdCBhZmZlY3QgdGhlIFBNVFUpIGZyb20gdGhlIHRo
ZSBwYWNrZXRzIGRyb3BzIGJlY2F1c2Ugb2YgYW4gb3ZlcnNpemVkIHBhY2tldCwgd2hpY2ggZG9l
cyBub3QgcmVxdWlyZSB0byBrbm93IGV4YWN0bHkgd2hpY2ggcGFja2V0IHdhcyBkcm9wcGVkLCBh
cyB0aGV5IGFyZSBhbGwgZHJvcHBlZC4gIE5vdGUgdGhhdCB0d28gcHJvYmVzIHdpdGggZGlmZmVy
ZW50IGxlbmd0aHMgd2lsbCBoYXZlIGRpZmZlcmVudCBjaGVja3N1bSwgc28gd2UgY2FuIGlzb2xh
dGUgZXhhY3RseSB3aGF0IHByb2JlIHdhcyByZWplY3RlZCBhbmQgd2h5Lg0KDQpUaGF0IHNhaWQs
IFJGQyA0ODIxIGxlYXZlcyB0aGUgY2xpZW50IGZyZWUgdG8gaW1wbGVtZW50IHdoYXRldmVyIGFs
Z29yaXRobSBpdCB3YW50LCBzbyB0aGVyZSBtYXkgYmUgc29tZSBmdXR1cmUgYWxnb3JpdGhtIHRo
YXQgY291bGQgdXNlIHRoZSBrbm93bGVkZ2Ugb2YgZXhhY3RseSB3aGljaCBwYWNrZXQgd2FzIGRy
b3BwZWQuICBJTiB0aGF0IGNhc2UgdGhlIGZ1dHVyZSBSRkMgdGhhdCB3aWxsIGRlc2NyaWJlIGhv
dyB0byByZWNvZ25pemUgdGhlIFVEUCBwYWNrZXRzIGZvciBhIHNwZWNpZmljIHByb3RvY29sIHdp
bGwganVzdCBoYXZlIHRvIGNob29zZSBhIG1ldGhvZCB0aGF0IHBlcm1pdHMgdG8gZGlmZmVyZW50
aWF0ZSBpbmRpdmlkdWFsIHBhY2tldHMgaW4gdGhlIFJlcG9ydCByZXNwb25zZS4NCg0KPiANCj4+
DQo+PiB2LSA3DQo+PiBUaGUgU2ltcGxlIFByb2JpbmcgbWVjaGFuaXNtIG1heSBiZSB1c2VkIHdp
dGhvdXQgYXV0aGVudGljYXRpb24NCj4+ICAgIGJlY2F1c2UgdGhpcyB1c2FnZSBieSBpdHNlbGYg
Y2Fubm90IHRyaWdnZXIgYW4gYW1wbGlmaWNhdGlvbiBhdHRhY2sNCj4+ICAgIGJlY2F1c2UgdGhl
IFByb2JlIFJlc3BvbnNlIGlzIHNtYWxsZXIgdGhhbiB0aGUgUHJvYmUgUmVxdWVzdC4NCj4+IElz
bid0IHRoZSBzYW1lIHRydWUgZm9yIFN1bShQcm9iZSBSZXF1ZXN0cykgPiAoUmVwb3J0IFJlc3Bv
bnNlKT8NCj4gDQo+IEkgdGhpbmsgdGhhdCBtZWNoYW5pc20gd2FzIHNldCBmb2xsb3dpbmcgYSBy
ZXZpZXcgdGhhdCB3YXMgd29ycmllZCBhYm91dCBhbXBsaWZpY2F0aW9uIGF0dGFjay4gIFdlIGhh
dmUgdGhlIHNpbXBsZSBwcm9iZSBtZWNoYW5pc20gd2l0aG91dCBhdXRoZW50aWNhdGlvbiB0byBr
ZWVwIHRoZSBiYXJyaWVyIHRvIGVudHJ5IHZlcnkgbG93LCBpLmUuIHRoZSBtaW5pbXVtIHJlcXVp
cmVkIGltcGxlbWVudGF0aW9uIHBvc3NpYmxlLg0KPiANCj4gU2VjdXJpdHkgZXhwZXJ0IGNhbiBj
aGltZSBpbi4NCj4gW1RPTEdBXSBJIHRoaW5rIHRoYXQgd291bGQgYmUgZ29vZC4gV2hvIHdvdWxk
IGJlIHRoYXQ/DQo+IA0KPj4NCj4+IHZpaS0gbml0DQo+PiA9PSBUaGUgY29weXJpZ2h0IHllYXIg
aW4gdGhlIElFVEYgVHJ1c3QgYW5kIGF1dGhvcnMgQ29weXJpZ2h0IExpbmUgZG9lcyBub3QNCj4+
ICAgICAgbWF0Y2ggdGhlIGN1cnJlbnQgeWVhcg0KPj4NCj4+ICAgLS0gVGhlIGRvY3VtZW50IGRh
dGUgKFNlcHRlbWJlciAxLCAyMDE3KSBpcyAxNjkgZGF5cyBpbiB0aGUgcGFzdC4gIElzIHRoaXMN
Cj4+ICAgICAgaW50ZW50aW9uYWw/DQo+IA0KPiBXaWxsIGJlIHVwZ3JhZGVkIHdpdGggdGhlIG5l
eHQgcHVibGljYXRpb24uDQo+IFtUT0xHQV0gVGhhbmtzLg0KPiANCg0KLS0gDQpNYXJjIFBldGl0
LUh1Z3VlbmluDQpFbWFpbDogbWFyY0BwZXRpdC1odWd1ZW5pbi5vcmcNCkJsb2c6IGh0dHBzOi8v
bWFyYy5wZXRpdC1odWd1ZW5pbi5vcmcNClByb2ZpbGU6IGh0dHBzOi8vd3d3LmxpbmtlZGluLmNv
bS9pbi9wZXRpdGh1Zw0KDQo=


From nobody Sun Mar 11 06:55:34 2018
Return-Path: <marc@petit-huguenin.org>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC163126D05; Sun, 11 Mar 2018 06:55:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.108
X-Spam-Level: 
X-Spam-Status: No, score=-1.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A25aYAUy_WSx; Sun, 11 Mar 2018 06:55:19 -0700 (PDT)
Received: from implementers.org (unknown [92.243.22.217]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AF311201FA; Sun, 11 Mar 2018 06:55:19 -0700 (PDT)
Received: from [IPv6:2601:648:8301:730f:ac0b:c7cc:59a:561f] (unknown [IPv6:2601:648:8301:730f:ac0b:c7cc:59a:561f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id CA1C3AE8D9; Sun, 11 Mar 2018 14:55:16 +0100 (CET)
To: Matthew Miller <linuxwolf+ietf@outer-planes.net>, secdir@ietf.org
Cc: draft-ietf-tram-stunbis.all@ietf.org, ietf@ietf.org, tram@ietf.org
References: <152063220998.11155.12669577501214588133@ietfa.amsl.com>
From: Marc Petit-Huguenin <marc@petit-huguenin.org>
Message-ID: <a9a7c497-3815-f022-f9a9-2fe53d3394f5@petit-huguenin.org>
Date: Sun, 11 Mar 2018 06:55:13 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <152063220998.11155.12669577501214588133@ietfa.amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="JepqGcMYKMNSj0OfaJE8H9s7Wn8JeDWtk"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/a-u39QZo5NAxw6vR68vvOvF_2yg>
Subject: Re: [tram] Secdir last call review of draft-ietf-tram-stunbis-16
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Mar 2018 13:55:21 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--JepqGcMYKMNSj0OfaJE8H9s7Wn8JeDWtk
Content-Type: multipart/mixed; boundary="nVlF3NljHW3Z231NkszQLrPd5dwYgVMIX";
 protected-headers="v1"
From: Marc Petit-Huguenin <marc@petit-huguenin.org>
To: Matthew Miller <linuxwolf+ietf@outer-planes.net>, secdir@ietf.org
Cc: draft-ietf-tram-stunbis.all@ietf.org, ietf@ietf.org, tram@ietf.org
Message-ID: <a9a7c497-3815-f022-f9a9-2fe53d3394f5@petit-huguenin.org>
Subject: Re: Secdir last call review of draft-ietf-tram-stunbis-16
References: <152063220998.11155.12669577501214588133@ietfa.amsl.com>
In-Reply-To: <152063220998.11155.12669577501214588133@ietfa.amsl.com>

--nVlF3NljHW3Z231NkszQLrPd5dwYgVMIX
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Hi,

Thanks for the review.

Please see inline.

On 03/09/2018 01:50 PM, Matthew Miller wrote:
> Reviewer: Matthew Miller
> Review result: Has Issues
>=20
> [ I realize how unfortunate it is this arrives well past last call.
> I beg forgiveness and ask that you accept the comments as you would
> have if they arrived on time. ]
>=20
> I have reviewed this document as part of the security directorate's
> ongoing effort to review all IETF documents being processed by the
> IESG.  These comments were written primarily for the benefit of the
> security area directors.  Document editors and WG chairs should
> treat these comments just like any other last call comments.
>=20
> Document: draft-ietf-stunbis-16
> Reviewer: Matthew A. Miller
> Review Date: 2018-03-07
> IETF LC End Date: 2018-02-20
> IESG Telechat date: 2018-04-05
>=20
> Summary:  This document obsoletes 5389, adding some protection to
> downgrade attacks against message integrity usage, as well
> incorporating DTLS (over UDP).
>=20
> The document is mostly ready, but there are a couple of issues I
> have.
>=20
> Major Issues: N/A
>=20
> Minor Issues:
>=20
> * I am wondering why a more robust password algorithm (key derivation
> function) was not defined (e.g., HKDF-SHA-256) instead of or in additio=
n
> to, a simple salted "SHA-256" hash.  Some amount of parameterization is=

> accounted for in the PASSWORD-ALGORITHM/S attributes.  I think it is
> perfectly fair and appropriate to take this issue as "asking for a quic=
k
> rationale (that maybe ought to be highlighted better in the document)"
> over "use a real key derivation function".

We proposed other algorithms to the Working Group but there was no consen=
sus past using what we have today in the draft.

We basically wanted to keep STUN aligned with HTTP Digest and SIP Digest =
as much as possible.  Rereading both RFC 7616 and draft-yusef-sipcore-dig=
est-scheme I can not find mention of using a key derivation function for =
these.

Can you explain how that could be used with STUN (and potentially with HT=
PP and SIP)?

>=20
> * The description for 17.5.1. "MD5" list the key size as 20 bytes, but =
the
> hash length of MD5 is 16 bytes (128 bits).  I think this is merely a ty=
po,
> since the purpose appears to be for backwards compatibility with existi=
ng
> systems.

Fixed.

>=20
> * Both 17.5.1.1. "MD5" Section 9.2.2. "HMAC Key" (long-term credential)=

> and Section appear to define the same functional algorithm, but with su=
btle
> syntax differences.  As far as I can tell, they are actually the same
> algorithm; would it not be acceptable to have Section 9.2.2 point to
> Section 17.5.1.1 for the algorithm description?
>=20
>=20

This is going into the IANA registry so I left things there.  I fixed the=
 discrepancy with section 9.2.2.

I also fixed the definition of the key for SHA-256, which must use Opaque=
String for the realm.

--=20
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: https://marc.petit-huguenin.org
Profile: https://www.linkedin.com/in/petithug


--nVlF3NljHW3Z231NkszQLrPd5dwYgVMIX--

--JepqGcMYKMNSj0OfaJE8H9s7Wn8JeDWtk
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEBSI+IuCHU8MsI1GjKcRFldZqfsQFAlqlNUIACgkQKcRFldZq
fsSGAA/+J/rGXho5aa1HwPjD67QM/HQ6BULBFP/JCJJs/NY01GYx9dfoH+Ao6PWV
b988bkqIsGB1j/B3fr+67gJ8keK8Gq/Ymv6H5ino5ZU4kz9IpSWDx/QWzxMKNnWd
gx16Kbr6HxXu4wB+C31Kr2rLNO9bLZ6Qqy8sGNfeXY6UpmhH0aNvD9JFkDVjNESc
kqdbxe2PqROW2m1e9WimLrL8nfbQhkiy+69lX8JGvPG/sJm+YY+b6HzBuzZ4wQz1
DpN1shc6NzC1CBHD8ucz9MliE9hXNW6lvzR5fdlt8x35BeyPcIdPiZyYsj6Cm95W
fyPil0oRFvREEM9Ed1C7wO7YcEMPeVMxA59KySqwEMoCmhOYt00cS4X9CSDkBeCE
36hzDjicDFShkTljutFT2BFEPNTjQjudCzROn9kmNfdSJQvpOpbfSgm6idBFrIuM
KZ+NhiqX8mWkHiwdY2IshxsDtL1VW6yQntBR2EGjZASwTI+pIKMTlMFzcSY3oEH4
RCV96WQa9MIOZm76iGJnWB6lpaGKCWZaPWmJn5MgNb4hCSiCtk0TflErLSv0t2+j
WLDfJ88YFZKIUpwSh+jIFG4ev1WhGLRKD0BL/GOqcMMklTcX1PTe+d/GQbV8rFNV
DQUjPaHLUfAJr3dIiW7L9f2M50ctOyx6Gu/wea8KRU9sgpazWsg=
=S3Pm
-----END PGP SIGNATURE-----

--JepqGcMYKMNSj0OfaJE8H9s7Wn8JeDWtk--


From nobody Sun Mar 11 20:00:37 2018
Return-Path: <torii0573@gmail.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 212DB1243F6; Sun, 11 Mar 2018 20:00:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.643
X-Spam-Level: 
X-Spam-Status: No, score=-0.643 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, LOCALPART_IN_SUBJECT=1.107, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AbkswN-TneVw; Sun, 11 Mar 2018 20:00:34 -0700 (PDT)
Received: from mail-ot0-x229.google.com (mail-ot0-x229.google.com [IPv6:2607:f8b0:4003:c0f::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E2C41200A0; Sun, 11 Mar 2018 20:00:34 -0700 (PDT)
Received: by mail-ot0-x229.google.com with SMTP id f11so13869756otj.12; Sun, 11 Mar 2018 20:00:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gnXBHwpS5YyFFMWWdup8zcHuMbaEE1CH3ggiyvhqDco=; b=mHDW6Gx7quIjInG0e8txnP9Gcptt2Rdv/C8jWUuvI1nboGb2whBHJJ98A8lZqJAVFy fTc7/78pFlMPTmIlBv3kjJ/Onn5nFYEUAJo/u3dVPTRYVKy/vBxzcH5t0a2exWwuaPpb +q3cQMdo4GM1WgWhlhrQBVz52hoVpV3F3OxBPBOSqCPCx1nF5fgDV5OOP/rJE3KGqd09 LrCkY6+PiTyizEb3VLyB9KQtSHJlrEYNDv5rEAQ9dOLIwNi9ISXpeYXcJvP24VFG0oOJ c5zYDTc0jE2ftNb2tiFSnZQYDvrD/NrOLf+syS63oSorEwBBFamDW9t4f/fuE1ZJ3ZCx 5Gjw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=gnXBHwpS5YyFFMWWdup8zcHuMbaEE1CH3ggiyvhqDco=; b=qL4jx8sgoWoet4npf+zB8Y8uU1i9+vjYdVBO3MPxjpOaBgitpqHumEgHE9f9ZDoJTv E7bC0NeM226LpdPuhEiuBZx1EkgcLZ88So5NTKkVse+bx7/7rWlSDTyK6ScKSn6L0CB0 C5OQvrmhym0+KklroqxUWh3Yb4LX1GKD4JvcPXykGtSi324ite/imwasjV82gDBepLod d3/nHK59Oa/YWA1pQpGLuwN+Q173e6UQNIsQvG8vG9HzxhYAlU5YRraNjP1l8XHeFUN5 60We9BKuG+GNEvMlUi+3RsLN5UWu0qbPpQ3rmEtmJH2awaUeGLta/Czaq2g/0xn2EHHa qUcA==
X-Gm-Message-State: AElRT7G9mfuMT5TiKvoF4d1GODBba+dvmrH/d+yRMDoWQqWXeYkpJ/78 2rdD6CYHxLX4yOp/PL9hAMIGdP8HRIm4lx0MasyahSy0
X-Google-Smtp-Source: AG47ELtAvU4wOxoW8AnjxrCJMP9Y1vt3kpY/z7SqtrDcYBVe43Qw08U+NYt+21CdoNOkG05Ha2Y4zay8+CI/hXdesUs=
X-Received: by 10.157.83.201 with SMTP id i9mr4224246oth.401.1520823633489; Sun, 11 Mar 2018 20:00:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.67.77 with HTTP; Sun, 11 Mar 2018 20:00:33 -0700 (PDT)
In-Reply-To: <9b5529b3-5d0d-e6a6-9481-a947a890acc3@petit-huguenin.org>
References: <CABEjbRJjU2LVb0iDkBavpSxtw-+PowvsyDdg9hhvwX+Gi9Awzw@mail.gmail.com> <9b5529b3-5d0d-e6a6-9481-a947a890acc3@petit-huguenin.org>
From: Noriyuki Torii <torii0573@gmail.com>
Date: Mon, 12 Mar 2018 12:00:33 +0900
Message-ID: <CABEjbRKec0Ro51sedo_MU41YLyhm68xbkBm65DaVG9BiBn+5Yw@mail.gmail.com>
To: draft-ietf-tram-stunbis@ietf.org
Cc: tram@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/x1CSljQKmWIdhtnm_sBJNKrBNbo>
Subject: Re: [tram] draft-ietf-tram-stunbis
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Mar 2018 03:00:36 -0000

Hi, Marc

Thank you for your consideration and response.

> I gave you an answer to that last time, but you did not responded to it.  Again, here's the email that justify these values:
>
> https://www.ietf.org/mail-archive/web/behave/current/msg02535.html
>
> Please give arguments why that answer is wrong.

Unfortunately I haven't received your previous "answer" email at this point yet.
(maybe delivery problem?)
Therefore I'm sorry to say but the following comment is not taken into account
your "answer".

Anyway, the email you cited says

> UTF-8 encoded sequence of less than 128 characters is up to
> (128-1)*6+1=763 bytes, counting the terminating nul

here +1 is intended as a extra room for the terminating nul.

But such a nul is just a implementation requirement for some programming
languages.
As far as my understandings, both UTF-8 and PRECIS OpaqueString specification
don't require that the nul termination of the string.
(If my understanding is wrong, please can anyone correct abobe)

Each STUN attributes have its own length field therefore the implementation
can detect the end of the string without the terminating nul. So IMHO, such a
consideration on an extra room for the terminating nul is not necessarily
needed as the STUN specification.
This is why the comment I submitted prevously.

---

Additionally, I found one more point in section 9.2.4.

>       *  If the request contains neither PASSWORD-ALGORITHMS nor
>          PASSWORD- ALGORITHM, then the request is processed as though
>          PASSWORD- ALGORITHM were MD5 (Note that if the original
>          PASSWORD-ALGORITHMS attribute did not contain MD5, this will
>          result in a 400 Bad Request in a later step below).
>
>       *  Otherwise, unless (1) PASSWORD-ALGORITHM and PASSWORD-
>          ALGORITHMS are both present, (2) PASSWORD-ALGORITHMS matches
>          the value sent in the response that sent this NONCE, and (3)
>          PASSWORD-ALGORITHM matches one of the entries in PASSWORD-
>          ALGORITHMS, the server MUST generate an error response with an
>          error code of 400 (Bad Request).

The first '*' paragraph says

> (Note that if the original
>          PASSWORD-ALGORITHMS attribute did not contain MD5, this will
>          result in a 400 Bad Request in a later step below).
>

But the second '*' paragraph starts with "Otherwise".

So if really "the request contains neither PASSWORD-ALGORITHMS nor PASSWORD-
ALGORITHM", then the second '*' check will be skipped as a whole and the
400 Bad Request will be never generated, whether or not "the original
PASSWORD-ALGORITHMS attribute did not contain MD5".

I guess it would be preferable something like below.

      *  If the request contains neither PASSWORD-ALGORITHMS nor
         PASSWORD-ALGORITHM, then the request is processed as though
         PASSWORD-ALGORITHMS was identical to the value sent in the
         response that was sent this NONCE and PASSWORD-ALGORITHM was MD5.
         Otherwise, unless PASSWORD-ALGORITHM and PASSWORD-ALGORITHMS are
         both present, the server MUST generate an error response with
         an error code of 400 (Bad Request).
         (Note that if the original PASSWORD-ALGORITHMS attribute did not
         contain MD5, this will result in a 400 Bad Request in a later
         step below).

      *  Unless (1) PASSWORD-ALGORITHMS matches the value sent in the
         response that sent this NONCE, and (2)PASSWORD-ALGORITHM matches
         one of the entries in PASSWORD-ALGORITHMS, the server MUST
         generate an error response with an error code of 400 (Bad Request).

Best regards,
Noriyuki Torii

2018-03-11 22:26 GMT+09:00 Marc Petit-Huguenin <marc@petit-huguenin.org>:
> Hi,
>
> Thanks for the review, please see inline.
>
> Note that the draft submission tool will reopen on 2018-03-18, so no new version of this draft will be published before that.
>
> On 03/07/2018 04:10 AM, Noriyuki Torii wrote:
>> To whom it may concern.
>>
>> I'm Noriyuki Torii. I have red the updated I-D of STUNbis-16 and found
>> some issues would like to be shared.
>>
>> Hope this may help for improvement.
>>
>> - Section 9.1.1 and 9.2.2 defines the HMAC key calculation based on some
>>   elements such that the password, username and realm.
>>   Sections say those elements should be proccessed using OpaqueString
>> profile
>>   defined in RFC8265.
>>
>>   On the other hand, RFC8265 says in its "Changes from RFC 7613" that
>>      "Removed UTF-8 as a mandatory encoding, because that is a matter
>>       for the application."
>>
>>   So, the specification of applied encoding for those elements on
>> calculating
>>   HMAC key is up to STUNbis document.
>>
>>   Please note that username and realm have the applied encoding
>> specification
>>   as UTF-8 in its corresponding STUN attribute description.
>>   (please see section 14.3 and 14.9)
>>   But the password doesn't have such a description, therefore some care need
>>   to be taken.
>
> Section 9.1.1 and 9.2.2 now have the following text:
>
>    For short-term credentials the HMAC key is defined as follow:
>
>                        key = OpaqueString(password)
>
>    where the OpaqueString profile is defined in [RFC8265].  The encoding
>    used is UTF-8 [RFC3629].
>
> [...]
>
>    For long-term credentials that do not use a different algorithm, as
>    specified by the PASSWORD-ALGORITHM attribute, the key is 16 bytes:
>
>   key = MD5(username ":" OpaqueString(realm) ":" OpaqueString(password))
>
>    Where MD5 is defined in [RFC1321] and the OpaqueString profile is
>    defined in [RFC8265].  The encoding used is UTF-8 [RFC3629].
>
>>
>> - Section 14.6 mentions to the HMAC truncation, but as far as I read, I
>>   couldn't precisely find out the minimum byte of length of the HMAC.
>>
>>   From my understandings, minimum length
>>   maybe 16 because
>>   > The HMAC MUST NOT be truncated below a minimum size of 16 bytes.
>>
>>   OR
>>   maybe 8 because
>>   > The value (snip) MUST be a positive multiple of 4 bytes
>>     AND
>>   > STUN Usages may specify a minimum length longer than 4 bytes.
>>
>>   Here above I conceived "longer than (but not equal to) 4 bytes".
>>   IMHO, some clarification will be preferable.
>
> I removed the last sentence of the paragraph, which did not make sense.
>
>>
>> - There are some occurence such like
>>    > a UTF-8 [RFC3629] encoded
>>    > sequence of less than 128 characters (which can be as long as 509
>>    > bytes when encoding them or 763 bytes when decoding them).
>>
>>    The sentence inside parenthesis have off-by-one error.
>>    To be exact,
>>
>>    (which can be less than 509 bytes when encoding them or 763 bytes
>>    when decoding them)
>>
>>    or alternatively
>>
>>    (which can be as long as 508 bytes when encoding them or 762 bytes
>>    when decoding them)
>
> I gave you an answer to that last time, but you did not responded to it.  Again, here's the email that justify these values:
>
> https://www.ietf.org/mail-archive/web/behave/current/msg02535.html
>
> Please give arguments why that answer is wrong.
>
>>
>> - In Section 9.2.4, there are some typoes.
>>   Unnecessary extra white space such that "PASSWORD- ALGORITHM".
>
> Fixed.
>
>>
>> - At page 40, bizzare (perhaps unintended) page break occurs.
>
> Fixed.
>
> --
> Marc Petit-Huguenin
> Email: marc@petit-huguenin.org
> Blog: https://marc.petit-huguenin.org
> Profile: https://www.linkedin.com/in/petithug
>


From nobody Mon Mar 12 00:10:12 2018
Return-Path: <torii0573@gmail.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C24B61204DA; Mon, 12 Mar 2018 00:10:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.643
X-Spam-Level: 
X-Spam-Status: No, score=-0.643 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, LOCALPART_IN_SUBJECT=1.107, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id irWJC-jePXE1; Mon, 12 Mar 2018 00:10:09 -0700 (PDT)
Received: from mail-ot0-x242.google.com (mail-ot0-x242.google.com [IPv6:2607:f8b0:4003:c0f::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75B231241F5; Mon, 12 Mar 2018 00:10:09 -0700 (PDT)
Received: by mail-ot0-x242.google.com with SMTP id l5so14237820otf.9; Mon, 12 Mar 2018 00:10:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to:cc; bh=OxEC32fhWI3HWU9XvXrMtutxvDYUEGcipEU2jARNYBw=; b=bg2bWvIXchnSGfX+K5chzzjTLOdcgHKs/imiFy2L/yCwvXRPSr7i/Qz2yhyWCqoSxt V2jV2wil+NcxnJ+KUZwl94KJKa4ojlNSSSlmikw1OCpWGAzy4jeJrjd87II/KxRBhu0J +0j0ZLtT7j1VjhZ98fhpmfooyZXCe/RyQ9DyWor/wg8g1dfdKHXzP4k6bNJU946xun+p 0iw4FFDbBTTdC9AoPw1dSflz2Qym2KvOV90L7hLUO+AWmubjabH61yZcQuyJdbSqUa9o kZCstANGw87qCTFGguRN99jhqTeBotHCqqULGNHPV8pNOjBTgCJM31PUkL7WbbXJU+vJ G5+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=OxEC32fhWI3HWU9XvXrMtutxvDYUEGcipEU2jARNYBw=; b=enT87rDFTghtKPVQSaIv6kijQWk6N7Od8eg0DS2UMTXtfJ3x6NV7N7y+LQRAFshcjK 6Z1N+lbmHpS6ebb+qF2ndbQuXyP4lCucpkiiGP2JQlTFxlH08VkZWlEVkuHKBDeSkc8E UrBHiMEt5BVCfbgIv1Bo9MNK5qW2RQa0cF4lSB1WpefWg3g4wFxpKtVZgguqczV3wSVt LBhBi+8PNHfzbweRYHcDYerdP96b5vTh69HlpLVW1zwnOqtwxtJjbTN/8fcLUlWPvrew FW0boumm7pTUUUQC2HIn51F+8qF4m5BHAJkR6BBp3QhLOnT4ZwJzxbCq3/NrNTbdhFjp /73Q==
X-Gm-Message-State: AElRT7HqAJJgtk8//ZuvrJ+7yCwoD1C+eJMLn9Mh7yHwHE8jZP/D1yCJ /tQafbWT5Z4D+9foJp/nKyR82jPkGZih0si6FVxDZeGm
X-Google-Smtp-Source: AG47ELtUOOpGdsIECq6Q9MCWpPimIqUyiFcX3wvpANfg58uQq/8pXgPovCMbZRWYtQKugJZbvKai7Ld6lP/bsB+GuT0=
X-Received: by 10.157.49.123 with SMTP id v56mr4545055otd.389.1520838608689; Mon, 12 Mar 2018 00:10:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.67.77 with HTTP; Mon, 12 Mar 2018 00:10:08 -0700 (PDT)
From: Noriyuki Torii <torii0573@gmail.com>
Date: Mon, 12 Mar 2018 16:10:08 +0900
Message-ID: <CABEjbRKS04Wx-L3eKJBNFbsNywZe_19X2NY++3NSovr_3viJWg@mail.gmail.com>
To: draft-ietf-tram-turnbis@ietf.org
Cc: tram@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/rUODOwDwaZSVJwsiXaUA0BlTY40>
Subject: [tram] draft-ietf-tram-turnbis
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Mar 2018 07:10:11 -0000

To whom it may concern.

I found some discrepancies in the draft-ietf-tram-turnbis-14.
Hope this may help for improvement.

- Section 12 defines the allowed channel numbers as below,

 >      0x4000 through 0x7FFF: These values are the allowed channel
 >      numbers (16,384 possible values).

 but the RFC 7983 shrinks the valid range of channel number to 0x4000 - 0x4FFF.
 Please see also
 https://www.iana.org/assignments/stun-parameters/stun-parameters.xhtml#turn-channel

- STUNbis specification requires that PASSWORD-ALGORITHMS and PASSWORD-
  ALGORITHM attributes are both present or neither not present in each
  request, from my understandings.
  If so, the section 18 needs refinements to reflect the above requirement,
  because some example requests shown in the current document only have
  PASSWORD-ALGORITHM and doesn't have PASSWORD-ALGORITHMS.

Best regards,

Noriyuki Torii


From nobody Mon Mar 12 06:36:13 2018
Return-Path: <TirumaleswarReddy_Konda@mcafee.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A09E124B0A; Mon, 12 Mar 2018 06:36:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mcafee.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MtUsVdwwITu9; Mon, 12 Mar 2018 06:36:11 -0700 (PDT)
Received: from DNVWSMAILOUT1.mcafee.com (dnvwsmailout1.mcafee.com [161.69.31.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 486C9127599; Mon, 12 Mar 2018 06:36:08 -0700 (PDT)
X-NAI-Header: Modified by McAfee Email Gateway (5500)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mcafee.com; s=s_mcafee; t=1520861757; h=From: To:CC:Subject:Thread-Topic:Thread-Index:Date: Message-ID:References:In-Reply-To:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: dlp-product:dlp-version:dlp-reaction:authentication-results: x-originating-ip:x-ms-publictraffictype:x-microsoft-exchange-diagnostics: x-ms-exchange-antispam-srfa-diagnostics:x-ms-office365-filtering-correlation-id: x-microsoft-antispam:x-ms-traffictypediagnostic: x-microsoft-antispam-prvs:x-exchange-antispam-report-test: x-exchange-antispam-report-cfa-test:x-forefront-prvs: x-forefront-antispam-report:received-spf:x-microsoft-antispam-message-info: spamdiagnosticoutput:spamdiagnosticmetadata: Content-Type:Content-Transfer-Encoding:MIME-Version: X-MS-Exchange-CrossTenant-Network-Message-Id: X-MS-Exchange-CrossTenant-originalarrivaltime: X-MS-Exchange-CrossTenant-fromentityheader: X-MS-Exchange-CrossTenant-id:X-MS-Exchange-Transport-CrossTenantHeadersStamped: X-OriginatorOrg:X-NAI-Spam-Flag:X-NAI-Spam-Threshold: X-NAI-Spam-Score:X-NAI-Spam-Version; bh=7 Eid7M6+kz46Lm0Ce7dkfPeQdPgWmaXqxxwXQYCW0Y I=; b=J+Vy/cuuSEQyBUWQjs9dfBbiohKKWLXYMu7ZSM8DG4mZ CFAbmmR7I4PPaDgsJPJcFFdwnXkVUrpZ7sfeFjLabFgIG/ueKE SI44O79k9kqmaLoW/lUcKiGD2vE8xIJ7EYQcod72jQOQ9u60Ij eu9Mlk5xzjUU2vlWtiUmeeztvuc=
Received: from DNVEXAPP1N04.corpzone.internalzone.com (unknown [10.44.48.88]) by DNVWSMAILOUT1.mcafee.com with smtp (TLS: TLSv1/SSLv3,256bits,ECDHE-RSA-AES256-SHA384) id 5b62_e454_d6acaa13_ba8c_48f7_8d87_1f397cef373a; Mon, 12 Mar 2018 08:35:56 -0500
Received: from DNVEXAPP1N04.corpzone.internalzone.com (10.44.48.88) by DNVEXAPP1N04.corpzone.internalzone.com (10.44.48.88) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Mon, 12 Mar 2018 07:35:01 -0600
Received: from DNVO365EDGE2.corpzone.internalzone.com (10.44.176.74) by DNVEXAPP1N04.corpzone.internalzone.com (10.44.48.88) with Microsoft SMTP Server (TLS) id 15.0.1347.2 via Frontend Transport; Mon, 12 Mar 2018 07:35:01 -0600
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (10.44.176.242) by edge.mcafee.com (10.44.176.74) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Mon, 12 Mar 2018 07:34:55 -0600
Received: from BN6PR16MB1425.namprd16.prod.outlook.com (10.172.207.19) by BN6PR16MB1617.namprd16.prod.outlook.com (10.172.27.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.567.12; Mon, 12 Mar 2018 13:34:54 +0000
Received: from BN6PR16MB1425.namprd16.prod.outlook.com ([10.172.207.19]) by BN6PR16MB1425.namprd16.prod.outlook.com ([10.172.207.19]) with mapi id 15.20.0567.018; Mon, 12 Mar 2018 13:34:54 +0000
From: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>
To: Noriyuki Torii <torii0573@gmail.com>, "draft-ietf-tram-turnbis@ietf.org" <draft-ietf-tram-turnbis@ietf.org>
CC: "tram@ietf.org" <tram@ietf.org>
Thread-Topic: [tram] draft-ietf-tram-turnbis
Thread-Index: AQHTudE4Fs843+xF7k+BrOpFdbSpHaPMmH3A
Date: Mon, 12 Mar 2018 13:34:54 +0000
Message-ID: <BN6PR16MB1425EF492922CE97B6CF256CEAD30@BN6PR16MB1425.namprd16.prod.outlook.com>
References: <CABEjbRKS04Wx-L3eKJBNFbsNywZe_19X2NY++3NSovr_3viJWg@mail.gmail.com>
In-Reply-To: <CABEjbRKS04Wx-L3eKJBNFbsNywZe_19X2NY++3NSovr_3viJWg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 11.0.200.100
dlp-reaction: no-action
authentication-results: spf=none (sender IP is ) smtp.mailfrom=TirumaleswarReddy_Konda@McAfee.com; 
x-originating-ip: [122.172.98.95]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR16MB1617; 7:4fXa6NIegeq1xmPMkJ+OxUwrMfbuqykhMgR8fGst1EAAvVw0xyB7gTRnZ4KULNoZiog/szwRZJ3k9JwSU5VQbSsk85uUH58gST6r2JpBZXZ0kagy/RuyZBczdJssbf27eadWHw0w5CIb/BCatGdp+wP6sDuyr5BBiJRhqupLhEWOhI4BrGeLqOaGnZOpIKvpd/Py+cJES47ynO5oidjvTaVtsVZZY2e8CdD+HwnYphJtlR6Q3c4rZqX1F/J70ddn
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 1ac1003f-39f5-4965-fccc-08d5881e0a1b
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BN6PR16MB1617; 
x-ms-traffictypediagnostic: BN6PR16MB1617:
x-microsoft-antispam-prvs: <BN6PR16MB1617A1A267068D8A7EBD8CCBEAD30@BN6PR16MB1617.namprd16.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(1591387915157);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3002001)(93006095)(93001095)(10201501046)(3231220)(944501244)(52105095)(6041310)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123560045)(20161123558120)(6072148)(201708071742011); SRVR:BN6PR16MB1617; BCL:0; PCL:0; RULEID:; SRVR:BN6PR16MB1617; 
x-forefront-prvs: 06098A2863
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(39860400002)(39380400002)(346002)(376002)(396003)(32952001)(199004)(189003)(13464003)(2501003)(3280700002)(106356001)(229853002)(39060400002)(3660700001)(4326008)(25786009)(76176011)(66066001)(6246003)(55016002)(7696005)(6436002)(9686003)(3846002)(6116002)(2906002)(6306002)(105586002)(97736004)(99286004)(80792005)(2950100002)(53936002)(7736002)(305945005)(8936002)(81166006)(68736007)(5660300001)(33656002)(551544002)(81156014)(186003)(8676002)(74316002)(14454004)(478600001)(2900100001)(966005)(316002)(110136005)(53546011)(6506007)(59450400001)(72206003)(102836004)(26005)(77096007)(86362001)(85282002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR16MB1617; H:BN6PR16MB1425.namprd16.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: McAfee.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: MEsE5kEktmzJksboXhwwOQicKGJ1Pm0Tew9wqYKg3GJ55Io9j25zLlcQSC0me8dGWxhEdvMoF32xTQthEyOZUgGlLPJyjB2Ysjno6ZfWEBHTGF+7T0Tqxy3anA/Q0+UXR5CQhNI2b+/TXjGGdjpWJwrWsEjuTHSGVj+Kqx1Bqzq0mx5SOzHH6b9uBsZKnguRA+hcbhp3GIzymm5vaIVddrl055WYMM7uajCXPre2wz/NkaHgP1+hyRn9u3L11rZ6feJ/4/wv+hsf5DxSjJ9EphA0SDIpyBBGJnhRAVTecmHxgs8KBavxpTWxbtSQRy4YLucoLpqeKI8vA2bl9tJD8Q==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 1ac1003f-39f5-4965-fccc-08d5881e0a1b
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Mar 2018 13:34:54.0894 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4943e38c-6dd4-428c-886d-24932bc2d5de
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR16MB1617
X-OriginatorOrg: mcafee.com
X-NAI-Spam-Flag: NO
X-NAI-Spam-Threshold: 15
X-NAI-Spam-Score: 0
X-NAI-Spam-Version: 2.3.0.9418 : core <6240> : inlines <6476> : streams <1781179> : uri <2606896>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/w0gF7DwL5XEKyzUGuRwJmWKNZuU>
Subject: Re: [tram] draft-ietf-tram-turnbis
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Mar 2018 13:36:12 -0000

> -----Original Message-----
> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Noriyuki Torii
> Sent: Monday, March 12, 2018 12:40 PM
> To: draft-ietf-tram-turnbis@ietf.org
> Cc: tram@ietf.org
> Subject: [tram] draft-ietf-tram-turnbis
>=20
> To whom it may concern.
>=20
> I found some discrepancies in the draft-ietf-tram-turnbis-14.
> Hope this may help for improvement.
>=20
> - Section 12 defines the allowed channel numbers as below,
>=20
>  >      0x4000 through 0x7FFF: These values are the allowed channel
>  >      numbers (16,384 possible values).
>=20
>  but the RFC 7983 shrinks the valid range of channel number to 0x4000 -
> 0x4FFF.
>  Please see also
>  https://www.iana.org/assignments/stun-parameters/stun-
> parameters.xhtml#turn-channel

Thanks, fixed.=20

>=20
> - STUNbis specification requires that PASSWORD-ALGORITHMS and
> PASSWORD-
>   ALGORITHM attributes are both present or neither not present in each
>   request, from my understandings.
>   If so, the section 18 needs refinements to reflect the above requiremen=
t,
>   because some example requests shown in the current document only have
>   PASSWORD-ALGORITHM and doesn't have PASSWORD-ALGORITHMS.

Section 18 discusses both PASSWORD-ALGORITHM and PASSWORD-ALGORITHMS (sent =
in Allocate error response).=20

-Tiru

>=20
> Best regards,
>=20
> Noriyuki Torii
>=20
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram


From nobody Mon Mar 12 09:02:20 2018
Return-Path: <brandon.williams@akamai.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B387127599; Mon, 12 Mar 2018 09:02:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l0K3bTqrSEz5; Mon, 12 Mar 2018 09:02:17 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDD98126DED; Mon, 12 Mar 2018 09:02:17 -0700 (PDT)
Received: from pps.filterd (m0122331.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w2CFvXDM024846; Mon, 12 Mar 2018 16:02:16 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=subject : to : cc : references : from : message-id : date : mime-version : in-reply-to : content-type : content-transfer-encoding; s=jan2016.eng; bh=GjY3HZNCxY18q4ZkpihNhG7kS8RTcnSv285UdA9j9tY=; b=aRhygvrU+TbAd6lwYtoUYNx6T0Hu92FisxeRRN0n0XoY8u9ugA6HpLl/5gswDClKxlri HMAdT6y7zHz8H4p25Bi8F9iyZF/GL3dNrA5CIdBflO6z2481+J8URA53zCCgHbeuaYCf mWpVcPxfqWF5q7m3xkNRhswHxZXOpnh7LQVe++hs+AiM8w11KjMfLFbiD3GHQtjMxpnu hIqTwG4tYhWLE/MTSTbWGAgY8lLecD2WZ3axHNnc/GKvwqgIVaYu2xqiPWVDwkscbPno z7X5hybbVoUqvn5XPsbMlRLVHnLX3MJHrlaJU+pn+BWPPft/a9lkm7vjvMLbYn8DroLF MQ== 
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19]) by mx0b-00190b01.pphosted.com with ESMTP id 2gm53vwdsq-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 12 Mar 2018 16:02:15 +0000
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w2CG1Aif032126; Mon, 12 Mar 2018 12:02:15 -0400
Received: from prod-mail-relay11.akamai.com ([172.27.118.250]) by prod-mail-ppoint2.akamai.com with ESMTP id 2gmbjypdbp-1; Mon, 12 Mar 2018 12:02:15 -0400
Received: from [172.28.118.62] (bowill.kendall.corp.akamai.com [172.28.118.62]) by prod-mail-relay11.akamai.com (Postfix) with ESMTP id 09165336E4; Mon, 12 Mar 2018 16:02:15 +0000 (GMT)
To: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>, Noriyuki Torii <torii0573@gmail.com>, "draft-ietf-tram-turnbis@ietf.org" <draft-ietf-tram-turnbis@ietf.org>
Cc: "tram@ietf.org" <tram@ietf.org>
References: <CABEjbRKS04Wx-L3eKJBNFbsNywZe_19X2NY++3NSovr_3viJWg@mail.gmail.com> <BN6PR16MB1425EF492922CE97B6CF256CEAD30@BN6PR16MB1425.namprd16.prod.outlook.com>
From: Brandon Williams <brandon.williams@akamai.com>
Message-ID: <ca9334ec-aa8c-55bd-3180-7086cd21952c@akamai.com>
Date: Mon, 12 Mar 2018 12:02:11 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <BN6PR16MB1425EF492922CE97B6CF256CEAD30@BN6PR16MB1425.namprd16.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-12_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803120183
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-12_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803120182
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/PP8ygYihP-LWhlThvvkf-h7loNw>
Subject: Re: [tram] draft-ietf-tram-turnbis
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Mar 2018 16:02:19 -0000

Hi Tiru,

I think that Torii's point is that according to stunbis section 9.2.5 a 
request that contains PASSWORD-ALGORITHM will also contain 
PASSWORD-ALGORITHMS, echoing back the value contained in the response. 
The example in section 18 does not show this.

--Brandon

On 03/12/2018 09:34 AM, Konda, Tirumaleswar Reddy wrote:
>> -----Original Message-----
>> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Noriyuki Torii
>> Sent: Monday, March 12, 2018 12:40 PM
>> To: draft-ietf-tram-turnbis@ietf.org
>> Cc: tram@ietf.org
>> Subject: [tram] draft-ietf-tram-turnbis
>>
>> To whom it may concern.
>>
>> I found some discrepancies in the draft-ietf-tram-turnbis-14.
>> Hope this may help for improvement.
>>
>> - Section 12 defines the allowed channel numbers as below,
>>
>>   >      0x4000 through 0x7FFF: These values are the allowed channel
>>   >      numbers (16,384 possible values).
>>
>>   but the RFC 7983 shrinks the valid range of channel number to 0x4000 -
>> 0x4FFF.
>>   Please see also
>>   https://www.iana.org/assignments/stun-parameters/stun-
>> parameters.xhtml#turn-channel
> 
> Thanks, fixed.
> 
>>
>> - STUNbis specification requires that PASSWORD-ALGORITHMS and
>> PASSWORD-
>>    ALGORITHM attributes are both present or neither not present in each
>>    request, from my understandings.
>>    If so, the section 18 needs refinements to reflect the above requirement,
>>    because some example requests shown in the current document only have
>>    PASSWORD-ALGORITHM and doesn't have PASSWORD-ALGORITHMS.
> 
> Section 18 discusses both PASSWORD-ALGORITHM and PASSWORD-ALGORITHMS (sent in Allocate error response).
> 
> -Tiru
> 
>>
>> Best regards,
>>
>> Noriyuki Torii
>>
>> _______________________________________________
>> tram mailing list
>> tram@ietf.org
>> https://www.ietf.org/mailman/listinfo/tram
> 
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram
> 


From nobody Mon Mar 12 17:05:43 2018
Return-Path: <torii0573@gmail.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28CBF124F57; Mon, 12 Mar 2018 17:05:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LLPXz9enec4u; Mon, 12 Mar 2018 17:05:41 -0700 (PDT)
Received: from mail-ot0-x22f.google.com (mail-ot0-x22f.google.com [IPv6:2607:f8b0:4003:c0f::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5234D1250B8; Mon, 12 Mar 2018 17:05:41 -0700 (PDT)
Received: by mail-ot0-x22f.google.com with SMTP id 79so17143053oth.11; Mon, 12 Mar 2018 17:05:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0BWgmpovPGSAnqOx4qEB9AMYSn9pu/SQltvcJV4eIiA=; b=ftASsw3BZS8b5H/KlrUB6ARMCXGqHVW6Hnvkv0CWuMIDNeVYE207Y6Js4LXSYk+XzY q4CefuxoWJuqefukzXITOoglEHeXwVhSjea4gUuDAQm7zgYeG/2vDUXrAyglpGh6fwbA Nhi9CcE1yZwtX8y0zu/Aak7bOD01hTz37Kr7lcEJhujPcswySh6QtmEQkoWulS6ZIDQQ PhvIip0kms6Ee2A365vCYcaEsHWF6DOnvqmG+FqzLHkHBNsUt4qbMunBHVzCj1e554qB jSFi64LvPR9Q8fqZtqaasWHZK+80RdAzE2D/oT0hP+ryFlIMvEdgKO5LBog0nMFsbbwx wCZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=0BWgmpovPGSAnqOx4qEB9AMYSn9pu/SQltvcJV4eIiA=; b=o19lFFlQJqTSQKpNuEOWFotQqBN2Qxq88+ZdF2rWfCnjDUvqqlspK0y6R7m792Fbc8 eXyU3XN6QcQ1MurYdsiiayjXWTS6iOE3OcILGHsgtfcvuqQ4SlW/DeYiJagDGU7Y6xUw LYOcCb965tGbxERqxrREFTqoevzTquXoH7QLWxBSwTr8hNdZ6UzyPgWIsUhm26rgXXQs BNgEcT5Q6IXQwjrUorU47pxDuSaCijz8ta+kZ4Cam3B4fQlDIuP23WFRyuJ7sgjb+huZ 39d+hZrOlAbj2bTBktmxy43eIjIlDf8Z50j15QYtOg86byGqyzRV7MUjoClUo0QX3w+N QYfA==
X-Gm-Message-State: AElRT7F0Gi7E/t6V3Gt9dwpfq2aMf4O8ejldEYzH46dPdukmppWb6XkX DHECowC4qt8J7tQ3PVryXmN/Fjpx3ECEZ48vEDnRxLR1
X-Google-Smtp-Source: AG47ELsy9eCNlCwjBpS+pODip9/Zt9sqlwLUNxzQDKKl+9raZxcte0yv2/mVVjBKq4/rxTjlpyKKuP3DchAOMK7Wong=
X-Received: by 10.157.75.130 with SMTP id k2mr7062494otf.244.1520899540608; Mon, 12 Mar 2018 17:05:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.67.77 with HTTP; Mon, 12 Mar 2018 17:05:40 -0700 (PDT)
In-Reply-To: <ca9334ec-aa8c-55bd-3180-7086cd21952c@akamai.com>
References: <CABEjbRKS04Wx-L3eKJBNFbsNywZe_19X2NY++3NSovr_3viJWg@mail.gmail.com> <BN6PR16MB1425EF492922CE97B6CF256CEAD30@BN6PR16MB1425.namprd16.prod.outlook.com> <ca9334ec-aa8c-55bd-3180-7086cd21952c@akamai.com>
From: Noriyuki Torii <torii0573@gmail.com>
Date: Tue, 13 Mar 2018 09:05:40 +0900
Message-ID: <CABEjbR+FGyu2gxs5KGucsqSByQpbC2T=-S3WZ2gt9qJt-BnotQ@mail.gmail.com>
To: "draft-ietf-tram-turnbis@ietf.org" <draft-ietf-tram-turnbis@ietf.org>
Cc: "tram@ietf.org" <tram@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/7e_isNi6hluYj42g9mi2QhCacUs>
Subject: Re: [tram] draft-ietf-tram-turnbis
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2018 00:05:43 -0000

Hi Brandon,

Thanks for your complementary note.
Truly, it is what I would like to say in the previous post.

Regards,
Noriyuki Torii

2018-03-13 1:02 GMT+09:00 Brandon Williams <brandon.williams@akamai.com>:
> Hi Tiru,
>
> I think that Torii's point is that according to stunbis section 9.2.5 a
> request that contains PASSWORD-ALGORITHM will also contain
> PASSWORD-ALGORITHMS, echoing back the value contained in the response. The
> example in section 18 does not show this.
>
> --Brandon
>
>
> On 03/12/2018 09:34 AM, Konda, Tirumaleswar Reddy wrote:
>>>
>>> -----Original Message-----
>>> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Noriyuki Torii
>>> Sent: Monday, March 12, 2018 12:40 PM
>>> To: draft-ietf-tram-turnbis@ietf.org
>>> Cc: tram@ietf.org
>>> Subject: [tram] draft-ietf-tram-turnbis
>>>
>>> To whom it may concern.
>>>
>>> I found some discrepancies in the draft-ietf-tram-turnbis-14.
>>> Hope this may help for improvement.
>>>
>>> - Section 12 defines the allowed channel numbers as below,
>>>
>>>   >      0x4000 through 0x7FFF: These values are the allowed channel
>>>   >      numbers (16,384 possible values).
>>>
>>>   but the RFC 7983 shrinks the valid range of channel number to 0x4000 -
>>> 0x4FFF.
>>>   Please see also
>>>   https://www.iana.org/assignments/stun-parameters/stun-
>>> parameters.xhtml#turn-channel
>>
>>
>> Thanks, fixed.
>>
>>>
>>> - STUNbis specification requires that PASSWORD-ALGORITHMS and
>>> PASSWORD-
>>>    ALGORITHM attributes are both present or neither not present in each
>>>    request, from my understandings.
>>>    If so, the section 18 needs refinements to reflect the above
>>> requirement,
>>>    because some example requests shown in the current document only have
>>>    PASSWORD-ALGORITHM and doesn't have PASSWORD-ALGORITHMS.
>>
>>
>> Section 18 discusses both PASSWORD-ALGORITHM and PASSWORD-ALGORITHMS (sent
>> in Allocate error response).
>>
>> -Tiru
>>
>>>
>>> Best regards,
>>>
>>> Noriyuki Torii
>>>
>>> _______________________________________________
>>> tram mailing list
>>> tram@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tram
>>
>>
>> _______________________________________________
>> tram mailing list
>> tram@ietf.org
>> https://www.ietf.org/mailman/listinfo/tram
>>
>


From nobody Mon Mar 12 21:28:31 2018
Return-Path: <TirumaleswarReddy_Konda@mcafee.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1D5012D948; Mon, 12 Mar 2018 21:28:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level: 
X-Spam-Status: No, score=-4.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mcafee.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oxywFKRE_6cx; Mon, 12 Mar 2018 21:28:26 -0700 (PDT)
Received: from DNVWSMAILOUT1.mcafee.com (dnvwsmailout1.mcafee.com [161.69.31.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61D2E129C53; Mon, 12 Mar 2018 21:28:26 -0700 (PDT)
X-NAI-Header: Modified by McAfee Email Gateway (5500)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mcafee.com; s=s_mcafee; t=1520915305; h=From: To:CC:Subject:Thread-Topic:Thread-Index:Date: Message-ID:References:In-Reply-To:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: dlp-product:dlp-version:dlp-reaction:authentication-results: x-originating-ip:x-ms-publictraffictype:x-microsoft-exchange-diagnostics: x-ms-exchange-antispam-srfa-diagnostics:x-ms-office365-filtering-correlation-id: x-microsoft-antispam:x-ms-traffictypediagnostic: x-microsoft-antispam-prvs:x-exchange-antispam-report-test: x-exchange-antispam-report-cfa-test:x-forefront-prvs: x-forefront-antispam-report:received-spf:x-microsoft-antispam-message-info: spamdiagnosticoutput:spamdiagnosticmetadata: Content-Type:Content-Transfer-Encoding:MIME-Version: X-MS-Exchange-CrossTenant-Network-Message-Id: X-MS-Exchange-CrossTenant-originalarrivaltime: X-MS-Exchange-CrossTenant-fromentityheader: X-MS-Exchange-CrossTenant-id:X-MS-Exchange-Transport-CrossTenantHeadersStamped: X-OriginatorOrg:X-NAI-Spam-Flag:X-NAI-Spam-Threshold: X-NAI-Spam-Score:X-NAI-Spam-Version; bh=4 ZN+i+LvwJy5ZAthQrpACxURRp6bR+724+Wxc6Npmx w=; b=KuBU5Lj4kUNaej8iThuoNX/vVzvN9ozAr6l3bCwpMFM7 IznaGl2lBd5hcX34bGVcZVrq1h6E5gSbKw+NWaS02TaCmOOv8E jOsDnn1XT/z0f1Oa/0R3HNIB+F+DEWdNq58oaZ2c25dmbBWhEl TjpWeDWT2BKn/+VLDfJdEejXK8I=
Received: from DNVEXAPP1N06.corpzone.internalzone.com (unknown [10.44.48.90]) by DNVWSMAILOUT1.mcafee.com with smtp (TLS: TLSv1/SSLv3,256bits,ECDHE-RSA-AES256-SHA384) id 1c29_02fc_22a1d7ff_6b55_469a_abeb_7ff621c98d49; Mon, 12 Mar 2018 23:28:24 -0500
Received: from DNVEXUSR1N10.corpzone.internalzone.com (10.44.48.83) by DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Mon, 12 Mar 2018 22:28:05 -0600
Received: from DNVEXAPP1N05.corpzone.internalzone.com (10.44.48.89) by DNVEXUSR1N10.corpzone.internalzone.com (10.44.48.83) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Mon, 12 Mar 2018 22:28:04 -0600
Received: from DNVO365EDGE1.corpzone.internalzone.com (10.44.176.66) by DNVEXAPP1N05.corpzone.internalzone.com (10.44.48.89) with Microsoft SMTP Server (TLS) id 15.0.1347.2 via Frontend Transport; Mon, 12 Mar 2018 22:28:04 -0600
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (10.44.176.243) by edge.mcafee.com (10.44.176.66) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Mon, 12 Mar 2018 22:28:03 -0600
Received: from BN6PR16MB1425.namprd16.prod.outlook.com (10.172.207.19) by BN6PR16MB1684.namprd16.prod.outlook.com (10.172.28.9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.567.14; Tue, 13 Mar 2018 04:28:02 +0000
Received: from BN6PR16MB1425.namprd16.prod.outlook.com ([10.172.207.19]) by BN6PR16MB1425.namprd16.prod.outlook.com ([10.172.207.19]) with mapi id 15.20.0567.018; Tue, 13 Mar 2018 04:28:02 +0000
From: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>
To: Noriyuki Torii <torii0573@gmail.com>, "draft-ietf-tram-turnbis@ietf.org" <draft-ietf-tram-turnbis@ietf.org>
CC: "tram@ietf.org" <tram@ietf.org>
Thread-Topic: [tram] draft-ietf-tram-turnbis
Thread-Index: AQHTudE4Fs843+xF7k+BrOpFdbSpHaPMmH3AgAAq1oCAAIcVAIAASSbg
Date: Tue, 13 Mar 2018 04:28:02 +0000
Message-ID: <BN6PR16MB1425E59E4FCBD6E28BF5BF70EAD20@BN6PR16MB1425.namprd16.prod.outlook.com>
References: <CABEjbRKS04Wx-L3eKJBNFbsNywZe_19X2NY++3NSovr_3viJWg@mail.gmail.com> <BN6PR16MB1425EF492922CE97B6CF256CEAD30@BN6PR16MB1425.namprd16.prod.outlook.com> <ca9334ec-aa8c-55bd-3180-7086cd21952c@akamai.com> <CABEjbR+FGyu2gxs5KGucsqSByQpbC2T=-S3WZ2gt9qJt-BnotQ@mail.gmail.com>
In-Reply-To: <CABEjbR+FGyu2gxs5KGucsqSByQpbC2T=-S3WZ2gt9qJt-BnotQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 11.0.200.100
dlp-reaction: no-action
authentication-results: spf=none (sender IP is ) smtp.mailfrom=TirumaleswarReddy_Konda@McAfee.com; 
x-originating-ip: [185.221.69.14]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR16MB1684; 7:U1TTMRYF5+ev3Ce/C8vFM+OI5D3pwbNJUcAB+pvRWy21Zv/vRXV5sS5pSfApVvyrJ/xL+4R3XNS4ZCQNj3PqeNNAUAW+D1/b04rmVF+E+aP2Y7B4zSsVt9fUL+LwoUTzYz88WCjZNfWPHj7ufap+ngNuRUVuecoH/44ZKFnk2EbWKALiXf9IfHVRdWWUoDwy1unKwK354CrNSAYugvfX+LFH//kYzAt7aAWZnbAb0dt68HXIFJW3sEJPWq4/TPai
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 14e44b15-0edf-42c3-35eb-08d5889acf21
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BN6PR16MB1684; 
x-ms-traffictypediagnostic: BN6PR16MB1684:
x-microsoft-antispam-prvs: <BN6PR16MB16845A7D194DDE10E3DEA3BFEAD20@BN6PR16MB1684.namprd16.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(1591387915157);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3231221)(944501244)(52105095)(3002001)(10201501046)(93006095)(93001095)(6041310)(20161123558120)(20161123560045)(20161123564045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:BN6PR16MB1684; BCL:0; PCL:0; RULEID:; SRVR:BN6PR16MB1684; 
x-forefront-prvs: 0610D16BBE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39380400002)(39860400002)(376002)(366004)(346002)(396003)(13464003)(51444003)(199004)(189003)(377424004)(32952001)(97736004)(2900100001)(80792005)(110136005)(2501003)(68736007)(3660700001)(66066001)(2950100002)(229853002)(105586002)(106356001)(6436002)(55016002)(53936002)(5660300001)(6246003)(9686003)(6306002)(33656002)(25786009)(53546011)(39060400002)(6506007)(26005)(4326008)(316002)(77096007)(3280700002)(81156014)(7736002)(7696005)(102836004)(551544002)(478600001)(966005)(72206003)(2906002)(186003)(74316002)(14454004)(59450400001)(8676002)(305945005)(86362001)(99286004)(76176011)(6116002)(3846002)(8936002)(81166006)(93886005)(85282002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR16MB1684; H:BN6PR16MB1425.namprd16.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: McAfee.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 5VZH05EPmLHorNiDJY0IzICWa5roFhPHPUs2atkKoaVed7lddmxqScyrILul9eseQ8TQnqsauTAm78SuKWcqot4jFpYgah08HhlpMknQyD7sxRFpxtjJxJosfxNnRNCfETN7Jl8ltpslTyEvyfJhJhVGZcaLOVaxZa5XZExpBPBuF3OVOj6vZEd5MMxh8e85cJYtmdyx3HN0TUXRcjr0r3YrmhOyINHiztPizKcHlM7248KGs5iX7PgNSm/jmWIysHY1CEb/7nZr7Tm5C1m/T39+UXcLrY/+SvcYDzOC1axc+l8dU5gA73wHbs7+lCophEOqFgdDMJE5P7ZAFDmlIw==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 14e44b15-0edf-42c3-35eb-08d5889acf21
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Mar 2018 04:28:02.2893 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4943e38c-6dd4-428c-886d-24932bc2d5de
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR16MB1684
X-OriginatorOrg: mcafee.com
X-NAI-Spam-Flag: NO
X-NAI-Spam-Threshold: 15
X-NAI-Spam-Score: 0
X-NAI-Spam-Version: 2.3.0.9418 : core <6240> : inlines <6478> : streams <1781238> : uri <2607270>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/jjaT6-K6nMF9Qh133DaaSpFn09o>
Subject: Re: [tram] draft-ietf-tram-turnbis
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2018 04:28:30 -0000

Thanks, updated example in Section 18.

Cheers,
-Tiru

> -----Original Message-----
> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Noriyuki Torii
> Sent: Tuesday, March 13, 2018 5:36 AM
> To: draft-ietf-tram-turnbis@ietf.org
> Cc: tram@ietf.org
> Subject: Re: [tram] draft-ietf-tram-turnbis
>=20
> Hi Brandon,
>=20
> Thanks for your complementary note.
> Truly, it is what I would like to say in the previous post.
>=20
> Regards,
> Noriyuki Torii
>=20
> 2018-03-13 1:02 GMT+09:00 Brandon Williams
> <brandon.williams@akamai.com>:
> > Hi Tiru,
> >
> > I think that Torii's point is that according to stunbis section 9.2.5
> > a request that contains PASSWORD-ALGORITHM will also contain
> > PASSWORD-ALGORITHMS, echoing back the value contained in the
> response.
> > The example in section 18 does not show this.
> >
> > --Brandon
> >
> >
> > On 03/12/2018 09:34 AM, Konda, Tirumaleswar Reddy wrote:
> >>>
> >>> -----Original Message-----
> >>> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Noriyuki
> >>> Torii
> >>> Sent: Monday, March 12, 2018 12:40 PM
> >>> To: draft-ietf-tram-turnbis@ietf.org
> >>> Cc: tram@ietf.org
> >>> Subject: [tram] draft-ietf-tram-turnbis
> >>>
> >>> To whom it may concern.
> >>>
> >>> I found some discrepancies in the draft-ietf-tram-turnbis-14.
> >>> Hope this may help for improvement.
> >>>
> >>> - Section 12 defines the allowed channel numbers as below,
> >>>
> >>>   >      0x4000 through 0x7FFF: These values are the allowed channel
> >>>   >      numbers (16,384 possible values).
> >>>
> >>>   but the RFC 7983 shrinks the valid range of channel number to
> >>> 0x4000 - 0x4FFF.
> >>>   Please see also
> >>>   https://www.iana.org/assignments/stun-parameters/stun-
> >>> parameters.xhtml#turn-channel
> >>
> >>
> >> Thanks, fixed.
> >>
> >>>
> >>> - STUNbis specification requires that PASSWORD-ALGORITHMS and
> >>> PASSWORD-
> >>>    ALGORITHM attributes are both present or neither not present in ea=
ch
> >>>    request, from my understandings.
> >>>    If so, the section 18 needs refinements to reflect the above
> >>> requirement,
> >>>    because some example requests shown in the current document only
> have
> >>>    PASSWORD-ALGORITHM and doesn't have PASSWORD-ALGORITHMS.
> >>
> >>
> >> Section 18 discusses both PASSWORD-ALGORITHM and PASSWORD-
> ALGORITHMS
> >> (sent in Allocate error response).
> >>
> >> -Tiru
> >>
> >>>
> >>> Best regards,
> >>>
> >>> Noriyuki Torii
> >>>
> >>> _______________________________________________
> >>> tram mailing list
> >>> tram@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/tram
> >>
> >>
> >> _______________________________________________
> >> tram mailing list
> >> tram@ietf.org
> >> https://www.ietf.org/mailman/listinfo/tram
> >>
> >
>=20
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram


From nobody Thu Mar 15 00:41:34 2018
Return-Path: <torii0573@gmail.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A0AE12D86C; Wed,  7 Mar 2018 04:10:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.642
X-Spam-Level: 
X-Spam-Status: No, score=-0.642 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, LOCALPART_IN_SUBJECT=1.107, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8bI62kgWULBb; Wed,  7 Mar 2018 04:10:42 -0800 (PST)
Received: from mail-ot0-x241.google.com (mail-ot0-x241.google.com [IPv6:2607:f8b0:4003:c0f::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D62E12D7FC; Wed,  7 Mar 2018 04:10:42 -0800 (PST)
Received: by mail-ot0-x241.google.com with SMTP id y11so1828988otg.0; Wed, 07 Mar 2018 04:10:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to:cc; bh=XBIbAuNxRbd82fy2Ek+10bP1jc4JuzUT31cUQFyHCDw=; b=cdSXP1o/yMyKvhc4/7ZDiIz/HCUdL+auPSPRPQMdV477G2UCzqqLu5BjvT1QEl14N7 siNn57Wuo4arHCtGmDsbL2Q+j9X4EnMkehFzWPAhplQAbCgjkjknZ685P+refOg6s21e yq4rotDrlOGJ191/czmO5c4NQzxsRpZnWh/EQq01egIlYnBE/CkwsQDMJRfVPOAEOvo8 r5BzVzkmTz1EHDtOsiqGk+Dmgf0zRC7J68IXKeFeFkQc5epT6Ee0bPabljUWCzToD7un qMJqelC445XMJcPzX9qKU1MVVeTPvaRiGKdBfGEqyV+fUVFXyUaeycKMlviJ20o+19IA jPAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=XBIbAuNxRbd82fy2Ek+10bP1jc4JuzUT31cUQFyHCDw=; b=pkh4uAvb6UZo8BUfaSfarHPRw8t1Wp83SW67vUP1TQPApbihHtk3g55PBxdFdKv1F2 /ek7eKcaxv/cYAFxs2wDJaC36SdrFsVVqQcHKCVmG655DJLVVXqUljwvWT/DTlKshNSZ Z2xKXInf0bTffPdz1RNUei5IPK62JdFI2tMAyBU9KnkMwlHAZ+LgGXUzhHn9aUxZuxBD x/xnzy7/pUYh/fO8YnxCf0+gwasPEzUEOvdQ0nS8gN0MGlQLr0phxYHUooFRzw49Ew4k V90doTw0TGIvGLPrK5SHohwAxoj2daVHbzbdgowuO4r8eSCUBtJv7Qdrnz8oMI/rlAXy rEDQ==
X-Gm-Message-State: AElRT7FafIsoOlzrfxUpVQ+N/gJDbEMS3Hjh+wpUoY7mj4rwqJTtSxfe wblj7w6H1+m23qz5qJsHMfXTaJnrEUAopLnYj/cxFLR0
X-Google-Smtp-Source: AG47ELt5AiIg0E+Amaq0TLvJcJQEvI3QFrax8Q6g9JKt4ed14rjQrkDO/5Pxl1aZvpEUS5JvEvMTtngbN9eMxQ8Rf6E=
X-Received: by 10.157.83.201 with SMTP id i9mr15010255oth.401.1520424641318; Wed, 07 Mar 2018 04:10:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.201.12.84 with HTTP; Wed, 7 Mar 2018 04:10:40 -0800 (PST)
From: Noriyuki Torii <torii0573@gmail.com>
Date: Wed, 7 Mar 2018 21:10:40 +0900
Message-ID: <CABEjbRJjU2LVb0iDkBavpSxtw-+PowvsyDdg9hhvwX+Gi9Awzw@mail.gmail.com>
To: draft-ietf-tram-stunbis@ietf.org
Cc: tram@ietf.org
Content-Type: multipart/alternative; boundary="f403043e4f78a756a30566d172ca"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/Tt8EyxUHYk3zGFf6bLY9hwltIHM>
X-Mailman-Approved-At: Thu, 15 Mar 2018 00:41:32 -0700
Subject: [tram] draft-ietf-tram-stunbis
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2018 12:10:43 -0000

--f403043e4f78a756a30566d172ca
Content-Type: text/plain; charset="UTF-8"

To whom it may concern.

I'm Noriyuki Torii. I have red the updated I-D of STUNbis-16 and found
some issues would like to be shared.

Hope this may help for improvement.

- Section 9.1.1 and 9.2.2 defines the HMAC key calculation based on some
  elements such that the password, username and realm.
  Sections say those elements should be proccessed using OpaqueString
profile
  defined in RFC8265.

  On the other hand, RFC8265 says in its "Changes from RFC 7613" that
     "Removed UTF-8 as a mandatory encoding, because that is a matter
      for the application."

  So, the specification of applied encoding for those elements on
calculating
  HMAC key is up to STUNbis document.

  Please note that username and realm have the applied encoding
specification
  as UTF-8 in its corresponding STUN attribute description.
  (please see section 14.3 and 14.9)
  But the password doesn't have such a description, therefore some care need
  to be taken.

- Section 14.6 mentions to the HMAC truncation, but as far as I read, I
  couldn't precisely find out the minimum byte of length of the HMAC.

  From my understandings, minimum length
  maybe 16 because
  > The HMAC MUST NOT be truncated below a minimum size of 16 bytes.

  OR
  maybe 8 because
  > The value (snip) MUST be a positive multiple of 4 bytes
    AND
  > STUN Usages may specify a minimum length longer than 4 bytes.

  Here above I conceived "longer than (but not equal to) 4 bytes".
  IMHO, some clarification will be preferable.

- There are some occurence such like
   > a UTF-8 [RFC3629] encoded
   > sequence of less than 128 characters (which can be as long as 509
   > bytes when encoding them or 763 bytes when decoding them).

   The sentence inside parenthesis have off-by-one error.
   To be exact,

   (which can be less than 509 bytes when encoding them or 763 bytes
   when decoding them)

   or alternatively

   (which can be as long as 508 bytes when encoding them or 762 bytes
   when decoding them)

- In Section 9.2.4, there are some typoes.
  Unnecessary extra white space such that "PASSWORD- ALGORITHM".

- At page 40, bizzare (perhaps unintended) page break occurs.

Best regards,

Noriyuki Torii

--f403043e4f78a756a30566d172ca
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><p>To whom it may concern.</p><p>I&#39;m Noriyuki Torii. I=
 have red the updated I-D of STUNbis-16 and found <br>some issues would lik=
e to be shared.</p><p>Hope this may help for improvement.</p><p>- Section 9=
.1.1 and 9.2.2 defines the HMAC key calculation based on some<br>=C2=A0 ele=
ments such that the password, username and realm.<br>=C2=A0 Sections say th=
ose elements should be proccessed using OpaqueString profile<br>=C2=A0 defi=
ned in RFC8265.</p><p>=C2=A0 On the other hand, RFC8265 says in its &quot;C=
hanges from RFC 7613&quot; that<br>=C2=A0=C2=A0=C2=A0=C2=A0 &quot;Removed U=
TF-8 as a mandatory encoding, because that is a matter<br>=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 for the application.&quot;</p><p>=C2=A0 So, the specificati=
on of applied encoding for those elements on calculating<br>=C2=A0 HMAC key=
 is up to STUNbis document.</p><p>=C2=A0 Please note that username and real=
m have the applied encoding specification<br>=C2=A0 as UTF-8 in its corresp=
onding STUN attribute description. <br>=C2=A0 (please see section 14.3 and =
14.9)<br>=C2=A0 But the password doesn&#39;t have such a description, there=
fore some care need<br>=C2=A0 to be taken.</p><p>- Section 14.6 mentions to=
 the HMAC truncation, but as far as I read, I <br>=C2=A0 couldn&#39;t preci=
sely find out the minimum byte of length of the HMAC.</p><p>=C2=A0 From my =
understandings, minimum length <br>=C2=A0 maybe 16 because<br>=C2=A0 &gt; T=
he HMAC MUST NOT be truncated below a minimum size of 16 bytes.</p><p>=C2=
=A0 OR <br>=C2=A0 maybe 8 because<br>=C2=A0 &gt; The value (snip) MUST be a=
 positive multiple of 4 bytes<br>=C2=A0=C2=A0=C2=A0 AND<br>=C2=A0 &gt; STUN=
 Usages may specify a minimum length longer than 4 bytes.</p><p>=C2=A0 Here=
 above I conceived &quot;longer than (but not equal to) 4 bytes&quot;.<br>=
=C2=A0 IMHO, some clarification will be preferable.</p><p>- There are some =
occurence such like <br>=C2=A0=C2=A0 &gt; a UTF-8 [RFC3629] encoded<br>=C2=
=A0=C2=A0 &gt; sequence of less than 128 characters (which can be as long a=
s 509<br>=C2=A0=C2=A0 &gt; bytes when encoding them or 763 bytes when decod=
ing them).</p><p>=C2=A0=C2=A0 The sentence inside parenthesis have off-by-o=
ne error.<br>=C2=A0=C2=A0 To be exact, </p><p>=C2=A0=C2=A0 (which can be le=
ss than 509 bytes when encoding them or 763 bytes <br>=C2=A0=C2=A0 when dec=
oding them)</p><p>=C2=A0=C2=A0 or alternatively</p><p>=C2=A0=C2=A0 (which c=
an be as long as 508 bytes when encoding them or 762 bytes <br>=C2=A0=C2=A0=
 when decoding them)</p><p>- In Section 9.2.4, there are some typoes. <br>=
=C2=A0 Unnecessary extra white space such that &quot;PASSWORD- ALGORITHM&qu=
ot;.</p><p>- At page 40, bizzare (perhaps unintended) page break occurs.</p=
><p>Best regards, </p><p>Noriyuki Torii<br><br></p></div>

--f403043e4f78a756a30566d172ca--


From nobody Fri Mar 16 04:35:44 2018
Return-Path: <linuxwolf+ietf@outer-planes.net>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C15BC127735 for <tram@ietfa.amsl.com>; Fri, 16 Mar 2018 04:35:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outer-planes-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6w_2gMS4DVvO for <tram@ietfa.amsl.com>; Fri, 16 Mar 2018 04:35:24 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF1B312778E for <tram@ietf.org>; Fri, 16 Mar 2018 04:35:21 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id t6so2437308wmt.5 for <tram@ietf.org>; Fri, 16 Mar 2018 04:35:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outer-planes-net.20150623.gappssmtp.com; s=20150623; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to; bh=mjfH8+sDDOY3keaN9cbSDqu7dpPGDDJaopPXIxzccS0=; b=n7F1a0FTgVE8fdRj3i5LkPCiX/iiYKsKXeMfCgGntvsQjfVGl80dnWanu5Ie7xGTxi b31665kDFBJcKlfaB4Ha6CO/ic1v+ElzdQO/jfPqJUF+l3puS2hFEnPeJHz1kXsSvy+B Nlv9AZcQSso/ovwqMDoPGRSe8ezTYXrL6L9QtBHyDG1CVKTQMTcks5Kf3BvvJDiZ2HSR ojPk4eR6WoOFS0dtjhVTBY9qTFhYc3zfGL1G1q0nyXj5aLQdARMII0xPiTokcEBTPlxu LVkHmctOMT3d27pqEEiJWBgUuqZ7ML44qlFsTZwbb5P2qqw8tNkB3yoDLpz8seQdPVaG 8jZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to; bh=mjfH8+sDDOY3keaN9cbSDqu7dpPGDDJaopPXIxzccS0=; b=raFhuXH2Xz+aMO2u+QYlqZ6YBU1d+hK24X8P28Pz4tLaCfWtUOGZjLRB00Gto9iSdD rt4k471W6+FzId0aTOqi8lDgeX3JZdgj9XAYhfiiA+X0gzqpS1ZyLP5Y0CqErJeqB+3W 8sMWGKwv7k8BhrRwbos1f5ItZsSMzY8dMuyY2Hh4ufPyXH1u3wVFUF1YDTcloBL/GeMw 7id5T2eHFtBJ8QqOT9rq8K5S16b7VFQhBgxlcxtwZ8BAqaI2ZZGibv1KnXzAJ+ykL4aw rZQh4BAxv+Ie3Jv9FT7btE7RiNCpInhTBN30sISTo+x46wDHud7tUWhWCMiobzUyoaZs yA2g==
X-Gm-Message-State: AElRT7FkeN43dadkySN5NM2r35HbkRcNiADj9zg0TMyO2EiYtlLsQ3pL i542dCrjBZebjALeB403gKuuygVeCIouJQ==
X-Google-Smtp-Source: AG47ELsGNAQ2viUfKxMPvSNIY7Kf9zVxMuTEPJRMo5E44CVp8oJYx72Mf/PqUgc4v6B1PS409ilMNQ==
X-Received: by 10.28.62.16 with SMTP id l16mr1604302wma.54.1521200119980; Fri, 16 Mar 2018 04:35:19 -0700 (PDT)
Received: from ?IPv6:2001:67c:1232:144:3dc5:da42:199a:6337? ([2001:67c:1232:144:3dc5:da42:199a:6337]) by smtp.gmail.com with ESMTPSA id m191sm6310234wma.21.2018.03.16.04.35.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 Mar 2018 04:35:19 -0700 (PDT)
Sender: Matthew Miller <linuxwolf@outer-planes.net>
To: Marc Petit-Huguenin <marc@petit-huguenin.org>, secdir@ietf.org
Cc: draft-ietf-tram-stunbis.all@ietf.org, ietf@ietf.org, tram@ietf.org
References: <152063220998.11155.12669577501214588133@ietfa.amsl.com> <a9a7c497-3815-f022-f9a9-2fe53d3394f5@petit-huguenin.org>
From: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
Message-ID: <8fdfe1a4-9aad-1b34-c05b-086020f0f8fa@outer-planes.net>
Date: Fri, 16 Mar 2018 05:35:18 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <a9a7c497-3815-f022-f9a9-2fe53d3394f5@petit-huguenin.org>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ZH0RjWPipU5xcHAywaciiFNIpF79zZNQ2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/C0Da8gQtATF59RYHaHSGT08GZuo>
Subject: Re: [tram] Secdir last call review of draft-ietf-tram-stunbis-16
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2018 11:35:26 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--ZH0RjWPipU5xcHAywaciiFNIpF79zZNQ2
Content-Type: multipart/mixed; boundary="IgZ0PUS4ADpgTmao4uYVHnqneekamYIlG";
 protected-headers="v1"
From: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
To: Marc Petit-Huguenin <marc@petit-huguenin.org>, secdir@ietf.org
Cc: draft-ietf-tram-stunbis.all@ietf.org, ietf@ietf.org, tram@ietf.org
Message-ID: <8fdfe1a4-9aad-1b34-c05b-086020f0f8fa@outer-planes.net>
Subject: Re: Secdir last call review of draft-ietf-tram-stunbis-16
References: <152063220998.11155.12669577501214588133@ietfa.amsl.com>
 <a9a7c497-3815-f022-f9a9-2fe53d3394f5@petit-huguenin.org>
In-Reply-To: <a9a7c497-3815-f022-f9a9-2fe53d3394f5@petit-huguenin.org>

--IgZ0PUS4ADpgTmao4uYVHnqneekamYIlG
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable


On 18/03/11 07:55, Marc Petit-Huguenin wrote:
> Hi,
>=20
> Thanks for the review.
>=20
> Please see inline.
>=20
> On 03/09/2018 01:50 PM, Matthew Miller wrote:
>> Reviewer: Matthew Miller
>> Review result: Has Issues
>>
>> [ I realize how unfortunate it is this arrives well past last call.
>> I beg forgiveness and ask that you accept the comments as you would
>> have if they arrived on time. ]
>>
>> I have reviewed this document as part of the security directorate's
>> ongoing effort to review all IETF documents being processed by the
>> IESG.  These comments were written primarily for the benefit of the
>> security area directors.  Document editors and WG chairs should
>> treat these comments just like any other last call comments.
>>
>> Document: draft-ietf-stunbis-16
>> Reviewer: Matthew A. Miller
>> Review Date: 2018-03-07
>> IETF LC End Date: 2018-02-20
>> IESG Telechat date: 2018-04-05
>>
>> Summary:  This document obsoletes 5389, adding some protection to
>> downgrade attacks against message integrity usage, as well
>> incorporating DTLS (over UDP).
>>
>> The document is mostly ready, but there are a couple of issues I
>> have.
>>
>> Major Issues: N/A
>>
>> Minor Issues:
>>
>> * I am wondering why a more robust password algorithm (key derivation
>> function) was not defined (e.g., HKDF-SHA-256) instead of or in additi=
on
>> to, a simple salted "SHA-256" hash.  Some amount of parameterization i=
s
>> accounted for in the PASSWORD-ALGORITHM/S attributes.  I think it is
>> perfectly fair and appropriate to take this issue as "asking for a qui=
ck
>> rationale (that maybe ought to be highlighted better in the document)"=

>> over "use a real key derivation function".
>=20
> We proposed other algorithms to the Working Group but there was no cons=
ensus past using what we have today in the draft.
>> We basically wanted to keep STUN aligned with HTTP Digest and SIP
Digest as much as possible.  Rereading both RFC 7616 and
draft-yusef-sipcore-digest-scheme I can not find mention of using a key
derivation function for these.
>=20
> Can you explain how that could be used with STUN (and potentially with =
HTTP and SIP)?
Thank you for the extra context.  The way this authentication is done
looks like something that would benefit from a more robust KDF.

I hesitate to add this, but these authentication schemes are quite
distant from HTTP (and SIP) digest authentication.  While they are using
the same hash algorithm, how the inputs are processed are radically
different from what STUN(bis) defines.

But, my intent is not to boil this ocean. It's not clear to me this
would be a worthwhile improvement by itself, and there is already a
warning in the security considerations about the weaknesses of the
authentication schemes.

I'm willing to consider this point addressed.

>=20
>>
>> * The description for 17.5.1. "MD5" list the key size as 20 bytes, but=
 the
>> hash length of MD5 is 16 bytes (128 bits).  I think this is merely a t=
ypo,
>> since the purpose appears to be for backwards compatibility with exist=
ing
>> systems.
>=20
> Fixed.
>=20
>>
>> * Both 17.5.1.1. "MD5" Section 9.2.2. "HMAC Key" (long-term credential=
)
>> and Section appear to define the same functional algorithm, but with s=
ubtle
>> syntax differences.  As far as I can tell, they are actually the same
>> algorithm; would it not be acceptable to have Section 9.2.2 point to
>> Section 17.5.1.1 for the algorithm description?
>>
>>
>=20
> This is going into the IANA registry so I left things there.  I fixed t=
he discrepancy with section 9.2.2.
>=20
> I also fixed the definition of the key for SHA-256, which must use Opaq=
ueString for the realm.
>=20

Thanks very much.


- m&m

Matthew A. Miller


--IgZ0PUS4ADpgTmao4uYVHnqneekamYIlG--

--ZH0RjWPipU5xcHAywaciiFNIpF79zZNQ2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEMddYjeyQaQ1rzJjg7PRyThCeBbsFAlqrq/YACgkQ7PRyThCe
BbtoYwgAo6BTfVn+B8A5g+6VOFLRrVA/0Y7bgsJZtdjQO+Lx/8+1AqfyhTuFc/+5
mz9l7bAdCI9POqomYjsKQicjYQskFokGyRpuFtdFCZ4XOTLs6cIMCk22UCM1xl0g
4z6wGjfOtS5qSG5uBCmDbUxHFUNyrQpYJoGSFDqi7Za/Ycjria5Iz751Gu121lLP
XbM3/7YeVOLNRgFBZo0QuxHKJN7bYwDMEKL8wkMRQ5VVM5L+MzVuk90Opvjp757X
Y2TfKAOSwmK7tDgZQp+LMqV50p9n8veDmxlDE2rB+W7uzyHm4tF4DbElHcY1fcR2
KZNr38lBOnk31WLACZzeOLnpF/xdzQ==
=DuXV
-----END PGP SIGNATURE-----

--ZH0RjWPipU5xcHAywaciiFNIpF79zZNQ2--


From nobody Sun Mar 18 01:43:29 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tram@ietf.org
Delivered-To: tram@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 92C951200FC; Sun, 18 Mar 2018 01:43:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: tram@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.75.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152136260256.18150.10551009018364033510@ietfa.amsl.com>
Date: Sun, 18 Mar 2018 01:43:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/S4NdFZFzWwIgULNEl53TnVcXVWw>
Subject: [tram] I-D Action: draft-ietf-tram-turnbis-15.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Mar 2018 08:43:22 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the TURN Revised and Modernized WG of the IETF.

        Title           : Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)
        Authors         : Tirumaleswar Reddy
                          Alan Johnston
                          Philip Matthews
                          Jonathan Rosenberg
	Filename        : draft-ietf-tram-turnbis-15.txt
	Pages           : 84
	Date            : 2018-03-18

Abstract:
   If a host is located behind a NAT, then in certain situations it can
   be impossible for that host to communicate directly with other hosts
   (peers).  In these situations, it is necessary for the host to use
   the services of an intermediate node that acts as a communication
   relay.  This specification defines a protocol, called TURN (Traversal
   Using Relays around NAT), that allows the host to control the
   operation of the relay and to exchange packets with its peers using
   the relay.  TURN differs from some other relay control protocols in
   that it allows a client to communicate with multiple peers using a
   single relay address.

   The TURN protocol was designed to be used as part of the ICE
   (Interactive Connectivity Establishment) approach to NAT traversal,
   though it also can be used without ICE.

   This document obsoletes RFC 5766 and RFC 6156.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tram-turnbis/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-tram-turnbis-15
https://datatracker.ietf.org/doc/html/draft-ietf-tram-turnbis-15

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-tram-turnbis-15


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Sun Mar 18 01:50:49 2018
Return-Path: <TirumaleswarReddy_Konda@mcafee.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACBAC1200FC for <tram@ietfa.amsl.com>; Sun, 18 Mar 2018 01:50:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.331
X-Spam-Level: 
X-Spam-Status: No, score=-4.331 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mcafee.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dphA1FCi1lvi for <tram@ietfa.amsl.com>; Sun, 18 Mar 2018 01:50:46 -0700 (PDT)
Received: from DNVWSMAILOUT1.mcafee.com (dnvwsmailout1.mcafee.com [161.69.31.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08A241243F6 for <tram@ietf.org>; Sun, 18 Mar 2018 01:50:45 -0700 (PDT)
X-NAI-Header: Modified by McAfee Email Gateway (5500)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mcafee.com; s=s_mcafee; t=1521363045; h=From: To:Subject:Thread-Topic:Thread-Index:Date: Message-ID:References:In-Reply-To:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: dlp-product:dlp-version:dlp-reaction:authentication-results: x-originating-ip:x-ms-publictraffictype:x-microsoft-exchange-diagnostics: x-ms-exchange-antispam-srfa-diagnostics:x-ms-office365-filtering-correlation-id: x-microsoft-antispam:x-ms-traffictypediagnostic: x-microsoft-antispam-prvs:x-exchange-antispam-report-test: x-exchange-antispam-report-cfa-test:x-forefront-prvs: x-forefront-antispam-report:received-spf:x-microsoft-antispam-message-info: spamdiagnosticoutput:spamdiagnosticmetadata: Content-Type:Content-Transfer-Encoding:MIME-Version: X-MS-Exchange-CrossTenant-Network-Message-Id: X-MS-Exchange-CrossTenant-originalarrivaltime: X-MS-Exchange-CrossTenant-fromentityheader: X-MS-Exchange-CrossTenant-id:X-MS-Exchange-Transport-CrossTenantHeadersStamped: X-OriginatorOrg:X-NAI-Spam-Flag:X-NAI-Spam-Threshold: X-NAI-Spam-Score:X-NAI-Spam-Version; bh=K EWthabrQYpB1Suzp2EWAtiVYSJI4pU3iCRWC9rPlT Q=; b=B6istIu8n+53G4XdrAK5wm9RSAjoyyHg9wb8zAYWd4bA ILPnLCGslSxaovHkGdulr/nuL5vgBSA9hbH34pVw4+huCcyive fY6T4sMzVc0/WweTGieWTHh3cSY4ov4+sPaASyY3Z0gUSxuU2j zMiTOdrSkEFR6SmF+E6nlRhmMio=
Received: from DNVEXAPP1N06.corpzone.internalzone.com (unknown [10.44.48.90]) by DNVWSMAILOUT1.mcafee.com with smtp (TLS: TLSv1/SSLv3,256bits,ECDHE-RSA-AES256-SHA384) id 5843_e693_9d4ac2fd_73e3_4b0d_a575_d08cd2974137; Sun, 18 Mar 2018 03:50:44 -0500
Received: from DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) by DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Sun, 18 Mar 2018 02:50:43 -0600
Received: from DNVEX10N01.corpzone.internalzone.com (10.44.82.192) by DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) with Microsoft SMTP Server (TLS) id 15.0.1347.2 via Frontend Transport; Sun, 18 Mar 2018 02:50:43 -0600
Received: from DNVO365EDGE1.corpzone.internalzone.com (10.44.176.66) by DNVEX10N01.corpzone.internalzone.com (10.44.82.192) with Microsoft SMTP Server (TLS) id 14.3.361.1; Sun, 18 Mar 2018 02:50:43 -0600
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (10.44.176.242) by edge.mcafee.com (10.44.176.66) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Sun, 18 Mar 2018 02:50:42 -0600
Received: from BN6PR16MB1425.namprd16.prod.outlook.com (10.172.207.19) by BN6PR16MB1585.namprd16.prod.outlook.com (10.172.208.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.588.14; Sun, 18 Mar 2018 08:50:41 +0000
Received: from BN6PR16MB1425.namprd16.prod.outlook.com ([10.172.207.19]) by BN6PR16MB1425.namprd16.prod.outlook.com ([10.172.207.19]) with mapi id 15.20.0588.016; Sun, 18 Mar 2018 08:50:41 +0000
From: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>
To: "tram@ietf.org" <tram@ietf.org>
Thread-Topic: [tram] I-D Action: draft-ietf-tram-turnbis-15.txt
Thread-Index: AQHTvpVCIExz03qGwU2I9I0I/uh+eqPVrxXQ
Date: Sun, 18 Mar 2018 08:50:41 +0000
Message-ID: <BN6PR16MB1425D61744AC7480972C800AEAD50@BN6PR16MB1425.namprd16.prod.outlook.com>
References: <152136260256.18150.10551009018364033510@ietfa.amsl.com>
In-Reply-To: <152136260256.18150.10551009018364033510@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 11.0.200.100
dlp-reaction: no-action
authentication-results: spf=none (sender IP is ) smtp.mailfrom=TirumaleswarReddy_Konda@McAfee.com; 
x-originating-ip: [31.55.36.73]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR16MB1585; 7:E4DOxl9d2YbkLN9sVl0nWRw2POGzdhmNThXDmbEVKUmilOu//4Jjf4x2mGYQzMMXMCjpfY4Sk+Ztp650F/YxIGvJi5D5pafB9OqEztBv5dobLgPyyZOGxLtKPEV3ZqJLwUM2752zufhv0mEPXZhv2seOPvFrV7jPXAcr1UKZdmWuFGZ0Srt9I6R0QG38MH/+YXZLaKvELztcf4T+RAVZgf6+F4gzPCJJR7Qu9tjc9lfqvDTSnVBldv6I7we7sVZG
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 0927d5b6-2e5e-450c-4912-08d58cad5434
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BN6PR16MB1585; 
x-ms-traffictypediagnostic: BN6PR16MB1585:
x-microsoft-antispam-prvs: <BN6PR16MB158580327D314E80EA0E783BEAD50@BN6PR16MB1585.namprd16.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3002001)(3231221)(944501300)(52105095)(10201501046)(93006095)(93001095)(6041310)(20161123558120)(20161123560045)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(6072148)(201708071742011); SRVR:BN6PR16MB1585; BCL:0; PCL:0; RULEID:; SRVR:BN6PR16MB1585; 
x-forefront-prvs: 06157D541C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(396003)(39380400002)(39850400004)(366004)(346002)(13464003)(189003)(199004)(377424004)(32952001)(81166006)(229853002)(102836004)(7696005)(72206003)(5660300001)(105586002)(14454004)(6116002)(3846002)(2351001)(3660700001)(6436002)(9686003)(66066001)(2501003)(25786009)(76176011)(55016002)(1730700003)(106356001)(68736007)(3280700002)(478600001)(86362001)(186003)(77096007)(97736004)(6916009)(316002)(26005)(53546011)(80792005)(6306002)(2950100002)(8676002)(305945005)(5640700003)(74316002)(966005)(81156014)(7736002)(2900100001)(53936002)(33656002)(6246003)(2906002)(99286004)(8936002)(6506007)(85282002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR16MB1585; H:BN6PR16MB1425.namprd16.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: McAfee.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: gtsqPY9hlr+QfR/tZ4EbUKH4/G3pCay31+vlrGCo8WKFOONaXo0vFnZ1ZYMREClEs0+iLgS6JkDyT6E/vvSSUJjyv3ER5Pl2bpu2z6VfYAeOwchayVMctYzeUPyOabKWMqx7EeAvFYn+LriX8VykvR4Xe6rHSLPvzooWCAIG+kW1Pg0QP4eazmPNaSc1ROv7Mo59hPqDV1ID2h1UEeTchqeYlpzbMHwv+iqGWZGDf4pyNtPdCu60nN4uByZAMJkff0PZ0aHrD5Jx41Fu7f2OiDlML/WEFHxIQNc4qyry5MvBm5mPsl92rcodF0BgU3pkJl3nvVoDhwEojHtivybFvg==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 0927d5b6-2e5e-450c-4912-08d58cad5434
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Mar 2018 08:50:41.1685 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4943e38c-6dd4-428c-886d-24932bc2d5de
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR16MB1585
X-OriginatorOrg: mcafee.com
X-NAI-Spam-Flag: NO
X-NAI-Spam-Threshold: 15
X-NAI-Spam-Score: 0
X-NAI-Spam-Version: 2.3.0.9418 : core <6244> : inlines <6499> : streams <1781638> : uri <2610313>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/CoY_4j8OXteC6HN3kW8Y84Yee6E>
Subject: Re: [tram] I-D Action: draft-ietf-tram-turnbis-15.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Mar 2018 08:50:48 -0000

This revision addresses comments from Mark, Karl and Noriyuki Torii.

-Tiru

> -----Original Message-----
> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of internet-
> drafts@ietf.org
> Sent: Sunday, March 18, 2018 8:43 AM
> To: i-d-announce@ietf.org
> Cc: tram@ietf.org
> Subject: [tram] I-D Action: draft-ietf-tram-turnbis-15.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the TURN Revised and Modernized WG of the
> IETF.
>=20
>         Title           : Traversal Using Relays around NAT (TURN): Relay=
 Extensions
> to Session Traversal Utilities for NAT (STUN)
>         Authors         : Tirumaleswar Reddy
>                           Alan Johnston
>                           Philip Matthews
>                           Jonathan Rosenberg
> 	Filename        : draft-ietf-tram-turnbis-15.txt
> 	Pages           : 84
> 	Date            : 2018-03-18
>=20
> Abstract:
>    If a host is located behind a NAT, then in certain situations it can
>    be impossible for that host to communicate directly with other hosts
>    (peers).  In these situations, it is necessary for the host to use
>    the services of an intermediate node that acts as a communication
>    relay.  This specification defines a protocol, called TURN (Traversal
>    Using Relays around NAT), that allows the host to control the
>    operation of the relay and to exchange packets with its peers using
>    the relay.  TURN differs from some other relay control protocols in
>    that it allows a client to communicate with multiple peers using a
>    single relay address.
>=20
>    The TURN protocol was designed to be used as part of the ICE
>    (Interactive Connectivity Establishment) approach to NAT traversal,
>    though it also can be used without ICE.
>=20
>    This document obsoletes RFC 5766 and RFC 6156.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tram-turnbis/
>=20
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-tram-turnbis-15
> https://datatracker.ietf.org/doc/html/draft-ietf-tram-turnbis-15
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tram-turnbis-15
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram


From nobody Sun Mar 18 17:59:33 2018
Return-Path: <torii0573@gmail.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2C03129C70 for <tram@ietfa.amsl.com>; Sun, 18 Mar 2018 17:59:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EZnODSIeEY6X for <tram@ietfa.amsl.com>; Sun, 18 Mar 2018 17:59:29 -0700 (PDT)
Received: from mail-ot0-x22e.google.com (mail-ot0-x22e.google.com [IPv6:2607:f8b0:4003:c0f::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36B74126C22 for <tram@ietf.org>; Sun, 18 Mar 2018 17:59:29 -0700 (PDT)
Received: by mail-ot0-x22e.google.com with SMTP id y11-v6so15723688otg.0 for <tram@ietf.org>; Sun, 18 Mar 2018 17:59:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1ACz2LxDaIYlJaJKMQh9DS/6iwjlBWuuGG7gSqCvUyY=; b=J2+FTc8pWiIrnud7+4Bn47vTQ7eWuk84In2b70czp9LZzkCUejVkLGNiMDYQws315E 1b1gvoJtQvzHTkSRmU7D4GrbJj52jo6yfi0RGcb321ynzHRabR6Hzciw1AZIp6LzLHWg cf/gc9pQZB+XA26TSrjTmDD4ugi9zYAkR8FcdhFh9sHBHz8pagy76+ci0sD6/NFqpVxW iioKbgLd5e7nVNaa6Qw6EzDylG77txEmRL65u3YUgSvDdQ1k3puo2aOh3V6Elj912EJY rNRVNTs/2qNX3hjLxnjM8iUN7dSL7x3/ZV3iVxLPC9Yb0eHEbznnRWF4wdBsdT1bEgx5 16Pw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1ACz2LxDaIYlJaJKMQh9DS/6iwjlBWuuGG7gSqCvUyY=; b=XLbXoi/lJH8v7HW/VZWA+ewugcXbTcxV/ysZZGnrn9iSZ8PUvk4rykBgt5NU4sY9UN rw2AcirvozlDygh5w5af4u6CkS9iP1JEWnGHSPyJxrP1pqndNrH9EfofQPhb3deX6GfX AESLa1AeUcI8Nm+xz6fYGjlLxgfICp2JFuA3plWu0wwNzhFV/87u+TOomRsSCNmTb4F3 SVL8GL4vz/Z5YQH1L6BAfyd1zjcqFJkZNwbGaEJErvMjpabEvZJisvQNTuiDyc/cBS7A UDpw+NjBzfW9g+q+hXgfnnZmZYESnNPV90QqfWcAPhq/GI96OdWP5uZRPZNPaIUrvFo2 Rlmg==
X-Gm-Message-State: AElRT7GKsmIttnOVJZYd/9DN+blZ9ZRqLXHpUxefBjMQqqxeHCqgn9af rKX3R/mcNPWaLbVG/EOaCoihuV02psphAHWBJCw=
X-Google-Smtp-Source: AG47ELuWTIyb+5Lutd+YNqV9Zdj8Dp0vGq4ndxd/X0jWlEwJqB/jYPSXhSKou2vNLyilLhfsWCG3sIFoXu7m4MtUvKc=
X-Received: by 2002:a9d:222a:: with SMTP id o39-v6mr6858438ota.176.1521421168509;  Sun, 18 Mar 2018 17:59:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.115.209 with HTTP; Sun, 18 Mar 2018 17:59:28 -0700 (PDT)
In-Reply-To: <BN6PR16MB1425D61744AC7480972C800AEAD50@BN6PR16MB1425.namprd16.prod.outlook.com>
References: <152136260256.18150.10551009018364033510@ietfa.amsl.com> <BN6PR16MB1425D61744AC7480972C800AEAD50@BN6PR16MB1425.namprd16.prod.outlook.com>
From: Noriyuki Torii <torii0573@gmail.com>
Date: Mon, 19 Mar 2018 09:59:28 +0900
Message-ID: <CABEjbR+uJQKegDWSncE5yM1sp=E+d0sHFdydhiGfyYS2U2n7Nw@mail.gmail.com>
To: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@mcafee.com>
Cc: "tram@ietf.org" <tram@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/UvWROusGNjGiXkAMm9hc-ku3kT8>
Subject: Re: [tram] I-D Action: draft-ietf-tram-turnbis-15.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Mar 2018 00:59:31 -0000

Hi Tiru,

I checked updated I-D and found some more points in section 12 below.

>      0x4000 through 0x4FFF: These values are the allowed channel
>      numbers (16,384 possible values).
                ~~~~~~
This value also need to be amended to 4,096.

>      0x8000 through 0xFFFF: These values are reserved for future use.

This line can be removed now because the previous sentence imply it, too.

And also, I think it may be preferable if the following paragraph is updated
so as to alignment to RFC 7983.

>   Because of this division, ChannelData messages can be distinguished
>   from STUN-formatted messages (e.g., Allocate request, Send
>   indication, etc.) by examining the first two bits of the message:
>
>      0b00: STUN-formatted message (since the first two bits of a STUN-
>      formatted message are always zero).
>
>      0b01: ChannelData message (since the channel number is the first
>      field in the ChannelData message and channel numbers fall in the
>      range 0x4000 - 0x7FFF).
>
>      0b10: Reserved
>
>      0b11: Reserved
>
>   The reserved values may be used in the future to extend the range of
>   channel numbers.  Thus, an implementation MUST NOT assume that a TURN
>   message always starts with a 0 bit.

I guess it could be

    According to RFC 7983, ChannelData messages can be distinguished
    from other multiplexed protocols by examining the first byte of the
    message:

          [0..3]  STUN
        [16..19]  ZRTP
        [20..63]  DTLS
        [64..79]  TURN Channel
      [128..191]  RTP/RTCP
          others  reserved, MUST be dropped and an alert MAY be logged

    Reserved values may be used in the future by other protocols.
    Thus, an implementation MUST comply the discrimination above.


Finally, in section 18, the example Refresh request in the diagram of the
page 67 doesn't have the PASSWORD-ALGORITHMS attribute nevertheless
it has the PASSWORD-ALGORITHM attributes, also need to be fixed.

Regards,
Noriyuki Torii

----------------

2018-03-18 17:50 GMT+09:00 Konda, Tirumaleswar Reddy
<TirumaleswarReddy_Konda@mcafee.com>:
> This revision addresses comments from Mark, Karl and Noriyuki Torii.
>
> -Tiru
>
>> -----Original Message-----
>> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of internet-
>> drafts@ietf.org
>> Sent: Sunday, March 18, 2018 8:43 AM
>> To: i-d-announce@ietf.org
>> Cc: tram@ietf.org
>> Subject: [tram] I-D Action: draft-ietf-tram-turnbis-15.txt
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> This draft is a work item of the TURN Revised and Modernized WG of the
>> IETF.
>>
>>         Title           : Traversal Using Relays around NAT (TURN): Relay Extensions
>> to Session Traversal Utilities for NAT (STUN)
>>         Authors         : Tirumaleswar Reddy
>>                           Alan Johnston
>>                           Philip Matthews
>>                           Jonathan Rosenberg
>>       Filename        : draft-ietf-tram-turnbis-15.txt
>>       Pages           : 84
>>       Date            : 2018-03-18
>>
>> Abstract:
>>    If a host is located behind a NAT, then in certain situations it can
>>    be impossible for that host to communicate directly with other hosts
>>    (peers).  In these situations, it is necessary for the host to use
>>    the services of an intermediate node that acts as a communication
>>    relay.  This specification defines a protocol, called TURN (Traversal
>>    Using Relays around NAT), that allows the host to control the
>>    operation of the relay and to exchange packets with its peers using
>>    the relay.  TURN differs from some other relay control protocols in
>>    that it allows a client to communicate with multiple peers using a
>>    single relay address.
>>
>>    The TURN protocol was designed to be used as part of the ICE
>>    (Interactive Connectivity Establishment) approach to NAT traversal,
>>    though it also can be used without ICE.
>>
>>    This document obsoletes RFC 5766 and RFC 6156.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-tram-turnbis/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-tram-turnbis-15
>> https://datatracker.ietf.org/doc/html/draft-ietf-tram-turnbis-15
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-tram-turnbis-15
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> tram mailing list
>> tram@ietf.org
>> https://www.ietf.org/mailman/listinfo/tram
>
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram


From nobody Mon Mar 19 03:51:09 2018
Return-Path: <sperreault@jive.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 798DC12751F for <tram@ietfa.amsl.com>; Mon, 19 Mar 2018 03:51:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=jive.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yl4SrHrj42Nl for <tram@ietfa.amsl.com>; Mon, 19 Mar 2018 03:51:04 -0700 (PDT)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AF57126E64 for <tram@ietf.org>; Mon, 19 Mar 2018 03:51:04 -0700 (PDT)
Received: by mail-oi0-x235.google.com with SMTP id 23so3316447oir.11 for <tram@ietf.org>; Mon, 19 Mar 2018 03:51:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jive.com; s=google; h=mime-version:from:date:message-id:subject:to:cc; bh=dqmRr/3kzdiAyYdNW2udkO3hMdUtI9smollGkLsV8Hs=; b=dRwqYkKLIWveZzTv41UIXwVZxuEr0CjSXwhym2VknE/8QkTPHba59XZ3MI/DfCvFIw ka2eZZpW+8FR26NdGSzBuVN+8ZmbgLHHP1eTiSH1qEvqMBj/k+2dSX0R3/tMzTNl/Aip QDbOokd1oGo4TF6F58eCU01jtniUlQBfF+sUeLcoOlKy7BWyYsJYOseB3/N0rwhqJRxO 8VrjrwAG8m0hQR8Rym2JxSAIqZyT6ISe8fkGZJopnhqbVkW4a2h+e9NyAuPHIWhwfoXi zmIxoWaQQPJgglePxyeYwY9LwbU//2DPv73di44qtdKfR/nT8IIYFEYsTM7Bi0Z/T+9/ FcFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=dqmRr/3kzdiAyYdNW2udkO3hMdUtI9smollGkLsV8Hs=; b=sokM76wE9FWQcfDvQSY1hShrSgJX4GB8zv7ZXa9gFID35vIJRPmWjia0Lly7F/tkrG AJ2g4DXq78Hmku/1LvWnJulttciNAZ9NGkHFRiynrZlIQgkmYQVV4lxpE4JSOPNLzAA2 4ZCCLToInAf4bFsI+ET34lbcqvckbSJdsJ/cLY9EFTloEN0UkcSFhYKHJpKkJzRPorzu 21IqUybLqDUFB/1mfnpAZP4Y3Kz/1DbCDlLv3znp6HhNUJYrythsWMVKqJl9Y5vBPI3d NXZVnSkP8sksbwzem1P1OACWPN0onOVxxKGIntevdP3/EUu0j299b0m3YtVReVyE+KEX /vPQ==
X-Gm-Message-State: AElRT7FIzxWTfX1/SjnuE5d+ZP4xslKdWJ1hoDrz/RPbmuHIxyEJer+t PxLPbFDDdPFMRLwfuWuryqOzE8BGY6zwNz8fmAsIP79C
X-Google-Smtp-Source: AG47ELurPcZepcjBNif8+j1PvbQf8cVVnA5cPdZdWAaivllPaM9CbWQdIDb7q7XTUWGiNkxJMzVvaA57mDPVg9XCFZ0=
X-Received: by 10.202.217.9 with SMTP id q9mr6523022oig.8.1521456663049; Mon, 19 Mar 2018 03:51:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.203.132 with HTTP; Mon, 19 Mar 2018 03:50:42 -0700 (PDT)
From: Simon Perreault <sperreault@jive.com>
Date: Mon, 19 Mar 2018 06:50:42 -0400
Message-ID: <CANO7kWDd8NZ=svBONwzo6sE5YH3Y5MAdWFP2CQMiTg7M-b47AQ@mail.gmail.com>
To: tram@ietf.org
Cc: Cullen Jennings <fluffy@cisco.com>, Eric Rescorla <ekr@rtfm.com>
Content-Type: multipart/alternative; boundary="001a113cd400f16fd10567c1bb6b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/9J77ARjKaHXXKYcLL2fhnzDc5ko>
Subject: [tram] Allow TURN to forward inbound connectivity checks without permission
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Mar 2018 10:51:05 -0000

--001a113cd400f16fd10567c1bb6b
Content-Type: text/plain; charset="UTF-8"

Tramsters,

$subject is an very interesting idea from EKR presented today by Cullen in
DISPATCH. Could/should we do this in TURN-bis? This could make TURN *much*
more attractive for certain use cases that require fewer round trips...

Simon

--001a113cd400f16fd10567c1bb6b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Tramsters,</div><div><br></div><div>$subject is an ve=
ry interesting idea from EKR presented today by Cullen in DISPATCH. Could/s=
hould we do this in TURN-bis? This could make TURN *much* more attractive f=
or certain use cases that require fewer round trips...</div><div><br></div>=
<div>Simon</div></div>

--001a113cd400f16fd10567c1bb6b--


From nobody Mon Mar 19 13:50:14 2018
Return-Path: <brandon.williams@akamai.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1007A12D93F for <tram@ietfa.amsl.com>; Mon, 19 Mar 2018 13:50:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yKXfR77sF3zP for <tram@ietfa.amsl.com>; Mon, 19 Mar 2018 13:50:11 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DDEF129C59 for <tram@ietf.org>; Mon, 19 Mar 2018 13:50:11 -0700 (PDT)
Received: from pps.filterd (m0050096.ppops.net [127.0.0.1]) by m0050096.ppops.net-00190b01. (8.16.0.22/8.16.0.22) with SMTP id w2JKlJHr025454; Mon, 19 Mar 2018 20:50:09 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=subject : to : cc : references : from : message-id : date : mime-version : in-reply-to : content-type : content-transfer-encoding; s=jan2016.eng; bh=sy/7LZeSLHTkfqwpGdPBZBvkYTJmh/7J/yyKFX5Mphs=; b=X9q9BJk9R4LAk8mQYR1KH4CtHoTK41jj1iNcrmHsXOUfmfmpFW0req2W/yL5Pv+oM1lG U086foSaGztNtXWvZXpwnCEnAqQbI3R+TOXJywQyEQYOdM2wpldiIzd/1/M3m/HoPxxu FP0KdJ+abMbEpP0IMK1wZxBZ3TXH+l6p8HG5B0CdcHhYHk0JBpFKjQHvlcpRVH9Wi05O RHfQZEl1gAOHTm9/YqWAvpyk1VqwlUWNODV3DiW75XX+51BIUZ8ZcLK4gHH3QL+3Z0mq Eaq8OaDABOJSM8alL/kYQaCVUqAs18jBBSb81P2UXFxVSRysZMQ0DhLZQkuWQRRYuud8 hw== 
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18]) by m0050096.ppops.net-00190b01. with ESMTP id 2grvabpchn-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 19 Mar 2018 20:50:09 +0000
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w2JKlPAG016717; Mon, 19 Mar 2018 16:50:08 -0400
Received: from prod-mail-relay11.akamai.com ([172.27.118.250]) by prod-mail-ppoint1.akamai.com with ESMTP id 2grxbufym7-1; Mon, 19 Mar 2018 16:50:08 -0400
Received: from [172.28.118.62] (bowill.kendall.corp.akamai.com [172.28.118.62]) by prod-mail-relay11.akamai.com (Postfix) with ESMTP id BA1D332B5D; Mon, 19 Mar 2018 20:50:08 +0000 (GMT)
To: Simon Perreault <sperreault@jive.com>, tram@ietf.org
Cc: Cullen Jennings <fluffy@cisco.com>, Eric Rescorla <ekr@rtfm.com>
References: <CANO7kWDd8NZ=svBONwzo6sE5YH3Y5MAdWFP2CQMiTg7M-b47AQ@mail.gmail.com>
From: Brandon Williams <brandon.williams@akamai.com>
Message-ID: <c9ef837c-bf7c-decb-9542-8a9ddeda67fd@akamai.com>
Date: Mon, 19 Mar 2018 16:50:02 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CANO7kWDd8NZ=svBONwzo6sE5YH3Y5MAdWFP2CQMiTg7M-b47AQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-19_12:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803190223
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-19_12:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803190223
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/4LKQXRLbet-yscQAEoBA7R9UBU8>
Subject: Re: [tram] Allow TURN to forward inbound connectivity checks without permission
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Mar 2018 20:50:13 -0000

The idea reminds me of the ufrag permissions draft that Justin and I put 
together a few years ago. It didn't generate much interest at the time, 
but maybe it's time to give it another look?

https://tools.ietf.org/html/draft-williams-tram-ufrag-permission-00

Not quite "forward without permission", but close.

In addition, some of the other parts of the new media stack deck (i.e. 
ICN and controller-based architecture) make me think of the discussions 
some of us have had about trying to allow TURN servers to act as a 
sort-of virtual mutlicast node.

--Brandon

On 03/19/2018 06:50 AM, Simon Perreault wrote:
> Tramsters,
> 
> $subject is an very interesting idea from EKR presented today by Cullen 
> in DISPATCH. Could/should we do this in TURN-bis? This could make TURN 
> *much* more attractive for certain use cases that require fewer round 
> trips...
> 
> Simon
> 
> 
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram
> 


From nobody Mon Mar 19 15:43:13 2018
Return-Path: <nohlmeier@mozilla.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8778124BAC for <tram@ietfa.amsl.com>; Mon, 19 Mar 2018 15:43:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O_HaTzvtXSY7 for <tram@ietfa.amsl.com>; Mon, 19 Mar 2018 15:43:08 -0700 (PDT)
Received: from mail-wr0-x22b.google.com (mail-wr0-x22b.google.com [IPv6:2a00:1450:400c:c0c::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F0081205F0 for <tram@ietf.org>; Mon, 19 Mar 2018 15:43:08 -0700 (PDT)
Received: by mail-wr0-x22b.google.com with SMTP id z73so15991549wrb.0 for <tram@ietf.org>; Mon, 19 Mar 2018 15:43:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=ZjUcZcgxZvUz3x0Ia2wlgCZ6eKbm7z7eJztxTouyvIE=; b=Gl6tax5cyjL0k6XxFxJST4b/7Z5+UT84eav75E2/Quig/c/U2HJIZbokqTNuGEFjlv pHr9623jdbhOzazgluyECrR+/vJ6QQFtaNF819F6jQvlM+kzBQ+G6F3wvcAGO7MYU3Os RZyya4w3Ud+D6F5pa4VuUN7RMwnodQ2sQwPmk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=ZjUcZcgxZvUz3x0Ia2wlgCZ6eKbm7z7eJztxTouyvIE=; b=Cd19bbOC3LcvoplENjB6tY4QrETvWcPjlZkrpCLnuvDOj7uRubG9GOogNwN31w+nJx 44AnQbYQKO7G/IfYHFv/9Towk3OpXbJWUGf9haSF0WbEUg3fY73jjUaRpfwpXXWF1Yn1 8MUDnkE943kHhO5L2x9W/GL/X5Jpm05iX4V/jQLuGUaE6N89PNF4jBlXN2xuaqSswd85 3999LgBtSF4telwMWrCUd4Xt7jrH9XxWK8MMkn//Q/S3cxQJa0C0MV0aDZnO98SBPeRr MqQamjpn4gm2kC1Mo4ddpTBG5MMz+o9JiekF/zc22Rmzf2gup8WMus1QGoKA0om05kBT Z9Bg==
X-Gm-Message-State: AElRT7GSU0/byMfO1IoCOens/vF/T+c9X2QsuRCU/8r9pDyWAR31QUcG 4qLudXC/f0iTs9lLm7gOHg/jrQ==
X-Google-Smtp-Source: AG47ELvuFlqHuOcFuRZR4Cwu3EwtpQuwtAyYve+HeBiSmCswaOoig4HvNwJOqb8/JX3CjER4mV/hNg==
X-Received: by 10.223.163.221 with SMTP id m29mr11689842wrb.4.1521499386787; Mon, 19 Mar 2018 15:43:06 -0700 (PDT)
Received: from ?IPv6:2001:67c:1232:144:6d39:9314:376c:ca3b? ([2001:67c:1232:144:6d39:9314:376c:ca3b]) by smtp.gmail.com with ESMTPSA id q13sm301588wrg.56.2018.03.19.15.43.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Mar 2018 15:43:05 -0700 (PDT)
From: Nils Ohlmeier <nohlmeier@mozilla.com>
Message-Id: <E3AB81FC-D841-47A6-A0E2-775461779770@mozilla.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_01348824-B04E-4D72-AC19-8E3004E6EE1D"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Mon, 19 Mar 2018 22:43:04 +0000
In-Reply-To: <c9ef837c-bf7c-decb-9542-8a9ddeda67fd@akamai.com>
Cc: Simon Perreault <sperreault@jive.com>, tram@ietf.org, Cullen Jennings <fluffy@cisco.com>, Eric Rescorla <ekr@rtfm.com>
To: Brandon Williams <brandon.williams@akamai.com>
References: <CANO7kWDd8NZ=svBONwzo6sE5YH3Y5MAdWFP2CQMiTg7M-b47AQ@mail.gmail.com> <c9ef837c-bf7c-decb-9542-8a9ddeda67fd@akamai.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/X1QlRhlWXMgTQuboq-VObxFzACM>
Subject: Re: [tram] Allow TURN to forward inbound connectivity checks without permission
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Mar 2018 22:43:12 -0000

--Apple-Mail=_01348824-B04E-4D72-AC19-8E3004E6EE1D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

It does indeed.

I think in general this is worth looking into.

I also like the idea of simply forwarding all binding requests to the =
TURN client. Because 1) it does not expose the ufrag to the network when =
talking to the TURN server. And 2) it=E2=80=99s easier for the TURN =
server to just check for the STUN request type and hot have to parse for =
the ufrag attribute as well.

One question which comes to my mind is if the TURN server at some point, =
e.g. after receiving the permission request, stops forwarding the =
binding requests blindly?

Best
  Nils Ohlmeier

> On Mar 19, 2018, at 20:50, Brandon Williams =
<brandon.williams@akamai.com> wrote:
>=20
> The idea reminds me of the ufrag permissions draft that Justin and I =
put together a few years ago. It didn't generate much interest at the =
time, but maybe it's time to give it another look?
>=20
> https://tools.ietf.org/html/draft-williams-tram-ufrag-permission-00
>=20
> Not quite "forward without permission", but close.
>=20
> In addition, some of the other parts of the new media stack deck (i.e. =
ICN and controller-based architecture) make me think of the discussions =
some of us have had about trying to allow TURN servers to act as a =
sort-of virtual mutlicast node.
>=20
> --Brandon
>=20
> On 03/19/2018 06:50 AM, Simon Perreault wrote:
>> Tramsters,
>> $subject is an very interesting idea from EKR presented today by =
Cullen in DISPATCH. Could/should we do this in TURN-bis? This could make =
TURN *much* more attractive for certain use cases that require fewer =
round trips...
>> Simon
>> _______________________________________________
>> tram mailing list
>> tram@ietf.org
>> https://www.ietf.org/mailman/listinfo/tram
>=20
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram


--Apple-Mail=_01348824-B04E-4D72-AC19-8E3004E6EE1D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEQ5rmmyEsAeItlZquY2o/VmzJ+KEFAlqwPPgACgkQY2o/VmzJ
+KGiDBAAwmIhxIg+piSWxVxD5703DX8beFzp7rWnBn/xhTNkxMuIRVkaEN8umc44
PD1RR8aQT07NhGzbpaC3OXlQ3gUPmiQSCYeEOHtg4QZtHRrsZk36UeCAGh+/SBWM
JdseqKKXlubkkSR9AE/51aU5r5K8byUmT38xUK+u+a0OT5VpEsmXQ7zMDqe6zpwE
d8OGPjdeQaFVfxfgwlxc4STK+YDWSFC0RCQENOmvB8j7sWysflGWOVBzBafmeqv1
Nkw9AbJ87mc3wV5NW63nt8RspSg81kG79hMEDUHeCgpHn7B7uIiBRFbGgL7At2d+
1lRK6mYKe+N23EEB2lBRoTfXAtW0O11hEQUDcEq1hyYADzxLWFkEvNbvto/7ocmE
WyPFJ/3GAB1SPB3LJC9cb3yzTlu3PLuCoE2xzeOAw69l/healLgGxYZsgmEeD8Xt
lz5iVkc0lj/Nvi85uX+RuPjqKofEXulm1opSdLLYbf6D+yHdcz9k60RtrpbdebIL
azL+l8Uq6sF8+UdmsV7tb3ZgG31mOqIfmzJ3WJkiSJUoRn+nOosCNc/TpkjvIey3
FaIGAddTjo9cWB1Hr67qPVdXJMM/gJWYTWNmxQHjuqDa2xJvy6ss/d+FQ3Y3fJKz
U23HCmUHT5zj1ZA2nwu4diwU2rY40TQbcU/arF2wPtWJfvBRE4M=
=wE6d
-----END PGP SIGNATURE-----

--Apple-Mail=_01348824-B04E-4D72-AC19-8E3004E6EE1D--


From nobody Tue Mar 20 03:08:26 2018
Return-Path: <sperreault@jive.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18AD8127337 for <tram@ietfa.amsl.com>; Tue, 20 Mar 2018 03:08:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=jive.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ss8N1OBpplTV for <tram@ietfa.amsl.com>; Tue, 20 Mar 2018 03:08:23 -0700 (PDT)
Received: from mail-ot0-x236.google.com (mail-ot0-x236.google.com [IPv6:2607:f8b0:4003:c0f::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFAE4126B6D for <tram@ietf.org>; Tue, 20 Mar 2018 03:08:20 -0700 (PDT)
Received: by mail-ot0-x236.google.com with SMTP id t2-v6so1071666otj.4 for <tram@ietf.org>; Tue, 20 Mar 2018 03:08:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jive.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NdfGd6Cl9Vga7hZvWwEIYlyF5KoOW7O/k5UVNyunKXQ=; b=NQkELG9+p0neihNCTeSWWQUmJVyHV3jNvxvLIMdu5bYuIaAsnWaIFh1bukxV1uErRt LdJH2JMBaw1XAqsIsloIlMx+aP5pSR8S0dzsp2BFxPOqYuSVLUx183N9D9KyqXhB5Nhk E1j9NupZvo4axg3RUGA91C+2uuh3ba0/RTKiT3ozKB0rLsPWPFt3H/7ditvPrVrN8to5 axd6bvz3WvpMzhuKwvfUkgcMmJYukIIVi2TQ5xX4MAybOnrwTgvVLpcdCrKHA8rd/5NH mSVyUlvSTb7NIX2p1p+5Etz8SSJsvjeoF4J9qd8NtIywHKKAItuaLU2zJu0T35SorTup qUYg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NdfGd6Cl9Vga7hZvWwEIYlyF5KoOW7O/k5UVNyunKXQ=; b=n12Pgz0YIJEyoZXGlLcor60ecbqKIvbqsLjD2DdSwsstBGG8JHHZMnkVcOKLRdzFgc IbmFxqeoO0IctJFvSfEAYAefB9T6PJwB8B4mxZMu4d17YjuWNLst47RpmiOKY/Zw7pq4 EkiF9iI03EY/M7gmlWIUemInvVnigVS15ozdHgOR3LMpFPd6jVJESlX47fpBMePPzWHW niWplrNKigAvHb5KiQ2lcEploo6HTcpUJgDtwS55oVd5GfQ5rkV0BbjFN+oTyW3R2AuK /8oBiAcNejh6gG3dohwfHkhf0JYtps0SMyOU8g46TRO3oFl4B+thxNhy//GJuXQl2RQb DSbA==
X-Gm-Message-State: AElRT7FStr1XDIT/MDXX+6gqUTkNoWKd1yfuI+FRsSj9DWOIkZ9BtXsI FxFYqxyP0kf9YFtlI64uPY8usU1qSKRrgOKWih68pg==
X-Google-Smtp-Source: AG47ELv9Zvjhp2dTdtl2rnHJIfJb8Es7UPGauKxWWMZazSRZkJwGaO5f7sVOv4ig1IrdIrIRaPIM01q1tsBkxdid1VM=
X-Received: by 2002:a9d:5262:: with SMTP id q34-v6mr7139059otg.67.1521540499968;  Tue, 20 Mar 2018 03:08:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.203.132 with HTTP; Tue, 20 Mar 2018 03:07:59 -0700 (PDT)
In-Reply-To: <E3AB81FC-D841-47A6-A0E2-775461779770@mozilla.com>
References: <CANO7kWDd8NZ=svBONwzo6sE5YH3Y5MAdWFP2CQMiTg7M-b47AQ@mail.gmail.com> <c9ef837c-bf7c-decb-9542-8a9ddeda67fd@akamai.com> <E3AB81FC-D841-47A6-A0E2-775461779770@mozilla.com>
From: Simon Perreault <sperreault@jive.com>
Date: Tue, 20 Mar 2018 06:07:59 -0400
Message-ID: <CANO7kWA4tmK7Di59tsjvCBoDdh-jW83FxMpqQH1-iSPGLS=mpA@mail.gmail.com>
To: Nils Ohlmeier <nohlmeier@mozilla.com>
Cc: Brandon Williams <brandon.williams@akamai.com>, tram@ietf.org,  Cullen Jennings <fluffy@cisco.com>, Eric Rescorla <ekr@rtfm.com>
Content-Type: multipart/alternative; boundary="0000000000000355420567d54125"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/80e_lAbii1NniRsOrJyFO6M1mUY>
Subject: Re: [tram] Allow TURN to forward inbound connectivity checks without permission
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2018 10:08:25 -0000

--0000000000000355420567d54125
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Wow, I had totally forgotten about ufrag perms!

2018-03-19 22:43 GMT+00:00 Nils Ohlmeier <nohlmeier@mozilla.com>:
>
> I also like the idea of simply forwarding all binding requests to the TUR=
N
> client. Because 1) it does not expose the ufrag to the network when talki=
ng
> to the TURN server. And 2) it=E2=80=99s easier for the TURN server to jus=
t check
> for the STUN request type and hot have to parse for the ufrag attribute a=
s
> well.
>

Same opinion here. The point of permissions is to prevent TURN clients from
being able to run generic servers. It seems like always allowing STUN
packets would preserve this feature while solving the session establishment
latency problem. And would be quite a bit simpler to implement than ufrag
perms. Have your cake, eat it, and eat it a second time.

Also, because this is so simple (just one sentence to specify it!), and
impact potential is so great (make Brandon happy!), I wonder if we
shouldn't simply add it to TURN-bis while there's still time.

One question which comes to my mind is if the TURN server at some point,
> e.g. after receiving the permission request, stops forwarding the binding
> requests blindly?


Because the allocation might be paired with multiple remote candidates, I
think we'd need to always forward STUN blindly.

Simon

--0000000000000355420567d54125
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Wow, I had totally forgotten about ufrag perms!<br><div cl=
ass=3D"gmail_extra"><br><div class=3D"gmail_quote">2018-03-19 22:43 GMT+00:=
00 Nils Ohlmeier <span dir=3D"ltr">&lt;<a href=3D"mailto:nohlmeier@mozilla.=
com" target=3D"_blank">nohlmeier@mozilla.com</a>&gt;</span>:<blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">
I also like the idea of simply forwarding all binding requests to the TURN =
client. Because 1) it does not expose the ufrag to the network when talking=
 to the TURN server. And 2) it=E2=80=99s easier for the TURN server to just=
 check for the STUN request type and hot have to parse for the ufrag attrib=
ute as well.<br></blockquote><div><br></div><div>Same opinion here. The poi=
nt of permissions is to prevent TURN clients from being able to run generic=
 servers. It seems like always allowing STUN packets would preserve this fe=
ature while solving the session establishment latency problem. And would be=
 quite a bit simpler to implement than ufrag perms. Have your cake, eat it,=
 and eat it a second time.</div><div><br></div><div>Also, because this is s=
o simple (just one sentence to specify it!), and impact potential is so gre=
at (make Brandon happy!), I wonder if we shouldn&#39;t simply add it to TUR=
N-bis while there&#39;s still time.</div><div><br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
One question which comes to my mind is if the TURN server at some point, e.=
g. after receiving the permission request, stops forwarding the binding req=
uests blindly?</blockquote></div><br></div><div class=3D"gmail_extra">Becau=
se the allocation might be paired with multiple remote candidates, I think =
we&#39;d need to always forward STUN blindly.</div><div class=3D"gmail_extr=
a"><br></div><div class=3D"gmail_extra">Simon</div></div>

--0000000000000355420567d54125--


From nobody Tue Mar 20 03:31:54 2018
Return-Path: <TirumaleswarReddy_Konda@mcafee.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A47E1242F7 for <tram@ietfa.amsl.com>; Tue, 20 Mar 2018 03:31:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.33
X-Spam-Level: 
X-Spam-Status: No, score=-4.33 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mcafee.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xmBxUpf_RWr1 for <tram@ietfa.amsl.com>; Tue, 20 Mar 2018 03:31:51 -0700 (PDT)
Received: from DNVWSMAILOUT1.mcafee.com (dnvwsmailout1.mcafee.com [161.69.31.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DEE8124207 for <tram@ietf.org>; Tue, 20 Mar 2018 03:31:51 -0700 (PDT)
X-NAI-Header: Modified by McAfee Email Gateway (5500)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mcafee.com; s=s_mcafee; t=1521541893; h=From: To:CC:Subject:Thread-Topic:Thread-Index:Date: Message-ID:References:In-Reply-To:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: dlp-product:dlp-version:dlp-reaction:authentication-results: x-originating-ip:x-ms-publictraffictype:x-microsoft-exchange-diagnostics: x-ms-exchange-antispam-srfa-diagnostics:x-ms-office365-filtering-correlation-id: x-microsoft-antispam:x-ms-traffictypediagnostic: x-microsoft-antispam-prvs:x-exchange-antispam-report-test: x-exchange-antispam-report-cfa-test:x-forefront-prvs: x-forefront-antispam-report:received-spf:x-microsoft-antispam-message-info: spamdiagnosticoutput:spamdiagnosticmetadata: Content-Type:MIME-Version:X-MS-Exchange-CrossTenant-Network-Message-Id: X-MS-Exchange-CrossTenant-originalarrivaltime: X-MS-Exchange-CrossTenant-fromentityheader: X-MS-Exchange-CrossTenant-id:X-MS-Exchange-Transport-CrossTenantHeadersStamped: X-OriginatorOrg:X-NAI-Spam-Flag:X-NAI-Spam-Threshold: X-NAI-Spam-Score:X-NAI-Spam-Version; bh=r 7kD7TGo/6ZbZH50RmwqoS0H7jkB+5C6+qHFBySj2S k=; b=H6Z4dlMzR3H69KqawRstMID0hXOq/1P2eyc6Ump+yeSi /AEjCXLoNipMn4TV6eLLNmrvS2P9jUoy23AxeVqKGuo8bTDy+C mT7cKEy8U0UBwsDA7y9COekFM2wUw1DgZNOnFzulon3+8j9W3i Iai+MoCbdyUbfop616Fw2BBjeKA=
Received: from DNVEXAPP1N06.corpzone.internalzone.com (unknown [10.44.48.90]) by DNVWSMAILOUT1.mcafee.com with smtp (TLS: TLSv1/SSLv3,256bits,ECDHE-RSA-AES256-SHA384) id 6013_483d_a1d60478_b140_497b_8f88_2bf72fe000b6; Tue, 20 Mar 2018 05:31:32 -0500
Received: from DNVEXUSR1N09.corpzone.internalzone.com (10.44.48.82) by DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 20 Mar 2018 04:31:04 -0600
Received: from DNVEXAPP1N04.corpzone.internalzone.com (10.44.48.88) by DNVEXUSR1N09.corpzone.internalzone.com (10.44.48.82) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 20 Mar 2018 04:31:03 -0600
Received: from DNVO365EDGE2.corpzone.internalzone.com (10.44.176.74) by DNVEXAPP1N04.corpzone.internalzone.com (10.44.48.88) with Microsoft SMTP Server (TLS) id 15.0.1347.2 via Frontend Transport; Tue, 20 Mar 2018 04:31:03 -0600
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (10.44.176.242) by edge.mcafee.com (10.44.176.74) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 20 Mar 2018 04:31:02 -0600
Received: from BN6PR16MB1425.namprd16.prod.outlook.com (10.172.207.19) by BN6PR16MB1841.namprd16.prod.outlook.com (10.172.29.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.588.14; Tue, 20 Mar 2018 10:31:00 +0000
Received: from BN6PR16MB1425.namprd16.prod.outlook.com ([10.172.207.19]) by BN6PR16MB1425.namprd16.prod.outlook.com ([10.172.207.19]) with mapi id 15.20.0588.017; Tue, 20 Mar 2018 10:31:00 +0000
From: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>
To: Simon Perreault <sperreault@jive.com>, Nils Ohlmeier <nohlmeier@mozilla.com>
CC: Cullen Jennings <fluffy@cisco.com>, Eric Rescorla <ekr@rtfm.com>, "tram@ietf.org" <tram@ietf.org>, Brandon Williams <brandon.williams@akamai.com>
Thread-Topic: [tram] Allow TURN to forward inbound connectivity checks without permission
Thread-Index: AQHTv3BE7H+lEDCzy0aE6LgkPsBdZKPYCNMAgAAflQCAAL9dgIAABGPg
Date: Tue, 20 Mar 2018 10:31:00 +0000
Message-ID: <BN6PR16MB14253012D6A5EA47A700EE1FEAAB0@BN6PR16MB1425.namprd16.prod.outlook.com>
References: <CANO7kWDd8NZ=svBONwzo6sE5YH3Y5MAdWFP2CQMiTg7M-b47AQ@mail.gmail.com> <c9ef837c-bf7c-decb-9542-8a9ddeda67fd@akamai.com> <E3AB81FC-D841-47A6-A0E2-775461779770@mozilla.com> <CANO7kWA4tmK7Di59tsjvCBoDdh-jW83FxMpqQH1-iSPGLS=mpA@mail.gmail.com>
In-Reply-To: <CANO7kWA4tmK7Di59tsjvCBoDdh-jW83FxMpqQH1-iSPGLS=mpA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 11.0.200.100
dlp-reaction: no-action
authentication-results: spf=none (sender IP is ) smtp.mailfrom=TirumaleswarReddy_Konda@McAfee.com; 
x-originating-ip: [185.125.225.10]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR16MB1841; 7:kih8Q6H6Koes7PZyeanBAMulyfGKadjP/SlloTmATePbv8QDFADwpjPC66YeSGzAy1HAxYlcccQyI3exU7e9nhFDnpdRfXOcrzf4VuciOSC3KYxOTEPs8Vu/C2q58IXK36powLg/NhUNg2vsGWOGIfxPMLj6ebtTt3Mn8ZcrqEPCNXulsP0E9gGn6qGyyleHFxvhZjkCx98/V+1UORcGYhTxqA3iSI2TyiP19rQDRt2dPfwLHKR/n7n42Dbe3Ljk
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: b8794908-ec5d-4780-dfe7-08d58e4dacc6
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BN6PR16MB1841; 
x-ms-traffictypediagnostic: BN6PR16MB1841:
x-microsoft-antispam-prvs: <BN6PR16MB184110417439A3EE5BF55A64EAAB0@BN6PR16MB1841.namprd16.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(158342451672863)(192374486261705)(95692535739014)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3002001)(10201501046)(3231221)(944501309)(52105095)(93006095)(93001095)(6041310)(20161123562045)(20161123558120)(20161123564045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:BN6PR16MB1841; BCL:0; PCL:0; RULEID:; SRVR:BN6PR16MB1841; 
x-forefront-prvs: 061725F016
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39380400002)(366004)(396003)(39860400002)(376002)(346002)(189003)(54094003)(199004)(377424004)(32952001)(76176011)(7696005)(2900100001)(86362001)(97736004)(25786009)(80792005)(4326008)(102836004)(55016002)(7736002)(26005)(6116002)(790700001)(3846002)(68736007)(316002)(54906003)(110136005)(54896002)(6306002)(236005)(33656002)(9686003)(3660700001)(99286004)(53936002)(77096007)(6246003)(186003)(14454004)(2950100002)(74316002)(66066001)(229853002)(8936002)(2906002)(6436002)(93886005)(59450400001)(106356001)(81156014)(81166006)(3280700002)(5660300001)(19609705001)(8676002)(478600001)(6506007)(72206003)(53546011)(105586002)(85282002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR16MB1841; H:BN6PR16MB1425.namprd16.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: McAfee.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: zTGcvgqPvfx2zH5blrJNvqYLJSy1F06+o6W2Q3ViK1GfATrDr+Yg5ufXsAA9ZtbK24cf8ut/+RrC2SGpNIx9lHT34N5ryGAMJcr+K2aqZQoprwv7MSVLiM9vrVtR74AIui1CIWySdLQ2afMAa0rjrqVF0AH9CBi2Fmqrh3NHRrFeyoREgfuRKX6Jd6h8BiCUqGcPZ1kWqtQ522U+nMfZiHHhT8A0TO2XvACRqaGwQvuxSXiX5jpUxotNBq9/bNlrzstreTF+ZS+6mb8LT1512PTVyBQsFraOKsVSEpw0pTUvfJ++OVp+ryO41T5I5mapinjbZCAoTWvYfCdSHnzvzQ==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BN6PR16MB14253012D6A5EA47A700EE1FEAAB0BN6PR16MB1425namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b8794908-ec5d-4780-dfe7-08d58e4dacc6
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Mar 2018 10:31:00.3002 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4943e38c-6dd4-428c-886d-24932bc2d5de
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR16MB1841
X-OriginatorOrg: mcafee.com
X-NAI-Spam-Flag: NO
X-NAI-Spam-Threshold: 15
X-NAI-Spam-Score: 0
X-NAI-Spam-Version: 2.3.0.9418 : core <6245> : inlines <6506> : streams <1781734> : uri <2611579>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/vIXBEB_OSOEf3S-7sQsI-EwloyA>
Subject: Re: [tram] Allow TURN to forward inbound connectivity checks without permission
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2018 10:31:53 -0000

--_000_BN6PR16MB14253012D6A5EA47A700EE1FEAAB0BN6PR16MB1425namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

TmljZSBvcHRpbWl6YXRpb24uDQpXZSBzaG91bGQgYWxzbyBkaXNjdXNzIHRoZSBzZWN1cml0eSBp
bXBsaWNhdGlvbnMsIElmIGFueSBTVFVOIHBhY2tldCBpcyBhbGxvd2VkIGZyb20gYW55b25lIGlu
IHRoZSBJbnRlcm5ldCwgdGhlIFRVUk4gY2xpZW50IGNvdWxkIGJlIHN1YmplY3RlZCB0byBERG9T
IGF0dGFjayAoZS5nLiBzcG9vZmVkIFNUVU4gcGFja2V0cyBmcm9tIGF0dGFja2VycywgY2xpZW50
IHdhc3RlcyBjeWNsZXMgdmFsaWRhdGluZyB0aGUgbWVzc2FnZSBpbnRlZ3JpdHksIGFuZCBjb3Vs
ZCBhbHNvIGJlIHN1YmplY3RlZCB0byBiYW5kd2lkdGgtaG9nZ2luZyBhdHRhY2spLg0KDQotVGly
dQ0KDQpGcm9tOiB0cmFtIFttYWlsdG86dHJhbS1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYg
T2YgU2ltb24gUGVycmVhdWx0DQpTZW50OiBUdWVzZGF5LCBNYXJjaCAyMCwgMjAxOCAxMDowOCBB
TQ0KVG86IE5pbHMgT2hsbWVpZXIgPG5vaGxtZWllckBtb3ppbGxhLmNvbT4NCkNjOiBDdWxsZW4g
SmVubmluZ3MgPGZsdWZmeUBjaXNjby5jb20+OyBFcmljIFJlc2NvcmxhIDxla3JAcnRmbS5jb20+
OyB0cmFtQGlldGYub3JnOyBCcmFuZG9uIFdpbGxpYW1zIDxicmFuZG9uLndpbGxpYW1zQGFrYW1h
aS5jb20+DQpTdWJqZWN0OiBSZTogW3RyYW1dIEFsbG93IFRVUk4gdG8gZm9yd2FyZCBpbmJvdW5k
IGNvbm5lY3Rpdml0eSBjaGVja3Mgd2l0aG91dCBwZXJtaXNzaW9uDQoNCldvdywgSSBoYWQgdG90
YWxseSBmb3Jnb3R0ZW4gYWJvdXQgdWZyYWcgcGVybXMhDQoNCjIwMTgtMDMtMTkgMjI6NDMgR01U
KzAwOjAwIE5pbHMgT2hsbWVpZXIgPG5vaGxtZWllckBtb3ppbGxhLmNvbTxtYWlsdG86bm9obG1l
aWVyQG1vemlsbGEuY29tPj46DQpJIGFsc28gbGlrZSB0aGUgaWRlYSBvZiBzaW1wbHkgZm9yd2Fy
ZGluZyBhbGwgYmluZGluZyByZXF1ZXN0cyB0byB0aGUgVFVSTiBjbGllbnQuIEJlY2F1c2UgMSkg
aXQgZG9lcyBub3QgZXhwb3NlIHRoZSB1ZnJhZyB0byB0aGUgbmV0d29yayB3aGVuIHRhbGtpbmcg
dG8gdGhlIFRVUk4gc2VydmVyLiBBbmQgMikgaXTigJlzIGVhc2llciBmb3IgdGhlIFRVUk4gc2Vy
dmVyIHRvIGp1c3QgY2hlY2sgZm9yIHRoZSBTVFVOIHJlcXVlc3QgdHlwZSBhbmQgaG90IGhhdmUg
dG8gcGFyc2UgZm9yIHRoZSB1ZnJhZyBhdHRyaWJ1dGUgYXMgd2VsbC4NCg0KU2FtZSBvcGluaW9u
IGhlcmUuIFRoZSBwb2ludCBvZiBwZXJtaXNzaW9ucyBpcyB0byBwcmV2ZW50IFRVUk4gY2xpZW50
cyBmcm9tIGJlaW5nIGFibGUgdG8gcnVuIGdlbmVyaWMgc2VydmVycy4gSXQgc2VlbXMgbGlrZSBh
bHdheXMgYWxsb3dpbmcgU1RVTiBwYWNrZXRzIHdvdWxkIHByZXNlcnZlIHRoaXMgZmVhdHVyZSB3
aGlsZSBzb2x2aW5nIHRoZSBzZXNzaW9uIGVzdGFibGlzaG1lbnQgbGF0ZW5jeSBwcm9ibGVtLiBB
bmQgd291bGQgYmUgcXVpdGUgYSBiaXQgc2ltcGxlciB0byBpbXBsZW1lbnQgdGhhbiB1ZnJhZyBw
ZXJtcy4gSGF2ZSB5b3VyIGNha2UsIGVhdCBpdCwgYW5kIGVhdCBpdCBhIHNlY29uZCB0aW1lLg0K
DQpBbHNvLCBiZWNhdXNlIHRoaXMgaXMgc28gc2ltcGxlIChqdXN0IG9uZSBzZW50ZW5jZSB0byBz
cGVjaWZ5IGl0ISksIGFuZCBpbXBhY3QgcG90ZW50aWFsIGlzIHNvIGdyZWF0IChtYWtlIEJyYW5k
b24gaGFwcHkhKSwgSSB3b25kZXIgaWYgd2Ugc2hvdWxkbid0IHNpbXBseSBhZGQgaXQgdG8gVFVS
Ti1iaXMgd2hpbGUgdGhlcmUncyBzdGlsbCB0aW1lLg0KDQpPbmUgcXVlc3Rpb24gd2hpY2ggY29t
ZXMgdG8gbXkgbWluZCBpcyBpZiB0aGUgVFVSTiBzZXJ2ZXIgYXQgc29tZSBwb2ludCwgZS5nLiBh
ZnRlciByZWNlaXZpbmcgdGhlIHBlcm1pc3Npb24gcmVxdWVzdCwgc3RvcHMgZm9yd2FyZGluZyB0
aGUgYmluZGluZyByZXF1ZXN0cyBibGluZGx5Pw0KDQpCZWNhdXNlIHRoZSBhbGxvY2F0aW9uIG1p
Z2h0IGJlIHBhaXJlZCB3aXRoIG11bHRpcGxlIHJlbW90ZSBjYW5kaWRhdGVzLCBJIHRoaW5rIHdl
J2QgbmVlZCB0byBhbHdheXMgZm9yd2FyZCBTVFVOIGJsaW5kbHkuDQoNClNpbW9uDQo=

--_000_BN6PR16MB14253012D6A5EA47A700EE1FEAAB0BN6PR16MB1425namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkRlbmdYaWFuOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAx
IDE7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIgMTUg
NSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IlxARGVuZ1hpYW4i
Ow0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMg
Ki8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBp
bjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZh
bWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJ
e21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1
bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1z
dHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVy
bGluZTt9DQpwLm1zb25vcm1hbDAsIGxpLm1zb25vcm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21z
by1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJn
aW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0
OjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNl
cmlmO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7
fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1m
YW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6
OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29y
ZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUg
bXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2
IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFw
ZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4N
CjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9
IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0
aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5OaWNlIG9wdGltaXphdGlvbi4gPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5XZSBzaG91bGQgYWxzbyBkaXNjdXNzIHRoZSBz
ZWN1cml0eSBpbXBsaWNhdGlvbnMsIElmIGFueSBTVFVOIHBhY2tldCBpcyBhbGxvd2VkIGZyb20g
YW55b25lIGluIHRoZSBJbnRlcm5ldCwgdGhlIFRVUk4gY2xpZW50IGNvdWxkIGJlIHN1YmplY3Rl
ZCB0byBERG9TIGF0dGFjayAoZS5nLiBzcG9vZmVkIFNUVU4gcGFja2V0cyBmcm9tIGF0dGFja2Vy
cywgY2xpZW50IHdhc3RlcyBjeWNsZXMgdmFsaWRhdGluZyB0aGUNCiBtZXNzYWdlIGludGVncml0
eSwgYW5kIGNvdWxkIGFsc28gYmUgc3ViamVjdGVkIHRvIGJhbmR3aWR0aC1ob2dnaW5nIGF0dGFj
aykuIDxvOnA+DQo8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi1UaXJ1PG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48YSBuYW1lPSJfTWFpbEVuZENvbXBvc2UiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9hPjwvcD4NCjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxFbmRDb21wb3NlIj48
L3NwYW4+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEu
NXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRl
cjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAw
aW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPkZyb206PC9iPiB0cmFtIFttYWlsdG86
dHJhbS1ib3VuY2VzQGlldGYub3JnXSA8Yj5PbiBCZWhhbGYgT2YNCjwvYj5TaW1vbiBQZXJyZWF1
bHQ8YnI+DQo8Yj5TZW50OjwvYj4gVHVlc2RheSwgTWFyY2ggMjAsIDIwMTggMTA6MDggQU08YnI+
DQo8Yj5Ubzo8L2I+IE5pbHMgT2hsbWVpZXIgJmx0O25vaGxtZWllckBtb3ppbGxhLmNvbSZndDs8
YnI+DQo8Yj5DYzo8L2I+IEN1bGxlbiBKZW5uaW5ncyAmbHQ7Zmx1ZmZ5QGNpc2NvLmNvbSZndDs7
IEVyaWMgUmVzY29ybGEgJmx0O2VrckBydGZtLmNvbSZndDs7IHRyYW1AaWV0Zi5vcmc7IEJyYW5k
b24gV2lsbGlhbXMgJmx0O2JyYW5kb24ud2lsbGlhbXNAYWthbWFpLmNvbSZndDs8YnI+DQo8Yj5T
dWJqZWN0OjwvYj4gUmU6IFt0cmFtXSBBbGxvdyBUVVJOIHRvIGZvcndhcmQgaW5ib3VuZCBjb25u
ZWN0aXZpdHkgY2hlY2tzIHdpdGhvdXQgcGVybWlzc2lvbjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPldvdywgSSBoYWQgdG90YWxseSBmb3Jnb3R0ZW4gYWJv
dXQgdWZyYWcgcGVybXMhPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+MjAx
OC0wMy0xOSAyMjo0MyBHTVQmIzQzOzAwOjAwIE5pbHMgT2hsbWVpZXIgJmx0OzxhIGhyZWY9Im1h
aWx0bzpub2hsbWVpZXJAbW96aWxsYS5jb20iIHRhcmdldD0iX2JsYW5rIj5ub2hsbWVpZXJAbW96
aWxsYS5jb208L2E+Jmd0Ozo8bzpwPjwvbzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3Jk
ZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAw
aW4gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5JIGFsc28gbGlrZSB0aGUgaWRlYSBvZiBzaW1wbHkgZm9yd2FyZGluZyBhbGwg
YmluZGluZyByZXF1ZXN0cyB0byB0aGUgVFVSTiBjbGllbnQuIEJlY2F1c2UgMSkgaXQgZG9lcyBu
b3QgZXhwb3NlIHRoZSB1ZnJhZyB0byB0aGUgbmV0d29yayB3aGVuIHRhbGtpbmcgdG8gdGhlIFRV
Uk4gc2VydmVyLiBBbmQgMikgaXTigJlzIGVhc2llciBmb3IgdGhlIFRVUk4gc2VydmVyIHRvIGp1
c3QgY2hlY2sgZm9yIHRoZSBTVFVODQogcmVxdWVzdCB0eXBlIGFuZCBob3QgaGF2ZSB0byBwYXJz
ZSBmb3IgdGhlIHVmcmFnIGF0dHJpYnV0ZSBhcyB3ZWxsLjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9j
a3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U2FtZSBvcGluaW9uIGhlcmUu
IFRoZSBwb2ludCBvZiBwZXJtaXNzaW9ucyBpcyB0byBwcmV2ZW50IFRVUk4gY2xpZW50cyBmcm9t
IGJlaW5nIGFibGUgdG8gcnVuIGdlbmVyaWMgc2VydmVycy4gSXQgc2VlbXMgbGlrZSBhbHdheXMg
YWxsb3dpbmcgU1RVTiBwYWNrZXRzIHdvdWxkIHByZXNlcnZlIHRoaXMgZmVhdHVyZSB3aGlsZSBz
b2x2aW5nIHRoZSBzZXNzaW9uIGVzdGFibGlzaG1lbnQgbGF0ZW5jeSBwcm9ibGVtLg0KIEFuZCB3
b3VsZCBiZSBxdWl0ZSBhIGJpdCBzaW1wbGVyIHRvIGltcGxlbWVudCB0aGFuIHVmcmFnIHBlcm1z
LiBIYXZlIHlvdXIgY2FrZSwgZWF0IGl0LCBhbmQgZWF0IGl0IGEgc2Vjb25kIHRpbWUuPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFsc28sIGJl
Y2F1c2UgdGhpcyBpcyBzbyBzaW1wbGUgKGp1c3Qgb25lIHNlbnRlbmNlIHRvIHNwZWNpZnkgaXQh
KSwgYW5kIGltcGFjdCBwb3RlbnRpYWwgaXMgc28gZ3JlYXQgKG1ha2UgQnJhbmRvbiBoYXBweSEp
LCBJIHdvbmRlciBpZiB3ZSBzaG91bGRuJ3Qgc2ltcGx5IGFkZCBpdCB0byBUVVJOLWJpcyB3aGls
ZSB0aGVyZSdzIHN0aWxsIHRpbWUuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVv
dGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFk
ZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGlu
Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uZSBxdWVzdGlvbiB3aGljaCBjb21lcyB0byBteSBt
aW5kIGlzIGlmIHRoZSBUVVJOIHNlcnZlciBhdCBzb21lIHBvaW50LCBlLmcuIGFmdGVyIHJlY2Vp
dmluZyB0aGUgcGVybWlzc2lvbiByZXF1ZXN0LCBzdG9wcyBmb3J3YXJkaW5nIHRoZSBiaW5kaW5n
IHJlcXVlc3RzIGJsaW5kbHk/PG86cD48L286cD48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QmVjYXVzZSB0aGUgYWxsb2NhdGlvbiBtaWdodCBiZSBw
YWlyZWQgd2l0aCBtdWx0aXBsZSByZW1vdGUgY2FuZGlkYXRlcywgSSB0aGluayB3ZSdkIG5lZWQg
dG8gYWx3YXlzIGZvcndhcmQgU1RVTiBibGluZGx5LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5TaW1vbjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_BN6PR16MB14253012D6A5EA47A700EE1FEAAB0BN6PR16MB1425namp_--


From nobody Tue Mar 20 05:17:56 2018
Return-Path: <sperreault@jive.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 156EE12702E for <tram@ietfa.amsl.com>; Tue, 20 Mar 2018 05:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=jive.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dMU4X4AVQ_zN for <tram@ietfa.amsl.com>; Tue, 20 Mar 2018 05:17:52 -0700 (PDT)
Received: from mail-ot0-x230.google.com (mail-ot0-x230.google.com [IPv6:2607:f8b0:4003:c0f::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D23D8126DFB for <tram@ietf.org>; Tue, 20 Mar 2018 05:17:50 -0700 (PDT)
Received: by mail-ot0-x230.google.com with SMTP id m22-v6so1426042otf.10 for <tram@ietf.org>; Tue, 20 Mar 2018 05:17:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jive.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=u0lAsGaGJsy4hlbi2/LOne1h6tBXTktkeM0X8mp7dC8=; b=BZVjwvbpNZkBER+MaCU4yjjyFAhkUQQAe8B4nupiDEvcWMzsB79Ueyy+aL0Bt3qUt4 B7ECgYjiA5yNAKjsH56dselWPv1tA4x4iHmovH7gHLY/oI3u63EgYDHuSWfKT1SdB8Fi Qq/tNy6FMJnqGdJzt9sCKKu1ofmPsAPfdw8V+AaSCoYFmpHaPWM/gN07ZCOFNR5Qvawu qrLtA0pAdzrTySoqQPoCEUgOZpSr1IYTMOxceLzhFhdaBmJ8ag046qSRcWr9RWR0CmVp aKS9TBqbApRzV+V6g0DatWR7p1s9aCay61h+HwXLbRzBoYVBtDDXxJTI0Scix+2J6LZU bFEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=u0lAsGaGJsy4hlbi2/LOne1h6tBXTktkeM0X8mp7dC8=; b=MrzCJTHolWtB7v6c/NMnlSBKAPHap9N5VhDb7AJvR9f3zXyKG9cQMkQ+BxGjunHEjR RNNz+F2pnd0fHLww1/ItqjdhkUttse1zDRi4jR8ksv37UBuHbw5SWAr0KOYO848GgOTK 3alp/GOia6IBQlSjGsYV4GqX/1U15Ml1yB2SxtPLQv4UMvHEruT9w++Qs9lWmpvwTe9L fEQnBT+koVV5YCysk375o5zTxSlBy0Jmy9jHqKvktsP5pTI9v/0KXCCt50ytSsFvrBmc xy2ABet/hXDcsc1kPgTGLlennJu5Wn/9pPGvxETdv7CYe8Ia0qIlVddfa+Uy1YHsNHnO qFIg==
X-Gm-Message-State: AElRT7HTzUUp0ZX+LTL9XXITKSQJhUtrX0XVX9emVC2+UjQtmqnmpN/0 DZjckSyMVV4UaK7RF4qHQrGZJonwK6Pn6wpa8Kq/jg==
X-Google-Smtp-Source: AG47ELukYv5f9+C0IG9G5agRbakKa9jCMBFOM5L2sGQfMfFt5xlR8NnpZ3JByiMBmhq8FNr6E/5Jt5wRfKr27chmH8A=
X-Received: by 2002:a9d:6218:: with SMTP id g24-v6mr5175072otj.76.1521548270153;  Tue, 20 Mar 2018 05:17:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.203.132 with HTTP; Tue, 20 Mar 2018 05:17:29 -0700 (PDT)
In-Reply-To: <BN6PR16MB14253012D6A5EA47A700EE1FEAAB0@BN6PR16MB1425.namprd16.prod.outlook.com>
References: <CANO7kWDd8NZ=svBONwzo6sE5YH3Y5MAdWFP2CQMiTg7M-b47AQ@mail.gmail.com> <c9ef837c-bf7c-decb-9542-8a9ddeda67fd@akamai.com> <E3AB81FC-D841-47A6-A0E2-775461779770@mozilla.com> <CANO7kWA4tmK7Di59tsjvCBoDdh-jW83FxMpqQH1-iSPGLS=mpA@mail.gmail.com> <BN6PR16MB14253012D6A5EA47A700EE1FEAAB0@BN6PR16MB1425.namprd16.prod.outlook.com>
From: Simon Perreault <sperreault@jive.com>
Date: Tue, 20 Mar 2018 08:17:29 -0400
Message-ID: <CANO7kWD3rpCOrgjcLrkVfh0ZF5nrDs+cRnB02VgMHHW1axSRMg@mail.gmail.com>
To: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@mcafee.com>
Cc: Nils Ohlmeier <nohlmeier@mozilla.com>, Cullen Jennings <fluffy@cisco.com>,  Eric Rescorla <ekr@rtfm.com>, "tram@ietf.org" <tram@ietf.org>,  Brandon Williams <brandon.williams@akamai.com>
Content-Type: multipart/alternative; boundary="00000000000026e7eb0567d71073"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/DNCPhF7L9ZRdv4ljq4Fifp4Ne30>
Subject: Re: [tram] Allow TURN to forward inbound connectivity checks without permission
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2018 12:17:54 -0000

--00000000000026e7eb0567d71073
Content-Type: text/plain; charset="UTF-8"

2018-03-20 10:31 GMT+00:00 Konda, Tirumaleswar Reddy <
TirumaleswarReddy_Konda@mcafee.com>:

> the TURN client could be subjected to DDoS attack (e.g. spoofed STUN
> packets from attackers, client wastes cycles validating the message
> integrity, and could also be subjected to bandwidth-hogging attack).
>

That would be new to TURN, but not new to the client: NAT pinholes, created
with STUN or otherwise, expose the client similarly. So while this is
certainly worth mentioning in the security considerations section, I don't
see this as a blocker.

I also can't think of a way that this could be exploited to mount any kind
of practical attack against a specific target...

Simon

--00000000000026e7eb0567d71073
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">2018=
-03-20 10:31 GMT+00:00 Konda, Tirumaleswar Reddy <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:TirumaleswarReddy_Konda@mcafee.com" target=3D"_blank">Tirumal=
eswarReddy_Konda@mcafee.com</a>&gt;</span>:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"m_-3039711730361655594WordSection1">
<p class=3D"MsoNormal">the TURN client could be subjected to DDoS attack (e=
.g. spoofed STUN packets from attackers, client wastes cycles validating th=
e
 message integrity, and could also be subjected to bandwidth-hogging attack=
).</p></div></div></blockquote><div><br></div><div>That would be new to TUR=
N, but not new to the client: NAT pinholes, created with STUN or otherwise,=
 expose the client similarly. So while this is certainly worth mentioning i=
n the security considerations section, I don&#39;t see this as a blocker.<b=
r></div><div><br></div><div>I also can&#39;t think of a way that this could=
 be exploited to mount any kind of practical attack against a specific targ=
et...</div><div><br></div><div>Simon</div></div></div></div>

--00000000000026e7eb0567d71073--


From nobody Tue Mar 20 05:30:06 2018
Return-Path: <nohlmeier@mozilla.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83CFC126D85 for <tram@ietfa.amsl.com>; Tue, 20 Mar 2018 05:30:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zTYvDbV8dsfE for <tram@ietfa.amsl.com>; Tue, 20 Mar 2018 05:30:04 -0700 (PDT)
Received: from mail-wr0-x231.google.com (mail-wr0-x231.google.com [IPv6:2a00:1450:400c:c0c::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3AE8124234 for <tram@ietf.org>; Tue, 20 Mar 2018 05:30:03 -0700 (PDT)
Received: by mail-wr0-x231.google.com with SMTP id 80so407717wrb.2 for <tram@ietf.org>; Tue, 20 Mar 2018 05:30:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=3FxR1l45YWltNOaZ8+TlrspeNpX6KqZIM29e+Awgua0=; b=DYkqJHODUni51N9kx75iRgZVepZ1jSabsy7ZY6lE0kciaiytHjnmOrwxMsdnSFZDMY HGEaRaVyhav+6b1miIC08ZExmq2rhWb9HU/8t5SwGxL5j57QMvzFZthlbRu7ElnuyxGp Ox3ymHPDNlW/BAIzzO+woQSh8lsx/EGPTyL1c=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=3FxR1l45YWltNOaZ8+TlrspeNpX6KqZIM29e+Awgua0=; b=cMFdmw4tnzm1MoPFnKd4D+RcKP4XVhU6NMVxkubiiUhjE5TQqpjFaO4AzQzonvIdYU S1fAXYTUKqoJhv166ew37bHWddq3G8/c/R12BTLFe96ewSAEd5Xav9L6vyaZdThhS5x6 8xnGUJk1wigDll6XbGwcLs4Cmruy0saLuCTYUB83I7Sd1jCRPfYUbOha2zhoDVUHUlLI Sx66dB6XUVDD6X7Jcw/WLoDrxnNUulDhgcb+4GSbR6eobyDje1RCjny+RRk0YEPI/0FK XQMEGZwycCfw0CAsPhDGNjA8BCwSaRksff5l7lT4VN6S/Kt1THsDLNgi/WrKKE6lEl0e yF1A==
X-Gm-Message-State: AElRT7GGHLVJ1MXCnyR+Zxp+Y/a3t9og/S+TmbBc0PUK2Fkk66enzkhr XzOk1K3AgQfLLmC9I+SQgnpKTQ==
X-Google-Smtp-Source: AG47ELsrIDofC9XAbi4RZO69tl+wbUXA0IWjBYc/ufQs+FppMRjvC92N98VJpmMy7pkzphMjiOpkBg==
X-Received: by 10.223.173.3 with SMTP id p3mr12457437wrc.202.1521549002214; Tue, 20 Mar 2018 05:30:02 -0700 (PDT)
Received: from ?IPv6:2001:67c:1232:144:6d39:9314:376c:ca3b? ([2001:67c:1232:144:6d39:9314:376c:ca3b]) by smtp.gmail.com with ESMTPSA id v22sm1388460wrd.43.2018.03.20.05.30.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Mar 2018 05:30:01 -0700 (PDT)
From: Nils Ohlmeier <nohlmeier@mozilla.com>
Message-Id: <F93213AC-991F-42B9-89D4-1FFBD7A251D9@mozilla.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_4ECEFD64-C2BA-4DB0-99D7-1F03A13A34B5"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Tue, 20 Mar 2018 12:30:00 +0000
In-Reply-To: <CANO7kWD3rpCOrgjcLrkVfh0ZF5nrDs+cRnB02VgMHHW1axSRMg@mail.gmail.com>
Cc: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@mcafee.com>, Cullen Jennings <fluffy@cisco.com>, Eric Rescorla <ekr@rtfm.com>, "tram@ietf.org" <tram@ietf.org>, Brandon Williams <brandon.williams@akamai.com>
To: Simon Perreault <sperreault@jive.com>
References: <CANO7kWDd8NZ=svBONwzo6sE5YH3Y5MAdWFP2CQMiTg7M-b47AQ@mail.gmail.com> <c9ef837c-bf7c-decb-9542-8a9ddeda67fd@akamai.com> <E3AB81FC-D841-47A6-A0E2-775461779770@mozilla.com> <CANO7kWA4tmK7Di59tsjvCBoDdh-jW83FxMpqQH1-iSPGLS=mpA@mail.gmail.com> <BN6PR16MB14253012D6A5EA47A700EE1FEAAB0@BN6PR16MB1425.namprd16.prod.outlook.com> <CANO7kWD3rpCOrgjcLrkVfh0ZF5nrDs+cRnB02VgMHHW1axSRMg@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/iMqcYe18N5v2erMgw9aXBHgt-f0>
Subject: Re: [tram] Allow TURN to forward inbound connectivity checks without permission
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2018 12:30:05 -0000

--Apple-Mail=_4ECEFD64-C2BA-4DB0-99D7-1F03A13A34B5
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_5DF3ED6C-5849-45A7-9AB4-DA858FE73612"


--Apple-Mail=_5DF3ED6C-5849-45A7-9AB4-DA858FE73612
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Mar 20, 2018, at 12:17, Simon Perreault <sperreault@jive.com> =
wrote:
>=20
> 2018-03-20 10:31 GMT+00:00 Konda, Tirumaleswar Reddy =
<TirumaleswarReddy_Konda@mcafee.com =
<mailto:TirumaleswarReddy_Konda@mcafee.com>>:
> the TURN client could be subjected to DDoS attack (e.g. spoofed STUN =
packets from attackers, client wastes cycles validating the message =
integrity, and could also be subjected to bandwidth-hogging attack).
>=20
>=20
> That would be new to TURN, but not new to the client: NAT pinholes, =
created with STUN or otherwise, expose the client similarly. So while =
this is certainly worth mentioning in the security considerations =
section, I don't see this as a blocker.
>=20
> I also can't think of a way that this could be exploited to mount any =
kind of practical attack against a specific target=E2=80=A6


I guess you could divide this into three categories:

- the TURN client is an ICE agent, which needs to be prepared to handle =
any incoming traffic already any way
- the TURN client is not an ICE agent, but a STUN client, and as Simon =
pointed out needs to be prepared to receive traffic through the pin =
holes it created
- the TURN client is purely a TURN client and only ever expected to get =
traffic back from the TURN relay

I would assume the last scenario is not very common, but I don=E2=80=99t =
have any numbers to back that up.
I think Simon is right that it=E2=80=99s worth mentioning in the =
security considerations.

Best
  Nils Ohlmeier

--Apple-Mail=_5DF3ED6C-5849-45A7-9AB4-DA858FE73612
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Mar 20, 2018, at 12:17, Simon Perreault &lt;<a =
href=3D"mailto:sperreault@jive.com" class=3D"">sperreault@jive.com</a>&gt;=
 wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"gmail_extra"><div =
class=3D"gmail_quote">2018-03-20 10:31 GMT+00:00 Konda, Tirumaleswar =
Reddy <span dir=3D"ltr" class=3D"">&lt;<a =
href=3D"mailto:TirumaleswarReddy_Konda@mcafee.com" target=3D"_blank" =
class=3D"">TirumaleswarReddy_Konda@mcafee.com</a>&gt;</span>:<br =
class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple" class=3D"">
<div class=3D"m_-3039711730361655594WordSection1"><p =
class=3D"MsoNormal">the TURN client could be subjected to DDoS attack =
(e.g. spoofed STUN packets from attackers, client wastes cycles =
validating the
 message integrity, and could also be subjected to bandwidth-hogging =
attack).</p></div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">That would be new to TURN, but not new =
to the client: NAT pinholes, created with STUN or otherwise, expose the =
client similarly. So while this is certainly worth mentioning in the =
security considerations section, I don't see this as a blocker.<br =
class=3D""></div><div class=3D""><br class=3D""></div><div class=3D"">I =
also can't think of a way that this could be exploited to mount any kind =
of practical attack against a specific =
target=E2=80=A6</div></div></div></div></div></blockquote></div><div =
class=3D""><br class=3D""></div>I guess you could divide this into three =
categories:<div class=3D""><br class=3D""><div class=3D"">- the TURN =
client is an ICE agent, which needs to be prepared to handle any =
incoming traffic already any way</div><div class=3D"">- the TURN client =
is not an ICE agent, but a STUN client, and as Simon pointed out needs =
to be prepared to receive traffic through the pin holes it =
created</div><div class=3D"">- the TURN client is purely a TURN client =
and only ever expected to get traffic back from the TURN relay</div><div =
class=3D""><br class=3D""></div><div class=3D"">I would assume the last =
scenario is not very common, but I don=E2=80=99t have any numbers to =
back that up.</div><div class=3D"">I think Simon is right that it=E2=80=99=
s worth mentioning in the security considerations.<br =
class=3D""></div></div><div class=3D""><br class=3D""></div><div =
class=3D"">Best</div><div class=3D"">&nbsp; Nils =
Ohlmeier</div></body></html>=

--Apple-Mail=_5DF3ED6C-5849-45A7-9AB4-DA858FE73612--

--Apple-Mail=_4ECEFD64-C2BA-4DB0-99D7-1F03A13A34B5
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEQ5rmmyEsAeItlZquY2o/VmzJ+KEFAlqw/sgACgkQY2o/VmzJ
+KGhFA/+O03VQIXbona4Lz/4TpdpeeMnHaYhru98lBPZwRTPwG/zgcBEWgmokFKN
zKGig+ZHWZrrUOYmars+nln2r7G+iCKiJ4ZV1+HPOhMKAVl3mnnYcWbt3CtRIs5s
q40riAvTZG3Lu+mxzayXSeMxmJXraNxJhv3ekb8tA+LshV1x0GoaQDSksNeNN0YN
uwmRbU+Hy1irG9YsrU01RaiYnqh2pCPi/s0mycnwEqrRPJ7v81z1CLgG4u4ZwWOW
cSwej3ok0rr9eTwdCy11PxCUUcHN4cXciXCUwpUD8UOXcV3OajzqtJeU1ZO1a3sP
OAp6zcy5FgT45zHxa9t/WDXnNiZzeAYWuNya9J/yFV31cg34YUwyrqlcnTDNZ6UN
jF/7e1HbGBJqD6+3aeXrt3BiE2Lmtdj23DhmldvQr0AfRMVVHqVvi+7gnu0taXQD
bCOFQOAVwpe3cuCzmjznU95/w8wpellbZ65AZjXqrOjbXq1liEBN4MtG1pFAvDKx
UAVhKb0zzufbbZPDhfK6wuYD0h07rXyfqs2mPKbykLQLaTXlNe/QufaUHbPKYY+w
ZNk8NfJCzcF2Wjbu7et+kKyBhkf9Ka6KrKAm1D6y1LD3rh6sTGPrgG2xQja7o2FH
W4AZ7YYz1Qguj3k+Vp5657H6BtAOGTHhFzDSkpoztx5LffhI+aI=
=UBS5
-----END PGP SIGNATURE-----

--Apple-Mail=_4ECEFD64-C2BA-4DB0-99D7-1F03A13A34B5--


From nobody Tue Mar 20 07:33:52 2018
Return-Path: <TirumaleswarReddy_Konda@mcafee.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25A8F1200B9 for <tram@ietfa.amsl.com>; Tue, 20 Mar 2018 07:33:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.33
X-Spam-Level: 
X-Spam-Status: No, score=-4.33 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mcafee.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mouFNVdAppUu for <tram@ietfa.amsl.com>; Tue, 20 Mar 2018 07:33:47 -0700 (PDT)
Received: from DNVWSMAILOUT1.mcafee.com (dnvwsmailout1.mcafee.com [161.69.31.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 696371200FC for <tram@ietf.org>; Tue, 20 Mar 2018 07:33:46 -0700 (PDT)
X-NAI-Header: Modified by McAfee Email Gateway (5500)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mcafee.com; s=s_mcafee; t=1521556411; h=From: To:CC:Subject:Thread-Topic:Thread-Index:Date: Message-ID:References:In-Reply-To:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: dlp-product:dlp-version:dlp-reaction:authentication-results: x-originating-ip:x-ms-publictraffictype:x-microsoft-exchange-diagnostics: x-ms-exchange-antispam-srfa-diagnostics:x-ms-office365-filtering-correlation-id: x-microsoft-antispam:x-ms-traffictypediagnostic: x-microsoft-antispam-prvs:x-exchange-antispam-report-test: x-exchange-antispam-report-cfa-test:x-forefront-prvs: x-forefront-antispam-report:received-spf:x-microsoft-antispam-message-info: spamdiagnosticoutput:spamdiagnosticmetadata: Content-Type:MIME-Version:X-MS-Exchange-CrossTenant-Network-Message-Id: X-MS-Exchange-CrossTenant-originalarrivaltime: X-MS-Exchange-CrossTenant-fromentityheader: X-MS-Exchange-CrossTenant-id:X-MS-Exchange-Transport-CrossTenantHeadersStamped: X-OriginatorOrg:X-NAI-Spam-Flag:X-NAI-Spam-Threshold: X-NAI-Spam-Score:X-NAI-Spam-Version; bh=D bhuvZeDWKS9/P+D/D1raCToqvY2Y8lpFQNwHbRjZI 0=; b=OAu2sc7fm1tFyzgBeczy48h3UIjZ3qtd8g8vwDzc3DZ1 mERL2pXvus7R90gwSlzA+fnyD7ERJJWiHfr7LBodsSeIzBjofS yJMViMr3UjMZVyCrDYu8xbC7PXKwoNHSUqrA7LmFM1dvI2xuww NvoPJwhwaKWC/iw8RjG8bUk73fA=
Received: from DNVEXAPP1N06.corpzone.internalzone.com (unknown [10.44.48.90]) by DNVWSMAILOUT1.mcafee.com with smtp (TLS: TLSv1/SSLv3,256bits,ECDHE-RSA-AES256-SHA384) id 6013_4486_9a0d197a_4196_45f8_81e1_b023702bf8f0; Tue, 20 Mar 2018 09:33:30 -0500
Received: from DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) by DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 20 Mar 2018 08:33:07 -0600
Received: from DNVEX10N01.corpzone.internalzone.com (10.44.82.192) by DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) with Microsoft SMTP Server (TLS) id 15.0.1347.2 via Frontend Transport; Tue, 20 Mar 2018 08:33:07 -0600
Received: from DNVO365EDGE1.corpzone.internalzone.com (10.44.176.66) by DNVEX10N01.corpzone.internalzone.com (10.44.82.192) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 20 Mar 2018 08:33:07 -0600
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (10.44.176.242) by edge.mcafee.com (10.44.176.66) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 20 Mar 2018 08:33:04 -0600
Received: from BN6PR16MB1425.namprd16.prod.outlook.com (10.172.207.19) by BN6PR16MB1715.namprd16.prod.outlook.com (10.172.28.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.609.10; Tue, 20 Mar 2018 14:33:05 +0000
Received: from BN6PR16MB1425.namprd16.prod.outlook.com ([10.172.207.19]) by BN6PR16MB1425.namprd16.prod.outlook.com ([10.172.207.19]) with mapi id 15.20.0588.017; Tue, 20 Mar 2018 14:33:05 +0000
From: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>
To: Nils Ohlmeier <nohlmeier@mozilla.com>, Simon Perreault <sperreault@jive.com>
CC: Cullen Jennings <fluffy@cisco.com>, Eric Rescorla <ekr@rtfm.com>, "tram@ietf.org" <tram@ietf.org>, Brandon Williams <brandon.williams@akamai.com>
Thread-Topic: [tram] Allow TURN to forward inbound connectivity checks without permission
Thread-Index: AQHTv3BE7H+lEDCzy0aE6LgkPsBdZKPYCNMAgAAflQCAAL9dgIAABGPggAAfy4CAAAOAAIAAIgBQ
Date: Tue, 20 Mar 2018 14:33:05 +0000
Message-ID: <BN6PR16MB14253EE9E98F221B88F3EDDFEAAB0@BN6PR16MB1425.namprd16.prod.outlook.com>
References: <CANO7kWDd8NZ=svBONwzo6sE5YH3Y5MAdWFP2CQMiTg7M-b47AQ@mail.gmail.com> <c9ef837c-bf7c-decb-9542-8a9ddeda67fd@akamai.com> <E3AB81FC-D841-47A6-A0E2-775461779770@mozilla.com> <CANO7kWA4tmK7Di59tsjvCBoDdh-jW83FxMpqQH1-iSPGLS=mpA@mail.gmail.com> <BN6PR16MB14253012D6A5EA47A700EE1FEAAB0@BN6PR16MB1425.namprd16.prod.outlook.com> <CANO7kWD3rpCOrgjcLrkVfh0ZF5nrDs+cRnB02VgMHHW1axSRMg@mail.gmail.com> <F93213AC-991F-42B9-89D4-1FFBD7A251D9@mozilla.com>
In-Reply-To: <F93213AC-991F-42B9-89D4-1FFBD7A251D9@mozilla.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 11.0.200.100
dlp-reaction: no-action
authentication-results: spf=none (sender IP is ) smtp.mailfrom=TirumaleswarReddy_Konda@McAfee.com; 
x-originating-ip: [161.69.163.25]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR16MB1715; 7:FIQeQjcPUrLlru7p2kymr2eSthDaQRMAhYlHjCQqSYe2/2f9NxBpgZQj2x4LYbTlWvaWwwN4h6j+K3+POJpq5g888idtbfVmfAOg71Cy1Sx2pjh6p6wLBzwQJ/7GypgY/T0SxEZGEYvoQ/QZQTZw31RUBq/xrwlnjpUp+rgbJaIWJmJ5gMKiXXz0PBUVzMg3Fufn+rwNCU9yoac27DykH8nlZ+9VjVZOLlD8tH39TebmbIwjZs+75WQmUbR7t3GL
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 0188e392-2e83-4f0a-82c7-08d58e6f7e97
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BN6PR16MB1715; 
x-ms-traffictypediagnostic: BN6PR16MB1715:
x-microsoft-antispam-prvs: <BN6PR16MB1715A9CB2F2AFA600AE6BA7BEAAB0@BN6PR16MB1715.namprd16.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(192374486261705)(95692535739014)(21748063052155)(123452027830198);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3002001)(10201501046)(93006095)(93001095)(3231221)(944501244)(52105095)(6041310)(20161123562045)(20161123560045)(20161123564045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:BN6PR16MB1715; BCL:0; PCL:0; RULEID:; SRVR:BN6PR16MB1715; 
x-forefront-prvs: 061725F016
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(346002)(39380400002)(396003)(366004)(39860400002)(377424004)(32952001)(199004)(189003)(7696005)(2906002)(72206003)(3846002)(6116002)(790700001)(97736004)(81156014)(8676002)(80792005)(99286004)(2900100001)(59450400001)(4326008)(53546011)(3660700001)(6506007)(25786009)(66066001)(14454004)(86362001)(93886005)(478600001)(76176011)(110136005)(3280700002)(316002)(102836004)(74316002)(106356001)(55016002)(105586002)(6246003)(26005)(54906003)(68736007)(33656002)(77096007)(7736002)(53936002)(186003)(19609705001)(229853002)(236005)(6436002)(8936002)(9686003)(54896002)(6306002)(5660300001)(2950100002)(81166006)(85282002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR16MB1715; H:BN6PR16MB1425.namprd16.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: McAfee.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: cDAqpEASl+GBYe+IvrI+IpIsABJRfNoDI1rPgt8KDqUL15vTVyql0q6/huavK201adzt1mHZOYEndG1hqTx/bV7Qa7XmOMkGZKnW+YRWb+AUj9x4oFG0SDw9zXC2Bo5VglKnGCVcDXXGDtyBi+fE3Hz/++cLVstW/78Xxq3gEFLFaXnfhkzohel/4zn2nAKrG0598D5WjGyHn3mNhnV++fgP7S5FVGRHh2JkTeEalwOnccmSwkuGv0S2irtXmbTBOVXAK+FMhwdVPhTDp453yuns6iBatgLSXsKkeKy4V3QYslPZrOwxksOqhKp7RFO8ILP2PiDj27UDKPDmmP+38w==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BN6PR16MB14253EE9E98F221B88F3EDDFEAAB0BN6PR16MB1425namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 0188e392-2e83-4f0a-82c7-08d58e6f7e97
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Mar 2018 14:33:05.8095 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4943e38c-6dd4-428c-886d-24932bc2d5de
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR16MB1715
X-OriginatorOrg: mcafee.com
X-NAI-Spam-Flag: NO
X-NAI-Spam-Threshold: 15
X-NAI-Spam-Score: 0
X-NAI-Spam-Version: 2.3.0.9418 : core <6246> : inlines <6507> : streams <1781750> : uri <2611680>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/eHuK5W6PoVE6GmfTOnppelmMHvI>
Subject: Re: [tram] Allow TURN to forward inbound connectivity checks without permission
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2018 14:33:50 -0000

--_000_BN6PR16MB14253EE9E98F221B88F3EDDFEAAB0BN6PR16MB1425namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

QWdyZWVkLCBpdOKAmXMgbm90IGEgYmxvY2tlciBidXQgbmVlZHMgdG8gYmUgZGlzY3Vzc2VkIGlu
IHRoZSBTZWN1cml0eSBDb25zaWRlcmF0aW9ucyBzZWN0aW9uLg0KDQotVGlydQ0KDQpGcm9tOiBO
aWxzIE9obG1laWVyIFttYWlsdG86bm9obG1laWVyQG1vemlsbGEuY29tXQ0KU2VudDogVHVlc2Rh
eSwgTWFyY2ggMjAsIDIwMTggMTI6MzAgUE0NClRvOiBTaW1vbiBQZXJyZWF1bHQgPHNwZXJyZWF1
bHRAaml2ZS5jb20+DQpDYzogS29uZGEsIFRpcnVtYWxlc3dhciBSZWRkeSA8VGlydW1hbGVzd2Fy
UmVkZHlfS29uZGFATWNBZmVlLmNvbT47IEN1bGxlbiBKZW5uaW5ncyA8Zmx1ZmZ5QGNpc2NvLmNv
bT47IEVyaWMgUmVzY29ybGEgPGVrckBydGZtLmNvbT47IHRyYW1AaWV0Zi5vcmc7IEJyYW5kb24g
V2lsbGlhbXMgPGJyYW5kb24ud2lsbGlhbXNAYWthbWFpLmNvbT4NClN1YmplY3Q6IFJlOiBbdHJh
bV0gQWxsb3cgVFVSTiB0byBmb3J3YXJkIGluYm91bmQgY29ubmVjdGl2aXR5IGNoZWNrcyB3aXRo
b3V0IHBlcm1pc3Npb24NCg0KDQoNCg0KT24gTWFyIDIwLCAyMDE4LCBhdCAxMjoxNywgU2ltb24g
UGVycmVhdWx0IDxzcGVycmVhdWx0QGppdmUuY29tPG1haWx0bzpzcGVycmVhdWx0QGppdmUuY29t
Pj4gd3JvdGU6DQoNCjIwMTgtMDMtMjAgMTA6MzEgR01UKzAwOjAwIEtvbmRhLCBUaXJ1bWFsZXN3
YXIgUmVkZHkgPFRpcnVtYWxlc3dhclJlZGR5X0tvbmRhQG1jYWZlZS5jb208bWFpbHRvOlRpcnVt
YWxlc3dhclJlZGR5X0tvbmRhQG1jYWZlZS5jb20+PjoNCnRoZSBUVVJOIGNsaWVudCBjb3VsZCBi
ZSBzdWJqZWN0ZWQgdG8gRERvUyBhdHRhY2sgKGUuZy4gc3Bvb2ZlZCBTVFVOIHBhY2tldHMgZnJv
bSBhdHRhY2tlcnMsIGNsaWVudCB3YXN0ZXMgY3ljbGVzIHZhbGlkYXRpbmcgdGhlIG1lc3NhZ2Ug
aW50ZWdyaXR5LCBhbmQgY291bGQgYWxzbyBiZSBzdWJqZWN0ZWQgdG8gYmFuZHdpZHRoLWhvZ2dp
bmcgYXR0YWNrKS4NCg0KVGhhdCB3b3VsZCBiZSBuZXcgdG8gVFVSTiwgYnV0IG5vdCBuZXcgdG8g
dGhlIGNsaWVudDogTkFUIHBpbmhvbGVzLCBjcmVhdGVkIHdpdGggU1RVTiBvciBvdGhlcndpc2Us
IGV4cG9zZSB0aGUgY2xpZW50IHNpbWlsYXJseS4gU28gd2hpbGUgdGhpcyBpcyBjZXJ0YWlubHkg
d29ydGggbWVudGlvbmluZyBpbiB0aGUgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMgc2VjdGlvbiwg
SSBkb24ndCBzZWUgdGhpcyBhcyBhIGJsb2NrZXIuDQoNCkkgYWxzbyBjYW4ndCB0aGluayBvZiBh
IHdheSB0aGF0IHRoaXMgY291bGQgYmUgZXhwbG9pdGVkIHRvIG1vdW50IGFueSBraW5kIG9mIHBy
YWN0aWNhbCBhdHRhY2sgYWdhaW5zdCBhIHNwZWNpZmljIHRhcmdldOKApg0KDQpJIGd1ZXNzIHlv
dSBjb3VsZCBkaXZpZGUgdGhpcyBpbnRvIHRocmVlIGNhdGVnb3JpZXM6DQoNCi0gdGhlIFRVUk4g
Y2xpZW50IGlzIGFuIElDRSBhZ2VudCwgd2hpY2ggbmVlZHMgdG8gYmUgcHJlcGFyZWQgdG8gaGFu
ZGxlIGFueSBpbmNvbWluZyB0cmFmZmljIGFscmVhZHkgYW55IHdheQ0KLSB0aGUgVFVSTiBjbGll
bnQgaXMgbm90IGFuIElDRSBhZ2VudCwgYnV0IGEgU1RVTiBjbGllbnQsIGFuZCBhcyBTaW1vbiBw
b2ludGVkIG91dCBuZWVkcyB0byBiZSBwcmVwYXJlZCB0byByZWNlaXZlIHRyYWZmaWMgdGhyb3Vn
aCB0aGUgcGluIGhvbGVzIGl0IGNyZWF0ZWQNCi0gdGhlIFRVUk4gY2xpZW50IGlzIHB1cmVseSBh
IFRVUk4gY2xpZW50IGFuZCBvbmx5IGV2ZXIgZXhwZWN0ZWQgdG8gZ2V0IHRyYWZmaWMgYmFjayBm
cm9tIHRoZSBUVVJOIHJlbGF5DQoNCkkgd291bGQgYXNzdW1lIHRoZSBsYXN0IHNjZW5hcmlvIGlz
IG5vdCB2ZXJ5IGNvbW1vbiwgYnV0IEkgZG9u4oCZdCBoYXZlIGFueSBudW1iZXJzIHRvIGJhY2sg
dGhhdCB1cC4NCkkgdGhpbmsgU2ltb24gaXMgcmlnaHQgdGhhdCBpdOKAmXMgd29ydGggbWVudGlv
bmluZyBpbiB0aGUgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMuDQoNCkJlc3QNCiAgTmlscyBPaGxt
ZWllcg0K

--_000_BN6PR16MB14253EE9E98F221B88F3EDDFEAAB0BN6PR16MB1425namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkRlbmdYaWFuOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAx
IDE7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIgMTUg
NSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IlxARGVuZ1hpYW4i
Ow0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMg
Ki8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBp
bjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZh
bWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJ
e21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1
bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1z
dHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVy
bGluZTt9DQpwLm1zb25vcm1hbDAsIGxpLm1zb25vcm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21z
by1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJn
aW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0
OjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNl
cmlmO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7
fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1z
aXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJ
bWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFn
ZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxv
OnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtl
bmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJl
ZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0
PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJs
dWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPkFncmVlZCwgaXTigJlzIG5vdCBhIGJsb2NrZXIgYnV0IG5lZWRzIHRvIGJl
IGRpc2N1c3NlZCBpbiB0aGUgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMgc2VjdGlvbi4NCjxhIG5h
bWU9Il9NYWlsRW5kQ29tcG9zZSI+PG86cD48L286cD48L2E+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbEVuZENvbXBvc2UiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJt
c28tYm9va21hcms6X01haWxFbmRDb21wb3NlIj4tVGlydTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxFbmRD
b21wb3NlIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8c3BhbiBzdHlsZT0ibXNvLWJv
b2ttYXJrOl9NYWlsRW5kQ29tcG9zZSI+PC9zcGFuPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7
Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0Ij4N
CjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEg
MS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
Yj5Gcm9tOjwvYj4gTmlscyBPaGxtZWllciBbbWFpbHRvOm5vaGxtZWllckBtb3ppbGxhLmNvbV0g
PGJyPg0KPGI+U2VudDo8L2I+IFR1ZXNkYXksIE1hcmNoIDIwLCAyMDE4IDEyOjMwIFBNPGJyPg0K
PGI+VG86PC9iPiBTaW1vbiBQZXJyZWF1bHQgJmx0O3NwZXJyZWF1bHRAaml2ZS5jb20mZ3Q7PGJy
Pg0KPGI+Q2M6PC9iPiBLb25kYSwgVGlydW1hbGVzd2FyIFJlZGR5ICZsdDtUaXJ1bWFsZXN3YXJS
ZWRkeV9Lb25kYUBNY0FmZWUuY29tJmd0OzsgQ3VsbGVuIEplbm5pbmdzICZsdDtmbHVmZnlAY2lz
Y28uY29tJmd0OzsgRXJpYyBSZXNjb3JsYSAmbHQ7ZWtyQHJ0Zm0uY29tJmd0OzsgdHJhbUBpZXRm
Lm9yZzsgQnJhbmRvbiBXaWxsaWFtcyAmbHQ7YnJhbmRvbi53aWxsaWFtc0Bha2FtYWkuY29tJmd0
Ozxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW3RyYW1dIEFsbG93IFRVUk4gdG8gZm9yd2FyZCBp
bmJvdW5kIGNvbm5lY3Rpdml0eSBjaGVja3Mgd2l0aG91dCBwZXJtaXNzaW9uPG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YnI+DQo8YnI+DQo8bzpwPjwvbzpwPjwvcD4NCjxibG9j
a3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIE1hciAyMCwgMjAxOCwgYXQgMTI6MTcsIFNpbW9u
IFBlcnJlYXVsdCAmbHQ7PGEgaHJlZj0ibWFpbHRvOnNwZXJyZWF1bHRAaml2ZS5jb20iPnNwZXJy
ZWF1bHRAaml2ZS5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxk
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+MjAxOC0wMy0yMCAxMDozMSBHTVQmIzQz
OzAwOjAwIEtvbmRhLCBUaXJ1bWFsZXN3YXIgUmVkZHkgJmx0OzxhIGhyZWY9Im1haWx0bzpUaXJ1
bWFsZXN3YXJSZWRkeV9Lb25kYUBtY2FmZWUuY29tIiB0YXJnZXQ9Il9ibGFuayI+VGlydW1hbGVz
d2FyUmVkZHlfS29uZGFAbWNhZmVlLmNvbTwvYT4mZ3Q7OjxvOnA+PC9vOnA+PC9wPg0KPGJsb2Nr
cXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7
cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6
MGluIj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj50aGUgVFVSTiBjbGll
bnQgY291bGQgYmUgc3ViamVjdGVkIHRvIEREb1MgYXR0YWNrIChlLmcuIHNwb29mZWQgU1RVTiBw
YWNrZXRzIGZyb20gYXR0YWNrZXJzLCBjbGllbnQgd2FzdGVzIGN5Y2xlcyB2YWxpZGF0aW5nIHRo
ZSBtZXNzYWdlIGludGVncml0eSwgYW5kIGNvdWxkIGFsc28gYmUgc3ViamVjdGVkIHRvDQogYmFu
ZHdpZHRoLWhvZ2dpbmcgYXR0YWNrKS48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGF0IHdvdWxkIGJl
IG5ldyB0byBUVVJOLCBidXQgbm90IG5ldyB0byB0aGUgY2xpZW50OiBOQVQgcGluaG9sZXMsIGNy
ZWF0ZWQgd2l0aCBTVFVOIG9yIG90aGVyd2lzZSwgZXhwb3NlIHRoZSBjbGllbnQgc2ltaWxhcmx5
LiBTbyB3aGlsZSB0aGlzIGlzIGNlcnRhaW5seSB3b3J0aCBtZW50aW9uaW5nIGluIHRoZSBzZWN1
cml0eSBjb25zaWRlcmF0aW9ucyBzZWN0aW9uLCBJIGRvbid0IHNlZSB0aGlzIGFzIGEgYmxvY2tl
ci48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
SSBhbHNvIGNhbid0IHRoaW5rIG9mIGEgd2F5IHRoYXQgdGhpcyBjb3VsZCBiZSBleHBsb2l0ZWQg
dG8gbW91bnQgYW55IGtpbmQgb2YgcHJhY3RpY2FsIGF0dGFjayBhZ2FpbnN0IGEgc3BlY2lmaWMg
dGFyZ2V04oCmPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkg
Z3Vlc3MgeW91IGNvdWxkIGRpdmlkZSB0aGlzIGludG8gdGhyZWUgY2F0ZWdvcmllczo8bzpwPjwv
bzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4tIHRoZSBUVVJOIGNsaWVudCBpcyBhbiBJ
Q0UgYWdlbnQsIHdoaWNoIG5lZWRzIHRvIGJlIHByZXBhcmVkIHRvIGhhbmRsZSBhbnkgaW5jb21p
bmcgdHJhZmZpYyBhbHJlYWR5IGFueSB3YXk8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPi0gdGhlIFRVUk4gY2xpZW50IGlzIG5vdCBhbiBJQ0UgYWdl
bnQsIGJ1dCBhIFNUVU4gY2xpZW50LCBhbmQgYXMgU2ltb24gcG9pbnRlZCBvdXQgbmVlZHMgdG8g
YmUgcHJlcGFyZWQgdG8gcmVjZWl2ZSB0cmFmZmljIHRocm91Z2ggdGhlIHBpbiBob2xlcyBpdCBj
cmVhdGVkPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij4tIHRoZSBUVVJOIGNsaWVudCBpcyBwdXJlbHkgYSBUVVJOIGNsaWVudCBhbmQgb25seSBldmVy
IGV4cGVjdGVkIHRvIGdldCB0cmFmZmljIGJhY2sgZnJvbSB0aGUgVFVSTiByZWxheTxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIHdvdWxkIGFz
c3VtZSB0aGUgbGFzdCBzY2VuYXJpbyBpcyBub3QgdmVyeSBjb21tb24sIGJ1dCBJIGRvbuKAmXQg
aGF2ZSBhbnkgbnVtYmVycyB0byBiYWNrIHRoYXQgdXAuPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIHRoaW5rIFNpbW9uIGlzIHJpZ2h0IHRoYXQg
aXTigJlzIHdvcnRoIG1lbnRpb25pbmcgaW4gdGhlIHNlY3VyaXR5IGNvbnNpZGVyYXRpb25zLjxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPkJlc3Q8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPiZuYnNwOyBOaWxzIE9obG1laWVyPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_BN6PR16MB14253EE9E98F221B88F3EDDFEAAB0BN6PR16MB1425namp_--


From nobody Tue Mar 20 08:02:22 2018
Return-Path: <brandon.williams@akamai.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4306A126DEE for <tram@ietfa.amsl.com>; Tue, 20 Mar 2018 08:02:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W_dnAY8LcGVM for <tram@ietfa.amsl.com>; Tue, 20 Mar 2018 08:02:15 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 701DC126D3F for <tram@ietf.org>; Tue, 20 Mar 2018 08:02:06 -0700 (PDT)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.22/8.16.0.22) with SMTP id w2KF04eW012581; Tue, 20 Mar 2018 15:02:04 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=subject : to : cc : references : from : message-id : date : mime-version : in-reply-to : content-type : content-transfer-encoding; s=jan2016.eng; bh=3WVAK4+uOCfYEq7Ud6Dh9pytZQXPw88yiMDBFapPTyo=; b=TjnSO4ljlE30fXHl+rBh8RHUQeyCiTGIRpwZzxKU07JwJjpCszxf88NwOvERN6SKHb/m Q1QOsqFNBn5lMhxZobzveZCM1gZfX7BFvLhw3155pv6IS1KrEsN5cfjYXhgXjyFvvZC4 kOXeEHE/K6cLRpJfQGv5FxgVUoAulgXETRiFuXw4YvW4ioPnGhVHpVHpUAwURgyNUpIN x4fHMNMvrcN5YRyaIVyqwAPFw/1J7G66Xty5QdA117u6E+OlZPPMeg4X23T08CUjACtw R08Ct/Pw7UOmhw0xone9fKNgITqHuNHiVY44E4OZVbl9z0i0YmaaNbjfWUrcPt83LggJ aQ== 
Received: from prod-mail-ppoint3 ([96.6.114.86]) by m0050102.ppops.net-00190b01. with ESMTP id 2grrygrt40-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 20 Mar 2018 15:02:03 +0000
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w2KElqIu011960; Tue, 20 Mar 2018 11:02:02 -0400
Received: from prod-mail-relay14.akamai.com ([172.27.17.39]) by prod-mail-ppoint3.akamai.com with ESMTP id 2grxbw82yk-1; Tue, 20 Mar 2018 11:02:02 -0400
Received: from [172.28.118.62] (bowill.kendall.corp.akamai.com [172.28.118.62]) by prod-mail-relay14.akamai.com (Postfix) with ESMTP id E6A2F83438; Tue, 20 Mar 2018 15:02:01 +0000 (GMT)
To: Simon Perreault <sperreault@jive.com>, Nils Ohlmeier <nohlmeier@mozilla.com>
Cc: tram@ietf.org, Cullen Jennings <fluffy@cisco.com>, Eric Rescorla <ekr@rtfm.com>
References: <CANO7kWDd8NZ=svBONwzo6sE5YH3Y5MAdWFP2CQMiTg7M-b47AQ@mail.gmail.com> <c9ef837c-bf7c-decb-9542-8a9ddeda67fd@akamai.com> <E3AB81FC-D841-47A6-A0E2-775461779770@mozilla.com> <CANO7kWA4tmK7Di59tsjvCBoDdh-jW83FxMpqQH1-iSPGLS=mpA@mail.gmail.com>
From: Brandon Williams <brandon.williams@akamai.com>
Message-ID: <8d57a9e5-5697-38f5-1b85-bf55930c6461@akamai.com>
Date: Tue, 20 Mar 2018 11:01:55 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CANO7kWA4tmK7Di59tsjvCBoDdh-jW83FxMpqQH1-iSPGLS=mpA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-20_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=820 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803200172
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-20_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=786 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803200174
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/XtjkczHdJ0xwfZY--Gg-odrkXTY>
Subject: Re: [tram] Allow TURN to forward inbound connectivity checks without permission
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2018 15:02:21 -0000

On 03/20/2018 06:07 AM, Simon Perreault wrote:
> Same opinion here. The point of permissions is to prevent TURN clients 
> from being able to run generic servers. It seems like always allowing 
> STUN packets would preserve this feature while solving the session 
> establishment latency problem. And would be quite a bit simpler to 
> implement than ufrag perms. Have your cake, eat it, and eat it a second 
> time.

If you want to prevent someone from running a server on the allocation 
you can't assume that a STUN-looking packet is actually legitimate, so 
some additional validations would be required. Perhaps packet size, 
rate-limiting, and max session counts are enough.

ufrag permissions didn't do enough to be more meaningful there, since it 
would be easy to post the ufrag somewhere public via a mechanism similar 
to dynamic DNS.

--Brandon



From nobody Tue Mar 20 08:09:01 2018
Return-Path: <TirumaleswarReddy_Konda@mcafee.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1744F126D74 for <tram@ietfa.amsl.com>; Tue, 20 Mar 2018 08:08:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.331
X-Spam-Level: 
X-Spam-Status: No, score=-4.331 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mcafee.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p54Vcnv60zwX for <tram@ietfa.amsl.com>; Tue, 20 Mar 2018 08:08:57 -0700 (PDT)
Received: from DNVWSMAILOUT1.mcafee.com (dnvwsmailout1.mcafee.com [161.69.31.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25872126D45 for <tram@ietf.org>; Tue, 20 Mar 2018 08:08:57 -0700 (PDT)
X-NAI-Header: Modified by McAfee Email Gateway (5500)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mcafee.com; s=s_mcafee; t=1521558528; h=From: To:CC:Subject:Thread-Topic:Thread-Index:Date: Message-ID:References:In-Reply-To:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: dlp-product:dlp-version:dlp-reaction:authentication-results: x-originating-ip:x-ms-publictraffictype:x-microsoft-exchange-diagnostics: x-ms-exchange-antispam-srfa-diagnostics:x-ms-office365-filtering-correlation-id: x-microsoft-antispam:x-ms-traffictypediagnostic: x-microsoft-antispam-prvs:x-exchange-antispam-report-test: x-exchange-antispam-report-cfa-test:x-forefront-prvs: x-forefront-antispam-report:received-spf:x-microsoft-antispam-message-info: spamdiagnosticoutput:spamdiagnosticmetadata: Content-Type:Content-Transfer-Encoding:MIME-Version: X-MS-Exchange-CrossTenant-Network-Message-Id: X-MS-Exchange-CrossTenant-originalarrivaltime: X-MS-Exchange-CrossTenant-fromentityheader: X-MS-Exchange-CrossTenant-id:X-MS-Exchange-Transport-CrossTenantHeadersStamped: X-OriginatorOrg:X-NAI-Spam-Flag:X-NAI-Spam-Level: X-NAI-Spam-Threshold:X-NAI-Spam-Score:X-NAI-Spam-Version; bh=6udCM0prz6we1xa3gQZ7dCw42l6KdTiwAIFk0U 5TT6I=; b=J8G4p5X34sjUwFklzRIHT9kMKKXJVXjGUjiYaU8B epfI1drAfb+CPp77Z36MUbeTh7MCatATiN80iybif2ZtdlGxd9 C8Vda1x2IcJo2HK3Dwg4gO9efFKBemReKuaLTiLi+mPLxMpSuW dgVKZNOjhTN4Eo8kiE1ZeFOi3CcIiE4=
Received: from DNVEXAPP1N06.corpzone.internalzone.com (unknown [10.44.48.90]) by DNVWSMAILOUT1.mcafee.com with smtp (TLS: TLSv1/SSLv3,256bits,ECDHE-RSA-AES256-SHA384) id 5ff1_cc41_0be0b132_18c2_415e_9b83_45478480830d; Tue, 20 Mar 2018 10:08:47 -0500
Received: from DNVEXUSR1N14.corpzone.internalzone.com (10.44.48.87) by DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 20 Mar 2018 09:08:01 -0600
Received: from DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) by DNVEXUSR1N14.corpzone.internalzone.com (10.44.48.87) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 20 Mar 2018 09:08:00 -0600
Received: from DNVO365EDGE1.corpzone.internalzone.com (10.44.176.66) by DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) with Microsoft SMTP Server (TLS) id 15.0.1347.2 via Frontend Transport; Tue, 20 Mar 2018 09:07:59 -0600
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (10.44.176.241) by edge.mcafee.com (10.44.176.66) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 20 Mar 2018 09:07:56 -0600
Received: from BN6PR16MB1425.namprd16.prod.outlook.com (10.172.207.19) by BN6PR16MB1540.namprd16.prod.outlook.com (10.172.208.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.609.10; Tue, 20 Mar 2018 15:07:57 +0000
Received: from BN6PR16MB1425.namprd16.prod.outlook.com ([10.172.207.19]) by BN6PR16MB1425.namprd16.prod.outlook.com ([10.172.207.19]) with mapi id 15.20.0588.017; Tue, 20 Mar 2018 15:07:57 +0000
From: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>
To: Brandon Williams <brandon.williams@akamai.com>, Simon Perreault <sperreault@jive.com>, Nils Ohlmeier <nohlmeier@mozilla.com>
CC: Cullen Jennings <fluffy@cisco.com>, Eric Rescorla <ekr@rtfm.com>, "tram@ietf.org" <tram@ietf.org>
Thread-Topic: [tram] Allow TURN to forward inbound connectivity checks without permission
Thread-Index: AQHTv3BE7H+lEDCzy0aE6LgkPsBdZKPYCNMAgAAflQCAAL9dgIAAUh+AgAAAqKA=
Date: Tue, 20 Mar 2018 15:07:56 +0000
Message-ID: <BN6PR16MB142571E36A8B89196CB7B080EAAB0@BN6PR16MB1425.namprd16.prod.outlook.com>
References: <CANO7kWDd8NZ=svBONwzo6sE5YH3Y5MAdWFP2CQMiTg7M-b47AQ@mail.gmail.com> <c9ef837c-bf7c-decb-9542-8a9ddeda67fd@akamai.com> <E3AB81FC-D841-47A6-A0E2-775461779770@mozilla.com> <CANO7kWA4tmK7Di59tsjvCBoDdh-jW83FxMpqQH1-iSPGLS=mpA@mail.gmail.com> <8d57a9e5-5697-38f5-1b85-bf55930c6461@akamai.com>
In-Reply-To: <8d57a9e5-5697-38f5-1b85-bf55930c6461@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 11.0.200.100
dlp-reaction: no-action
authentication-results: spf=none (sender IP is ) smtp.mailfrom=TirumaleswarReddy_Konda@McAfee.com; 
x-originating-ip: [161.69.163.25]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR16MB1540; 7:hgdDT7q7sOSJQubPEC8FDgNCWcmA7b+ORSQCcfltI2Lvkp0RPBrIW4NRgLiMBsV/b6D7KMmRI9Xs8hz4kwMyU+6hfhCLQx5aq664VEUvXJ88SikP3Ad4WYo1DfdrEJQuUZxXu6Xk6syyBiqRAgqTUSEk0fOw4xRe+AoNlmQKaI8YupXbITX+xaeoSNFmmzf+/PukkYVb/AppFpueKQ0+214jHumDDUXleAxbv7CteB5SIAuMpA5QoaNi+gU/DGkH
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: f9c71825-7e85-49d4-bb98-08d58e745cfb
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BN6PR16MB1540; 
x-ms-traffictypediagnostic: BN6PR16MB1540:
x-microsoft-antispam-prvs: <BN6PR16MB1540391743BA1A0D5C5B5B69EAAB0@BN6PR16MB1540.namprd16.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(95692535739014);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(3231221)(944501244)(52105095)(10201501046)(3002001)(6041310)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123558120)(20161123562045)(6072148)(201708071742011); SRVR:BN6PR16MB1540; BCL:0; PCL:0; RULEID:; SRVR:BN6PR16MB1540; 
x-forefront-prvs: 061725F016
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(39380400002)(39860400002)(366004)(396003)(376002)(32952001)(189003)(199004)(13464003)(72206003)(2906002)(106356001)(2900100001)(97736004)(5660300001)(14454004)(6506007)(53546011)(8936002)(53936002)(3846002)(966005)(6116002)(6246003)(93886005)(6436002)(26005)(186003)(55016002)(80792005)(77096007)(99286004)(105586002)(305945005)(316002)(74316002)(7696005)(7736002)(66066001)(102836004)(478600001)(9686003)(6306002)(76176011)(68736007)(33656002)(2950100002)(110136005)(25786009)(86362001)(4326008)(54906003)(229853002)(3280700002)(81166006)(81156014)(3660700001)(8676002)(85282002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR16MB1540; H:BN6PR16MB1425.namprd16.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: McAfee.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: z6fBB1TwCpEcGEFNGSpkC9eq6Xiz2kp5Q7SmA0RRASkAs20FSevGwPE9mTUGGw9fxtYZArrzlObhVsAPaFhM27mLsP6MTTrirpJV6lva2DVncS82+zw8XLD3+PCF1+EihhassX42LlDbD/EjiUsP0b6qufeSCbY04GTDXyhcfm523uOPpc/hPWpDSN+wM8WuqcTpRZUG3kqk6lvYlEHhpGs/9YIQlfgpciRqoTCR1h/nlDf90cAyK4jekfmKmw3VlUj1TQk9YHXi6pnxVkKB/9C39XhVXPZb756RF8CK3ShJqElV5pyw8buXLtwbTNYlbDSeafvvAKfksccGpRXp3w==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: f9c71825-7e85-49d4-bb98-08d58e745cfb
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Mar 2018 15:07:56.9874 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4943e38c-6dd4-428c-886d-24932bc2d5de
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR16MB1540
X-OriginatorOrg: mcafee.com
X-NAI-Spam-Flag: NO
X-NAI-Spam-Level: 
X-NAI-Spam-Threshold: 15
X-NAI-Spam-Score: 0.1
X-NAI-Spam-Version: 2.3.0.9418 : core <6246> : inlines <6507> : streams <1781753> : uri <2611694>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/m6fdSGHJZ-zXwIOAgCslBAHP7Bo>
Subject: Re: [tram] Allow TURN to forward inbound connectivity checks without permission
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2018 15:08:59 -0000

> -----Original Message-----
> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Brandon Williams
> Sent: Tuesday, March 20, 2018 3:02 PM
> To: Simon Perreault <sperreault@jive.com>; Nils Ohlmeier
> <nohlmeier@mozilla.com>
> Cc: Cullen Jennings <fluffy@cisco.com>; Eric Rescorla <ekr@rtfm.com>;
> tram@ietf.org
> Subject: Re: [tram] Allow TURN to forward inbound connectivity checks wit=
hout
> permission
>=20
> On 03/20/2018 06:07 AM, Simon Perreault wrote:
> > Same opinion here. The point of permissions is to prevent TURN clients
> > from being able to run generic servers. It seems like always allowing
> > STUN packets would preserve this feature while solving the session
> > establishment latency problem. And would be quite a bit simpler to
> > implement than ufrag perms. Have your cake, eat it, and eat it a
> > second time.
>=20
> If you want to prevent someone from running a server on the allocation yo=
u
> can't assume that a STUN-looking packet is actually legitimate, so some
> additional validations would be required. Perhaps packet size, rate-limit=
ing, and
> max session counts are enough.

TURN server can also check for the presence of username and MI in the=20
STUN packets.

-Tiru

>=20
> ufrag permissions didn't do enough to be more meaningful there, since it =
would
> be easy to post the ufrag somewhere public via a mechanism similar to dyn=
amic
> DNS.
>=20
> --Brandon
>=20
>=20
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram


From nobody Tue Mar 20 12:55:31 2018
Return-Path: <karl@ingate.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A56741241F5 for <tram@ietfa.amsl.com>; Tue, 20 Mar 2018 12:55:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.001
X-Spam-Level: 
X-Spam-Status: No, score=-1.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MSGID_MULTIPLE_AT=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ingate.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sQ3WwV4dtjvQ for <tram@ietfa.amsl.com>; Tue, 20 Mar 2018 12:55:26 -0700 (PDT)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-he1eur02on0614.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe05::614]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A08B212025C for <tram@ietf.org>; Tue, 20 Mar 2018 12:55:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ingate.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=FqjDAxOXKlYgiTcY3+B77/01Dl+VIehZSISl3TPqNTY=; b=X9W7543EM4v2w5WAAdajTKCpKNn9g8TbU7eiIi7KCiWPBy8kcjVA0aPt1iFImWX9N7tnl21QB0bCAnJScEhbyrBvxWuoZqwIoAuVHzQNd8TU+ulFknSIzn7p/HQZOX1Y5c5BVXt0wUpkZ09Ld16P/YpXX3zaLbFdNf3FFwrrvMQ=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=karl@ingate.com; 
Received: from Kallei7 (90.229.133.175) by VI1PR01MB1838.eurprd01.prod.exchangelabs.com (2a01:111:e400:7bd8::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.588.14; Tue, 20 Mar 2018 19:55:20 +0000
From: "Karl Stahl" <karl.stahl@ingate.com>
To: "'Konda, Tirumaleswar Reddy'" <TirumaleswarReddy_Konda@McAfee.com>, <tram@ietf.org>
References: <152136260256.18150.10551009018364033510@ietfa.amsl.com> <BN6PR16MB1425D61744AC7480972C800AEAD50@BN6PR16MB1425.namprd16.prod.outlook.com>
In-Reply-To: <BN6PR16MB1425D61744AC7480972C800AEAD50@BN6PR16MB1425.namprd16.prod.outlook.com>
Date: Tue, 20 Mar 2018 20:55:15 +0100
Message-ID: <031e01d3c085$5f581db0$1e085910$@stahl@ingate.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHTvpVCIExz03qGwU2I9I0I/uh+eqPVrxXQgAOrdjA=
Content-Language: sv
X-Originating-IP: [90.229.133.175]
X-ClientProxiedBy: AM6PR07CA0019.eurprd07.prod.outlook.com (2603:10a6:209:2a::32) To VI1PR01MB1838.eurprd01.prod.exchangelabs.com (2a01:111:e400:7bd8::24)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 545b27fb-9bb1-41f4-7c0e-08d58e9c8360
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(5600026)(4604075)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(2017052603328)(7153060)(7193020); SRVR:VI1PR01MB1838; 
X-Microsoft-Exchange-Diagnostics: 1; VI1PR01MB1838; 3:i/jkaeu4JjYbO6Rwhw9C74YMlYeqlbIPlYgNY4agGieN4dom1yW1ULy34Bf3WBSkdbIbJqbP6JcnA4jpi4slJMsQrzUOgaT2dEhafah9iLmp3E0Rmi13zlv0atdRNpDGsclBJpXiIV7TAkwx3TO2SVInGg15hVXs8QkRwT0uMSZxRHYwCWn305nAYi1MC+v8m3bCd9LbMdKVpKdiQCeL5wQCKsEGOjV+vpVn06ERNN7Tgj3ICWDPpV6BP2w8fw94; 25:Y450nuXcK+KVKNI6+9z/lUFH8QU449z9ONLfidR7xdzx+GtRDd0SRVOdMIrdehlVamyeEySmlTutbW/m+fRzFnQm+W1/Zz/yW3LQUPBqqmTH2AYsJs8jBXUDWc444a7vqme9morLoweSbs9GQk+YrUFiaOl1ZKZWWzMuKHzAt0hxz5+W7x/o5abklLe5lejBlTA1Hee4TOYzu5tZ+BeMQ+f7VyvpxJSITs4uZvKyi8GCik+vr/9gpb6rKn+/mjYqCmLSenkgY4hWxkFBXrQjmCNmBkqgXO9aOJDKtlO+KyLbcp0yBBH0RRkTd8M1r6gIHm+rX64I+z+Ou+UzD0CAuA==; 31:taur9SmFF4dqqX/aEjJpivl42KhQF8MB3H92CHA1X9+rUVKOKqC7sgfRRo4/SMiNq1YshjHf1EtlcR3/e4cI+DeRrwgFG7VQWeQeWd/O6ot/C6k5SrSdv+GO7++NdWqlTcKk5Saqc9rAY4uwoZBmHN+C6xqmN93KrmDZjvxNjPkZiMAYdO7KeKuyCBU9Ld24HaMcbuK1bOL2FgFqORzOmE5fggyvXu/kGTv5Ho0ig74=
X-MS-TrafficTypeDiagnostic: VI1PR01MB1838:
X-Microsoft-Antispam-PRVS: <VI1PR01MB1838C7B89E6277FBD923EF3AB1AB0@VI1PR01MB1838.eurprd01.prod.exchangelabs.com>
X-Exchange-Antispam-Report-Test: UriScan:(158342451672863)(120809045254105)(213716511872227)(123452027830198); 
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(3231221)(944501314)(52105095)(10201501046)(3002001)(6041310)(20161123560045)(20161123558120)(20161123564045)(2016111802025)(20161123562045)(6072148)(6043046)(201708071742011); SRVR:VI1PR01MB1838; BCL:0; PCL:0; RULEID:; SRVR:VI1PR01MB1838; 
X-Microsoft-Exchange-Diagnostics: 1; VI1PR01MB1838; 4:7g122dgdbjD3jshWaC4tf+fMqUmob4RArYTY39fbpjK5YNUX4FJ7TcH9+KXiJ1VBbHZBQxjHDxi2nFtgQ9Mt6Bb+JoLHHJz4gNZCrlGNqM7ymEwnrc5ulTBsX0Td3l9HLAXj5T+/iUW7YSEp+ERqrHf3oA4aC8Hpm+dyP+fugtcki9ms1ka38b2pYEklDjQf7UFcEkRGGeeU0vOZmog9XWPztr0x/BVqfV4TpWVYQaUpZZo8sCfPhs3M7KlN2isXE+nbzKK9a2wPC5yG12+pChI9y30n426qQpnVJ1kceXn+Wsed4GzJ+qEO5fkZDpBKQo8PR2ekUPBra4kpKSfFXPurhqUhaVcDRLtoIcm/Ibcb5YqUdn3xVmEoBJvQW5LvQwTKd5cLFq0M418NEOL663EpG7meHjomaznD9fW9g3Y=
X-Forefront-PRVS: 061725F016
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(366004)(376002)(396003)(39380400002)(346002)(39830400003)(13464003)(377424004)(199004)(189003)(38534002)(52116002)(1420700001)(50226002)(6496006)(59450400001)(81166006)(110136005)(3846002)(105586002)(81156014)(386003)(33896004)(6116002)(76176011)(8936002)(8746002)(53546011)(102836004)(478600001)(966005)(26005)(50466002)(305945005)(36756003)(7736002)(5660300001)(8676002)(2950100002)(96836002)(68736007)(47776003)(16526019)(186003)(97736004)(66066001)(61296003)(9686003)(6306002)(61793004)(106356001)(2906002)(6666003)(84116003)(23756003)(53936002)(14726001)(25786009)(44736005)(6486002)(316002)(21314002)(2101003); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR01MB1838; H:Kallei7; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: ingate.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?iso-8859-1?Q?1; VI1PR01MB1838; 23:Ml+hzgI6YYMI0gg7N2dNAyFl23GLtzUM7gBvsng?= =?iso-8859-1?Q?r/gvZfHzjPGnHl8OrILygaZEX1LJ225z/Hx4MFUhY2Zqzqo/UB0T+6qQJ5?= =?iso-8859-1?Q?xtNT0+Tl04fD+TogmI2ScJcRCl96z/VOqAR7x5fbGq+GSRwMcihPIDwu0h?= =?iso-8859-1?Q?B1N3c3Tmqtn0+mn6VIxuwEr/j0IhVngfDvO0itV/0aEvzxi5BfNo2kzURw?= =?iso-8859-1?Q?XwsYaTfpXzfPwZdIxS7rOpEvDML7ERbct2DANJEj35DUlsKc3P+EaXm0uV?= =?iso-8859-1?Q?gvLYKylvfj1Avu/M9mkoyGt47lSXoPlfQ91bMgx+NdblyaqbgyjicFxE3D?= =?iso-8859-1?Q?YYhazJE6IHrZo5PuictlUjpvWtZ6TpmurJitMKs0kmzkkzRJDwyRzAjIeD?= =?iso-8859-1?Q?SQzAnz4KJrdjbQ96WITS7h/PtsfbrCLb6++NvA4cJyx1x+iKAw0Wq/rjFY?= =?iso-8859-1?Q?23wnlq/ikQokgVVw0UxmOsVsD5HkBBUrfWfOZFj5iWwzSp43jN4lMg7Jc3?= =?iso-8859-1?Q?8zbdQ7b1BCtJhUbPwMwV3XkMRr+eqLs+vqcOmMBMF+7IARyc+XCDDDVjml?= =?iso-8859-1?Q?BZdPsojIgp3awCQMxc1jcbRkLiUYeLi5sQBpq9QnlrrSEKyrB4CEahR2+O?= =?iso-8859-1?Q?I/WC7hzDps0xrS5zr278iMUjN7uYpcQ4sx38rGMUpkElulMQO6PczGMAdS?= =?iso-8859-1?Q?WdSf9lesZSLhHILPrw1eEaOTeiTIX78qLYLDAVwa9kuRZglJCOsBpcXASI?= =?iso-8859-1?Q?N4qjoe1C0+fSzr0/dAPdkK0OTJnuHawxA0c3pCCzLE1Z9keYfcVQKicojw?= =?iso-8859-1?Q?HWC4ooTBMELNcEMIH+XwxordYH9R2jqCguYgUQtkNvGiyGifGBsPX5gYcc?= =?iso-8859-1?Q?ROdRDJmrEnPQttQsjiqiSz16U0J9+f2HndXjdB/1ik5Yd2azr8kQrQhN77?= =?iso-8859-1?Q?1/hDV/qxmMP40yW9EXUC8cGS2b9wlfJVB5FmceOA6/yfIf8TNICBXhQvrf?= =?iso-8859-1?Q?i6HAqJg/lcs9mxqeGe16okPabkAJ8NXhfi1kkgHOz7HbvrkFc1B2mLpu2G?= =?iso-8859-1?Q?QmzOss4JyE9xdr3AKvVPv0nwTSQGxKgeTd+eYBmw2WqHOUeyai7FQK2oTC?= =?iso-8859-1?Q?DHyx/ll2lCKy2kDsvVnnlpNzD0SbAf4xZtZIsO57YGx907cdCw2wNE497B?= =?iso-8859-1?Q?WGqibNEXunqeAxYu87yh+FgkaKBZ7XXXnZ0g+hh/SMzkiLd8MGukfaqRj0?= =?iso-8859-1?Q?6P1GnBWvEY6NcvxN7xBFqyIXO+RSf6azvW10YrkVU2MK3uwMs3z32eIrbE?= =?iso-8859-1?Q?Pc9UU5mch3W/SSHmMg7YZsKEmZG2kEDDo/rI75kJ1j1lgfY49clMke5GXU?= =?iso-8859-1?Q?XJuL6MQ0PU/lsiAL56LhQ+qO3XPbX8P26oucqjBQal7dOne14mKMSdoGRr?= =?iso-8859-1?Q?mAoeD+46o2zJAgJ8SHSUPCW7eMpiKQ1Ow3q1RyoAH6MAqOJH7X3nd7bvg?= =?iso-8859-1?Q?=3D=3D?=
X-Microsoft-Antispam-Message-Info: 2dyAGzHD/mmX0ymXSDzaEspEFmUGGRGNVVvAHSrzVV/pMuubbXeVREJtbEVJ2A298o8tHop4dkYBLwolU/UuKTxeZ63u3q+vMZPJ2OZDJMjctguLnuAxUabeN++hxUKRBzZtx5u4598t9HUQt0SdJJ9g5GaDxY+MadKj/jBjQ58QiDlWu/cBGfuWCF6TTgX0
X-Microsoft-Exchange-Diagnostics: 1; VI1PR01MB1838; 6:6fOiIrxXjOwUxww+cOH4r8RDoec8MqMmI2zuQHL28d0/RTEdrHCCf+vf9WF4X8j23zQfDlzjMzm1jttu0RRczpaleF5BQr4MWvARys618JiJIMKrRCarXvszEnDOqMn0Ingzeo7Ay13O2qcJ6Qz22ouKMurlQY14hU7Acd21U41Aqdb7hIRt83/n/9VvLRmMIzslp4zNgQhMHID8oAXMyYjZrcnJQ13lx31ITtMe/BA0osgGvWoFL5lvoFomPuVs1OJOqLMST8KdjtkxA2rvDLc2ouzIRfjNgDY9ZZeiDEth9pQOBinSToW/I5kysXodqbTet8hW5aKl/sVJAb3CkklFup7a+s2kw4DEfpxIILc=; 5:gyK/Lyl5GG0S3xTS7DY54FS1FlWVwnS9WgdNNIIxBfAidm9m1VJqC5qoVHB+5qCsmcIPe1wnZNP0FG749oiUtCqSnW9fIiTzgroh2IP5dP9RK3s1tH8pfvq3Es03NVy8tR0MR2MuJuE3BcJLxq9SLtORbnFMz+05HQkn/68wK/I=; 24:c+6dJBacpTUxG3QTzQ9E4bdJQdlYq/clHqKmfBue4EoY0mVNfPF16IWMiF8y3B8KRmXFbjFvjWnJhsxk7iWTU6frOqGyXxWJzvqcgKHmIy0=; 7:4O+7FHhuBjtbbz8jVV/87QUwshdmcscUteNYu+Wl3C0t6/K9RiwTIQ4sA2myDw7pL3jdO2syilcjoGN/6dZIQM75ywKSpFntfHtVNz1rt3KNB3BgcIWWShqyeT3YC+u+jUyMeZ1z1p4Vi7g+Hlff50W0xorU7agSpT67ywCUkMp/Ts4r0VDAaG0Np4bX0MhLrJeaEyH9zihjx41d0iA22TqocEVRdUbobOVyoW5ub3EBaQodrZ03vPuFsm7TVJ9R
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: ingate.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 20 Mar 2018 19:55:20.9380 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 545b27fb-9bb1-41f4-7c0e-08d58e9c8360
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: c3eda49a-3ed0-46c6-8a9e-d0d8ce3d2fae
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR01MB1838
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/AootRCE14Z4pjpJlnPWRVU1xlqY>
Subject: [tram] Multiple allocations SV: I-D Action: draft-ietf-tram-turnbis-15.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2018 19:55:29 -0000

> This revision addresses comments from Mark, Karl and Noriyuki Torii.
My comment about need for multiple allocations is NOT addressed.

Let me explain more clearly why multiple allocations is needed:

ICE is about finding all/many paths for the media, e.g. with the help of
TURN servers.
Those paths are not over ONE IPv4 network, over ONE IPv6 network or =
EXACTLY
ONE OF EACH.=20
If fact, it is more common that you have several IPv4 networks paths.

Now that we have network provided TURN servers, you only ask for =
Allocation
once (contrary to application provided TURN servers, where you can be
directed to Allocate several times.) and thus we need all relay =
addresses in
one allocation request.

Wasn't that the reason dual allocation was requested? The need for =
multiple
allocation is stronger!

Please address this, e.g. like below (seems you are almost there).

/Karl


******************* Previous *******************

Allowing a turn allocation to return multiple relayed transport =
addresses,
beyond ONE IPv4 and ONE IPv6 (which may sit on the same or on different
interfaces/network segments), seems like very small step now when the =
dual
allocation was put in place in this draft. We certainly need it (some
reasons below) if TURN is going to be used where needed and we cannot =
wait
for any additional draft.

Seems like it is sufficient to extent this table (found in draft 14) =
with 3
new values (as shown):=20

16.  STUN Attributes

   This STUN extension defines the following attributes:

     0x000C: CHANNEL-NUMBER
     0x000D: LIFETIME
     0x0010: Reserved (was BANDWIDTH)
     0x0012: XOR-PEER-ADDRESS
     0x0013: DATA
     0x0016: XOR-RELAYED-ADDRESS
     0x0017: REQUESTED-ADDRESS-FAMILY
     0x0018: EVEN-PORT
     0x0019: REQUESTED-TRANSPORT
     0x001A: DONT-FRAGMENT
     0x0021: Reserved (was TIMER-VAL)
     0x0022: RESERVATION-TOKEN
     TBD-CA: ADDITIONAL-ADDRESS-FAMILY
ADDITIONAL-ADDRESS-ALL
ADDITIONAL-ADDRESS-ALLV4
ADDITIONAL-ADDRESS-ALLV6
     TBD-CA: ADDRESS-ERROR-CODE
     TBD-CA: ICMP

Actually, browsing through the draft for ADDITIONAL-ADDRESS-FAMILY, very
little text seems to be added for generalization to  =
ADDITIONAL-ADDRESS-xxx.
Almost everything applies to ADDITIONAL-ADDRESS-xxx and can be reused.

ADDITIONAL-ADDRESS-ALL should be the default for any modern TURN client. =


Check! - We need this now.

Thanks,
Karl

> -----Original Message-----
> From: Karl Stahl [mailto:karl.stahl@ingate.com]
> Sent: Sunday, March 4, 2018 10:36 PM
> To: 'Marc Petit-Huguenin' <petithug@acm.org>; Konda, Tirumaleswar =
Reddy
> <TirumaleswarReddy_Konda@McAfee.com>; tram@ietf.org
> Subject: SV: [tram] Review of dual allocation in TURNbis-11
>=20
> Hi,
>=20
> When we now have "dual allocation" into this draft (I see on page 26: =
"If
the
> client wishes to obtain one IPv6 and one IPv4 relayed transport =
address
then
> it includes an ADDITIONAL-ADDRESS-FAMILY transport address then it") =
can
> we not generalize that further and allow MORE THAN ONE relayed =
transport
> address (of any family) in response to an allocation?
>=20
> I mean that a TURN server could have several relay interfaces at =
different
IP-
> addresses into different networks - not just the Internet, but also a =
VoIP
> (higher quality) network e.g. by some triple play service provider, an =
IMS
> network or some branch office network.
>=20
> I think this is specifically important for network provided/auto
discovered
> turn servers (application provided turn servers could instead just =
list
several
> turn servers).
>=20
> I saw someone snipped this about "SINGLE relayed transport address per
> allocation request"
> > > https://tools.ietf.org/html/rfc6156#section-3
> > > <snip>
> > >
> > >    TURN servers allocate a single relayed transport address per
> > >    allocation request.  Therefore, Allocate requests cannot carry =
more
> > >    than one REQUESTED-ADDRESS-FAMILY attribute.  Consequently, a
> client
> > >    that wishes to allocate more than one relayed transport address =
at
a
> > >    TURN server (e.g., an IPv4 and an IPv6 address) needs to =
perform
> > >    several allocation requests (one allocation request per relayed
> > >    transport address).
> > > </snip>
>=20
> but if that is remedied now, it seems like a small step to generalize =
so
we can
> get multiple relayed transport addresses from one allocate request?
>=20
> /Karl


-----Ursprungligt meddelande-----
Fr=E5n: tram [mailto:tram-bounces@ietf.org] F=F6r Konda, Tirumaleswar =
Reddy
Skickat: den 18 mars 2018 09:51
Till: tram@ietf.org
=C4mne: Re: [tram] I-D Action: draft-ietf-tram-turnbis-15.txt

This revision addresses comments from Mark, Karl and Noriyuki Torii.

-Tiru

> -----Original Message-----
> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of internet-
> drafts@ietf.org
> Sent: Sunday, March 18, 2018 8:43 AM
> To: i-d-announce@ietf.org
> Cc: tram@ietf.org
> Subject: [tram] I-D Action: draft-ietf-tram-turnbis-15.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> This draft is a work item of the TURN Revised and Modernized WG of the
> IETF.
>=20
>         Title           : Traversal Using Relays around NAT (TURN): =
Relay
Extensions
> to Session Traversal Utilities for NAT (STUN)
>         Authors         : Tirumaleswar Reddy
>                           Alan Johnston
>                           Philip Matthews
>                           Jonathan Rosenberg
> 	Filename        : draft-ietf-tram-turnbis-15.txt
> 	Pages           : 84
> 	Date            : 2018-03-18
>=20
> Abstract:
>    If a host is located behind a NAT, then in certain situations it =
can
>    be impossible for that host to communicate directly with other =
hosts
>    (peers).  In these situations, it is necessary for the host to use
>    the services of an intermediate node that acts as a communication
>    relay.  This specification defines a protocol, called TURN =
(Traversal
>    Using Relays around NAT), that allows the host to control the
>    operation of the relay and to exchange packets with its peers using
>    the relay.  TURN differs from some other relay control protocols in
>    that it allows a client to communicate with multiple peers using a
>    single relay address.
>=20
>    The TURN protocol was designed to be used as part of the ICE
>    (Interactive Connectivity Establishment) approach to NAT traversal,
>    though it also can be used without ICE.
>=20
>    This document obsoletes RFC 5766 and RFC 6156.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tram-turnbis/
>=20
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-tram-turnbis-15
> https://datatracker.ietf.org/doc/html/draft-ietf-tram-turnbis-15
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tram-turnbis-15
>=20
>=20
> Please note that it may take a couple of minutes from the time of
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram

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


From nobody Tue Mar 20 13:35:08 2018
Return-Path: <oej@edvina.net>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB713124D6C for <tram@ietfa.amsl.com>; Tue, 20 Mar 2018 13:35:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r8XAKkM3lvOt for <tram@ietfa.amsl.com>; Tue, 20 Mar 2018 13:35:03 -0700 (PDT)
Received: from smtp7.webway.se (smtp7.webway.se [212.3.14.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B070C12946D for <tram@ietf.org>; Tue, 20 Mar 2018 13:34:57 -0700 (PDT)
Received: from [192.168.40.3] (h-205-12.A165.corp.bahnhof.se [176.10.205.12]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp7.webway.se (Postfix) with ESMTPSA id 26662306D; Tue, 20 Mar 2018 21:34:53 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: "Olle E. Johansson" <oej@edvina.net>
In-Reply-To: <031e01d3c085$5f581db0$1e085910$@stahl@ingate.com>
Date: Tue, 20 Mar 2018 21:34:53 +0100
Cc: Olle E Johansson <oej@edvina.net>, "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>, tram@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <BEC020EA-C973-48E5-A918-EF2D25953E33@edvina.net>
References: <152136260256.18150.10551009018364033510@ietfa.amsl.com> <BN6PR16MB1425D61744AC7480972C800AEAD50@BN6PR16MB1425.namprd16.prod.outlook.com> <031e01d3c085$5f581db0$1e085910$@stahl@ingate.com>
To: Karl Stahl <karl.stahl@ingate.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/yRqIF1uMw-w3sRPdXjicEBJVh7M>
Subject: Re: [tram] Multiple allocations SV: I-D Action: draft-ietf-tram-turnbis-15.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2018 20:35:07 -0000

> On 20 Mar 2018, at 20:55, Karl Stahl <karl.stahl@ingate.com> wrote:
>=20
>> This revision addresses comments from Mark, Karl and Noriyuki Torii.
> My comment about need for multiple allocations is NOT addressed.
>=20
> Let me explain more clearly why multiple allocations is needed:
>=20
> ICE is about finding all/many paths for the media, e.g. with the help =
of
> TURN servers.
> Those paths are not over ONE IPv4 network, over ONE IPv6 network or =
EXACTLY
> ONE OF EACH.=20
> If fact, it is more common that you have several IPv4 networks paths.
>=20
> Now that we have network provided TURN servers, you only ask for =
Allocation
> once (contrary to application provided TURN servers, where you can be
> directed to Allocate several times.) and thus we need all relay =
addresses in
> one allocation request.

I agree with Karl here, for network-provided turn servers (which is not =
defined
in the terminology section here on in 8155) I think there are use cases =
for=20
multiple addresses in multiple families.=20

I also understand that this will make the draft more complex. Consider
the case where a turn server have two IPv4 networks and one IPv6
and have run out of possible allocations on one IPv4 network - should
it send what=E2=80=99s available or send an error message and fail =
completely?

Regardless, this is a good time to fix this.

/O


>=20
> Wasn't that the reason dual allocation was requested? The need for =
multiple
> allocation is stronger!
>=20
> Please address this, e.g. like below (seems you are almost there).
>=20
> /Karl
>=20
>=20
> ******************* Previous *******************
>=20
> Allowing a turn allocation to return multiple relayed transport =
addresses,
> beyond ONE IPv4 and ONE IPv6 (which may sit on the same or on =
different
> interfaces/network segments), seems like very small step now when the =
dual
> allocation was put in place in this draft. We certainly need it (some
> reasons below) if TURN is going to be used where needed and we cannot =
wait
> for any additional draft.
>=20
> Seems like it is sufficient to extent this table (found in draft 14) =
with 3
> new values (as shown):=20
>=20
> 16.  STUN Attributes
>=20
>   This STUN extension defines the following attributes:
>=20
>     0x000C: CHANNEL-NUMBER
>     0x000D: LIFETIME
>     0x0010: Reserved (was BANDWIDTH)
>     0x0012: XOR-PEER-ADDRESS
>     0x0013: DATA
>     0x0016: XOR-RELAYED-ADDRESS
>     0x0017: REQUESTED-ADDRESS-FAMILY
>     0x0018: EVEN-PORT
>     0x0019: REQUESTED-TRANSPORT
>     0x001A: DONT-FRAGMENT
>     0x0021: Reserved (was TIMER-VAL)
>     0x0022: RESERVATION-TOKEN
>     TBD-CA: ADDITIONAL-ADDRESS-FAMILY
> ADDITIONAL-ADDRESS-ALL
> ADDITIONAL-ADDRESS-ALLV4
> ADDITIONAL-ADDRESS-ALLV6
>     TBD-CA: ADDRESS-ERROR-CODE
>     TBD-CA: ICMP
>=20
> Actually, browsing through the draft for ADDITIONAL-ADDRESS-FAMILY, =
very
> little text seems to be added for generalization to  =
ADDITIONAL-ADDRESS-xxx.
> Almost everything applies to ADDITIONAL-ADDRESS-xxx and can be reused.
>=20
> ADDITIONAL-ADDRESS-ALL should be the default for any modern TURN =
client.=20
>=20
> Check! - We need this now.
>=20
> Thanks,
> Karl
>=20
>> -----Original Message-----
>> From: Karl Stahl [mailto:karl.stahl@ingate.com]
>> Sent: Sunday, March 4, 2018 10:36 PM
>> To: 'Marc Petit-Huguenin' <petithug@acm.org>; Konda, Tirumaleswar =
Reddy
>> <TirumaleswarReddy_Konda@McAfee.com>; tram@ietf.org
>> Subject: SV: [tram] Review of dual allocation in TURNbis-11
>>=20
>> Hi,
>>=20
>> When we now have "dual allocation" into this draft (I see on page 26: =
"If
> the
>> client wishes to obtain one IPv6 and one IPv4 relayed transport =
address
> then
>> it includes an ADDITIONAL-ADDRESS-FAMILY transport address then it") =
can
>> we not generalize that further and allow MORE THAN ONE relayed =
transport
>> address (of any family) in response to an allocation?
>>=20
>> I mean that a TURN server could have several relay interfaces at =
different
> IP-
>> addresses into different networks - not just the Internet, but also a =
VoIP
>> (higher quality) network e.g. by some triple play service provider, =
an IMS
>> network or some branch office network.
>>=20
>> I think this is specifically important for network provided/auto
> discovered
>> turn servers (application provided turn servers could instead just =
list
> several
>> turn servers).
>>=20
>> I saw someone snipped this about "SINGLE relayed transport address =
per
>> allocation request"
>>>> https://tools.ietf.org/html/rfc6156#section-3
>>>> <snip>
>>>>=20
>>>>   TURN servers allocate a single relayed transport address per
>>>>   allocation request.  Therefore, Allocate requests cannot carry =
more
>>>>   than one REQUESTED-ADDRESS-FAMILY attribute.  Consequently, a
>> client
>>>>   that wishes to allocate more than one relayed transport address =
at
> a
>>>>   TURN server (e.g., an IPv4 and an IPv6 address) needs to perform
>>>>   several allocation requests (one allocation request per relayed
>>>>   transport address).
>>>> </snip>
>>=20
>> but if that is remedied now, it seems like a small step to generalize =
so
> we can
>> get multiple relayed transport addresses from one allocate request?
>>=20
>> /Karl
>=20
>=20
> -----Ursprungligt meddelande-----
> Fr=C3=A5n: tram [mailto:tram-bounces@ietf.org] F=C3=B6r Konda, =
Tirumaleswar Reddy
> Skickat: den 18 mars 2018 09:51
> Till: tram@ietf.org
> =C3=84mne: Re: [tram] I-D Action: draft-ietf-tram-turnbis-15.txt
>=20
> This revision addresses comments from Mark, Karl and Noriyuki Torii.
>=20
> -Tiru
>=20
>> -----Original Message-----
>> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of internet-
>> drafts@ietf.org
>> Sent: Sunday, March 18, 2018 8:43 AM
>> To: i-d-announce@ietf.org
>> Cc: tram@ietf.org
>> Subject: [tram] I-D Action: draft-ietf-tram-turnbis-15.txt
>>=20
>>=20
>> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>> This draft is a work item of the TURN Revised and Modernized WG of =
the
>> IETF.
>>=20
>>        Title           : Traversal Using Relays around NAT (TURN): =
Relay
> Extensions
>> to Session Traversal Utilities for NAT (STUN)
>>        Authors         : Tirumaleswar Reddy
>>                          Alan Johnston
>>                          Philip Matthews
>>                          Jonathan Rosenberg
>> 	Filename        : draft-ietf-tram-turnbis-15.txt
>> 	Pages           : 84
>> 	Date            : 2018-03-18
>>=20
>> Abstract:
>>   If a host is located behind a NAT, then in certain situations it =
can
>>   be impossible for that host to communicate directly with other =
hosts
>>   (peers).  In these situations, it is necessary for the host to use
>>   the services of an intermediate node that acts as a communication
>>   relay.  This specification defines a protocol, called TURN =
(Traversal
>>   Using Relays around NAT), that allows the host to control the
>>   operation of the relay and to exchange packets with its peers using
>>   the relay.  TURN differs from some other relay control protocols in
>>   that it allows a client to communicate with multiple peers using a
>>   single relay address.
>>=20
>>   The TURN protocol was designed to be used as part of the ICE
>>   (Interactive Connectivity Establishment) approach to NAT traversal,
>>   though it also can be used without ICE.
>>=20
>>   This document obsoletes RFC 5766 and RFC 6156.
>>=20
>>=20
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-tram-turnbis/
>>=20
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-tram-turnbis-15
>> https://datatracker.ietf.org/doc/html/draft-ietf-tram-turnbis-15
>>=20
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tram-turnbis-15
>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of
> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>=20
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>=20
>> _______________________________________________
>> tram mailing list
>> tram@ietf.org
>> https://www.ietf.org/mailman/listinfo/tram
>=20
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram
>=20


From nobody Wed Mar 21 08:24:09 2018
Return-Path: <TirumaleswarReddy_Konda@mcafee.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91CC51275F4 for <tram@ietfa.amsl.com>; Wed, 21 Mar 2018 08:24:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.33
X-Spam-Level: 
X-Spam-Status: No, score=-4.33 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mcafee.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UcA3wcLwYa3g for <tram@ietfa.amsl.com>; Wed, 21 Mar 2018 08:24:04 -0700 (PDT)
Received: from DNVWSMAILOUT1.mcafee.com (dnvwsmailout1.mcafee.com [161.69.31.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90BB41242F5 for <tram@ietf.org>; Wed, 21 Mar 2018 08:24:04 -0700 (PDT)
X-NAI-Header: Modified by McAfee Email Gateway (5500)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mcafee.com; s=s_mcafee; t=1521645843; h=From: To:CC:Subject:Thread-Topic:Thread-Index:Date: Message-ID:References:In-Reply-To:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: dlp-product:dlp-version:dlp-reaction:authentication-results: x-originating-ip:x-ms-publictraffictype:x-microsoft-exchange-diagnostics: x-ms-exchange-antispam-srfa-diagnostics:x-ms-office365-filtering-correlation-id: x-microsoft-antispam:x-ms-traffictypediagnostic: x-microsoft-antispam-prvs:x-exchange-antispam-report-test: x-exchange-antispam-report-cfa-test:x-forefront-prvs: x-forefront-antispam-report:received-spf:x-microsoft-antispam-message-info: spamdiagnosticoutput:spamdiagnosticmetadata: Content-Type:Content-Transfer-Encoding:MIME-Version: X-MS-Exchange-CrossTenant-Network-Message-Id: X-MS-Exchange-CrossTenant-originalarrivaltime: X-MS-Exchange-CrossTenant-fromentityheader: X-MS-Exchange-CrossTenant-id:X-MS-Exchange-Transport-CrossTenantHeadersStamped: X-OriginatorOrg:X-NAI-Spam-Flag:X-NAI-Spam-Threshold: X-NAI-Spam-Score:X-NAI-Spam-Version; bh=A 2rFaRG/W6PKtXY8UwN/yjO6wI9dffw0tuutWcjUqI Q=; b=JyLOzOd9Qbf6nk6mgpg8qfe6BvvpMmqozLLptorPXnC2 JWKKhqJUVnYmhYz++73m+TaiOclBREbhc/jPLGCi7Ib/bsXYNl oKRrfzC5q+TTloYn55U6PTrHgoZV00reOVb93UP3OK8e+FqwUO yRvpfbW3hCfyr/C31sxSdJY8Zd0=
Received: from DNVEXAPP1N05.corpzone.internalzone.com (unknown [10.44.48.89]) by DNVWSMAILOUT1.mcafee.com with smtp (TLS: TLSv1/SSLv3,256bits,ECDHE-RSA-AES256-SHA384) id 213e_7af8_b182043a_7ae5_40ee_9c1e_8e2bbefdffd1; Wed, 21 Mar 2018 10:24:02 -0500
Received: from DNVEXUSR1N11.corpzone.internalzone.com (10.44.48.84) by DNVEXAPP1N05.corpzone.internalzone.com (10.44.48.89) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Wed, 21 Mar 2018 09:23:07 -0600
Received: from DNVEXUSR1N08.corpzone.internalzone.com (10.44.48.81) by DNVEXUSR1N11.corpzone.internalzone.com (10.44.48.84) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Wed, 21 Mar 2018 09:23:06 -0600
Received: from DNVO365EDGE2.corpzone.internalzone.com (10.44.176.74) by DNVEXUSR1N08.corpzone.internalzone.com (10.44.48.81) with Microsoft SMTP Server (TLS) id 15.0.1347.2 via Frontend Transport; Wed, 21 Mar 2018 09:23:06 -0600
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (10.44.176.240) by edge.mcafee.com (10.44.176.74) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Wed, 21 Mar 2018 09:23:03 -0600
Received: from BN6PR16MB1425.namprd16.prod.outlook.com (10.172.207.19) by BN6PR16MB1699.namprd16.prod.outlook.com (10.172.28.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.609.10; Wed, 21 Mar 2018 15:23:02 +0000
Received: from BN6PR16MB1425.namprd16.prod.outlook.com ([fe80::b9d0:eb7e:fb41:137d]) by BN6PR16MB1425.namprd16.prod.outlook.com ([fe80::b9d0:eb7e:fb41:137d%2]) with mapi id 15.20.0609.010; Wed, 21 Mar 2018 15:23:02 +0000
From: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>
To: "Olle E. Johansson" <oej@edvina.net>, Karl Stahl <karl.stahl@ingate.com>
CC: "tram@ietf.org" <tram@ietf.org>
Thread-Topic: Multiple allocations SV: [tram] I-D Action: draft-ietf-tram-turnbis-15.txt
Thread-Index: AQHTwIr66qpogqxcHEaAWopQQtB26KPaif/Q
Date: Wed, 21 Mar 2018 15:23:01 +0000
Message-ID: <BN6PR16MB1425327E5CD094CF18A040F2EAAA0@BN6PR16MB1425.namprd16.prod.outlook.com>
References: <152136260256.18150.10551009018364033510@ietfa.amsl.com> <BN6PR16MB1425D61744AC7480972C800AEAD50@BN6PR16MB1425.namprd16.prod.outlook.com> <031e01d3c085$5f581db0$1e085910$@stahl@ingate.com> <BEC020EA-C973-48E5-A918-EF2D25953E33@edvina.net>
In-Reply-To: <BEC020EA-C973-48E5-A918-EF2D25953E33@edvina.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 11.0.200.100
dlp-reaction: no-action
authentication-results: spf=none (sender IP is ) smtp.mailfrom=TirumaleswarReddy_Konda@McAfee.com; 
x-originating-ip: [161.69.163.25]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR16MB1699; 7:FpM/+GDWavG649pS1lkj4XnhkOJ8DHOXcCrlj6oXIiBQF98SosK0U9D1S/HsxwnZsI4mrcdorbLsNcZUTJV/F8mwhIBQ/zt9zUrycy4gpO4ZcmvduzDDZH3eZFLVxjG81rCetxMsMeD39hmP6lpb60bVZXTip1YiQRdEDSNtVpKC8YjQqsux9rbaE/LuRtc1ceQzopd+lqvdiVpYC5jYZoYiV1tp+JM40ErpacfcqP8+U2F+9RKzBJ89HLIqHznj
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: d690aa04-be50-4b7a-5052-08d58f3fa2e3
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BN6PR16MB1699; 
x-ms-traffictypediagnostic: BN6PR16MB1699:
x-microsoft-antispam-prvs: <BN6PR16MB1699F0F2368D2B3BE6A63E9AEAAA0@BN6PR16MB1699.namprd16.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(120809045254105)(213716511872227)(123452027830198); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3002001)(10201501046)(93006095)(93001095)(3231221)(944501244)(52105095)(6041310)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123558120)(6072148)(201708071742011); SRVR:BN6PR16MB1699; BCL:0; PCL:0; RULEID:; SRVR:BN6PR16MB1699; 
x-forefront-prvs: 0618E4E7E1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(979002)(396003)(39380400002)(376002)(346002)(39860400002)(366004)(377424004)(38534002)(52084003)(13464003)(32952001)(189003)(199004)(68736007)(81156014)(81166006)(8676002)(93886005)(8936002)(7696005)(6116002)(3846002)(76176011)(3280700002)(72206003)(53546011)(105586002)(59450400001)(53936002)(7736002)(26005)(305945005)(6436002)(9686003)(6306002)(6506007)(55016002)(97736004)(86362001)(4326008)(6246003)(5250100002)(229853002)(2906002)(5660300001)(74316002)(966005)(3660700001)(186003)(14454004)(316002)(80792005)(110136005)(2950100002)(25786009)(478600001)(2900100001)(102836004)(99286004)(106356001)(33656002)(66066001)(21314002)(85282002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR16MB1699; H:BN6PR16MB1425.namprd16.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: McAfee.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: W/XGIEQ49lwuiFHhfBxqr5GqvSOWqB/q7+m5+u6BoLGfwKMRdI9q/3nYahOEDSxsw3PS2mik5zaGPwZ1N7aHN+pRtZaBAkoE3LNVRNsk5GSQcmT8qWUrJV4xHEF16imYc6rVJRd9IWDcavy6IFKzaEUUXkwc63DSoMJyeFrSelYq2H0gX6dbqp+UpeDTWRhJz/xB3TmtpVPPGya4tdedE7f7P5lh1HpQ5ceV6HMv5ulNIKMP5HIe4wSEAusn7op3CtDUwcRMFuYflcRth6w7uNMwaM4NyZgvhoAiLcw0LjIw08mee/mBcWWbQ7dlVkkzbQGFpuUybP4GtAM646o1bQ==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d690aa04-be50-4b7a-5052-08d58f3fa2e3
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Mar 2018 15:23:02.0373 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4943e38c-6dd4-428c-886d-24932bc2d5de
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR16MB1699
X-OriginatorOrg: mcafee.com
X-NAI-Spam-Flag: NO
X-NAI-Spam-Threshold: 15
X-NAI-Spam-Score: 0
X-NAI-Spam-Version: 2.3.0.9418 : core <6247> : inlines <6510> : streams <1781849> : uri <2612277>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/JTuFEZddmq9xDKjHg5Ck5qMZ2bQ>
Subject: Re: [tram] Multiple allocations SV: I-D Action: draft-ietf-tram-turnbis-15.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2018 15:24:07 -0000

PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBPbGxlIEUuIEpvaGFuc3NvbiBb
bWFpbHRvOm9lakBlZHZpbmEubmV0XQ0KPiBTZW50OiBUdWVzZGF5LCBNYXJjaCAyMCwgMjAxOCA4
OjM1IFBNDQo+IFRvOiBLYXJsIFN0YWhsIDxrYXJsLnN0YWhsQGluZ2F0ZS5jb20+DQo+IENjOiBP
bGxlIEUgSm9oYW5zc29uIDxvZWpAZWR2aW5hLm5ldD47IEtvbmRhLCBUaXJ1bWFsZXN3YXIgUmVk
ZHkNCj4gPFRpcnVtYWxlc3dhclJlZGR5X0tvbmRhQE1jQWZlZS5jb20+OyB0cmFtQGlldGYub3Jn
DQo+IFN1YmplY3Q6IFJlOiBNdWx0aXBsZSBhbGxvY2F0aW9ucyBTVjogW3RyYW1dIEktRCBBY3Rp
b246IGRyYWZ0LWlldGYtdHJhbS10dXJuYmlzLQ0KPiAxNS50eHQNCj4gDQo+IA0KPiA+IE9uIDIw
IE1hciAyMDE4LCBhdCAyMDo1NSwgS2FybCBTdGFobCA8a2FybC5zdGFobEBpbmdhdGUuY29tPiB3
cm90ZToNCj4gPg0KPiA+PiBUaGlzIHJldmlzaW9uIGFkZHJlc3NlcyBjb21tZW50cyBmcm9tIE1h
cmssIEthcmwgYW5kIE5vcml5dWtpIFRvcmlpLg0KPiA+IE15IGNvbW1lbnQgYWJvdXQgbmVlZCBm
b3IgbXVsdGlwbGUgYWxsb2NhdGlvbnMgaXMgTk9UIGFkZHJlc3NlZC4NCj4gPg0KPiA+IExldCBt
ZSBleHBsYWluIG1vcmUgY2xlYXJseSB3aHkgbXVsdGlwbGUgYWxsb2NhdGlvbnMgaXMgbmVlZGVk
Og0KPiA+DQo+ID4gSUNFIGlzIGFib3V0IGZpbmRpbmcgYWxsL21hbnkgcGF0aHMgZm9yIHRoZSBt
ZWRpYSwgZS5nLiB3aXRoIHRoZSBoZWxwDQo+ID4gb2YgVFVSTiBzZXJ2ZXJzLg0KPiA+IFRob3Nl
IHBhdGhzIGFyZSBub3Qgb3ZlciBPTkUgSVB2NCBuZXR3b3JrLCBvdmVyIE9ORSBJUHY2IG5ldHdv
cmsgb3INCj4gPiBFWEFDVExZIE9ORSBPRiBFQUNILg0KPiA+IElmIGZhY3QsIGl0IGlzIG1vcmUg
Y29tbW9uIHRoYXQgeW91IGhhdmUgc2V2ZXJhbCBJUHY0IG5ldHdvcmtzIHBhdGhzLg0KPiA+DQo+
ID4gTm93IHRoYXQgd2UgaGF2ZSBuZXR3b3JrIHByb3ZpZGVkIFRVUk4gc2VydmVycywgeW91IG9u
bHkgYXNrIGZvcg0KPiA+IEFsbG9jYXRpb24gb25jZSAoY29udHJhcnkgdG8gYXBwbGljYXRpb24g
cHJvdmlkZWQgVFVSTiBzZXJ2ZXJzLCB3aGVyZQ0KPiA+IHlvdSBjYW4gYmUgZGlyZWN0ZWQgdG8g
QWxsb2NhdGUgc2V2ZXJhbCB0aW1lcy4pIGFuZCB0aHVzIHdlIG5lZWQgYWxsDQo+ID4gcmVsYXkg
YWRkcmVzc2VzIGluIG9uZSBhbGxvY2F0aW9uIHJlcXVlc3QuDQo+IA0KPiBJIGFncmVlIHdpdGgg
S2FybCBoZXJlLCBmb3IgbmV0d29yay1wcm92aWRlZCB0dXJuIHNlcnZlcnMgKHdoaWNoIGlzIG5v
dCBkZWZpbmVkIGluDQo+IHRoZSB0ZXJtaW5vbG9neSBzZWN0aW9uIGhlcmUgb24gaW4gODE1NSkg
SSB0aGluayB0aGVyZSBhcmUgdXNlIGNhc2VzIGZvciBtdWx0aXBsZQ0KPiBhZGRyZXNzZXMgaW4g
bXVsdGlwbGUgZmFtaWxpZXMuDQoNClRoZSBXRyBoYXMgb25seSBhZ3JlZWQgb24gZHVhbCBhbGxv
Y2F0aW9uLCB0aGlzIGlzIGEgbmV3IHJlcXVpcmVtZW50IGZvciBhIHNwZWNpZmljIGRlcGxveW1l
bnQgc2NlbmFyaW8uIA0KWW91IG1heSB3YW50IHRvIHN1Ym1pdCBhIG5ldyBkcmFmdCAoanVzdCBs
aWtlIHdlIGRpZCBmb3IgUkZDODE1NSkuIA0KDQotVGlydQ0KDQo+IA0KPiBJIGFsc28gdW5kZXJz
dGFuZCB0aGF0IHRoaXMgd2lsbCBtYWtlIHRoZSBkcmFmdCBtb3JlIGNvbXBsZXguIENvbnNpZGVy
IHRoZSBjYXNlDQo+IHdoZXJlIGEgdHVybiBzZXJ2ZXIgaGF2ZSB0d28gSVB2NCBuZXR3b3JrcyBh
bmQgb25lIElQdjYgYW5kIGhhdmUgcnVuIG91dCBvZg0KPiBwb3NzaWJsZSBhbGxvY2F0aW9ucyBv
biBvbmUgSVB2NCBuZXR3b3JrIC0gc2hvdWxkIGl0IHNlbmQgd2hhdOKAmXMgYXZhaWxhYmxlIG9y
DQo+IHNlbmQgYW4gZXJyb3IgbWVzc2FnZSBhbmQgZmFpbCBjb21wbGV0ZWx5Pw0KPiANCj4gUmVn
YXJkbGVzcywgdGhpcyBpcyBhIGdvb2QgdGltZSB0byBmaXggdGhpcy4NCj4gDQo+IC9PDQo+IA0K
PiANCj4gPg0KPiA+IFdhc24ndCB0aGF0IHRoZSByZWFzb24gZHVhbCBhbGxvY2F0aW9uIHdhcyBy
ZXF1ZXN0ZWQ/IFRoZSBuZWVkIGZvcg0KPiA+IG11bHRpcGxlIGFsbG9jYXRpb24gaXMgc3Ryb25n
ZXIhDQo+ID4NCj4gPiBQbGVhc2UgYWRkcmVzcyB0aGlzLCBlLmcuIGxpa2UgYmVsb3cgKHNlZW1z
IHlvdSBhcmUgYWxtb3N0IHRoZXJlKS4NCj4gPg0KPiA+IC9LYXJsDQo+ID4NCj4gPg0KPiA+ICoq
KioqKioqKioqKioqKioqKiogUHJldmlvdXMgKioqKioqKioqKioqKioqKioqKg0KPiA+DQo+ID4g
QWxsb3dpbmcgYSB0dXJuIGFsbG9jYXRpb24gdG8gcmV0dXJuIG11bHRpcGxlIHJlbGF5ZWQgdHJh
bnNwb3J0DQo+ID4gYWRkcmVzc2VzLCBiZXlvbmQgT05FIElQdjQgYW5kIE9ORSBJUHY2ICh3aGlj
aCBtYXkgc2l0IG9uIHRoZSBzYW1lIG9yDQo+ID4gb24gZGlmZmVyZW50IGludGVyZmFjZXMvbmV0
d29yayBzZWdtZW50cyksIHNlZW1zIGxpa2UgdmVyeSBzbWFsbCBzdGVwDQo+ID4gbm93IHdoZW4g
dGhlIGR1YWwgYWxsb2NhdGlvbiB3YXMgcHV0IGluIHBsYWNlIGluIHRoaXMgZHJhZnQuIFdlDQo+
ID4gY2VydGFpbmx5IG5lZWQgaXQgKHNvbWUgcmVhc29ucyBiZWxvdykgaWYgVFVSTiBpcyBnb2lu
ZyB0byBiZSB1c2VkDQo+ID4gd2hlcmUgbmVlZGVkIGFuZCB3ZSBjYW5ub3Qgd2FpdCBmb3IgYW55
IGFkZGl0aW9uYWwgZHJhZnQuDQo+ID4NCj4gPiBTZWVtcyBsaWtlIGl0IGlzIHN1ZmZpY2llbnQg
dG8gZXh0ZW50IHRoaXMgdGFibGUgKGZvdW5kIGluIGRyYWZ0IDE0KQ0KPiA+IHdpdGggMyBuZXcg
dmFsdWVzIChhcyBzaG93bik6DQo+ID4NCj4gPiAxNi4gIFNUVU4gQXR0cmlidXRlcw0KPiA+DQo+
ID4gICBUaGlzIFNUVU4gZXh0ZW5zaW9uIGRlZmluZXMgdGhlIGZvbGxvd2luZyBhdHRyaWJ1dGVz
Og0KPiA+DQo+ID4gICAgIDB4MDAwQzogQ0hBTk5FTC1OVU1CRVINCj4gPiAgICAgMHgwMDBEOiBM
SUZFVElNRQ0KPiA+ICAgICAweDAwMTA6IFJlc2VydmVkICh3YXMgQkFORFdJRFRIKQ0KPiA+ICAg
ICAweDAwMTI6IFhPUi1QRUVSLUFERFJFU1MNCj4gPiAgICAgMHgwMDEzOiBEQVRBDQo+ID4gICAg
IDB4MDAxNjogWE9SLVJFTEFZRUQtQUREUkVTUw0KPiA+ICAgICAweDAwMTc6IFJFUVVFU1RFRC1B
RERSRVNTLUZBTUlMWQ0KPiA+ICAgICAweDAwMTg6IEVWRU4tUE9SVA0KPiA+ICAgICAweDAwMTk6
IFJFUVVFU1RFRC1UUkFOU1BPUlQNCj4gPiAgICAgMHgwMDFBOiBET05ULUZSQUdNRU5UDQo+ID4g
ICAgIDB4MDAyMTogUmVzZXJ2ZWQgKHdhcyBUSU1FUi1WQUwpDQo+ID4gICAgIDB4MDAyMjogUkVT
RVJWQVRJT04tVE9LRU4NCj4gPiAgICAgVEJELUNBOiBBRERJVElPTkFMLUFERFJFU1MtRkFNSUxZ
DQo+ID4gQURESVRJT05BTC1BRERSRVNTLUFMTA0KPiA+IEFERElUSU9OQUwtQUREUkVTUy1BTExW
NA0KPiA+IEFERElUSU9OQUwtQUREUkVTUy1BTExWNg0KPiA+ICAgICBUQkQtQ0E6IEFERFJFU1Mt
RVJST1ItQ09ERQ0KPiA+ICAgICBUQkQtQ0E6IElDTVANCj4gPg0KPiA+IEFjdHVhbGx5LCBicm93
c2luZyB0aHJvdWdoIHRoZSBkcmFmdCBmb3IgQURESVRJT05BTC1BRERSRVNTLUZBTUlMWSwNCj4g
PiB2ZXJ5IGxpdHRsZSB0ZXh0IHNlZW1zIHRvIGJlIGFkZGVkIGZvciBnZW5lcmFsaXphdGlvbiB0
byAgQURESVRJT05BTC0NCj4gQUREUkVTUy14eHguDQo+ID4gQWxtb3N0IGV2ZXJ5dGhpbmcgYXBw
bGllcyB0byBBRERJVElPTkFMLUFERFJFU1MteHh4IGFuZCBjYW4gYmUgcmV1c2VkLg0KPiA+DQo+
ID4gQURESVRJT05BTC1BRERSRVNTLUFMTCBzaG91bGQgYmUgdGhlIGRlZmF1bHQgZm9yIGFueSBt
b2Rlcm4gVFVSTiBjbGllbnQuDQo+ID4NCj4gPiBDaGVjayEgLSBXZSBuZWVkIHRoaXMgbm93Lg0K
PiA+DQo+ID4gVGhhbmtzLA0KPiA+IEthcmwNCj4gPg0KPiA+PiAtLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQ0KPiA+PiBGcm9tOiBLYXJsIFN0YWhsIFttYWlsdG86a2FybC5zdGFobEBpbmdhdGUu
Y29tXQ0KPiA+PiBTZW50OiBTdW5kYXksIE1hcmNoIDQsIDIwMTggMTA6MzYgUE0NCj4gPj4gVG86
ICdNYXJjIFBldGl0LUh1Z3VlbmluJyA8cGV0aXRodWdAYWNtLm9yZz47IEtvbmRhLCBUaXJ1bWFs
ZXN3YXINCj4gPj4gUmVkZHkgPFRpcnVtYWxlc3dhclJlZGR5X0tvbmRhQE1jQWZlZS5jb20+OyB0
cmFtQGlldGYub3JnDQo+ID4+IFN1YmplY3Q6IFNWOiBbdHJhbV0gUmV2aWV3IG9mIGR1YWwgYWxs
b2NhdGlvbiBpbiBUVVJOYmlzLTExDQo+ID4+DQo+ID4+IEhpLA0KPiA+Pg0KPiA+PiBXaGVuIHdl
IG5vdyBoYXZlICJkdWFsIGFsbG9jYXRpb24iIGludG8gdGhpcyBkcmFmdCAoSSBzZWUgb24gcGFn
ZSAyNjoNCj4gPj4gIklmDQo+ID4gdGhlDQo+ID4+IGNsaWVudCB3aXNoZXMgdG8gb2J0YWluIG9u
ZSBJUHY2IGFuZCBvbmUgSVB2NCByZWxheWVkIHRyYW5zcG9ydA0KPiA+PiBhZGRyZXNzDQo+ID4g
dGhlbg0KPiA+PiBpdCBpbmNsdWRlcyBhbiBBRERJVElPTkFMLUFERFJFU1MtRkFNSUxZIHRyYW5z
cG9ydCBhZGRyZXNzIHRoZW4gaXQiKQ0KPiA+PiBjYW4gd2Ugbm90IGdlbmVyYWxpemUgdGhhdCBm
dXJ0aGVyIGFuZCBhbGxvdyBNT1JFIFRIQU4gT05FIHJlbGF5ZWQNCj4gPj4gdHJhbnNwb3J0IGFk
ZHJlc3MgKG9mIGFueSBmYW1pbHkpIGluIHJlc3BvbnNlIHRvIGFuIGFsbG9jYXRpb24/DQo+ID4+
DQo+ID4+IEkgbWVhbiB0aGF0IGEgVFVSTiBzZXJ2ZXIgY291bGQgaGF2ZSBzZXZlcmFsIHJlbGF5
IGludGVyZmFjZXMgYXQNCj4gPj4gZGlmZmVyZW50DQo+ID4gSVAtDQo+ID4+IGFkZHJlc3NlcyBp
bnRvIGRpZmZlcmVudCBuZXR3b3JrcyAtIG5vdCBqdXN0IHRoZSBJbnRlcm5ldCwgYnV0IGFsc28g
YQ0KPiA+PiBWb0lQIChoaWdoZXIgcXVhbGl0eSkgbmV0d29yayBlLmcuIGJ5IHNvbWUgdHJpcGxl
IHBsYXkgc2VydmljZQ0KPiA+PiBwcm92aWRlciwgYW4gSU1TIG5ldHdvcmsgb3Igc29tZSBicmFu
Y2ggb2ZmaWNlIG5ldHdvcmsuDQo+ID4+DQo+ID4+IEkgdGhpbmsgdGhpcyBpcyBzcGVjaWZpY2Fs
bHkgaW1wb3J0YW50IGZvciBuZXR3b3JrIHByb3ZpZGVkL2F1dG8NCj4gPiBkaXNjb3ZlcmVkDQo+
ID4+IHR1cm4gc2VydmVycyAoYXBwbGljYXRpb24gcHJvdmlkZWQgdHVybiBzZXJ2ZXJzIGNvdWxk
IGluc3RlYWQganVzdA0KPiA+PiBsaXN0DQo+ID4gc2V2ZXJhbA0KPiA+PiB0dXJuIHNlcnZlcnMp
Lg0KPiA+Pg0KPiA+PiBJIHNhdyBzb21lb25lIHNuaXBwZWQgdGhpcyBhYm91dCAiU0lOR0xFIHJl
bGF5ZWQgdHJhbnNwb3J0IGFkZHJlc3MNCj4gPj4gcGVyIGFsbG9jYXRpb24gcmVxdWVzdCINCj4g
Pj4+PiBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNjE1NiNzZWN0aW9uLTMNCj4gPj4+
PiA8c25pcD4NCj4gPj4+Pg0KPiA+Pj4+ICAgVFVSTiBzZXJ2ZXJzIGFsbG9jYXRlIGEgc2luZ2xl
IHJlbGF5ZWQgdHJhbnNwb3J0IGFkZHJlc3MgcGVyDQo+ID4+Pj4gICBhbGxvY2F0aW9uIHJlcXVl
c3QuICBUaGVyZWZvcmUsIEFsbG9jYXRlIHJlcXVlc3RzIGNhbm5vdCBjYXJyeSBtb3JlDQo+ID4+
Pj4gICB0aGFuIG9uZSBSRVFVRVNURUQtQUREUkVTUy1GQU1JTFkgYXR0cmlidXRlLiAgQ29uc2Vx
dWVudGx5LCBhDQo+ID4+IGNsaWVudA0KPiA+Pj4+ICAgdGhhdCB3aXNoZXMgdG8gYWxsb2NhdGUg
bW9yZSB0aGFuIG9uZSByZWxheWVkIHRyYW5zcG9ydCBhZGRyZXNzDQo+ID4+Pj4gYXQNCj4gPiBh
DQo+ID4+Pj4gICBUVVJOIHNlcnZlciAoZS5nLiwgYW4gSVB2NCBhbmQgYW4gSVB2NiBhZGRyZXNz
KSBuZWVkcyB0byBwZXJmb3JtDQo+ID4+Pj4gICBzZXZlcmFsIGFsbG9jYXRpb24gcmVxdWVzdHMg
KG9uZSBhbGxvY2F0aW9uIHJlcXVlc3QgcGVyIHJlbGF5ZWQNCj4gPj4+PiAgIHRyYW5zcG9ydCBh
ZGRyZXNzKS4NCj4gPj4+PiA8L3NuaXA+DQo+ID4+DQo+ID4+IGJ1dCBpZiB0aGF0IGlzIHJlbWVk
aWVkIG5vdywgaXQgc2VlbXMgbGlrZSBhIHNtYWxsIHN0ZXAgdG8gZ2VuZXJhbGl6ZQ0KPiA+PiBz
bw0KPiA+IHdlIGNhbg0KPiA+PiBnZXQgbXVsdGlwbGUgcmVsYXllZCB0cmFuc3BvcnQgYWRkcmVz
c2VzIGZyb20gb25lIGFsbG9jYXRlIHJlcXVlc3Q/DQo+ID4+DQo+ID4+IC9LYXJsDQo+ID4NCj4g
Pg0KPiA+IC0tLS0tVXJzcHJ1bmdsaWd0IG1lZGRlbGFuZGUtLS0tLQ0KPiA+IEZyw6VuOiB0cmFt
IFttYWlsdG86dHJhbS1ib3VuY2VzQGlldGYub3JnXSBGw7ZyIEtvbmRhLCBUaXJ1bWFsZXN3YXIN
Cj4gPiBSZWRkeQ0KPiA+IFNraWNrYXQ6IGRlbiAxOCBtYXJzIDIwMTggMDk6NTENCj4gPiBUaWxs
OiB0cmFtQGlldGYub3JnDQo+ID4gw4RtbmU6IFJlOiBbdHJhbV0gSS1EIEFjdGlvbjogZHJhZnQt
aWV0Zi10cmFtLXR1cm5iaXMtMTUudHh0DQo+ID4NCj4gPiBUaGlzIHJldmlzaW9uIGFkZHJlc3Nl
cyBjb21tZW50cyBmcm9tIE1hcmssIEthcmwgYW5kIE5vcml5dWtpIFRvcmlpLg0KPiA+DQo+ID4g
LVRpcnUNCj4gPg0KPiA+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+PiBGcm9tOiB0
cmFtIFttYWlsdG86dHJhbS1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgaW50ZXJuZXQt
DQo+ID4+IGRyYWZ0c0BpZXRmLm9yZw0KPiA+PiBTZW50OiBTdW5kYXksIE1hcmNoIDE4LCAyMDE4
IDg6NDMgQU0NCj4gPj4gVG86IGktZC1hbm5vdW5jZUBpZXRmLm9yZw0KPiA+PiBDYzogdHJhbUBp
ZXRmLm9yZw0KPiA+PiBTdWJqZWN0OiBbdHJhbV0gSS1EIEFjdGlvbjogZHJhZnQtaWV0Zi10cmFt
LXR1cm5iaXMtMTUudHh0DQo+ID4+DQo+ID4+DQo+ID4+IEEgTmV3IEludGVybmV0LURyYWZ0IGlz
IGF2YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIEludGVybmV0LURyYWZ0cw0KPiA+IGRpcmVjdG9y
aWVzLg0KPiA+PiBUaGlzIGRyYWZ0IGlzIGEgd29yayBpdGVtIG9mIHRoZSBUVVJOIFJldmlzZWQg
YW5kIE1vZGVybml6ZWQgV0cgb2YNCj4gPj4gdGhlIElFVEYuDQo+ID4+DQo+ID4+ICAgICAgICBU
aXRsZSAgICAgICAgICAgOiBUcmF2ZXJzYWwgVXNpbmcgUmVsYXlzIGFyb3VuZCBOQVQgKFRVUk4p
OiBSZWxheQ0KPiA+IEV4dGVuc2lvbnMNCj4gPj4gdG8gU2Vzc2lvbiBUcmF2ZXJzYWwgVXRpbGl0
aWVzIGZvciBOQVQgKFNUVU4pDQo+ID4+ICAgICAgICBBdXRob3JzICAgICAgICAgOiBUaXJ1bWFs
ZXN3YXIgUmVkZHkNCj4gPj4gICAgICAgICAgICAgICAgICAgICAgICAgIEFsYW4gSm9obnN0b24N
Cj4gPj4gICAgICAgICAgICAgICAgICAgICAgICAgIFBoaWxpcCBNYXR0aGV3cw0KPiA+PiAgICAg
ICAgICAgICAgICAgICAgICAgICAgSm9uYXRoYW4gUm9zZW5iZXJnDQo+ID4+IAlGaWxlbmFtZSAg
ICAgICAgOiBkcmFmdC1pZXRmLXRyYW0tdHVybmJpcy0xNS50eHQNCj4gPj4gCVBhZ2VzICAgICAg
ICAgICA6IDg0DQo+ID4+IAlEYXRlICAgICAgICAgICAgOiAyMDE4LTAzLTE4DQo+ID4+DQo+ID4+
IEFic3RyYWN0Og0KPiA+PiAgIElmIGEgaG9zdCBpcyBsb2NhdGVkIGJlaGluZCBhIE5BVCwgdGhl
biBpbiBjZXJ0YWluIHNpdHVhdGlvbnMgaXQgY2FuDQo+ID4+ICAgYmUgaW1wb3NzaWJsZSBmb3Ig
dGhhdCBob3N0IHRvIGNvbW11bmljYXRlIGRpcmVjdGx5IHdpdGggb3RoZXIgaG9zdHMNCj4gPj4g
ICAocGVlcnMpLiAgSW4gdGhlc2Ugc2l0dWF0aW9ucywgaXQgaXMgbmVjZXNzYXJ5IGZvciB0aGUg
aG9zdCB0byB1c2UNCj4gPj4gICB0aGUgc2VydmljZXMgb2YgYW4gaW50ZXJtZWRpYXRlIG5vZGUg
dGhhdCBhY3RzIGFzIGEgY29tbXVuaWNhdGlvbg0KPiA+PiAgIHJlbGF5LiAgVGhpcyBzcGVjaWZp
Y2F0aW9uIGRlZmluZXMgYSBwcm90b2NvbCwgY2FsbGVkIFRVUk4gKFRyYXZlcnNhbA0KPiA+PiAg
IFVzaW5nIFJlbGF5cyBhcm91bmQgTkFUKSwgdGhhdCBhbGxvd3MgdGhlIGhvc3QgdG8gY29udHJv
bCB0aGUNCj4gPj4gICBvcGVyYXRpb24gb2YgdGhlIHJlbGF5IGFuZCB0byBleGNoYW5nZSBwYWNr
ZXRzIHdpdGggaXRzIHBlZXJzIHVzaW5nDQo+ID4+ICAgdGhlIHJlbGF5LiAgVFVSTiBkaWZmZXJz
IGZyb20gc29tZSBvdGhlciByZWxheSBjb250cm9sIHByb3RvY29scyBpbg0KPiA+PiAgIHRoYXQg
aXQgYWxsb3dzIGEgY2xpZW50IHRvIGNvbW11bmljYXRlIHdpdGggbXVsdGlwbGUgcGVlcnMgdXNp
bmcgYQ0KPiA+PiAgIHNpbmdsZSByZWxheSBhZGRyZXNzLg0KPiA+Pg0KPiA+PiAgIFRoZSBUVVJO
IHByb3RvY29sIHdhcyBkZXNpZ25lZCB0byBiZSB1c2VkIGFzIHBhcnQgb2YgdGhlIElDRQ0KPiA+
PiAgIChJbnRlcmFjdGl2ZSBDb25uZWN0aXZpdHkgRXN0YWJsaXNobWVudCkgYXBwcm9hY2ggdG8g
TkFUIHRyYXZlcnNhbCwNCj4gPj4gICB0aG91Z2ggaXQgYWxzbyBjYW4gYmUgdXNlZCB3aXRob3V0
IElDRS4NCj4gPj4NCj4gPj4gICBUaGlzIGRvY3VtZW50IG9ic29sZXRlcyBSRkMgNTc2NiBhbmQg
UkZDIDYxNTYuDQo+ID4+DQo+ID4+DQo+ID4+IFRoZSBJRVRGIGRhdGF0cmFja2VyIHN0YXR1cyBw
YWdlIGZvciB0aGlzIGRyYWZ0IGlzOg0KPiA+PiBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3Jn
L2RvYy9kcmFmdC1pZXRmLXRyYW0tdHVybmJpcy8NCj4gPj4NCj4gPj4gVGhlcmUgYXJlIGFsc28g
aHRtbGl6ZWQgdmVyc2lvbnMgYXZhaWxhYmxlIGF0Og0KPiA+PiBodHRwczovL3Rvb2xzLmlldGYu
b3JnL2h0bWwvZHJhZnQtaWV0Zi10cmFtLXR1cm5iaXMtMTUNCj4gPj4gaHR0cHM6Ly9kYXRhdHJh
Y2tlci5pZXRmLm9yZy9kb2MvaHRtbC9kcmFmdC1pZXRmLXRyYW0tdHVybmJpcy0xNQ0KPiA+Pg0K
PiA+PiBBIGRpZmYgZnJvbSB0aGUgcHJldmlvdXMgdmVyc2lvbiBpcyBhdmFpbGFibGUgYXQ6DQo+
ID4+IGh0dHBzOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1pZXRmLXRyYW0tdHVy
bmJpcy0xNQ0KPiA+Pg0KPiA+Pg0KPiA+PiBQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEg
Y291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZg0KPiA+IHN1Ym1pc3Npb24NCj4gPj4g
dW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29s
cy5pZXRmLm9yZy4NCj4gPj4NCj4gPj4gSW50ZXJuZXQtRHJhZnRzIGFyZSBhbHNvIGF2YWlsYWJs
ZSBieSBhbm9ueW1vdXMgRlRQIGF0Og0KPiA+PiBmdHA6Ly9mdHAuaWV0Zi5vcmcvaW50ZXJuZXQt
ZHJhZnRzLw0KPiA+Pg0KPiA+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KPiA+PiB0cmFtIG1haWxpbmcgbGlzdA0KPiA+PiB0cmFtQGlldGYub3JnDQo+
ID4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdHJhbQ0KPiA+DQo+ID4g
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPiB0cmFt
IG1haWxpbmcgbGlzdA0KPiA+IHRyYW1AaWV0Zi5vcmcNCj4gPiBodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL3RyYW0NCj4gPg0KDQo=


From nobody Wed Mar 21 10:06:25 2018
Return-Path: <brandon.williams@akamai.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08AF61270AB for <tram@ietfa.amsl.com>; Wed, 21 Mar 2018 10:06:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qLIUOImArAOl for <tram@ietfa.amsl.com>; Wed, 21 Mar 2018 10:06:21 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2ACA7126CC7 for <tram@ietf.org>; Wed, 21 Mar 2018 10:06:20 -0700 (PDT)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.22/8.16.0.22) with SMTP id w2LH5eD9025956; Wed, 21 Mar 2018 17:06:08 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=subject : to : cc : references : from : message-id : date : mime-version : in-reply-to : content-type : content-transfer-encoding; s=jan2016.eng; bh=nBP9QMgUxuuWbE/20nxFl319TwoaC/LzwZ8lC2baHW0=; b=b9uWwfoxEOzeVxXavhlFN0u4tUT9NT4ScNKd5VBiIbZvKhJILhAcB1fFoWPegVvI9y74 UtxmIHMwfUhxV81nsn3SMXVaIO25VkRMV9w0ajGjZe2VJ2l7zchphEA6Tz+4Yf1WrCNS P9Nui9IjmwyhDx/+KTBATHeB+3y60LfZTa6Kjhhphq37U7GndgBTkB6R4YA7ZadomyAZ IY2/Xb13UncTXbQYqrRLOB6bTSW/u4TpOZ3vkJdG3hT8QcPsC51H9ZUjLHytHrKqKlSD 4HVBkowsJJ1Znn3sEw3/ASKPN13e+LsPK8R0KqUFlesOwdFQ/qyMCSE/QBAo75Ryy5mC xw== 
Received: from prod-mail-ppoint4 ([96.6.114.87]) by m0050102.ppops.net-00190b01. with ESMTP id 2gue7t1s1s-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 21 Mar 2018 17:06:07 +0000
Received: from pps.filterd (prod-mail-ppoint4.akamai.com [127.0.0.1]) by prod-mail-ppoint4.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w2LH2Ngj012181; Wed, 21 Mar 2018 13:06:06 -0400
Received: from prod-mail-relay14.akamai.com ([172.27.17.39]) by prod-mail-ppoint4.akamai.com with ESMTP id 2grxbvvcsd-1; Wed, 21 Mar 2018 13:06:05 -0400
Received: from [172.28.118.62] (bowill.kendall.corp.akamai.com [172.28.118.62]) by prod-mail-relay14.akamai.com (Postfix) with ESMTP id D170083A06; Wed, 21 Mar 2018 17:06:04 +0000 (GMT)
To: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>, "Olle E. Johansson" <oej@edvina.net>, Karl Stahl <karl.stahl@ingate.com>
Cc: "tram@ietf.org" <tram@ietf.org>
References: <152136260256.18150.10551009018364033510@ietfa.amsl.com> <BN6PR16MB1425D61744AC7480972C800AEAD50@BN6PR16MB1425.namprd16.prod.outlook.com> <031e01d3c085$5f581db0$1e085910$@stahl@ingate.com> <BEC020EA-C973-48E5-A918-EF2D25953E33@edvina.net> <BN6PR16MB1425327E5CD094CF18A040F2EAAA0@BN6PR16MB1425.namprd16.prod.outlook.com>
From: Brandon Williams <brandon.williams@akamai.com>
Message-ID: <c3584946-2782-2ac7-7f7c-7e7ae273fec9@akamai.com>
Date: Wed, 21 Mar 2018 13:05:57 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <BN6PR16MB1425327E5CD094CF18A040F2EAAA0@BN6PR16MB1425.namprd16.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-21_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803210196
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-21_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803210196
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/H3r8jqmLqVX52lHXggyR3kYsmlo>
Subject: Re: [tram] Multiple allocations SV: I-D Action: draft-ietf-tram-turnbis-15.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2018 17:06:24 -0000

+1

When Tiru indicated that he had covered Karl's comments, I believe that 
he meant the other comments that were not asking to increase the scope 
of the document.

I think there will be enough work in this area to define the rationale 
and protocol changes that it would be an equivalent level of effort to 
change turnbis at this point vs just working it with a new draft. For 
that reason, I prefer covering the gap with a new draft.

If this does go in to turnbis, we'll need WG consensus to expand scope.

Chairs, Any suggestions on approach?

On 03/21/2018 11:23 AM, Konda, Tirumaleswar Reddy wrote:
>> -----Original Message-----
>> From: Olle E. Johansson [mailto:oej@edvina.net]
>> Sent: Tuesday, March 20, 2018 8:35 PM
>> To: Karl Stahl <karl.stahl@ingate.com>
>> Cc: Olle E Johansson <oej@edvina.net>; Konda, Tirumaleswar Reddy
>> <TirumaleswarReddy_Konda@McAfee.com>; tram@ietf.org
>> Subject: Re: Multiple allocations SV: [tram] I-D Action: draft-ietf-tram-turnbis-
>> 15.txt
>>
>>
>>> On 20 Mar 2018, at 20:55, Karl Stahl <karl.stahl@ingate.com> wrote:
>>>
>>>> This revision addresses comments from Mark, Karl and Noriyuki Torii.
>>> My comment about need for multiple allocations is NOT addressed.
>>>
>>> Let me explain more clearly why multiple allocations is needed:
>>>
>>> ICE is about finding all/many paths for the media, e.g. with the help
>>> of TURN servers.
>>> Those paths are not over ONE IPv4 network, over ONE IPv6 network or
>>> EXACTLY ONE OF EACH.
>>> If fact, it is more common that you have several IPv4 networks paths.
>>>
>>> Now that we have network provided TURN servers, you only ask for
>>> Allocation once (contrary to application provided TURN servers, where
>>> you can be directed to Allocate several times.) and thus we need all
>>> relay addresses in one allocation request.
>>
>> I agree with Karl here, for network-provided turn servers (which is not defined in
>> the terminology section here on in 8155) I think there are use cases for multiple
>> addresses in multiple families.
> 
> The WG has only agreed on dual allocation, this is a new requirement for a specific deployment scenario.
> You may want to submit a new draft (just like we did for RFC8155).
> 
> -Tiru
> 
>>
>> I also understand that this will make the draft more complex. Consider the case
>> where a turn server have two IPv4 networks and one IPv6 and have run out of
>> possible allocations on one IPv4 network - should it send whatâ€™s available or
>> send an error message and fail completely?
>>
>> Regardless, this is a good time to fix this.
>>
>> /O
>>
>>
>>>
>>> Wasn't that the reason dual allocation was requested? The need for
>>> multiple allocation is stronger!
>>>
>>> Please address this, e.g. like below (seems you are almost there).
>>>
>>> /Karl
>>>
>>>
>>> ******************* Previous *******************
>>>
>>> Allowing a turn allocation to return multiple relayed transport
>>> addresses, beyond ONE IPv4 and ONE IPv6 (which may sit on the same or
>>> on different interfaces/network segments), seems like very small step
>>> now when the dual allocation was put in place in this draft. We
>>> certainly need it (some reasons below) if TURN is going to be used
>>> where needed and we cannot wait for any additional draft.
>>>
>>> Seems like it is sufficient to extent this table (found in draft 14)
>>> with 3 new values (as shown):
>>>
>>> 16.  STUN Attributes
>>>
>>>    This STUN extension defines the following attributes:
>>>
>>>      0x000C: CHANNEL-NUMBER
>>>      0x000D: LIFETIME
>>>      0x0010: Reserved (was BANDWIDTH)
>>>      0x0012: XOR-PEER-ADDRESS
>>>      0x0013: DATA
>>>      0x0016: XOR-RELAYED-ADDRESS
>>>      0x0017: REQUESTED-ADDRESS-FAMILY
>>>      0x0018: EVEN-PORT
>>>      0x0019: REQUESTED-TRANSPORT
>>>      0x001A: DONT-FRAGMENT
>>>      0x0021: Reserved (was TIMER-VAL)
>>>      0x0022: RESERVATION-TOKEN
>>>      TBD-CA: ADDITIONAL-ADDRESS-FAMILY
>>> ADDITIONAL-ADDRESS-ALL
>>> ADDITIONAL-ADDRESS-ALLV4
>>> ADDITIONAL-ADDRESS-ALLV6
>>>      TBD-CA: ADDRESS-ERROR-CODE
>>>      TBD-CA: ICMP
>>>
>>> Actually, browsing through the draft for ADDITIONAL-ADDRESS-FAMILY,
>>> very little text seems to be added for generalization to  ADDITIONAL-
>> ADDRESS-xxx.
>>> Almost everything applies to ADDITIONAL-ADDRESS-xxx and can be reused.
>>>
>>> ADDITIONAL-ADDRESS-ALL should be the default for any modern TURN client.
>>>
>>> Check! - We need this now.
>>>
>>> Thanks,
>>> Karl
>>>
>>>> -----Original Message-----
>>>> From: Karl Stahl [mailto:karl.stahl@ingate.com]
>>>> Sent: Sunday, March 4, 2018 10:36 PM
>>>> To: 'Marc Petit-Huguenin' <petithug@acm.org>; Konda, Tirumaleswar
>>>> Reddy <TirumaleswarReddy_Konda@McAfee.com>; tram@ietf.org
>>>> Subject: SV: [tram] Review of dual allocation in TURNbis-11
>>>>
>>>> Hi,
>>>>
>>>> When we now have "dual allocation" into this draft (I see on page 26:
>>>> "If
>>> the
>>>> client wishes to obtain one IPv6 and one IPv4 relayed transport
>>>> address
>>> then
>>>> it includes an ADDITIONAL-ADDRESS-FAMILY transport address then it")
>>>> can we not generalize that further and allow MORE THAN ONE relayed
>>>> transport address (of any family) in response to an allocation?
>>>>
>>>> I mean that a TURN server could have several relay interfaces at
>>>> different
>>> IP-
>>>> addresses into different networks - not just the Internet, but also a
>>>> VoIP (higher quality) network e.g. by some triple play service
>>>> provider, an IMS network or some branch office network.
>>>>
>>>> I think this is specifically important for network provided/auto
>>> discovered
>>>> turn servers (application provided turn servers could instead just
>>>> list
>>> several
>>>> turn servers).
>>>>
>>>> I saw someone snipped this about "SINGLE relayed transport address
>>>> per allocation request"
>>>>>> https://tools.ietf.org/html/rfc6156#section-3
>>>>>> <snip>
>>>>>>
>>>>>>    TURN servers allocate a single relayed transport address per
>>>>>>    allocation request.  Therefore, Allocate requests cannot carry more
>>>>>>    than one REQUESTED-ADDRESS-FAMILY attribute.  Consequently, a
>>>> client
>>>>>>    that wishes to allocate more than one relayed transport address
>>>>>> at
>>> a
>>>>>>    TURN server (e.g., an IPv4 and an IPv6 address) needs to perform
>>>>>>    several allocation requests (one allocation request per relayed
>>>>>>    transport address).
>>>>>> </snip>
>>>>
>>>> but if that is remedied now, it seems like a small step to generalize
>>>> so
>>> we can
>>>> get multiple relayed transport addresses from one allocate request?
>>>>
>>>> /Karl
>>>
>>>
>>> -----Ursprungligt meddelande-----
>>> FrÃ¥n: tram [mailto:tram-bounces@ietf.org] FÃ¶r Konda, Tirumaleswar
>>> Reddy
>>> Skickat: den 18 mars 2018 09:51
>>> Till: tram@ietf.org
>>> Ã„mne: Re: [tram] I-D Action: draft-ietf-tram-turnbis-15.txt
>>>
>>> This revision addresses comments from Mark, Karl and Noriyuki Torii.
>>>
>>> -Tiru
>>>
>>>> -----Original Message-----
>>>> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of internet-
>>>> drafts@ietf.org
>>>> Sent: Sunday, March 18, 2018 8:43 AM
>>>> To: i-d-announce@ietf.org
>>>> Cc: tram@ietf.org
>>>> Subject: [tram] I-D Action: draft-ietf-tram-turnbis-15.txt
>>>>
>>>>
>>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>> directories.
>>>> This draft is a work item of the TURN Revised and Modernized WG of
>>>> the IETF.
>>>>
>>>>         Title           : Traversal Using Relays around NAT (TURN): Relay
>>> Extensions
>>>> to Session Traversal Utilities for NAT (STUN)
>>>>         Authors         : Tirumaleswar Reddy
>>>>                           Alan Johnston
>>>>                           Philip Matthews
>>>>                           Jonathan Rosenberg
>>>> 	Filename        : draft-ietf-tram-turnbis-15.txt
>>>> 	Pages           : 84
>>>> 	Date            : 2018-03-18
>>>>
>>>> Abstract:
>>>>    If a host is located behind a NAT, then in certain situations it can
>>>>    be impossible for that host to communicate directly with other hosts
>>>>    (peers).  In these situations, it is necessary for the host to use
>>>>    the services of an intermediate node that acts as a communication
>>>>    relay.  This specification defines a protocol, called TURN (Traversal
>>>>    Using Relays around NAT), that allows the host to control the
>>>>    operation of the relay and to exchange packets with its peers using
>>>>    the relay.  TURN differs from some other relay control protocols in
>>>>    that it allows a client to communicate with multiple peers using a
>>>>    single relay address.
>>>>
>>>>    The TURN protocol was designed to be used as part of the ICE
>>>>    (Interactive Connectivity Establishment) approach to NAT traversal,
>>>>    though it also can be used without ICE.
>>>>
>>>>    This document obsoletes RFC 5766 and RFC 6156.
>>>>
>>>>
>>>> The IETF datatracker status page for this draft is:
>>>> https://datatracker.ietf.org/doc/draft-ietf-tram-turnbis/
>>>>
>>>> There are also htmlized versions available at:
>>>> https://tools.ietf.org/html/draft-ietf-tram-turnbis-15
>>>> https://datatracker.ietf.org/doc/html/draft-ietf-tram-turnbis-15
>>>>
>>>> A diff from the previous version is available at:
>>>> https://www.ietf.org/rfcdiff?url2=draft-ietf-tram-turnbis-15
>>>>
>>>>
>>>> Please note that it may take a couple of minutes from the time of
>>> submission
>>>> until the htmlized version and diff are available at tools.ietf.org.
>>>>
>>>> Internet-Drafts are also available by anonymous FTP at:
>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>
>>>> _______________________________________________
>>>> tram mailing list
>>>> tram@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/tram
>>>
>>> _______________________________________________
>>> tram mailing list
>>> tram@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tram
>>>
> 
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram
> 


From nobody Wed Mar 21 10:13:41 2018
Return-Path: <sperreault@jive.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4D4812E043 for <tram@ietfa.amsl.com>; Wed, 21 Mar 2018 10:13:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=jive.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d5Obzl8j_FRN for <tram@ietfa.amsl.com>; Wed, 21 Mar 2018 10:13:38 -0700 (PDT)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71ADB127137 for <tram@ietf.org>; Wed, 21 Mar 2018 10:13:38 -0700 (PDT)
Received: by mail-oi0-x22a.google.com with SMTP id 23-v6so4941422oir.11 for <tram@ietf.org>; Wed, 21 Mar 2018 10:13:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jive.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0yXFC0Cnj+IUFfDZBJy2GhAGsVgBPuAo9xune0Wc5mk=; b=Sj672clPMFdj1wMmRCXV1Tbpfo2RMmZvYYjkdy7nQ5uVNiHlG7hBgRCLbFrx/u+xka RxtWZGluYdLzh5EpXmbOrzUFo/JCm1XFFvKN9f1lTbBsjY5OL1/RUvbN/xYqF+tRD/q3 e9oeXm+yGg8rAenpQEgAiXZhVLH6XBKi5FMUn0ysmAAGk4lAdZdgxWosH1mMn147plEi 83E4q3TaEGsJElzNdmIUlXNVSg50cVRwjC89qfZ4THKY0uP5VxZfFxh84LPKSMB7kXxS sXuWLpVjq4L5+cgpf84k1rsQ+Fl0UbAv0lbl7v60J/VCF703kNW57EUoj9z3tpOgUoCr ScRA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=0yXFC0Cnj+IUFfDZBJy2GhAGsVgBPuAo9xune0Wc5mk=; b=TbFb6ZGHi0nK3qjEjsdFFi7FBrzpI9i71EzkWX2tvesTqYYTi05G4TEcyviQ7jGncU kZov1yHxhxexPLLG94ErfO3YtkDjtiKTsQhTh9TWtFhJpW5FzVbRg8CIAfAr7+mBYBhY gHR11ZDcsROaSu4UNdDBYrdak2MTLPwzMr3aaCMiosreAheEPP07ttUgCOvrXkhkMp8W PEMo2m0hMiYcw1D/Uc077wbouWvkGHiND+qf2friGcrn18BqycThaMdiTE66xixZFnhy Pz7WnT6Z+Vl5BLAeicgnvTvhUIIVdC3krAfMI+JFuyMskqOfWA8yJtv6OcKVOizun0Xc ZA/w==
X-Gm-Message-State: AElRT7Emk5t1hw/O73RpCQ8hJjSAZ7dsZZ4fZeFEmyEpqM/eTNazAyNp Wd2MGDfDlDQVaqrbyGJeRvuF9ycZXd9yMjGuzPoc5Q==
X-Google-Smtp-Source: AG47ELv3Wn8pIwUHZ+BWTZZyj9vEvDUxDtigc+PjRTUUwpgLK3o7ydiQSsiQpQQ1B4GxQ3BvM3t+bbXJEn2kMKecOyg=
X-Received: by 10.202.188.6 with SMTP id m6mr4134793oif.313.1521652417549; Wed, 21 Mar 2018 10:13:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.203.132 with HTTP; Wed, 21 Mar 2018 10:13:16 -0700 (PDT)
In-Reply-To: <c3584946-2782-2ac7-7f7c-7e7ae273fec9@akamai.com>
References: <152136260256.18150.10551009018364033510@ietfa.amsl.com> <BN6PR16MB1425D61744AC7480972C800AEAD50@BN6PR16MB1425.namprd16.prod.outlook.com> <BEC020EA-C973-48E5-A918-EF2D25953E33@edvina.net> <BN6PR16MB1425327E5CD094CF18A040F2EAAA0@BN6PR16MB1425.namprd16.prod.outlook.com> <c3584946-2782-2ac7-7f7c-7e7ae273fec9@akamai.com>
From: Simon Perreault <sperreault@jive.com>
Date: Wed, 21 Mar 2018 13:13:16 -0400
Message-ID: <CANO7kWC5H_0jv-=MsRzQaO7C=SsTbqz-UJhARm2f1SWOA6uutA@mail.gmail.com>
To: Brandon Williams <brandon.williams@akamai.com>
Cc: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@mcafee.com>,  "Olle E. Johansson" <oej@edvina.net>, Karl Stahl <karl.stahl@ingate.com>, "tram@ietf.org" <tram@ietf.org>
Content-Type: multipart/alternative; boundary="001a113dd406d255690567ef4ff2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/zwNXoEy6wQzK0AHWRjdD02H3vuM>
Subject: Re: [tram] Multiple allocations SV: I-D Action: draft-ietf-tram-turnbis-15.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2018 17:13:40 -0000

--001a113dd406d255690567ef4ff2
Content-Type: text/plain; charset="UTF-8"

2018-03-21 17:05 GMT+00:00 Brandon Williams <brandon.williams@akamai.com>:
>
> Chairs, Any suggestions on approach?


The proposal on the table is for Karl+Olle to write their idea into a new
draft.

Karl+Olle, can you guys live with that?

Simon

--001a113dd406d255690567ef4ff2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">2018=
-03-21 17:05 GMT+00:00 Brandon Williams <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:brandon.williams@akamai.com" target=3D"_blank">brandon.williams@akamai=
.com</a>&gt;</span>:<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Chairs, Any suggestions on approach?</blockquote></div><br></div><div class=
=3D"gmail_extra">The proposal on the table is for Karl+Olle to write their =
idea into a new draft.</div><div class=3D"gmail_extra"><br></div><div class=
=3D"gmail_extra">Karl+Olle, can you guys live with that?</div><div class=3D=
"gmail_extra"><br></div><div class=3D"gmail_extra">Simon</div></div>

--001a113dd406d255690567ef4ff2--


From Martin.Gartner@ingate.com  Tue Mar 20 23:01:15 2018
Return-Path: <Martin.Gartner@ingate.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40AEF12D88B for <tram@ietfa.amsl.com>; Tue, 20 Mar 2018 23:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.371
X-Spam-Level: 
X-Spam-Status: No, score=-1.371 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, STOX_REPLY_TYPE=0.439, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=ingate.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6fPQeQz2bMoZ for <tram@ietfa.amsl.com>; Tue, 20 Mar 2018 23:01:12 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01on0079.outbound.protection.outlook.com [104.47.0.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E66812D7E6 for <tram@ietf.org>; Tue, 20 Mar 2018 23:01:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ingate.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=SStlKvKvXi7yqgOBWc2/MrF1CHQ/ZHy2xIXNg+KlSGE=; b=rz6Xmq4fbUVVeCJtlOT6v0T7A3M35exaiVgjnagxLqbsd1n4klOXUasbZc/Dg4X8f6+4EMUl5nlA42Y8MkfZHTkuQ9k8VTXHQCIzb34Clm9PLyJpefJPTPMp+ApjL6soOvdH9QjBbRWgZ3NeB3b9qM80rsePs++n8q03JXd1VSo=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=Martin.Gartner@ingate.com; 
Received: from LAPTOPCFG0QRG2 (90.227.0.12) by VI1PR0102MB3405.eurprd01.prod.exchangelabs.com (2603:10a6:803:16::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.588.14; Wed, 21 Mar 2018 06:01:06 +0000
Message-ID: <877AA15B7BDF48D4930EC0E548FE2748@LAPTOPCFG0QRG2>
From: "Martin Gartner" <martin.gartner@ingate.com>
To: "Karl Stahl" <karl.stahl@ingate.com>, "'Konda, Tirumaleswar Reddy'" <TirumaleswarReddy_Konda@McAfee.com>, <tram@ietf.org>
References: <152136260256.18150.10551009018364033510@ietfa.amsl.com> <BN6PR16MB1425D61744AC7480972C800AEAD50@BN6PR16MB1425.namprd16.prod.outlook.com> <031e01d3c085$5f581db0$1e085910$@stahl@ingate.com>
In-Reply-To: <031e01d3c085$5f581db0$1e085910$@stahl@ingate.com>
Date: Wed, 21 Mar 2018 07:01:04 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3528.331
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331
X-Originating-IP: [90.227.0.12]
X-ClientProxiedBy: HE1PR0202CA0027.eurprd02.prod.outlook.com (2603:10a6:3:e4::13) To VI1PR0102MB3405.eurprd01.prod.exchangelabs.com (2603:10a6:803:16::18)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: bc4f15a5-c2d6-432f-4796-08d58ef12359
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(2017052603328)(7153060)(7193020);  SRVR:VI1PR0102MB3405; 
X-Microsoft-Exchange-Diagnostics: 1; VI1PR0102MB3405; 3:Ii9g/ORPxq7P1OQHEK0oghqGoJALvVPd7AFsP9/YColclnE2aX4loJS2htMItxMmxOmOihc2unsjvNWxeHgq9bmakOPph2C5LXG+L87cBQD6QT8zFWBgAStQFlpjpWxt1lLuB3xORwwegwWRUQ9dYL9zwg5G/tQ2Pl5zX8qWhSUSrgyYRAIKCv2DrY9aEsPaa95Gc2ZlSLi/1CvPFO7nx4mKgrlToJb+YRXAhM4pfaMcIHmBHobF5W1YNI/8vV2m; 25:idH9D+Eq45IalFzK2L1Cveo/Srur8u2yB4O0wpu91lqYXAHq+P1wnDnQsMinhiCiGvTq7Z5pFaJrygS4TQxNOENBE81JqbWt8Vfne935kRmAkR1XOs2SRe8Uj3Q+IrxGpj50MRvhu5fo109Mg8AoKLkmClHFcUKtOXIKKPTOSI+H6jdYN6ep7/559G+G1aPxFbjduUdZhsQ+eg76k/3xyfcmeG6rfvo8sS49qZ7X1UVfL8pDATXkk0fSCQ9w2Db29C6DCBbIwiOFcC+6+5B/Q3L7mH0TUUwKAjLizQaWbOwq8VVIjxvvIyKS3PNHroLRygaIqf7ME93TB82gFmBzVA==; 31:GY/xwIBiRJIyj75YxxShXK/z3LoYUMLo9gmXodTW5m/biusaNoW0Wm2neziZZYWue54QiyyqIMM8LgChWQozGmVYfSDXfEtVDZdoBHfNwidh+ForPzFXqwfjeznU/BpxRKhNSGa7UZ9WLPE1jk0tpXeNYrTKwSjv7ywtqap57gKsEu7PpPwQ3gt3kVoaIM2oEbOAuY3ZOn+WKBD6eNlYQwsnufQNJsN3tw3mqPcH4bc=
X-MS-TrafficTypeDiagnostic: VI1PR0102MB3405:
X-Microsoft-Antispam-PRVS: <VI1PR0102MB3405F072F8DDD9EA571CFA13FFAA0@VI1PR0102MB3405.eurprd01.prod.exchangelabs.com>
X-Exchange-Antispam-Report-Test: UriScan:(158342451672863)(120809045254105)(213716511872227)(123452027830198); 
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(10201501046)(3231221)(944501319)(52105095)(93006095)(93001095)(3002001)(6041310)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(2016111802025)(20161123560045)(20161123558120)(20161123564045)(6043046)(6072148)(201708071742011); SRVR:VI1PR0102MB3405; BCL:0; PCL:0; RULEID:; SRVR:VI1PR0102MB3405; 
X-Microsoft-Exchange-Diagnostics: 1; VI1PR0102MB3405; 4:USUjMn8iCbY4CVzvNtFcaEJFxb3X1eXqbDTGhTfwWwm5TlCLxl1B/Hj8cCMJES8p2A0X56bt19x5eFWYs9MHMPDYjeH3HXXfJqFgOrwNeFXTxc49ipXrDchVfGq8qWroLyRdMsO5BeEUO13rveximVpdUAFqOutkhiCNjXkz8ckpY620uDT5XuWhUujqJrVRGbtWLoZXGWMnmE+b9PPLDo9AKHX0fwCd+r0kFzpm+Ymrp7MK9dcNWqY42UDSee17RBBtnqUEgF3EExyZt0nb7rmr/cjCPkwmWGXHxrr+xCl/DysCL2/wRbRPLXUzGryJiFnMPqbm4VJIjd+OYwm7NKsemUJI+9JfJtvkjK3Q7oKxZXQ9R+5U6+V7T2nkqIFwsXtFyqUjiPOpt1Ggymu6ly185zqjFHViERNJwxuLN9w=
X-Forefront-PRVS: 0618E4E7E1
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(346002)(396003)(376002)(366004)(39380400002)(39830400003)(38534002)(199004)(189003)(13464003)(377424004)(8936002)(5660300001)(8426002)(81156014)(2950100002)(25786009)(22776003)(81166006)(4720700003)(72206003)(44706002)(16526019)(478600001)(386003)(6246003)(33716001)(50226002)(9686003)(6306002)(8676002)(229853002)(53936002)(305945005)(7736002)(97736004)(55016002)(86362001)(6116002)(44726023)(3846002)(316002)(21396002)(33656002)(93886005)(105586002)(2920100001)(2906002)(23756003)(2870700001)(81686011)(59450400001)(110136005)(62236002)(61296003)(53546011)(966005)(52116002)(68736007)(106356001)(33896004)(76176011)(81816011)(26005)(47776003)(50466002)(67846002)(66066001)(6496006)(4560500001)(21314002)(37786002)(2101003); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR0102MB3405; H:LAPTOPCFG0QRG2; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: ingate.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?iso-8859-1?Q?1; VI1PR0102MB3405; 23:kgrZUlGAZjmuwEknQm5oiofZnEsw+XT2ZENqv?= =?iso-8859-1?Q?xmhwygiMT22+ctTo1UPqfVLWycwHVSgtKPqbxm0k9eb2mVoomk0XRGv05M?= =?iso-8859-1?Q?acVcQu0vTI3Xxj/pD2DSOyqJW0hk6+jwU1N9ty4rfOACkPxu0C0YokknCw?= =?iso-8859-1?Q?tKPQozqGGpIDsRXj8+05quwPm3xzq0csyz+q2jlmvtDxshVmH8uoWKKQaB?= =?iso-8859-1?Q?NmKPkGs9r14ejZW8gj3KKJEjP4uXeq2EsThYNGPKqd/F1NS/4oH/oV9q+U?= =?iso-8859-1?Q?ABFH1iJAoQWaA9kJWnQEFtideJmInDknX4/mzAaEDXYDMGg8VPTrucoLpy?= =?iso-8859-1?Q?L2K2DXjduFHtItO9t+up4a0AGSzQKx+MVf24Wd7siWDFIxkwCdkDvnwsLn?= =?iso-8859-1?Q?YAC4huRb3A4muJdZ5hd7PdahkPvbez7unA2/v8sS0lIrESbuTjbsjoDJlx?= =?iso-8859-1?Q?ATHXoU1nuNj3IhV/ysbBygoSFZ/FQSXCJOad31DmPh85s9U56xlRas597H?= =?iso-8859-1?Q?uZ5V2EUr2er+WQE8JAHB5obeV1CjFPfs5Hyz4s/wg4prz9rpZtQ/1hmy0E?= =?iso-8859-1?Q?WZlomq3oYbOvS2mPLPvzhsW76TevnoCfoHvdB9/CnqASVao6G4QFhTtCFT?= =?iso-8859-1?Q?LUiPjI0E0xzd3e1cD9q7kMNSsL5h7ds+R5Sf6nzpt885wbZAf0USsqDso9?= =?iso-8859-1?Q?ycrLCeK63E4dXqksYtg10cbwQl5UswkNcpilfq4vm9oJ8OoY09I6rMIVUe?= =?iso-8859-1?Q?cqAeq9rX0QJ7mhpPd7JWHlgT3FLj8PT3aGz9cxxrYQ7zKW+FagFHDWeMtF?= =?iso-8859-1?Q?d8FLkI354lFYlktKZ6nYNI6M7h2ofbMQAQsC7tTEodzBaln+o8Xt7tgHFF?= =?iso-8859-1?Q?+mD7e7hu6nOZnxYcFZKLPeoxga64Z56X5jxpXAQkvY+bbA93kPEYadUqrJ?= =?iso-8859-1?Q?J2SKTCj4m6Er8xsPbR2jlT9atkwDbE1IKbg3bmZBQHrtccBDkFLZXITGG/?= =?iso-8859-1?Q?X+82mWw9ntoT2hg4NkjkXu1p+PNTCz7ENruwFXtTzjO+F2VKZxH19/yDLL?= =?iso-8859-1?Q?FVrAWmydfSYcvOCdO/FSYb21sRTk+1gUcE5Ka4vse/aFhTCj6YVGRvXR8N?= =?iso-8859-1?Q?HTUeWr2e+iCAc2eHpFu5i6d68k5lQUGWJDRjZNpXaHnB7OgyVvFN6N1Wa3?= =?iso-8859-1?Q?vdnEipgVCDzbAhlEdCTcvtvCAmv8rdmcx7HKve22XaSMXl/zaifo/K62FI?= =?iso-8859-1?Q?UzJbet71ehiGZlWfwxkMj2ogNdG5ZN/n94Id0b3iXQuPTIvo2WzbuS+9hf?= =?iso-8859-1?Q?W6nzMcDdHOFE87SK4ZCxfjpnJYo3vPMpmrm0dEztBcSWF4kq8w0i6ZFvg+?= =?iso-8859-1?Q?jZQSdihCLPGh7XxFHdWDR5E9g2PD+drp0hjaErvgMs6yN35wXqAhKOEbB0?= =?iso-8859-1?Q?QKHQE5+xkFgguOF3s7+yT2ugOjjGEWeKLOYt+gQzdRGxN2hnMnmR0wiecJ?= =?iso-8859-1?Q?MfVYJSI8UbRwZhcFYFIeFDGO91cl17v9++v9qtfhOu5rRN2tdstoyoQfAS?= =?iso-8859-1?Q?2+Q2jsxzR2nYmNuWqAgaHlPhQiHM/R2hgGt+YRJ0h8Q6N5rBgldZ45bvew?= =?iso-8859-1?Q?sx3DSrJv1PcWKCWhzgQG5x0T92Qo71CM9Eeioj0gcLO/Vkjo3xyk+3+z5I?= =?iso-8859-1?Q?njaLF5u8h17/IQ1ZcNbbfvTM5rmOV4hP2GaZoIi8QT3fVQXCtXN2DZHw3t?= =?iso-8859-1?Q?K2p?=
X-Microsoft-Antispam-Message-Info: h+uaDWrFTi6UUqokYXBvio4PbQmr/jika2+jcA6sS1SXWjUYgTwX8x6G7vsqpboH/WcvkBjEdae8Pv9k6Q7oVuVZEUSETDMOrOWKIVw7g2NdE+0Ol2lzKv59haRnVLuzYxQxhdRay2k9Yf2XsDm4V3d8BORz88DDehm0oAB1e84zc45d5ruhEzfcpEYiHxkk
X-Microsoft-Exchange-Diagnostics: 1; VI1PR0102MB3405; 6:rZdYZygi1GdPp7bXtSR4cCwtRkKEZlzvCMwQ5cgw2sQ2uU1mRsH54BrS3I/GfQl9jBDljIJ3axXAmJKL1YbLduglTK+LBOZv6AXAVICXT0S1L+GdcUDAxluAQn/ueidbR0zRFNrcC8o/NWzJLW266SQcCZtX/gALSZkpuq8nl8Uqv4LclZkrLnA4vl0Gsb6sgK3Eu9lJY7DC6r61FWS7TwKoufznzVqEHYvITI+NIZC0I+mK7kUrjxsjGTZhRObI+ttIS0Gx1ULbNWcKofDcPgw4DHg/agYCUcaPc/SzazKV5k2GUlOfCGhV6wssd31oGehCY0bV+wKESPQ6hu1HxTD9w1JFihGXaL/fmFGvd+A=; 5:0j3I6ALGQ6BkQbj97+bMYOlh5faeEuwTPN/LpnTjK43UcL/dZrdxNHaiM11azF8yym8FnO5jy0C8LYNjE263tP2wJOpbENOEsh5NrOJIimds97A2PIr+J1n78LZJhXJzagCb0PwiL4kzFYYKLZDXx2lrLlX0+aP4rMSpyzH5Q4U=; 24:1eRv3vGI93Gx7HOqWz5LAZKt6DKH5Io6FN0hiS2f8CrMo03Z5BAMwunq05M861nULhnrzB8YSnVv56MDk14t7YA3DqfWRW5IMux4boUsNXs=; 7:Ci5rVYNhMrxVN1JH8yCrEnUbShq18Sc5XD2veOHQqNa8HEsn+bVIBodgaMGxhEHrV0zEimDdsbhxSZVzsT2vMSvlQWikYiYPHNAkJt8woRM2FncJEvk16fVOdqbxXaPoOVkITRPj6Hql4zYr+ub5v/+8bVfsfA2DJT6vD4VvtJ0UBsi00pggUkcnfpfFayUF1vPpCEkDla1Opcg45utPz9uisWNdA8pNZRE19UhnOf3BFKuf3dAXpICbqqG8sVS4
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: ingate.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Mar 2018 06:01:06.8171 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: bc4f15a5-c2d6-432f-4796-08d58ef12359
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: c3eda49a-3ed0-46c6-8a9e-d0d8ce3d2fae
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0102MB3405
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/tXu9t2850NPHKJpbX552cUnI2Eo>
X-Mailman-Approved-At: Wed, 21 Mar 2018 11:27:07 -0700
Subject: Re: [tram] Multiple allocations SV: I-D Action: draft-ietf-tram-turnbis-15.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2018 06:03:16 -0000

In my thinking, a TURN server is just a remote extension of the available 
interfaces which a client can use to try network connections by using ICE.
All client interfaces are used when trying to find the best network path 
with ICE, so it seems just logical to do the same for the TURN server, to 
use all of its interfaces when trying to find the best network path. And to 
make this possible, there must be a way to inform the client about more than 
one available relay address, if the network provided TURN server has access 
to more than one network path.
So it seems what Karl proposes is definitely needed.
Martin

-----Ursprungligt meddelande----- 
From: Karl Stahl
Sent: Tuesday, March 20, 2018 8:55 PM
To: 'Konda, Tirumaleswar Reddy' ; tram@ietf.org
Subject: Multiple allocations SV: [tram] I-D Action: 
draft-ietf-tram-turnbis-15.txt

> This revision addresses comments from Mark, Karl and Noriyuki Torii.
My comment about need for multiple allocations is NOT addressed.

Let me explain more clearly why multiple allocations is needed:

ICE is about finding all/many paths for the media, e.g. with the help of
TURN servers.
Those paths are not over ONE IPv4 network, over ONE IPv6 network or EXACTLY
ONE OF EACH.
If fact, it is more common that you have several IPv4 networks paths.

Now that we have network provided TURN servers, you only ask for Allocation
once (contrary to application provided TURN servers, where you can be
directed to Allocate several times.) and thus we need all relay addresses in
one allocation request.

Wasn't that the reason dual allocation was requested? The need for multiple
allocation is stronger!

Please address this, e.g. like below (seems you are almost there).

/Karl


******************* Previous *******************

Allowing a turn allocation to return multiple relayed transport addresses,
beyond ONE IPv4 and ONE IPv6 (which may sit on the same or on different
interfaces/network segments), seems like very small step now when the dual
allocation was put in place in this draft. We certainly need it (some
reasons below) if TURN is going to be used where needed and we cannot wait
for any additional draft.

Seems like it is sufficient to extent this table (found in draft 14) with 3
new values (as shown):

16.  STUN Attributes

   This STUN extension defines the following attributes:

     0x000C: CHANNEL-NUMBER
     0x000D: LIFETIME
     0x0010: Reserved (was BANDWIDTH)
     0x0012: XOR-PEER-ADDRESS
     0x0013: DATA
     0x0016: XOR-RELAYED-ADDRESS
     0x0017: REQUESTED-ADDRESS-FAMILY
     0x0018: EVEN-PORT
     0x0019: REQUESTED-TRANSPORT
     0x001A: DONT-FRAGMENT
     0x0021: Reserved (was TIMER-VAL)
     0x0022: RESERVATION-TOKEN
     TBD-CA: ADDITIONAL-ADDRESS-FAMILY
ADDITIONAL-ADDRESS-ALL
ADDITIONAL-ADDRESS-ALLV4
ADDITIONAL-ADDRESS-ALLV6
     TBD-CA: ADDRESS-ERROR-CODE
     TBD-CA: ICMP

Actually, browsing through the draft for ADDITIONAL-ADDRESS-FAMILY, very
little text seems to be added for generalization to  ADDITIONAL-ADDRESS-xxx.
Almost everything applies to ADDITIONAL-ADDRESS-xxx and can be reused.

ADDITIONAL-ADDRESS-ALL should be the default for any modern TURN client.

Check! - We need this now.

Thanks,
Karl

> -----Original Message-----
> From: Karl Stahl [mailto:karl.stahl@ingate.com]
> Sent: Sunday, March 4, 2018 10:36 PM
> To: 'Marc Petit-Huguenin' <petithug@acm.org>; Konda, Tirumaleswar Reddy
> <TirumaleswarReddy_Konda@McAfee.com>; tram@ietf.org
> Subject: SV: [tram] Review of dual allocation in TURNbis-11
>
> Hi,
>
> When we now have "dual allocation" into this draft (I see on page 26: "If
the
> client wishes to obtain one IPv6 and one IPv4 relayed transport address
then
> it includes an ADDITIONAL-ADDRESS-FAMILY transport address then it") can
> we not generalize that further and allow MORE THAN ONE relayed transport
> address (of any family) in response to an allocation?
>
> I mean that a TURN server could have several relay interfaces at different
IP-
> addresses into different networks - not just the Internet, but also a VoIP
> (higher quality) network e.g. by some triple play service provider, an IMS
> network or some branch office network.
>
> I think this is specifically important for network provided/auto
discovered
> turn servers (application provided turn servers could instead just list
several
> turn servers).
>
> I saw someone snipped this about "SINGLE relayed transport address per
> allocation request"
> > > https://tools.ietf.org/html/rfc6156#section-3
> > > <snip>
> > >
> > >    TURN servers allocate a single relayed transport address per
> > >    allocation request.  Therefore, Allocate requests cannot carry more
> > >    than one REQUESTED-ADDRESS-FAMILY attribute.  Consequently, a
> client
> > >    that wishes to allocate more than one relayed transport address at
a
> > >    TURN server (e.g., an IPv4 and an IPv6 address) needs to perform
> > >    several allocation requests (one allocation request per relayed
> > >    transport address).
> > > </snip>
>
> but if that is remedied now, it seems like a small step to generalize so
we can
> get multiple relayed transport addresses from one allocate request?
>
> /Karl


-----Ursprungligt meddelande-----
Från: tram [mailto:tram-bounces@ietf.org] För Konda, Tirumaleswar Reddy
Skickat: den 18 mars 2018 09:51
Till: tram@ietf.org
Ämne: Re: [tram] I-D Action: draft-ietf-tram-turnbis-15.txt

This revision addresses comments from Mark, Karl and Noriyuki Torii.

-Tiru

> -----Original Message-----
> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of internet-
> drafts@ietf.org
> Sent: Sunday, March 18, 2018 8:43 AM
> To: i-d-announce@ietf.org
> Cc: tram@ietf.org
> Subject: [tram] I-D Action: draft-ietf-tram-turnbis-15.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> This draft is a work item of the TURN Revised and Modernized WG of the
> IETF.
>
>         Title           : Traversal Using Relays around NAT (TURN): Relay
Extensions
> to Session Traversal Utilities for NAT (STUN)
>         Authors         : Tirumaleswar Reddy
>                           Alan Johnston
>                           Philip Matthews
>                           Jonathan Rosenberg
> Filename        : draft-ietf-tram-turnbis-15.txt
> Pages           : 84
> Date            : 2018-03-18
>
> Abstract:
>    If a host is located behind a NAT, then in certain situations it can
>    be impossible for that host to communicate directly with other hosts
>    (peers).  In these situations, it is necessary for the host to use
>    the services of an intermediate node that acts as a communication
>    relay.  This specification defines a protocol, called TURN (Traversal
>    Using Relays around NAT), that allows the host to control the
>    operation of the relay and to exchange packets with its peers using
>    the relay.  TURN differs from some other relay control protocols in
>    that it allows a client to communicate with multiple peers using a
>    single relay address.
>
>    The TURN protocol was designed to be used as part of the ICE
>    (Interactive Connectivity Establishment) approach to NAT traversal,
>    though it also can be used without ICE.
>
>    This document obsoletes RFC 5766 and RFC 6156.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tram-turnbis/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-tram-turnbis-15
> https://datatracker.ietf.org/doc/html/draft-ietf-tram-turnbis-15
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-tram-turnbis-15
>
>
> Please note that it may take a couple of minutes from the time of
submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram

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


From nobody Thu Mar 22 14:17:25 2018
Return-Path: <karl@ingate.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 314AD1241F5 for <tram@ietfa.amsl.com>; Thu, 22 Mar 2018 14:17:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MSGID_MULTIPLE_AT=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ingate.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XKoZe_Z8_rkq for <tram@ietfa.amsl.com>; Thu, 22 Mar 2018 14:17:20 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0624.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe02::624]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4642D12025C for <tram@ietf.org>; Thu, 22 Mar 2018 14:17:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ingate.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=MRhcKYrIhyFcQu+dDMJiLW65KCoLlg0Ra7Yf/LVJPKM=; b=JHNgFV+CEPg7M5vZlxkma8+yO+EZLUry83omAEvWWcBAK3CkWUl2HrvCC+YcxvsoY3esyrxKdgvTGfO9ECYkOZ3KT/SMqUulCC3YqAF2XlbFHxmdK9TtbZPppNvDcUuna8VoErViCVqOLyrD8n9vjOmAlMQBR+OeNN/RkKTUC4Q=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=karl@ingate.com; 
Received: from Kallei7 (90.229.133.175) by HE1PR01MB1836.eurprd01.prod.exchangelabs.com (2a01:111:e400:7bc0::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.588.14; Thu, 22 Mar 2018 21:17:14 +0000
From: "Karl Stahl" <karl.stahl@ingate.com>
To: "'Simon Perreault'" <sperreault@jive.com>, "'Brandon Williams'" <brandon.williams@akamai.com>
Cc: "'Konda, Tirumaleswar Reddy'" <TirumaleswarReddy_Konda@mcafee.com>, "'Olle E. Johansson'" <oej@edvina.net>, <tram@ietf.org>
References: <152136260256.18150.10551009018364033510@ietfa.amsl.com> <BN6PR16MB1425D61744AC7480972C800AEAD50@BN6PR16MB1425.namprd16.prod.outlook.com> <BEC020EA-C973-48E5-A918-EF2D25953E33@edvina.net> <BN6PR16MB1425327E5CD094CF18A040F2EAAA0@BN6PR16MB1425.namprd16.prod.outlook.com> <c3584946-2782-2ac7-7f7c-7e7ae273fec9@akamai.com> <CANO7kWC5H_0jv-=MsRzQaO7C=SsTbqz-UJhARm2f1SWOA6uutA@mail.gmail.com>
In-Reply-To: <CANO7kWC5H_0jv-=MsRzQaO7C=SsTbqz-UJhARm2f1SWOA6uutA@mail.gmail.com>
Date: Thu, 22 Mar 2018 22:17:09 +0100
Message-ID: <048b01d3c223$249e62c0$6ddb2840$@stahl@ingate.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_048C_01D3C22B.8662CAC0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdPBN/Tmrg2D/NKJTfC9XoJn8XHKcQA3WhUw
Content-Language: sv
X-Originating-IP: [90.229.133.175]
X-ClientProxiedBy: AM0PR0102CA0067.eurprd01.prod.exchangelabs.com (2603:10a6:208::44) To HE1PR01MB1836.eurprd01.prod.exchangelabs.com (2a01:111:e400:7bc0::26)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 8ab610ab-5440-4804-87ab-08d5903a493d
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(5600026)(4604075)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(2017052603328)(7153060)(7193020); SRVR:HE1PR01MB1836; 
X-Microsoft-Exchange-Diagnostics: 1; HE1PR01MB1836; 3:vQv/jecoZgqoDUM+smnkNKz+7oAIkSnPEnhFo7fsUa6365Q3NOLPJ/+/iCojIs23cNbk2iqnTcc7kykbIWLgQlG3fDS2SMLpW/SCZRVBnJxKujhayY2XP64QNfwVUfByhnqaOvlk4G2GQXlZvKHFCVBIC5Fj1V6AtUqDQzg4AHVXigv/d9Fk3PoUWyYixniCUoc+PKiQ9yu6yrvfQ6moZUiPJ3qelhGsGWCJWXMncQlPCG89P8VmZBhEjrfFCVHV; 25:34TzzxNtwVzeqNxIyR79gV5SDCji1QQyi13Cydlp9onco2VNo5dcoK0QwbV0QXYrG4pL1BgleCCkfwpFsra0oRRhcQYL668dTvvZ9hY0lkphbDr5nxKpFodp5fUlc5VvxeJ3WBUoBfNSB53LKVWUBez155g8qAxNMtLxtMR35LfdsKaNG23/Yp1ypaHxHrtot66wGPj3a23Ovqaaitd0WhMonm8+F6J9NfAxV0Nq6FqtNZjJCKbiS7FzVjIocgVF2JNx8Rsq9cZ1pfUayhknPctYHwhvsD9LvlrZf0XiaZCxW7osL8BgY7TyJ3gJ3Lbr5WaF97qZKY6Jw5W0ujuSUw==; 31:N8x9ZuffxBmaj2xeyA4+nWB9wgmjuNBAkx+WMzDPwdhbL9RVrrfldGkkVnvJ31APuPG4jYZjazXT3PsA3toIxuIay21gBvHvlfD5B3x02oHAhqWO8KDf2BfbrRP7vbEQGq38hjSG4ibqNo2W9cpapF7TZnYaRPQt3oyuewpfIAEjFr19gB1/0rrLe5qOpjJncGRiY9oUDQKY8stjWKufKIn7p2oyqa+L0fYjTAHhlcg=
X-MS-TrafficTypeDiagnostic: HE1PR01MB1836:
X-Microsoft-Antispam-PRVS: <HE1PR01MB1836D08B1CE4F0EE962B0871B1A90@HE1PR01MB1836.eurprd01.prod.exchangelabs.com>
X-Exchange-Antispam-Report-Test: UriScan:(28532068793085)(21748063052155);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(3231221)(944501327)(52105095)(10201501046)(3002001)(6041310)(20161123560045)(20161123558120)(20161123564045)(2016111802025)(20161123562045)(6043046)(6072148)(201708071742011); SRVR:HE1PR01MB1836; BCL:0; PCL:0; RULEID:; SRVR:HE1PR01MB1836; 
X-Microsoft-Exchange-Diagnostics: 1; HE1PR01MB1836; 4:YLC0TzLm+NjquIzxYPHwb/WjcwS/b6iP+idqyQA/491TI/oBAhsltJSkwIuo2xnJHoXnHqvy3vDAnQ16S7eOvv03S2ZdGqEfE3ROqyyIl4CEAz8EBnOFHaPViJsTb2RFngt8xKqjL4GVZJWsSJd4qqJhkN1d/jxr4YCAo6bQqpjxXWPVAiwne9GmZb5oCzuFRPRWOxSWzhOEhT+sWyS1BbfFNn4IFuRE66pKydAi9e3MckOoVIYBU4htkHUjTnnMVELLiGadj/6d4Nkl4Ekmctx8Y/7+kqowTPA02RMpEvd8vDy3FdkkwvQqiQMezc2B4ZQn2dbEqmNFJWH5DgadhZ+FRCsbBxIUkfxwAdK5vL8=
X-Forefront-PRVS: 0619D53754
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(39380400002)(396003)(346002)(366004)(376002)(39830400003)(377424004)(189003)(199004)(18717965001)(36756003)(7826002)(3846002)(81166006)(6116002)(97736004)(790700001)(8676002)(52116002)(76176011)(9686003)(54896002)(7736002)(81156014)(61793004)(6306002)(236005)(6666003)(316002)(446003)(84116003)(96836002)(16586007)(93886005)(106356001)(8936002)(50226002)(561944003)(71636004)(14726001)(2906002)(186003)(1420700001)(105586002)(25786009)(61296003)(53936002)(386003)(16526019)(59450400001)(39060400002)(33896004)(478600001)(4326008)(6496006)(26005)(5660300001)(66066001)(6486002)(110136005)(68736007)(54906003)(44736005)(102836004)(84326002)(33964004)(11346002)(21314002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR01MB1836; H:Kallei7; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received-SPF: None (protection.outlook.com: ingate.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; HE1PR01MB1836; 23:WETP1T4Rpq2gnmbyi0XO+a1dSDAe9fpZksBEJ/B25?= =?us-ascii?Q?JkpNB7ozXmnvQjDT0wR6v+9RMl+enEcrDQyfaAQfNchTjYyJf6R+5UpewEED?= =?us-ascii?Q?9xHkBuxh9m7Ov5SvXVRFFm5NziXbDSwdVSX8UPUAxrZ8KAjmRIvKga9nIUss?= =?us-ascii?Q?DZbLORVIVhw2xLQCVUTBMfB66hXbh1gpE5KxNWehhaLeW/wNwNCtDM7gXKlh?= =?us-ascii?Q?XM/VGqvR4ffFpbSFp2IQEsVfqdHwoSjSe5hBGd1m6QuxDkFUlJA7/rnAbQ38?= =?us-ascii?Q?iO8DjBCTcB0aK4iPWX5m+nerV7HVhPlkEFcyZimIVSSqBPwuY10KMZ+5QAdH?= =?us-ascii?Q?qvG1hBM0bUqJmfkHIiaojyQiwhZbQi1CV7Ko48TvfJVSJoJpwTXyENWFw7/+?= =?us-ascii?Q?RJf9u9hluLJGBfunL3dykA3M1VPz5NXbiqZFH2DxpijUX4/nLLixAcckawPk?= =?us-ascii?Q?bT6+GtttL0Lkf8DvaT9D2J70nYm8Fob6AXq4Ocru0KPphOCkXVAYUb2Sri/D?= =?us-ascii?Q?msunyeE4f9L1IoIopDPFuZkWQb75qQwuSJSe5xbjA8jtANuOKFNPrYF08upq?= =?us-ascii?Q?tKCXGXhg/2pIYIC0rpPcok2RDdjhEgR1XpBBk7lpoJySvYNIzNVcj3I3D5UA?= =?us-ascii?Q?Uup9DlVXNM3szF/T5VsUfNjpj+XEACVzEKOIXpTST0GD+jNhQqUVDRJk5NDw?= =?us-ascii?Q?ReKWwujq2iOfieoB3EgfwkAK9AbO/9fe/XlzbIlYKOQNIa7Oj3aHr8Laivge?= =?us-ascii?Q?Z81LdcZKxjQjj/Zz8Iwe4NiIRcsTLLaDmCMe4RN074sWYnMMb4WLgqdmeEIT?= =?us-ascii?Q?my+J415ixKnHTzrSzoRhSsp+TDT4KK571b1A8NE5JzNBlhdCRQkRy3DdO4T8?= =?us-ascii?Q?ySgd7x+b7S8Ap2a7GwQK7UGw9VuFWyjJnL9sd/RzrelgE5SSCk8IdWaHjIqZ?= =?us-ascii?Q?cj+b/bqP64hfwfGwjIKswYYkBfrjQkDTbXbbd++ygDlY0sPf9qC8qnFftNNm?= =?us-ascii?Q?Phjo4E7NyNRs/MHIVpQnke+NWVLpJSmtg3Fj7mfIdbXlgWAvdzmvcZLlQlvD?= =?us-ascii?Q?yZZ58s4gmbYAshsFThfmW10EORKPxncXMzmF8CD8LqJsFo42uKoW9/6Xz09K?= =?us-ascii?Q?4B9a0+B/5+UdTOp61iibgo8/916nAvM8ZuMiJ58T6X9XFxcH4GcXcGmigdvi?= =?us-ascii?Q?2QrplelrnImxo+KEJ9iLTIPDkTk1KQewowKgI46NKgCNcp7UpuyeoZx6W0fM?= =?us-ascii?Q?xS1T48O+LV9YytsbCSyax+exhgc8yAaz8Ucm1Qo2/wTVJpbd2Zl9LNMPFJvT?= =?us-ascii?Q?l1NMidI4A40dEE3T64R0YloxorijaUOEruVS+FEOYElnMgcFpYRCqL+Cvxnm?= =?us-ascii?Q?sF7RD/zcF3cwnHsPOYMx5309T9hXyTJ9UIxMf0dZ6K5GEqbi9r9LVV4RAelc?= =?us-ascii?Q?Ga2bJlSoenh0U0vS2w+5XtMqSjEthAGnyq0hXqVtqPmxP3LEejRTHNHhJjgX?= =?us-ascii?Q?I5QaCoGp9fyr3n8p4dWNSsDy7strSY9g6WIF9zm9UqGkk4U6GHSo2QU?=
X-Microsoft-Antispam-Message-Info: 0G/JRuWpm36b6QqG+sx0MxxEFtSQNdGT5tzE5WGhnCUz977tox7VWyiDl0pQP9V93aGJ1B++4uyDpMOShrxLAjDKlliRuZJe4acV/n+UOu+ptmK7QHpivNdFaXtQU6bBdDpAPgdDve+MibYF+OfzbeaLdy7kQP4KM/b/bMQpKZyNTnXVGFEvf27gBXZj2LBU
X-Microsoft-Exchange-Diagnostics: 1; HE1PR01MB1836; 6:ga1WEAcje0qZFEIiMd/34wIS0kHS+YloxyZDAk2K4s8mwVLJgd75p7FmRdj0O2qY7V3oPNKpCC+92xy/QMmmlNPn493fDjuFY9KFp2Dwd1KtByH84u5XVDQeUyIxgSbmq7rYXaUZKIrGM2Ptwss8TH8lJqKlsh2NIopNQBW/0FhNiB9MTYs1RgffKgsZcQgJv1xAXNoMiJ8AWRtcQzgaQWLpkQakgXsDyh9qfieJfFf11GHb439V1UoDNo2JSK4tSReL1fWRdhUqVELii2n3xZz3ERBULIB0+0PwwfzLD0Zl200ns7Wt3oDFQgmBfvfyQL0jaE0g7nf1Bxxvi2pCDXOnDFSvKdnLO/I2Rsrh4iA=; 5:X6dp7SPr1Qey0QwJbsbT7MbBZk0qV4hjQBPP0vKuRiDCoIa7KjRLcHQyQX6/cayh/zkXFheCES9V2McAc8YOYLaz9btbQhypgchaiiti3BgzCW+CNt71g6DRHk1idFCQI2qkpVGqByaaXhNR5f8qJBBZTCiu3nVuuWEPvF4AjsE=; 24:gmaOLRRufcmKJUSPz+OzSlvKEcl+1PcDavXamnBw1e8WRk75tjQdapfOJu+YtlqDZAZLp9f5T6GBrbrVlKPDNFhaFYovCOp7sSvdi51l1CA=; 7:NeOzNBoV/JI4BkmFgSHo7EmxmM0WnBj+ODfNt/M7QEeOMsVrVdbbQY36pvHSvaQa5oJlOmU4DhVMr7Yx9K3tU9D2Rd4sqaGwh0qbVGes6gKUYZtgduD09rkSrKoDwSQUj9W94RtPTPJsWzJNy0JVHaHUCUtq10BAcn9MHC1S6oO0WHsA/eehDtSClraTqcRc/8k6w3+syzbZZxn6YhibVOoTsB6N++EBmkrFhKGP5FGCBrv9ItsDUmypArz8XPdL
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: ingate.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 22 Mar 2018 21:17:14.6252 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 8ab610ab-5440-4804-87ab-08d5903a493d
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: c3eda49a-3ed0-46c6-8a9e-d0d8ce3d2fae
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR01MB1836
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/SQ7v5cjyo14A5XTNIgZ-AG5u8vQ>
Subject: Re: [tram] Multiple allocations SV: I-D Action: draft-ietf-tram-turnbis-15.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2018 21:17:23 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_048C_01D3C22B.8662CAC0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

No and this draft cannot be approved without the generalization I have =
pointed out.

I really don=E2=80=99t understand why we are having this resistance.

=20

Already the second paragraph of the Abstract states:

The TURN protocol was designed to be used as part of the ICE

   (Interactive Connectivity Establishment) approach to NAT traversal,

   though it also can be used without ICE.

=20

And further in the Introduction

TURN was designed as one piece in the larger ICE approach to NAT

   traversal.  Implementors of TURN are urged to investigate ICE and

   seriously consider using it for their application.

=20

=20

I cannot imagine that there is some WG decision to hinder ICE usage for =
network provided TURN servers EXCEPT FOR EXACTLY BRANDON=E2=80=99S =
NETWORK.=20

=20

For now I refrain from writing/debating more =E2=80=93 which would =
override the effort of what is required to generalize as asked.=20

Please be happy that most of the dual allocation work done, can be =
reused to fulfill the generalization.

=20

Tiru and Brandon are encouraged to read the TRAM charter =E2=80=A6=20

=20

/Karl

=20

=20

Fr=C3=A5n: Simon Perreault [mailto:sperreault@jive.com]=20
Skickat: den 21 mars 2018 18:13
Till: Brandon Williams
Kopia: Konda, Tirumaleswar Reddy; Olle E. Johansson; Karl Stahl; =
tram@ietf.org
=C3=84mne: Re: [tram] Multiple allocations SV: I-D Action: =
draft-ietf-tram-turnbis-15.txt

=20

2018-03-21 17:05 GMT+00:00 Brandon Williams =
<brandon.williams@akamai.com>:

Chairs, Any suggestions on approach?

=20

The proposal on the table is for Karl+Olle to write their idea into a =
new draft.

=20

Karl+Olle, can you guys live with that?

=20

Simon

=20

**********************

=20

Let me explain more clearly why multiple allocations is needed:

=20

ICE is about finding all/many paths for the media, e.g. with the help of

TURN servers.

Those paths are not over ONE IPv4 network, over ONE IPv6 network or =
EXACTLY

ONE OF EACH.

If fact, it is more common that you have several IPv4 networks paths.

=20

Now that we have network provided TURN servers, you only ask for =
Allocation

once (contrary to application provided TURN servers, where you can be

directed to Allocate several times.) and thus we need all relay =
addresses in

one allocation request.

=20

Wasn't that the reason dual allocation was requested? The need for =
multiple

allocation is stronger!

=20

Please address this, e.g. like below (seems you are almost there).

=20

/Karl

=20

=20

******************* Previous *******************

=20

Allowing a turn allocation to return multiple relayed transport =
addresses,

beyond ONE IPv4 and ONE IPv6 (which may sit on the same or on different

interfaces/network segments), seems like very small step now when the =
dual

allocation was put in place in this draft. We certainly need it (some

reasons below) if TURN is going to be used where needed and we cannot =
wait

for any additional draft.

=20

Seems like it is sufficient to extent this table (found in draft 14) =
with 3

new values (as shown):

=20

16.  STUN Attributes

=20

   This STUN extension defines the following attributes:

=20

     0x000C: CHANNEL-NUMBER

     0x000D: LIFETIME

     0x0010: Reserved (was BANDWIDTH)

     0x0012: XOR-PEER-ADDRESS

     0x0013: DATA

     0x0016: XOR-RELAYED-ADDRESS

     0x0017: REQUESTED-ADDRESS-FAMILY

     0x0018: EVEN-PORT

     0x0019: REQUESTED-TRANSPORT

     0x001A: DONT-FRAGMENT

     0x0021: Reserved (was TIMER-VAL)

     0x0022: RESERVATION-TOKEN

     TBD-CA: ADDITIONAL-ADDRESS-FAMILY

ADDITIONAL-ADDRESS-ALL

ADDITIONAL-ADDRESS-ALLV4

ADDITIONAL-ADDRESS-ALLV6

     TBD-CA: ADDRESS-ERROR-CODE

     TBD-CA: ICMP

=20

Actually, browsing through the draft for ADDITIONAL-ADDRESS-FAMILY, very

little text seems to be added for generalization to  =
ADDITIONAL-ADDRESS-xxx.

Almost everything applies to ADDITIONAL-ADDRESS-xxx and can be reused.

=20

ADDITIONAL-ADDRESS-ALL should be the default for any modern TURN client.

=20

Check! - We need this now.

=20

Thanks,

Karl

=20

=20


------=_NextPart_000_048C_01D3C22B.8662CAC0
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 12 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Oformaterad text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML - f=C3=B6rformaterad Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
span.E-postmall17
	{mso-style-type:personal-reply;
	font-family:"Arial","sans-serif";
	color:blue;}
span.OformateradtextChar
	{mso-style-name:"Oformaterad text Char";
	mso-style-priority:99;
	mso-style-link:"Oformaterad text";
	font-family:Consolas;}
span.HTML-frformateradChar
	{mso-style-name:"HTML - f=C3=B6rformaterad Char";
	mso-style-priority:99;
	mso-style-link:"HTML - f=C3=B6rformaterad";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DSV link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>No=
 and this draft cannot be approved without the generalization I have =
pointed out.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>I =
really don=E2=80=99t understand why we are having this =
resistance.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'><o=
:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>Al=
ready the second paragraph of the Abstract =
states:<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN =
style=3D'font-family:"Courier New"'>The TURN protocol was designed to be =
used as part of the ICE<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN style=3D'font-family:"Courier New"'>=C2=A0=C2=A0 (Interactive =
Connectivity Establishment) approach to NAT =
traversal,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN =
style=3D'font-family:"Courier New"'>=C2=A0=C2=A0 though it also can be =
used without ICE.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'><o=
:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>An=
d further in the Introduction<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-family:"Courier New"'>TURN was designed as one piece in =
the larger ICE approach to NAT<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'page-break-before:always'><span lang=3DEN =
style=3D'font-family:"Courier New"'>=C2=A0=C2=A0 traversal.=C2=A0 =
Implementors of TURN are <b><u>urged</u></b> to investigate ICE =
and<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN =
style=3D'font-family:"Courier New"'>=C2=A0=C2=A0 seriously consider =
using it for their application.</span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:blue'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'><o=
:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'><o=
:p>&nbsp;</o:p></span></b></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>I =
cannot imagine that there is some WG decision to hinder ICE usage for =
network provided TURN servers EXCEPT FOR EXACTLY BRANDON=E2=80=99S =
NETWORK. <o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'><o=
:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>Fo=
r now I refrain from writing/debating more =E2=80=93 which would =
override the effort of what is required to generalize as asked. =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>Pl=
ease be happy that most of the dual allocation work done, can be reused =
to fulfill the generalization.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'><o=
:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>Ti=
ru and Brandon are encouraged to read the TRAM charter =E2=80=A6 =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'><o=
:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>/K=
arl<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'><o=
:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'><o=
:p>&nbsp;</o:p></span></p><div style=3D'border:none;border-top:solid =
#B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Fr=C3=A5n:</=
span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Simon =
Perreault [mailto:sperreault@jive.com] <br><b>Skickat:</b> den 21 mars =
2018 18:13<br><b>Till:</b> Brandon Williams<br><b>Kopia:</b> Konda, =
Tirumaleswar Reddy; Olle E. Johansson; Karl Stahl; =
tram@ietf.org<br><b>=C3=84mne:</b> Re: [tram] Multiple allocations SV: =
I-D Action: draft-ietf-tram-turnbis-15.txt<o:p></o:p></span></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><div><p =
class=3DMsoNormal>2018-03-21 17:05 GMT+00:00 Brandon Williams &lt;<a =
href=3D"mailto:brandon.williams@akamai.com" =
target=3D"_blank">brandon.williams@akamai.com</a>&gt;:<o:p></o:p></p><p =
class=3DMsoNormal>Chairs, Any suggestions on =
approach?<o:p></o:p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The proposal on the table is for Karl+Olle to write =
their idea into a new draft.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Karl+Olle, can you guys live with =
that?<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Simon<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'><o=
:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>**=
********************<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'><o=
:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>Let =
me explain more clearly why multiple allocations is =
needed:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>ICE is about finding all/many paths for the media, e.g. =
with the help of<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>TURN servers.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>Those paths are not over ONE =
IPv4 network, over ONE IPv6 network or EXACTLY<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>ONE OF =
EACH.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>If =
fact, it is more common that you have several IPv4 networks =
paths.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Now that we have network provided TURN servers, you only =
ask for Allocation<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>once (contrary to application provided TURN servers, where =
you can be<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>directed to Allocate several times.) and thus we need all =
relay addresses in<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>one allocation request.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>Wasn't that the reason dual =
allocation was requested? The need for multiple<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>allocation is =
stronger!<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Please address this, e.g. like below (seems you are almost =
there).<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>/Karl<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>******************* Previous =
*******************<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Allowing a turn allocation to return multiple relayed =
transport addresses,<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>beyond ONE IPv4 and ONE IPv6 (which may sit on the same or =
on different<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>interfaces/network segments), seems like very small step =
now when the dual<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>allocation was put in place in this draft. We certainly =
need it (some<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>reasons below) if TURN is going to be used where needed and =
we cannot wait<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>for any additional draft.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>Seems like it is sufficient to =
extent this table (found in draft 14) with 3<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>new values (as =
shown):<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>16.=C2=A0 STUN Attributes<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>=C2=A0=C2=A0 This STUN extension =
defines the following attributes:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>=C2=A0=C2=A0=C2=A0=C2=A0 0x000C: =
CHANNEL-NUMBER<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0=C2=A0=C2=A0 0x000D: =
LIFETIME<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0=C2=A0=C2=A0 0x0010: Reserved (was =
BANDWIDTH)<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0=C2=A0=C2=A0 0x0012: =
XOR-PEER-ADDRESS<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0=C2=A0=C2=A0 0x0013: =
DATA<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0=C2=A0=C2=A0 0x0016: =
XOR-RELAYED-ADDRESS<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0=C2=A0=C2=A0 0x0017: =
REQUESTED-ADDRESS-FAMILY<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>=C2=A0=C2=A0=C2=A0=C2=A0 0x0018: =
EVEN-PORT<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0=C2=A0=C2=A0 0x0019: =
REQUESTED-TRANSPORT<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0=C2=A0=C2=A0 0x001A: =
DONT-FRAGMENT<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0=C2=A0=C2=A0 0x0021: Reserved (was =
TIMER-VAL)<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0=C2=A0=C2=A0 0x0022: =
RESERVATION-TOKEN<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0=C2=A0=C2=A0 TBD-CA: =
ADDITIONAL-ADDRESS-FAMILY<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>ADDITIONAL-ADDRESS-ALL<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>ADDITIONAL-ADDRESS-ALLV4<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>ADDITIONAL-ADDRESS-ALLV6<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>=C2=A0=C2=A0=C2=A0=C2=A0 TBD-CA: =
ADDRESS-ERROR-CODE<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=C2=A0=C2=A0=C2=A0=C2=A0 TBD-CA: =
ICMP<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Actually, browsing through the draft for =
ADDITIONAL-ADDRESS-FAMILY, very<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>little text seems to be added =
for generalization to=C2=A0 =
ADDITIONAL-ADDRESS-xxx.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>Almost everything applies to =
ADDITIONAL-ADDRESS-xxx and can be reused.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>ADDITIONAL-ADDRESS-ALL should be =
the default for any modern TURN client.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>Check! - We need this =
now.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>Thanks,<o:p></o:p></p><p =
class=3DMsoPlainText>Karl<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'><o=
:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'><o=
:p>&nbsp;</o:p></span></p></div></div></div></body></html>
------=_NextPart_000_048C_01D3C22B.8662CAC0--


From nobody Tue Mar 27 07:28:18 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tram@ietf.org
Delivered-To: tram@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E71212E88B; Tue, 27 Mar 2018 07:28:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: tram@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.76.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152216088538.5180.2169165990264943156@ietfa.amsl.com>
Date: Tue, 27 Mar 2018 07:28:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/QCUe4VnJMwhY9jYsfgS0jMVOQjo>
Subject: [tram] I-D Action: draft-ietf-tram-turnbis-16.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Mar 2018 14:28:16 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the TURN Revised and Modernized WG of the IETF.

        Title           : Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)
        Authors         : Tirumaleswar Reddy
                          Alan Johnston
                          Philip Matthews
                          Jonathan Rosenberg
	Filename        : draft-ietf-tram-turnbis-16.txt
	Pages           : 84
	Date            : 2018-03-27

Abstract:
   If a host is located behind a NAT, then in certain situations it can
   be impossible for that host to communicate directly with other hosts
   (peers).  In these situations, it is necessary for the host to use
   the services of an intermediate node that acts as a communication
   relay.  This specification defines a protocol, called TURN (Traversal
   Using Relays around NAT), that allows the host to control the
   operation of the relay and to exchange packets with its peers using
   the relay.  TURN differs from some other relay control protocols in
   that it allows a client to communicate with multiple peers using a
   single relay address.

   The TURN protocol was designed to be used as part of the ICE
   (Interactive Connectivity Establishment) approach to NAT traversal,
   though it also can be used without ICE.

   This document obsoletes RFC 5766 and RFC 6156.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tram-turnbis/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-tram-turnbis-16
https://datatracker.ietf.org/doc/html/draft-ietf-tram-turnbis-16

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-tram-turnbis-16


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From nobody Tue Mar 27 07:30:20 2018
Return-Path: <TirumaleswarReddy_Konda@mcafee.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 235C812DA27 for <tram@ietfa.amsl.com>; Tue, 27 Mar 2018 07:30:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level: 
X-Spam-Status: No, score=-4.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mcafee.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0pd7TsCDKifJ for <tram@ietfa.amsl.com>; Tue, 27 Mar 2018 07:30:18 -0700 (PDT)
Received: from DNVWSMAILOUT1.mcafee.com (dnvwsmailout1.mcafee.com [161.69.31.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 435D4127369 for <tram@ietf.org>; Tue, 27 Mar 2018 07:30:18 -0700 (PDT)
X-NAI-Header: Modified by McAfee Email Gateway (5500)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mcafee.com; s=s_mcafee; t=1522161017; h=From: To:CC:Subject:Thread-Topic:Thread-Index:Date: Message-ID:References:In-Reply-To:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: dlp-product:dlp-version:dlp-reaction:authentication-results: x-originating-ip:x-ms-publictraffictype:x-microsoft-exchange-diagnostics: x-ms-exchange-antispam-srfa-diagnostics:x-ms-office365-filtering-correlation-id: x-microsoft-antispam:x-ms-traffictypediagnostic: x-microsoft-antispam-prvs:x-exchange-antispam-report-test: x-exchange-antispam-report-cfa-test:x-forefront-prvs: x-forefront-antispam-report:received-spf:x-microsoft-antispam-message-info: spamdiagnosticoutput:spamdiagnosticmetadata: Content-Type:Content-Transfer-Encoding:MIME-Version: X-MS-Exchange-CrossTenant-Network-Message-Id: X-MS-Exchange-CrossTenant-originalarrivaltime: X-MS-Exchange-CrossTenant-fromentityheader: X-MS-Exchange-CrossTenant-id:X-MS-Exchange-Transport-CrossTenantHeadersStamped: X-OriginatorOrg:X-NAI-Spam-Flag:X-NAI-Spam-Threshold: X-NAI-Spam-Score:X-NAI-Spam-Version; bh=4 jipU2tcZY7VRp92nTA9NAbzzKDZhMctR+nouKAeoo U=; b=g9NXy+M1+t0fyW7CAovcCebfBw9cI3dk5fi9rtvDZ/J/ 0lDpMfqOMb7wzZXxRIlGTbwJMqdJmlgFRzTaBQs3ZkTgpAVLfg nLmIjK78fLm+qnLRwe3MqUMzuWZAbGZDebaXAkQsQKJmaoV934 /YYWicZtytHDM9HJse7tqMLG8IU=
Received: from DNVEXAPP1N05.corpzone.internalzone.com (unknown [10.44.48.89]) by DNVWSMAILOUT1.mcafee.com with smtp (TLS: TLSv1/SSLv3,256bits,ECDHE-RSA-AES256-SHA384) id 31de_4c4d_b8cfbe2d_fb26_4abb_99a6_755a647f7f3d; Tue, 27 Mar 2018 09:30:16 -0500
Received: from DNVEXUSR1N12.corpzone.internalzone.com (10.44.48.85) by DNVEXAPP1N05.corpzone.internalzone.com (10.44.48.89) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 27 Mar 2018 08:29:56 -0600
Received: from DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) by DNVEXUSR1N12.corpzone.internalzone.com (10.44.48.85) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 27 Mar 2018 08:29:55 -0600
Received: from DNVO365EDGE1.corpzone.internalzone.com (10.44.176.66) by DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) with Microsoft SMTP Server (TLS) id 15.0.1347.2 via Frontend Transport; Tue, 27 Mar 2018 08:29:55 -0600
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (10.44.176.241) by edge.mcafee.com (10.44.176.66) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 27 Mar 2018 08:29:53 -0600
Received: from BN6PR16MB1425.namprd16.prod.outlook.com (10.172.207.19) by BN6PR16MB1524.namprd16.prod.outlook.com (10.172.208.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.609.10; Tue, 27 Mar 2018 14:29:54 +0000
Received: from BN6PR16MB1425.namprd16.prod.outlook.com ([fe80::b9d0:eb7e:fb41:137d]) by BN6PR16MB1425.namprd16.prod.outlook.com ([fe80::b9d0:eb7e:fb41:137d%2]) with mapi id 15.20.0609.012; Tue, 27 Mar 2018 14:29:54 +0000
From: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>
To: Noriyuki Torii <torii0573@gmail.com>
CC: "tram@ietf.org" <tram@ietf.org>
Thread-Topic: [tram] I-D Action: draft-ietf-tram-turnbis-15.txt
Thread-Index: AQHTvpVCIExz03qGwU2I9I0I/uh+eqPVrxXQgAEO0ACADXSKkA==
Date: Tue, 27 Mar 2018 14:29:54 +0000
Message-ID: <BN6PR16MB1425458B1903641D0965E7A5EAAC0@BN6PR16MB1425.namprd16.prod.outlook.com>
References: <152136260256.18150.10551009018364033510@ietfa.amsl.com> <BN6PR16MB1425D61744AC7480972C800AEAD50@BN6PR16MB1425.namprd16.prod.outlook.com> <CABEjbR+uJQKegDWSncE5yM1sp=E+d0sHFdydhiGfyYS2U2n7Nw@mail.gmail.com>
In-Reply-To: <CABEjbR+uJQKegDWSncE5yM1sp=E+d0sHFdydhiGfyYS2U2n7Nw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 11.0.200.100
dlp-reaction: no-action
authentication-results: spf=none (sender IP is ) smtp.mailfrom=TirumaleswarReddy_Konda@McAfee.com; 
x-originating-ip: [103.245.47.20]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR16MB1524; 7:G/IHcYM+D3+vsodzUqwNRuska4Lu0XLp9FV9/5Pkvce0UAnj1vf1iE7Kd+dI29mUSAB/OaJBnn5JibaV6Kx1/c2/kvduCFf4FC/GHBsubjOuMQp/xfhVcbx5C1XqwZzlc6CGjDMgT6op4YMCpIbCIG2tSAz7myjsxpgMbnwwj5s7YQiKpcMdEbeK+uiVUtHWRMlehjwZjMOgY0Kj9N4YPxGPp71Rzs2G3TPGB6ABwEBKGCTBq2umiRfZn0vvgZLr
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: c40c5a71-f702-497e-1d73-08d593ef3550
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BN6PR16MB1524; 
x-ms-traffictypediagnostic: BN6PR16MB1524:
x-microsoft-antispam-prvs: <BN6PR16MB15247AB254169A632479A6F7EAAC0@BN6PR16MB1524.namprd16.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105)(85827821059158)(123452027830198); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3231221)(944501327)(52105095)(93006095)(93001095)(10201501046)(3002001)(6041310)(20161123558120)(20161123564045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(6072148)(201708071742011); SRVR:BN6PR16MB1524; BCL:0; PCL:0; RULEID:; SRVR:BN6PR16MB1524; 
x-forefront-prvs: 0624A2429E
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39380400002)(366004)(39860400002)(396003)(376002)(346002)(377424004)(13464003)(32952001)(189003)(199004)(11346002)(305945005)(25786009)(7736002)(6306002)(39060400002)(86362001)(14454004)(26005)(7696005)(8936002)(55016002)(2906002)(74316002)(476003)(4326008)(33656002)(68736007)(966005)(316002)(72206003)(446003)(2900100001)(478600001)(6246003)(80792005)(76176011)(6506007)(6916009)(59450400001)(97736004)(3660700001)(6116002)(3846002)(66066001)(102836004)(105586002)(9686003)(8676002)(53936002)(551544002)(6436002)(486005)(186003)(486005)(106356001)(99286004)(53546011)(81166006)(81156014)(1411001)(5250100002)(229853002)(5660300001)(3280700002)(85282002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR16MB1524; H:BN6PR16MB1425.namprd16.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: McAfee.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: yeLYQJs7fw1yUh036VmEhsFahFh8Mo23dOFYn4KTEx4JpnqeO4gFUDrMLPn4DEBWWWUcA6Py9Ok/uFq2zY+Wqb4dudYpFF1Sj7UgFWxE8+P8MxsvO1IggqHLo3l9xMyjNrNDGzaNTPF36tt/sMrb4+lGKbS0IZAw7SU07d2F519GrZGedoax5XnkpR6md3yTeK0nTuRXfeZceJLrk82Ubx8lzzQm1w9LkQ3yWVdxMzVxOZYtlWbKIbNTJ4BDjEAmBiWk0neMzuDWC5cdm1FawtJxDJisOmulOO1dnhcjuX+CKa1cB9oxPAvlifbVTtvrVFIpMP+gIc17/qyUJF6lGQ==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: c40c5a71-f702-497e-1d73-08d593ef3550
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Mar 2018 14:29:54.2140 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4943e38c-6dd4-428c-886d-24932bc2d5de
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR16MB1524
X-OriginatorOrg: mcafee.com
X-NAI-Spam-Flag: NO
X-NAI-Spam-Threshold: 15
X-NAI-Spam-Score: 0
X-NAI-Spam-Version: 2.3.0.9418 : core <6251> : inlines <6521> : streams <1782418> : uri <2615756>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/DzfCh0EodaIQni-satdUB03e-c0>
Subject: Re: [tram] I-D Action: draft-ietf-tram-turnbis-15.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Mar 2018 14:30:20 -0000

VGhhbmtzIE5vcml5dWtpIFRvcmlpLCBhZGRyZXNzZWQgdGhlIGNvbW1lbnRzIGluIHRoZSBuZXcg
cmV2aXNpb24uDQoNCkNoZWVycywNCi1UaXJ1DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS0NCj4gRnJvbTogTm9yaXl1a2kgVG9yaWkgW21haWx0bzp0b3JpaTA1NzNAZ21haWwuY29tXQ0K
PiBTZW50OiBNb25kYXksIE1hcmNoIDE5LCAyMDE4IDY6MjkgQU0NCj4gVG86IEtvbmRhLCBUaXJ1
bWFsZXN3YXIgUmVkZHkgPFRpcnVtYWxlc3dhclJlZGR5X0tvbmRhQE1jQWZlZS5jb20+DQo+IENj
OiB0cmFtQGlldGYub3JnDQo+IFN1YmplY3Q6IFJlOiBbdHJhbV0gSS1EIEFjdGlvbjogZHJhZnQt
aWV0Zi10cmFtLXR1cm5iaXMtMTUudHh0DQo+IA0KPiBIaSBUaXJ1LA0KPiANCj4gSSBjaGVja2Vk
IHVwZGF0ZWQgSS1EIGFuZCBmb3VuZCBzb21lIG1vcmUgcG9pbnRzIGluIHNlY3Rpb24gMTIgYmVs
b3cuDQo+IA0KPiA+ICAgICAgMHg0MDAwIHRocm91Z2ggMHg0RkZGOiBUaGVzZSB2YWx1ZXMgYXJl
IHRoZSBhbGxvd2VkIGNoYW5uZWwNCj4gPiAgICAgIG51bWJlcnMgKDE2LDM4NCBwb3NzaWJsZSB2
YWx1ZXMpLg0KPiAgICAgICAgICAgICAgICAgfn5+fn5+DQo+IFRoaXMgdmFsdWUgYWxzbyBuZWVk
IHRvIGJlIGFtZW5kZWQgdG8gNCwwOTYuDQo+IA0KPiA+ICAgICAgMHg4MDAwIHRocm91Z2ggMHhG
RkZGOiBUaGVzZSB2YWx1ZXMgYXJlIHJlc2VydmVkIGZvciBmdXR1cmUgdXNlLg0KPiANCj4gVGhp
cyBsaW5lIGNhbiBiZSByZW1vdmVkIG5vdyBiZWNhdXNlIHRoZSBwcmV2aW91cyBzZW50ZW5jZSBp
bXBseSBpdCwgdG9vLg0KPiANCj4gQW5kIGFsc28sIEkgdGhpbmsgaXQgbWF5IGJlIHByZWZlcmFi
bGUgaWYgdGhlIGZvbGxvd2luZyBwYXJhZ3JhcGggaXMgdXBkYXRlZCBzbyBhcw0KPiB0byBhbGln
bm1lbnQgdG8gUkZDIDc5ODMuDQo+IA0KPiA+ICAgQmVjYXVzZSBvZiB0aGlzIGRpdmlzaW9uLCBD
aGFubmVsRGF0YSBtZXNzYWdlcyBjYW4gYmUgZGlzdGluZ3Vpc2hlZA0KPiA+ICAgZnJvbSBTVFVO
LWZvcm1hdHRlZCBtZXNzYWdlcyAoZS5nLiwgQWxsb2NhdGUgcmVxdWVzdCwgU2VuZA0KPiA+ICAg
aW5kaWNhdGlvbiwgZXRjLikgYnkgZXhhbWluaW5nIHRoZSBmaXJzdCB0d28gYml0cyBvZiB0aGUg
bWVzc2FnZToNCj4gPg0KPiA+ICAgICAgMGIwMDogU1RVTi1mb3JtYXR0ZWQgbWVzc2FnZSAoc2lu
Y2UgdGhlIGZpcnN0IHR3byBiaXRzIG9mIGEgU1RVTi0NCj4gPiAgICAgIGZvcm1hdHRlZCBtZXNz
YWdlIGFyZSBhbHdheXMgemVybykuDQo+ID4NCj4gPiAgICAgIDBiMDE6IENoYW5uZWxEYXRhIG1l
c3NhZ2UgKHNpbmNlIHRoZSBjaGFubmVsIG51bWJlciBpcyB0aGUgZmlyc3QNCj4gPiAgICAgIGZp
ZWxkIGluIHRoZSBDaGFubmVsRGF0YSBtZXNzYWdlIGFuZCBjaGFubmVsIG51bWJlcnMgZmFsbCBp
biB0aGUNCj4gPiAgICAgIHJhbmdlIDB4NDAwMCAtIDB4N0ZGRikuDQo+ID4NCj4gPiAgICAgIDBi
MTA6IFJlc2VydmVkDQo+ID4NCj4gPiAgICAgIDBiMTE6IFJlc2VydmVkDQo+ID4NCj4gPiAgIFRo
ZSByZXNlcnZlZCB2YWx1ZXMgbWF5IGJlIHVzZWQgaW4gdGhlIGZ1dHVyZSB0byBleHRlbmQgdGhl
IHJhbmdlIG9mDQo+ID4gICBjaGFubmVsIG51bWJlcnMuICBUaHVzLCBhbiBpbXBsZW1lbnRhdGlv
biBNVVNUIE5PVCBhc3N1bWUgdGhhdCBhIFRVUk4NCj4gPiAgIG1lc3NhZ2UgYWx3YXlzIHN0YXJ0
cyB3aXRoIGEgMCBiaXQuDQo+IA0KPiBJIGd1ZXNzIGl0IGNvdWxkIGJlDQo+IA0KPiAgICAgQWNj
b3JkaW5nIHRvIFJGQyA3OTgzLCBDaGFubmVsRGF0YSBtZXNzYWdlcyBjYW4gYmUgZGlzdGluZ3Vp
c2hlZA0KPiAgICAgZnJvbSBvdGhlciBtdWx0aXBsZXhlZCBwcm90b2NvbHMgYnkgZXhhbWluaW5n
IHRoZSBmaXJzdCBieXRlIG9mIHRoZQ0KPiAgICAgbWVzc2FnZToNCj4gDQo+ICAgICAgICAgICBb
MC4uM10gIFNUVU4NCj4gICAgICAgICBbMTYuLjE5XSAgWlJUUA0KPiAgICAgICAgIFsyMC4uNjNd
ICBEVExTDQo+ICAgICAgICAgWzY0Li43OV0gIFRVUk4gQ2hhbm5lbA0KPiAgICAgICBbMTI4Li4x
OTFdICBSVFAvUlRDUA0KPiAgICAgICAgICAgb3RoZXJzICByZXNlcnZlZCwgTVVTVCBiZSBkcm9w
cGVkIGFuZCBhbiBhbGVydCBNQVkgYmUgbG9nZ2VkDQo+IA0KPiAgICAgUmVzZXJ2ZWQgdmFsdWVz
IG1heSBiZSB1c2VkIGluIHRoZSBmdXR1cmUgYnkgb3RoZXIgcHJvdG9jb2xzLg0KPiAgICAgVGh1
cywgYW4gaW1wbGVtZW50YXRpb24gTVVTVCBjb21wbHkgdGhlIGRpc2NyaW1pbmF0aW9uIGFib3Zl
Lg0KPiANCj4gDQo+IEZpbmFsbHksIGluIHNlY3Rpb24gMTgsIHRoZSBleGFtcGxlIFJlZnJlc2gg
cmVxdWVzdCBpbiB0aGUgZGlhZ3JhbSBvZiB0aGUgcGFnZSA2Nw0KPiBkb2Vzbid0IGhhdmUgdGhl
IFBBU1NXT1JELUFMR09SSVRITVMgYXR0cmlidXRlIG5ldmVydGhlbGVzcyBpdCBoYXMgdGhlDQo+
IFBBU1NXT1JELUFMR09SSVRITSBhdHRyaWJ1dGVzLCBhbHNvIG5lZWQgdG8gYmUgZml4ZWQuDQo+
IA0KPiBSZWdhcmRzLA0KPiBOb3JpeXVraSBUb3JpaQ0KPiANCj4gLS0tLS0tLS0tLS0tLS0tLQ0K
PiANCj4gMjAxOC0wMy0xOCAxNzo1MCBHTVQrMDk6MDAgS29uZGEsIFRpcnVtYWxlc3dhciBSZWRk
eQ0KPiA8VGlydW1hbGVzd2FyUmVkZHlfS29uZGFAbWNhZmVlLmNvbT46DQo+ID4gVGhpcyByZXZp
c2lvbiBhZGRyZXNzZXMgY29tbWVudHMgZnJvbSBNYXJrLCBLYXJsIGFuZCBOb3JpeXVraSBUb3Jp
aS4NCj4gPg0KPiA+IC1UaXJ1DQo+ID4NCj4gPj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0N
Cj4gPj4gRnJvbTogdHJhbSBbbWFpbHRvOnRyYW0tYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxm
IE9mIGludGVybmV0LQ0KPiA+PiBkcmFmdHNAaWV0Zi5vcmcNCj4gPj4gU2VudDogU3VuZGF5LCBN
YXJjaCAxOCwgMjAxOCA4OjQzIEFNDQo+ID4+IFRvOiBpLWQtYW5ub3VuY2VAaWV0Zi5vcmcNCj4g
Pj4gQ2M6IHRyYW1AaWV0Zi5vcmcNCj4gPj4gU3ViamVjdDogW3RyYW1dIEktRCBBY3Rpb246IGRy
YWZ0LWlldGYtdHJhbS10dXJuYmlzLTE1LnR4dA0KPiA+Pg0KPiA+Pg0KPiA+PiBBIE5ldyBJbnRl
cm5ldC1EcmFmdCBpcyBhdmFpbGFibGUgZnJvbSB0aGUgb24tbGluZSBJbnRlcm5ldC1EcmFmdHMg
ZGlyZWN0b3JpZXMuDQo+ID4+IFRoaXMgZHJhZnQgaXMgYSB3b3JrIGl0ZW0gb2YgdGhlIFRVUk4g
UmV2aXNlZCBhbmQgTW9kZXJuaXplZCBXRyBvZg0KPiA+PiB0aGUgSUVURi4NCj4gPj4NCj4gPj4g
ICAgICAgICBUaXRsZSAgICAgICAgICAgOiBUcmF2ZXJzYWwgVXNpbmcgUmVsYXlzIGFyb3VuZCBO
QVQgKFRVUk4pOiBSZWxheSBFeHRlbnNpb25zDQo+ID4+IHRvIFNlc3Npb24gVHJhdmVyc2FsIFV0
aWxpdGllcyBmb3IgTkFUIChTVFVOKQ0KPiA+PiAgICAgICAgIEF1dGhvcnMgICAgICAgICA6IFRp
cnVtYWxlc3dhciBSZWRkeQ0KPiA+PiAgICAgICAgICAgICAgICAgICAgICAgICAgIEFsYW4gSm9o
bnN0b24NCj4gPj4gICAgICAgICAgICAgICAgICAgICAgICAgICBQaGlsaXAgTWF0dGhld3MNCj4g
Pj4gICAgICAgICAgICAgICAgICAgICAgICAgICBKb25hdGhhbiBSb3NlbmJlcmcNCj4gPj4gICAg
ICAgRmlsZW5hbWUgICAgICAgIDogZHJhZnQtaWV0Zi10cmFtLXR1cm5iaXMtMTUudHh0DQo+ID4+
ICAgICAgIFBhZ2VzICAgICAgICAgICA6IDg0DQo+ID4+ICAgICAgIERhdGUgICAgICAgICAgICA6
IDIwMTgtMDMtMTgNCj4gPj4NCj4gPj4gQWJzdHJhY3Q6DQo+ID4+ICAgIElmIGEgaG9zdCBpcyBs
b2NhdGVkIGJlaGluZCBhIE5BVCwgdGhlbiBpbiBjZXJ0YWluIHNpdHVhdGlvbnMgaXQgY2FuDQo+
ID4+ICAgIGJlIGltcG9zc2libGUgZm9yIHRoYXQgaG9zdCB0byBjb21tdW5pY2F0ZSBkaXJlY3Rs
eSB3aXRoIG90aGVyIGhvc3RzDQo+ID4+ICAgIChwZWVycykuICBJbiB0aGVzZSBzaXR1YXRpb25z
LCBpdCBpcyBuZWNlc3NhcnkgZm9yIHRoZSBob3N0IHRvIHVzZQ0KPiA+PiAgICB0aGUgc2Vydmlj
ZXMgb2YgYW4gaW50ZXJtZWRpYXRlIG5vZGUgdGhhdCBhY3RzIGFzIGEgY29tbXVuaWNhdGlvbg0K
PiA+PiAgICByZWxheS4gIFRoaXMgc3BlY2lmaWNhdGlvbiBkZWZpbmVzIGEgcHJvdG9jb2wsIGNh
bGxlZCBUVVJOIChUcmF2ZXJzYWwNCj4gPj4gICAgVXNpbmcgUmVsYXlzIGFyb3VuZCBOQVQpLCB0
aGF0IGFsbG93cyB0aGUgaG9zdCB0byBjb250cm9sIHRoZQ0KPiA+PiAgICBvcGVyYXRpb24gb2Yg
dGhlIHJlbGF5IGFuZCB0byBleGNoYW5nZSBwYWNrZXRzIHdpdGggaXRzIHBlZXJzIHVzaW5nDQo+
ID4+ICAgIHRoZSByZWxheS4gIFRVUk4gZGlmZmVycyBmcm9tIHNvbWUgb3RoZXIgcmVsYXkgY29u
dHJvbCBwcm90b2NvbHMgaW4NCj4gPj4gICAgdGhhdCBpdCBhbGxvd3MgYSBjbGllbnQgdG8gY29t
bXVuaWNhdGUgd2l0aCBtdWx0aXBsZSBwZWVycyB1c2luZyBhDQo+ID4+ICAgIHNpbmdsZSByZWxh
eSBhZGRyZXNzLg0KPiA+Pg0KPiA+PiAgICBUaGUgVFVSTiBwcm90b2NvbCB3YXMgZGVzaWduZWQg
dG8gYmUgdXNlZCBhcyBwYXJ0IG9mIHRoZSBJQ0UNCj4gPj4gICAgKEludGVyYWN0aXZlIENvbm5l
Y3Rpdml0eSBFc3RhYmxpc2htZW50KSBhcHByb2FjaCB0byBOQVQgdHJhdmVyc2FsLA0KPiA+PiAg
ICB0aG91Z2ggaXQgYWxzbyBjYW4gYmUgdXNlZCB3aXRob3V0IElDRS4NCj4gPj4NCj4gPj4gICAg
VGhpcyBkb2N1bWVudCBvYnNvbGV0ZXMgUkZDIDU3NjYgYW5kIFJGQyA2MTU2Lg0KPiA+Pg0KPiA+
Pg0KPiA+PiBUaGUgSUVURiBkYXRhdHJhY2tlciBzdGF0dXMgcGFnZSBmb3IgdGhpcyBkcmFmdCBp
czoNCj4gPj4gaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi10cmFt
LXR1cm5iaXMvDQo+ID4+DQo+ID4+IFRoZXJlIGFyZSBhbHNvIGh0bWxpemVkIHZlcnNpb25zIGF2
YWlsYWJsZSBhdDoNCj4gPj4gaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYt
dHJhbS10dXJuYmlzLTE1DQo+ID4+IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2h0
bWwvZHJhZnQtaWV0Zi10cmFtLXR1cm5iaXMtMTUNCj4gPj4NCj4gPj4gQSBkaWZmIGZyb20gdGhl
IHByZXZpb3VzIHZlcnNpb24gaXMgYXZhaWxhYmxlIGF0Og0KPiA+PiBodHRwczovL3d3dy5pZXRm
Lm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtaWV0Zi10cmFtLXR1cm5iaXMtMTUNCj4gPj4NCj4gPj4N
Cj4gPj4gUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBtaW51dGVzIGZy
b20gdGhlIHRpbWUgb2YNCj4gPj4gc3VibWlzc2lvbiB1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lv
biBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLg0KPiA+Pg0KPiA+PiBJ
bnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZhaWxhYmxlIGJ5IGFub255bW91cyBGVFAgYXQ6DQo+
ID4+IGZ0cDovL2Z0cC5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvDQo+ID4+DQo+ID4+IF9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4+IHRyYW0gbWFp
bGluZyBsaXN0DQo+ID4+IHRyYW1AaWV0Zi5vcmcNCj4gPj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby90cmFtDQo+ID4NCj4gPiBfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXw0KPiA+IHRyYW0gbWFpbGluZyBsaXN0DQo+ID4gdHJhbUBp
ZXRmLm9yZw0KPiA+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdHJhbQ0K


From nobody Tue Mar 27 23:43:22 2018
Return-Path: <torii0573@gmail.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB4861200E5 for <tram@ietfa.amsl.com>; Tue, 27 Mar 2018 23:43:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y5iAtzHb5Jsr for <tram@ietfa.amsl.com>; Tue, 27 Mar 2018 23:43:19 -0700 (PDT)
Received: from mail-ot0-x234.google.com (mail-ot0-x234.google.com [IPv6:2607:f8b0:4003:c0f::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AF461200A0 for <tram@ietf.org>; Tue, 27 Mar 2018 23:43:19 -0700 (PDT)
Received: by mail-ot0-x234.google.com with SMTP id x6-v6so1494481otg.11 for <tram@ietf.org>; Tue, 27 Mar 2018 23:43:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lm3N/RN4CrI2kLvuL7nwplgYBrQ0vHIA4VM0rT+/Nq0=; b=pz1EsDBpbIOGTAEPx834KoRZKkuKo0IjO+JQYdG8uq0a4TWyLr4mdg5Fxvu5Tw9ify OczQ4KXows2e48XST39wOIjBSZ7Ra4CiR+Is5CKWpVEitnfqnsXuVvPDlPladD9rQmZH 9Mv3OUa+McnC959q7cDVWyySIiuO3KBqnchIn4dXy0CXrNJVmy18rhbaWWnU0vQFGicw rjIFVtr3PgEFtgy1zKAJLC8muldbwhzPVqVKbkeTdWFOZ9RCmDvHRujeDVa58w+cXnKC EZu6zuoybpdWQTax8ZVGV2Av9aynKMN/Rq8dZsGJjHF3VNtppjzL9pZDqdceNN16RVCo 8pww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=lm3N/RN4CrI2kLvuL7nwplgYBrQ0vHIA4VM0rT+/Nq0=; b=txbUeNhFuA+3al64gJovI4Qbg2J+14+EKj9u7sW7yowr5e9Y4A3uEtDf8x/bYeTMTk 35rNaRGv+RUTz3omr4MuZexpNDWGrkvB2cnG8jnLBLcUeyEsW3YyAsNjB+C3fNNkMgTz CPHtEgnBbl0Mt1jyJNB4nvzsYEH/Rd08nRtfGHE4O00eIdJMkgWYQ8UjqN+SFxPzFXjw L353K6ShPenAvudISrfNtw53y55fCqJVhds5TcCYKSYxX4aHbRiubwsggYC2Qw8P680W FejSDiQotvqcFMmtAiFYeLPmo6y538JzyD1E/6RdhHoBz2HD3N8VkwfmawktsmbgZ1LF Z7BQ==
X-Gm-Message-State: ALQs6tC846ghb+CJQpQNgTdDDQZwyRI9k02TPxNQFMsCaiy8FNPNGOiQ nKD2AsCSGNwKGuW8GavCoV+IX4dsVoV3c57N8BI=
X-Google-Smtp-Source: AIpwx4/wUkOKeUf79oleKot02tmeaXXrD2Oavxv7D5quZ3e2N+FZTn/claEw/dRpUkDV8i21zYmbRCLSxl8f3GNYV54=
X-Received: by 2002:a9d:cee:: with SMTP id o43-v6mr1344224otd.293.1522219398466;  Tue, 27 Mar 2018 23:43:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.115.209 with HTTP; Tue, 27 Mar 2018 23:43:18 -0700 (PDT)
In-Reply-To: <BN6PR16MB1425458B1903641D0965E7A5EAAC0@BN6PR16MB1425.namprd16.prod.outlook.com>
References: <152136260256.18150.10551009018364033510@ietfa.amsl.com> <BN6PR16MB1425D61744AC7480972C800AEAD50@BN6PR16MB1425.namprd16.prod.outlook.com> <CABEjbR+uJQKegDWSncE5yM1sp=E+d0sHFdydhiGfyYS2U2n7Nw@mail.gmail.com> <BN6PR16MB1425458B1903641D0965E7A5EAAC0@BN6PR16MB1425.namprd16.prod.outlook.com>
From: Noriyuki Torii <torii0573@gmail.com>
Date: Wed, 28 Mar 2018 15:43:18 +0900
Message-ID: <CABEjbRJh3GhA++iVp-Jt3e-oc3405NK4vvfXtpgY+dEbpSHWdw@mail.gmail.com>
To: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@mcafee.com>
Cc: "tram@ietf.org" <tram@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/ymnPEx_NGDXHRVs1AE1g3JKGTRU>
Subject: Re: [tram] I-D Action: draft-ietf-tram-turnbis-15.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Mar 2018 06:43:21 -0000

Hi Tiru,

Thank you for the update.
I hesitate to say but I noticed I've missed one more point.

That is the first paragraph of section 12.6

>   The receiver of the ChannelData message uses the first two bits to
>   distinguish it from STUN-formatted messages, as described above.  If
>   the message uses a value in the reserved range (0x8000 through
>   0xFFFF), then the message is silently discarded.

Apparently, above paragraph also need update to align with RFC7983 and
also last update of section 12.

Regards,
Noriyuki Torii


2018-03-27 23:29 GMT+09:00 Konda, Tirumaleswar Reddy
<TirumaleswarReddy_Konda@mcafee.com>:
> Thanks Noriyuki Torii, addressed the comments in the new revision.
>
> Cheers,
> -Tiru
>
>> -----Original Message-----
>> From: Noriyuki Torii [mailto:torii0573@gmail.com]
>> Sent: Monday, March 19, 2018 6:29 AM
>> To: Konda, Tirumaleswar Reddy <TirumaleswarReddy_Konda@McAfee.com>
>> Cc: tram@ietf.org
>> Subject: Re: [tram] I-D Action: draft-ietf-tram-turnbis-15.txt
>>
>> Hi Tiru,
>>
>> I checked updated I-D and found some more points in section 12 below.
>>
>> >      0x4000 through 0x4FFF: These values are the allowed channel
>> >      numbers (16,384 possible values).
>>                 ~~~~~~
>> This value also need to be amended to 4,096.
>>
>> >      0x8000 through 0xFFFF: These values are reserved for future use.
>>
>> This line can be removed now because the previous sentence imply it, too.
>>
>> And also, I think it may be preferable if the following paragraph is updated so as
>> to alignment to RFC 7983.
>>
>> >   Because of this division, ChannelData messages can be distinguished
>> >   from STUN-formatted messages (e.g., Allocate request, Send
>> >   indication, etc.) by examining the first two bits of the message:
>> >
>> >      0b00: STUN-formatted message (since the first two bits of a STUN-
>> >      formatted message are always zero).
>> >
>> >      0b01: ChannelData message (since the channel number is the first
>> >      field in the ChannelData message and channel numbers fall in the
>> >      range 0x4000 - 0x7FFF).
>> >
>> >      0b10: Reserved
>> >
>> >      0b11: Reserved
>> >
>> >   The reserved values may be used in the future to extend the range of
>> >   channel numbers.  Thus, an implementation MUST NOT assume that a TURN
>> >   message always starts with a 0 bit.
>>
>> I guess it could be
>>
>>     According to RFC 7983, ChannelData messages can be distinguished
>>     from other multiplexed protocols by examining the first byte of the
>>     message:
>>
>>           [0..3]  STUN
>>         [16..19]  ZRTP
>>         [20..63]  DTLS
>>         [64..79]  TURN Channel
>>       [128..191]  RTP/RTCP
>>           others  reserved, MUST be dropped and an alert MAY be logged
>>
>>     Reserved values may be used in the future by other protocols.
>>     Thus, an implementation MUST comply the discrimination above.
>>
>>
>> Finally, in section 18, the example Refresh request in the diagram of the page 67
>> doesn't have the PASSWORD-ALGORITHMS attribute nevertheless it has the
>> PASSWORD-ALGORITHM attributes, also need to be fixed.
>>
>> Regards,
>> Noriyuki Torii
>>
>> ----------------
>>
>> 2018-03-18 17:50 GMT+09:00 Konda, Tirumaleswar Reddy
>> <TirumaleswarReddy_Konda@mcafee.com>:
>> > This revision addresses comments from Mark, Karl and Noriyuki Torii.
>> >
>> > -Tiru
>> >
>> >> -----Original Message-----
>> >> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of internet-
>> >> drafts@ietf.org
>> >> Sent: Sunday, March 18, 2018 8:43 AM
>> >> To: i-d-announce@ietf.org
>> >> Cc: tram@ietf.org
>> >> Subject: [tram] I-D Action: draft-ietf-tram-turnbis-15.txt
>> >>
>> >>
>> >> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> >> This draft is a work item of the TURN Revised and Modernized WG of
>> >> the IETF.
>> >>
>> >>         Title           : Traversal Using Relays around NAT (TURN): Relay Extensions
>> >> to Session Traversal Utilities for NAT (STUN)
>> >>         Authors         : Tirumaleswar Reddy
>> >>                           Alan Johnston
>> >>                           Philip Matthews
>> >>                           Jonathan Rosenberg
>> >>       Filename        : draft-ietf-tram-turnbis-15.txt
>> >>       Pages           : 84
>> >>       Date            : 2018-03-18
>> >>
>> >> Abstract:
>> >>    If a host is located behind a NAT, then in certain situations it can
>> >>    be impossible for that host to communicate directly with other hosts
>> >>    (peers).  In these situations, it is necessary for the host to use
>> >>    the services of an intermediate node that acts as a communication
>> >>    relay.  This specification defines a protocol, called TURN (Traversal
>> >>    Using Relays around NAT), that allows the host to control the
>> >>    operation of the relay and to exchange packets with its peers using
>> >>    the relay.  TURN differs from some other relay control protocols in
>> >>    that it allows a client to communicate with multiple peers using a
>> >>    single relay address.
>> >>
>> >>    The TURN protocol was designed to be used as part of the ICE
>> >>    (Interactive Connectivity Establishment) approach to NAT traversal,
>> >>    though it also can be used without ICE.
>> >>
>> >>    This document obsoletes RFC 5766 and RFC 6156.
>> >>
>> >>
>> >> The IETF datatracker status page for this draft is:
>> >> https://datatracker.ietf.org/doc/draft-ietf-tram-turnbis/
>> >>
>> >> There are also htmlized versions available at:
>> >> https://tools.ietf.org/html/draft-ietf-tram-turnbis-15
>> >> https://datatracker.ietf.org/doc/html/draft-ietf-tram-turnbis-15
>> >>
>> >> A diff from the previous version is available at:
>> >> https://www.ietf.org/rfcdiff?url2=draft-ietf-tram-turnbis-15
>> >>
>> >>
>> >> Please note that it may take a couple of minutes from the time of
>> >> submission until the htmlized version and diff are available at tools.ietf.org.
>> >>
>> >> Internet-Drafts are also available by anonymous FTP at:
>> >> ftp://ftp.ietf.org/internet-drafts/
>> >>
>> >> _______________________________________________
>> >> tram mailing list
>> >> tram@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/tram
>> >
>> > _______________________________________________
>> > tram mailing list
>> > tram@ietf.org
>> > https://www.ietf.org/mailman/listinfo/tram
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram


From nobody Thu Mar 29 19:45:41 2018
Return-Path: <worley@ariadne.com>
X-Original-To: tram@ietf.org
Delivered-To: tram@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 430CD1241F5; Thu, 29 Mar 2018 19:45:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dale Worley <worley@ariadne.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-tram-stunbis.all@ietf.org, ietf@ietf.org, tram@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.76.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152237792217.20556.13689609450529144296@ietfa.amsl.com>
Date: Thu, 29 Mar 2018 19:45:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/LMlZnAI2onP-KR7ndQy6PsD6K_k>
Subject: [tram] Genart telechat review of draft-ietf-tram-stunbis-16
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Mar 2018 02:45:22 -0000

Reviewer: Dale Worley
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft.  The General Area
Review Team (Gen-ART) reviews all IETF documents being processed by
the IESG for the IETF Chair.  Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at
<https://wiki.tools.ietf.org/area/gen/wiki/GenArtfaq>.

Document:  draft-ietf-tram-stunbis-16
Reviewer:  Dale R. Worley
Review Date:  2018-03-29
IETF LC End Date:  2018-02-20
IESG Telechat date:  2018-04-19

Summary:

       This draft is basically ready for publication, but has nits
       that should be fixed before publication.

The only interesting item concerns section 17.1, where the assignment
of meanings to bits in the "security feature set" value is different
from the assignment in -16.  This is either non-upward-compatible with
-16, or there is an error in either -16 or -17.

----------------------------------------------------------------------

There is an issue that shows up in several places:  The NAT may
forward the request using an IP family that is different from the IP
family that it received the request using.  This means that the
"source IP family of the request" may depend on whether one is
speaking of the client or the server.  The draft is cognizant of this,
and mentions its consequences in sections 6.3.3 and 12.  But this also
has consequences for ALTERNATE-SERVER:  Section 14.15 says "The IP
address family MUST be identical to that of the source IP address of
the request." even though that family might not be usable by the
client.  The draft doesn't seem to explicitly say that this comes from
address-switching by the NAT.  It would help if there was a
higher-level discussion of this matter, pointing to the various
consequences.

3.  Terminology

This section needs to be updated to reference RFC 8174, including
updating the paragraph (especially the final two lines) to read as
specified in RFC 8174:

      The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
      NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",
      "MAY", and "OPTIONAL" in this document are to be interpreted as
      described in BCP 14 [RFC2119] [RFC8174] when, and only when, they
      appear in all capitals, as shown here.

6.2.2.  Sending over TCP or TLS-over-TCP

   o  if multiplexing other application protocols over that port, has
      finished using that other protocol, and

The two clauses don't match in grammatical number.  This should be
either

   o  if multiplexing other application protocols over that port, has
      finished using those other protocols, and

or

   o  if multiplexing another application protocol over that port, has
      finished using that other protocol, and

9.2.4.  Receiving a Request

      *  If the request contains neither PASSWORD-ALGORITHMS nor
         PASSWORD- ALGORITHM, then the request is processed as though
         PASSWORD- ALGORITHM were MD5 (Note that if the original
         PASSWORD-ALGORITHMS attribute did not contain MD5, this will
         result in a 400 Bad Request in a later step below).

There are two places where s/PASSWORD- ALGORITHM/PASSWORD-ALGORITHM/.

14.3.  USERNAME

   The value of USERNAME is a variable-length value containing the
   authentication username.  It MUST contain a UTF-8 [RFC3629] encoded
   sequence of less than 509 bytes, and MUST have been processed using
   the OpaqueString profile [RFC8265].  A compliant implementation MUST
   be able to parse UTF-8 encoded sequence of less than 763.

The final "763" is grammatically incorrect.  I think you intend
s/763/763 bytes/, to parallel other items.

14.4.  USERHASH

   userhash = SHA-256(Opaque(username) ":" Opaque(realm))

I believe that this should be

   userhash = SHA-256(OpaqueString(username) ":" OpaqueString(realm))

14.5.  MESSAGE-INTEGRITY

   Petit-Huguenin, et al.  Expires September 6, 2018 [Page 40]

   Internet-Draft Session Traversal Utilities for NAT (STUN) March 2018

This bit of text appears as body text in the middle of page 40.

14.6.  MESSAGE-INTEGRITY-SHA256

   The MESSAGE-INTEGRITY-SHA256 attribute contains an HMAC-SHA256
   [RFC2104] of the STUN message.  The MESSAGE-INTEGRITY-SHA256
   attribute can be present in any STUN message type.  The MESSAGE-
   INTEGRITY-SHA256 attribute contains an initial portion of the HMAC-
   SHA-256 [RFC2104] of the STUN message.  The value will be at most 32
   bytes and MUST be a positive multiple of 4 bytes.  The HMAC MUST NOT
   be truncated below a minimum size of 16 bytes.  The value must be the
   full 32 bytes unless the STUN Usage explicitly specifies that
   truncation is allowed.  STUN Usages may specify a minimum length
   longer than 4 bytes.

This seems to be less clear than it could be.  (And my apologies, some
of the redundancy was my suggestion!)  Perhaps this is an improvement:

   The value will be at most 32 bytes, MUST be at least 16 bytes, and
   MUST be a multiple of 4 bytes.  The value must be the full 32 bytes
   unless the STUN Usage explicitly specifies that truncation is
   allowed.  STUN Usages may specify a minimum length longer than 16
   bytes.

17.1.  STUN Security Features Registry

   A STUN Security Feature set defines 24 bit as flags.

   IANA is requested to create a new registry containing the STUN
   Security Features that are protected by the bid down attack
   prevention mechanism described in section Section 9.2.1.

   The initial STUN Security Features are:

   Bit 0: Password algorithms
   Bit 1: Username anonymity
   Bit 2-23: Unassigned

Beware that the assignment of features to bits in the security feature
value has changed!  Bit numbers are assigned from the left/high-order
end -- see figure 2 in the draft.  So the *values* for these bits are:

0x400000   Bit 0: Password algorithms
0x200000   Bit 1: Username anonymity

But the values assigned in -15 were:

   0x000001: Password algorithms
   0x000002: Username anonymity

[END]



From nobody Sat Mar 31 15:50:57 2018
Return-Path: <juberti@google.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82D3F12420B for <tram@ietfa.amsl.com>; Sat, 31 Mar 2018 15:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level: 
X-Spam-Status: No, score=-2.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Njr-KkltwxEM for <tram@ietfa.amsl.com>; Sat, 31 Mar 2018 15:50:54 -0700 (PDT)
Received: from mail-ua0-x22c.google.com (mail-ua0-x22c.google.com [IPv6:2607:f8b0:400c:c08::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC4DF1200F1 for <tram@ietf.org>; Sat, 31 Mar 2018 15:50:53 -0700 (PDT)
Received: by mail-ua0-x22c.google.com with SMTP id s92so7131416uas.11 for <tram@ietf.org>; Sat, 31 Mar 2018 15:50:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=oCFisk05R3PMGeRddoUZqOc8sdoe9kW/vUNLnCfITKY=; b=NrLY1nlURMABUt30kQ2S8GgieelI93n/FNNqkrFTyl29abSwnK4QwaVgyoK6M05RGJ jxZH24BdZIwTYdhe27olN7trOn78bCru5OKwL4g1pkGCNYJ0l4YnRJoUnU/ouXtgWy47 9X4uxQqgqrIXfcRzj8kFM/oJc+ppz3GfLt49BuMnKwQx6CYG/clHURWcq6SMgq1W1qqq dEQO4ZUmMaYD8rwOSupUSS2vxFSFA5jB4XmUc+qojjgHHZQgc+M/hdApLDbPIyPgezjd GQiHDdcdMatKBCQ3S0FK8TYnLi6RLBy1vBBF26dzL81iBwr6iWXxt4fEb1QTFqKq9Kll ABQw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=oCFisk05R3PMGeRddoUZqOc8sdoe9kW/vUNLnCfITKY=; b=t4UKzxNn/fkaeLQM67ZAav7mSu1YvtkZlHVPdLNJLpQYnSzwvg7KA2UrU6WrLrOSF1 Z9MEYGdbjG1QwlKtlAfaGQqTxWdmF+ssd5CBHVhrnfEjbq7bUJP2ue6Yawf+N9sA8SsG wNNAHrHGGT04ayts+mJUXdddvtuNfisEvhfjz4xGfgKb1EHvG0VSI50OQUdubSz/tj5J OhdtIFXkCY1/pYJ2axoFRzwcNrAXS8OiMR/s1FYspd1coFoxahMfFXRLmHRUpxHsOVMT 5iT+SpWpAZXyaA+QrtNEW0cH3QfwsyzpHlgEp3O3GQJK8sKZWySfajKKq94GCaeeDu5W 7/nQ==
X-Gm-Message-State: ALQs6tCC3kZ28wDObUrdfS2pd6v/RQkZYk+xouvqkzYhwxglNiBjM4CH FiiGbk3rMFaW+Bs9R9etJGwkZrxuLuyYa1hMUIvcuA==
X-Google-Smtp-Source: AIpwx4/QyXs64mc6pdy6pDi46TvqOr2m0P+TcW6l5W/Flgu4J/Ox3mTVSM3aL4YN6j2eknZAghKdCjUGNSeeUqYroQQ=
X-Received: by 10.159.41.99 with SMTP id t90mr2394186uat.127.1522536652528; Sat, 31 Mar 2018 15:50:52 -0700 (PDT)
MIME-Version: 1.0
References: <CANO7kWDd8NZ=svBONwzo6sE5YH3Y5MAdWFP2CQMiTg7M-b47AQ@mail.gmail.com> <c9ef837c-bf7c-decb-9542-8a9ddeda67fd@akamai.com> <E3AB81FC-D841-47A6-A0E2-775461779770@mozilla.com> <CANO7kWA4tmK7Di59tsjvCBoDdh-jW83FxMpqQH1-iSPGLS=mpA@mail.gmail.com> <8d57a9e5-5697-38f5-1b85-bf55930c6461@akamai.com> <BN6PR16MB142571E36A8B89196CB7B080EAAB0@BN6PR16MB1425.namprd16.prod.outlook.com>
In-Reply-To: <BN6PR16MB142571E36A8B89196CB7B080EAAB0@BN6PR16MB1425.namprd16.prod.outlook.com>
From: Justin Uberti <juberti@google.com>
Date: Sat, 31 Mar 2018 22:50:41 +0000
Message-ID: <CAOJ7v-1es3HqF4qN9Ha+v5jgGoONP0rs32vpKMJBP6j546uwqA@mail.gmail.com>
To: TirumaleswarReddy_Konda@mcafee.com
Cc: Brandon Williams <brandon.williams@akamai.com>, Simon Perreault <sperreault@jive.com>,  Nils Ohlmeier <nohlmeier@mozilla.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>, Eric Rescorla <ekr@rtfm.com>, tram@ietf.org
Content-Type: multipart/alternative; boundary="001a114dfb385570b20568bd30ea"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/QpPZn9fZhe44AHYMgzL_Fag041k>
Subject: Re: [tram] Allow TURN to forward inbound connectivity checks without permission
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Mar 2018 22:50:56 -0000

--001a114dfb385570b20568bd30ea
Content-Type: text/plain; charset="UTF-8"

As Brandon says, the ufrag/pwd info could be posted along with the address
of the server, so while this raises the bar, it doesn't solve the problem.

I agree with Brandon that the only reasonable way to completely contain
this is some sort of server policy, e.g., some time window or session count
after which the permission bypass expires, meaning that someone running a
server would have to be continually requesting new allocations and posting
their address/credentials.

On Tue, Mar 20, 2018 at 8:09 AM Konda, Tirumaleswar Reddy <
TirumaleswarReddy_Konda@mcafee.com> wrote:

>
>
> > -----Original Message-----
> > From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Brandon Williams
> > Sent: Tuesday, March 20, 2018 3:02 PM
> > To: Simon Perreault <sperreault@jive.com>; Nils Ohlmeier
> > <nohlmeier@mozilla.com>
> > Cc: Cullen Jennings <fluffy@cisco.com>; Eric Rescorla <ekr@rtfm.com>;
> > tram@ietf.org
> > Subject: Re: [tram] Allow TURN to forward inbound connectivity checks
> without
> > permission
> >
> > On 03/20/2018 06:07 AM, Simon Perreault wrote:
> > > Same opinion here. The point of permissions is to prevent TURN clients
> > > from being able to run generic servers. It seems like always allowing
> > > STUN packets would preserve this feature while solving the session
> > > establishment latency problem. And would be quite a bit simpler to
> > > implement than ufrag perms. Have your cake, eat it, and eat it a
> > > second time.
> >
> > If you want to prevent someone from running a server on the allocation
> you
> > can't assume that a STUN-looking packet is actually legitimate, so some
> > additional validations would be required. Perhaps packet size,
> rate-limiting, and
> > max session counts are enough.
>
> TURN server can also check for the presence of username and MI in the
> STUN packets.
>
> -Tiru
>
> >
> > ufrag permissions didn't do enough to be more meaningful there, since it
> would
> > be easy to post the ufrag somewhere public via a mechanism similar to
> dynamic
> > DNS.
> >
> > --Brandon
> >
> >
> > _______________________________________________
> > tram mailing list
> > tram@ietf.org
> > https://www.ietf.org/mailman/listinfo/tram
>
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram
>

--001a114dfb385570b20568bd30ea
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">As Brandon says, the ufrag/pwd info could be posted along =
with the address of the server, so while this raises the bar, it doesn&#39;=
t solve the problem.<div><br></div><div>I agree with Brandon that the only =
reasonable way to completely contain this is some sort of server policy, e.=
g., some time window or session count after which the permission bypass exp=
ires, meaning that someone running a server would have to be continually re=
questing new allocations and posting their address/credentials.</div></div>=
<br><div class=3D"gmail_quote"><div dir=3D"ltr">On Tue, Mar 20, 2018 at 8:0=
9 AM Konda, Tirumaleswar Reddy &lt;<a href=3D"mailto:TirumaleswarReddy_Kond=
a@mcafee.com">TirumaleswarReddy_Konda@mcafee.com</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex"><br>
<br>
&gt; -----Original Message-----<br>
&gt; From: tram [mailto:<a href=3D"mailto:tram-bounces@ietf.org" target=3D"=
_blank">tram-bounces@ietf.org</a>] On Behalf Of Brandon Williams<br>
&gt; Sent: Tuesday, March 20, 2018 3:02 PM<br>
&gt; To: Simon Perreault &lt;<a href=3D"mailto:sperreault@jive.com" target=
=3D"_blank">sperreault@jive.com</a>&gt;; Nils Ohlmeier<br>
&gt; &lt;<a href=3D"mailto:nohlmeier@mozilla.com" target=3D"_blank">nohlmei=
er@mozilla.com</a>&gt;<br>
&gt; Cc: Cullen Jennings &lt;<a href=3D"mailto:fluffy@cisco.com" target=3D"=
_blank">fluffy@cisco.com</a>&gt;; Eric Rescorla &lt;<a href=3D"mailto:ekr@r=
tfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt;;<br>
&gt; <a href=3D"mailto:tram@ietf.org" target=3D"_blank">tram@ietf.org</a><b=
r>
&gt; Subject: Re: [tram] Allow TURN to forward inbound connectivity checks =
without<br>
&gt; permission<br>
&gt;<br>
&gt; On 03/20/2018 06:07 AM, Simon Perreault wrote:<br>
&gt; &gt; Same opinion here. The point of permissions is to prevent TURN cl=
ients<br>
&gt; &gt; from being able to run generic servers. It seems like always allo=
wing<br>
&gt; &gt; STUN packets would preserve this feature while solving the sessio=
n<br>
&gt; &gt; establishment latency problem. And would be quite a bit simpler t=
o<br>
&gt; &gt; implement than ufrag perms. Have your cake, eat it, and eat it a<=
br>
&gt; &gt; second time.<br>
&gt;<br>
&gt; If you want to prevent someone from running a server on the allocation=
 you<br>
&gt; can&#39;t assume that a STUN-looking packet is actually legitimate, so=
 some<br>
&gt; additional validations would be required. Perhaps packet size, rate-li=
miting, and<br>
&gt; max session counts are enough.<br>
<br>
TURN server can also check for the presence of username and MI in the<br>
STUN packets.<br>
<br>
-Tiru<br>
<br>
&gt;<br>
&gt; ufrag permissions didn&#39;t do enough to be more meaningful there, si=
nce it would<br>
&gt; be easy to post the ufrag somewhere public via a mechanism similar to =
dynamic<br>
&gt; DNS.<br>
&gt;<br>
&gt; --Brandon<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; tram mailing list<br>
&gt; <a href=3D"mailto:tram@ietf.org" target=3D"_blank">tram@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/tram" rel=3D"noreferr=
er" target=3D"_blank">https://www.ietf.org/mailman/listinfo/tram</a><br>
<br>
_______________________________________________<br>
tram mailing list<br>
<a href=3D"mailto:tram@ietf.org" target=3D"_blank">tram@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tram" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/tram</a><br>
</blockquote></div>

--001a114dfb385570b20568bd30ea--

