
From nobody Thu Sep  1 00:06:19 2016
Return-Path: <aamelnikov@fastmail.fm>
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 E1EC21200DF; Thu,  1 Sep 2016 00:06:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=atpNDWQK; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=W0lQ4mWY
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 A_l_9NsuPYNO; Thu,  1 Sep 2016 00:06:16 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6282C12D1D7; Thu,  1 Sep 2016 00:06:16 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id B527E20318; Thu,  1 Sep 2016 03:06:15 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Thu, 01 Sep 2016 03:06:15 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=0kQevv1CyUbCEvijjrj/3ro9eFI=; b=atpNDW QK5xmyk7u7SRDYUYyKVOMaVCmej+u+3HSSCWtlE+TYwRMApfy+cqzHZFzjhKTwoG JvieOAIAbSpmt3+3azh0iaNdseBaA3eF3gf/qAdTiX2Ktmg4hX2QDqjdjig9MNTS CXWQhmAh7nWh555mIl1vLqfFTHGGPtse0vIMc=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=0kQevv1CyUbCEvi jjrj/3ro9eFI=; b=W0lQ4mWYrP7MBNLRBLkVbC/xquHdX49DWSgrTmipiphDi5H UzQ8u0wsvp1Ne9CIOJeC35qEdZFtmwMB4nFlL1+djioBy1Mcr3z6n0ACrXPMV8Jw ALtUSdwXCCVMwmpOxJd+zQka1U00MTo0lz9RgX3i+rreSR0C25ObE8vACyow=
X-Sasl-enc: MfnPg5KwFeQgFeVUFzJWlqj5ETE56SVPE9lm5ss9Lx4G 1472713575
Received: from [192.168.0.6] (cpc5-nmal20-2-0-cust24.19-2.cable.virginm.net [92.234.84.25]) by mail.messagingengine.com (Postfix) with ESMTPA id 4C189F29CD; Thu,  1 Sep 2016 03:06:15 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPad Mail (13G35)
In-Reply-To: <21b2559f2a234c64b47595eb4615c661@XCH-RCD-017.cisco.com>
Date: Thu, 1 Sep 2016 08:18:33 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <932002F5-18BA-46E7-9C71-EC985A0FCFDC@fastmail.fm>
References: <147265807396.13320.16720268350417791956.idtracker@ietfa.amsl.com> <21b2559f2a234c64b47595eb4615c661@XCH-RCD-017.cisco.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/AH8QUEPqwu2gRP76imPaGaIAU20>
Cc: "tram@ietf.org" <tram@ietf.org>, Simon Perreault <sperreault@jive.com>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, The IESG <iesg@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>
Subject: Re: [tram] Alexey Melnikov's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Sep 2016 07:06:18 -0000

Hi,

On 1 Sep 2016, at 04:48, Tirumaleswar Reddy (tireddy) <tireddy@cisco.com> wr=
ote:

>> -----Original Message-----
>> From: Alexey Melnikov [mailto:aamelnikov@fastmail.fm]
>> Sent: Wednesday, August 31, 2016 9:11 PM
>> To: The IESG <iesg@ietf.org>
>> Cc: draft-ietf-tram-turn-server-discovery@ietf.org; Simon Perreault
>> <sperreault@jive.com>; tram-chairs@ietf.org; sperreault@jive.com;
>> tram@ietf.org
>> Subject: Alexey Melnikov's Discuss on draft-ietf-tram-turn-server-discove=
ry-
>> 09: (with DISCUSS)
>>=20
>> Alexey Melnikov has entered the following ballot position for
>> draft-ietf-tram-turn-server-discovery-09: Discuss
>>=20
>> When responding, please keep the subject line intact and reply to all ema=
il
>> addresses included in the To and CC lines. (Feel free to cut this introdu=
ctory
>> paragraph, however.)
>>=20
>>=20
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html=

>> for more information about IESG DISCUSS and COMMENT positions.
>>=20
>>=20
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-tram-turn-server-discovery/
>>=20
>>=20
>>=20
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>=20
>> In Section 9:
>>=20
>> o  For certificate-based authentication, a pre-populated trust anchor
>>      store [RFC6024] allows a TURN client to perform path validation
>>      for the server certificate obtained during the (D)TLS handshake.
>>=20
>>      If the client used a domain name to discover the TURN server, that
>>      domain name also provides a mechanism for validation of the TURN
>>      server.  The client MUST use the rules and guidelines given in
>>      section 6 of [RFC6125] to validate the TURN server identity.
>>=20
>> I am glad that you are referencing RFC 6125, but unfortunately you don't
>> provide enough details. Please add details as specified in Section 3 of R=
FC
>> 6125 to your document.
>=20
> Sure, will add the following lines:
> Certification authorities that issue TURN server certificates SHOULD suppo=
rt the DNS-ID and SRV-ID identifier types. TURN service providers SHOULD inc=
lude the DNS-ID and SRV-ID identifier types in certificate requests.

What about use of CN-IDs and URI-IDs? Wildcards?


From nobody Thu Sep  1 02:34:11 2016
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 3D88712D8DE; Thu,  1 Sep 2016 02:34:08 -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>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.31.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147272244824.10212.8038409365316315202.idtracker@ietfa.amsl.com>
Date: Thu, 01 Sep 2016 02:34:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/VxUs8QkVj9gM4DS8vxhGURpkkH8>
Cc: tram@ietf.org
Subject: [tram] I-D Action: draft-ietf-tram-turn-mobility-06.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Sep 2016 09:34:08 -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 of the IETF.

        Title           : Mobility with TURN
        Authors         : Tirumaleswar Reddy
                          Dan Wing
                          Prashanth Patil
                          Paal-Erik Martinsen
	Filename        : draft-ietf-tram-turn-mobility-06.txt
	Pages           : 13
	Date            : 2016-09-01

Abstract:
   It is desirable to minimize traffic disruption caused by changing IP
   address during a mobility event.  One mechanism to minimize
   disruption is to expose a shorter network path to the mobility event
   so only the local network elements are aware of the changed IP
   address but the remote peer is unaware of the changed IP address.

   This draft provides such an IP address mobility solution using
   Traversal Using Relays around NAT (TURN).  This is achieved by
   allowing a client to retain an allocation on the TURN server when the
   IP address of the client changes.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-tram-turn-mobility-06

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


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 Thu Sep  1 02:38:24 2016
Return-Path: <tireddy@cisco.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 79D2912D8DE for <tram@ietfa.amsl.com>; Thu,  1 Sep 2016 02:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.069
X-Spam-Level: 
X-Spam-Status: No, score=-15.069 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 uLpKegtiP39p for <tram@ietfa.amsl.com>; Thu,  1 Sep 2016 02:38:19 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0861F12D8FA for <tram@ietf.org>; Thu,  1 Sep 2016 02:37:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2301; q=dns/txt; s=iport; t=1472722677; x=1473932277; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=U7ZC2f9mkA41EGY2whGjf06uGnf7uNF9qjnCOtuv9Lk=; b=JgvF11Zg3CfmnHqcBQY4GL2VecjwA629DBU0FQikb1T+4eJapws+nKUD Ck0qiKlYJ1RPggbzK3Lkz9g2nmQIkJ4aO4RHc8CJEe98210uaY2SGxzhe 2AyKOHmXL/xZDimDku5FQtAHwLTg+5+BIwwewHyYsTAKRjSp7e4LmANNJ w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BNAgDo9cdX/5pdJa1dg1ABAQEBAR5Xf?= =?us-ascii?q?Ae4IYIBJIV4AoFNOBQBAgEBAQEBAQFeHAuEYQEBBQEBODQXBAIBCBEEAQEfCQc?= =?us-ascii?q?nCxQJCAIEEwgTiC0OumoBAQEBAQEBAQEBAQEBAQEBAQEBAQEchi+ETYQqhXIFm?= =?us-ascii?q?VABhh+JCoF0ToQPiQ2MSIN4AR42hDFwhW1/AQEB?=
X-IronPort-AV: E=Sophos;i="5.30,266,1470700800"; d="scan'208";a="317424962"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Sep 2016 09:37:56 +0000
Received: from XCH-ALN-017.cisco.com (xch-aln-017.cisco.com [173.36.7.27]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u819buVj023348 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <tram@ietf.org>; Thu, 1 Sep 2016 09:37:56 GMT
Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-ALN-017.cisco.com (173.36.7.27) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 1 Sep 2016 04:37:55 -0500
Received: from xch-rcd-017.cisco.com ([173.37.102.27]) by XCH-RCD-017.cisco.com ([173.37.102.27]) with mapi id 15.00.1210.000; Thu, 1 Sep 2016 04:37:55 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: "tram@ietf.org" <tram@ietf.org>
Thread-Topic: [tram] I-D Action: draft-ietf-tram-turn-mobility-06.txt
Thread-Index: AQHSBDQG3YLSZzGXI0mzYpR4Dm46yaBkYGoQ
Date: Thu, 1 Sep 2016 09:37:55 +0000
Message-ID: <6b556bec225a458c87e7e38168de916f@XCH-RCD-017.cisco.com>
References: <147272244824.10212.8038409365316315202.idtracker@ietfa.amsl.com>
In-Reply-To: <147272244824.10212.8038409365316315202.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.232.21.139]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/ODMZmIPvW1XeH6m9aPrKoDIivrc>
Subject: Re: [tram] I-D Action: draft-ietf-tram-turn-mobility-06.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Sep 2016 09:38:22 -0000

This revision addresses comments from ISEG review.

-Tiru

> -----Original Message-----
> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of internet-
> drafts@ietf.org
> Sent: Thursday, September 1, 2016 3:04 PM
> To: i-d-announce@ietf.org
> Cc: tram@ietf.org
> Subject: [tram] I-D Action: draft-ietf-tram-turn-mobility-06.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 of the IETF.
>=20
>         Title           : Mobility with TURN
>         Authors         : Tirumaleswar Reddy
>                           Dan Wing
>                           Prashanth Patil
>                           Paal-Erik Martinsen
> 	Filename        : draft-ietf-tram-turn-mobility-06.txt
> 	Pages           : 13
> 	Date            : 2016-09-01
>=20
> Abstract:
>    It is desirable to minimize traffic disruption caused by changing IP
>    address during a mobility event.  One mechanism to minimize
>    disruption is to expose a shorter network path to the mobility event
>    so only the local network elements are aware of the changed IP
>    address but the remote peer is unaware of the changed IP address.
>=20
>    This draft provides such an IP address mobility solution using
>    Traversal Using Relays around NAT (TURN).  This is achieved by
>    allowing a client to retain an allocation on the TURN server when the
>    IP address of the client changes.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tram-turn-mobility/
>=20
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-tram-turn-mobility-06
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tram-turn-mobility-06
>=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 Thu Sep  1 02:48:25 2016
Return-Path: <ietf@kuehlewind.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 C61F312D8E9 for <tram@ietfa.amsl.com>; Thu,  1 Sep 2016 02:48:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable 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 URTM15pAJWzd for <tram@ietfa.amsl.com>; Thu,  1 Sep 2016 02:48:23 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B92F12D8CA for <tram@ietf.org>; Thu,  1 Sep 2016 02:48:22 -0700 (PDT)
Received: (qmail 18308 invoked from network); 1 Sep 2016 11:41:39 +0200
Received: from p5dec2a74.dip0.t-ipconnect.de (HELO ?192.168.178.33?) (93.236.42.116) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated);  1 Sep 2016 11:41:39 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <03dee07ec1db4647ade4bd88c6d60676@XCH-RCD-017.cisco.com>
Date: Thu, 1 Sep 2016 11:41:38 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <BE89F713-56F1-477B-924E-3198017A7582@kuehlewind.net>
References: <147266585183.31972.12785596914482997600.idtracker@ietfa.amsl.com> <03dee07ec1db4647ade4bd88c6d60676@XCH-RCD-017.cisco.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/1ajY9FJr-7YeZf34ihXPnIZ8hGI>
Cc: "draft-ietf-tram-turn-mobility@ietf.org" <draft-ietf-tram-turn-mobility@ietf.org>, "sperreault@jive.com" <sperreault@jive.com>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>, The IESG <iesg@ietf.org>, "tram@ietf.org" <tram@ietf.org>
Subject: Re: [tram] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-i?= =?utf-8?q?etf-tram-turn-mobility-05=3A_=28with_COMMENT=29?=
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Sep 2016 09:48:24 -0000

Hi Tiru,

see below.

> Am 01.09.2016 um 04:52 schrieb Tirumaleswar Reddy (tireddy) =
<tireddy@cisco.com>:
>=20
>> -----Original Message-----
>> From: Mirja Kuehlewind [mailto:ietf@kuehlewind.net]
>> Sent: Wednesday, August 31, 2016 11:21 PM
>> To: The IESG <iesg@ietf.org>
>> Cc: draft-ietf-tram-turn-mobility@ietf.org; Simon Perreault
>> <sperreault@jive.com>; tram-chairs@ietf.org; sperreault@jive.com;
>> tram@ietf.org
>> Subject: Mirja K=C3=BChlewind's No Objection on =
draft-ietf-tram-turn-mobility-05:
>> (with COMMENT)
>>=20
>> Mirja K=C3=BChlewind has entered the following ballot position for
>> draft-ietf-tram-turn-mobility-05: No Objection
>>=20
>> When responding, please keep the subject line intact and reply to all =
email
>> addresses included in the To and CC lines. (Feel free to cut this =
introductory
>> paragraph, however.)
>>=20
>>=20
>> Please refer to =
https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>=20
>>=20
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-tram-turn-mobility/
>>=20
>>=20
>>=20
>> =
----------------------------------------------------------------------
>> COMMENT:
>> =
----------------------------------------------------------------------
>>=20
>> Is the following scenario worth to be discussed in the doc?
>>=20
>> A client receives a MOBILITY-TICKET from the server but when it tries =
to send
>> a Refresh Request the server ignors the ticket and sets up a new =
association
>> (maybe because the server seemlessly migrated to a machine that does =
not
>> support/understand MOBILITY-TICKETs or because of policy
>> reasons) and therefore also does not send a new MOBILITY-TICKET back. =
I
>> guess in this case the client would probably still want to =
communication with
>> the destination server and just start a new transport connection, =
right?
>=20
> Yes, server will throw an error and client will have to start a new =
allocation.
> It's an corner case, but probably worth discussing.=20
>=20
> I can add the following lines to Section 3.2.2:=20
>=20
> If the server configuration changes to forbid mobility or the server =
transparently fails-over to another server instance that does support =
MOBILITY-TICKET then the server rejects the Refresh request with a  =
Mobility Forbidden error code and the client starts afresh with a new =
allocation.

That=E2=80=99s not quite the case I talking about. What if the new =
server doesn=E2=80=99t even implement MOBILITY-TICKETs. That means it =
can not send a Mobility Forbidden error code.

Mirja

>=20
> -Tiru
>=20
>>=20
>=20


From nobody Thu Sep  1 02:50:48 2016
Return-Path: <tireddy@cisco.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 BC0A812D0A6; Thu,  1 Sep 2016 02:50:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.069
X-Spam-Level: 
X-Spam-Status: No, score=-15.069 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 crdTp_T4wZwD; Thu,  1 Sep 2016 02:50:37 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 440A612D87A; Thu,  1 Sep 2016 02:50:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4758; q=dns/txt; s=iport; t=1472723437; x=1473933037; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=gqVhs/o6S88TMbFvdY3wRe7wglbSoW4wdsToq0O7ovg=; b=dHGrEfTAtwjinBVTlMCqwN05wAyVPJZQOPHNqZYXQxp1zdgr+kNZWRFd RknFI8v45nkUtI7ObqaKtnuQZgLDJAbMW8EWnlgqNqsg6Hgo67mOKdiTn U4A6YubLQikqoIaV8Iel3ThqRl+A4cg4k7qjU9vCmBcH5HMmKyQ9wFvB5 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BNAgAx+cdX/4UNJK1TCoNQAQEBAQEeV?= =?us-ascii?q?3wHs12CNYIPggEkhXgCHIExOBQBAgEBAQEBAQFeJ4RhAQEEASMRRQwEAgEIEQQ?= =?us-ascii?q?BAQMCIwMCAgIwFAEFAwgCBA4FCIg4CA6td4x1AQEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBFwWBBYUqhE2EEgYLAQYGJ4JrgloFiC2RIwGGH4kKgXSEXYkNjEiDeAEeNoJ?= =?us-ascii?q?8gTVwAYRMgSB/AQEB?=
X-IronPort-AV: E=Sophos;i="5.30,266,1470700800"; d="scan'208";a="142322939"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 01 Sep 2016 09:50:36 +0000
Received: from XCH-RCD-016.cisco.com (xch-rcd-016.cisco.com [173.37.102.26]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id u819oaZq016054 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 1 Sep 2016 09:50:36 GMT
Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-RCD-016.cisco.com (173.37.102.26) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 1 Sep 2016 04:50:35 -0500
Received: from xch-rcd-017.cisco.com ([173.37.102.27]) by XCH-RCD-017.cisco.com ([173.37.102.27]) with mapi id 15.00.1210.000; Thu, 1 Sep 2016 04:50:35 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Thread-Topic: =?utf-8?B?TWlyamEgS8O8aGxld2luZCdzIE5vIE9iamVjdGlvbiBvbiBkcmFmdC1pZXRm?= =?utf-8?Q?-tram-turn-mobility-05:_(with_COMMENT)?=
Thread-Index: AQHSA7A5OrjPMRj10EyfKqHpfAiZ56Bj4BywgADWZwD//6zYAA==
Date: Thu, 1 Sep 2016 09:50:35 +0000
Message-ID: <b836a1625d084f7ab9580f03fc055169@XCH-RCD-017.cisco.com>
References: <147266585183.31972.12785596914482997600.idtracker@ietfa.amsl.com> <03dee07ec1db4647ade4bd88c6d60676@XCH-RCD-017.cisco.com> <BE89F713-56F1-477B-924E-3198017A7582@kuehlewind.net>
In-Reply-To: <BE89F713-56F1-477B-924E-3198017A7582@kuehlewind.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.232.21.139]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/9xRVfkVwRa_LA-VHDWY3B7J7HVg>
Cc: "draft-ietf-tram-turn-mobility@ietf.org" <draft-ietf-tram-turn-mobility@ietf.org>, "sperreault@jive.com" <sperreault@jive.com>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>, The IESG <iesg@ietf.org>, "tram@ietf.org" <tram@ietf.org>
Subject: Re: [tram] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-i?= =?utf-8?q?etf-tram-turn-mobility-05=3A_=28with_COMMENT=29?=
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Sep 2016 09:50:41 -0000

PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBNaXJqYSBLdWVobGV3aW5kIChJ
RVRGKSBbbWFpbHRvOmlldGZAa3VlaGxld2luZC5uZXRdDQo+IFNlbnQ6IFRodXJzZGF5LCBTZXB0
ZW1iZXIgMSwgMjAxNiAzOjEyIFBNDQo+IFRvOiBUaXJ1bWFsZXN3YXIgUmVkZHkgKHRpcmVkZHkp
IDx0aXJlZGR5QGNpc2NvLmNvbT4NCj4gQ2M6IFRoZSBJRVNHIDxpZXNnQGlldGYub3JnPjsgc3Bl
cnJlYXVsdEBqaXZlLmNvbTsgdHJhbUBpZXRmLm9yZzsgZHJhZnQtaWV0Zi0NCj4gdHJhbS10dXJu
LW1vYmlsaXR5QGlldGYub3JnOyB0cmFtLWNoYWlyc0BpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTog
TWlyamEgS8O8aGxld2luZCdzIE5vIE9iamVjdGlvbiBvbiBkcmFmdC1pZXRmLXRyYW0tdHVybi1t
b2JpbGl0eS0NCj4gMDU6ICh3aXRoIENPTU1FTlQpDQo+IA0KPiBIaSBUaXJ1LA0KPiANCj4gc2Vl
IGJlbG93Lg0KPiANCj4gPiBBbSAwMS4wOS4yMDE2IHVtIDA0OjUyIHNjaHJpZWIgVGlydW1hbGVz
d2FyIFJlZGR5ICh0aXJlZGR5KQ0KPiA8dGlyZWRkeUBjaXNjby5jb20+Og0KPiA+DQo+ID4+IC0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4+IEZyb206IE1pcmphIEt1ZWhsZXdpbmQgW21h
aWx0bzppZXRmQGt1ZWhsZXdpbmQubmV0XQ0KPiA+PiBTZW50OiBXZWRuZXNkYXksIEF1Z3VzdCAz
MSwgMjAxNiAxMToyMSBQTQ0KPiA+PiBUbzogVGhlIElFU0cgPGllc2dAaWV0Zi5vcmc+DQo+ID4+
IENjOiBkcmFmdC1pZXRmLXRyYW0tdHVybi1tb2JpbGl0eUBpZXRmLm9yZzsgU2ltb24gUGVycmVh
dWx0DQo+ID4+IDxzcGVycmVhdWx0QGppdmUuY29tPjsgdHJhbS1jaGFpcnNAaWV0Zi5vcmc7IHNw
ZXJyZWF1bHRAaml2ZS5jb207DQo+ID4+IHRyYW1AaWV0Zi5vcmcNCj4gPj4gU3ViamVjdDogTWly
amEgS8O8aGxld2luZCdzIE5vIE9iamVjdGlvbiBvbiBkcmFmdC1pZXRmLXRyYW0tdHVybi1tb2Jp
bGl0eS0NCj4gMDU6DQo+ID4+ICh3aXRoIENPTU1FTlQpDQo+ID4+DQo+ID4+IE1pcmphIEvDvGhs
ZXdpbmQgaGFzIGVudGVyZWQgdGhlIGZvbGxvd2luZyBiYWxsb3QgcG9zaXRpb24gZm9yDQo+ID4+
IGRyYWZ0LWlldGYtdHJhbS10dXJuLW1vYmlsaXR5LTA1OiBObyBPYmplY3Rpb24NCj4gPj4NCj4g
Pj4gV2hlbiByZXNwb25kaW5nLCBwbGVhc2Uga2VlcCB0aGUgc3ViamVjdCBsaW5lIGludGFjdCBh
bmQgcmVwbHkgdG8gYWxsDQo+ID4+IGVtYWlsIGFkZHJlc3NlcyBpbmNsdWRlZCBpbiB0aGUgVG8g
YW5kIENDIGxpbmVzLiAoRmVlbCBmcmVlIHRvIGN1dA0KPiA+PiB0aGlzIGludHJvZHVjdG9yeSBw
YXJhZ3JhcGgsIGhvd2V2ZXIuKQ0KPiA+Pg0KPiA+Pg0KPiA+PiBQbGVhc2UgcmVmZXIgdG8NCj4g
Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvaWVzZy9zdGF0ZW1lbnQvZGlzY3Vzcy1jcml0ZXJpYS5o
dG1sDQo+ID4+IGZvciBtb3JlIGluZm9ybWF0aW9uIGFib3V0IElFU0cgRElTQ1VTUyBhbmQgQ09N
TUVOVCBwb3NpdGlvbnMuDQo+ID4+DQo+ID4+DQo+ID4+IFRoZSBkb2N1bWVudCwgYWxvbmcgd2l0
aCBvdGhlciBiYWxsb3QgcG9zaXRpb25zLCBjYW4gYmUgZm91bmQgaGVyZToNCj4gPj4gaHR0cHM6
Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi10cmFtLXR1cm4tbW9iaWxpdHkv
DQo+ID4+DQo+ID4+DQo+ID4+DQo+ID4+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiA+PiAtDQo+ID4+IENPTU1F
TlQ6DQo+ID4+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiA+PiAtDQo+ID4+DQo+ID4+IElzIHRoZSBmb2xsb3dp
bmcgc2NlbmFyaW8gd29ydGggdG8gYmUgZGlzY3Vzc2VkIGluIHRoZSBkb2M/DQo+ID4+DQo+ID4+
IEEgY2xpZW50IHJlY2VpdmVzIGEgTU9CSUxJVFktVElDS0VUIGZyb20gdGhlIHNlcnZlciBidXQg
d2hlbiBpdCB0cmllcw0KPiA+PiB0byBzZW5kIGEgUmVmcmVzaCBSZXF1ZXN0IHRoZSBzZXJ2ZXIg
aWdub3JzIHRoZSB0aWNrZXQgYW5kIHNldHMgdXAgYQ0KPiA+PiBuZXcgYXNzb2NpYXRpb24gKG1h
eWJlIGJlY2F1c2UgdGhlIHNlcnZlciBzZWVtbGVzc2x5IG1pZ3JhdGVkIHRvIGENCj4gPj4gbWFj
aGluZSB0aGF0IGRvZXMgbm90IHN1cHBvcnQvdW5kZXJzdGFuZCBNT0JJTElUWS1USUNLRVRzIG9y
IGJlY2F1c2UNCj4gPj4gb2YgcG9saWN5DQo+ID4+IHJlYXNvbnMpIGFuZCB0aGVyZWZvcmUgYWxz
byBkb2VzIG5vdCBzZW5kIGEgbmV3IE1PQklMSVRZLVRJQ0tFVCBiYWNrLg0KPiA+PiBJIGd1ZXNz
IGluIHRoaXMgY2FzZSB0aGUgY2xpZW50IHdvdWxkIHByb2JhYmx5IHN0aWxsIHdhbnQgdG8NCj4g
Pj4gY29tbXVuaWNhdGlvbiB3aXRoIHRoZSBkZXN0aW5hdGlvbiBzZXJ2ZXIgYW5kIGp1c3Qgc3Rh
cnQgYSBuZXcgdHJhbnNwb3J0DQo+IGNvbm5lY3Rpb24sIHJpZ2h0Pw0KPiA+DQo+ID4gWWVzLCBz
ZXJ2ZXIgd2lsbCB0aHJvdyBhbiBlcnJvciBhbmQgY2xpZW50IHdpbGwgaGF2ZSB0byBzdGFydCBh
IG5ldyBhbGxvY2F0aW9uLg0KPiA+IEl0J3MgYW4gY29ybmVyIGNhc2UsIGJ1dCBwcm9iYWJseSB3
b3J0aCBkaXNjdXNzaW5nLg0KPiA+DQo+ID4gSSBjYW4gYWRkIHRoZSBmb2xsb3dpbmcgbGluZXMg
dG8gU2VjdGlvbiAzLjIuMjoNCj4gPg0KPiA+IElmIHRoZSBzZXJ2ZXIgY29uZmlndXJhdGlvbiBj
aGFuZ2VzIHRvIGZvcmJpZCBtb2JpbGl0eSBvciB0aGUgc2VydmVyDQo+IHRyYW5zcGFyZW50bHkg
ZmFpbHMtb3ZlciB0byBhbm90aGVyIHNlcnZlciBpbnN0YW5jZSB0aGF0IGRvZXMgc3VwcG9ydA0K
PiBNT0JJTElUWS1USUNLRVQgdGhlbiB0aGUgc2VydmVyIHJlamVjdHMgdGhlIFJlZnJlc2ggcmVx
dWVzdCB3aXRoIGEgIE1vYmlsaXR5DQo+IEZvcmJpZGRlbiBlcnJvciBjb2RlIGFuZCB0aGUgY2xp
ZW50IHN0YXJ0cyBhZnJlc2ggd2l0aCBhIG5ldyBhbGxvY2F0aW9uLg0KPiANCj4gVGhhdOKAmXMg
bm90IHF1aXRlIHRoZSBjYXNlIEkgdGFsa2luZyBhYm91dC4gV2hhdCBpZiB0aGUgbmV3IHNlcnZl
ciBkb2VzbuKAmXQgZXZlbg0KPiBpbXBsZW1lbnQgTU9CSUxJVFktVElDS0VUcy4gVGhhdCBtZWFu
cyBpdCBjYW4gbm90IHNlbmQgYSBNb2JpbGl0eQ0KPiBGb3JiaWRkZW4gZXJyb3IgY29kZS4NCg0K
R290IGl0LiBJbiB0aGlzIGNhc2Ugc2VydmVyIHdpbGwgaWdub3JlIHRoZSBhdHRyaWJ1dGUgYW5k
IHdpbGwgdHJ5IHRvIHJldHJpZXZlIHRoZSA1LXR1cGxlIGZyb20gdGhlIHBhY2tldA0KdG8gaWRl
bnRpZnkgYW4gYXNzb2NpYXRlZCBhbGxvY2F0aW9uLCBsb29rLXVwIGZhaWxzIGFuZCB0aGUgc2Vy
dmVyIHdvdWxkIHJldHVybiA0MzcgKEFsbG9jYXRpb24gTWlzbWF0Y2gpIGVycm9yLg0KDQotVGly
dQ0KDQo+IA0KPiBNaXJqYQ0KPiANCj4gPg0KPiA+IC1UaXJ1DQo+ID4NCj4gPj4NCj4gPg0KDQo=


From nobody Thu Sep  1 03:15:05 2016
Return-Path: <ietf@kuehlewind.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 D6C9412D8DD for <tram@ietfa.amsl.com>; Thu,  1 Sep 2016 03:15:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable 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 KrOkyZDgro_f for <tram@ietfa.amsl.com>; Thu,  1 Sep 2016 03:15:01 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 277A312D902 for <tram@ietf.org>; Thu,  1 Sep 2016 03:15:00 -0700 (PDT)
Received: (qmail 19979 invoked from network); 1 Sep 2016 12:08:18 +0200
Received: from p5dec2a74.dip0.t-ipconnect.de (HELO ?192.168.178.33?) (93.236.42.116) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated);  1 Sep 2016 12:08:17 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <b836a1625d084f7ab9580f03fc055169@XCH-RCD-017.cisco.com>
Date: Thu, 1 Sep 2016 12:08:15 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <91ACD21C-9A4D-4183-9787-9F41ABF24520@kuehlewind.net>
References: <147266585183.31972.12785596914482997600.idtracker@ietfa.amsl.com> <03dee07ec1db4647ade4bd88c6d60676@XCH-RCD-017.cisco.com> <BE89F713-56F1-477B-924E-3198017A7582@kuehlewind.net> <b836a1625d084f7ab9580f03fc055169@XCH-RCD-017.cisco.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/q098ul-MYfNbaIWoB0AsxTgKCeU>
Cc: The IESG <iesg@ietf.org>, "sperreault@jive.com" <sperreault@jive.com>, "tram@ietf.org" <tram@ietf.org>, "draft-ietf-tram-turn-mobility@ietf.org" <draft-ietf-tram-turn-mobility@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>
Subject: Re: [tram] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-i?= =?utf-8?q?etf-tram-turn-mobility-05=3A_=28with_COMMENT=29?=
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Sep 2016 10:15:04 -0000

Hi,

see below.=20

> Am 01.09.2016 um 11:50 schrieb Tirumaleswar Reddy (tireddy) =
<tireddy@cisco.com>:
>=20
>> -----Original Message-----
>> From: Mirja Kuehlewind (IETF) [mailto:ietf@kuehlewind.net]
>> Sent: Thursday, September 1, 2016 3:12 PM
>> To: Tirumaleswar Reddy (tireddy) <tireddy@cisco.com>
>> Cc: The IESG <iesg@ietf.org>; sperreault@jive.com; tram@ietf.org; =
draft-ietf-
>> tram-turn-mobility@ietf.org; tram-chairs@ietf.org
>> Subject: Re: Mirja K=C3=BChlewind's No Objection on =
draft-ietf-tram-turn-mobility-
>> 05: (with COMMENT)
>>=20
>> Hi Tiru,
>>=20
>> see below.
>>=20
>>> Am 01.09.2016 um 04:52 schrieb Tirumaleswar Reddy (tireddy)
>> <tireddy@cisco.com>:
>>>=20
>>>> -----Original Message-----
>>>> From: Mirja Kuehlewind [mailto:ietf@kuehlewind.net]
>>>> Sent: Wednesday, August 31, 2016 11:21 PM
>>>> To: The IESG <iesg@ietf.org>
>>>> Cc: draft-ietf-tram-turn-mobility@ietf.org; Simon Perreault
>>>> <sperreault@jive.com>; tram-chairs@ietf.org; sperreault@jive.com;
>>>> tram@ietf.org
>>>> Subject: Mirja K=C3=BChlewind's No Objection on =
draft-ietf-tram-turn-mobility-
>> 05:
>>>> (with COMMENT)
>>>>=20
>>>> Mirja K=C3=BChlewind has entered the following ballot position for
>>>> draft-ietf-tram-turn-mobility-05: No Objection
>>>>=20
>>>> When responding, please keep the subject line intact and reply to =
all
>>>> email addresses included in the To and CC lines. (Feel free to cut
>>>> this introductory paragraph, however.)
>>>>=20
>>>>=20
>>>> Please refer to
>>>> https://www.ietf.org/iesg/statement/discuss-criteria.html
>>>> for more information about IESG DISCUSS and COMMENT positions.
>>>>=20
>>>>=20
>>>> The document, along with other ballot positions, can be found here:
>>>> https://datatracker.ietf.org/doc/draft-ietf-tram-turn-mobility/
>>>>=20
>>>>=20
>>>>=20
>>>> =
---------------------------------------------------------------------
>>>> -
>>>> COMMENT:
>>>> =
---------------------------------------------------------------------
>>>> -
>>>>=20
>>>> Is the following scenario worth to be discussed in the doc?
>>>>=20
>>>> A client receives a MOBILITY-TICKET from the server but when it =
tries
>>>> to send a Refresh Request the server ignors the ticket and sets up =
a
>>>> new association (maybe because the server seemlessly migrated to a
>>>> machine that does not support/understand MOBILITY-TICKETs or =
because
>>>> of policy
>>>> reasons) and therefore also does not send a new MOBILITY-TICKET =
back.
>>>> I guess in this case the client would probably still want to
>>>> communication with the destination server and just start a new =
transport
>> connection, right?
>>>=20
>>> Yes, server will throw an error and client will have to start a new =
allocation.
>>> It's an corner case, but probably worth discussing.
>>>=20
>>> I can add the following lines to Section 3.2.2:
>>>=20
>>> If the server configuration changes to forbid mobility or the server
>> transparently fails-over to another server instance that does support
>> MOBILITY-TICKET then the server rejects the Refresh request with a  =
Mobility
>> Forbidden error code and the client starts afresh with a new =
allocation.
>>=20
>> That=E2=80=99s not quite the case I talking about. What if the new =
server doesn=E2=80=99t even
>> implement MOBILITY-TICKETs. That means it can not send a Mobility
>> Forbidden error code.
>=20
> Got it. In this case server will ignore the attribute and will try to =
retrieve the 5-tuple from the packet
> to identify an associated allocation, look-up fails and the server =
would return 437 (Allocation Mismatch) error.

Ah okay. In this case it=E2=80=99s actually fine.

Mirja


>=20
> -Tiru
>=20
>>=20
>> Mirja
>>=20
>>>=20
>>> -Tiru
>>>=20
>>>>=20
>>>=20
>=20


From nobody Thu Sep  1 03:28:21 2016
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 89843127058; Thu,  1 Sep 2016 03:28:17 -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>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.31.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147272569752.10180.7542723989952602398.idtracker@ietfa.amsl.com>
Date: Thu, 01 Sep 2016 03:28:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/CmMqIldd-j11D_XZNTMBSI3f-9w>
Cc: tram@ietf.org
Subject: [tram] I-D Action: draft-ietf-tram-turn-mobility-07.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Sep 2016 10:28:17 -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 of the IETF.

        Title           : Mobility with TURN
        Authors         : Tirumaleswar Reddy
                          Dan Wing
                          Prashanth Patil
                          Paal-Erik Martinsen
	Filename        : draft-ietf-tram-turn-mobility-07.txt
	Pages           : 13
	Date            : 2016-09-01

Abstract:
   It is desirable to minimize traffic disruption caused by changing IP
   address during a mobility event.  One mechanism to minimize
   disruption is to expose a shorter network path to the mobility event
   so only the local network elements are aware of the changed IP
   address but the remote peer is unaware of the changed IP address.

   This draft provides such an IP address mobility solution using
   Traversal Using Relays around NAT (TURN).  This is achieved by
   allowing a client to retain an allocation on the TURN server when the
   IP address of the client changes.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-tram-turn-mobility-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-tram-turn-mobility-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 Thu Sep  1 05:07:26 2016
Return-Path: <kathleen.moriarty.ietf@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 CB32612D80F; Thu,  1 Sep 2016 05:07:19 -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, FREEMAIL_FROM=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=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 vdXeDrcjYVjH; Thu,  1 Sep 2016 05:07:15 -0700 (PDT)
Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::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 5A014128874; Thu,  1 Sep 2016 05:07:15 -0700 (PDT)
Received: by mail-qk0-x22a.google.com with SMTP id l2so81990574qkf.3; Thu, 01 Sep 2016 05:07:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Xv3RrA4Hqx8IR+c6uBJIRhc4UQKV9DxadCeYKz84m7k=; b=EVQF5VFX763LgnvHfuZdRmTRySI32qK4mxswmqg/b/KCeXxSdatBoa0+xzneYvi7ak lje1dCP858JuN9qdOLTAQbh9EsacuS1XYXtj5jqQIXkI4ZrQ2StjTeamvA3dIxLuaSvP cRw5QBQgtv0ig+kEbULGZIy9Mhb6Aqm/k2LlUl6M6FlNiN3aBfUbL+GGnHsLwuLWCSPS EGhiwU6YH8qB4BPTYLSVImf6n999vHBow/riWzc2UQpqXj7vWh0ECXEwn7X+GGiiBrgr W73Ov1FaSWXIpSE3ZVMAZTdPNIxuZyeplQAy0jpp4mqA8SItCtVeCdSeKVnUa4VIx/gU QLtg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Xv3RrA4Hqx8IR+c6uBJIRhc4UQKV9DxadCeYKz84m7k=; b=OozQ330UVXF017Npp3cLUS9b4YzusNA2e0yszlLpNE1csQgm0wc0d/gyNVu6c3M/fJ Ubpqlz6zku3NQqQ7mCKI1Vd5grFTEJDboXqamt9IfE2D8y9ZOAqEWUJfsz8q5VlUP+88 5xLffNhfaJGZwKmo4PXZD0XhrdW5cxLkCq1DFo2V2RnWiLtmj3Ib41hIHGGnpge8XJXD gPUZS9/mhSLYZQX/0FEo+eI02LgovWhzjPaP9fSaOSVRTjkroWzGj/6Q5VgGxibr0KL+ d/BXob7brzUSDWYQVAeic8L4K9THG8pvB8wdD/Cy/12Hjg5t40YzNbvwMPNaejmx+ft+ pRoA==
X-Gm-Message-State: AE9vXwOx4qw1ama6cQZm4ZEYxAzRLFTROnMijSgBv5lNpWUycpAqGFkWilnUE3FLzN3uHw==
X-Received: by 10.55.5.65 with SMTP id 62mr16921753qkf.279.1472731634494; Thu, 01 Sep 2016 05:07:14 -0700 (PDT)
Received: from [192.168.1.6] (209-6-124-204.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com. [209.6.124.204]) by smtp.gmail.com with ESMTPSA id t1sm2596333qtt.25.2016.09.01.05.07.13 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 01 Sep 2016 05:07:14 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: kathleen.moriarty.ietf@gmail.com
X-Mailer: iPhone Mail (13G35)
In-Reply-To: <d742e129f2714a0cabb722288bfeb1a6@XCH-RCD-017.cisco.com>
Date: Thu, 1 Sep 2016 08:07:13 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC3E0CC4-79EE-4F5E-A59C-2BB78E13E4BB@gmail.com>
References: <147247859789.14154.18257109792324801465.idtracker@ietfa.amsl.com> <d742e129f2714a0cabb722288bfeb1a6@XCH-RCD-017.cisco.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/YO729hAErZSgpT8XijU2Qur2pb8>
Cc: "tram@ietf.org" <tram@ietf.org>, Simon Perreault <sperreault@jive.com>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, The IESG <iesg@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>
Subject: Re: [tram] Kathleen Moriarty's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Sep 2016 12:07:20 -0000

Sent from my iPhone

On Aug 31, 2016, at 3:02 AM, Tirumaleswar Reddy (tireddy) <tireddy@cisco.com=
> wrote:

>> -----Original Message-----
>> From: Kathleen Moriarty [mailto:Kathleen.Moriarty.ietf@gmail.com]
>> Sent: Monday, August 29, 2016 7:20 PM
>> To: The IESG <iesg@ietf.org>
>> Cc: draft-ietf-tram-turn-server-discovery@ietf.org; Simon Perreault
>> <sperreault@jive.com>; tram-chairs@ietf.org; sperreault@jive.com;
>> tram@ietf.org
>> Subject: Kathleen Moriarty's Discuss on draft-ietf-tram-turn-server-disco=
very-
>> 09: (with DISCUSS)
>>=20
>> Kathleen Moriarty has entered the following ballot position for
>> draft-ietf-tram-turn-server-discovery-09: Discuss
>>=20
>> When responding, please keep the subject line intact and reply to all ema=
il
>> addresses included in the To and CC lines. (Feel free to cut this introdu=
ctory
>> paragraph, however.)
>>=20
>>=20
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html=

>> for more information about IESG DISCUSS and COMMENT positions.
>>=20
>>=20
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-tram-turn-server-discovery/
>>=20
>>=20
>>=20
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>=20
>> This should be easy to resolve.  In reading the draft, it doesn't cover a=
ny
>> mechanism for the TURN server to limit what clients can discover it.
>> For the second and third method, it seems like there are possible ways to=
 do
>> this.  Could these be added to the security considerations?  You'd need t=
o
>> state that this isn't possible with the first method.  If there is a reas=
on why it is
>> always okay to discover a TURN server, please let me know why this is not=

>> appropriate to add.  Thanks.
>=20
> I don't see a reason why TURN server discovery should be restricted only t=
o specific clients. Please explain the scenarios for imposing such restricti=
ons.

Hello Tiru,

Are there any cases where some domains or addresses should be restricted?  W=
hen you have open services, it's possible to attack them.  It could be from a=
 design or implementation problem that makes an exploit possible or it might=
 just be for network reconnaissance.  Is there something different about TUR=
N servers that makes this point moot.

Thank you,
Kathleen=20
>=20
> Cheers,
> -Tiru
>=20
>=20


From nobody Thu Sep  1 05:55:38 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
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 625E012DAD5; Thu,  1 Sep 2016 05:55:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.31.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147273453736.10136.2190061654209677850.idtracker@ietfa.amsl.com>
Date: Thu, 01 Sep 2016 05:55:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/4EYrJyR3adHyjat7QnVmi-HNijQ>
Cc: sperreault@jive.com, tram@ietf.org, draft-ietf-tram-turn-mobility@ietf.org, tram-chairs@ietf.org
Subject: [tram] Stephen Farrell's Discuss on draft-ietf-tram-turn-mobility-07: (with DISCUSS)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Sep 2016 12:55:37 -0000

Stephen Farrell has entered the following ballot position for
draft-ietf-tram-turn-mobility-07: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-tram-turn-mobility/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------


Apologies if these discuss points are off-base, I was pressed
for time when reviewing this:-(

(1) section 6 correctly says that encryption and integrity
protection are needed to prevent attacks, but the wording
seems ambiguous. Does the MUST here mean that a) TURN servers
MUST use strong crypto whenever they send tickets or b) if a
TURN server does not use strong crypto then tickets can be
abused? I hope it's the former, but in any case I think you
need to clearly say.

(2) I guess the use of (D)TLS is fairly clear here. But I'm
less clear that things are ok for the other cases when the
ticket is (I guess?) visible to a network attacker. Don't you
need to say that in those other cases the server MUST NOT
honour the ticket unless the authentication mechanisms have
worked out ok?





From nobody Thu Sep  1 06:04:40 2016
Return-Path: <spencerdawkins.ietf@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 2D6B712DBCC; Thu,  1 Sep 2016 06:04: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, FREEMAIL_FROM=0.001, 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=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 LO1DU6OM6a6a; Thu,  1 Sep 2016 06:04:33 -0700 (PDT)
Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::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 E1F1912DBD4; Thu,  1 Sep 2016 05:41:18 -0700 (PDT)
Received: by mail-yw0-x230.google.com with SMTP id j12so49293489ywb.2; Thu, 01 Sep 2016 05:41:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:from:date:message-id:subject:to; bh=IjRaLsf9JLvgKZmuAMc9LehopUMSqwybvz/jL2gszYk=; b=PW3rtLyjTI59qU6pNUoYr8L/Wdw7o4KQ4PIfAaWuGI1JxNLyw9MfYzTgHWWzapXdKy Mw4h6GJZ++j7kukbXkWpWvPNbyCEnLBXbJsbC4D/3NKeY4QXOtqbk9356ECmnBoK8ZEl pJ58/6Swv3o4jlJRZDyyh3A0dFfSUxS9tjx3URWp8jprDOnL46kp//UtEa8PEbqtao2T 6Dnh9cWKCWeKOvJfjczyfm29ZaW/x4L+0OrUVVSS9XKxMNoj5PIraLvYetYT0j/r5Ub9 cs7+VAQItyXZ+BvnRXr1H4DXEorn8Ppo+hQ1zSH0med2FEarPai65RIV8otmfpJNnHR4 3eew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=IjRaLsf9JLvgKZmuAMc9LehopUMSqwybvz/jL2gszYk=; b=dwmOLeIAekbtdJMLqcis0hbNAaxLV5CZV8JFUF2Wv6aqbLMOPKwBitEsgqFd7MBOi9 jFa2IRQj9xSPpben2UyZG/8BlDEUoxKakV6moC3lWI2z4DAilK8ulZ1PPVcqqhjMy0a2 ei43YLefyeVmGCpHjSZvQ6xaiBCgyelciUwaT3DdD1vTUe2wbs+nop1E4tZ3l1RzQA2E eS/AWDQOdurbQvke5BV+Tc0YoD4si7Bo7N7Tl/1LsAk+vdBqurf0rnjDmYMDpIBzmYEg PM5rPoo9YY1taWXe28YQGK4uMvmkYvqBaGB+pB2eqT4f96ZDIyZqUpdLJJszZnRr5HAn rsHw==
X-Gm-Message-State: AE9vXwNCnaLqNH/pZkm0Uxv/MdCJv2QNaYItxca0VKQSwGqxNH/CgWNjYAYbAzC1krxkZuxOhH8csW67fO742g==
X-Received: by 10.129.82.12 with SMTP id g12mr1231183ywb.208.1472733678187; Thu, 01 Sep 2016 05:41:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.24.86 with HTTP; Thu, 1 Sep 2016 05:41:17 -0700 (PDT)
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 1 Sep 2016 07:41:17 -0500
Message-ID: <CAKKJt-cQB8wtv_7Fg_99EanpAj+PFKb8hrjerv4RmrRYFE5tpA@mail.gmail.com>
To: Simon Perreault <sperreault@jive.com>, draft-ietf-tram-turn-server-discovery@ietf.org,  "tram@ietf.org" <tram@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>
Content-Type: multipart/alternative; boundary=001a114da67cbcbbcf053b7187e1
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/gJj6W4Rp9fB37u2_EcmNG0PYcNs>
Subject: [tram] Discuss ballot positions on draft-ietf-tram-turn-server-discovery
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Sep 2016 13:04:39 -0000

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

Dear Authors,

I haven't seen responses to Discuss positions from Ben and from Suresh on
this draft, at least not yet (thank you for the quick responses to the
Discuss positions from Alexey, Kathleen, and Terry).

Ben's seems pretty clear, but I wanted to make sure Suresh's Discuss is
clear enough for you to work with. If you have a chance to let me know
something about that in the next couple of hours (pre-telechat), that would
be awesome.

The datatracker page with ballot positions is (as always) at
https://datatracker.ietf.org/doc/draft-ietf-tram-turn-server-discovery/ballot/
.

Thanks,

Spencer

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

<div dir=3D"ltr">Dear Authors,<div><br></div><div>I haven&#39;t seen respon=
ses to Discuss positions from Ben and from Suresh on this draft, at least n=
ot yet (thank you for the quick responses to the Discuss positions from Ale=
xey, Kathleen, and Terry).</div><div><br></div><div>Ben&#39;s seems pretty =
clear, but I wanted to make sure Suresh&#39;s Discuss is clear enough for y=
ou to work with. If you have a chance to let me know something about that i=
n the next couple of hours (pre-telechat), that would be awesome.</div><div=
><br></div><div>The datatracker page with ballot positions is (as always) a=
t=C2=A0<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-tram-turn-ser=
ver-discovery/ballot/">https://datatracker.ietf.org/doc/draft-ietf-tram-tur=
n-server-discovery/ballot/</a>.</div><div><br></div><div>Thanks,</div><div>=
<br></div><div>Spencer</div></div>

--001a114da67cbcbbcf053b7187e1--


From nobody Thu Sep  1 06:12:29 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
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 E220012D97C; Thu,  1 Sep 2016 06:12:23 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.31.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147273554388.10233.10088423389265732467.idtracker@ietfa.amsl.com>
Date: Thu, 01 Sep 2016 06:12:23 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/6boeULbF5dHOJ9kYXeePL7aGglY>
Cc: sperreault@jive.com, draft-ietf-tram-turn-server-discovery@ietf.org, tram@ietf.org, tram-chairs@ietf.org
Subject: [tram] Stephen Farrell's No Objection on draft-ietf-tram-turn-server-discovery-09: (with COMMENT)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Sep 2016 13:12:24 -0000

Stephen Farrell has entered the following ballot position for
draft-ietf-tram-turn-server-discovery-09: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-tram-turn-server-discovery/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


- 5.1: s/chance/change/

- I think section 9 covers all the bases in terms of what
might be done, but probably has to be a bit vague about what's
best to do and the consequences that follow. (For example,
with the reference to how RFC7250 "could be used.") I think it
might be a good idea to admit that we don't really yet know
the security implications of this mechanism, if widely
deployed.  However, I also admit that I'm unsure about this
since it's just very hard to know the security properties of
discovery of this kind ahead of time, so I'm not sure what
kind of text to suggest that'd be useful.



From nobody Thu Sep  1 06:58:16 2016
Return-Path: <tireddy@cisco.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 72BFF12D962; Thu,  1 Sep 2016 06:58:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.069
X-Spam-Level: 
X-Spam-Status: No, score=-15.069 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 MJNd7JdK0UuC; Thu,  1 Sep 2016 06:58:10 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFC1012D9ED; Thu,  1 Sep 2016 06:38:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2780; q=dns/txt; s=iport; t=1472737102; x=1473946702; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=eacnXMknaA97NjQp1RoSeKA2BWFudQ3RPgHMr74XLOU=; b=OuHztER2St1dVvw8xtiCFrRPinzl94KdU+xiHTDeg2rm9xy1qzLKNckL kMyEfkLzOFEK/HxrtR7MCzxtIkLkrmy/FZuBEy2XYlYl4ky5AphlmSQci M9hfDcZ+3BSM/RP/hy+yVtCX0HLEXH4xSdVrd4n4gm2ZQdw5bUwCAw+xh o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D/AQAcLshX/5RdJa1dg1ABAQEBAR5Xf?= =?us-ascii?q?Ae4I4ICJIV4AoFSOBQBAgEBAQEBAQFeJ4RhAQEFAQE4NAsMBAIBCBEEAQEfCQc?= =?us-ascii?q?nCxQJCAIEAQ0FCIhADrpKAQEBAQEBAQEBAQEBAQEBAQEBAQEBFwWGL4RNhBIRA?= =?us-ascii?q?QYGQoUqBYgtkSMBhh+JCoF0hF2JDYZwhViDeAEeNoJ8gTVwAYRMgSB/AQEB?=
X-IronPort-AV: E=Sophos;i="5.30,267,1470700800"; d="scan'208";a="316342125"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Sep 2016 13:38:20 +0000
Received: from XCH-ALN-019.cisco.com (xch-aln-019.cisco.com [173.36.7.29]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id u81DcKp9001733 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 1 Sep 2016 13:38:20 GMT
Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-ALN-019.cisco.com (173.36.7.29) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 1 Sep 2016 08:38:20 -0500
Received: from xch-rcd-017.cisco.com ([173.37.102.27]) by XCH-RCD-017.cisco.com ([173.37.102.27]) with mapi id 15.00.1210.000; Thu, 1 Sep 2016 08:38:19 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, The IESG <iesg@ietf.org>
Thread-Topic: [tram] Stephen Farrell's Discuss on draft-ietf-tram-turn-mobility-07: (with DISCUSS)
Thread-Index: AQHSBFAm7SpipZMdr064/HdJ1esKm6Bkm3Mg
Date: Thu, 1 Sep 2016 13:38:19 +0000
Message-ID: <95abfbf9dd424ed4b6df6ddaeb28ca9f@XCH-RCD-017.cisco.com>
References: <147273453736.10136.2190061654209677850.idtracker@ietfa.amsl.com>
In-Reply-To: <147273453736.10136.2190061654209677850.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.55.65]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/RcoZfh6DhOF_U9E_ZL-TQw-9njQ>
Cc: "tram-chairs@ietf.org" <tram-chairs@ietf.org>, "sperreault@jive.com" <sperreault@jive.com>, "tram@ietf.org" <tram@ietf.org>, "draft-ietf-tram-turn-mobility@ietf.org" <draft-ietf-tram-turn-mobility@ietf.org>
Subject: Re: [tram] Stephen Farrell's Discuss on draft-ietf-tram-turn-mobility-07: (with DISCUSS)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Sep 2016 13:58:14 -0000

> -----Original Message-----
> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Stephen Farrell
> Sent: Thursday, September 1, 2016 6:26 PM
> To: The IESG <iesg@ietf.org>
> Cc: sperreault@jive.com; tram@ietf.org; draft-ietf-tram-turn-
> mobility@ietf.org; tram-chairs@ietf.org
> Subject: [tram] Stephen Farrell's Discuss on draft-ietf-tram-turn-mobilit=
y-07:
> (with DISCUSS)
>=20
> Stephen Farrell has entered the following ballot position for
> draft-ietf-tram-turn-mobility-07: Discuss
>=20
> When responding, please keep the subject line intact and reply to all ema=
il
> addresses included in the To and CC lines. (Feel free to cut this introdu=
ctory
> paragraph, however.)
>=20
>=20
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-tram-turn-mobility/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>=20
>=20
> Apologies if these discuss points are off-base, I was pressed for time wh=
en
> reviewing this:-(
>=20
> (1) section 6 correctly says that encryption and integrity protection are
> needed to prevent attacks, but the wording seems ambiguous. Does the MUST
> here mean that a) TURN servers MUST use strong crypto whenever they send
> tickets or b) if a TURN server does not use strong crypto then tickets ca=
n be
> abused? I hope it's the former, but in any case I think you need to clear=
ly say.

Yes, it is a). How about adding the following line to Section 6 ?
TURN server MUST ensure that the tickets is authenticated and encrypted usi=
ng strong cryptographic algorithm=20
to prevent modification or eavesdropping by an attacker.

>=20
> (2) I guess the use of (D)TLS is fairly clear here. But I'm less clear th=
at things
> are ok for the other cases when the ticket is (I guess?) visible to a net=
work
> attacker. Don't you need to say that in those other cases the server MUST
> NOT honour the ticket unless the authentication mechanisms have worked
> out ok?

Yes, I can update the draft to say the following:
TURN client and server MUST use STUN long-term credential mechanism [RFC538=
9] or STUN Extension for Third-Party Authorization [RFC7635] or (D)TLS conn=
ection to avoid malicious users trying to impersonate the client using the =
ticket for TURN mobility.

-Tiru

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


From nobody Thu Sep  1 07:02:14 2016
Return-Path: <gsalguei@cisco.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 463AA12D9E8 for <tram@ietfa.amsl.com>; Thu,  1 Sep 2016 07:02:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.069
X-Spam-Level: 
X-Spam-Status: No, score=-15.069 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 7gZqPHGUbnzn for <tram@ietfa.amsl.com>; Thu,  1 Sep 2016 07:02:09 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC6CA12DA89 for <tram@ietf.org>; Thu,  1 Sep 2016 06:48:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1624; q=dns/txt; s=iport; t=1472737728; x=1473947328; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=UtEIikOa1v/7sQIZoGBcWkaK8YDfJ+t7HO+qA2fPg/4=; b=GgVE5Ja3mBQmT6iYS8GLa6wOf9cn7YRClyvG2DdT/V3lmFBdA7KCNMgc uhJGXGwaSCgnKyqmbXp8Go/1MUrf9yRFCucOGtIYozN1+xsIaViZx1+4h TAToDSKhusD+PRMdEZ8jPAmnncQiwhBencb+MgFkHMsx0pdAai3+KeOB+ E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D/AQDtMMhX/4oNJK1dg1ABAQEBAR5Xf?= =?us-ascii?q?Ae4I4ICJIV4AoFTOBQBAgEBAQEBAQFeJ4RhAQEEAQEBODQLBQsCAQgYHhAnCyU?= =?us-ascii?q?CBA4FiEAIDrpPAQEBAQEBAQEBAQEBAQEBAQEBAQEBFwWGL4F4glWEQIMtgi8Fm?= =?us-ascii?q?VABhh+JEYFthF2JDYxIg3gBHjaEMXCFbX8BAQE?=
X-IronPort-AV: E=Sophos;i="5.30,267,1470700800"; d="scan'208";a="318061414"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 01 Sep 2016 13:48:48 +0000
Received: from XCH-RCD-006.cisco.com (xch-rcd-006.cisco.com [173.37.102.16]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u81DmmSA021417 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 1 Sep 2016 13:48:48 GMT
Received: from xch-aln-009.cisco.com (173.36.7.19) by XCH-RCD-006.cisco.com (173.37.102.16) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 1 Sep 2016 08:48:47 -0500
Received: from xch-aln-009.cisco.com ([173.36.7.19]) by XCH-ALN-009.cisco.com ([173.36.7.19]) with mapi id 15.00.1210.000; Thu, 1 Sep 2016 08:48:47 -0500
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Thread-Topic: [tram] Dedicated reviewers needed for draft-ietf-tram-stun-pmtud
Thread-Index: AQHSBByEBVEeJMqD6kW/sNkqomYyJKBk+rcA
Date: Thu, 1 Sep 2016 13:48:47 +0000
Message-ID: <50E8BB5D-43D3-48A9-8D4A-1334065DB006@cisco.com>
References: <3d8524a8-95bb-d63e-0c97-9e56140fde9b@ericsson.com> <9338c4b8-3664-83a2-8e8f-d72f0ecac034@ericsson.com> <ef071e41-2d7d-09de-549b-6973ecf97056@ericsson.com>
In-Reply-To: <ef071e41-2d7d-09de-549b-6973ecf97056@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.212.176]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A6341102124DFE4FB8C215671154443E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/0j9wjwShfrS-5f_J0y5SgEPdxLw>
Cc: Simon Perreault <sperreault@jive.com>, tram mailing list <tram@ietf.org>
Subject: Re: [tram] Dedicated reviewers needed for draft-ietf-tram-stun-pmtud
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Sep 2016 14:02:13 -0000

Thanks for the reviews.  We will try and get a new version out shortly addr=
essing these comments.

Thanks,

Gonzalo


> On Sep 1, 2016, at 2:45 AM, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson=
.com> wrote:
>=20
> Tiru, Ram: thanks for your reviews!
>=20
> Marc, Gonzalo: could you please address the comments you have received?
>=20
> Cheers,
>=20
> Gonzalo
>=20
> On 26/07/2016 7:58 PM, Gonzalo Camarillo wrote:
>> Hi,
>>=20
>> per our session in Berlin, we are still looking for volunteers to review
>> this draft. Please, contact the chairs if you would like to volunteer.
>>=20
>> Thanks,
>>=20
>> Gonzalo
>>=20
>> On 07/07/2016 9:06 AM, Gonzalo Camarillo wrote:
>>> Folks,
>>>=20
>>> we would like to get the following draft in a good-enough shape so that
>>> we can start its WGLC in the near future. For that, we need at least tw=
o
>>> dedicated reviewers:
>>>=20
>>> https://datatracker.ietf.org/doc/draft-ietf-tram-stun-pmtud/
>>>=20
>>> If you would like to volunteer to review this draft, please let the
>>> chairs know.
>>>=20
>>> We are after a general review of the draft. In addition, we would like
>>> the dedicated reviewers to provide input on the two proposed Probing
>>> Mechanisms (Simple and Complete).
>>>=20
>>> Thanks,
>>>=20
>>> Gonzalo
>>>=20
>>> _______________________________________________
>>> tram mailing list
>>> tram@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tram
>>>=20
>>=20
>=20
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram


From nobody Thu Sep  1 07:10:46 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
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 8282F12D134; Thu,  1 Sep 2016 07:10:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.849
X-Spam-Level: 
X-Spam-Status: No, score=-4.849 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, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 YOJ8QUqh9Mif; Thu,  1 Sep 2016 07:10:34 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 699B712D16B; Thu,  1 Sep 2016 07:00:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id DBDC4BE83; Thu,  1 Sep 2016 15:00:43 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qZztNdSyLE_S; Thu,  1 Sep 2016 15:00:43 +0100 (IST)
Received: from [134.226.36.93] (bilbo.dsg.cs.tcd.ie [134.226.36.93]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 1E76FBE7C; Thu,  1 Sep 2016 15:00:43 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1472738443; bh=RoaiSO3YGBjMrOfisUG3Z6ESG0B0k0/9k3Ulskp9g/Q=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=WSTL9LbbmL5+Q0y6tKhRvjkMSg3YQi1V1SAkpmIGx9dZqIqNLWTJUaT2VQ8Bm4RCe +DJlzyei9qj/HvR8IAqCtEo5Jm8/FxMjwo1plEUfxJPTe3CbpE+vs3TLF+dW2mvYXP HSlBDt6iCNzD/nkhegpegs0VGsqyF9PjiSjEskvE=
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, The IESG <iesg@ietf.org>
References: <147273453736.10136.2190061654209677850.idtracker@ietfa.amsl.com> <95abfbf9dd424ed4b6df6ddaeb28ca9f@XCH-RCD-017.cisco.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <d36c8d79-68fd-6bc1-86e6-e8882073a39b@cs.tcd.ie>
Date: Thu, 1 Sep 2016 15:00:42 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <95abfbf9dd424ed4b6df6ddaeb28ca9f@XCH-RCD-017.cisco.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms040709000002020103060801"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/CcS6HXsDd8TzGBk7qPvrKq0Lwvw>
Cc: "tram-chairs@ietf.org" <tram-chairs@ietf.org>, "sperreault@jive.com" <sperreault@jive.com>, "tram@ietf.org" <tram@ietf.org>, "draft-ietf-tram-turn-mobility@ietf.org" <draft-ietf-tram-turn-mobility@ietf.org>
Subject: Re: [tram] Stephen Farrell's Discuss on draft-ietf-tram-turn-mobility-07: (with DISCUSS)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Sep 2016 14:10:38 -0000

This is a cryptographically signed message in MIME format.

--------------ms040709000002020103060801
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hiya,

On 01/09/16 14:38, Tirumaleswar Reddy (tireddy) wrote:
>> -----Original Message----- From: tram
>> [mailto:tram-bounces@ietf.org] On Behalf Of Stephen Farrell Sent:
>> Thursday, September 1, 2016 6:26 PM To: The IESG <iesg@ietf.org>=20
>> Cc: sperreault@jive.com; tram@ietf.org; draft-ietf-tram-turn-=20
>> mobility@ietf.org; tram-chairs@ietf.org Subject: [tram] Stephen
>> Farrell's Discuss on draft-ietf-tram-turn-mobility-07: (with
>> DISCUSS)
>>=20
>> Stephen Farrell has entered the following ballot position for=20
>> draft-ietf-tram-turn-mobility-07: Discuss
>>=20
>> When responding, please keep the subject line intact and reply to
>> all email addresses included in the To and CC lines. (Feel free to
>> cut this introductory paragraph, however.)
>>=20
>>=20
>> Please refer to
>> https://www.ietf.org/iesg/statement/discuss-criteria.html for more
>> information about IESG DISCUSS and COMMENT positions.
>>=20
>>=20
>> The document, along with other ballot positions, can be found
>> here:=20
>> https://datatracker.ietf.org/doc/draft-ietf-tram-turn-mobility/
>>=20
>>=20
>>=20
>> ----------------------------------------------------------------------=

>>
>>=20
DISCUSS:
>> ----------------------------------------------------------------------=

>>
>>
>>
>>=20
Apologies if these discuss points are off-base, I was pressed for time wh=
en
>> reviewing this:-(
>>=20
>> (1) section 6 correctly says that encryption and integrity
>> protection are needed to prevent attacks, but the wording seems
>> ambiguous. Does the MUST here mean that a) TURN servers MUST use
>> strong crypto whenever they send tickets or b) if a TURN server
>> does not use strong crypto then tickets can be abused? I hope it's
>> the former, but in any case I think you need to clearly say.
>=20
> Yes, it is a). How about adding the following line to Section 6 ?=20
> TURN server MUST ensure that the tickets is authenticated and
> encrypted using strong cryptographic algorithm to prevent
> modification or eavesdropping by an attacker.

That'd be great thanks.

But are the tickets encrypted if (D)TLS is not used? I think
in any case strong authentication is what's needed, even if
encryption is also a good idea.

>=20
>>=20
>> (2) I guess the use of (D)TLS is fairly clear here. But I'm less
>> clear that things are ok for the other cases when the ticket is (I
>> guess?) visible to a network attacker. Don't you need to say that
>> in those other cases the server MUST NOT honour the ticket unless
>> the authentication mechanisms have worked out ok?
>=20
> Yes, I can update the draft to say the following: TURN client and
> server MUST use STUN long-term credential mechanism [RFC5389] or STUN
> Extension for Third-Party Authorization [RFC7635] or (D)TLS
> connection to avoid malicious users trying to impersonate the client
> using the ticket for TURN mobility.

That's also good, thanks. You could add that clients and server
MUST fail if the authentication fails. I guess that's implicit
already when you say "MUST use" but it might be no harm to call
out. (Programmers do sometimes make the most inventive errors:-)

Cheers,
S.


>=20
> -Tiru
>=20
>>=20
>>=20
>>=20
>>=20
>> _______________________________________________ tram mailing list=20
>> tram@ietf.org https://www.ietf.org/mailman/listinfo/tram


--------------ms040709000002020103060801
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CvIwggUIMIID8KADAgECAhBPzaE7pzYviUJyhmHTFBdnMA0GCSqGSIb3DQEBCwUAMHUxCzAJ
BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBD
ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGll
bnQgQ0EwHhcNMTYwMjA5MDkyODE1WhcNMTcwMjA5MDkyODE1WjBOMSIwIAYDVQQDDBlzdGVw
aGVuLmZhcnJlbGxAY3MudGNkLmllMSgwJgYJKoZIhvcNAQkBFhlzdGVwaGVuLmZhcnJlbGxA
Y3MudGNkLmllMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtuC0rYze/2JinSra
C9F2RjGdQZjNALLcW9C3WKTwYII3wBslobmHuPEYE5JaGItmzuKnAW619R1rD/kfoNWC19N3
rBZ6UX9Cmb9D9exCwYIwVuSwjrCQWGxgCtNQTrwKzCCpI790GRiMTvxvO7UmzmBrCaBLiZW5
R0fBjK5Yn6hUhAzGBkNbkIEL28cLJqH0yVz7Kl92OlzrQqTPEts5m6cDnNdY/ADfeAX18c1r
dxZqcAxhLotrCqgsVA4ilbQDMMXGTLlB5TP35HeWZuGBU7xu003rLcFLdOkD8xvpJoYZy9Kt
3oABXPS5yqtMK+XCNdqmMn+4mOtLwQSMmPCSiQIDAQABo4IBuTCCAbUwCwYDVR0PBAQDAgSw
MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAJBgNVHRMEAjAAMB0GA1UdDgQWBBQJ
QhvwQ5Fl372Z6xqo6fdn8XejTTAfBgNVHSMEGDAWgBQkgWw5Yb5JD4+3G0YrySi1J0htaDBv
BggrBgEFBQcBAQRjMGEwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbTA5
BggrBgEFBQcwAoYtaHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc2NhLmNsaWVudDEu
Y3J0MDgGA1UdHwQxMC8wLaAroCmGJ2h0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL3NjYS1jbGll
bnQxLmNybDAkBgNVHREEHTAbgRlzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllMCMGA1UdEgQc
MBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzBGBgNVHSAEPzA9MDsGCysGAQQBgbU3AQIE
MCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeTANBgkqhkiG
9w0BAQsFAAOCAQEArzrSv2C8PlBBmGuiGrzm2Wma46/KHtXmZYS0bsd43pM66Pc/MsqPE0HD
C1GzMFfwB6BfkJn8ijNSIhlgj898WzjvnpM/SO8KStjlB8719ig/xKISrOl5mX55XbFlQtX9
U6MrqRgbDIATxhD9IDr+ryvovDzChqgQj7mt2jYr4mdlRjsjod3H1VY6XglRmaaNGZfsCARM
aE/TU5SXIiqauwt5KxNGYAY67QkOBs7O1FkSXpTk7+1MmzJMF4nP8QQ5n8vhVNseF+/Wm7ai
9mtnrkLbaznMsy/ULo/C2yuLUWTbZZbf4EKNmVdme6tUDgYkFjAFOblfA7W1fSPiQGagYzCC
BeIwggPKoAMCAQICEGunin0K14jWUQr5WeTntOEwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MB4XDTE1MTIxNjAxMDAwNVoXDTMwMTIxNjAxMDAwNVowdTELMAkGA1UEBhMC
SUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5MSMwIQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL192vfDon2D9luC/dtbX64eG3XAtRmv
mCSsu1d52DXsCR58zJQbCtB2/A5uFqNxWacpXGGtTCRk9dEDBlmixEd8QiLkUfvHpJX/xKnm
VkS6Iye8wUbYzMsDzgnpazlPg19dnSqfhM+Cevdfa89VLnUztRr2cgmCfyO9Otrh7LJDPG+4
D8ZnAqDtVB8MKYJL6QgKyVhhaBc4y3bGWxKyXEtx7QIZZGxPwSkzK3WIN+VKNdkiwTubW5PI
dopmykwvIjLPqbJK7yPwFZYekKE015OsW6FV+s4DIM8UlVS8pkIsoGGJtMuWjLL4tq2hYQuu
N0jhrxK1ljz50hH23gA9cbMCAwEAAaOCAWQwggFgMA4GA1UdDwEB/wQEAwIBBjAdBgNVHSUE
FjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIBADAyBgNVHR8EKzAp
MCegJaAjhiFodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9zZnNjYS5jcmwwZgYIKwYBBQUHAQEE
WjBYMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5zdGFydHNzbC5jb20wMAYIKwYBBQUHMAKG
JGh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL2NhLmNydDAdBgNVHQ4EFgQUJIFsOWG+
SQ+PtxtGK8kotSdIbWgwHwYDVR0jBBgwFoAUTgvvGqRAW6UXaYcwyjRoQ9BBrvIwPwYDVR0g
BDgwNjA0BgRVHSAAMCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Bv
bGljeTANBgkqhkiG9w0BAQsFAAOCAgEAi+P3h+wBi4StDwECW5zhIycjBL008HACblIf26HY
0JdOruKbrWDsXUsiI0j/7Crft9S5oxvPiDtVqspBOB/y5uzSns1lZwh7sG96bYBZpcGzGxpF
NjDmQbcM3yl3WFIRS4WhNrsOY14V7y2IrUGsvetsD+bjyOngCIVeC/GmsmtbuLOzJ606tEc9
uRbhjTu/b0x2Fo+/e7UkQvKzNeo7OMhijixaULyINBfCBJb+e29bLafgu6JqjOUJ9eXXj20p
6q/CW+uVrZiSW57+q5an2P2i7hP85jQJcy5j4HzA0rSiF3YPhKGAWUxKPMAVGgcYoXzWydOv
Z3UDsTDTagXpRDIKQLZo02wrlxY6iMFqvlzsemVf1odhQJmi7Eh5TbxI40kDGcBOBHhwnaOu
mZhLP+SWJQnjpLpSlUOj95uf1zo9oz9e0NgIJoz/tdfrBzez76xtDsK0KfUDHt1/q59BvDI7
RX6gVr0fQoCyMczNzCTcRXYHY0tq2J0oT+bsb6sH2b4WVWAiJKnSYaWDjdA70qHX4mq9MIjO
/ZskmSY8wtAk24orAc0vwXgYanqNsBX5Yv4sN4Z9VyrwMdLcusP7HJgRdAGKpkR2I9U4zEsN
JQJewM7S4Jalo1DyPrLpL2nTET8ZrSl5Utp1UeGp/2deoprGevfnxWB+vHNQiu85o6MxggPM
MIIDyAIBATCBiTB1MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEpMCcG
A1UECxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIzAhBgNVBAMTGlN0YXJ0
Q29tIENsYXNzIDEgQ2xpZW50IENBAhBPzaE7pzYviUJyhmHTFBdnMA0GCWCGSAFlAwQCAQUA
oIICEzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjA5MDEx
NDAwNDJaMC8GCSqGSIb3DQEJBDEiBCBt/odVsnQZF//8VaEKqCBX/GA6X4gxE2Um31mSmlOc
ijBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMIGaBgkrBgEEAYI3EAQxgYwwgYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMw
IQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzCB
nAYLKoZIhvcNAQkQAgsxgYyggYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYD
VQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzANBgkq
hkiG9w0BAQEFAASCAQA0sd/cumxCR5WNQPfBE4LAsm0DxextTmb9LOb/UtvvqtSWyEkBovib
OhFpXeXHJcjRTZc99YgBnybJ0IPn9enQubZT3dWqX5or/bIuw/drwEt3yOBKAEahY9CGbgfu
oZl0fTTGxhA2NoZE+tF1se/nS4RlJ+H8LIaEEjOrvaQOcoZhqDIGMe3qW3X6ErYeYJkoh04L
wRlvL6QcqOmGPynhWsIZGzqFteBQLINIkvsbvtWyA13IrzO6snHPheSSBpC3gYeOTA5+PydQ
uX80h9K1yF9s5yqjFGjIovD2EColvM4S2bR/MpgQBXetRnLy8JOFamLL6zcHuTjolouXxZgX
AAAAAAAA
--------------ms040709000002020103060801--


From nobody Thu Sep  1 07:16:37 2016
Return-Path: <tireddy@cisco.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 8007212D94D; Thu,  1 Sep 2016 07:16:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.07
X-Spam-Level: 
X-Spam-Status: No, score=-15.07 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 XPYkIH6UMqoK; Thu,  1 Sep 2016 07:16:34 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9B6112D9DC; Thu,  1 Sep 2016 07:12:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5998; q=dns/txt; s=iport; t=1472739127; x=1473948727; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Mis0g5kX+SOGvZsaEzAAK7JFWS8WpwoQrVWjb1vYUZE=; b=fPNF3/Q4vFKoMuSVndhIHRugizTDmozif4Id8EaMy1HiMGYbgPL2TJsM eQnJvzHB5Q+ZZHMAhpSfviOGs7qJlj1u7GdP/nNcfEGJZ361vE4J/K272 j2WzW5K+ntVF6Vge92mZiiKpsJF4BDFrPBcHXnQg38g4muLvEfZS5wL7e g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AAAgCSNshX/4YNJK1dg1ABAQEBAR5Xf?= =?us-ascii?q?Ae4IoICJIV4AhyBNTgUAQIBAQEBAQEBXieEYQEBBAEBASEROgsFBwQCAQgRBAE?= =?us-ascii?q?BAQICIwMCAgIlCxQBCAgCBAENBQiIOAgOrWGMeAEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBARcFgQWFKoRNhBIRAQYGJ4JrgloFiC2RIwGGH4kKgXSEXYkNhnCFWIN4AR4?= =?us-ascii?q?2gnyBNXABhEyBIH8BAQE?=
X-IronPort-AV: E=Sophos;i="5.30,267,1470700800"; d="scan'208";a="147869940"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 01 Sep 2016 14:12:05 +0000
Received: from XCH-RCD-016.cisco.com (xch-rcd-016.cisco.com [173.37.102.26]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id u81EC5GZ015678 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 1 Sep 2016 14:12:05 GMT
Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-RCD-016.cisco.com (173.37.102.26) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 1 Sep 2016 09:12:05 -0500
Received: from xch-rcd-017.cisco.com ([173.37.102.27]) by XCH-RCD-017.cisco.com ([173.37.102.27]) with mapi id 15.00.1210.000; Thu, 1 Sep 2016 09:12:04 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, The IESG <iesg@ietf.org>
Thread-Topic: [tram] Stephen Farrell's Discuss on draft-ietf-tram-turn-mobility-07: (with DISCUSS)
Thread-Index: AQHSBFAm7SpipZMdr064/HdJ1esKm6Bkm3MggABiMgD//6yWsA==
Date: Thu, 1 Sep 2016 14:12:04 +0000
Message-ID: <92294450d65346dc895cef1ad7d526a8@XCH-RCD-017.cisco.com>
References: <147273453736.10136.2190061654209677850.idtracker@ietfa.amsl.com> <95abfbf9dd424ed4b6df6ddaeb28ca9f@XCH-RCD-017.cisco.com> <d36c8d79-68fd-6bc1-86e6-e8882073a39b@cs.tcd.ie>
In-Reply-To: <d36c8d79-68fd-6bc1-86e6-e8882073a39b@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.55.65]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/GJwqQvmX3Yg0ugCBfr62_AAfJQc>
Cc: "tram-chairs@ietf.org" <tram-chairs@ietf.org>, "sperreault@jive.com" <sperreault@jive.com>, "tram@ietf.org" <tram@ietf.org>, "draft-ietf-tram-turn-mobility@ietf.org" <draft-ietf-tram-turn-mobility@ietf.org>
Subject: Re: [tram] Stephen Farrell's Discuss on draft-ietf-tram-turn-mobility-07: (with DISCUSS)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Sep 2016 14:16:36 -0000

PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBTdGVwaGVuIEZhcnJlbGwgW21h
aWx0bzpzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllXQ0KPiBTZW50OiBUaHVyc2RheSwgU2VwdGVt
YmVyIDEsIDIwMTYgNzozMSBQTQ0KPiBUbzogVGlydW1hbGVzd2FyIFJlZGR5ICh0aXJlZGR5KSA8
dGlyZWRkeUBjaXNjby5jb20+OyBUaGUgSUVTRw0KPiA8aWVzZ0BpZXRmLm9yZz4NCj4gQ2M6IHNw
ZXJyZWF1bHRAaml2ZS5jb207IHRyYW1AaWV0Zi5vcmc7IGRyYWZ0LWlldGYtdHJhbS10dXJuLQ0K
PiBtb2JpbGl0eUBpZXRmLm9yZzsgdHJhbS1jaGFpcnNAaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6
IFt0cmFtXSBTdGVwaGVuIEZhcnJlbGwncyBEaXNjdXNzIG9uIGRyYWZ0LWlldGYtdHJhbS10dXJu
LW1vYmlsaXR5LQ0KPiAwNzogKHdpdGggRElTQ1VTUykNCj4gDQo+IA0KPiBIaXlhLA0KPiANCj4g
T24gMDEvMDkvMTYgMTQ6MzgsIFRpcnVtYWxlc3dhciBSZWRkeSAodGlyZWRkeSkgd3JvdGU6DQo+
ID4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tIEZyb206IHRyYW0NCj4gPj4gW21haWx0bzp0
cmFtLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBTdGVwaGVuIEZhcnJlbGwgU2VudDoN
Cj4gPj4gVGh1cnNkYXksIFNlcHRlbWJlciAxLCAyMDE2IDY6MjYgUE0gVG86IFRoZSBJRVNHIDxp
ZXNnQGlldGYub3JnPg0KPiA+PiBDYzogc3BlcnJlYXVsdEBqaXZlLmNvbTsgdHJhbUBpZXRmLm9y
ZzsgZHJhZnQtaWV0Zi10cmFtLXR1cm4tDQo+ID4+IG1vYmlsaXR5QGlldGYub3JnOyB0cmFtLWNo
YWlyc0BpZXRmLm9yZyBTdWJqZWN0OiBbdHJhbV0gU3RlcGhlbg0KPiA+PiBGYXJyZWxsJ3MgRGlz
Y3VzcyBvbiBkcmFmdC1pZXRmLXRyYW0tdHVybi1tb2JpbGl0eS0wNzogKHdpdGgNCj4gPj4gRElT
Q1VTUykNCj4gPj4NCj4gPj4gU3RlcGhlbiBGYXJyZWxsIGhhcyBlbnRlcmVkIHRoZSBmb2xsb3dp
bmcgYmFsbG90IHBvc2l0aW9uIGZvcg0KPiA+PiBkcmFmdC1pZXRmLXRyYW0tdHVybi1tb2JpbGl0
eS0wNzogRGlzY3Vzcw0KPiA+Pg0KPiA+PiBXaGVuIHJlc3BvbmRpbmcsIHBsZWFzZSBrZWVwIHRo
ZSBzdWJqZWN0IGxpbmUgaW50YWN0IGFuZCByZXBseSB0bw0KPiA+PiBhbGwgZW1haWwgYWRkcmVz
c2VzIGluY2x1ZGVkIGluIHRoZSBUbyBhbmQgQ0MgbGluZXMuIChGZWVsIGZyZWUgdG8NCj4gPj4g
Y3V0IHRoaXMgaW50cm9kdWN0b3J5IHBhcmFncmFwaCwgaG93ZXZlci4pDQo+ID4+DQo+ID4+DQo+
ID4+IFBsZWFzZSByZWZlciB0bw0KPiA+PiBodHRwczovL3d3dy5pZXRmLm9yZy9pZXNnL3N0YXRl
bWVudC9kaXNjdXNzLWNyaXRlcmlhLmh0bWwgZm9yIG1vcmUNCj4gPj4gaW5mb3JtYXRpb24gYWJv
dXQgSUVTRyBESVNDVVNTIGFuZCBDT01NRU5UIHBvc2l0aW9ucy4NCj4gPj4NCj4gPj4NCj4gPj4g
VGhlIGRvY3VtZW50LCBhbG9uZyB3aXRoIG90aGVyIGJhbGxvdCBwb3NpdGlvbnMsIGNhbiBiZSBm
b3VuZA0KPiA+PiBoZXJlOg0KPiA+PiBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9k
cmFmdC1pZXRmLXRyYW0tdHVybi1tb2JpbGl0eS8NCj4gPj4NCj4gPj4NCj4gPj4NCj4gPj4gLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLQ0KPiA+Pg0KPiA+Pg0KPiBESVNDVVNTOg0KPiA+PiAtLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+
ID4+DQo+ID4+DQo+ID4+DQo+ID4+DQo+IEFwb2xvZ2llcyBpZiB0aGVzZSBkaXNjdXNzIHBvaW50
cyBhcmUgb2ZmLWJhc2UsIEkgd2FzIHByZXNzZWQgZm9yIHRpbWUgd2hlbg0KPiA+PiByZXZpZXdp
bmcgdGhpczotKA0KPiA+Pg0KPiA+PiAoMSkgc2VjdGlvbiA2IGNvcnJlY3RseSBzYXlzIHRoYXQg
ZW5jcnlwdGlvbiBhbmQgaW50ZWdyaXR5DQo+ID4+IHByb3RlY3Rpb24gYXJlIG5lZWRlZCB0byBw
cmV2ZW50IGF0dGFja3MsIGJ1dCB0aGUgd29yZGluZyBzZWVtcw0KPiA+PiBhbWJpZ3VvdXMuIERv
ZXMgdGhlIE1VU1QgaGVyZSBtZWFuIHRoYXQgYSkgVFVSTiBzZXJ2ZXJzIE1VU1QgdXNlDQo+ID4+
IHN0cm9uZyBjcnlwdG8gd2hlbmV2ZXIgdGhleSBzZW5kIHRpY2tldHMgb3IgYikgaWYgYSBUVVJO
IHNlcnZlcg0KPiA+PiBkb2VzIG5vdCB1c2Ugc3Ryb25nIGNyeXB0byB0aGVuIHRpY2tldHMgY2Fu
IGJlIGFidXNlZD8gSSBob3BlIGl0J3MNCj4gPj4gdGhlIGZvcm1lciwgYnV0IGluIGFueSBjYXNl
IEkgdGhpbmsgeW91IG5lZWQgdG8gY2xlYXJseSBzYXkuDQo+ID4NCj4gPiBZZXMsIGl0IGlzIGEp
LiBIb3cgYWJvdXQgYWRkaW5nIHRoZSBmb2xsb3dpbmcgbGluZSB0byBTZWN0aW9uIDYgPw0KPiA+
IFRVUk4gc2VydmVyIE1VU1QgZW5zdXJlIHRoYXQgdGhlIHRpY2tldHMgaXMgYXV0aGVudGljYXRl
ZCBhbmQNCj4gPiBlbmNyeXB0ZWQgdXNpbmcgc3Ryb25nIGNyeXB0b2dyYXBoaWMgYWxnb3JpdGht
IHRvIHByZXZlbnQNCj4gPiBtb2RpZmljYXRpb24gb3IgZWF2ZXNkcm9wcGluZyBieSBhbiBhdHRh
Y2tlci4NCj4gDQo+IFRoYXQnZCBiZSBncmVhdCB0aGFua3MuDQo+IA0KPiBCdXQgYXJlIHRoZSB0
aWNrZXRzIGVuY3J5cHRlZCBpZiAoRClUTFMgaXMgbm90IHVzZWQgPyANCg0KWWVzLCB0aWNrZXQg
aXMgYWx3YXlzIGVuY3J5cHRlZC4NCk5FVzoNClRVUk4gc2VydmVyIE1VU1QgYWx3YXlzIGVuc3Vy
ZSB0aGF0IHRoZSB0aWNrZXRzIGlzIGF1dGhlbnRpY2F0ZWQgYW5kIGVuY3J5cHRlZCB1c2luZyBz
dHJvbmcgY3J5cHRvZ3JhcGhpYyBhbGdvcml0aG0gdG8gcHJldmVudCBtb2RpZmljYXRpb24gb3Ig
ZWF2ZXNkcm9wcGluZyBieSBhbiBhdHRhY2tlci4NCg0KPiBJIHRoaW5rDQo+IGluIGFueSBjYXNl
IHN0cm9uZyBhdXRoZW50aWNhdGlvbiBpcyB3aGF0J3MgbmVlZGVkLCBldmVuIGlmDQo+IGVuY3J5
cHRpb24gaXMgYWxzbyBhIGdvb2QgaWRlYS4NCj4gDQo+ID4NCj4gPj4NCj4gPj4gKDIpIEkgZ3Vl
c3MgdGhlIHVzZSBvZiAoRClUTFMgaXMgZmFpcmx5IGNsZWFyIGhlcmUuIEJ1dCBJJ20gbGVzcw0K
PiA+PiBjbGVhciB0aGF0IHRoaW5ncyBhcmUgb2sgZm9yIHRoZSBvdGhlciBjYXNlcyB3aGVuIHRo
ZSB0aWNrZXQgaXMgKEkNCj4gPj4gZ3Vlc3M/KSB2aXNpYmxlIHRvIGEgbmV0d29yayBhdHRhY2tl
ci4gRG9uJ3QgeW91IG5lZWQgdG8gc2F5IHRoYXQNCj4gPj4gaW4gdGhvc2Ugb3RoZXIgY2FzZXMg
dGhlIHNlcnZlciBNVVNUIE5PVCBob25vdXIgdGhlIHRpY2tldCB1bmxlc3MNCj4gPj4gdGhlIGF1
dGhlbnRpY2F0aW9uIG1lY2hhbmlzbXMgaGF2ZSB3b3JrZWQgb3V0IG9rPw0KPiA+DQo+ID4gWWVz
LCBJIGNhbiB1cGRhdGUgdGhlIGRyYWZ0IHRvIHNheSB0aGUgZm9sbG93aW5nOiBUVVJOIGNsaWVu
dCBhbmQNCj4gPiBzZXJ2ZXIgTVVTVCB1c2UgU1RVTiBsb25nLXRlcm0gY3JlZGVudGlhbCBtZWNo
YW5pc20gW1JGQzUzODldIG9yIFNUVU4NCj4gPiBFeHRlbnNpb24gZm9yIFRoaXJkLVBhcnR5IEF1
dGhvcml6YXRpb24gW1JGQzc2MzVdIG9yIChEKVRMUw0KPiA+IGNvbm5lY3Rpb24gdG8gYXZvaWQg
bWFsaWNpb3VzIHVzZXJzIHRyeWluZyB0byBpbXBlcnNvbmF0ZSB0aGUgY2xpZW50DQo+ID4gdXNp
bmcgdGhlIHRpY2tldCBmb3IgVFVSTiBtb2JpbGl0eS4NCj4gDQo+IFRoYXQncyBhbHNvIGdvb2Qs
IHRoYW5rcy4gWW91IGNvdWxkIGFkZCB0aGF0IGNsaWVudHMgYW5kIHNlcnZlcg0KPiBNVVNUIGZh
aWwgaWYgdGhlIGF1dGhlbnRpY2F0aW9uIGZhaWxzLiBJIGd1ZXNzIHRoYXQncyBpbXBsaWNpdA0K
PiBhbHJlYWR5IHdoZW4geW91IHNheSAiTVVTVCB1c2UiIGJ1dCBpdCBtaWdodCBiZSBubyBoYXJt
IHRvIGNhbGwNCj4gb3V0LiAoUHJvZ3JhbW1lcnMgZG8gc29tZXRpbWVzIG1ha2UgdGhlIG1vc3Qg
aW52ZW50aXZlIGVycm9yczotKQ0KDQpTdXJlLCB3aWxsIGFsc28gYWRkIHRoZSBmb2xsb3dpbmcg
bGluZToNCklmIChEKVRMUyBpcyBub3QgdXNlZCBvciAoRClUTFMgaGFuZHNoYWtlIGZhaWxzIGFu
ZCBhdXRoZW50aWNhdGlvbiBhbHNvIGZhaWxzIHRoZW4gVFVSTiBjbGllbnQgYW5kIHNlcnZlciBN
VVNUIGZhaWwsIGFuZCBub3QgcHJvY2VlZCB3aXRoIFRVUk4gbW9iaWxpdHkuDQoNCkNoZWVycywN
Ci1UaXJ1DQoNCj4gDQo+IENoZWVycywNCj4gUy4NCj4gDQo+IA0KPiA+DQo+ID4gLVRpcnUNCj4g
Pg0KPiA+Pg0KPiA+Pg0KPiA+Pg0KPiA+Pg0KPiA+PiBfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXyB0cmFtIG1haWxpbmcgbGlzdA0KPiA+PiB0cmFtQGlldGYu
b3JnIGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdHJhbQ0KDQo=


From nobody Thu Sep  1 07:20:00 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
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 8814E12D9A3; Thu,  1 Sep 2016 07:19:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.849
X-Spam-Level: 
X-Spam-Status: No, score=-4.849 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, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 M-N2SDl-nfO8; Thu,  1 Sep 2016 07:19:49 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFAE212D98E; Thu,  1 Sep 2016 07:18:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 9ABD8BE5D; Thu,  1 Sep 2016 15:18:21 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jDFSUAAuVPmI; Thu,  1 Sep 2016 15:18:21 +0100 (IST)
Received: from [134.226.36.93] (bilbo.dsg.cs.tcd.ie [134.226.36.93]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 07950BE58; Thu,  1 Sep 2016 15:18:21 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1472739501; bh=oI8oEDSPQlXsG+bCqCy9PQfkkRoyMJlsDO36qM03jv4=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=ZkaD9WbT3J04RTrYMZMZxs5pFAnmWmFKqnnz7RI4T+18BiSIOkh1nSw+8CXUTh1tv ScEPvZGxprkrfK4ohiTuIxc/xwbP+HxeT+Lm0xS1mkYpnakXA6F3XugV7OWZEg+y5C 0vBYfV//e4VYXM+CQ2HJ5EMo2PwkfIF5hMRfH5x0=
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, The IESG <iesg@ietf.org>
References: <147273453736.10136.2190061654209677850.idtracker@ietfa.amsl.com> <95abfbf9dd424ed4b6df6ddaeb28ca9f@XCH-RCD-017.cisco.com> <d36c8d79-68fd-6bc1-86e6-e8882073a39b@cs.tcd.ie> <92294450d65346dc895cef1ad7d526a8@XCH-RCD-017.cisco.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <1d71f94a-9386-3139-9801-d2f15624204a@cs.tcd.ie>
Date: Thu, 1 Sep 2016 15:18:20 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <92294450d65346dc895cef1ad7d526a8@XCH-RCD-017.cisco.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms050906020504040304050907"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/FgVjf2k6elPPMUDhf9VvcJiSxpQ>
Cc: "draft-ietf-tram-turn-mobility@ietf.org" <draft-ietf-tram-turn-mobility@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>, "tram@ietf.org" <tram@ietf.org>, "sperreault@jive.com" <sperreault@jive.com>
Subject: Re: [tram] Stephen Farrell's Discuss on draft-ietf-tram-turn-mobility-07: (with DISCUSS)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Sep 2016 14:19:54 -0000

This is a cryptographically signed message in MIME format.

--------------ms050906020504040304050907
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hi Tiru,

Those are all good. Shoot out a rev and I'll clear,

Thanks,
S.

On 01/09/16 15:12, Tirumaleswar Reddy (tireddy) wrote:
>> -----Original Message-----
>> From: Stephen Farrell [mailto:stephen.farrell@cs.tcd.ie]
>> Sent: Thursday, September 1, 2016 7:31 PM
>> To: Tirumaleswar Reddy (tireddy) <tireddy@cisco.com>; The IESG
>> <iesg@ietf.org>
>> Cc: sperreault@jive.com; tram@ietf.org; draft-ietf-tram-turn-
>> mobility@ietf.org; tram-chairs@ietf.org
>> Subject: Re: [tram] Stephen Farrell's Discuss on draft-ietf-tram-turn-=
mobility-
>> 07: (with DISCUSS)
>>
>>
>> Hiya,
>>
>> On 01/09/16 14:38, Tirumaleswar Reddy (tireddy) wrote:
>>>> -----Original Message----- From: tram
>>>> [mailto:tram-bounces@ietf.org] On Behalf Of Stephen Farrell Sent:
>>>> Thursday, September 1, 2016 6:26 PM To: The IESG <iesg@ietf.org>
>>>> Cc: sperreault@jive.com; tram@ietf.org; draft-ietf-tram-turn-
>>>> mobility@ietf.org; tram-chairs@ietf.org Subject: [tram] Stephen
>>>> Farrell's Discuss on draft-ietf-tram-turn-mobility-07: (with
>>>> DISCUSS)
>>>>
>>>> Stephen Farrell has entered the following ballot position for
>>>> draft-ietf-tram-turn-mobility-07: Discuss
>>>>
>>>> When responding, please keep the subject line intact and reply to
>>>> all email addresses included in the To and CC lines. (Feel free to
>>>> cut this introductory paragraph, however.)
>>>>
>>>>
>>>> Please refer to
>>>> https://www.ietf.org/iesg/statement/discuss-criteria.html for more
>>>> information about IESG DISCUSS and COMMENT positions.
>>>>
>>>>
>>>> The document, along with other ballot positions, can be found
>>>> here:
>>>> https://datatracker.ietf.org/doc/draft-ietf-tram-turn-mobility/
>>>>
>>>>
>>>>
>>>> --------------------------------------------------------------------=
--
>>>>
>>>>
>> DISCUSS:
>>>> --------------------------------------------------------------------=
--
>>>>
>>>>
>>>>
>>>>
>> Apologies if these discuss points are off-base, I was pressed for time=
 when
>>>> reviewing this:-(
>>>>
>>>> (1) section 6 correctly says that encryption and integrity
>>>> protection are needed to prevent attacks, but the wording seems
>>>> ambiguous. Does the MUST here mean that a) TURN servers MUST use
>>>> strong crypto whenever they send tickets or b) if a TURN server
>>>> does not use strong crypto then tickets can be abused? I hope it's
>>>> the former, but in any case I think you need to clearly say.
>>>
>>> Yes, it is a). How about adding the following line to Section 6 ?
>>> TURN server MUST ensure that the tickets is authenticated and
>>> encrypted using strong cryptographic algorithm to prevent
>>> modification or eavesdropping by an attacker.
>>
>> That'd be great thanks.
>>
>> But are the tickets encrypted if (D)TLS is not used ?=20
>=20
> Yes, ticket is always encrypted.
> NEW:
> TURN server MUST always ensure that the tickets is authenticated and en=
crypted using strong cryptographic algorithm to prevent modification or e=
avesdropping by an attacker.
>=20
>> I think
>> in any case strong authentication is what's needed, even if
>> encryption is also a good idea.
>>
>>>
>>>>
>>>> (2) I guess the use of (D)TLS is fairly clear here. But I'm less
>>>> clear that things are ok for the other cases when the ticket is (I
>>>> guess?) visible to a network attacker. Don't you need to say that
>>>> in those other cases the server MUST NOT honour the ticket unless
>>>> the authentication mechanisms have worked out ok?
>>>
>>> Yes, I can update the draft to say the following: TURN client and
>>> server MUST use STUN long-term credential mechanism [RFC5389] or STUN=

>>> Extension for Third-Party Authorization [RFC7635] or (D)TLS
>>> connection to avoid malicious users trying to impersonate the client
>>> using the ticket for TURN mobility.
>>
>> That's also good, thanks. You could add that clients and server
>> MUST fail if the authentication fails. I guess that's implicit
>> already when you say "MUST use" but it might be no harm to call
>> out. (Programmers do sometimes make the most inventive errors:-)
>=20
> Sure, will also add the following line:
> If (D)TLS is not used or (D)TLS handshake fails and authentication also=
 fails then TURN client and server MUST fail, and not proceed with TURN m=
obility.
>=20
> Cheers,
> -Tiru
>=20
>>
>> Cheers,
>> S.
>>
>>
>>>
>>> -Tiru
>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________ tram mailing list
>>>> tram@ietf.org https://www.ietf.org/mailman/listinfo/tram
>=20


--------------ms050906020504040304050907
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CvIwggUIMIID8KADAgECAhBPzaE7pzYviUJyhmHTFBdnMA0GCSqGSIb3DQEBCwUAMHUxCzAJ
BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBD
ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGll
bnQgQ0EwHhcNMTYwMjA5MDkyODE1WhcNMTcwMjA5MDkyODE1WjBOMSIwIAYDVQQDDBlzdGVw
aGVuLmZhcnJlbGxAY3MudGNkLmllMSgwJgYJKoZIhvcNAQkBFhlzdGVwaGVuLmZhcnJlbGxA
Y3MudGNkLmllMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtuC0rYze/2JinSra
C9F2RjGdQZjNALLcW9C3WKTwYII3wBslobmHuPEYE5JaGItmzuKnAW619R1rD/kfoNWC19N3
rBZ6UX9Cmb9D9exCwYIwVuSwjrCQWGxgCtNQTrwKzCCpI790GRiMTvxvO7UmzmBrCaBLiZW5
R0fBjK5Yn6hUhAzGBkNbkIEL28cLJqH0yVz7Kl92OlzrQqTPEts5m6cDnNdY/ADfeAX18c1r
dxZqcAxhLotrCqgsVA4ilbQDMMXGTLlB5TP35HeWZuGBU7xu003rLcFLdOkD8xvpJoYZy9Kt
3oABXPS5yqtMK+XCNdqmMn+4mOtLwQSMmPCSiQIDAQABo4IBuTCCAbUwCwYDVR0PBAQDAgSw
MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAJBgNVHRMEAjAAMB0GA1UdDgQWBBQJ
QhvwQ5Fl372Z6xqo6fdn8XejTTAfBgNVHSMEGDAWgBQkgWw5Yb5JD4+3G0YrySi1J0htaDBv
BggrBgEFBQcBAQRjMGEwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbTA5
BggrBgEFBQcwAoYtaHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc2NhLmNsaWVudDEu
Y3J0MDgGA1UdHwQxMC8wLaAroCmGJ2h0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL3NjYS1jbGll
bnQxLmNybDAkBgNVHREEHTAbgRlzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllMCMGA1UdEgQc
MBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzBGBgNVHSAEPzA9MDsGCysGAQQBgbU3AQIE
MCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeTANBgkqhkiG
9w0BAQsFAAOCAQEArzrSv2C8PlBBmGuiGrzm2Wma46/KHtXmZYS0bsd43pM66Pc/MsqPE0HD
C1GzMFfwB6BfkJn8ijNSIhlgj898WzjvnpM/SO8KStjlB8719ig/xKISrOl5mX55XbFlQtX9
U6MrqRgbDIATxhD9IDr+ryvovDzChqgQj7mt2jYr4mdlRjsjod3H1VY6XglRmaaNGZfsCARM
aE/TU5SXIiqauwt5KxNGYAY67QkOBs7O1FkSXpTk7+1MmzJMF4nP8QQ5n8vhVNseF+/Wm7ai
9mtnrkLbaznMsy/ULo/C2yuLUWTbZZbf4EKNmVdme6tUDgYkFjAFOblfA7W1fSPiQGagYzCC
BeIwggPKoAMCAQICEGunin0K14jWUQr5WeTntOEwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MB4XDTE1MTIxNjAxMDAwNVoXDTMwMTIxNjAxMDAwNVowdTELMAkGA1UEBhMC
SUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5MSMwIQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL192vfDon2D9luC/dtbX64eG3XAtRmv
mCSsu1d52DXsCR58zJQbCtB2/A5uFqNxWacpXGGtTCRk9dEDBlmixEd8QiLkUfvHpJX/xKnm
VkS6Iye8wUbYzMsDzgnpazlPg19dnSqfhM+Cevdfa89VLnUztRr2cgmCfyO9Otrh7LJDPG+4
D8ZnAqDtVB8MKYJL6QgKyVhhaBc4y3bGWxKyXEtx7QIZZGxPwSkzK3WIN+VKNdkiwTubW5PI
dopmykwvIjLPqbJK7yPwFZYekKE015OsW6FV+s4DIM8UlVS8pkIsoGGJtMuWjLL4tq2hYQuu
N0jhrxK1ljz50hH23gA9cbMCAwEAAaOCAWQwggFgMA4GA1UdDwEB/wQEAwIBBjAdBgNVHSUE
FjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIBADAyBgNVHR8EKzAp
MCegJaAjhiFodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9zZnNjYS5jcmwwZgYIKwYBBQUHAQEE
WjBYMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5zdGFydHNzbC5jb20wMAYIKwYBBQUHMAKG
JGh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL2NhLmNydDAdBgNVHQ4EFgQUJIFsOWG+
SQ+PtxtGK8kotSdIbWgwHwYDVR0jBBgwFoAUTgvvGqRAW6UXaYcwyjRoQ9BBrvIwPwYDVR0g
BDgwNjA0BgRVHSAAMCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Bv
bGljeTANBgkqhkiG9w0BAQsFAAOCAgEAi+P3h+wBi4StDwECW5zhIycjBL008HACblIf26HY
0JdOruKbrWDsXUsiI0j/7Crft9S5oxvPiDtVqspBOB/y5uzSns1lZwh7sG96bYBZpcGzGxpF
NjDmQbcM3yl3WFIRS4WhNrsOY14V7y2IrUGsvetsD+bjyOngCIVeC/GmsmtbuLOzJ606tEc9
uRbhjTu/b0x2Fo+/e7UkQvKzNeo7OMhijixaULyINBfCBJb+e29bLafgu6JqjOUJ9eXXj20p
6q/CW+uVrZiSW57+q5an2P2i7hP85jQJcy5j4HzA0rSiF3YPhKGAWUxKPMAVGgcYoXzWydOv
Z3UDsTDTagXpRDIKQLZo02wrlxY6iMFqvlzsemVf1odhQJmi7Eh5TbxI40kDGcBOBHhwnaOu
mZhLP+SWJQnjpLpSlUOj95uf1zo9oz9e0NgIJoz/tdfrBzez76xtDsK0KfUDHt1/q59BvDI7
RX6gVr0fQoCyMczNzCTcRXYHY0tq2J0oT+bsb6sH2b4WVWAiJKnSYaWDjdA70qHX4mq9MIjO
/ZskmSY8wtAk24orAc0vwXgYanqNsBX5Yv4sN4Z9VyrwMdLcusP7HJgRdAGKpkR2I9U4zEsN
JQJewM7S4Jalo1DyPrLpL2nTET8ZrSl5Utp1UeGp/2deoprGevfnxWB+vHNQiu85o6MxggPM
MIIDyAIBATCBiTB1MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEpMCcG
A1UECxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIzAhBgNVBAMTGlN0YXJ0
Q29tIENsYXNzIDEgQ2xpZW50IENBAhBPzaE7pzYviUJyhmHTFBdnMA0GCWCGSAFlAwQCAQUA
oIICEzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjA5MDEx
NDE4MjBaMC8GCSqGSIb3DQEJBDEiBCBO0sTNciN7hn0tQU76sww/KDs6gbju2RXphqIJe0F8
jDBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMIGaBgkrBgEEAYI3EAQxgYwwgYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMw
IQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzCB
nAYLKoZIhvcNAQkQAgsxgYyggYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYD
VQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzANBgkq
hkiG9w0BAQEFAASCAQCzPDCg+0HJ1xfHdwJ6m8ozu4n6u7NyJsQEDeLzkAYH+7su+5X/0471
zBr5RJrcdtVAC2ImWxcPwiw3pIjrouBzoWQ46QPpPaGcLJ4ZIeEvBOqFohY1AOr82rJHn9pu
lnwcMc4DJr56QHex23sd4u406JbJoKd+cMBb+YK4QiZhfyV0B/NYllp8lSn0yb7AYGmy194+
2/2IjJIZqbh9AjTjxPq00cb16E72HuWhR6VBCX+d16N3OpgwsyqMk24BGncMxFPNoHALgogR
sq5S14CJqoXWEskHIpRc2vJfDTHlvL7WVEuCAQ9cr1IL/6xiJXNBFquviQi8srTssudvd7Oi
AAAAAAAA
--------------ms050906020504040304050907--


From nobody Thu Sep  1 07:24:05 2016
Return-Path: <tireddy@cisco.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 D821512D984; Thu,  1 Sep 2016 07:24:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.069
X-Spam-Level: 
X-Spam-Status: No, score=-15.069 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 oe1ak7q0mdwk; Thu,  1 Sep 2016 07:24:02 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCDF612D986; Thu,  1 Sep 2016 07:24:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2222; q=dns/txt; s=iport; t=1472739841; x=1473949441; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=Ak9IGqXlVBl06tSP6UJPRNJ0BMQMzVwRvRj19vhYyG8=; b=VgLeeec1xX4FJu8BEfi8LupBgxuO9rrdJaIcDoZAXY+NHjq9hG/WhoGi 6diYaYBVwxGY48IiUwkWsGTUhRQ0KSAloDsGxxnHlurzLxG1Ttd7PRWUC jrJU8s2AjSvcLEwfMeEl6wrpj9UjPwUfPb0koSnh500zlpXfeGSwAopqB g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AAAgAkOchX/4QNJK1dg1ABAQEBAR5Xf?= =?us-ascii?q?AerbYw1ggImhXYCHIE1OBQBAgEBAQEBAQFeJ4RhAQEEASMRUQQCAQgRBAEBAwI?= =?us-ascii?q?jAwICAh8RFAEICAIEARIIiCYDDwgOrWuJOw2DLwEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBARcFgQWFKoRNgkOBZAODGIJaBZkcNAGGH4Y+gkyBdI1qhnCBT4QJg3gBHja?= =?us-ascii?q?EMXCEP4EufwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.30,267,1470700800"; d="scan'208";a="146424498"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 01 Sep 2016 14:24:00 +0000
Received: from XCH-ALN-016.cisco.com (xch-aln-016.cisco.com [173.36.7.26]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id u81EO08r014542 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 1 Sep 2016 14:24:00 GMT
Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-ALN-016.cisco.com (173.36.7.26) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 1 Sep 2016 09:24:00 -0500
Received: from xch-rcd-017.cisco.com ([173.37.102.27]) by XCH-RCD-017.cisco.com ([173.37.102.27]) with mapi id 15.00.1210.000; Thu, 1 Sep 2016 09:24:00 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Simon Perreault <sperreault@jive.com>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, "tram@ietf.org" <tram@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>
Thread-Topic: Discuss ballot positions on draft-ietf-tram-turn-server-discovery
Thread-Index: AQHSBFGmaZNBI5g1FU+H96yZbt6fIqBkonSA
Date: Thu, 1 Sep 2016 14:23:59 +0000
Message-ID: <1fd125ccd3a84a4f9240b6f8d488bd5b@XCH-RCD-017.cisco.com>
References: <CAKKJt-cQB8wtv_7Fg_99EanpAj+PFKb8hrjerv4RmrRYFE5tpA@mail.gmail.com>
In-Reply-To: <CAKKJt-cQB8wtv_7Fg_99EanpAj+PFKb8hrjerv4RmrRYFE5tpA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.55.65]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/0RpWRUFTByj4oXTXBzOG5BGUByQ>
Subject: Re: [tram] Discuss ballot positions on draft-ietf-tram-turn-server-discovery
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Sep 2016 14:24:05 -0000

PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBTcGVuY2VyIERhd2tpbnMgYXQg
SUVURiBbbWFpbHRvOnNwZW5jZXJkYXdraW5zLmlldGZAZ21haWwuY29tXQ0KPiBTZW50OiBUaHVy
c2RheSwgU2VwdGVtYmVyIDEsIDIwMTYgNjoxMSBQTQ0KPiBUbzogU2ltb24gUGVycmVhdWx0IDxz
cGVycmVhdWx0QGppdmUuY29tPjsgZHJhZnQtaWV0Zi10cmFtLXR1cm4tc2VydmVyLQ0KPiBkaXNj
b3ZlcnlAaWV0Zi5vcmc7IHRyYW1AaWV0Zi5vcmc7IHRyYW0tY2hhaXJzQGlldGYub3JnDQo+IFN1
YmplY3Q6IERpc2N1c3MgYmFsbG90IHBvc2l0aW9ucyBvbiBkcmFmdC1pZXRmLXRyYW0tdHVybi1z
ZXJ2ZXItZGlzY292ZXJ5DQo+IA0KPiBEZWFyIEF1dGhvcnMsDQo+IA0KPiBJIGhhdmVuJ3Qgc2Vl
biByZXNwb25zZXMgdG8gRGlzY3VzcyBwb3NpdGlvbnMgZnJvbSBCZW4gYW5kIGZyb20gU3VyZXNo
IG9uDQo+IHRoaXMgZHJhZnQsIGF0IGxlYXN0IG5vdCB5ZXQgKHRoYW5rIHlvdSBmb3IgdGhlIHF1
aWNrIHJlc3BvbnNlcyB0byB0aGUgRGlzY3Vzcw0KPiBwb3NpdGlvbnMgZnJvbSBBbGV4ZXksIEth
dGhsZWVuLCBhbmQgVGVycnkpLg0KDQpJIGp1c3Qgbm93IGZpbmlzaGVkIHRha2luZyBjYXJlIG9m
IGNvbW1lbnRzIGFuZCBkaXNjdXNzIHBvaW50cyBvbiBUVVJOIE1vYmlsaXR5IDopDQoNCj4gDQo+
IEJlbidzIHNlZW1zIHByZXR0eSBjbGVhciwgYnV0IEkgd2FudGVkIHRvIG1ha2Ugc3VyZSBTdXJl
c2gncyBEaXNjdXNzIGlzIGNsZWFyDQo+IGVub3VnaCBmb3IgeW91IHRvIHdvcmsgd2l0aC4gSWYg
eW91IGhhdmUgYSBjaGFuY2UgdG8gbGV0IG1lIGtub3cgc29tZXRoaW5nDQo+IGFib3V0IHRoYXQg
aW4gdGhlIG5leHQgY291cGxlIG9mIGhvdXJzIChwcmUtdGVsZWNoYXQpLCB0aGF0IHdvdWxkIGJl
IGF3ZXNvbWUuDQoNClN1cmVzaCBkaXNjdXNzIGxvb2tzIGNsZWFyIHRvIG1lLiBUaGUgcG9pbnRz
IHJhaXNlZCBieSBCZW4ncyBhbmQgS2F0aGxlZW4gbmVlZHMgdG8gZGlzY3Vzc2VkIGluIHRoZSBX
Ry4gTXkgaW5pdGlhbCB0aG91Z2h0czoNCmEpV2Ugd2lsbCBoYXZlIHRvIGRpc2N1c3MgYW5kIHVw
ZGF0ZSBzZWN1cml0eSBjb25zaWRlcmF0aW9ucyBzZWN0aW9uIHRoYXQgaWYgU1RVTiBhdXRoZW50
aWNhdGlvbiBpcyBvcHRpb25hbCB0aGVuIHRoZSBFbnRlcnByaXNlL0FjY2VzcyBuZXR3b3JrcyBt
dXN0IHVzZSB2YXJpb3VzIG1lY2hhbmlzbXMgbGlrZSBzdWJzY3JpYmVyLXF1b3RhLCBwZXJtaXQg
cmVxdWVzdHMgdG8gdGhlIFRVUk4gc2VydmVyIG9ubHkgZnJvbSBzcGVjaWZpYyBJUCBhZGRyZXNz
ZXMsIEluZ3Jlc3MgRmlsdGVyaW5nIGV0Yy4NCmIpVGhpcyBkcmFmdCB3aWxsIGhhdmUgdG8gdXBk
YXRlIFJGQzU3NjYuDQpjKURvIHdlIHJlYWxseSB3YW50IHRvIG1ha2UgSS1ELmlldGYtcnRjd2Vi
LXJldHVybiBub3JtYXRpdmUgKEkgcHJlZmVyIG5vdCkgPw0KDQotVGlydQ0KDQo+IA0KPiBUaGUg
ZGF0YXRyYWNrZXIgcGFnZSB3aXRoIGJhbGxvdCBwb3NpdGlvbnMgaXMgKGFzIGFsd2F5cykgYXQN
Cj4gaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi10cmFtLXR1cm4t
c2VydmVyLWRpc2NvdmVyeS9iYWxsb3QvDQo=


From nobody Thu Sep  1 08:11:59 2016
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 E29A512DA26; Thu,  1 Sep 2016 08:11:52 -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>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.31.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147274271292.10108.9388693920966514843.idtracker@ietfa.amsl.com>
Date: Thu, 01 Sep 2016 08:11:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/dYPwl5jrxMIRLQij9Wz7qG5-L2s>
Cc: tram@ietf.org
Subject: [tram] I-D Action: draft-ietf-tram-turn-mobility-08.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Sep 2016 15:11:53 -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 of the IETF.

        Title           : Mobility with TURN
        Authors         : Tirumaleswar Reddy
                          Dan Wing
                          Prashanth Patil
                          Paal-Erik Martinsen
	Filename        : draft-ietf-tram-turn-mobility-08.txt
	Pages           : 14
	Date            : 2016-09-01

Abstract:
   It is desirable to minimize traffic disruption caused by changing IP
   address during a mobility event.  One mechanism to minimize
   disruption is to expose a shorter network path to the mobility event
   so only the local network elements are aware of the changed IP
   address but the remote peer is unaware of the changed IP address.

   This draft provides such an IP address mobility solution using
   Traversal Using Relays around NAT (TURN).  This is achieved by
   allowing a client to retain an allocation on the TURN server when the
   IP address of the client changes.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-tram-turn-mobility-08

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


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 Thu Sep  1 08:23:05 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
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 45D9C12DA3E; Thu,  1 Sep 2016 08:23:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.31.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147274338124.10160.33595401137876747.idtracker@ietfa.amsl.com>
Date: Thu, 01 Sep 2016 08:23:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/FllCa5QDhFogPWsWuvmITo7C4f4>
Cc: sperreault@jive.com, tram@ietf.org, draft-ietf-tram-turn-mobility@ietf.org, tram-chairs@ietf.org
Subject: [tram] Stephen Farrell's No Objection on draft-ietf-tram-turn-mobility-08: (with COMMENT)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Sep 2016 15:23:01 -0000

Stephen Farrell has entered the following ballot position for
draft-ietf-tram-turn-mobility-08: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-tram-turn-mobility/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


Tbanks for so speedily handling my discuss points.



From nobody Thu Sep  1 20:02:46 2016
Return-Path: <tireddy@cisco.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 396F512DB71; Thu,  1 Sep 2016 20:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.069
X-Spam-Level: 
X-Spam-Status: No, score=-15.069 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 7qVPyp4_Md3y; Thu,  1 Sep 2016 20:02:42 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F71C12DB5C; Thu,  1 Sep 2016 20:02:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3077; q=dns/txt; s=iport; t=1472785362; x=1473994962; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=6L8iP0b6XymmuvHaYMI5BWk/lEQMAo17g1G2fO9LiMs=; b=lqb13BcYwmsHUFLiTrvkfBp65S8LguvCaaKZRQrbGXkeGdsYdSrPxxPH OKtQRtRrdjU1D4ctYPtVoYluqAfna+2dKrk9PSDI3Ih7kjrD3mXg5PDFl Ak2Pcr/MWkktulEVhUG3hX9vA+sfz4hLd5r5rZBoYqmnp02U+dIk9zXMd U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BjAQB968hX/4kNJK1UCRkBAQEBAQEBA?= =?us-ascii?q?QEBAYMsAQEBAQEeV3wHjSeodIIPggIkhXgCgVk4FAECAQEBAQEBAV4nhGEBAQE?= =?us-ascii?q?DATo/BQcEAgEIDgMEAQEBHgkHMhQJCAIEDgUIiDoIDrogAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBFwWGL4RNhBIHCgEGSIUqBYgthXeLLgGGIIkMgXWEXokNjEmDeQE?= =?us-ascii?q?eNoJ8gTVwAYRQDRcHgQJ/AQEB?=
X-IronPort-AV: E=Sophos;i="5.30,269,1470700800"; d="scan'208";a="147317336"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 02 Sep 2016 03:02:14 +0000
Received: from XCH-ALN-016.cisco.com (xch-aln-016.cisco.com [173.36.7.26]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u8232Egn001136 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 2 Sep 2016 03:02:14 GMT
Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-ALN-016.cisco.com (173.36.7.26) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 1 Sep 2016 22:02:13 -0500
Received: from xch-rcd-017.cisco.com ([173.37.102.27]) by XCH-RCD-017.cisco.com ([173.37.102.27]) with mapi id 15.00.1210.000; Thu, 1 Sep 2016 22:02:13 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Thread-Topic: Alexey Melnikov's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
Thread-Index: AQHSA54fDJMoqK9Hq0C6sHCN+3QJCaBj/4YwgACPJ4CAAPZdcA==
Date: Fri, 2 Sep 2016 03:02:13 +0000
Message-ID: <c6baeabd62854628aaadfb75ac7d250a@XCH-RCD-017.cisco.com>
References: <147265807396.13320.16720268350417791956.idtracker@ietfa.amsl.com> <21b2559f2a234c64b47595eb4615c661@XCH-RCD-017.cisco.com> <932002F5-18BA-46E7-9C71-EC985A0FCFDC@fastmail.fm>
In-Reply-To: <932002F5-18BA-46E7-9C71-EC985A0FCFDC@fastmail.fm>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.43.213]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/0KPTcXv1HawZvGFQ2z5mXu_YgLo>
Cc: "tram@ietf.org" <tram@ietf.org>, Simon Perreault <sperreault@jive.com>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, The IESG <iesg@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>
Subject: Re: [tram] Alexey Melnikov's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 03:02:44 -0000

> -----Original Message-----
> From: Alexey Melnikov [mailto:aamelnikov@fastmail.fm]
> Sent: Thursday, September 1, 2016 12:49 PM
> To: Tirumaleswar Reddy (tireddy) <tireddy@cisco.com>
> Cc: The IESG <iesg@ietf.org>; draft-ietf-tram-turn-server-discovery@ietf.=
org;
> Simon Perreault <sperreault@jive.com>; tram-chairs@ietf.org; tram@ietf.or=
g
> Subject: Re: Alexey Melnikov's Discuss on draft-ietf-tram-turn-server-
> discovery-09: (with DISCUSS)
>=20
> Hi,
>=20
> On 1 Sep 2016, at 04:48, Tirumaleswar Reddy (tireddy) <tireddy@cisco.com>
> wrote:
>=20
> >> -----Original Message-----
> >> From: Alexey Melnikov [mailto:aamelnikov@fastmail.fm]
> >> Sent: Wednesday, August 31, 2016 9:11 PM
> >> To: The IESG <iesg@ietf.org>
> >> Cc: draft-ietf-tram-turn-server-discovery@ietf.org; Simon Perreault
> >> <sperreault@jive.com>; tram-chairs@ietf.org; sperreault@jive.com;
> >> tram@ietf.org
> >> Subject: Alexey Melnikov's Discuss on
> >> draft-ietf-tram-turn-server-discovery-
> >> 09: (with DISCUSS)
> >>
> >> Alexey Melnikov has entered the following ballot position for
> >> draft-ietf-tram-turn-server-discovery-09: Discuss
> >>
> >> When responding, please keep the subject line intact and reply to all
> >> email addresses included in the To and CC lines. (Feel free to cut
> >> this introductory paragraph, however.)
> >>
> >>
> >> Please refer to
> >> https://www.ietf.org/iesg/statement/discuss-criteria.html
> >> for more information about IESG DISCUSS and COMMENT positions.
> >>
> >>
> >> The document, along with other ballot positions, can be found here:
> >> https://datatracker.ietf.org/doc/draft-ietf-tram-turn-server-discover
> >> y/
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> -
> >> DISCUSS:
> >> ---------------------------------------------------------------------
> >> -
> >>
> >> In Section 9:
> >>
> >> o  For certificate-based authentication, a pre-populated trust anchor
> >>      store [RFC6024] allows a TURN client to perform path validation
> >>      for the server certificate obtained during the (D)TLS handshake.
> >>
> >>      If the client used a domain name to discover the TURN server, tha=
t
> >>      domain name also provides a mechanism for validation of the TURN
> >>      server.  The client MUST use the rules and guidelines given in
> >>      section 6 of [RFC6125] to validate the TURN server identity.
> >>
> >> I am glad that you are referencing RFC 6125, but unfortunately you
> >> don't provide enough details. Please add details as specified in
> >> Section 3 of RFC
> >> 6125 to your document.
> >
> > Sure, will add the following lines:
> > Certification authorities that issue TURN server certificates SHOULD su=
pport
> the DNS-ID and SRV-ID identifier types. TURN service providers SHOULD
> include the DNS-ID and SRV-ID identifier types in certificate requests.
>=20
> What about use of CN-IDs and URI-IDs?=20

Yes, added.

> Wildcards ?

I don't think wildcards are required.

-Tiru


From nobody Fri Sep  2 01:19:52 2016
Return-Path: <aamelnikov@fastmail.fm>
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 BF11012D66A; Fri,  2 Sep 2016 01:19:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=COmiBOug; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=Gv2lzCp4
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 tMqKx-ZY6_B4; Fri,  2 Sep 2016 01:19:44 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDBDF12D620; Fri,  2 Sep 2016 01:19:43 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 1F4D5202F7; Fri,  2 Sep 2016 04:19:43 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Fri, 02 Sep 2016 04:19:43 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=26zAMECgkKWBBX8SseQmhkodFtA=; b=COmiBO ugbNich61Lm6yZmJWI6nzZv1iplZ7us+Hwuvp9d3aFtQybHan0PDcVBjIGfuOMpG 2mYFPQrCWEbZ1ZfJmMBo7ZaHlKY7v59A63h9ntH+JSfmAX1zC/sF7/wbik8xTwjQ WPblbTNQzZsz7U9vXUx/1lesAmNj7YShJNB44=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=26zAMECgkKWBBX8 SseQmhkodFtA=; b=Gv2lzCp4tcn/yzkna/6JL5l/2FDknvVjAwHTU4T9M+LFEi3 YGh6kWfolJ7MnZjdX4RLTUtafTHDf96nFFvchcmlotdwx+Fbib5jV8Cmn0d4+/ES EMGeYe/olb8FTZxknEvMe9ClTn54k5C1gEMLKMGBNF2SD84WEQ07HV1k8nS0=
X-Sasl-enc: HFYp5sgX1/MolekFTnE0lx02t6J18TWqxi7yjJi/nQBV 1472804382
Received: from [10.9.76.95] (unknown [185.69.144.25]) by mail.messagingengine.com (Postfix) with ESMTPA id B70A3F29CC; Fri,  2 Sep 2016 04:19:42 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPhone Mail (13G35)
In-Reply-To: <c6baeabd62854628aaadfb75ac7d250a@XCH-RCD-017.cisco.com>
Date: Fri, 2 Sep 2016 09:32:08 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <12ED9DC3-7950-4517-A005-2B29F5D08C09@fastmail.fm>
References: <147265807396.13320.16720268350417791956.idtracker@ietfa.amsl.com> <21b2559f2a234c64b47595eb4615c661@XCH-RCD-017.cisco.com> <932002F5-18BA-46E7-9C71-EC985A0FCFDC@fastmail.fm> <c6baeabd62854628aaadfb75ac7d250a@XCH-RCD-017.cisco.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/i8eGr1aetFwiYTN2QWbnmJQ5M60>
Cc: "tram@ietf.org" <tram@ietf.org>, Simon Perreault <sperreault@jive.com>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, The IESG <iesg@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>
Subject: Re: [tram] Alexey Melnikov's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 08:19:46 -0000

Hi,

On 2 Sep 2016, at 04:02, Tirumaleswar Reddy (tireddy) <tireddy@cisco.com> wr=
ote:

>> -----Original Message-----
>> From: Alexey Melnikov [mailto:aamelnikov@fastmail.fm]
>> Sent: Thursday, September 1, 2016 12:49 PM
>> To: Tirumaleswar Reddy (tireddy) <tireddy@cisco.com>
>> Cc: The IESG <iesg@ietf.org>; draft-ietf-tram-turn-server-discovery@ietf.=
org;
>> Simon Perreault <sperreault@jive.com>; tram-chairs@ietf.org; tram@ietf.or=
g
>> Subject: Re: Alexey Melnikov's Discuss on draft-ietf-tram-turn-server-
>> discovery-09: (with DISCUSS)
>>=20
>> Hi,
>>=20
>> On 1 Sep 2016, at 04:48, Tirumaleswar Reddy (tireddy) <tireddy@cisco.com>=

>> wrote:
>>=20
>>>> -----Original Message-----
>>>> From: Alexey Melnikov [mailto:aamelnikov@fastmail.fm]
>>>> Sent: Wednesday, August 31, 2016 9:11 PM
>>>> To: The IESG <iesg@ietf.org>
>>>> Cc: draft-ietf-tram-turn-server-discovery@ietf.org; Simon Perreault
>>>> <sperreault@jive.com>; tram-chairs@ietf.org; sperreault@jive.com;
>>>> tram@ietf.org
>>>> Subject: Alexey Melnikov's Discuss on
>>>> draft-ietf-tram-turn-server-discovery-
>>>> 09: (with DISCUSS)
>>>>=20
>>>> Alexey Melnikov has entered the following ballot position for
>>>> draft-ietf-tram-turn-server-discovery-09: Discuss
>>>>=20
>>>> When responding, please keep the subject line intact and reply to all
>>>> email addresses included in the To and CC lines. (Feel free to cut
>>>> this introductory paragraph, however.)
>>>>=20
>>>>=20
>>>> Please refer to
>>>> https://www.ietf.org/iesg/statement/discuss-criteria.html
>>>> for more information about IESG DISCUSS and COMMENT positions.
>>>>=20
>>>>=20
>>>> The document, along with other ballot positions, can be found here:
>>>> https://datatracker.ietf.org/doc/draft-ietf-tram-turn-server-discover
>>>> y/
>>>>=20
>>>>=20
>>>>=20
>>>> ---------------------------------------------------------------------
>>>> -
>>>> DISCUSS:
>>>> ---------------------------------------------------------------------
>>>> -
>>>>=20
>>>> In Section 9:
>>>>=20
>>>> o  For certificate-based authentication, a pre-populated trust anchor
>>>>     store [RFC6024] allows a TURN client to perform path validation
>>>>     for the server certificate obtained during the (D)TLS handshake.
>>>>=20
>>>>     If the client used a domain name to discover the TURN server, that
>>>>     domain name also provides a mechanism for validation of the TURN
>>>>     server.  The client MUST use the rules and guidelines given in
>>>>     section 6 of [RFC6125] to validate the TURN server identity.
>>>>=20
>>>> I am glad that you are referencing RFC 6125, but unfortunately you
>>>> don't provide enough details. Please add details as specified in
>>>> Section 3 of RFC
>>>> 6125 to your document.
>>>=20
>>> Sure, will add the following lines:
>>> Certification authorities that issue TURN server certificates SHOULD sup=
port
>> the DNS-ID and SRV-ID identifier types. TURN service providers SHOULD
>> include the DNS-ID and SRV-ID identifier types in certificate requests.
>>=20
>> What about use of CN-IDs and URI-IDs?
>=20
> Yes, added.

Just to clarify: you can pick which ones of the 4 types you want to use, you=
 can disallow some. You just have to be explicit.
>=20
>> Wildcards ?
>=20
> I don't think wildcards are required.

Please say so in the document.



From nobody Fri Sep  2 14:54:16 2016
Return-Path: <praspati@cisco.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 4FA0D12D589; Fri,  2 Sep 2016 14:54:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.069
X-Spam-Level: 
X-Spam-Status: No, score=-15.069 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 LVEVjVyjIMxc; Fri,  2 Sep 2016 14:54:07 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 658D6127735; Fri,  2 Sep 2016 14:54:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2732; q=dns/txt; s=iport; t=1472853247; x=1474062847; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=MatHtiovrTziaFwLpJnza8paoIlLWazFuyMZaIIxON0=; b=hAO+RcSNtz/NXIlHpr5oAd8wKbQ2/i4vzXQGESpn6bjnr+rxxG5s+8Sq irArK+FTMvx21P6vMfc3O3o9Jx8tcQqJmU5U09FPsV6A1VN2sSNOfYRh+ VbpUtfipjznK7EMU6sm/OHalfSR8A9VNIAwZ4Q210rY+XO1VPBuAz1u5a 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CyAgAZ9MlX/40NJK1TCoNQAQEBAQEeV?= =?us-ascii?q?3wHtiGCD4ICJIV4AoFiOBQBAgEBAQEBAQFeJ4RiAQU6PxACAQg2EDIlAgQBDQW?= =?us-ascii?q?ISg68EQEBAQEBAQEBAQEBAQEBAQEBAQEBARcFhi+ETYQSBgsBBkiFKgEEiC6Fd?= =?us-ascii?q?4suAYYgiRWBboReiQ2QRAEeNoMIgTVwAYRYgSB/AQEB?=
X-IronPort-AV: E=Sophos;i="5.30,272,1470700800"; d="scan'208";a="144797938"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 02 Sep 2016 21:54:06 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id u82Ls5LI002997 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 2 Sep 2016 21:54:06 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 2 Sep 2016 17:54:04 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Fri, 2 Sep 2016 17:54:04 -0400
From: "Prashanth Patil (praspati)" <praspati@cisco.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, The IESG <iesg@ietf.org>
Thread-Topic: Suresh Krishnan's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
Thread-Index: AQHSBWSFXPFPd+NuBk2VZoqNItlVwg==
Date: Fri, 2 Sep 2016 21:54:04 +0000
Message-ID: <D3EDDAE4.130787%praspati@cisco.com>
References: <147270350795.31961.8306227467315681365.idtracker@ietfa.amsl.com>
In-Reply-To: <147270350795.31961.8306227467315681365.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.4.160422
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.155.85.140]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <76F67559F4776A408FEE323D606D252C@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/lYaVi6kdWt43nHEIsaYS73aL3Uo>
Cc: Simon Perreault <sperreault@jive.com>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, "tram@ietf.org" <tram@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>
Subject: Re: [tram] Suresh Krishnan's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 21:54:09 -0000

Hi Suresh,
Apologies for the delay, just back from holiday. Please see inline..

On 8/31/16, 9:18 PM, "Suresh Krishnan" <suresh.krishnan@ericsson.com>
wrote:

>Suresh Krishnan has entered the following ballot position for
>draft-ietf-tram-turn-server-discovery-09: Discuss
>
>When responding, please keep the subject line intact and reply to all
>email addresses included in the To and CC lines. (Feel free to cut this
>introductory paragraph, however.)
>
>
>Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>for more information about IESG DISCUSS and COMMENT positions.
>
>
>The document, along with other ballot positions, can be found here:
>https://datatracker.ietf.org/doc/draft-ietf-tram-turn-server-discovery/
>
>
>
>----------------------------------------------------------------------
>DISCUSS:
>----------------------------------------------------------------------
>
>* Section 4.1.1.
>
>The DHCP procedure is underspecified. I think this can be easily fixed
>but it requires some work.
>
>Please describe what sort of messages you would be using. i.e. are you
>going for a stateful exchange to piggy pack with other address and config
>information or are you going for a stateless Information-request based
>exchange(Most likely). Is there an ORO? If so, what options are requested
>in the ORO? Are there multiple request-response round trips as implied by
>the text?

Does following text address your concerns?

..
   DHCP can be used to determine the domain name related to an
   interface's point of network attachment.  Network operators may
   provide the domain name to be used for service discovery within an
   access network using DHCP.  Sections 3.2 and 3.3 of [RFC5986] define
   DHCP IPv4 and IPv6 access network domain name options,
   OPTION_V4_ACCESS_DOMAIN and OPTION_V6_ACCESS_DOMAIN respectively, to
   identify a domain name that is suitable for service discovery within
   the access network.

   For IPv4, the discovery procedure MUST request for an access network
   domain name option in a Parameter Request List option, as described
   in [RFC2131].  [RFC2132] defines the DHCP IPv4 domain name option;
   while this option is less suitable, a client MAY request for it if
   the access network domain name defined in [RFC5986] is not available.

   For IPv6, the discovery procedure MUST request for an access network
   domain name option in an Options Request Option (ORO), as described
   in [RFC3315].

   If neither option can be retrieved the procedure fails for this
   interface.  If a result can be retrieved it will be used as input
   for S-NAPTR resolution.

..

-Prashanth

>
>
>
>


From nobody Sat Sep  3 20:02:57 2016
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 E076212B129; Sat,  3 Sep 2016 20:02:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.978
X-Spam-Level: 
X-Spam-Status: No, score=0.978 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-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_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ingate.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 bI6OaF0MNvHm; Sat,  3 Sep 2016 20:02:53 -0700 (PDT)
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-eopbgr50065.outbound.protection.outlook.com [40.107.5.65]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF7EF12B09B; Sat,  3 Sep 2016 20:02:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ingate.onmicrosoft.com; s=selector1-ingate-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=nanY6ItD7wrLtQCrae7JL/5A0qS7VdmoZyfA7qdG3jM=; b=dFh+Ov2XJzCwp/mgz3mhodlPzUZi55OEAgYp4WcJgSYU0akW1N6zIzVW5HnikTjqy38890/0KCqWqGL/MmZEsdaetYPnkwgEEaTiZgq1+AFovndxHZ86NmyWVCJBPqKMC9zKXyxjzUczVd5qrN+0q1K2E0vSymGQP8wje0VLwG8=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=karl@ingate.com; 
Received: from Kallei7 (90.227.80.227) by VI1PR01MB1840.eurprd01.prod.exchangelabs.com (10.166.40.26) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id 15.1.599.9; Sun, 4 Sep 2016 03:02:47 +0000
From: Karl Stahl <karl.stahl@ingate.com>
To: "'Tirumaleswar Reddy (tireddy)'" <tireddy@cisco.com>, 'Spencer Dawkins at IETF' <spencerdawkins.ietf@gmail.com>, 'Simon Perreault' <sperreault@jive.com>, <draft-ietf-tram-turn-server-discovery@ietf.org>, <tram@ietf.org>, <tram-chairs@ietf.org>
References: <CAKKJt-cQB8wtv_7Fg_99EanpAj+PFKb8hrjerv4RmrRYFE5tpA@mail.gmail.com> <1fd125ccd3a84a4f9240b6f8d488bd5b@XCH-RCD-017.cisco.com>
In-Reply-To: <1fd125ccd3a84a4f9240b6f8d488bd5b@XCH-RCD-017.cisco.com>
Date: Sun, 4 Sep 2016 05:02:42 +0200
Message-ID: <073001d20658$d114dda0$733e98e0$@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: AQHSBFGmaZNBI5g1FU+H96yZbt6fIqBkonSAgAHjyfA=
Content-Language: sv
X-Originating-IP: [90.227.80.227]
X-ClientProxiedBy: AM2PR09CA0083.eurprd09.prod.outlook.com (10.160.228.179) To VI1PR01MB1840.eurprd01.prod.exchangelabs.com (10.166.40.26)
X-MS-Office365-Filtering-Correlation-Id: f181c35e-8de4-4036-a1e2-08d3d46ff3a2
X-Microsoft-Exchange-Diagnostics: 1; VI1PR01MB1840; 2:uZSkkWlBEdfK+Sl5dYr1KwKfQwd31ek9YyJnyf3myM2fuPROXWvmvy/zjNbewj8qXzTerb2qpsTpq4sTiPGFyYcNr7JchIX35mCxqMNnz9FL4Rw17lWzD+zZb3IHy1tteAPBgmdWTK+bbLm4IstxM/Wdo4GBQypIKkssd038oTQ8VPAlt9bCRkUoTk9NKzWX; 3:pXz8Av4mJ6P7xhcsmlEs5TAj3rdbQICJ60FMfiToWgynSKNNBaVb7yELRDZ9w8Z6nDRqL6vbGiYkSALWF4lCdkk5seNbGkWhU69DcSL+0YcakqkCU8mRDjL4nkskgadf
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:VI1PR01MB1840;
X-Microsoft-Exchange-Diagnostics: 1; VI1PR01MB1840; 25:iyGsULhoFd1WWEIlCjHnPcBPYNrKiI2xjirhWv0PLLx8fhNDGASTcjaPBOPqcvhjQqNDxfKlArgAfnNfc5gvNll45QF8PDpJpmbBTp5lWwHWv1QIh73I0RbZCp3HYHbtF7f7uDJ+payEn3n5IRVugAMNP6A53BPfahO5T6McAagaQ53fRF04WWdAQglklPPOJxm+DSpEX1tT5osWBNAICQSVO8VUnw0fGoFpzmhEZiJTsyrEVHtggFA8kn4C0QxH+nnVdl5q1aCLcmFpR6utrd3O5DQGNncNsXfC9gKGLqzDAiIbI6cf7BXegmlz4y2P8HyUgbD9vsi5eEd650LVjhhi/86azmY/b/Y1C49O+BqcKwcMPnD/LTi4++toJwPCxJPI7sx/iCwJll/wAXbVTK98KtO4sVhg9XzWQ0yQP2iDtOGZMy3wv1DS/L07WZW51M3ySvy9YkqMQydjbwRr6sHG30ILpZPpWxr2n5PysHSg6pbv7NBVDgZQMI5PsZF2NQgM5uExizqtZNQjVB+a/qZ4mKdbpXQWJmP9gfHpKD4TMZPMR7i9IN0JD0VWEtihE7Ctmgn2MmUym1eHx6xEtKYmS3fcQSgA481JZbwTB8hpuYc24icH1WveEI2lxsVpkSiYTELUM9XYnKd8/c4CK04po+90WHtY4F7WKuhirhJxxBPxcdGcxHnwoi5Vq4oL/J+1oaTxi4Axqywe9dgJtJ47SPcyPdNYjA+Z0+bWlhM8dwwUTTCBc4eZPeNllHHkAMuUpHSZiYglFYvQka9D3Evx5OeUo608QQyPCVKKZONCwb4bkUK1138+Gpeezzlk2ZZOgx+Oxf3JYt0fSaXdPQ==
X-Microsoft-Exchange-Diagnostics: 1; VI1PR01MB1840; 31:42kgTF/L5T1rg3S/txTsgEhLq0p7AlzckbIbcYZtTxClpqJtkBThOYZthJL7iHgo0/i0WzRnqH3wHQNx9xGg8fHNIwrsqy2n9KdzfMLn4ziBSjKjulfQwPV23tlUcsKDpuxlgfTfN1Km0CktVoewyKv5EDz1VSoPbl3Sh72UvCOuJ1uOGULJA8YDbLuHZuGZk3arZq3ogEnCXP1zYZf0/LaJfYSvBzf8TN8YT3+GK0c=; 4:37AgmO4WxwOvjFJP0zpwNEl21Aj2w3MzbCKieiayPFR244Eo2VZ5hCWZuZc4Q2U9lytx1n8d2xqNqoQU7kCJNi8fXjEQS7W5divfEwelJoynxLY4S2xK4RVMnbmJX6GMoQT9E6MhmfFCXQ7J6QkxAAhTt4lyEyuvKNI1wOAtO8u3O1z5ZQySwXggEQxQT4jvrBWQt5Yo8lu4YmLb7ITu/zLsewdCdW544xIFbNu4vjjnXyQ7dKJXDVzZcmZHLiSmT68E3GMx6LJ/bxHuLTkdFrCUSlsivWHJqZoQDn0l0wkEQBlswRV3MlJdgrEhvMSjISWcGCW1LAiUl/pmSTubYReuhusQ/9q8iNk5Pi1kD2rUDEL8RihtZkRQckdblVLNlnleex42qmxctEEtgMXPdgAu9FBQU2zFSNPQP9xWl4MtqANK3GYG9NIuvTBXn/FZVmbudFCpewA9PSYimZBeyqPbFcwsE/UtG66QFWD61Vyxp7ZprPB6TXuNuach0rA/zC0tj4lMAsPVx5MKFAVYAYJlZpGFpVpbHnqaf901CvKaMGAY2t3Sz9mEZUa4gluDsmLcRtAYf8lqPxh0nNmWQSd1PhKtJ7C3d2V/HOWl904tsK00nDqzzrYqAcMAEtk+4gT/9hBmj3+ntdfe/W/Lsw==
X-Microsoft-Antispam-PRVS: <VI1PR01MB1840ABBBE2DDBE736A0A9EB4B1E70@VI1PR01MB1840.eurprd01.prod.exchangelabs.com>
X-Exchange-Antispam-Report-Test: UriScan:(158342451672863)(278428928389397)(120809045254105)(192374486261705)(21532816269658)(17755550239193);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6043046)(6042046); SRVR:VI1PR01MB1840; BCL:0; PCL:0; RULEID:; SRVR:VI1PR01MB1840; 
X-Forefront-PRVS: 00550ABE1F
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(4630300001)(6009001)(7916002)(189002)(13464003)(199003)(38534002)(377454003)(23756003)(42186005)(9686002)(106356001)(7736002)(33646002)(61296003)(8746002)(50226002)(81156014)(81166006)(305945005)(19580395003)(19580405001)(14726001)(50466002)(345774005)(229853001)(106116001)(68736007)(2201001)(36756003)(66066001)(96836002)(47776003)(105586002)(76176999)(107886002)(7846002)(230783001)(84116002)(97736004)(2950100001)(50986999)(5001770100001)(77096005)(5660300001)(2906002)(15975445007)(92566002)(586003)(189998001)(102836003)(6116002)(1420700001)(101416001)(3846002); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR01MB1840; 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: =?iso-8859-1?Q?1; VI1PR01MB1840; 23:SzKVLjMx4Rvn2nR8nDIf0Rn9nF8Xmv+DAGoUSYQ?= =?iso-8859-1?Q?U/pGiToZxdgx8NL6ZNPvcz1fJ5F6H6L96aaoB+ml33RroJDkXKUoCwA00J?= =?iso-8859-1?Q?X97SI72ztkMag4w9GVVGfcemUu7qPPLFVl4sydtxzNLa+8rAxKSG+gMLNc?= =?iso-8859-1?Q?bZ0I3xXrULc+0/HmSvB8D8qsxVuLERVrGYXJNYhYu+NclDAGzrAVtQR77z?= =?iso-8859-1?Q?wMzIlABpDgFlX3PfnX2zJmGhZmO1doV1SI6LdMWtg0zfqChR2c3N3puTrA?= =?iso-8859-1?Q?EbjoQDB66BiRv4YrHc4ftfduEwvZuYZfvOhzVy0faNu0pKF58DfyLj6YFJ?= =?iso-8859-1?Q?PYoMS51fITtyUrlYvmCO1THK/0uSntXwIHQcPWkkFcSQ0qsir97SF6eTD2?= =?iso-8859-1?Q?8BjF++okPyncO7nHrh3hGECE0xokKNN96OX247NpkCBnLgau15NV5JfoON?= =?iso-8859-1?Q?v689P9Qx64nrcdacATBTEUDlfbnTytoHGAknW/n6bqk8VQavbxd+J74x4L?= =?iso-8859-1?Q?DU13Xp97o+X1G9ZonXoK1Zkl1r1s28VsFeSUyxtzokhBVlg6Q0t8f+Mb1t?= =?iso-8859-1?Q?zHsl5zS2MFNS1CwV4qcDcf0Jxbaj3nFK2QIywWY4NWcMSukniLAjBuaxGi?= =?iso-8859-1?Q?NWDNhCJAfEvYTi3oKGd8hp5tIIbrMgOWtNLmEah1WWEFoE4Q3BNLdTLIem?= =?iso-8859-1?Q?ou5EeyTkoMQe1rwbePjo4gzMAB0N8TdIlfbRw4ltbtXoF7lwyCZlNkcQur?= =?iso-8859-1?Q?xWOMYUlV1tKMdGmz0lECojFnfcPYsWBEJ3ie/ig391CbyGPSLY6Yepp7h4?= =?iso-8859-1?Q?tQWWghGtnpR5BlgGMwBq0Hf4lV/A6JWjrxninnRp2aww1s+eFun16ogiDt?= =?iso-8859-1?Q?3xWK3qi5R9QmJtVcraqRcvO4eUaLAxQoXfeng5wtkUkSTXtw1dRk1+5Gbp?= =?iso-8859-1?Q?hqAIazZ0f0UoaCzgQTD9C+BUZWwu43leJgEhA3xeljw2JWE+FEzy6edlpO?= =?iso-8859-1?Q?qNWUXS0bblkkyHlXG9zi6N5cHwkyqHzvbkX2LjvSL3hYUpfpySHaiLAtLQ?= =?iso-8859-1?Q?uJScK03aP6gk5yzN31zM2DzQbkarLyknap4dGKsMMgmkvq/7jzsp4cjAb8?= =?iso-8859-1?Q?nkQYIxKhppizSHcfBzLTmkl/BlzlFsuKa1K4sUmwHuqLrqRVa4yM5FryFM?= =?iso-8859-1?Q?0jiOg6wPl9lzQ51HybJsE7F98nmR6E36OFUbYcDF5IdCYuA8bbKoJ2FviO?= =?iso-8859-1?Q?f4CEcInaOICcJskIn93xLDkVGrwk+EHfzRViEzmGFdS9cP1j/gjqMsV8+p?= =?iso-8859-1?Q?dd8yA5peXurDzrvvIzdJFzFen2oqs+J09Ojsv6k+gyEg6dQ2chml78QU/7?= =?iso-8859-1?Q?ZcazpFhOrrFehlPWX42OZD3GD6rvq?=
X-Microsoft-Exchange-Diagnostics: 1; VI1PR01MB1840; 6:kVJh8FeaPoR75XlvL6BFMuyVKy1tWsH+FQZb7Ln+/mNB8ZdRiWT5Q5PXCAR2ZffQINwHWiRrvCeWsTe97haLS+Es62ovNmwI7JtSzuhXE67q86rHSpSF24tzJL6SATuP+QaKpB0hl0dzMWDP3BWNhb/teIV2esAVxL+eI4BkU91Mc839n4nDdDBWnpqVM2J53zk6lw3dHrIZalvfKcvpSdHRhdAJ+fC+lnqiKjHHkz9+Y6hklA90Uk4aPEE2NG5Wse6XEIOilXY4NaGnMxcvhdvLsw8NzkEmreJ6df8bvvjtt42AIEh/4BmQYx//JkRU; 5:j1gFJvD7ayUznI/17YUdkOFNsYenruP5yymnx2UKSJg4pka/9AHMKythKfW0OM57Rbam0OJxHACvZqx5wKbBN7tyUhOvFeGz8RcQbAN6Uxmsg5EnhVQ4nA9isdlIgwWk575XTvnTf4nx7PkCsFxMqA==; 24:XytOiO2H8/cvTAcg+qEv+UFUigAZovbWtvg0f4epMNEdXGd/9vSms5c6LEIzbhMSguWVa8J5m4u9nvfzse2poFLi44JbA3LoOPHdlnezWUE=; 7:sSEA4qSSdmQFEzol6p5mvIHW+yMHULL1XT4bCU/D3Tj/tquGaXgDP9GIx1a9ZNaA/jcs2hKPIHYSYcX7SIK+IN0f5LCydtVTccmTGz/XqGevR/Lro9JwmVkBjeObws0MSMN8jktbfDlhezte/0X+ih8kiTHH33JIbOZkIJOGd7LocUBz7DBbcvOIfj5dFlGekqAkVo7E/yLRfm7OVjUZDB0A/6TslMuR0kxi2aql5J3poRnUU0V/1nzIxgHXM+JF
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: ingate.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 04 Sep 2016 03:02:47.8757 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR01MB1840
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/O-U5WLYkx1fFy4DBRnH1pZ4Jas4>
Subject: Re: [tram] Discuss ballot positions on	draft-ietf-tram-turn-server-discovery
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 03:02:56 -0000

Tiru, to add to your stress :)

What happened to=20
https://www.ietf.org/mail-archive/web/tram/current/msg02081.html (and an
earlier WG entry pointing out the same)?
The Anycast method does not work with RFC5766 TURN servers! That has not
been addressed at all.

A TURN server doesn=92t react one way (answering 300 Try Alternate) when
addressed by an anycast address and another way (accepting the Allocate
request) when addressed by its unicast address, does it?=20

I suggested this modification:

=93When a client requires TURN services, it sends a STUN binding request =
to
the assigned anycast address.  The STUN server
responds with a 300 (Try Alternate) error as described in [RFC5389];  =
The
response contains a unicast address in the ALTERNATE-SERVER attribute, =
which
the client compares with the source address of the response and if the
addresses are the same, it is an indication to use the TURN server at =
that
address.=20

For subsequent communication with the TURN server, the client uses that
responding server's unicast address.=94

This proposed change has important advantages for security and =
usefulness
for draft-ietf-rtcweb-return-01 also.

See further [Karl] comments below.

/Karl

-----Ursprungligt meddelande-----
Fr=E5n: tram [mailto:tram-bounces@ietf.org] F=F6r Tirumaleswar Reddy =
(tireddy)
Skickat: den 1 september 2016 16:24
Till: Spencer Dawkins at IETF; Simon Perreault;
draft-ietf-tram-turn-server-discovery@ietf.org; tram@ietf.org;
tram-chairs@ietf.org
=C4mne: Re: [tram] Discuss ballot positions on
draft-ietf-tram-turn-server-discovery

> -----Original Message-----
> From: Spencer Dawkins at IETF [mailto:spencerdawkins.ietf@gmail.com]
> Sent: Thursday, September 1, 2016 6:11 PM
> To: Simon Perreault <sperreault@jive.com>; =
draft-ietf-tram-turn-server-
> discovery@ietf.org; tram@ietf.org; tram-chairs@ietf.org
> Subject: Discuss ballot positions on =
draft-ietf-tram-turn-server-discovery
>=20
> Dear Authors,
>=20
> I haven't seen responses to Discuss positions from Ben and from Suresh =
on
> this draft, at least not yet (thank you for the quick responses to the
Discuss
> positions from Alexey, Kathleen, and Terry).

I just now finished taking care of comments and discuss points on TURN
Mobility :)

>=20
> Ben's seems pretty clear, but I wanted to make sure Suresh's Discuss =
is
clear
> enough for you to work with. If you have a chance to let me know =
something
> about that in the next couple of hours (pre-telechat), that would be
awesome.

Suresh discuss looks clear to me. The points raised by Ben's and =
Kathleen
needs to discussed in the WG. My initial thoughts:
a)We will have to discuss and update security considerations section =
that if
STUN authentication is optional then the Enterprise/Access networks must =
use
various mechanisms like subscriber-quota, permit requests to the TURN =
server
only from specific IP addresses, Ingress Filtering etc.
b)This draft will have to update RFC5766.

[Karl] The "autoconfiguration" of RFC 7478 (Web Real-Time Communication =
Use
Cases and Requirements) 2.3.5.1:
An enterprise that uses a WebRTC-based web application for
   communication desires to audit all WebRTC-based application sessions
   used from inside the company towards any external peer.  To be able
   to do this, they deploy a TURN server that straddles the boundary
   between the internal and the external network.
   The firewall will block all attempts to use STUN with an external
   destination unless they go to the enterprise auditing TURN server.
   In cases where employees are using WebRTC applications provided by an
   external service provider, they still want the traffic to stay inside
   their internal network and in addition not load the straddling TURN
   server; thus, they deploy a STUN server allowing the WebRTC client to
   determine its server reflexive address on the internal side.  Thus,
   enabling cases where peers are both on the internal side to connect
   without the traffic leaving the internal network.  It must be
   possible to configure the browsers used in the enterprise with
   network specific STUN and TURN servers.  This should be possible to
   achieve by autoconfiguration methods.  The WebRTC functionality will
   need to utilize both network specific STUN and TURN resources and
   STUN and TURN servers provisioned by the web application.

Does that not in itself provide sufficient "argument that the =
local/access
network is somehow equally protected." that Ben is looking for, so that
RFC5766 need not be updated (at least not for this use case)?=20

And regarding Kathleen's discuss, isn't this use case "reason why TURN
server discovery should be restricted only to specific clients"?


c)Do we really want to make I-D.ietf-rtcweb-return normative (I prefer =
not)
?
[Karl] Why?


-Tiru

>=20
> The datatracker page with ballot positions is (as always) at
>
https://datatracker.ietf.org/doc/draft-ietf-tram-turn-server-discovery/ba=
llo
t/
_______________________________________________
tram mailing list
tram@ietf.org
https://www.ietf.org/mailman/listinfo/tram


From nobody Mon Sep  5 19:05:44 2016
Return-Path: <tireddy@cisco.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 9D70012B0FE; Mon,  5 Sep 2016 19:05:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.029
X-Spam-Level: 
X-Spam-Status: No, score=-16.029 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 di7GmKPOyfH2; Mon,  5 Sep 2016 19:05:35 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12798128E19; Mon,  5 Sep 2016 19:05:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4084; q=dns/txt; s=iport; t=1473127535; x=1474337135; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Zb7t0roeIugHF8eaWSZL1YVT2w1S3VhAeuUhR0P2D4o=; b=MPAmNPzs3vxSAL1rjoiU/fgN5j/otRTi3a8WxOh3mMPVOqJwClG0WDsG Icm9ItgxnzZgQBi7whnnLVAHEuE7bErsrPyrmiaraqWBEskYY8J1mGgMH jStD53H9ACvXDbqv88gYV81S7dsz3MvVBijUpeY/7wBxaComOr0pQDch8 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BfAQDoI85X/40NJK1UCRkBAQEBAQEBA?= =?us-ascii?q?QEBAYMtAQEBAQEeV3wHjSeoeIIPggIkhXgCgVE4FAECAQEBAQEBAV4nhGEBAQE?= =?us-ascii?q?EOj8MBAIBCA4DBAEBAR4JBzIUCQgCBA4FCIhCDrxZAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBFwWGL4ROhBIHCgEGSIUqBYguhXeFZYVJAYYgiQ6BdYReiQ2GcoVag3k?= =?us-ascii?q?BHjaDEoE1cAGEPQ0XB4ECfwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.30,289,1470700800"; d="scan'208";a="145843642"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 06 Sep 2016 02:05:05 +0000
Received: from XCH-RCD-018.cisco.com (xch-rcd-018.cisco.com [173.37.102.28]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id u86255JJ006657 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 6 Sep 2016 02:05:05 GMT
Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-RCD-018.cisco.com (173.37.102.28) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 5 Sep 2016 21:05:05 -0500
Received: from xch-rcd-017.cisco.com ([173.37.102.27]) by XCH-RCD-017.cisco.com ([173.37.102.27]) with mapi id 15.00.1210.000; Mon, 5 Sep 2016 21:05:04 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Thread-Topic: Alexey Melnikov's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
Thread-Index: AQHSA54fDJMoqK9Hq0C6sHCN+3QJCaBj/4YwgACPJ4CAAPZdcIAAsIcAgAWJGkA=
Date: Tue, 6 Sep 2016 02:05:04 +0000
Message-ID: <9b0692f895bc497f8f0aa2b63ed5be27@XCH-RCD-017.cisco.com>
References: <147265807396.13320.16720268350417791956.idtracker@ietfa.amsl.com> <21b2559f2a234c64b47595eb4615c661@XCH-RCD-017.cisco.com> <932002F5-18BA-46E7-9C71-EC985A0FCFDC@fastmail.fm> <c6baeabd62854628aaadfb75ac7d250a@XCH-RCD-017.cisco.com> <12ED9DC3-7950-4517-A005-2B29F5D08C09@fastmail.fm>
In-Reply-To: <12ED9DC3-7950-4517-A005-2B29F5D08C09@fastmail.fm>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.70.128]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/lSmXZggNLcRIY7KKdQNLbV46vyg>
Cc: "tram@ietf.org" <tram@ietf.org>, Simon Perreault <sperreault@jive.com>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, The IESG <iesg@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>
Subject: Re: [tram] Alexey Melnikov's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 06 Sep 2016 02:05:37 -0000

> -----Original Message-----
> From: Alexey Melnikov [mailto:aamelnikov@fastmail.fm]
> Sent: Friday, September 2, 2016 2:02 PM
> To: Tirumaleswar Reddy (tireddy) <tireddy@cisco.com>
> Cc: The IESG <iesg@ietf.org>; draft-ietf-tram-turn-server-discovery@ietf.=
org;
> Simon Perreault <sperreault@jive.com>; tram-chairs@ietf.org; tram@ietf.or=
g
> Subject: Re: Alexey Melnikov's Discuss on draft-ietf-tram-turn-server-
> discovery-09: (with DISCUSS)
>=20
> Hi,
>=20
> On 2 Sep 2016, at 04:02, Tirumaleswar Reddy (tireddy) <tireddy@cisco.com>
> wrote:
>=20
> >> -----Original Message-----
> >> From: Alexey Melnikov [mailto:aamelnikov@fastmail.fm]
> >> Sent: Thursday, September 1, 2016 12:49 PM
> >> To: Tirumaleswar Reddy (tireddy) <tireddy@cisco.com>
> >> Cc: The IESG <iesg@ietf.org>;
> >> draft-ietf-tram-turn-server-discovery@ietf.org;
> >> Simon Perreault <sperreault@jive.com>; tram-chairs@ietf.org;
> >> tram@ietf.org
> >> Subject: Re: Alexey Melnikov's Discuss on
> >> draft-ietf-tram-turn-server-
> >> discovery-09: (with DISCUSS)
> >>
> >> Hi,
> >>
> >> On 1 Sep 2016, at 04:48, Tirumaleswar Reddy (tireddy)
> >> <tireddy@cisco.com>
> >> wrote:
> >>
> >>>> -----Original Message-----
> >>>> From: Alexey Melnikov [mailto:aamelnikov@fastmail.fm]
> >>>> Sent: Wednesday, August 31, 2016 9:11 PM
> >>>> To: The IESG <iesg@ietf.org>
> >>>> Cc: draft-ietf-tram-turn-server-discovery@ietf.org; Simon Perreault
> >>>> <sperreault@jive.com>; tram-chairs@ietf.org; sperreault@jive.com;
> >>>> tram@ietf.org
> >>>> Subject: Alexey Melnikov's Discuss on
> >>>> draft-ietf-tram-turn-server-discovery-
> >>>> 09: (with DISCUSS)
> >>>>
> >>>> Alexey Melnikov has entered the following ballot position for
> >>>> draft-ietf-tram-turn-server-discovery-09: Discuss
> >>>>
> >>>> When responding, please keep the subject line intact and reply to
> >>>> all email addresses included in the To and CC lines. (Feel free to
> >>>> cut this introductory paragraph, however.)
> >>>>
> >>>>
> >>>> Please refer to
> >>>> https://www.ietf.org/iesg/statement/discuss-criteria.html
> >>>> for more information about IESG DISCUSS and COMMENT positions.
> >>>>
> >>>>
> >>>> The document, along with other ballot positions, can be found here:
> >>>> https://datatracker.ietf.org/doc/draft-ietf-tram-turn-server-discov
> >>>> er
> >>>> y/
> >>>>
> >>>>
> >>>>
> >>>> -------------------------------------------------------------------
> >>>> --
> >>>> -
> >>>> DISCUSS:
> >>>> -------------------------------------------------------------------
> >>>> --
> >>>> -
> >>>>
> >>>> In Section 9:
> >>>>
> >>>> o  For certificate-based authentication, a pre-populated trust ancho=
r
> >>>>     store [RFC6024] allows a TURN client to perform path validation
> >>>>     for the server certificate obtained during the (D)TLS handshake.
> >>>>
> >>>>     If the client used a domain name to discover the TURN server, th=
at
> >>>>     domain name also provides a mechanism for validation of the TURN
> >>>>     server.  The client MUST use the rules and guidelines given in
> >>>>     section 6 of [RFC6125] to validate the TURN server identity.
> >>>>
> >>>> I am glad that you are referencing RFC 6125, but unfortunately you
> >>>> don't provide enough details. Please add details as specified in
> >>>> Section 3 of RFC
> >>>> 6125 to your document.
> >>>
> >>> Sure, will add the following lines:
> >>> Certification authorities that issue TURN server certificates SHOULD
> >>> support
> >> the DNS-ID and SRV-ID identifier types. TURN service providers SHOULD
> >> include the DNS-ID and SRV-ID identifier types in certificate requests=
.
> >>
> >> What about use of CN-IDs and URI-IDs?
> >
> > Yes, added.
>=20
> Just to clarify: you can pick which ones of the 4 types you want to use, =
you can
> disallow some. You just have to be explicit.

Okay.

> >
> >> Wildcards ?
> >
> > I don't think wildcards are required.
>=20
> Please say so in the document.

Sure, will update.

-Tiru

>=20


From nobody Tue Sep  6 09:05:17 2016
Return-Path: <presnick@qti.qualcomm.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 CAE8012B52A; Tue,  6 Sep 2016 09:05:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.528
X-Spam-Level: 
X-Spam-Status: No, score=-8.528 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.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 SfAkF6kwCn2e; Tue,  6 Sep 2016 09:05:09 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0E8912B5CE; Tue,  6 Sep 2016 08:55:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1473177328; x=1504713328; h=from:to:cc:subject:date:message-id:mime-version; bh=TgC/aIOmQ5O2A93ANdZcH+bvzFLjAn2djNsfwehZObk=; b=p5HxI5a0+X0rVPhWaIlhYU+xHVferRq+9stCZeuyyJLzWv7MNpQmMBXd 5uUznA9M+i+acmnZZz/tf7dwJ1qJeUl5sVzpJAN1KyQ7qKVUBsTvmz/10 wDbXCdgTLzKUqxfUsFbwLs1sz051jPxWbDvV9MoBin1sLAqurEhZlHsse E=;
X-IronPort-AV: E=Sophos;i="5.30,292,1470726000";  d="scan'208,217";a="317405948"
Received: from unknown (HELO Ironmsg04-R.qualcomm.com) ([10.53.140.108]) by wolverine02.qualcomm.com with ESMTP; 06 Sep 2016 08:55:28 -0700
X-IronPort-AV: E=McAfee;i="5700,7163,8280"; a="1267038269"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 06 Sep 2016 08:55:27 -0700
Received: from [10.64.128.83] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Tue, 6 Sep 2016 08:55:26 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: IESG <iesg@ietf.org>
Date: Tue, 6 Sep 2016 10:55:25 -0500
Message-ID: <6ECD9A3A-0D63-421B-953D-A516D773CCBA@qti.qualcomm.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_ACCA4C19-B7E7-44C8-9142-F06EB58A79A6_="
X-Mailer: MailMate (1.9.5r5260)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01C.na.qualcomm.com (10.85.0.83) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/Lv7dHnYXIHcv9Xqj9CNmZbsStwg>
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-tram-turn-mobility.all@ietf.org, tram@ietf.org
Subject: [tram] GenART post-telechat comment on draft-ietf-tram-turn-mobility-08
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 06 Sep 2016 16:05:15 -0000

--=_MailMate_ACCA4C19-B7E7-44C8-9142-F06EB58A79A6_=
Content-Type: text/plain; format=flowed; markup=markdown

Greetings,

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 participants comments.

For more information, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-tram-turn-mobility-03
Reviewer: Pete Resnick
Review Date: 2016-09-06
IESG Telechat date: 2016-09-01

Summary: This is an odd post-telechat review, but I think the draft has 
gone from "Ready" to "Ready with an issue" because of an IESG Eval 
change.

Details:

I did not get to my post-Last Call GenART review of 
draft-ietf-tram-turn-mobility until after the telechat. Had I done so, 
which would have been on version -05, I would have said "Looks fine to 
me". However, I happened to look at the latest version, figuring I would 
just confirm. I found that a change was made in response to an IESG 
Evaluation comment from Suresh 
<https://mailarchive.ietf.org/arch/msg/tram/SYVAXc1dF6xUcm0OQ9xyuaknJco>:

> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> * Section 3.2.1
>
> The section on sending a Refresh when the IP address does not change
> needs a little bit more tightening. Given that the server would reject
> the request with a mobility ticket in this case, it would be good to 
> put
> in an explicit restriction to not add the mobility ticket in the
> following statement
>
> OLD: If a client wants to refresh an existing allocation and update 
> its
> time-to-expiry or delete an existing allocation, it will send a 
> Refresh
> Request as described in Section 7.1 of [RFC5766]
>
> NEW:
> If a client wants to refresh an existing allocation and update its
> time-to-expiry or delete an existing allocation, it MUST send a 
> Refresh
> Request as described in Section 7.1 of [RFC5766] and MUST NOT include 
> a
> MOBILITY-TICKET attribute.

I'm not sure if the "MUST NOT" in the latter part of the sentence is 
correct: Since the server will reject it anyway, I don't see the harm in 
including the attribute that the "MUST NOT" implies, but perhaps this is 
belt-and-braces protocol description. On this point, I can't complain 
too much. However, I believe Suresh was incorrect in suggesting the 
first "MUST", and it should be removed. There is no harm being prevented 
here. "If a client wants X, it MUST send Y" is absolutely no different 
protocol-wise from "If a client wants X, it will send Y". The "MUST" is 
a misuse. I believe that this change should be undone before 
publication.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478
--=_MailMate_ACCA4C19-B7E7-44C8-9142-F06EB58A79A6_=
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
<style>
div.markdown { white-space: normal; }
body { font-family: sans-serif; }
h1 { font-size: 1.4em; }
h2 { font-size: 1.2em; }
h3 { font-size: 1.1em; }
blockquote { margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #=
777777; color: #777777; }
blockquote blockquote { border-left-color: #999999; color: #999999; }
blockquote blockquote blockquote { border-left-color: #BBBBBB; color: #BB=
BBBB; }
a { color: #3983C4 }
blockquote a { color: #777777; }
blockquote blockquote a { color: #999999; }
blockquote blockquote blockquote a { color: #BBBBBB; }
math[display=3D"inline"] > mrow { padding:5px; }
hr { border: 0; height: 1px; background: #333; background-image: linear-g=
radient(to right, #ccc, #333, #ccc); }
div.footnotes li p { margin: 0.2em 0; }
</style>
</head>
<body>
<div class=3D"markdown">
<p dir=3D"auto">Greetings,</p>

<p dir=3D"auto">I am the assigned Gen-ART reviewer for this draft. The Ge=
neral Area Review Team (Gen-ART) reviews all IETF documents being process=
ed by the IESG for the IETF Chair.  Please treat these comments just like=
 any other participants comments.</p>

<p dir=3D"auto">For more information, please see the FAQ at</p>

<p dir=3D"auto"><a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/=
GenArtfaq">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>.</=
p>

<p dir=3D"auto">Document: draft-ietf-tram-turn-mobility-03<br>
Reviewer: Pete Resnick<br>
Review Date: 2016-09-06<br>
IESG Telechat date: 2016-09-01</p>

<p dir=3D"auto">Summary: This is an odd post-telechat review, but I think=
 the draft has gone from "Ready" to "Ready with an issue" because of an I=
ESG Eval change.</p>

<p dir=3D"auto">Details:</p>

<p dir=3D"auto">I did not get to my post-Last Call GenART review of draft=
-ietf-tram-turn-mobility until after the telechat. Had I done so, which w=
ould have been on version -05, I would have said "Looks fine to me". Howe=
ver, I happened to look at the latest version, figuring I would just conf=
irm. I found that a change was made in response to an IESG Evaluation com=
ment from Suresh <a href=3D"https://mailarchive.ietf.org/arch/msg/tram/SY=
VAXc1dF6xUcm0OQ9xyuaknJco">https://mailarchive.ietf.org/arch/msg/tram/SYV=
AXc1dF6xUcm0OQ9xyuaknJco</a>:</p>

<blockquote>
<hr>

<h2>COMMENT:</h2>

<ul>
<li>Section 3.2.1</li>
</ul>

<p dir=3D"auto">The section on sending a Refresh when the IP address does=
 not change<br>
needs a little bit more tightening. Given that the server would reject<br=
>
the request with a mobility ticket in this case, it would be good to put<=
br>
in an explicit restriction to not add the mobility ticket in the<br>
following statement</p>

<p dir=3D"auto">OLD: If a client wants to refresh an existing allocation =
and update its<br>
time-to-expiry or delete an existing allocation, it will send a Refresh<b=
r>
Request as described in Section 7.1 of [RFC5766]</p>

<p dir=3D"auto">NEW:<br>
If a client wants to refresh an existing allocation and update its<br>
time-to-expiry or delete an existing allocation, it MUST send a Refresh<b=
r>
Request as described in Section 7.1 of [RFC5766] and MUST NOT include a<b=
r>
MOBILITY-TICKET attribute.</p>
</blockquote>

<p dir=3D"auto">I'm not sure if the "MUST NOT" in the latter part of the =
sentence is correct: Since the server will reject it anyway, I don't see =
the harm in including the attribute that the "MUST NOT" implies, but perh=
aps this is belt-and-braces protocol description. On this point, I can't =
complain too much. However, I believe Suresh was incorrect in suggesting =
the first "MUST", and it should be removed. There is no harm being preven=
ted here. "If a client wants X, it MUST send Y" is absolutely no differen=
t protocol-wise from "If a client wants X, it will send Y". The "MUST" is=
 a misuse. I believe that this change should be undone before publication=
=2E</p>

<p dir=3D"auto">pr<br>
-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/">http://www.=
qualcomm.com/~presnick/</a><br>
Qualcomm Technologies, Inc. - +1 (858)651-4478</p>
</div>

</body>
</html>

--=_MailMate_ACCA4C19-B7E7-44C8-9142-F06EB58A79A6_=--


From nobody Tue Sep  6 18:45:01 2016
Return-Path: <tireddy@cisco.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 E6AF712B0ED; Tue,  6 Sep 2016 18:44:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.028
X-Spam-Level: 
X-Spam-Status: No, score=-16.028 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 YLF5OxRWmg78; Tue,  6 Sep 2016 18:44:48 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 497A812B09D; Tue,  6 Sep 2016 18:44:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15718; q=dns/txt; s=iport; t=1473212688; x=1474422288; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=6MuxW+sDZueoRPzRMhj/k3PO2Knc8mP3YCLC0QZGW6s=; b=a5zW4onyDwGGigeYX2PvHnPObonwelxo7mbWwAABlnWWQG9YAuCQA58r sPKwSEZAxJleWEr/S5yRClyB3f1L1uzxOyAnhrMRezigdPyF/uJ5ycziU 8m5tfyD0sSZDqnBau081nRNLdGBtTYdejGtzBUm3c3Tu/gZdYV4hN/Deo Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BUAQDGb89X/5hdJa1aAxYDAQEBAQEBA?= =?us-ascii?q?QEBAQGCejMBAQEBAR5XfAeFR4dho1GCLYUNggIkhB6BWgKBZzgUAQIBAQEBAQE?= =?us-ascii?q?BXieEYQEBAQQtTBACAQgOAwMBAQEoBzIUCQgCBAENBQiIQg4DvB8BAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEchi+EToQqBhUbARURhRUFiDuHI4l4AYYhhQqEBYF1ToQ?= =?us-ascii?q?QiQ+Gc4Vbg3kBDw82gi8OKhuBTXABhTJ/AQEB?=
X-IronPort-AV: E=Sophos;i="5.30,294,1470700800";  d="scan'208,217";a="319632208"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Sep 2016 01:44:47 +0000
Received: from XCH-RCD-020.cisco.com (xch-rcd-020.cisco.com [173.37.102.30]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u871ikvT004363 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 7 Sep 2016 01:44:47 GMT
Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-RCD-020.cisco.com (173.37.102.30) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 6 Sep 2016 20:44:46 -0500
Received: from xch-rcd-017.cisco.com ([173.37.102.27]) by XCH-RCD-017.cisco.com ([173.37.102.27]) with mapi id 15.00.1210.000; Tue, 6 Sep 2016 20:44:46 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, IESG <iesg@ietf.org>, "Suresh Krishnan" <suresh.krishnan@ericsson.com>
Thread-Topic: GenART post-telechat comment on draft-ietf-tram-turn-mobility-08
Thread-Index: AQHSCFiLm4+HgrE2lU6LKYpWnDFIuqBtPtUw
Date: Wed, 7 Sep 2016 01:44:46 +0000
Message-ID: <4d628d80cee442cabfd473a62e520b14@XCH-RCD-017.cisco.com>
References: <6ECD9A3A-0D63-421B-953D-A516D773CCBA@qti.qualcomm.com>
In-Reply-To: <6ECD9A3A-0D63-421B-953D-A516D773CCBA@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.64.100]
Content-Type: multipart/alternative; boundary="_000_4d628d80cee442cabfd473a62e520b14XCHRCD017ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/wclyqSaSs0urniBjJ8RSYGyQi8E>
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-tram-turn-mobility.all@ietf.org" <draft-ietf-tram-turn-mobility.all@ietf.org>, "tram@ietf.org" <tram@ietf.org>
Subject: Re: [tram] GenART post-telechat comment on draft-ietf-tram-turn-mobility-08
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 01:44:53 -0000

--_000_4d628d80cee442cabfd473a62e520b14XCHRCD017ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

From: Pete Resnick [mailto:presnick@qti.qualcomm.com]
Sent: Tuesday, September 6, 2016 9:25 PM
To: IESG <iesg@ietf.org>
Cc: tram@ietf.org; draft-ietf-tram-turn-mobility.all@ietf.org; General Area=
 Review Team <gen-art@ietf.org>
Subject: GenART post-telechat comment on draft-ietf-tram-turn-mobility-08


Greetings,

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 t=
he IETF Chair. Please treat these comments just like any other participants=
 comments.

For more information, please see the FAQ at

http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq.

Document: draft-ietf-tram-turn-mobility-03
Reviewer: Pete Resnick
Review Date: 2016-09-06
IESG Telechat date: 2016-09-01

Summary: This is an odd post-telechat review, but I think the draft has gon=
e from "Ready" to "Ready with an issue" because of an IESG Eval change.

Details:

I did not get to my post-Last Call GenART review of draft-ietf-tram-turn-mo=
bility until after the telechat. Had I done so, which would have been on ve=
rsion -05, I would have said "Looks fine to me". However, I happened to loo=
k at the latest version, figuring I would just confirm. I found that a chan=
ge was made in response to an IESG Evaluation comment from Suresh https://m=
ailarchive.ietf.org/arch/msg/tram/SYVAXc1dF6xUcm0OQ9xyuaknJco:

________________________________
COMMENT:

  *   Section 3.2.1

The section on sending a Refresh when the IP address does not change
needs a little bit more tightening. Given that the server would reject
the request with a mobility ticket in this case, it would be good to put
in an explicit restriction to not add the mobility ticket in the
following statement

OLD: If a client wants to refresh an existing allocation and update its
time-to-expiry or delete an existing allocation, it will send a Refresh
Request as described in Section 7.1 of [RFC5766]

NEW:
If a client wants to refresh an existing allocation and update its
time-to-expiry or delete an existing allocation, it MUST send a Refresh
Request as described in Section 7.1 of [RFC5766] and MUST NOT include a
MOBILITY-TICKET attribute.

I'm not sure if the "MUST NOT" in the latter part of the sentence is correc=
t: Since the server will reject it anyway, I don't see the harm in includin=
g the attribute that the "MUST NOT" implies, but perhaps this is belt-and-b=
races protocol description. On this point, I can't complain too much.

[TR] "MUST NOT" is required to prevent the client from sending the request =
with the ticket which will be rejected by the server and the client will ha=
ve to again re-try the request without the ticket.

However, I believe Suresh was incorrect in suggesting the first "MUST", and=
 it should be removed. There is no harm being prevented here. "If a client =
wants X, it MUST send Y" is absolutely no different protocol-wise from "If =
a client wants X, it will send Y". The "MUST" is a misuse. I believe that t=
his change should be undone before publication.

[TR] I can the update the line; including Suresh to see if he has any objec=
tions.

-Tiru

pr
--
Pete Resnick http://www.qualcomm.com/~presnick/<http://www.qualcomm.com/%7E=
presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478

--_000_4d628d80cee442cabfd473a62e520b14XCHRCD017ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-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=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
h1
	{mso-style-priority:9;
	mso-style-link:"Heading 1 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:17.0pt;
	font-family:"Times New Roman",serif;
	font-weight:bold;}
h2
	{mso-style-priority:9;
	mso-style-link:"Heading 2 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:14.5pt;
	font-family:"Times New Roman",serif;
	font-weight:bold;}
h3
	{mso-style-priority:9;
	mso-style-link:"Heading 3 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:13.0pt;
	font-family:"Times New Roman",serif;
	font-weight:bold;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#3983C4;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#3983C4;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Cambria",serif;
	color:#365F91;}
span.Heading2Char
	{mso-style-name:"Heading 2 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 2";
	font-family:"Cambria",serif;
	color:#365F91;}
span.Heading3Char
	{mso-style-name:"Heading 3 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 3";
	font-family:"Cambria",serif;
	color:#243F60;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:96684629;
	mso-list-template-ids:-670151036;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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=3D"EN-US" link=3D"#3983C4" vlink=3D"#3983C4">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> Pete Resnick [mailto:presnick@=
qti.qualcomm.com]
<br>
<b>Sent:</b> Tuesday, September 6, 2016 9:25 PM<br>
<b>To:</b> IESG &lt;iesg@ietf.org&gt;<br>
<b>Cc:</b> tram@ietf.org; draft-ietf-tram-turn-mobility.all@ietf.org; Gener=
al Area Review Team &lt;gen-art@ietf.org&gt;<br>
<b>Subject:</b> GenART post-telechat comment on draft-ietf-tram-turn-mobili=
ty-08<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">Greetings,<o:p>=
</o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">I am the assign=
ed 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
 participants comments.<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">For more inform=
ation, please see the FAQ at<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif"><a href=3D"http=
://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wiki.tools.ietf=
.org/area/gen/trac/wiki/GenArtfaq</a>.<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">Document: draft=
-ietf-tram-turn-mobility-03<br>
Reviewer: Pete Resnick<br>
Review Date: 2016-09-06<br>
IESG Telechat date: 2016-09-01<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">Summary: This i=
s an odd post-telechat review, but I think the draft has gone from &quot;Re=
ady&quot; to &quot;Ready with an issue&quot; because of an IESG Eval change=
.<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">Details:<o:p></=
o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">I did not get t=
o my post-Last Call GenART review of draft-ietf-tram-turn-mobility until af=
ter the telechat. Had I done so, which would have been on version -05, I wo=
uld have said &quot;Looks fine to me&quot;. However, I
 happened to look at the latest version, figuring I would just confirm. I f=
ound that a change was made in response to an IESG Evaluation comment from =
Suresh
<a href=3D"https://mailarchive.ietf.org/arch/msg/tram/SYVAXc1dF6xUcm0OQ9xyu=
aknJco">
https://mailarchive.ietf.org/arch/msg/tram/SYVAXc1dF6xUcm0OQ9xyuaknJco</a>:=
<o:p></o:p></span></p>
<blockquote style=3D"border:none;border-left:solid #777777 1.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:0in;margin-right:0in;margin-bottom:3.75pt">
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-family:&quot;Arial&quot;,sans-serif;color:#777777">
<hr size=3D"3" width=3D"100%" align=3D"center">
</span></div>
<h2><span style=3D"font-family:&quot;Arial&quot;,sans-serif;color:#777777">=
COMMENT:<o:p></o:p></span></h2>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:#777777;mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style=3D"font-family:&quot;Arial&quot;,sans-serif">Section 3.2.1<o:p>=
</o:p></span></li></ul>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif;color:#777777">T=
he section on sending a Refresh when the IP address does not change<br>
needs a little bit more tightening. Given that the server would reject<br>
the request with a mobility ticket in this case, it would be good to put<br=
>
in an explicit restriction to not add the mobility ticket in the<br>
following statement<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif;color:#777777">O=
LD: If a client wants to refresh an existing allocation and update its<br>
time-to-expiry or delete an existing allocation, it will send a Refresh<br>
Request as described in Section 7.1 of [RFC5766]<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif;color:#777777">N=
EW:<br>
If a client wants to refresh an existing allocation and update its<br>
time-to-expiry or delete an existing allocation, it MUST send a Refresh<br>
Request as described in Section 7.1 of [RFC5766] and MUST NOT include a<br>
MOBILITY-TICKET attribute.<o:p></o:p></span></p>
</blockquote>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">I'm not sure if=
 the &quot;MUST NOT&quot; in the latter part of the sentence is correct: Si=
nce the server will reject it anyway, I don't see the harm in including the=
 attribute that the &quot;MUST NOT&quot; implies, but perhaps this
 is belt-and-braces protocol description. On this point, I can't complain t=
oo much.
<span style=3D"color:#1F497D"><o:p></o:p></span></span></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-ser=
if;color:#1F497D">[TR] &#8220;MUST NOT&#8221; is required to prevent the cl=
ient from sending the request with the ticket which will be rejected by the=
 server and the client will have to again re-try the request
 without the ticket.<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">However, I beli=
eve Suresh was incorrect in suggesting the first &quot;MUST&quot;, and it s=
hould be removed. There is no harm being prevented here. &quot;If a client =
wants X, it MUST send Y&quot; is absolutely no different protocol-wise
 from &quot;If a client wants X, it will send Y&quot;. The &quot;MUST&quot;=
 is a misuse. I believe that this change should be undone before publicatio=
n.<o:p></o:p></span></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-ser=
if;color:#1F497D">[TR] I can the update the line; including Suresh to see i=
f he has any objections.<o:p></o:p></span></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-ser=
if;color:#1F497D">-Tiru<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">pr<br>
-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/">http://www.qu=
alcomm.com/~presnick/</a><br>
Qualcomm Technologies, Inc. - &#43;1 (858)651-4478<o:p></o:p></span></p>
</div>
</div>
</body>
</html>

--_000_4d628d80cee442cabfd473a62e520b14XCHRCD017ciscocom_--


From nobody Tue Sep  6 18:59:02 2016
Return-Path: <spencerdawkins.ietf@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 1290312B48D; Tue,  6 Sep 2016 18:58:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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=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 5HEhtA2iqKi7; Tue,  6 Sep 2016 18:58:50 -0700 (PDT)
Received: from mail-yb0-x230.google.com (mail-yb0-x230.google.com [IPv6:2607:f8b0:4002:c09::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 3D95E12B10C; Tue,  6 Sep 2016 18:58:50 -0700 (PDT)
Received: by mail-yb0-x230.google.com with SMTP id g5so881008yba.2; Tue, 06 Sep 2016 18:58:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=OdXLhZMn61c/2V5GEyBRPblgWSMsHW+VuNDTCBX4O5g=; b=L2goFxQoTX0G+OLNlAn8pfklNgTtoGA1XvWauDwn/gkppSqVtdi3n7Tun09d+rjQ3j BEit5f1lkWtLcFFMg9WA9Pe1gNZuRLBSxRCTNAy7dMqtfp+RYnRrtP4p3Dr5t5mXgZqZ hHMt5jzV5sIZnglQ1agXn0uYX2GYmUYok5iM76FbjR6gawMK4/XC6mbLI3N5OYDdtUT1 o4llIewHTRlPkZnDAkFQoeoD2a+3EqDx/oEGwXklTqFFJ4cLZL2WFiQjDbYE7QsjOzEO EbqE0VYuzAJ/R/MrGR3v2V0Bak3E/JAZrNcysrFh8DO0VXV/DGTbhRFprCDbbyFs2iQ/ aFjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=OdXLhZMn61c/2V5GEyBRPblgWSMsHW+VuNDTCBX4O5g=; b=bDdJVqWVIw1sHnVD9+xqwfJNQF1zsUjlDyk6OZXxitDkoJIyku3ZxWwNby+q5aFl+m otNZinPnSlY7DB0RIRdTCQIGLQErDPYNCMsHNdeGt+O6wkimR/lvxVnC4MfazGa/CJe1 RlcObydFX7B+UW/M5ePS0ZmAkOtmpC1LGCj8NUGrJmwoLQdK2r72nrxedPoLvaQpD5a/ qERtjGwU2GsHC8YPTSsGSN/vtFsZQbNfkr9Jhw9oZcaeDt/qMysS7Zy1vu8QOZEqKIuQ dgaSofrOUPtruE1Koxj76GYVC3FjufShtqhO362WzFrOuKIY+Nyt5gA9aWV0q6DbpXhv Hb3g==
X-Gm-Message-State: AE9vXwN4z6s/LooBzAQNskuo46P5piY5ejHPOUmqFe+KqFuC+VRmcKqUhlaSckkZCgX1G/2w3KXcsM2zZZAC0g==
X-Received: by 10.37.126.133 with SMTP id z127mr19347560ybc.68.1473213529466;  Tue, 06 Sep 2016 18:58:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.24.86 with HTTP; Tue, 6 Sep 2016 18:58:48 -0700 (PDT)
In-Reply-To: <4d628d80cee442cabfd473a62e520b14@XCH-RCD-017.cisco.com>
References: <6ECD9A3A-0D63-421B-953D-A516D773CCBA@qti.qualcomm.com> <4d628d80cee442cabfd473a62e520b14@XCH-RCD-017.cisco.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 6 Sep 2016 20:58:48 -0500
Message-ID: <CAKKJt-fREkRoDOjaiM=gtc-GjpVEpymhpeohbNRBGYaO8hJRWA@mail.gmail.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
Content-Type: multipart/alternative; boundary=001a114e1a221a2d93053be14141
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/XZ2q6QhT5fE7j8TQ_Uv-P7NQ-0s>
Cc: "tram@ietf.org" <tram@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>, "draft-ietf-tram-turn-mobility.all@ietf.org" <draft-ietf-tram-turn-mobility.all@ietf.org>, IESG <iesg@ietf.org>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [tram] GenART post-telechat comment on draft-ietf-tram-turn-mobility-08
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 01:58:53 -0000

--001a114e1a221a2d93053be14141
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I'll wait to see what Suresh thinks (we're discussing his Comment), but

On Tue, Sep 6, 2016 at 8:44 PM, Tirumaleswar Reddy (tireddy) <
tireddy@cisco.com> wrote:

> *From:* Pete Resnick [mailto:presnick@qti.qualcomm.com]
> *Sent:* Tuesday, September 6, 2016 9:25 PM
> *To:* IESG <iesg@ietf.org>
> *Cc:* tram@ietf.org; draft-ietf-tram-turn-mobility.all@ietf.org; General
> Area Review Team <gen-art@ietf.org>
> *Subject:* GenART post-telechat comment on draft-ietf-tram-turn-mobility-
> 08
>
>
>
> Greetings,
>
> I am the assigned Gen-ART reviewer for this draft. The General Area Revie=
w
> Team (Gen-ART) reviews all IETF documents being processed by the IESG for
> the IETF Chair. Please treat these comments just like any other
> participants comments.
>
> For more information, please see the FAQ at
>
> http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq.
>
> Document: draft-ietf-tram-turn-mobility-03
> Reviewer: Pete Resnick
> Review Date: 2016-09-06
> IESG Telechat date: 2016-09-01
>
> Summary: This is an odd post-telechat review, but I think the draft has
> gone from "Ready" to "Ready with an issue" because of an IESG Eval change=
.
>
> Details:
>
> I did not get to my post-Last Call GenART review of
> draft-ietf-tram-turn-mobility until after the telechat. Had I done so,
> which would have been on version -05, I would have said "Looks fine to me=
".
> However, I happened to look at the latest version, figuring I would just
> confirm. I found that a change was made in response to an IESG Evaluation
> comment from Suresh https://mailarchive.ietf.org/arch/msg/tram/
> SYVAXc1dF6xUcm0OQ9xyuaknJco:
>
> ------------------------------
> COMMENT:
>
>    - Section 3.2.1
>
> The section on sending a Refresh when the IP address does not change
> needs a little bit more tightening. Given that the server would reject
> the request with a mobility ticket in this case, it would be good to put
> in an explicit restriction to not add the mobility ticket in the
> following statement
>
> OLD: If a client wants to refresh an existing allocation and update its
> time-to-expiry or delete an existing allocation, it will send a Refresh
> Request as described in Section 7.1 of [RFC5766]
>
> NEW:
> If a client wants to refresh an existing allocation and update its
> time-to-expiry or delete an existing allocation, it MUST send a Refresh
> Request as described in Section 7.1 of [RFC5766] and MUST NOT include a
> MOBILITY-TICKET attribute.
>
> I'm not sure if the "MUST NOT" in the latter part of the sentence is
> correct: Since the server will reject it anyway, I don't see the harm in
> including the attribute that the "MUST NOT" implies, but perhaps this is
> belt-and-braces protocol description. On this point, I can't complain too
> much.
>
> [TR] =E2=80=9CMUST NOT=E2=80=9D is required to prevent the client from se=
nding the request
> with the ticket which will be rejected by the server and the client will
> have to again re-try the request without the ticket.
>
> However, I believe Suresh was incorrect in suggesting the first "MUST",
> and it should be removed. There is no harm being prevented here. "If a
> client wants X, it MUST send Y" is absolutely no different protocol-wise
> from "If a client wants X, it will send Y". The "MUST" is a misuse. I
> believe that this change should be undone before publication.
>
> [TR] I can the update the line; including Suresh to see if he has any
> objections
>

Given that we're usually in a minimize-the-number-of-round-trips
environment here, I'm more sympathetic to MUST as an optimization, and not
just belt-and-suspenders ("ask me no questions and I'll tell you no lies")
in this case than I would usually be.

Spencer


> -Tiru
>
> pr
> --
> Pete Resnick http://www.qualcomm.com/~presnick/
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>

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

<div dir=3D"ltr">I&#39;ll wait to see what Suresh thinks (we&#39;re discuss=
ing his Comment), but=C2=A0<div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On Tue, Sep 6, 2016 at 8:44 PM, Tirumaleswar Reddy (tireddy) <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:tireddy@cisco.com" target=3D"_blank">ti=
reddy@cisco.com</a>&gt;</span> wrote:<br><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"#3983C4" vlink=3D"#3983C4">
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> Pete Resnick [mailto:<a href=
=3D"mailto:presnick@qti.qualcomm.com" target=3D"_blank">presnick@qti.qualco=
mm.<wbr>com</a>]
<br>
<b>Sent:</b> Tuesday, September 6, 2016 9:25 PM<br>
<b>To:</b> IESG &lt;<a href=3D"mailto:iesg@ietf.org" target=3D"_blank">iesg=
@ietf.org</a>&gt;<br>
<b>Cc:</b> <a href=3D"mailto:tram@ietf.org" target=3D"_blank">tram@ietf.org=
</a>; <a href=3D"mailto:draft-ietf-tram-turn-mobility.all@ietf.org" target=
=3D"_blank">draft-ietf-tram-turn-mobility.<wbr>all@ietf.org</a>; General Ar=
ea Review Team &lt;<a href=3D"mailto:gen-art@ietf.org" target=3D"_blank">ge=
n-art@ietf.org</a>&gt;<br>
<b>Subject:</b> GenART post-telechat comment on draft-ietf-tram-turn-mobili=
ty-<wbr>08<u></u><u></u></span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div><div><div class=3D"h5">
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">Greetings,<u></=
u><u></u></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">I am the assign=
ed 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
 participants comments.<u></u><u></u></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">For more inform=
ation, please see the FAQ at<u></u><u></u></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif"><a href=3D"http=
://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" target=3D"_blank">http=
://wiki.tools.ietf.org/<wbr>area/gen/trac/wiki/GenArtfaq</a>.<u></u><u></u>=
</span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">Document: draft=
-ietf-tram-turn-mobility-<wbr>03<br>
Reviewer: Pete Resnick<br>
Review Date: 2016-09-06<br>
IESG Telechat date: 2016-09-01<u></u><u></u></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">Summary: This i=
s an odd post-telechat review, but I think the draft has gone from &quot;Re=
ady&quot; to &quot;Ready with an issue&quot; because of an IESG Eval change=
.<u></u><u></u></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">Details:<u></u>=
<u></u></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">I did not get t=
o my post-Last Call GenART review of draft-ietf-tram-turn-mobility until af=
ter the telechat. Had I done so, which would have been on version -05, I wo=
uld have said &quot;Looks fine to me&quot;. However, I
 happened to look at the latest version, figuring I would just confirm. I f=
ound that a change was made in response to an IESG Evaluation comment from =
Suresh
<a href=3D"https://mailarchive.ietf.org/arch/msg/tram/SYVAXc1dF6xUcm0OQ9xyu=
aknJco" target=3D"_blank">
https://mailarchive.ietf.org/<wbr>arch/msg/tram/<wbr>SYVAXc1dF6xUcm0OQ9xyua=
knJco</a>:<u></u><u></u></span></p>
<blockquote style=3D"border:none;border-left:solid #777777 1.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:0in;margin-right:0in;margin-bottom:3.75pt">
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-family:&quot;Arial&quot;,sans-serif;color:#777777">
<hr size=3D"3" width=3D"100%" align=3D"center">
</span></div>
<h2><span style=3D"font-family:&quot;Arial&quot;,sans-serif;color:#777777">=
COMMENT:<u></u><u></u></span></h2>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:#777777">
<span style=3D"font-family:&quot;Arial&quot;,sans-serif">Section 3.2.1<u></=
u><u></u></span></li></ul>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif;color:#777777">T=
he section on sending a Refresh when the IP address does not change<br>
needs a little bit more tightening. Given that the server would reject<br>
the request with a mobility ticket in this case, it would be good to put<br=
>
in an explicit restriction to not add the mobility ticket in the<br>
following statement<u></u><u></u></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif;color:#777777">O=
LD: If a client wants to refresh an existing allocation and update its<br>
time-to-expiry or delete an existing allocation, it will send a Refresh<br>
Request as described in Section 7.1 of [RFC5766]<u></u><u></u></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif;color:#777777">N=
EW:<br>
If a client wants to refresh an existing allocation and update its<br>
time-to-expiry or delete an existing allocation, it MUST send a Refresh<br>
Request as described in Section 7.1 of [RFC5766] and MUST NOT include a<br>
MOBILITY-TICKET attribute.<u></u><u></u></span></p>
</blockquote>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">I&#39;m not sur=
e if the &quot;MUST NOT&quot; in the latter part of the sentence is correct=
: Since the server will reject it anyway, I don&#39;t see the harm in inclu=
ding the attribute that the &quot;MUST NOT&quot; implies, but perhaps this
 is belt-and-braces protocol description. On this point, I can&#39;t compla=
in too much.
<span style=3D"color:#1f497d"><u></u><u></u></span></span></p>
</div></div><p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&qu=
ot;,sans-serif;color:#1f497d">[TR] =E2=80=9CMUST NOT=E2=80=9D is required t=
o prevent the client from sending the request with the ticket which will be=
 rejected by the server and the client will have to again re-try the reques=
t
 without the ticket.<u></u><u></u></span></p><span class=3D"">
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">However, I beli=
eve Suresh was incorrect in suggesting the first &quot;MUST&quot;, and it s=
hould be removed. There is no harm being prevented here. &quot;If a client =
wants X, it MUST send Y&quot; is absolutely no different protocol-wise
 from &quot;If a client wants X, it will send Y&quot;. The &quot;MUST&quot;=
 is a misuse. I believe that this change should be undone before publicatio=
n.<u></u><u></u></span></p>
</span><p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,s=
ans-serif;color:#1f497d">[TR] I can the update the line; including Suresh t=
o see if he has any objections</span></p></div></div></div></blockquote><di=
v><br></div><div>Given that we&#39;re usually in a minimize-the-number-of-r=
ound-trips environment here, I&#39;m more sympathetic to MUST as an optimiz=
ation, and not just belt-and-suspenders (&quot;ask me no questions and I&#3=
9;ll tell you no lies&quot;) in this case than I would usually be.</div><di=
v><br></div><div>Spencer</div><div>=C2=A0</div><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"#3983C4" vlink=3D"#3983C4"><div><div><p><spa=
n style=3D"color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11=
pt">-Tiru</span></p><span class=3D"">
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">pr<br>
-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" target=3D"_bl=
ank">http://www.qualcomm.com/~<wbr>presnick/</a><br>
Qualcomm Technologies, Inc. - <a href=3D"tel:%2B1%20%28858%29651-4478" valu=
e=3D"+18586514478" target=3D"_blank">+1 (858)651-4478</a><u></u><u></u></sp=
an></p>
</span></div>
</div>
</div>

</blockquote></div><br></div></div>

--001a114e1a221a2d93053be14141--


From nobody Tue Sep  6 20:28:00 2016
Return-Path: <tireddy@cisco.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 7CE0D12B03D; Tue,  6 Sep 2016 20:27:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.029
X-Spam-Level: 
X-Spam-Status: No, score=-16.029 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 aajDtxNy6c-u; Tue,  6 Sep 2016 20:27:57 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8136812B036; Tue,  6 Sep 2016 20:27:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3859; q=dns/txt; s=iport; t=1473218877; x=1474428477; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=capn+3W1+KI4QwJwGeqKrJaST4ubnBaWNdrMN1u/dm0=; b=BV4RjBJ1+dSi1E+iF4YsoEkEY/0qMxQFpmWMcsliuaHV/gOtmanR5oF7 XAwi1Vt1on8rAVyiElmmWxTpWHR8j58B+PFUH1yfrEiLDwL998iV3X35G vkzKZUU0x5CU0AjfS2kO61VlF5Ot/SS+NaR5xqdzDQKrsxgWhLqbJsDn+ Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BGAQAniM9X/5ldJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBgy0BAQEBAR5XfAeNKJ5WjDaCAiSFeAKBYjgUAQIBAQEBAQEBXhwLhGEBAQE?= =?us-ascii?q?DATo/BQcEAgEIEQQBAQEeCQchERQJCAIEDgUIiCgDDwgOuHwNgwwBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEXBYYvhE6CQ4FPCwYBAwNIhSoFiC6QczUBhiGGPoJRgXW?= =?us-ascii?q?EXokPiEOEC4N5AR42gxqBNXABhAQOF4EJfwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.30,294,1470700800"; d="scan'208";a="146142875"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Sep 2016 03:27:56 +0000
Received: from XCH-ALN-018.cisco.com (xch-aln-018.cisco.com [173.36.7.28]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u873Ruoq000457 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 7 Sep 2016 03:27:56 GMT
Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-ALN-018.cisco.com (173.36.7.28) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 6 Sep 2016 22:27:55 -0500
Received: from xch-rcd-017.cisco.com ([173.37.102.27]) by XCH-RCD-017.cisco.com ([173.37.102.27]) with mapi id 15.00.1210.000; Tue, 6 Sep 2016 22:27:55 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: "kathleen.moriarty.ietf@gmail.com" <kathleen.moriarty.ietf@gmail.com>
Thread-Topic: Kathleen Moriarty's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
Thread-Index: AQHSAfw9GKziJUsFG0mb9R1x8tRHg6BipUYwgAI9UoCAAMJZUA==
Date: Wed, 7 Sep 2016 03:27:55 +0000
Message-ID: <a45b893264144f779883cb78319fba6a@XCH-RCD-017.cisco.com>
References: <147247859789.14154.18257109792324801465.idtracker@ietfa.amsl.com> <d742e129f2714a0cabb722288bfeb1a6@XCH-RCD-017.cisco.com> <EC3E0CC4-79EE-4F5E-A59C-2BB78E13E4BB@gmail.com>
In-Reply-To: <EC3E0CC4-79EE-4F5E-A59C-2BB78E13E4BB@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.64.100]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/J7PQGGYI48ftkE5vNUJCovwQfIc>
Cc: "tram@ietf.org" <tram@ietf.org>, Simon Perreault <sperreault@jive.com>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, The IESG <iesg@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>
Subject: Re: [tram] Kathleen Moriarty's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 03:27:59 -0000

> -----Original Message-----
> From: kathleen.moriarty.ietf@gmail.com
> [mailto:kathleen.moriarty.ietf@gmail.com]
> Sent: Thursday, September 1, 2016 5:37 PM
> To: Tirumaleswar Reddy (tireddy) <tireddy@cisco.com>
> Cc: The IESG <iesg@ietf.org>; draft-ietf-tram-turn-server-discovery@ietf.=
org;
> Simon Perreault <sperreault@jive.com>; tram-chairs@ietf.org; tram@ietf.or=
g
> Subject: Re: Kathleen Moriarty's Discuss on draft-ietf-tram-turn-server-
> discovery-09: (with DISCUSS)
>=20
>=20
>=20
> Sent from my iPhone
>=20
> On Aug 31, 2016, at 3:02 AM, Tirumaleswar Reddy (tireddy)
> <tireddy@cisco.com> wrote:
>=20
> >> -----Original Message-----
> >> From: Kathleen Moriarty [mailto:Kathleen.Moriarty.ietf@gmail.com]
> >> Sent: Monday, August 29, 2016 7:20 PM
> >> To: The IESG <iesg@ietf.org>
> >> Cc: draft-ietf-tram-turn-server-discovery@ietf.org; Simon Perreault
> >> <sperreault@jive.com>; tram-chairs@ietf.org; sperreault@jive.com;
> >> tram@ietf.org
> >> Subject: Kathleen Moriarty's Discuss on
> >> draft-ietf-tram-turn-server-discovery-
> >> 09: (with DISCUSS)
> >>
> >> Kathleen Moriarty has entered the following ballot position for
> >> draft-ietf-tram-turn-server-discovery-09: Discuss
> >>
> >> When responding, please keep the subject line intact and reply to all
> >> email addresses included in the To and CC lines. (Feel free to cut
> >> this introductory paragraph, however.)
> >>
> >>
> >> Please refer to
> >> https://www.ietf.org/iesg/statement/discuss-criteria.html
> >> for more information about IESG DISCUSS and COMMENT positions.
> >>
> >>
> >> The document, along with other ballot positions, can be found here:
> >> https://datatracker.ietf.org/doc/draft-ietf-tram-turn-server-discover
> >> y/
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> -
> >> DISCUSS:
> >> ---------------------------------------------------------------------
> >> -
> >>
> >> This should be easy to resolve.  In reading the draft, it doesn't
> >> cover any mechanism for the TURN server to limit what clients can
> discover it.
> >> For the second and third method, it seems like there are possible
> >> ways to do this.  Could these be added to the security
> >> considerations?  You'd need to state that this isn't possible with
> >> the first method.  If there is a reason why it is always okay to
> >> discover a TURN server, please let me know why this is not appropriate=
 to
> add.  Thanks.
> >
> > I don't see a reason why TURN server discovery should be restricted onl=
y to
> specific clients. Please explain the scenarios for imposing such restrict=
ions.
>=20
> Hello Tiru,
>=20
> Are there any cases where some domains or addresses should be restricted?

Yes.

> When you have open services, it's possible to attack them.  It could be f=
rom a
> design or implementation problem that makes an exploit possible or it mig=
ht
> just be for network reconnaissance.  Is there something different about T=
URN
> servers that makes this point moot.

Restricting access to use the TURN server seems more important than discove=
ring the TURN server; will add more details that TURN servers deployed in D=
MZ must only process STUN requests from the trusted network and not from th=
e external network. Similarly TURN server in access network must only proce=
ss STUN requests only its subscribers. Access control can be provided by ac=
cess-control lists, firewalls and/or by user authentication to the TURN ser=
ver. We can also discuss other recommendations like per-subscriber quota li=
mit, ingress filtering.=20

Please share any other mechanisms you would like to use to discuss in the W=
G and include in the draft.

-Tiru

>=20
> Thank you,
> Kathleen
> >
> > Cheers,
> > -Tiru
> >
> >


From nobody Tue Sep  6 20:57:44 2016
Return-Path: <suresh.krishnan@ericsson.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 630FD12B128; Tue,  6 Sep 2016 20:57:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 kmUoHFIL_gam; Tue,  6 Sep 2016 20:57:24 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (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 63D3C12B016; Tue,  6 Sep 2016 20:57:24 -0700 (PDT)
X-AuditID: c6180641-e87ff70000000a0b-5b-57cf3bbf9d1e
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by  (Symantec Mail Security) with SMTP id 58.22.02571.FBB3FC75; Tue,  6 Sep 2016 23:57:21 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.03.0301.000; Tue, 6 Sep 2016 23:57:21 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, IESG <iesg@ietf.org>
Thread-Topic: GenART post-telechat comment on draft-ietf-tram-turn-mobility-08
Thread-Index: AQHSCFh4psfOltlceECMFEqRrV0QZQ==
Date: Wed, 7 Sep 2016 03:57:20 +0000
Message-ID: <E87B771635882B4BA20096B589152EF643E961F1@eusaamb107.ericsson.se>
References: <6ECD9A3A-0D63-421B-953D-A516D773CCBA@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrMLMWRmVeSWpSXmKPExsUyuXRPlO5B6/PhBh+PCluceP6a0eLqq88s FjP+TGS2uHK1hdniw9oLbA6sHkuW/GTyWDT1GWMAUxSXTUpqTmZZapG+XQJXxpXfO9gKVspV tD3+y9bA2CfRxcjJISFgIvF8wVHWLkYuDiGBDYwSB05tYoJwljFKnDtzmgmkig2oasPOz2C2 iICTxP1pzcwgRcwC6xklru54zwqSEBbwldi0+DRQggOoKEBifWMwRL2exKJr/9hBbBYBFYkf Sy6ygdi8QOVf57wBs4UEnCWOL/oBNp9RQEzi+6k1YDazgLjErSfzmSAuFZBYsuc8M4QtKvHy 8T9WCFtJ4uPv+ewQ9ToSC3Z/YoOwtSWWLXzNDLFLUOLkzCcsExhFZiEZOwtJyywkLbOQtCxg ZFnFyFFaXJCTm25kuIkRGBXHJNgcdzDu7fU8xCjAwajEw7tg8rlwIdbEsuLK3EOMEhzMSiK8 jP3nw4V4UxIrq1KL8uOLSnNSiw8xSnOwKInz6r9UDBcSSE8sSc1OTS1ILYLJMnFwSjUwWvsc kzjt8Y5b7mHhz9AzaUWxi3JWCot4/17/VDDm0oTDMnbhzyapb+/f+dBwtRy768st33v+rlhr dmBNycW/a48uY/JyzOI+MPm1AfucZQFcfJXyt15febxU4JFF7+uH/ZtOtqz4HPq58aHaBPdd NXxZvJsuTc8MXJ2UPUP/2M+Nd2/fLDlRPEOJpTgj0VCLuag4EQCxAcmdhgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/S7fDsYs1Mxqgl69Hd3RpXVg-iOE>
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-tram-turn-mobility.all@ietf.org" <draft-ietf-tram-turn-mobility.all@ietf.org>, "tram@ietf.org" <tram@ietf.org>
Subject: Re: [tram] GenART post-telechat comment on draft-ietf-tram-turn-mobility-08
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 03:57:26 -0000

Hi Pete,=0A=
=0A=
On 09/06/2016 12:05 PM, Pete Resnick wrote:=0A=
> Greetings,=0A=
>=0A=
> I am the assigned Gen-ART reviewer for this draft. The General Area Revie=
w=0A=
> Team (Gen-ART) reviews all IETF documents being processed by the IESG for=
 the=0A=
> IETF Chair. Please treat these comments just like any other participants=
=0A=
> comments.=0A=
>=0A=
> For more information, please see the FAQ at=0A=
>=0A=
> http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq.=0A=
>=0A=
> Document: draft-ietf-tram-turn-mobility-03=0A=
> Reviewer: Pete Resnick=0A=
> Review Date: 2016-09-06=0A=
> IESG Telechat date: 2016-09-01=0A=
>=0A=
> Summary: This is an odd post-telechat review, but I think the draft has g=
one=0A=
> from "Ready" to "Ready with an issue" because of an IESG Eval change.=0A=
>=0A=
> Details:=0A=
>=0A=
> I did not get to my post-Last Call GenART review of=0A=
> draft-ietf-tram-turn-mobility until after the telechat. Had I done so, wh=
ich=0A=
> would have been on version -05, I would have said "Looks fine to me".=0A=
> However, I happened to look at the latest version, figuring I would just=
=0A=
> confirm. I found that a change was made in response to an IESG Evaluation=
=0A=
> comment from Suresh=0A=
> https://mailarchive.ietf.org/arch/msg/tram/SYVAXc1dF6xUcm0OQ9xyuaknJco:=
=0A=
>=0A=
>     ---------------------------------------------------------------------=
--------=0A=
>=0A=
>=0A=
>         COMMENT:=0A=
>=0A=
>       * Section 3.2.1=0A=
>=0A=
>     The section on sending a Refresh when the IP address does not change=
=0A=
>     needs a little bit more tightening. Given that the server would rejec=
t=0A=
>     the request with a mobility ticket in this case, it would be good to =
put=0A=
>     in an explicit restriction to not add the mobility ticket in the=0A=
>     following statement=0A=
>=0A=
>     OLD: If a client wants to refresh an existing allocation and update i=
ts=0A=
>     time-to-expiry or delete an existing allocation, it will send a Refre=
sh=0A=
>     Request as described in Section 7.1 of [RFC5766]=0A=
>=0A=
>     NEW:=0A=
>     If a client wants to refresh an existing allocation and update its=0A=
>     time-to-expiry or delete an existing allocation, it MUST send a Refre=
sh=0A=
>     Request as described in Section 7.1 of [RFC5766] and MUST NOT include=
 a=0A=
>     MOBILITY-TICKET attribute.=0A=
>=0A=
> I'm not sure if the "MUST NOT" in the latter part of the sentence is corr=
ect:=0A=
> Since the server will reject it anyway, I don't see the harm in including=
 the=0A=
> attribute that the "MUST NOT" implies, but perhaps this is belt-and-brace=
s=0A=
> protocol description. On this point, I can't complain too much. However, =
I=0A=
> believe Suresh was incorrect in suggesting the first "MUST", and it shoul=
d be=0A=
> removed. There is no harm being prevented here. "If a client wants X, it =
MUST=0A=
> send Y" is absolutely no different protocol-wise from "If a client wants =
X,=0A=
> it will send Y". The "MUST" is a misuse. I believe that this change shoul=
d be=0A=
> undone before publication.=0A=
=0A=
I will try to explain my line of reasoning. Let me know where you disagree.=
 =0A=
If the client includes a MOBILTY-TICKET attribute in the refresh method, th=
e =0A=
refresh will fail. So, the MUST NOT is aimed at preventing the client from =
=0A=
sending a useless packet that will be rejected anyway. The MUST stresses th=
at =0A=
the original Refresh procedure from RFC5766 needs to be used instead of the=
 =0A=
Refresh procedure with the MOBILITY-TICKET described in this one. Anyway, I=
 =0A=
am not wedded to keeping the MUST as long as the MUST NOT prevents the =0A=
sending of a packet that is certain to be rejected.=0A=
=0A=
Thanks=0A=
Suresh=0A=
=0A=
=0A=
=0A=


From nobody Tue Sep  6 21:22:29 2016
Return-Path: <suresh.krishnan@ericsson.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 0EA5612B2A3; Tue,  6 Sep 2016 21:22:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, 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 NBhJo-uJ3kI8; Tue,  6 Sep 2016 21:22:20 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (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 93B7B12B113; Tue,  6 Sep 2016 21:22:20 -0700 (PDT)
X-AuditID: c618062d-743ff700000009b8-cf-57cf97a7a5d6
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by  (Symantec Mail Security) with SMTP id 85.B5.02488.7A79FC75; Wed,  7 Sep 2016 06:29:29 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.03.0301.000; Wed, 7 Sep 2016 00:22:16 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: "Prashanth Patil (praspati)" <praspati@cisco.com>, The IESG <iesg@ietf.org>
Thread-Topic: Suresh Krishnan's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
Thread-Index: AQHSBAfnnle9TS+moUifmMZPWr6O+Q==
Date: Wed, 7 Sep 2016 04:22:16 +0000
Message-ID: <E87B771635882B4BA20096B589152EF643E96358@eusaamb107.ericsson.se>
References: <147270350795.31961.8306227467315681365.idtracker@ietfa.amsl.com> <D3EDDAE4.130787%praspati@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDLMWRmVeSWpSXmKPExsUyuXRPiO7K6efDDZb/0bP4tC7aYsaficwW 3TuPMlpcvxJqsfznSjaLD2svsDmweUz5vZHVY8mSn0we/+Y8ZQ5gjuKySUnNySxLLdK3S+DK 2PzvJlPBBumKExu+MTUwLhLrYuTkkBAwkWh7f4epi5GLQ0hgA6PExJU3WCGcZYwSs47uZwOp YgOq2rDzMxOILSIQKDH1xF+wImaBR4wS/SeWMoMkhAVSJCafnMEOUZQq0TZvMSOErSfxruEu mM0ioCKxc18v2CBeAV+JFauWsYLYQgIlEjvObgWbwyggJvH91BqwGmYBcYlbT+YzQZwqILFk z3lmCFtU4uXjf6wQtpLEx9/z2SHqdSQW7P7EBmFrSyxb+JoZYpegxMmZT1gmMIrMQjJ2FpKW WUhaZiFpWcDIsoqRo7S4ICc33chgEyMwTo5JsOnuYLw/3fMQowAHoxIP74PT58KFWBPLiitz DzFKcDArifDOm3Q+XIg3JbGyKrUoP76oNCe1+BCjNAeLkjiv2CPFcCGB9MSS1OzU1ILUIpgs EwenVAPjjPm3U5UuFBZ6NLXVZpuw5fVz8JTYsWUp1dXbrHzYY5AfwNU7g+UUG+O80x8jmszi lke8rIk+rNz74Ifd3rSNr+52MYlV/L++wkYhcK3iBWmFipTbT0WOd8kbM612aYs5VO7Zcmj/ 9rmBz5ZF8tcoSl75O0Hz6IWlrI09s09q5Zw31a3Z4abEUpyRaKjFXFScCACK5bAdjwIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/tE5SoFIDiVz4Vw1Jvyv82JICkxk>
Cc: Simon Perreault <sperreault@jive.com>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, "tram@ietf.org" <tram@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>
Subject: Re: [tram] Suresh Krishnan's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 04:22:23 -0000

Hi Prashanth,=0A=
=0A=
On 09/02/2016 05:54 PM, Prashanth Patil (praspati) wrote:=0A=
> Hi Suresh,=0A=
> Apologies for the delay, just back from holiday. Please see inline..=0A=
>=0A=
> On 8/31/16, 9:18 PM, "Suresh Krishnan" <suresh.krishnan@ericsson.com>=0A=
> wrote:=0A=
>=0A=
>> Suresh Krishnan has entered the following ballot position for=0A=
>> draft-ietf-tram-turn-server-discovery-09: Discuss=0A=
>>=0A=
>> When responding, please keep the subject line intact and reply to all=0A=
>> email addresses included in the To and CC lines. (Feel free to cut this=
=0A=
>> introductory paragraph, however.)=0A=
>>=0A=
>>=0A=
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.htm=
l=0A=
>> for more information about IESG DISCUSS and COMMENT positions.=0A=
>>=0A=
>>=0A=
>> The document, along with other ballot positions, can be found here:=0A=
>> https://datatracker.ietf.org/doc/draft-ietf-tram-turn-server-discovery/=
=0A=
>>=0A=
>>=0A=
>>=0A=
>> ----------------------------------------------------------------------=
=0A=
>> DISCUSS:=0A=
>> ----------------------------------------------------------------------=
=0A=
>>=0A=
>> * Section 4.1.1.=0A=
>>=0A=
>> The DHCP procedure is underspecified. I think this can be easily fixed=
=0A=
>> but it requires some work.=0A=
>>=0A=
>> Please describe what sort of messages you would be using. i.e. are you=
=0A=
>> going for a stateful exchange to piggy pack with other address and confi=
g=0A=
>> information or are you going for a stateless Information-request based=
=0A=
>> exchange(Most likely). Is there an ORO? If so, what options are requeste=
d=0A=
>> in the ORO? Are there multiple request-response round trips as implied b=
y=0A=
>> the text?=0A=
>=0A=
> Does following text address your concerns?=0A=
>=0A=
> ..=0A=
>    DHCP can be used to determine the domain name related to an=0A=
>    interface's point of network attachment.  Network operators may=0A=
>    provide the domain name to be used for service discovery within an=0A=
>    access network using DHCP.  Sections 3.2 and 3.3 of [RFC5986] define=
=0A=
>    DHCP IPv4 and IPv6 access network domain name options,=0A=
>    OPTION_V4_ACCESS_DOMAIN and OPTION_V6_ACCESS_DOMAIN respectively, to=
=0A=
>    identify a domain name that is suitable for service discovery within=
=0A=
>    the access network.=0A=
>=0A=
>    For IPv4, the discovery procedure MUST request for an access network=
=0A=
>    domain name option in a Parameter Request List option, as described=0A=
>    in [RFC2131].  [RFC2132] defines the DHCP IPv4 domain name option;=0A=
>    while this option is less suitable, a client MAY request for it if=0A=
>    the access network domain name defined in [RFC5986] is not available.=
=0A=
>=0A=
>    For IPv6, the discovery procedure MUST request for an access network=
=0A=
>    domain name option in an Options Request Option (ORO), as described=0A=
>    in [RFC3315].=0A=
>=0A=
>    If neither option can be retrieved the procedure fails for this=0A=
>    interface.  If a result can be retrieved it will be used as input=0A=
>    for S-NAPTR resolution.=0A=
=0A=
Thank you. That certainly addresses one part of my DISCUSS but it still nee=
ds =0A=
additional text on the DHCPv6 side to specify which message exchange will b=
e =0A=
used. Did you intend to use the stateful exchange or the stateless exchange=
?=0A=
=0A=
Regards=0A=
Suresh=0A=
=0A=


From nobody Wed Sep  7 00:25:06 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
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 B1D6812B09A; Wed,  7 Sep 2016 00:24:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.808
X-Spam-Level: 
X-Spam-Status: No, score=-5.808 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_SORBS_SPAM=0.001, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 ryDJEWgSi3WA; Wed,  7 Sep 2016 00:24:56 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C672F12B006; Wed,  7 Sep 2016 00:24:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 934C3193BB7; Wed,  7 Sep 2016 08:24:34 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cPKKztMG3c7a; Wed,  7 Sep 2016 08:24:33 +0100 (IST)
Received: from [10.87.48.210] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 99B73193A62; Wed,  7 Sep 2016 08:24:32 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1473233073; bh=1w9auj01X5UxI2v0j2LLMzSVvJib72VGjrUZjcOFUSM=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=uxynRMOIGKs6CNmYGhCxh/dK8hTLJaD6gCKQMr5HoHJQt+LpVZa/dRHyAwiYoGOij 9M5o/Q3kyTFrw1kctpAaAXraurmlbESauMkSuYbVc+xu26DEuz0F+L1b4vUhaNwqqX 2YcQIHrQCsZSfoyTfx0t5MoI/fQK3d6ly4JolEjQ=
To: Pete Resnick <presnick@qti.qualcomm.com>, IESG <iesg@ietf.org>
References: <6ECD9A3A-0D63-421B-953D-A516D773CCBA@qti.qualcomm.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <66a3884d-17c3-8b94-7252-526c231a6cb6@cs.tcd.ie>
Date: Wed, 7 Sep 2016 08:24:32 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <6ECD9A3A-0D63-421B-953D-A516D773CCBA@qti.qualcomm.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms020907070608060904030002"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/tVPZEY3kr0pxFt07BQWnEwW91UA>
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-tram-turn-mobility.all@ietf.org, tram@ietf.org
Subject: Re: [tram] GenART post-telechat comment on draft-ietf-tram-turn-mobility-08
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 07:24:58 -0000

This is a cryptographically signed message in MIME format.

--------------ms020907070608060904030002
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hi Pete,

On 06/09/16 16:55, Pete Resnick wrote:
> However, I believe Suresh was incorrect in suggesting the first "MUST",=

> and it should be removed. There is no harm being prevented here. "If a
> client wants X, it MUST send Y" is absolutely no different protocol-wis=
e
> from "If a client wants X, it will send Y". The "MUST" is a misuse. I
> believe that this change should be undone before publication.

This is something we rehearsed at length and fairly
regularly (if only occasionally) when one Mr. Resnick
was on the IESG:-)

My impression of those discussions is that we ended
up with a draw: Pete continues to not like when such
gratuitous MUST statements are included, and is strictly
correct that they aren't needed. However, authors do do
that and the sky does not fall in, so others (incl. me)
feel that the IESG badgering authors on this topic is
counter-productive.

IOW, I don't think the change needs to be undone. But
I don't care if that happens or not in this case.

If the IESG were to extrapolate from that to suggesting
that Pete's preferred approach MUST be followed, then
I would have a problem with that. (But I hope we're not
going there:-)

S.


--------------ms020907070608060904030002
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CvIwggUIMIID8KADAgECAhBPzaE7pzYviUJyhmHTFBdnMA0GCSqGSIb3DQEBCwUAMHUxCzAJ
BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBD
ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGll
bnQgQ0EwHhcNMTYwMjA5MDkyODE1WhcNMTcwMjA5MDkyODE1WjBOMSIwIAYDVQQDDBlzdGVw
aGVuLmZhcnJlbGxAY3MudGNkLmllMSgwJgYJKoZIhvcNAQkBFhlzdGVwaGVuLmZhcnJlbGxA
Y3MudGNkLmllMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtuC0rYze/2JinSra
C9F2RjGdQZjNALLcW9C3WKTwYII3wBslobmHuPEYE5JaGItmzuKnAW619R1rD/kfoNWC19N3
rBZ6UX9Cmb9D9exCwYIwVuSwjrCQWGxgCtNQTrwKzCCpI790GRiMTvxvO7UmzmBrCaBLiZW5
R0fBjK5Yn6hUhAzGBkNbkIEL28cLJqH0yVz7Kl92OlzrQqTPEts5m6cDnNdY/ADfeAX18c1r
dxZqcAxhLotrCqgsVA4ilbQDMMXGTLlB5TP35HeWZuGBU7xu003rLcFLdOkD8xvpJoYZy9Kt
3oABXPS5yqtMK+XCNdqmMn+4mOtLwQSMmPCSiQIDAQABo4IBuTCCAbUwCwYDVR0PBAQDAgSw
MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAJBgNVHRMEAjAAMB0GA1UdDgQWBBQJ
QhvwQ5Fl372Z6xqo6fdn8XejTTAfBgNVHSMEGDAWgBQkgWw5Yb5JD4+3G0YrySi1J0htaDBv
BggrBgEFBQcBAQRjMGEwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbTA5
BggrBgEFBQcwAoYtaHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc2NhLmNsaWVudDEu
Y3J0MDgGA1UdHwQxMC8wLaAroCmGJ2h0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL3NjYS1jbGll
bnQxLmNybDAkBgNVHREEHTAbgRlzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllMCMGA1UdEgQc
MBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzBGBgNVHSAEPzA9MDsGCysGAQQBgbU3AQIE
MCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeTANBgkqhkiG
9w0BAQsFAAOCAQEArzrSv2C8PlBBmGuiGrzm2Wma46/KHtXmZYS0bsd43pM66Pc/MsqPE0HD
C1GzMFfwB6BfkJn8ijNSIhlgj898WzjvnpM/SO8KStjlB8719ig/xKISrOl5mX55XbFlQtX9
U6MrqRgbDIATxhD9IDr+ryvovDzChqgQj7mt2jYr4mdlRjsjod3H1VY6XglRmaaNGZfsCARM
aE/TU5SXIiqauwt5KxNGYAY67QkOBs7O1FkSXpTk7+1MmzJMF4nP8QQ5n8vhVNseF+/Wm7ai
9mtnrkLbaznMsy/ULo/C2yuLUWTbZZbf4EKNmVdme6tUDgYkFjAFOblfA7W1fSPiQGagYzCC
BeIwggPKoAMCAQICEGunin0K14jWUQr5WeTntOEwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MB4XDTE1MTIxNjAxMDAwNVoXDTMwMTIxNjAxMDAwNVowdTELMAkGA1UEBhMC
SUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5MSMwIQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL192vfDon2D9luC/dtbX64eG3XAtRmv
mCSsu1d52DXsCR58zJQbCtB2/A5uFqNxWacpXGGtTCRk9dEDBlmixEd8QiLkUfvHpJX/xKnm
VkS6Iye8wUbYzMsDzgnpazlPg19dnSqfhM+Cevdfa89VLnUztRr2cgmCfyO9Otrh7LJDPG+4
D8ZnAqDtVB8MKYJL6QgKyVhhaBc4y3bGWxKyXEtx7QIZZGxPwSkzK3WIN+VKNdkiwTubW5PI
dopmykwvIjLPqbJK7yPwFZYekKE015OsW6FV+s4DIM8UlVS8pkIsoGGJtMuWjLL4tq2hYQuu
N0jhrxK1ljz50hH23gA9cbMCAwEAAaOCAWQwggFgMA4GA1UdDwEB/wQEAwIBBjAdBgNVHSUE
FjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIBADAyBgNVHR8EKzAp
MCegJaAjhiFodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9zZnNjYS5jcmwwZgYIKwYBBQUHAQEE
WjBYMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5zdGFydHNzbC5jb20wMAYIKwYBBQUHMAKG
JGh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL2NhLmNydDAdBgNVHQ4EFgQUJIFsOWG+
SQ+PtxtGK8kotSdIbWgwHwYDVR0jBBgwFoAUTgvvGqRAW6UXaYcwyjRoQ9BBrvIwPwYDVR0g
BDgwNjA0BgRVHSAAMCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Bv
bGljeTANBgkqhkiG9w0BAQsFAAOCAgEAi+P3h+wBi4StDwECW5zhIycjBL008HACblIf26HY
0JdOruKbrWDsXUsiI0j/7Crft9S5oxvPiDtVqspBOB/y5uzSns1lZwh7sG96bYBZpcGzGxpF
NjDmQbcM3yl3WFIRS4WhNrsOY14V7y2IrUGsvetsD+bjyOngCIVeC/GmsmtbuLOzJ606tEc9
uRbhjTu/b0x2Fo+/e7UkQvKzNeo7OMhijixaULyINBfCBJb+e29bLafgu6JqjOUJ9eXXj20p
6q/CW+uVrZiSW57+q5an2P2i7hP85jQJcy5j4HzA0rSiF3YPhKGAWUxKPMAVGgcYoXzWydOv
Z3UDsTDTagXpRDIKQLZo02wrlxY6iMFqvlzsemVf1odhQJmi7Eh5TbxI40kDGcBOBHhwnaOu
mZhLP+SWJQnjpLpSlUOj95uf1zo9oz9e0NgIJoz/tdfrBzez76xtDsK0KfUDHt1/q59BvDI7
RX6gVr0fQoCyMczNzCTcRXYHY0tq2J0oT+bsb6sH2b4WVWAiJKnSYaWDjdA70qHX4mq9MIjO
/ZskmSY8wtAk24orAc0vwXgYanqNsBX5Yv4sN4Z9VyrwMdLcusP7HJgRdAGKpkR2I9U4zEsN
JQJewM7S4Jalo1DyPrLpL2nTET8ZrSl5Utp1UeGp/2deoprGevfnxWB+vHNQiu85o6MxggPM
MIIDyAIBATCBiTB1MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEpMCcG
A1UECxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIzAhBgNVBAMTGlN0YXJ0
Q29tIENsYXNzIDEgQ2xpZW50IENBAhBPzaE7pzYviUJyhmHTFBdnMA0GCWCGSAFlAwQCAQUA
oIICEzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjA5MDcw
NzI0MzJaMC8GCSqGSIb3DQEJBDEiBCDAZ/MLOmPh9DmjFvRKuaQROF9bJCCC6xlJX+j2Kw47
2zBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMIGaBgkrBgEEAYI3EAQxgYwwgYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMw
IQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzCB
nAYLKoZIhvcNAQkQAgsxgYyggYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYD
VQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzANBgkq
hkiG9w0BAQEFAASCAQA20ao3TlSrvd86dolAqn44VPeho+vHo8dJHAkI0rZmF8BxJTCfd2dH
oFvlcochVhsv6AADtdLXe+c1A6fzpSFw6lqI16oJHXy/PzoC8Sg5If4u41nDqz40GS94+Ps+
5XBB+iRA8DMNTnu3vBl7WPBYA66L+D5MzkBazZk0FsKm3RLyMNKXbeatJXBfdbBNG/vXG/N/
cuYF0+ESDHS4GM3Rju5t8ywfMYJdTSgQBHq6DZhvLoKpouBuBXP03pP75ElpNUYfja/lXIfO
bKeRsqBHeYCGfgWwoUGM10cgwKhJkUU83vva44RNen9UNem5Dp0TpatVWqAVkdPybymJOVlp
AAAAAAAA
--------------ms020907070608060904030002--


From nobody Wed Sep  7 08:23:47 2016
Return-Path: <presnick@qti.qualcomm.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 E2F7212B1FB; Wed,  7 Sep 2016 08:23:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.528
X-Spam-Level: 
X-Spam-Status: No, score=-8.528 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.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 KQEh4SUGwIhT; Wed,  7 Sep 2016 08:23:31 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A8A312B1FA; Wed,  7 Sep 2016 08:23:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1473261811; x=1504797811; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=GVWJlx/CZI7PZbcsA9D/8zPKpFFNZqr8tvI0XORo0Oc=; b=v1jr/wxV27fDG23FiHXrJITJgmKAS8xwArxl0+gq9aizmLN9GLwh1Ktf QjnONMDa7umPHAEKqG4l1KxVuLRogmyx7QO+RGlBJ3VnbF96SAM/gyjEm cxhz1oCmaK+sGeQimv9l66xqHDlnEK/d/q+pJBv82wVYmCbHqIu2Mc+PY k=;
X-IronPort-AV: E=Sophos;i="5.30,296,1470726000";  d="scan'208,217";a="222524409"
Received: from unknown (HELO Ironmsg03-R.qualcomm.com) ([10.53.140.107]) by wolverine01.qualcomm.com with ESMTP; 07 Sep 2016 08:23:30 -0700
X-IronPort-AV: E=McAfee;i="5700,7163,8280"; a="1213984931"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 07 Sep 2016 08:23:30 -0700
Received: from [10.64.128.83] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Wed, 7 Sep 2016 08:23:29 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Date: Wed, 7 Sep 2016 10:23:27 -0500
Message-ID: <092F2B7C-4B03-4956-9C0E-1C5983D2AF72@qti.qualcomm.com>
In-Reply-To: <E87B771635882B4BA20096B589152EF643E961F1@eusaamb107.ericsson.se>
References: <6ECD9A3A-0D63-421B-953D-A516D773CCBA@qti.qualcomm.com> <E87B771635882B4BA20096B589152EF643E961F1@eusaamb107.ericsson.se>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_59AA27B1-AB66-4D54-AB47-AC36ACCC1EDD_="
X-Mailer: MailMate (1.9.5r5260)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01C.na.qualcomm.com (10.85.0.83) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/8ZEekwukFR8pr3XED62L4G_Lxb4>
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-tram-turn-mobility.all@ietf.org" <draft-ietf-tram-turn-mobility.all@ietf.org>, IESG <iesg@ietf.org>, "tram@ietf.org" <tram@ietf.org>
Subject: Re: [tram] GenART post-telechat comment on draft-ietf-tram-turn-mobility-08
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 15:23:34 -0000

--=_MailMate_59AA27B1-AB66-4D54-AB47-AC36ACCC1EDD_=
Content-Type: text/plain; format=flowed

[Trimming down a bit]

On 6 Sep 2016, at 22:57, Suresh Krishnan wrote:

>>     OLD: If a client wants to refresh an existing allocation and 
>> update its
>>     time-to-expiry or delete an existing allocation, it will send a 
>> Refresh
>>     Request as described in Section 7.1 of [RFC5766]
>>
>>     NEW:
>>     If a client wants to refresh an existing allocation and update 
>> its
>>     time-to-expiry or delete an existing allocation, it MUST send a 
>> Refresh
>>     Request as described in Section 7.1 of [RFC5766] and MUST NOT 
>> include a
>>     MOBILITY-TICKET attribute.
>
> I will try to explain my line of reasoning. Let me know where you 
> disagree.
> If the client includes a MOBILTY-TICKET attribute in the refresh 
> method, the
> refresh will fail. So, the MUST NOT is aimed at preventing the client 
> from
> sending a useless packet that will be rejected anyway.

"Useless" seems not a good reason for a "MUST NOT". Perhaps Tiru's 
explanation of "will cause an extra retransmission" is a better reason. 
But as I said, this isn't one that I will complain too vociferously 
about: What this says is "don't include the attribute; it will be 
rejected and you'll have to retransmit"; if you want a "MUST NOT" for 
that, so be it. But:

> The MUST stresses that
> the original Refresh procedure from RFC5766 needs to be used instead 
> of the
> Refresh procedure with the MOBILITY-TICKET described in this one.

Ah! If that's was meant, that's not what was said. It sounds like you're 
saying that the client *can't* refresh a request by simply sending an 
allocate request with the old MOBILITY-TICKET. And then I get a bit 
confused about the MUST NOT: The next sentence after this bit says:

    If the client wants to retain
    the existing allocation in case of IP change, it will include the
    MOBILITY-TICKET attribute received in the Allocate Success response.

The previous sentence says that you MUST NOT include the attribute. This 
sentence says that you do include it. I suspect that what was intended 
was, "If you *just* want to refresh to retain the existing allocation in 
case of an IP change, you can send an allocate request including the old 
MOBILITY-TICKET attribute. If you need to update time-to-expiry or 
delete the allocation, then you *can't* just send a new allocate request 
with the attribute; that will get rejected. You instead *have to* use 
the refresh request in 5766." Do I have that right? If so, the paragraph 
could use a rewrite; it's not the MUST and the MUST NOT that are the 
problem.

> Anyway, I
> am not wedded to keeping the MUST as long as the MUST NOT prevents the
> sending of a packet that is certain to be rejected.

Ack. See above.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478
--=_MailMate_59AA27B1-AB66-4D54-AB47-AC36ACCC1EDD_=
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">[Trimming down a bit]</p>

<p dir=3D"auto">On 6 Sep 2016, at 22:57, Suresh Krishnan wrote:</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:pre-wrap"><blockquote style=3D"border-left:2px =
solid #777; color:#777; margin:0 0 5px; padding-left:5px"><blockquote sty=
le=3D"border-left:2px solid #777; color:#999; margin:0 0 5px; padding-lef=
t:5px; border-left-color:#999"><div dir=3D"auto">    OLD: If a client wan=
ts to refresh an existing allocation and update its
</div><div dir=3D"auto">    time-to-expiry or delete an existing allocati=
on, it will send a Refresh
</div><div dir=3D"auto">    Request as described in Section 7.1 of [RFC57=
66]
</div><div dir=3D"auto">
</div><div dir=3D"auto">    NEW:
</div><div dir=3D"auto">    If a client wants to refresh an existing allo=
cation and update its
</div><div dir=3D"auto">    time-to-expiry or delete an existing allocati=
on, it MUST send a Refresh
</div><div dir=3D"auto">    Request as described in Section 7.1 of [RFC57=
66] and MUST NOT include a
</div><div dir=3D"auto">    MOBILITY-TICKET attribute.
</div></blockquote><div dir=3D"auto">
</div><div dir=3D"auto">I will try to explain my line of reasoning. Let m=
e know where you disagree.
</div><div dir=3D"auto">If the client includes a MOBILTY-TICKET attribute=
 in the refresh method, the
</div><div dir=3D"auto">refresh will fail. So, the MUST NOT is aimed at p=
reventing the client from
</div><div dir=3D"auto">sending a useless packet that will be rejected an=
yway.
</div></blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">"Useless" seems not a good reason for a "MUST NOT". Perha=
ps Tiru's explanation of "will cause an extra retransmission" is a better=
 reason. But as I said, this isn't one that I will complain too vociferou=
sly about: What this says is "don't include the attribute; it will be rej=
ected and you'll have to retransmit"; if you want a "MUST NOT" for that, =
so be it. But:</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:pre-wrap"><blockquote style=3D"border-left:2px =
solid #777; color:#777; margin:0 0 5px; padding-left:5px"><div dir=3D"aut=
o">The MUST stresses that
</div><div dir=3D"auto">the original Refresh procedure from RFC5766 needs=
 to be used instead of the
</div><div dir=3D"auto">Refresh procedure with the MOBILITY-TICKET descri=
bed in this one.
</div></blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">Ah! If that's was meant, that's not what was said. It sou=
nds like you're saying that the client <em>can't</em> refresh a request b=
y simply sending an allocate request with the old MOBILITY-TICKET. And th=
en I get a bit confused about the MUST NOT: The next sentence after this =
bit says:</p>

<p dir=3D"auto">If the client wants to retain<br>
   the existing allocation in case of IP change, it will include the<br>
   MOBILITY-TICKET attribute received in the Allocate Success response.</=
p>

<p dir=3D"auto">The previous sentence says that you MUST NOT include the =
attribute. This sentence says that you do include it. I suspect that what=
 was intended was, "If you <em>just</em> want to refresh to retain the ex=
isting allocation in case of an IP change, you can send an allocate reque=
st including the old MOBILITY-TICKET attribute. If you need to update tim=
e-to-expiry or delete the allocation, then you <em>can't</em> just send a=
 new allocate request with the attribute; that will get rejected. You ins=
tead <em>have to</em> use the refresh request in 5766." Do I have that ri=
ght? If so, the paragraph could use a rewrite; it's not the MUST and the =
MUST NOT that are the problem.</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:pre-wrap"><blockquote style=3D"border-left:2px =
solid #777; color:#777; margin:0 0 5px; padding-left:5px"><div dir=3D"aut=
o">Anyway, I
</div><div dir=3D"auto">am not wedded to keeping the MUST as long as the =
MUST NOT prevents the
</div><div dir=3D"auto">sending of a packet that is certain to be rejecte=
d.
</div></blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">Ack. See above.</p>

<p dir=3D"auto">pr<br>
-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" style=3D"co=
lor:#3983C4">http://www.qualcomm.com/~presnick/</a><br>
Qualcomm Technologies, Inc. - +1 (858)651-4478</p>
</div>
</div>
</body>
</html>

--=_MailMate_59AA27B1-AB66-4D54-AB47-AC36ACCC1EDD_=--


From nobody Wed Sep  7 08:27:25 2016
Return-Path: <presnick@qti.qualcomm.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 25D8412B1D1; Wed,  7 Sep 2016 08:27:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.528
X-Spam-Level: 
X-Spam-Status: No, score=-8.528 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.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 GmKYjwrZxUAq; Wed,  7 Sep 2016 08:27:21 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD95D12B209; Wed,  7 Sep 2016 08:27:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1473262039; x=1504798039; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=x4+xxqnoI8Hidlq9mMqaBTmTrz1j+JugnyE2Fz9s8Yw=; b=zfhE/FCedPB8eYB3+z102zRmvmKdtoZRosOULN3EM1vM7/343D1YeFmP m3Yr3M0X7eSdavihkjx8KqoIFDQWbyjvd8xt+8g9YAB6wcwYU7nZSs5ZE pgRt5n8OFtQzrO418UOXRx8eoAqY0Anh4rcDilcB0rEF7gxesWeuqtiih g=;
X-IronPort-AV: E=Sophos;i="5.30,296,1470726000";  d="scan'208,217";a="222524766"
Received: from unknown (HELO Ironmsg04-R.qualcomm.com) ([10.53.140.108]) by wolverine01.qualcomm.com with ESMTP; 07 Sep 2016 08:27:19 -0700
X-IronPort-AV: E=McAfee;i="5700,7163,8281"; a="1267962939"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 07 Sep 2016 08:27:18 -0700
Received: from [10.64.128.83] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Wed, 7 Sep 2016 08:27:16 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Date: Wed, 7 Sep 2016 10:27:12 -0500
Message-ID: <38B980BF-5391-4E5E-BF5A-13797A095AC1@qti.qualcomm.com>
In-Reply-To: <66a3884d-17c3-8b94-7252-526c231a6cb6@cs.tcd.ie>
References: <6ECD9A3A-0D63-421B-953D-A516D773CCBA@qti.qualcomm.com> <66a3884d-17c3-8b94-7252-526c231a6cb6@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_9828B6DB-BFB4-4A8E-832B-6BC6AD33280E_="
X-Mailer: MailMate (1.9.5r5260)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01B.na.qualcomm.com (10.85.0.82) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/qlqyNlNDVjY12dpEzxB38G0OhwY>
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-tram-turn-mobility.all@ietf.org, IESG <iesg@ietf.org>, tram@ietf.org
Subject: Re: [tram] GenART post-telechat comment on draft-ietf-tram-turn-mobility-08
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 15:27:23 -0000

--=_MailMate_9828B6DB-BFB4-4A8E-832B-6BC6AD33280E_=
Content-Type: text/plain; format=flowed; markup=markdown

Stephen,

As per my reply to Suresh: It is often the case that the gratuitous use 
of "MUST"s hides ambiguities in meaning that need to be fixed anyway.

And for the sake of keeping things the same as they were when I was on 
the IESG, I say to you, with great affection:

:-b

pr

On 7 Sep 2016, at 2:24, Stephen Farrell wrote:

>
> Hi Pete,
>
> On 06/09/16 16:55, Pete Resnick wrote:
>> However, I believe Suresh was incorrect in suggesting the first 
>> "MUST",
>> and it should be removed. There is no harm being prevented here. "If 
>> a
>> client wants X, it MUST send Y" is absolutely no different 
>> protocol-wise
>> from "If a client wants X, it will send Y". The "MUST" is a misuse. I
>> believe that this change should be undone before publication.
>
> This is something we rehearsed at length and fairly
> regularly (if only occasionally) when one Mr. Resnick
> was on the IESG:-)
>
> My impression of those discussions is that we ended
> up with a draw: Pete continues to not like when such
> gratuitous MUST statements are included, and is strictly
> correct that they aren't needed. However, authors do do
> that and the sky does not fall in, so others (incl. me)
> feel that the IESG badgering authors on this topic is
> counter-productive.
>
> IOW, I don't think the change needs to be undone. But
> I don't care if that happens or not in this case.
>
> If the IESG were to extrapolate from that to suggesting
> that Pete's preferred approach MUST be followed, then
> I would have a problem with that. (But I hope we're not
> going there:-)
>
> S.
>


-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478
--=_MailMate_9828B6DB-BFB4-4A8E-832B-6BC6AD33280E_=
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">Stephen,</p>

<p dir=3D"auto">As per my reply to Suresh: It is often the case that the =
gratuitous use of "MUST"s hides ambiguities in meaning that need to be fi=
xed anyway.</p>

<p dir=3D"auto">And for the sake of keeping things the same as they were =
when I was on the IESG, I say to you, with great affection:</p>

<p dir=3D"auto">:-b</p>

<p dir=3D"auto">pr</p>

<p dir=3D"auto">On 7 Sep 2016, at 2:24, Stephen Farrell wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">Hi Pete,</p>

<p dir=3D"auto">On 06/09/16 16:55, Pete Resnick wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 5=
px; padding-left:5px; border-left-color:#999">
<p dir=3D"auto">However, I believe Suresh was incorrect in suggesting the=
 first "MUST",<br>
and it should be removed. There is no harm being prevented here. "If a<br=
>
client wants X, it MUST send Y" is absolutely no different protocol-wise<=
br>
from "If a client wants X, it will send Y". The "MUST" is a misuse. I<br>=

believe that this change should be undone before publication.</p>
</blockquote>

<p dir=3D"auto">This is something we rehearsed at length and fairly<br>
regularly (if only occasionally) when one Mr. Resnick<br>
was on the IESG:-)</p>

<p dir=3D"auto">My impression of those discussions is that we ended<br>
up with a draw: Pete continues to not like when such<br>
gratuitous MUST statements are included, and is strictly<br>
correct that they aren't needed. However, authors do do<br>
that and the sky does not fall in, so others (incl. me)<br>
feel that the IESG badgering authors on this topic is<br>
counter-productive.</p>

<p dir=3D"auto">IOW, I don't think the change needs to be undone. But<br>=

I don't care if that happens or not in this case.</p>

<p dir=3D"auto">If the IESG were to extrapolate from that to suggesting<b=
r>
that Pete's preferred approach MUST be followed, then<br>
I would have a problem with that. (But I hope we're not<br>
going there:-)</p>

<p dir=3D"auto">S.</p>
</blockquote>

<p dir=3D"auto">-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" style=3D"co=
lor:#3983C4">http://www.qualcomm.com/~presnick/</a><br>
Qualcomm Technologies, Inc. - +1 (858)651-4478</p>
</div>
</div>
</body>
</html>

--=_MailMate_9828B6DB-BFB4-4A8E-832B-6BC6AD33280E_=--


From nobody Wed Sep  7 14:22:43 2016
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 7CB7312B118; Wed,  7 Sep 2016 14:22:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.903
X-Spam-Level: 
X-Spam-Status: No, score=-0.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_MULTIPLE_AT=1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ingate.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 4DCdbT0dqeza; Wed,  7 Sep 2016 14:22:40 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0061.outbound.protection.outlook.com [104.47.2.61]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB8FC12B0C7; Wed,  7 Sep 2016 14:22:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ingate.onmicrosoft.com; s=selector1-ingate-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=nbNJQrOQDW274a5bHT9/LiRpMnOG2P/MVsDJZ62Boaw=; b=qm4hVPM1BjYEWukFNKKmFbYMLCeAFm+8sV9vV/uwj8dzGopfYDcp/Sqbk060+JHxiJxOq6LSJKei8tOE0QIfVVaTkwWry0BwddZr/Q5qoKpSREk0g8SKijFiKiMY1KIir5p0YScsItmiELK/zBSUgMrtmL5varBMPoYuUOPCXa4=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=karl@ingate.com; 
Received: from Kallei7 (90.227.80.227) by AM4PR01MB1827.eurprd01.prod.exchangelabs.com (10.167.85.25) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id 15.1.599.9; Wed, 7 Sep 2016 21:22:34 +0000
From: Karl Stahl <karl.stahl@ingate.com>
To: "'Tirumaleswar Reddy (tireddy)'" <tireddy@cisco.com>, <kathleen.moriarty.ietf@gmail.com>
References: <147247859789.14154.18257109792324801465.idtracker@ietfa.amsl.com> <d742e129f2714a0cabb722288bfeb1a6@XCH-RCD-017.cisco.com> <EC3E0CC4-79EE-4F5E-A59C-2BB78E13E4BB@gmail.com> <a45b893264144f779883cb78319fba6a@XCH-RCD-017.cisco.com>
In-Reply-To: <a45b893264144f779883cb78319fba6a@XCH-RCD-017.cisco.com>
Date: Wed, 7 Sep 2016 23:22:18 +0200
Message-ID: <0a2501d2094d$f3bfc9d0$db3f5d70$@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: AQHSAfw9GKziJUsFG0mb9R1x8tRHg6BipUYwgAI9UoCAAMJZUIAI7c6w
Content-Language: sv
X-Originating-IP: [90.227.80.227]
X-ClientProxiedBy: DM2PR07CA0039.namprd07.prod.outlook.com (10.141.52.167) To AM4PR01MB1827.eurprd01.prod.exchangelabs.com (10.167.85.25)
X-MS-Office365-Filtering-Correlation-Id: b2dd5307-2688-4c60-ad90-08d3d7651778
X-Microsoft-Exchange-Diagnostics: 1; AM4PR01MB1827; 2:ubQhtckouCqa6xMXaT1Y+A/mwubJKSOkZ2xauXmi2aTwwpZdplAUeFeVxJZA5fAQgzCDg8BWu+7muOJQk4Nj1fqvuhlhEWH2ZhxGJDIT9EBoLzxAJ6mhkZziVg3AAhIWPJ+N2KX1bq8EQR3EVe27eeH3kXg4E8NIEvHy27i7uDRwkhAEkr4Pvxs7z6eaqCOq; 3:+D/4TW+6Gr/sKxYY3L8wAKke0ciccLrf31KtCObkpTOYlDHpreL1JiuchJ4l4g8uKqVglCHKfaoh7wpOj9ON5GVJI3PnLjIC3VhlXZosEPpz/WBmY17eJFeDRw1UDSpL; 25:+AKd9yx4Gl1Z6pqpXT6gD6Lwhz5rUAf3wlXttaicyH7Kt7UOIG9lr2ARJ1tRhJL+P/s0qk2jXNMsCC9iRo25YrdDqzcDZIsxIy3yG8XvQ39KnpU1NOlWodMjcazd7Dw0Nr6EZygEW13MceNz88+Hv8E4UFPVj2cWovUb2/aogZ9wsqvhN//l3jMrssoAcl6EnI5KV17OhlF/hRX5PdMzV78V3L6znroskbvsumZ0A+SSJlODs+uukuutTIA2tWRwX1puCjJvJfWy1Fd+CqPz0HCZC8JT7wgz3On2MY2UODJMwPjtYnLshplIIQPZMqIJdwMsRlPXSmCSqCEdMDnb3qfWGcABQfoiof6TVBlOHlY3dvHrhVM4aVqk3qqYNEFwsr4Wzzw6sTzlmORGR4SE29iciJ2Nxrp0VnFlCGuO80g=
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AM4PR01MB1827;
X-Microsoft-Exchange-Diagnostics: 1; AM4PR01MB1827; 31:EVUuwCGl9eNhHAgUJZBoL1SRDjAataqK8y0hwhg2irEVS4ILA2gGCC9zaX+wQJJUx8B8ekPzR2Ims+t2nREZoRtLXSSIuLq9uL6Wie/8a58ZLoTq4Jpa4J4eCinTJ1RHx3BJAuE7r7IbELOqJm1wsGqvSvZRSxcjM5wIziMqsYAqXUbvw3p+Xqd42Y/CO6RT9tUgPVnPP4p8aBdS8Yd7bENN+NfTnDmPjPUCwat51OI=; 4:SxwblOS+5dFdEl+OsRv/O98aYvQ1vRSTBOgE3wPvy/hAIGaS8XWwYiDWv0PKNPaNfjNRYwGf32tgKV+KEmUhxc1IYO9TuFnXdXKn0KKIYRN6dDNCydid5UCOY8iZ7+8V7MpUiAW+gHzPhd2jU8YO4qekj4asnayz+DEuQscVRyHPu54cWwhjfWN3rugZBen/JlFGWK1MeK81eytZ+oJSdazWXtrth0AoNHbyZEkt76QcxQVHeiirJjHD+8rXGmDsfSpqxSVmGhvl7cw5roeQ8Qmyq61tKiylI3ayUNnWoEuz1FpGCnyZ+JMsezdmYRXW52B7H7xiHtHq+om8djb+T5I9wQvRqhr7cZPZjO2NV5uFrnVCZ8LmbzUyg0YDS+2isFE/kXr5vx0Zf9dRNtD1IE2QdRXvZBTEzK8QNZ9geF1TAsso4flXa9mmKADQEGR/n7DYNc+rPF5gz//sVv17AVPufYzeYWWurzNvDQdkaEy4124OgRoYPpQmAh5ioavc8a18I8j4uWKjLXurD6MLyZwcBaGQG5f1Wb8t240i8I0qSFGFNcyZtkY1jQKdVAcMpcMtNdTy21gFtx8ikE7+lALQ9+tz/oVeuFXQWz7UYyc=
X-Microsoft-Antispam-PRVS: <AM4PR01MB1827FDDB76AB5418ADD90BEFB1F80@AM4PR01MB1827.eurprd01.prod.exchangelabs.com>
X-Exchange-Antispam-Report-Test: UriScan:(158342451672863)(120809045254105)(192374486261705)(95692535739014)(116097685857584);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6043046)(6042046); SRVR:AM4PR01MB1827; BCL:0; PCL:0; RULEID:; SRVR:AM4PR01MB1827; 
X-Forefront-PRVS: 0058ABBBC7
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(4630300001)(6009001)(7916002)(24454002)(13464003)(199003)(189002)(38534002)(377454003)(36756003)(7846002)(15975445007)(2906002)(8746002)(96836002)(33646002)(84116002)(81156014)(93886004)(5660300001)(9686002)(105586002)(5003630100001)(305945005)(4326007)(14726001)(106356001)(23756003)(76176999)(2950100001)(68736007)(19580395003)(101416001)(66066001)(81166006)(50226002)(19580405001)(568814002)(97736004)(92566002)(61296003)(50466002)(229853001)(1420700001)(5001770100001)(47776003)(3846002)(102836003)(106116001)(8676002)(7736002)(230783001)(6116002)(586003)(189998001)(42186005)(77096005)(50986999); DIR:OUT; SFP:1101; SCL:1; SRVR:AM4PR01MB1827; 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; AM4PR01MB1827; 23:KckZ30UHskUVp2T40W/inNPjC2AwD2vJ5weP2Mm?= =?iso-8859-1?Q?PFy9sC8r2oi1Cma5cTzgBbwq2zYXv1SgLqeiEdesAA8zPljPP9teoIVz0C?= =?iso-8859-1?Q?31p6+jIH9oAY4zoZ5TuLD6RJYkATp9D6CNcOWvd/XtbLiuYqj6KQPFdIhh?= =?iso-8859-1?Q?7sw42Co/OsAoGQHM/z7smcaPLhXI9sW0xL5mHZIFg8mscc8bUKcb5pTEhX?= =?iso-8859-1?Q?XFbDkmHyAAenMr83opI6CrpCMo0BTHA+EgKRMY3emqMT2/klmGeyxJu3Mq?= =?iso-8859-1?Q?7oVwpPAUJiaYkBTOmdPvkS4i1JjwaGBoQGBdytLv3eXbS/eQ1hl8nh+3P0?= =?iso-8859-1?Q?6aBq6Z19HDQKSWmispRA0qwAbALF7cr8IjDsDPDDDWbDSn5AfOSyVoXWUJ?= =?iso-8859-1?Q?2iqoN0YtTeCfruN8UGRIo0kB61w0MGj3pkLILzNN0QyoXmiSboAW4OKVe2?= =?iso-8859-1?Q?059vmZ0p6jLGDsol7KYO3WRadmXmq5Ebg9m9/A931GKsowRTDAzMZ2qRCd?= =?iso-8859-1?Q?ivTykNh9pD70td+BaECMJ8/p4p2Sf0j0i8unDP5pF1TtRpheGPFQNNBn95?= =?iso-8859-1?Q?+7gurWbZqRxUo/Og3AARh2Cc7uBT52TbkXJ32EdpR8ujBROSlZm93z4hNW?= =?iso-8859-1?Q?COfEOUzp4fjfqgbgIaAZUReX12wGfb/uJopFEYpkz8ql9GYH4wU5A5Y0t+?= =?iso-8859-1?Q?C/5BewVg1cJC/+zaMbVCdDLYSrYrHNnmQkinRl/+g8qq89lU/Yq2ZYgwhr?= =?iso-8859-1?Q?EzDcSum7Qx3jRzJNSDM5qd5B7+TaG6Brl9ezDzzxsTs09w3Kp5UzXbK0RO?= =?iso-8859-1?Q?3oklCHJA8qS9bXz4bynEkSbDhkmp+w8MyYqgFmpLGqjvZyxZqra71AHlxc?= =?iso-8859-1?Q?TI/vEgbULZBcnBhZ0uVkkKIRY77/eEDqhhRuo/Ch+JGVdSl7k0/o7nQWSk?= =?iso-8859-1?Q?TR0MpUMhKPN4yeGYjYJBEX4864swKgTdMpUKm0SdVIUrSgKtLhcK8rk2x+?= =?iso-8859-1?Q?DtdTEPVX1nSOcvd1MTFSAPrkuGf/FNNkAPbNYkli/eQJ3ymDER1YReRsl1?= =?iso-8859-1?Q?5vhTMUIeLgfogrckve8LrQNIN6xrXjp4YsVULaVkKfFm1bWHaVt3eyIHLC?= =?iso-8859-1?Q?n1kwAIXPW/9+3b1zTYNvg1lljjY+32U8B1VXsz3K0mOew8CUqEBZQ9TmKZ?= =?iso-8859-1?Q?pYF3cC1icSxp/aPN5Tm+Qb+SlUH++hC8ZOhqWlVcc1P2oDFu1LlMhCjIU5?= =?iso-8859-1?Q?zamtIk6N9UPJxpOw7bsUks/qi8aGVgIV7o6Xd9S99JPoZFdkz1k1bHZ2/R?= =?iso-8859-1?Q?C4UO0tF/IuamCQHOTY9gnTv8ylaq+GqZ9KxsYFFYj1fSdaq5DdzaL/qaE1?= =?iso-8859-1?Q?ZiqpYizZW7o2GpyGaint6borZzrcDj+d41xAbCeyjG4lsnCEDPu98mrzip?= =?iso-8859-1?Q?8GymMDKBhgakI5bbD90HN6gpnqikUGvdq+n?=
X-Microsoft-Exchange-Diagnostics: 1; AM4PR01MB1827; 6:9vYI1zt3+d4F0NSXz5wSDb6m1O6aIZ0ENLUicn7mDSiIkI2oh7aM2Az8h0JEHA3xnY+6mXmQI3daTfUFO6TWnkMSCc+NrdCgK7NR+wc+xuEaEBHJagN6O9sBSoN6GXA4C7SaEaQFaZFOsVVAn8IAgaJoK1agRV4H8jIvcZhallxe9aWVsOMDtJLNQmGWCb3mNmz9sO/M6GiLVeE4znn+MLFzjrPEPn7ZCOmmEeeKWAV+TlpMgSKSxiOkLLfTBvKio7Yq1UKXSkNf402nfM8Y362xpAy0nYSQmzHM498scIiSBrSaaHUyXDj2XgoPXPsr; 5:j+TAet4Lr+08RL7SQ+s5kcBBFAzJucpn1+TxWRO6jfwxk3404XbgW2gNk9OixWW95oTePzB37Ge3YR8xHxg+lWsD2hhDhKjSvcjiQKRKIQBq3py+/P23NekkqU5jL8tGYb0WY2xZC5aYdtlWaNGapA==; 24:orU+gBiQEs4+qorihXM/7gaMu5TNhXgbqMNzpMyZsXCrfZ+cdqk+Yerhlv9LWzoZF2GuFsszTVWC8+bQNvP1SBjSNKidyQKqCccEaaZtZNU=; 7:6yEkMcJ+g/QA+LFAC3TrfUKDgkJqFFxkqgmd68UilcxJHBaEKPWUbolJlF6TEGhRu1nh1jyt+NgdCpRo1D4tH2lphkkiryCa+9tvFOEwAswYqn+IdEBirL6P5KYd5QyPnjpN8cdhur7klZBYym+8WB7aawWPSE5GKK+nHXAAVQ+YltnY+XUyEtBBvSTll6hlVaxiA6LHsQVfNrAw7wZtTbsDJ/LvXxHY7g+W/xiG7tBD4gAzoCz6HwaJynpC7PDJ
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: ingate.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 07 Sep 2016 21:22:34.9855 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM4PR01MB1827
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/hYGsNsQXdPb-eef1Sv6rP5ZMbic>
Cc: tram-chairs@ietf.org, 'Simon Perreault' <sperreault@jive.com>, draft-ietf-tram-turn-server-discovery@ietf.org, tram@ietf.org, 'The IESG' <iesg@ietf.org>
Subject: Re: [tram] Kathleen Moriarty's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 21:22:42 -0000

-----Ursprungligt meddelande-----
Fr=E5n: tram [mailto:tram-bounces@ietf.org] F=F6r Tirumaleswar Reddy =
(tireddy)
Skickat: den 7 september 2016 05:28
Till: kathleen.moriarty.ietf@gmail.com
Kopia: tram@ietf.org; Simon Perreault;
draft-ietf-tram-turn-server-discovery@ietf.org; The IESG;
tram-chairs@ietf.org
=C4mne: Re: [tram] Kathleen Moriarty's Discuss on
draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)

> -----Original Message-----
> From: kathleen.moriarty.ietf@gmail.com
> [mailto:kathleen.moriarty.ietf@gmail.com]
> Sent: Thursday, September 1, 2016 5:37 PM
> To: Tirumaleswar Reddy (tireddy) <tireddy@cisco.com>
> Cc: The IESG <iesg@ietf.org>;
draft-ietf-tram-turn-server-discovery@ietf.org;
> Simon Perreault <sperreault@jive.com>; tram-chairs@ietf.org; =
tram@ietf.org
> Subject: Re: Kathleen Moriarty's Discuss on =
draft-ietf-tram-turn-server-
> discovery-09: (with DISCUSS)
>=20
>=20
>=20
> Sent from my iPhone
>=20
> On Aug 31, 2016, at 3:02 AM, Tirumaleswar Reddy (tireddy)
> <tireddy@cisco.com> wrote:
>=20
> >> -----Original Message-----
> >> From: Kathleen Moriarty [mailto:Kathleen.Moriarty.ietf@gmail.com]
> >> Sent: Monday, August 29, 2016 7:20 PM
> >> To: The IESG <iesg@ietf.org>
> >> Cc: draft-ietf-tram-turn-server-discovery@ietf.org; Simon Perreault
> >> <sperreault@jive.com>; tram-chairs@ietf.org; sperreault@jive.com;
> >> tram@ietf.org
> >> Subject: Kathleen Moriarty's Discuss on
> >> draft-ietf-tram-turn-server-discovery-
> >> 09: (with DISCUSS)
> >>
> >> Kathleen Moriarty has entered the following ballot position for
> >> draft-ietf-tram-turn-server-discovery-09: Discuss
> >>
> >> When responding, please keep the subject line intact and reply to =
all
> >> email addresses included in the To and CC lines. (Feel free to cut
> >> this introductory paragraph, however.)
> >>
> >>
> >> Please refer to
> >> https://www.ietf.org/iesg/statement/discuss-criteria.html
> >> for more information about IESG DISCUSS and COMMENT positions.
> >>
> >>
> >> The document, along with other ballot positions, can be found here:
> >> =
https://datatracker.ietf.org/doc/draft-ietf-tram-turn-server-discover
> >> y/
> >>
> >>
> >>
> >> =
---------------------------------------------------------------------
> >> -
> >> DISCUSS:
> >> =
---------------------------------------------------------------------
> >> -
> >>
> >> This should be easy to resolve.  In reading the draft, it doesn't
> >> cover any mechanism for the TURN server to limit what clients can
> discover it.
> >> For the second and third method, it seems like there are possible
> >> ways to do this.  Could these be added to the security
> >> considerations?  You'd need to state that this isn't possible with
> >> the first method.  If there is a reason why it is always okay to
> >> discover a TURN server, please let me know why this is not =
appropriate
to
> add.  Thanks.
> >
> > I don't see a reason why TURN server discovery should be restricted =
only
to
> specific clients. Please explain the scenarios for imposing such
restrictions.
>=20
> Hello Tiru,
>=20
> Are there any cases where some domains or addresses should be =
restricted?

Yes.

> When you have open services, it's possible to attack them.  It could =
be
from a
> design or implementation problem that makes an exploit possible or it
might
> just be for network reconnaissance.  Is there something different =
about
TURN
> servers that makes this point moot.

Restricting access to use the TURN server seems more important than
discovering the TURN server; will add more details that TURN servers
deployed in DMZ must only process STUN requests from the trusted network =
and
not from the external network. Similarly TURN server in access network =
must
only process STUN requests only its subscribers. Access control can be
provided by access-control lists, firewalls and/or by user =
authentication to
the TURN server. We can also discuss other recommendations like
per-subscriber quota limit, ingress filtering.=20

Please share any other mechanisms you would like to use to discuss in =
the WG
and include in the draft.

-Tiru

Hi Tiru,

For the use case of a network provided TURN server paralleling a =
firewall or
default gateway (like RFC 7478 (Web Real-Time Communication Use Cases =
and
Requirements) 2.3.5.1), shouldn't both usage and discovery be restricted =
to
the local users?

The Anycast method has this "built-in", but when it comes to the methods
using DNS, isn't it the intention of the draft that the DNS should be =
local
only? I.e. network provided TURN servers SHOULD not be deployed in =
public
DNS, where we don't want to find local IP addresses like 192.168.1.1 =
over
and over again (or don't we care)? I think it at least should be =
recommended
(even if a MUST may not be required).

/Karl

>=20
> Thank you,
> Kathleen
> >
> > Cheers,
> > -Tiru
> >
> >

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


From nobody Wed Sep  7 18:39:22 2016
Return-Path: <kathleen.moriarty.ietf@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 CB91C12B40A; Wed,  7 Sep 2016 18:39:20 -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, FREEMAIL_FROM=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=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 HQ_VcLEr5nEy; Wed,  7 Sep 2016 18:39:19 -0700 (PDT)
Received: from mail-qt0-x22a.google.com (mail-qt0-x22a.google.com [IPv6:2607:f8b0:400d:c0d::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 C636212B405; Wed,  7 Sep 2016 18:39:18 -0700 (PDT)
Received: by mail-qt0-x22a.google.com with SMTP id p30so16525114qte.3; Wed, 07 Sep 2016 18:39:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ikxAcYBXt9KU0N/CaCnoZB2T5CvGMC8lHkXWMXJ5a4A=; b=qTX56luUOm5mFKVBbG2cDiHq0wQdDmb1VJyNYXMOqKXWEtb3owWPXCBA3m25TDxviZ wLbkJ+WcOrfWeDy6ur3PZcZUu28/vi3m5t7akgx6wDAwuZvd4Z6nh6rIYMydLRbLdGX+ ELhnxaOXn+mKeZ42C/6tXiX40n893ifd8gVMqEh/LLUel39OgQ2yYCJdXg+afX3t/dMx o2wFayxWpDobRaCVdTeMPRD622xV1pJwUoT3kQOpYrXcvijrSKSKSVrUGKFyBUzelCQB EX6rAXAgp0uHTg7CylmT1R0XvQtwgFRWSASD0JvhJL8nnABXKOIRXiu/sYlX5oyfPxY8 6uAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ikxAcYBXt9KU0N/CaCnoZB2T5CvGMC8lHkXWMXJ5a4A=; b=fdLmBwAgQA73cnJPfATS2gtaXGfO6QEPqWfku0DY5ycv/M6+kjp4elohlnTPcmlBxN uZWes23LluGHwUgmSDErv6+/ilmgNkfxpxp2hm0Sc/1uCUbQMGFFBqFd4qsGIX3xeTua 3RJxUB7PZtfSKh7a9a6UDvP9Kt3+C9wSbpAvaIWNTwVYuROi8AgpFG6xNsQR0pr5A6Gn gzTUYvMXq7s+/YyjGufd7Anusz4/lwz1QVW4tj11TSMlpPFzYktTrR1bwPETxaFCIepT /DqgHlUFG57h8caZd3iG8VwzzOHdseupiEquyK6BGOMHF+JszDRa5bptzRGHIfBaEGvR T21g==
X-Gm-Message-State: AE9vXwPH8ulJkIF3sKi3qo2w714vINqw/bEZcKP4Daqrq+0NKk6gGWO0/92mdZQA8VYkAQ==
X-Received: by 10.237.51.101 with SMTP id u92mr14003857qtd.2.1473298757963; Wed, 07 Sep 2016 18:39:17 -0700 (PDT)
Received: from [192.168.1.3] (209-6-124-204.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com. [209.6.124.204]) by smtp.gmail.com with ESMTPSA id m4sm22660433qkf.29.2016.09.07.18.39.16 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 07 Sep 2016 18:39:17 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: kathleen.moriarty.ietf@gmail.com
X-Mailer: iPhone Mail (13G35)
In-Reply-To: <a45b893264144f779883cb78319fba6a@XCH-RCD-017.cisco.com>
Date: Wed, 7 Sep 2016 21:39:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5D9A0F6D-DFEF-4C65-8EC6-219FB9A32C58@gmail.com>
References: <147247859789.14154.18257109792324801465.idtracker@ietfa.amsl.com> <d742e129f2714a0cabb722288bfeb1a6@XCH-RCD-017.cisco.com> <EC3E0CC4-79EE-4F5E-A59C-2BB78E13E4BB@gmail.com> <a45b893264144f779883cb78319fba6a@XCH-RCD-017.cisco.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/y_Rkm3U3a6mWsEAwAXKYlTSNjRo>
Cc: "tram@ietf.org" <tram@ietf.org>, Simon Perreault <sperreault@jive.com>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, The IESG <iesg@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>
Subject: Re: [tram] Kathleen Moriarty's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 08 Sep 2016 01:39:21 -0000

Hi Tiru,


Sent from my iPhone

On Sep 6, 2016, at 11:27 PM, Tirumaleswar Reddy (tireddy) <tireddy@cisco.com=
> wrote:

>> -----Original Message-----
>> From: kathleen.moriarty.ietf@gmail.com
>> [mailto:kathleen.moriarty.ietf@gmail.com]
>> Sent: Thursday, September 1, 2016 5:37 PM
>> To: Tirumaleswar Reddy (tireddy) <tireddy@cisco.com>
>> Cc: The IESG <iesg@ietf.org>; draft-ietf-tram-turn-server-discovery@ietf.=
org;
>> Simon Perreault <sperreault@jive.com>; tram-chairs@ietf.org; tram@ietf.or=
g
>> Subject: Re: Kathleen Moriarty's Discuss on draft-ietf-tram-turn-server-
>> discovery-09: (with DISCUSS)
>>=20
>>=20
>>=20
>> Sent from my iPhone
>>=20
>> On Aug 31, 2016, at 3:02 AM, Tirumaleswar Reddy (tireddy)
>> <tireddy@cisco.com> wrote:
>>=20
>>>> -----Original Message-----
>>>> From: Kathleen Moriarty [mailto:Kathleen.Moriarty.ietf@gmail.com]
>>>> Sent: Monday, August 29, 2016 7:20 PM
>>>> To: The IESG <iesg@ietf.org>
>>>> Cc: draft-ietf-tram-turn-server-discovery@ietf.org; Simon Perreault
>>>> <sperreault@jive.com>; tram-chairs@ietf.org; sperreault@jive.com;
>>>> tram@ietf.org
>>>> Subject: Kathleen Moriarty's Discuss on
>>>> draft-ietf-tram-turn-server-discovery-
>>>> 09: (with DISCUSS)
>>>>=20
>>>> Kathleen Moriarty has entered the following ballot position for
>>>> draft-ietf-tram-turn-server-discovery-09: Discuss
>>>>=20
>>>> When responding, please keep the subject line intact and reply to all
>>>> email addresses included in the To and CC lines. (Feel free to cut
>>>> this introductory paragraph, however.)
>>>>=20
>>>>=20
>>>> Please refer to
>>>> https://www.ietf.org/iesg/statement/discuss-criteria.html
>>>> for more information about IESG DISCUSS and COMMENT positions.
>>>>=20
>>>>=20
>>>> The document, along with other ballot positions, can be found here:
>>>> https://datatracker.ietf.org/doc/draft-ietf-tram-turn-server-discover
>>>> y/
>>>>=20
>>>>=20
>>>>=20
>>>> ---------------------------------------------------------------------
>>>> -
>>>> DISCUSS:
>>>> ---------------------------------------------------------------------
>>>> -
>>>>=20
>>>> This should be easy to resolve.  In reading the draft, it doesn't
>>>> cover any mechanism for the TURN server to limit what clients can
>> discover it.
>>>> For the second and third method, it seems like there are possible
>>>> ways to do this.  Could these be added to the security
>>>> considerations?  You'd need to state that this isn't possible with
>>>> the first method.  If there is a reason why it is always okay to
>>>> discover a TURN server, please let me know why this is not appropriate t=
o
>> add.  Thanks.
>>>=20
>>> I don't see a reason why TURN server discovery should be restricted only=
 to
>> specific clients. Please explain the scenarios for imposing such restrict=
ions.
>>=20
>> Hello Tiru,
>>=20
>> Are there any cases where some domains or addresses should be restricted?=

>=20
> Yes.
>=20
>> When you have open services, it's possible to attack them.  It could be f=
rom a
>> design or implementation problem that makes an exploit possible or it mig=
ht
>> just be for network reconnaissance.  Is there something different about T=
URN
>> servers that makes this point moot.
>=20
> Restricting access to use the TURN server seems more important than discov=
ering the TURN server; will add more details that TURN servers deployed in D=
MZ must only process STUN requests from the trusted network and not from the=
 external network. Similarly TURN server in access network must only process=
 STUN requests only its subscribers. Access control can be provided by acces=
s-control lists, firewalls and/or by user authentication to the TURN server.=
 We can also discuss other recommendations like per-subscriber quota limit, i=
ngress filtering.=20
>=20
> Please share any other mechanisms you would like to use to discuss in the W=
G and include in the draft.

That sounds good, thank you.  Since this draft is about discovery, the restr=
ictions you are going to add would also prevent reconnaissance, so you might=
 want to mention that as well.

If the other recommendations are in another draft, a punter to that would be=
 good.  If not, adding them might be helpful and you can point to this text i=
n the future.

Thank you,
Kathleen=20
>=20
> -Tiru
>=20
>>=20
>> Thank you,
>> Kathleen
>>>=20
>>> Cheers,
>>> -Tiru
>>>=20
>>>=20


From nobody Wed Sep  7 19:23:05 2016
Return-Path: <tireddy@cisco.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 9DCEE12B40A; Wed,  7 Sep 2016 19:22:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.029
X-Spam-Level: 
X-Spam-Status: No, score=-16.029 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 9B5cLXo_j2bH; Wed,  7 Sep 2016 19:22:57 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D10912B0AE; Wed,  7 Sep 2016 19:22:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5299; q=dns/txt; s=iport; t=1473301377; x=1474510977; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=1XdKW/Foxgn9TtQDrPmBhsMIzQoR9BjtPFWIiy2zQjw=; b=jE4A5cWYhfmYuqYEuMT0a1HJ0aMsW/f9Thmys/aLhad/vK7y7MD7Yyj9 YocXzyEFpG3gdr0pAzKmIYFYWIwicdm9mSZQCinY4PfILUn8o7uW+Znak Sp8cP7o/Ins1loOyX5OaMtRT8AwoIxFvcgNcUw6uycHnerxSvirgUYyzL E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BQAQBGytBX/4UNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBgy0BAQEBAR5XfAeNK55bjDaCAySFeAKBajgUAQIBAQEBAQEBXhwLhGEBAQE?= =?us-ascii?q?DATo/DAQCAQgRBAEBAR4JByERFAkIAgQOBQiIKAMPCA65Rg2CewEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBARcFhi+EToJDgU8LBgEDA0iFKgWILotehRg1AYYhhkCCVIF?= =?us-ascii?q?1hF6JD4ZzgVGEDIN6AR42gx+BNXABg28OF4EJfwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.30,298,1470700800"; d="scan'208";a="149422272"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Sep 2016 02:22:56 +0000
Received: from XCH-ALN-016.cisco.com (xch-aln-016.cisco.com [173.36.7.26]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id u882Muak007449 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 8 Sep 2016 02:22:56 GMT
Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-ALN-016.cisco.com (173.36.7.26) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 7 Sep 2016 21:22:55 -0500
Received: from xch-rcd-017.cisco.com ([173.37.102.27]) by XCH-RCD-017.cisco.com ([173.37.102.27]) with mapi id 15.00.1210.000; Wed, 7 Sep 2016 21:22:55 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: "kathleen.moriarty.ietf@gmail.com" <kathleen.moriarty.ietf@gmail.com>
Thread-Topic: Kathleen Moriarty's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
Thread-Index: AQHSAfw9GKziJUsFG0mb9R1x8tRHg6BipUYwgAI9UoCAAMJZUIAJjoYA//+vw7A=
Date: Thu, 8 Sep 2016 02:22:55 +0000
Message-ID: <2675d94d58264487b5d2a5ecb6c5f03e@XCH-RCD-017.cisco.com>
References: <147247859789.14154.18257109792324801465.idtracker@ietfa.amsl.com> <d742e129f2714a0cabb722288bfeb1a6@XCH-RCD-017.cisco.com> <EC3E0CC4-79EE-4F5E-A59C-2BB78E13E4BB@gmail.com> <a45b893264144f779883cb78319fba6a@XCH-RCD-017.cisco.com> <5D9A0F6D-DFEF-4C65-8EC6-219FB9A32C58@gmail.com>
In-Reply-To: <5D9A0F6D-DFEF-4C65-8EC6-219FB9A32C58@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.80.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/SRzwRJub7IlXq2DijO1ETCdNX-Q>
Cc: "tram@ietf.org" <tram@ietf.org>, Simon Perreault <sperreault@jive.com>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, The IESG <iesg@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>
Subject: Re: [tram] Kathleen Moriarty's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 08 Sep 2016 02:23:00 -0000

> -----Original Message-----
> From: kathleen.moriarty.ietf@gmail.com
> [mailto:kathleen.moriarty.ietf@gmail.com]
> Sent: Thursday, September 8, 2016 7:09 AM
> To: Tirumaleswar Reddy (tireddy) <tireddy@cisco.com>
> Cc: The IESG <iesg@ietf.org>; draft-ietf-tram-turn-server-discovery@ietf.=
org;
> Simon Perreault <sperreault@jive.com>; tram-chairs@ietf.org; tram@ietf.or=
g
> Subject: Re: Kathleen Moriarty's Discuss on draft-ietf-tram-turn-server-
> discovery-09: (with DISCUSS)
>=20
> Hi Tiru,
>=20
>=20
> Sent from my iPhone
>=20
> On Sep 6, 2016, at 11:27 PM, Tirumaleswar Reddy (tireddy)
> <tireddy@cisco.com> wrote:
>=20
> >> -----Original Message-----
> >> From: kathleen.moriarty.ietf@gmail.com
> >> [mailto:kathleen.moriarty.ietf@gmail.com]
> >> Sent: Thursday, September 1, 2016 5:37 PM
> >> To: Tirumaleswar Reddy (tireddy) <tireddy@cisco.com>
> >> Cc: The IESG <iesg@ietf.org>;
> >> draft-ietf-tram-turn-server-discovery@ietf.org;
> >> Simon Perreault <sperreault@jive.com>; tram-chairs@ietf.org;
> >> tram@ietf.org
> >> Subject: Re: Kathleen Moriarty's Discuss on
> >> draft-ietf-tram-turn-server-
> >> discovery-09: (with DISCUSS)
> >>
> >>
> >>
> >> Sent from my iPhone
> >>
> >> On Aug 31, 2016, at 3:02 AM, Tirumaleswar Reddy (tireddy)
> >> <tireddy@cisco.com> wrote:
> >>
> >>>> -----Original Message-----
> >>>> From: Kathleen Moriarty [mailto:Kathleen.Moriarty.ietf@gmail.com]
> >>>> Sent: Monday, August 29, 2016 7:20 PM
> >>>> To: The IESG <iesg@ietf.org>
> >>>> Cc: draft-ietf-tram-turn-server-discovery@ietf.org; Simon Perreault
> >>>> <sperreault@jive.com>; tram-chairs@ietf.org; sperreault@jive.com;
> >>>> tram@ietf.org
> >>>> Subject: Kathleen Moriarty's Discuss on
> >>>> draft-ietf-tram-turn-server-discovery-
> >>>> 09: (with DISCUSS)
> >>>>
> >>>> Kathleen Moriarty has entered the following ballot position for
> >>>> draft-ietf-tram-turn-server-discovery-09: Discuss
> >>>>
> >>>> When responding, please keep the subject line intact and reply to
> >>>> all email addresses included in the To and CC lines. (Feel free to
> >>>> cut this introductory paragraph, however.)
> >>>>
> >>>>
> >>>> Please refer to
> >>>> https://www.ietf.org/iesg/statement/discuss-criteria.html
> >>>> for more information about IESG DISCUSS and COMMENT positions.
> >>>>
> >>>>
> >>>> The document, along with other ballot positions, can be found here:
> >>>> https://datatracker.ietf.org/doc/draft-ietf-tram-turn-server-discov
> >>>> er
> >>>> y/
> >>>>
> >>>>
> >>>>
> >>>> -------------------------------------------------------------------
> >>>> --
> >>>> -
> >>>> DISCUSS:
> >>>> -------------------------------------------------------------------
> >>>> --
> >>>> -
> >>>>
> >>>> This should be easy to resolve.  In reading the draft, it doesn't
> >>>> cover any mechanism for the TURN server to limit what clients can
> >> discover it.
> >>>> For the second and third method, it seems like there are possible
> >>>> ways to do this.  Could these be added to the security
> >>>> considerations?  You'd need to state that this isn't possible with
> >>>> the first method.  If there is a reason why it is always okay to
> >>>> discover a TURN server, please let me know why this is not
> >>>> appropriate to
> >> add.  Thanks.
> >>>
> >>> I don't see a reason why TURN server discovery should be restricted
> >>> only to
> >> specific clients. Please explain the scenarios for imposing such restr=
ictions.
> >>
> >> Hello Tiru,
> >>
> >> Are there any cases where some domains or addresses should be
> restricted?
> >
> > Yes.
> >
> >> When you have open services, it's possible to attack them.  It could
> >> be from a design or implementation problem that makes an exploit
> >> possible or it might just be for network reconnaissance.  Is there
> >> something different about TURN servers that makes this point moot.
> >
> > Restricting access to use the TURN server seems more important than
> discovering the TURN server; will add more details that TURN servers
> deployed in DMZ must only process STUN requests from the trusted network
> and not from the external network. Similarly TURN server in access networ=
k
> must only process STUN requests only its subscribers. Access control can =
be
> provided by access-control lists, firewalls and/or by user authentication=
 to the
> TURN server. We can also discuss other recommendations like per-subscribe=
r
> quota limit, ingress filtering.
> >
> > Please share any other mechanisms you would like to use to discuss in t=
he
> WG and include in the draft.
>=20
> That sounds good, thank you.  Since this draft is about discovery, the
> restrictions you are going to add would also prevent reconnaissance, so y=
ou
> might want to mention that as well.

Sure.

>=20
> If the other recommendations are in another draft, a punter to that would=
 be
> good.  If not, adding them might be helpful and you can point to this tex=
t in the
> future.

Other TURN drafts are not discussing the above restrictions, we will update=
 the draft.

-Tiru

>=20
> Thank you,
> Kathleen
> >
> > -Tiru
> >
> >>
> >> Thank you,
> >> Kathleen
> >>>
> >>> Cheers,
> >>> -Tiru
> >>>
> >>>


From nobody Wed Sep  7 19:50:24 2016
Return-Path: <tireddy@cisco.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 0280A12B40A; Wed,  7 Sep 2016 19:50:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.028
X-Spam-Level: 
X-Spam-Status: No, score=-16.028 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 S3e9ltbGJD0n; Wed,  7 Sep 2016 19:50:17 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEE2212B3FD; Wed,  7 Sep 2016 19:50:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16732; q=dns/txt; s=iport; t=1473303016; x=1474512616; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=xlFBn+d1+vUvTc1fDNdbxugOPWTIHRwmabynSqB8zkI=; b=Aa2ZR3JYauzsst66kme72PaFFzkPDRejZLI4pC0XAJ6p0YSFb6hcPXNa cdqnabHsk58irtkoB88QbtSGz6t7RKWo4UrlVoKZ9NP1z7EHTeS2Ec8eP gJAfG/Nppd8LcWknfqcXdoKbSJB518c0Gbd2cl29FBkAL2PDVEhs2Qv+Z 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CMAQB70dBX/4gNJK1aAxYDAQEBAQEBA?= =?us-ascii?q?QEBAQGCejMBAQEBAR5XfAeNK6YEhQ2CAyCFfAKBaDgUAQIBAQEBAQEBXieEYQE?= =?us-ascii?q?BAQQtTBACAQgOAwQBASgHMhQJCAIEAQ0FCIhCDrxPAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBHIYvhE6EMDEVEYUVBYg7hySELYVNAY81gXWEXokPhnOFXYN6AR42gjQ?= =?us-ascii?q?4G4FNcINvB4EofwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.30,298,1470700800";  d="scan'208,217";a="320855218"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Sep 2016 02:50:15 +0000
Received: from XCH-RCD-017.cisco.com (xch-rcd-017.cisco.com [173.37.102.27]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u882oFo0007686 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 8 Sep 2016 02:50:15 GMT
Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-RCD-017.cisco.com (173.37.102.27) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 7 Sep 2016 21:50:14 -0500
Received: from xch-rcd-017.cisco.com ([173.37.102.27]) by XCH-RCD-017.cisco.com ([173.37.102.27]) with mapi id 15.00.1210.000; Wed, 7 Sep 2016 21:50:14 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>
Thread-Topic: GenART post-telechat comment on draft-ietf-tram-turn-mobility-08
Thread-Index: AQHSCFiLm4+HgrE2lU6LKYpWnDFIuqBuerCAgABrFkA=
Date: Thu, 8 Sep 2016 02:50:14 +0000
Message-ID: <abf54eff0f4c4d28b45db8e185e5e5c2@XCH-RCD-017.cisco.com>
References: <6ECD9A3A-0D63-421B-953D-A516D773CCBA@qti.qualcomm.com> <E87B771635882B4BA20096B589152EF643E961F1@eusaamb107.ericsson.se> <092F2B7C-4B03-4956-9C0E-1C5983D2AF72@qti.qualcomm.com>
In-Reply-To: <092F2B7C-4B03-4956-9C0E-1C5983D2AF72@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.80.46]
Content-Type: multipart/alternative; boundary="_000_abf54eff0f4c4d28b45db8e185e5e5c2XCHRCD017ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/atAHmTIH5Mrvo-5GXazBlcrxVC0>
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-tram-turn-mobility.all@ietf.org" <draft-ietf-tram-turn-mobility.all@ietf.org>, IESG <iesg@ietf.org>, "tram@ietf.org" <tram@ietf.org>
Subject: Re: [tram] GenART post-telechat comment on draft-ietf-tram-turn-mobility-08
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 08 Sep 2016 02:50:19 -0000

--_000_abf54eff0f4c4d28b45db8e185e5e5c2XCHRCD017ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Please see inline
From: Pete Resnick [mailto:presnick@qti.qualcomm.com]
Sent: Wednesday, September 7, 2016 8:53 PM
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Cc: IESG <iesg@ietf.org>; General Area Review Team <gen-art@ietf.org>; draf=
t-ietf-tram-turn-mobility.all@ietf.org; tram@ietf.org
Subject: Re: GenART post-telechat comment on draft-ietf-tram-turn-mobility-=
08


[Trimming down a bit]

On 6 Sep 2016, at 22:57, Suresh Krishnan wrote:
OLD: If a client wants to refresh an existing allocation and update its
time-to-expiry or delete an existing allocation, it will send a Refresh
Request as described in Section 7.1 of [RFC5766]
NEW:
If a client wants to refresh an existing allocation and update its
time-to-expiry or delete an existing allocation, it MUST send a Refresh
Request as described in Section 7.1 of [RFC5766] and MUST NOT include a
MOBILITY-TICKET attribute.
I will try to explain my line of reasoning. Let me know where you disagree.
If the client includes a MOBILTY-TICKET attribute in the refresh method, th=
e
refresh will fail. So, the MUST NOT is aimed at preventing the client from
sending a useless packet that will be rejected anyway.

"Useless" seems not a good reason for a "MUST NOT". Perhaps Tiru's explanat=
ion of "will cause an extra retransmission" is a better reason. But as I sa=
id, this isn't one that I will complain too vociferously about: What this s=
ays is "don't include the attribute; it will be rejected and you'll have to=
 retransmit"; if you want a "MUST NOT" for that, so be it. But:
The MUST stresses that
the original Refresh procedure from RFC5766 needs to be used instead of the
Refresh procedure with the MOBILITY-TICKET described in this one.

Ah! If that's was meant, that's not what was said. It sounds like you're sa=
ying that the client can't refresh a request by simply sending an allocate =
request with the old MOBILITY-TICKET. And then I get a bit confused about t=
he MUST NOT: The next sentence after this bit says:

If the client wants to retain
the existing allocation in case of IP change, it will include the
MOBILITY-TICKET attribute received in the Allocate Success response.

The previous sentence says that you MUST NOT include the attribute. This se=
ntence says that you do include it. I suspect that what was intended was, "=
If you just want to refresh to retain the existing allocation in case of an=
 IP change, you can send an allocate request including the old MOBILITY-TIC=
KET attribute. If you need to update time-to-expiry or delete the allocatio=
n, then you can't just send a new allocate request with the attribute; that=
 will get rejected. You instead have to use the refresh request in 5766." D=
o I have that right? If so, the paragraph could use a rewrite; it's not the=
 MUST and the MUST NOT that are the problem.

[TR] I propose the following text to avoid the confusion:
   If a client wants to refresh an existing allocation and update its
   time-to-expiry or delete an existing allocation in case of no IP address=
 change, it will send a
   Refresh Request as described in Section 7.1 of [RFC5766] and MUST NOT
   include a MOBILITY-TICKET attribute.  If the client wants to retain
   the existing allocation in case of IP address change, it will include th=
e
   MOBILITY-TICKET attribute received in the Allocate Success response
   in the Refresh Request.

Cheers,
-Tiru

Anyway, I
am not wedded to keeping the MUST as long as the MUST NOT prevents the
sending of a packet that is certain to be rejected.

Ack. See above.

pr
--
Pete Resnick http://www.qualcomm.com/~presnick/<http://www.qualcomm.com/%7E=
presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478

--_000_abf54eff0f4c4d28b45db8e185e5e5c2XCHRCD017ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-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=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	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
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Please see inline
<o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> Pete Resnick [mailto:presnick@=
qti.qualcomm.com]
<br>
<b>Sent:</b> Wednesday, September 7, 2016 8:53 PM<br>
<b>To:</b> Suresh Krishnan &lt;suresh.krishnan@ericsson.com&gt;<br>
<b>Cc:</b> IESG &lt;iesg@ietf.org&gt;; General Area Review Team &lt;gen-art=
@ietf.org&gt;; draft-ietf-tram-turn-mobility.all@ietf.org; tram@ietf.org<br=
>
<b>Subject:</b> Re: GenART post-telechat comment on draft-ietf-tram-turn-mo=
bility-08<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">[Trimming down =
a bit]<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">On 6 Sep 2016, =
at 22:57, Suresh Krishnan wrote:<o:p></o:p></span></p>
</div>
<div>
<blockquote style=3D"border:none;border-left:solid #777777 1.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:0in;margin-right:0in;margin-bottom:3.75pt">
<blockquote style=3D"border:none;border-left:solid #999999 1.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:0in;margin-right:0in;margin-bottom:3.75pt">
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#999999">OLD: If a client wants to refresh an existing allocation=
 and update its
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#999999">time-to-expiry or delete an existing allocation, it will=
 send a Refresh
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#999999">Request as described in Section 7.1 of [RFC5766]
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#999999">NEW:
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#999999">If a client wants to refresh an existing allocation and =
update its
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#999999">time-to-expiry or delete an existing allocation, it MUST=
 send a Refresh
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#999999">Request as described in Section 7.1 of [RFC5766] and MUS=
T NOT include a
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#999999">MOBILITY-TICKET attribute.
<o:p></o:p></span></p>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#777777">I will try to explain my line of reasoning. Let me know =
where you disagree.
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#777777">If the client includes a MOBILTY-TICKET attribute in the=
 refresh method, the
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#777777">refresh will fail. So, the MUST NOT is aimed at preventi=
ng the client from
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#777777">sending a useless packet that will be rejected anyway.
<o:p></o:p></span></p>
</div>
</blockquote>
</div>
<div>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">&quot;Useless&q=
uot; seems not a good reason for a &quot;MUST NOT&quot;. Perhaps Tiru's exp=
lanation of &quot;will cause an extra retransmission&quot; is a better reas=
on. But as I said, this isn't one that I will complain too vociferously abo=
ut:
 What this says is &quot;don't include the attribute; it will be rejected a=
nd you'll have to retransmit&quot;; if you want a &quot;MUST NOT&quot; for =
that, so be it. But:<o:p></o:p></span></p>
</div>
<div>
<blockquote style=3D"border:none;border-left:solid #777777 1.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:0in;margin-right:0in;margin-bottom:3.75pt">
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#777777">The MUST stresses that
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#777777">the original Refresh procedure from RFC5766 needs to be =
used instead of the
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#777777">Refresh procedure with the MOBILITY-TICKET described in =
this one.
<o:p></o:p></span></p>
</div>
</blockquote>
</div>
<div>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">Ah! If that's w=
as meant, that's not what was said. It sounds like you're saying that the c=
lient
<em><span style=3D"font-family:&quot;Arial&quot;,sans-serif">can't</span></=
em> refresh a request by simply sending an allocate request with the old MO=
BILITY-TICKET. And then I get a bit confused about the MUST NOT: The next s=
entence after this bit says:<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">If the client w=
ants to retain<br>
the existing allocation in case of IP change, it will include the<br>
MOBILITY-TICKET attribute received in the Allocate Success response.<o:p></=
o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">The previous se=
ntence says that you MUST NOT include the attribute. This sentence says tha=
t you do include it. I suspect that what was intended was, &quot;If you
<em><span style=3D"font-family:&quot;Arial&quot;,sans-serif">just</span></e=
m> want to refresh to retain the existing allocation in case of an IP chang=
e, you can send an allocate request including the old MOBILITY-TICKET attri=
bute. If you need to update time-to-expiry or
 delete the allocation, then you <em><span style=3D"font-family:&quot;Arial=
&quot;,sans-serif">can't</span></em> just send a new allocate request with =
the attribute; that will get rejected. You instead
<em><span style=3D"font-family:&quot;Arial&quot;,sans-serif">have to</span>=
</em> use the refresh request in 5766.&quot; Do I have that right? If so, t=
he paragraph could use a rewrite; it's not the MUST and the MUST NOT that a=
re the problem.<o:p></o:p></span></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-ser=
if;color:#1F497D">[TR] I propose the following text to avoid the confusion:=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">&nbsp;&nbsp; If a client wants to ref=
resh an existing allocation and update its<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">&nbsp;&nbsp; time-to-expiry or delete=
 an existing allocation in case of no IP address change, it will send a<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">&nbsp;&nbsp; Refresh Request as descr=
ibed in Section 7.1 of [RFC5766] and MUST NOT<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">&nbsp;&nbsp; include a MOBILITY-TICKE=
T attribute.&nbsp; If the client wants to retain<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">&nbsp;&nbsp; the existing allocation =
in case of IP address change, it will include the<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">&nbsp;&nbsp; MOBILITY-TICKET attribut=
e received in the Allocate Success response<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">&nbsp;&nbsp; in the Refresh Request.<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">-Tiru<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<blockquote style=3D"border:none;border-left:solid #777777 1.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:0in;margin-right:0in;margin-bottom:3.75pt">
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#777777">Anyway, I
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#777777">am not wedded to keeping the MUST as long as the MUST NO=
T prevents the
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#777777">sending of a packet that is certain to be rejected.
<o:p></o:p></span></p>
</div>
</blockquote>
</div>
<div>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">Ack. See above.=
<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">pr<br>
-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/"><span style=
=3D"color:#3983C4">http://www.qualcomm.com/~presnick/</span></a><br>
Qualcomm Technologies, Inc. - &#43;1 (858)651-4478<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_abf54eff0f4c4d28b45db8e185e5e5c2XCHRCD017ciscocom_--


From nobody Wed Sep  7 20:22:50 2016
Return-Path: <praspati@cisco.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 8A1F912B41A; Wed,  7 Sep 2016 20:22:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.03
X-Spam-Level: 
X-Spam-Status: No, score=-16.03 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_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 GbBdBUltRXOo; Wed,  7 Sep 2016 20:22:40 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C5AA12B415; Wed,  7 Sep 2016 20:22:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5914; q=dns/txt; s=iport; t=1473304960; x=1474514560; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=5Z8xIaBTvBn5XW5ibChxVvXLhVpOBUgCkjz6hjsKRlI=; b=EYrNW6ZlL+eRMBx28p0B64NaB5VUlpjDje2quSjvksPQFhpYS0ma2ZuN eAiR1TGZ1CiMo0VVVm57ACRw+4TMIpikFXzkVFywsMocDS/tA1sd4Tvlm b2Ru+BF+5VyFuk0r/Yyw6I/2RjccwiKpUgckR+8o9+D/Ii7ajQgn0Csqi 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BLAQBC2NBX/4oNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBgy0BAQEBAR5XfAeNK6kCgg+CAySFeAKBYzgUAQIBAQEBAQEBXieEYgEBAwF?= =?us-ascii?q?5BQsCAQhGMiUCBAENBYhCCA68RQEBAQEBAQEBAQEBAQEBAQEBAQEBARcFhi+ET?= =?us-ascii?q?oQSCwYBAwNIhSoFiC6FeTqFK4VNAYYhiRuBboRegzWFWoZziVcBHjaCcRYYgTV?= =?us-ascii?q?wAYNvDheBCX8BAQE?=
X-IronPort-AV: E=Sophos;i="5.30,298,1470700800"; d="scan'208";a="320899233"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Sep 2016 03:22:39 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u883MduA027895 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 8 Sep 2016 03:22:39 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 7 Sep 2016 23:22:38 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Wed, 7 Sep 2016 23:22:38 -0400
From: "Prashanth Patil (praspati)" <praspati@cisco.com>
To: Ben Campbell <ben@nostrum.com>, The IESG <iesg@ietf.org>
Thread-Topic: Ben Campbell's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS and COMMENT)
Thread-Index: AQHSCYA/0tuOUJIb3kaZpKjLJKq6fw==
Date: Thu, 8 Sep 2016 03:22:38 +0000
Message-ID: <D3EDF13E.13092C%praspati@cisco.com>
References: <147269306853.31916.11958166980739260630.idtracker@ietfa.amsl.com>
In-Reply-To: <147269306853.31916.11958166980739260630.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.4.160422
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.77.215]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <3BF5BA01ADF45C4EA32C141E600A0D46@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/W_L2ehe73GLxb4oKms2emq3FhHY>
Cc: Simon Perreault <sperreault@jive.com>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, "tram@ietf.org" <tram@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>
Subject: Re: [tram] Ben Campbell's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS and COMMENT)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 08 Sep 2016 03:22:42 -0000

Hi Ben,
Apologies for the delay. Please see inline..


On 8/31/16, 6:24 PM, "Ben Campbell" <ben@nostrum.com> wrote:

>Ben Campbell has entered the following ballot position for
>draft-ietf-tram-turn-server-discovery-09: Discuss
>
>When responding, please keep the subject line intact and reply to all
>email addresses included in the To and CC lines. (Feel free to cut this
>introductory paragraph, however.)
>
>
>Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>for more information about IESG DISCUSS and COMMENT positions.
>
>
>The document, along with other ballot positions, can be found here:
>https://datatracker.ietf.org/doc/draft-ietf-tram-turn-server-discovery/
>
>
>
>----------------------------------------------------------------------
>DISCUSS:
>----------------------------------------------------------------------
>
>-9, first paragraph says:
>
> "Use of Session Traversal Utilities for NAT (STUN) [RFC5389]
>   authentication is OPTIONAL for TURN servers provided by the local
>   network or by the access network.  A network provided TURN server MAY
>   be configured to accept Allocation requests without STUN
>   authentication, and a TURN client MAY be configured to accept
>   Allocation success responses without STUN authentication from a
>   network provided TURN server. "
>
>This seems to relax the MUST level requirement in RFC 5766 that says TURN
>MUST use STUN long-term credential authentication, or use some other
>equally strong mechanism. From a purely process perpective, this would
>either require an update to 5766, or it would require an argument that
>the local/access network is somehow equally protected. I think the latter
>would only be true if the access network has some sort of protection
>beyond just being the access network (e.g. a vpn, ipsec, or physical
>isolation.)  I don't recall seeing text that suggested any of those.

Tiru and Kathleen have discussed this in another thread. We intend to add
text around the following:

"will add more details that TURN servers deployed in DMZ must only process
STUN requests from a trusted network and not from external networks.
Similarly TURN servers in access networks must only process STUN requests
from its subscribers. Access control can be provided by access-control
lists, firewalls and/or by user authentication to the TURN server. We can
also discuss other recommendations like per-subscriber quota limit,
ingress filtering.=B2


Would this address your concern?

>
>But in any case, I think relaxing that requirement needs some discussion
>about how the server or client can be sure that all communication is in
>fact constrained to the local network.
>
>
>----------------------------------------------------------------------
>COMMENT:
>----------------------------------------------------------------------
>
>Substantive:
>
>- general: I agree with the DISCUSS positions from Terry, Alexey, and
>Kathleen.
>
>-3, paragraph 1: Are the MUST and MAY in this paragraph _new_
>requirements, or just statements of fact about previously existing
>requirements? If the latter, they should not use 2119 keywords.

These are new requirements.

>=20
>
>-4.1.2, first paragraph: It would be helpful to have a discussion about
>clients that may support multiple users, potentially with different
>domains, or for a single user to use different domains for different
>services.

Sure. Would it suffice if we included the following text:

"A client may support multiple users, potentially with different
   domains, or for a single user to use different domains for different
   services.  The means to choose and extract the desired domain name may
be
   different based on the type of identifier, service being used etc
   which are outside the scope of this document."


>
>-4.2, general: Do I correctly understand that most of this section
>describes the results of applying RFC 5928 procedures to the extracted
>domain name?

Yes, the section does exactly that.

> If so, is it not enough reference 5928 and leave it at that?

Sure. We can certainly remove the example.

>
>-4.2, last paragraph, last sentence: Is this requirement new to this
>draft, or something from 5928? If the latter, please use descriptive
>language.

It is not explicitly stated in 5928 but yes, it should be descriptive.

>
>-9, paragraph 5: "Any discovered TURN server outside the criteria is
>considered untrusted and is not used for privacy sensitive
>communication."
>
>It seems like this needs stronger guidance, maybe even "MUST NOT be
>used..."

Sure.=20

>
>- Informational References:
>I-D.ietf-rtcweb-return and RFC 6125 are cited as part of normative
>requirements, which makes them by definition need to be normative
>references. I-D.ietf-tram-turn-mobility, RFC6024, and RFC7250 are
>borderline; I think one could make an argument that one needs to read
>them to fully understand this draft.

We'll update the draft to cite these as non-normative.

>
>Editorial:
>
>-3, last paragraph: "MAY optionally" is redundant.

Fixed.

>
>-5.1, first paragraph, first sentence: I got lost in the nested =B3or=B2s.
>Please consider breaking this up into a few simpler sentences.

Fixed.

>
>- Figure 1: Why merge the query and reply for the A/AAAA query but not
>the other queries?

There was another comment that suggested that we refer to RFC 6762 and RFC
6763. We=B9ll end up removing the figure then.


>
>-6, first paragraph, last sentence: I'm not sure what that sentence
>means.

It was meant to indicate that a client could choose to send out every
*new* TURN request on the anycast address to discover the most optimal
unicast address for each request. We could reword the sentence to make the
intent more obvious.

-Prashanth

>
>


From nobody Wed Sep  7 20:27:11 2016
Return-Path: <praspati@cisco.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 0535712B41B; Wed,  7 Sep 2016 20:27:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.029
X-Spam-Level: 
X-Spam-Status: No, score=-16.029 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 3h9uBMwJhvvz; Wed,  7 Sep 2016 20:27:08 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FB2212B416; Wed,  7 Sep 2016 20:27:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3460; q=dns/txt; s=iport; t=1473305228; x=1474514828; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ryoquKjjNnsdzVenjWinPjAIA+v0TKkFCa0zdZ+eYv8=; b=l2tnadue9KoDOxl9r32hdGAbtTi8V6TfgHVqTlSsLeQP810X1LLwTXSe OKqc18ul1GN1uiTaN9wfG7Wav1NqgL5I3yWKWEylFgJUWqC+HArVPgmm4 wbohNn7mFIiEtKomF++Zb/4XLADMLCHLmAhl3zslhF6JCQ6Mc1v5Gf29z s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BLAQCf2dBX/5BdJa1TChkBAQEBAQEBA?= =?us-ascii?q?QEBAYMtAQEBAQEeV3wHjSupAoIPggMkhXgCgWM4FAECAQEBAQEBAV4nhGIBAQQ?= =?us-ascii?q?6PxACAQgYHhAyJQIEAQ0FiEoOvEYBAQEBAQEBAQEBAQEBAQEBAQEBAQEXBYYvh?= =?us-ascii?q?E6EEgYLAQZCBoUqBYguhXmLMgGGIYkbgW6EXokPhnOFXYN6AR42gmwbGIE1cAG?= =?us-ascii?q?DfYEgfwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.30,298,1470700800"; d="scan'208";a="146739783"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Sep 2016 03:27:07 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id u883R6ll001703 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 8 Sep 2016 03:27:07 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 7 Sep 2016 23:27:05 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Wed, 7 Sep 2016 23:27:05 -0400
From: "Prashanth Patil (praspati)" <praspati@cisco.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, The IESG <iesg@ietf.org>
Thread-Topic: Suresh Krishnan's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
Thread-Index: AQHSBAfnnle9TS+moUifmMZPWr6O+aBux3uA
Date: Thu, 8 Sep 2016 03:27:05 +0000
Message-ID: <D3F627AD.13251F%praspati@cisco.com>
References: <147270350795.31961.8306227467315681365.idtracker@ietfa.amsl.com> <D3EDDAE4.130787%praspati@cisco.com> <E87B771635882B4BA20096B589152EF643E96358@eusaamb107.ericsson.se>
In-Reply-To: <E87B771635882B4BA20096B589152EF643E96358@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.4.160422
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.77.215]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C061D341873FA743B4F1D0B1A8113D2B@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/cMP5FHqAGdq2z9K38SeU-RsE0wU>
Cc: Simon Perreault <sperreault@jive.com>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, "tram@ietf.org" <tram@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>
Subject: Re: [tram] Suresh Krishnan's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 08 Sep 2016 03:27:10 -0000

Hi Suresh,

On 9/6/16, 9:22 PM, "Suresh Krishnan" <suresh.krishnan@ericsson.com> wrote:

>Hi Prashanth,
>
>On 09/02/2016 05:54 PM, Prashanth Patil (praspati) wrote:
>> Hi Suresh,
>> Apologies for the delay, just back from holiday. Please see inline..
>>
>> On 8/31/16, 9:18 PM, "Suresh Krishnan" <suresh.krishnan@ericsson.com>
>> wrote:
>>
>>> Suresh Krishnan has entered the following ballot position for
>>> draft-ietf-tram-turn-server-discovery-09: Discuss
>>>
>>> When responding, please keep the subject line intact and reply to all
>>> email addresses included in the To and CC lines. (Feel free to cut this
>>> introductory paragraph, however.)
>>>
>>>
>>> Please refer to
>>>https://www.ietf.org/iesg/statement/discuss-criteria.html
>>> for more information about IESG DISCUSS and COMMENT positions.
>>>
>>>
>>> The document, along with other ballot positions, can be found here:
>>> https://datatracker.ietf.org/doc/draft-ietf-tram-turn-server-discovery/
>>>
>>>
>>>
>>> ----------------------------------------------------------------------
>>> DISCUSS:
>>> ----------------------------------------------------------------------
>>>
>>> * Section 4.1.1.
>>>
>>> The DHCP procedure is underspecified. I think this can be easily fixed
>>> but it requires some work.
>>>
>>> Please describe what sort of messages you would be using. i.e. are you
>>> going for a stateful exchange to piggy pack with other address and
>>>config
>>> information or are you going for a stateless Information-request based
>>> exchange(Most likely). Is there an ORO? If so, what options are
>>>requested
>>> in the ORO? Are there multiple request-response round trips as implied
>>>by
>>> the text?
>>
>> Does following text address your concerns?
>>
>> ..
>>    DHCP can be used to determine the domain name related to an
>>    interface's point of network attachment.  Network operators may
>>    provide the domain name to be used for service discovery within an
>>    access network using DHCP.  Sections 3.2 and 3.3 of [RFC5986] define
>>    DHCP IPv4 and IPv6 access network domain name options,
>>    OPTION_V4_ACCESS_DOMAIN and OPTION_V6_ACCESS_DOMAIN respectively, to
>>    identify a domain name that is suitable for service discovery within
>>    the access network.
>>
>>    For IPv4, the discovery procedure MUST request for an access network
>>    domain name option in a Parameter Request List option, as described
>>    in [RFC2131].  [RFC2132] defines the DHCP IPv4 domain name option;
>>    while this option is less suitable, a client MAY request for it if
>>    the access network domain name defined in [RFC5986] is not available.
>>
>>    For IPv6, the discovery procedure MUST request for an access network
>>    domain name option in an Options Request Option (ORO), as described
>>    in [RFC3315].
>>
>>    If neither option can be retrieved the procedure fails for this
>>    interface.  If a result can be retrieved it will be used as input
>>    for S-NAPTR resolution.
>
>Thank you. That certainly addresses one part of my DISCUSS but it still
>needs=20
>additional text on the DHCPv6 side to specify which message exchange will
>be=20
>used.=20

Sorry, missed that one.

>Did you intend to use the stateful exchange or the stateless exchange?

We intend to use stateless. Will update the draft accordingly.

Thanks,
Prashanth

>
>Regards
>Suresh
>


From nobody Thu Sep  8 13:48:33 2016
Return-Path: <ben@nostrum.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 86CD312B24C; Thu,  8 Sep 2016 13:48:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.408
X-Spam-Level: 
X-Spam-Status: No, score=-3.408 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.508] 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 O2rdaBSFOwkz; Thu,  8 Sep 2016 13:48:24 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 32F8A12B249; Thu,  8 Sep 2016 13:48:24 -0700 (PDT)
Received: from [10.0.1.21] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u88KmGwa045703 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 8 Sep 2016 15:48:17 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.21]
From: "Ben Campbell" <ben@nostrum.com>
To: "Prashanth Patil" <praspati@cisco.com>
Date: Thu, 08 Sep 2016 15:48:16 -0500
Message-ID: <362B7B05-81DA-49D7-8452-9BA21F991D00@nostrum.com>
In-Reply-To: <D3EDF13E.13092C%praspati@cisco.com>
References: <147269306853.31916.11958166980739260630.idtracker@ietfa.amsl.com> <D3EDF13E.13092C%praspati@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.5r5260)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/WAlBsxEa8EjjTUGg9-fqD1H-L2o>
Cc: "tram@ietf.org" <tram@ietf.org>, Simon Perreault <sperreault@jive.com>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, The IESG <iesg@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>
Subject: Re: [tram] Ben Campbell's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS and COMMENT)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 08 Sep 2016 20:48:26 -0000

Hi, thanks for the response. Some more comments inline (I removed 
sections that do not seem to need further discussion.).

Thanks!

Ben.

On 7 Sep 2016, at 22:22, Prashanth Patil (praspati) wrote:

> Hi Ben,
> Apologies for the delay. Please see inline..
>
> On 8/31/16, 6:24 PM, "Ben Campbell" <ben@nostrum.com> wrote:
>

[...]

>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>> -9, first paragraph says:
>>
>> "Use of Session Traversal Utilities for NAT (STUN) [RFC5389]
>>   authentication is OPTIONAL for TURN servers provided by the local
>>   network or by the access network.  A network provided TURN server 
>> MAY
>>   be configured to accept Allocation requests without STUN
>>   authentication, and a TURN client MAY be configured to accept
>>   Allocation success responses without STUN authentication from a
>>   network provided TURN server. "
>>
>> This seems to relax the MUST level requirement in RFC 5766 that says 
>> TURN
>> MUST use STUN long-term credential authentication, or use some other
>> equally strong mechanism. From a purely process perpective, this 
>> would
>> either require an update to 5766, or it would require an argument 
>> that
>> the local/access network is somehow equally protected. I think the 
>> latter
>> would only be true if the access network has some sort of protection
>> beyond just being the access network (e.g. a vpn, ipsec, or physical
>> isolation.)  I don't recall seeing text that suggested any of those.
>
> Tiru and Kathleen have discussed this in another thread. We intend to 
> add
> text around the following:
>
> "will add more details that TURN servers deployed in DMZ must only 
> process
> STUN requests from a trusted network and not from external networks.
> Similarly TURN servers in access networks must only process STUN 
> requests
> from its subscribers. Access control can be provided by access-control
> lists, firewalls and/or by user authentication to the TURN server. We 
> can
> also discuss other recommendations like per-subscriber quota limit,
> ingress filtering.²
>
> Would this address your concern?

It helps, but if I understand the intend correctly, it doesn't entirely 
address my concern.

This draft seems to relax the "MUST" level requirement to use stun 
authentication (or something equally strong) to an effective "MAY", 
without any real explanation of why, and without really exploring the 
security implications. Do you assume that a TURN server used in this 
context is using "something equally strong"? A number of the security 
considerations in RFC 5766 are mitigated by the assumption of stun 
authentication. How are they impacted by this relaxation? Does the lack 
of authentication lead to a risk of allocation-hijacking? (especially if 
combined with turn mobility?)

So I guess I would like to see some text that explains why this change 
is made, and why it's okay, and warning about related risks.

Finally, I still think this sort of normative change warrants an 
"UPDATES RFC 5766" label.


>
>>
>> But in any case, I think relaxing that requirement needs some 
>> discussion
>> about how the server or client can be sure that all communication is 
>> in
>> fact constrained to the local network.
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> Substantive:
>>
>> - general: I agree with the DISCUSS positions from Terry, Alexey, and
>> Kathleen.
>>
>> -3, paragraph 1: Are the MUST and MAY in this paragraph _new_
>> requirements, or just statements of fact about previously existing
>> requirements? If the latter, they should not use 2119 keywords.
>
> These are new requirements.

I find that confusing, because it seems like the paragraph is describing 
the state of affairs that this draft seeks to improve. Also, the "For 
example," in front of a sentence with a 2119 keyword is confusing if the 
purpose is to define a new requirement.

>
>>
>>
>> -4.1.2, first paragraph: It would be helpful to have a discussion 
>> about
>> clients that may support multiple users, potentially with different
>> domains, or for a single user to use different domains for different
>> services.
>
> Sure. Would it suffice if we included the following text:
>
> "A client may support multiple users, potentially with different
>    domains, or for a single user to use different domains for 
> different
>    services.  The means to choose and extract the desired domain name 
> may
> be
>    different based on the type of identifier, service being used etc
>    which are outside the scope of this document."

Yes, thanks.

>
>>
>> -4.2, general: Do I correctly understand that most of this section
>> describes the results of applying RFC 5928 procedures to the 
>> extracted
>> domain name?
>
> Yes, the section does exactly that.
>
>> If so, is it not enough reference 5928 and leave it at that?
>
> Sure. We can certainly remove the example.

On reflection, I will leave that to your discretion.

[...]

>
>>
>> - Informational References:
>> I-D.ietf-rtcweb-return and RFC 6125 are cited as part of normative
>> requirements, which makes them by definition need to be normative
>> references. I-D.ietf-tram-turn-mobility, RFC6024, and RFC7250 are
>> borderline; I think one could make an argument that one needs to read
>> them to fully understand this draft.
>
> We'll update the draft to cite these as non-normative.
>

It may not be that simple. Normative language around a citation is a 
clue that a reference needs to be normative. But lack of it does not 
necessarily prove the opposite. The test is whether someone could fully 
understand and implement this draft without reading the referenced 
document.

[...]


From nobody Fri Sep  9 02:34:44 2016
Return-Path: <suresh.krishnan@ericsson.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 B83A712B379; Fri,  9 Sep 2016 02:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 zSWxHmfAI3PV; Fri,  9 Sep 2016 02:34:35 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (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 7F4C712B391; Fri,  9 Sep 2016 02:33:18 -0700 (PDT)
X-AuditID: c6180641-e73ff70000000a0b-48-57d22d77c187
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by  (Symantec Mail Security) with SMTP id A1.10.02571.87D22D75; Fri,  9 Sep 2016 05:33:14 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.03.0301.000; Fri, 9 Sep 2016 05:33:14 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, Pete Resnick <presnick@qti.qualcomm.com>
Thread-Topic: GenART post-telechat comment on draft-ietf-tram-turn-mobility-08
Thread-Index: AQHSCFh4psfOltlceECMFEqRrV0QZQ==
Date: Fri, 9 Sep 2016 09:33:14 +0000
Message-ID: <E87B771635882B4BA20096B589152EF643E99AAA@eusaamb107.ericsson.se>
References: <6ECD9A3A-0D63-421B-953D-A516D773CCBA@qti.qualcomm.com> <E87B771635882B4BA20096B589152EF643E961F1@eusaamb107.ericsson.se> <092F2B7C-4B03-4956-9C0E-1C5983D2AF72@qti.qualcomm.com> <abf54eff0f4c4d28b45db8e185e5e5c2@XCH-RCD-017.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLLMWRmVeSWpSXmKPExsUyuXRPoG6V7qVwg6PvLC1OPH/NaHH11WcW ixl/JjJbXLnawmxxYvc2RosPay+wObB5TPm9kdVjyZKfTB6Lpj5jDGCO4rJJSc3JLEst0rdL 4Mr4/aafveCLYkVf/2KmBsa7Ul2MHBwSAiYSEx8IdzFycQgJbGCUuPipmwnCWcYocenLRdYu Rk4ONqCiDTs/M4HYIgJJEuuv/mcFKWIWOMoo0fNoF1iRsICvxKbFp5lBpooIBEisbwyGqNeT WHTtHzuIzSKgIrHjzl2wcl6g8v+7nrNBLPvDKDFzwR2wBYwCYhLfT60Bs5kFxCVuPZkPZksI CEgs2XOeGcIWlXj5+B8rhK0k8fH3fHaIeh2JBbs/sUHY2hLLFr5mhlgmKHFy5hOWCYwis5CM nYWkZRaSlllIWhYwsqxi5CgtLsjJTTcy3MQIjJRjEmyOOxj39noeYhTgYFTi4V1gdjFciDWx rLgy9xCjBAezkgjv/oZL4UK8KYmVValF+fFFpTmpxYcYpTlYlMR59V8qhgsJpCeWpGanphak FsFkmTg4pRoY563rTH5yk6fj/4O2Y49iZUqPrmHffubKhOhK6y4T99uOJ89/FXqboHHJf2mX /enw47Pm95r0aajmGTd479yXoseVmvtU+odtg+2X44lcT2oaXUwidi5LrTuhqVRYv9A/xvDC n+t22SLflSfeS9h8eMPFGSKsj9XONi1ct2pGgdun0Dll4vk6SizFGYmGWsxFxYkAhvE0JJAC AAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/rOIqqUAOgfeI4g6ENIhqf1UdDmo>
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-tram-turn-mobility.all@ietf.org" <draft-ietf-tram-turn-mobility.all@ietf.org>, IESG <iesg@ietf.org>, "tram@ietf.org" <tram@ietf.org>
Subject: Re: [tram] GenART post-telechat comment on draft-ietf-tram-turn-mobility-08
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 09:34:39 -0000

Hi Tiru,=0A=
=0A=
On 09/07/2016 10:50 PM, Tirumaleswar Reddy (tireddy) wrote:=0A=
> Please see inline=0A=
>=0A=
> *From:*Pete Resnick [mailto:presnick@qti.qualcomm.com]=0A=
> *Sent:* Wednesday, September 7, 2016 8:53 PM=0A=
> *To:* Suresh Krishnan <suresh.krishnan@ericsson.com>=0A=
> *Cc:* IESG <iesg@ietf.org>; General Area Review Team <gen-art@ietf.org>;=
=0A=
> draft-ietf-tram-turn-mobility.all@ietf.org; tram@ietf.org=0A=
> *Subject:* Re: GenART post-telechat comment on draft-ietf-tram-turn-mobil=
ity-08=0A=
>=0A=
>=0A=
>=0A=
> [Trimming down a bit]=0A=
>=0A=
> On 6 Sep 2016, at 22:57, Suresh Krishnan wrote:=0A=
>=0A=
>         OLD: If a client wants to refresh an existing allocation and upda=
te its=0A=
>=0A=
>         time-to-expiry or delete an existing allocation, it will send a R=
efresh=0A=
>=0A=
>         Request as described in Section 7.1 of [RFC5766]=0A=
>=0A=
>         NEW:=0A=
>=0A=
>         If a client wants to refresh an existing allocation and update it=
s=0A=
>=0A=
>         time-to-expiry or delete an existing allocation, it MUST send a R=
efresh=0A=
>=0A=
>         Request as described in Section 7.1 of [RFC5766] and MUST NOT inc=
lude a=0A=
>=0A=
>         MOBILITY-TICKET attribute.=0A=
>=0A=
>     I will try to explain my line of reasoning. Let me know where you dis=
agree.=0A=
>=0A=
>     If the client includes a MOBILTY-TICKET attribute in the refresh meth=
od, the=0A=
>=0A=
>     refresh will fail. So, the MUST NOT is aimed at preventing the client=
 from=0A=
>=0A=
>     sending a useless packet that will be rejected anyway.=0A=
>=0A=
> "Useless" seems not a good reason for a "MUST NOT". Perhaps Tiru's=0A=
> explanation of "will cause an extra retransmission" is a better reason. B=
ut=0A=
> as I said, this isn't one that I will complain too vociferously about: Wh=
at=0A=
> this says is "don't include the attribute; it will be rejected and you'll=
=0A=
> have to retransmit"; if you want a "MUST NOT" for that, so be it. But:=0A=
>=0A=
>     The MUST stresses that=0A=
>=0A=
>     the original Refresh procedure from RFC5766 needs to be used instead =
of the=0A=
>=0A=
>     Refresh procedure with the MOBILITY-TICKET described in this one.=0A=
>=0A=
> Ah! If that's was meant, that's not what was said. It sounds like you're=
=0A=
> saying that the client /can't/ refresh a request by simply sending an=0A=
> allocate request with the old MOBILITY-TICKET. And then I get a bit confu=
sed=0A=
> about the MUST NOT: The next sentence after this bit says:=0A=
>=0A=
> If the client wants to retain=0A=
> the existing allocation in case of IP change, it will include the=0A=
> MOBILITY-TICKET attribute received in the Allocate Success response.=0A=
>=0A=
> The previous sentence says that you MUST NOT include the attribute. This=
=0A=
> sentence says that you do include it. I suspect that what was intended wa=
s,=0A=
> "If you /just/ want to refresh to retain the existing allocation in case =
of=0A=
> an IP change, you can send an allocate request including the old=0A=
> MOBILITY-TICKET attribute. If you need to update time-to-expiry or delete=
 the=0A=
> allocation, then you /can't/ just send a new allocate request with the=0A=
> attribute; that will get rejected. You instead /have to/ use the refresh=
=0A=
> request in 5766." Do I have that right? If so, the paragraph could use a=
=0A=
> rewrite; it's not the MUST and the MUST NOT that are the problem.=0A=
>=0A=
> [TR] I propose the following text to avoid the confusion:=0A=
>=0A=
>    If a client wants to refresh an existing allocation and update its=0A=
>=0A=
>    time-to-expiry or delete an existing allocation in case of no IP addre=
ss=0A=
> change, it will send a=0A=
>=0A=
>    Refresh Request as described in Section 7.1 of [RFC5766] and MUST NOT=
=0A=
>=0A=
>    include a MOBILITY-TICKET attribute.  If the client wants to retain=0A=
>=0A=
>    the existing allocation in case of IP address change, it will include =
the=0A=
>=0A=
>    MOBILITY-TICKET attribute received in the Allocate Success response=0A=
>=0A=
>    in the Refresh Request.=0A=
=0A=
I have no issues with this new text. Please check with Pete if it resolves =
=0A=
his concerns.=0A=
=0A=
Thanks=0A=
Suresh=0A=
=0A=


From nobody Fri Sep  9 03:20:22 2016
Return-Path: <suresh.krishnan@ericsson.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 3C73F12B339; Fri,  9 Sep 2016 03:20:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 y71I4m2qaGkV; Fri,  9 Sep 2016 03:20:13 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (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 DE95512B2F7; Fri,  9 Sep 2016 03:20:07 -0700 (PDT)
X-AuditID: c6180641-e73ff70000000a0b-ba-57d238734067
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by  (Symantec Mail Security) with SMTP id D3.E1.02571.37832D75; Fri,  9 Sep 2016 06:20:04 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0301.000; Fri, 9 Sep 2016 06:20:04 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: "Prashanth Patil (praspati)" <praspati@cisco.com>, The IESG <iesg@ietf.org>
Thread-Topic: Suresh Krishnan's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
Thread-Index: AQHSBAfnnle9TS+moUifmMZPWr6O+Q==
Date: Fri, 9 Sep 2016 10:20:04 +0000
Message-ID: <E87B771635882B4BA20096B589152EF643E99BCB@eusaamb107.ericsson.se>
References: <147270350795.31961.8306227467315681365.idtracker@ietfa.amsl.com> <D3EDDAE4.130787%praspati@cisco.com> <E87B771635882B4BA20096B589152EF643E96358@eusaamb107.ericsson.se> <D3F627AD.13251F%praspati@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLLMWRmVeSWpSXmKPExsUyuXRPgm6JxaVwg2WXdC0+rYu2mPFnIrNF 986jjBbXr4RaLP+5ks3iw9oLbA5sHlN+b2T1WLLkJ5PHvzlPmQOYo7hsUlJzMstSi/TtErgy DjS3MBWsFKi4s3IGUwPjF54uRk4OCQETidn377B3MXJxCAlsYJRo+jGFDcJZxiix/PFOZpAq NqCqDTs/M4HYIgKBElNP/GUFKWIWeMQo0X9iKViRsECKxOSTM9ghilIl2uYtZoSw9STeNdwF s1kEVCS23HvGBmLzCvhK7Pn+kgVi231GibdXfoAVMQqISXw/tQZsG7OAuMStJ/OZIG4VkFiy 5zwzhC0q8fLxP1YIW0lizutrzBD1OhILdn9ig7C1JZYtfM0MsUxQ4uTMJywTGEVmIRk7C0nL LCQts5C0LGBkWcXIUVpckJObbmS4iREYKcck2Bx3MO7t9TzEKMDBqMTDu8DsYrgQa2JZcWXu IUYJDmYlEd6J3ZfChXhTEiurUovy44tKc1KLDzFKc7AoifPqv1QMFxJITyxJzU5NLUgtgsky cXBKNTBG8vTtDu24mlOhUHVw06+/r6Y8Wqztlu9s+8Wed05xhaR7WVJoAvtVk23npKymHJgZ yzJ5uvnDU8fyl3s9STSV+Hsj+GKGblXRRPnDm5ntvxewyqfenpt9SWQKx+Pyg1VF/XuWTdsf NPXS9JLTCoEF+Us1fuc4TuM8e/0v/+oVn5hFkqw+CjQosRRnJBpqMRcVJwIAov4Sf5ACAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/0IGWP8YgmwDQkbzBkAN2cf2SZDI>
Cc: Simon Perreault <sperreault@jive.com>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, "tram@ietf.org" <tram@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>
Subject: Re: [tram] Suresh Krishnan's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 10:20:16 -0000

Hi Prashanth,=0A=
=0A=
On 09/07/2016 11:27 PM, Prashanth Patil (praspati) wrote:=0A=
>>> Does following text address your concerns?=0A=
>>>=0A=
>>> ..=0A=
>>>    DHCP can be used to determine the domain name related to an=0A=
>>>    interface's point of network attachment.  Network operators may=0A=
>>>    provide the domain name to be used for service discovery within an=
=0A=
>>>    access network using DHCP.  Sections 3.2 and 3.3 of [RFC5986] define=
=0A=
>>>    DHCP IPv4 and IPv6 access network domain name options,=0A=
>>>    OPTION_V4_ACCESS_DOMAIN and OPTION_V6_ACCESS_DOMAIN respectively, to=
=0A=
>>>    identify a domain name that is suitable for service discovery within=
=0A=
>>>    the access network.=0A=
>>>=0A=
>>>    For IPv4, the discovery procedure MUST request for an access network=
=0A=
>>>    domain name option in a Parameter Request List option, as described=
=0A=
>>>    in [RFC2131].  [RFC2132] defines the DHCP IPv4 domain name option;=
=0A=
>>>    while this option is less suitable, a client MAY request for it if=
=0A=
>>>    the access network domain name defined in [RFC5986] is not available=
.=0A=
>>>=0A=
>>>    For IPv6, the discovery procedure MUST request for an access network=
=0A=
>>>    domain name option in an Options Request Option (ORO), as described=
=0A=
>>>    in [RFC3315].=0A=
>>>=0A=
>>>    If neither option can be retrieved the procedure fails for this=0A=
>>>    interface.  If a result can be retrieved it will be used as input=0A=
>>>    for S-NAPTR resolution.=0A=
>>=0A=
>> Thank you. That certainly addresses one part of my DISCUSS but it still=
=0A=
>> needs=0A=
>> additional text on the DHCPv6 side to specify which message exchange wil=
l=0A=
>> be=0A=
>> used.=0A=
>=0A=
> Sorry, missed that one.=0A=
>=0A=
>> Did you intend to use the stateful exchange or the stateless exchange?=
=0A=
>=0A=
> We intend to use stateless. Will update the draft accordingly.=0A=
=0A=
Sounds good. I will clear when the new revision posts.=0A=
=0A=
Thanks=0A=
Suresh=0A=
=0A=


From nobody Fri Sep  9 09:08:11 2016
Return-Path: <presnick@qti.qualcomm.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 F11C512B27E; Fri,  9 Sep 2016 09:08:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.528
X-Spam-Level: 
X-Spam-Status: No, score=-8.528 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.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 qqf_OP20rP2g; Fri,  9 Sep 2016 09:08:09 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98C2C12B28C; Fri,  9 Sep 2016 09:08:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1473437289; x=1504973289; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=5qsbxy2p3DNUlSRTJm2ss4aIGDpRBWLGGVdMM5nr6oY=; b=YoCGeY9PxaXwbS4nkjtO7aCDPQy1THVF7fBeoP+SWO4g9sSw7SA3X8zu qJnljsXrJDJzNPZARZMem7k86S3uCSEhDYuKHU+fQ7I5M53+ljCCS2x8F gxmSGJ4hKrHYdYZHTL2QTpMfzibgls1fTO4EFLWseBEcn5Zy1IZb4zivX o=;
X-IronPort-AV: E=Sophos;i="5.30,305,1470726000";  d="scan'208,217";a="318365434"
Received: from unknown (HELO Ironmsg03-R.qualcomm.com) ([10.53.140.107]) by wolverine02.qualcomm.com with ESMTP; 09 Sep 2016 09:08:09 -0700
X-IronPort-AV: E=McAfee;i="5700,7163,8283"; a="1215790883"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 09 Sep 2016 09:08:08 -0700
Received: from [10.64.128.83] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 9 Sep 2016 09:08:07 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Date: Fri, 9 Sep 2016 11:08:05 -0500
Message-ID: <B4CE5A5C-3DB0-4B4B-86B9-B7AF02F7DB76@qti.qualcomm.com>
In-Reply-To: <E87B771635882B4BA20096B589152EF643E99AAA@eusaamb107.ericsson.se>
References: <6ECD9A3A-0D63-421B-953D-A516D773CCBA@qti.qualcomm.com> <E87B771635882B4BA20096B589152EF643E961F1@eusaamb107.ericsson.se> <092F2B7C-4B03-4956-9C0E-1C5983D2AF72@qti.qualcomm.com> <abf54eff0f4c4d28b45db8e185e5e5c2@XCH-RCD-017.cisco.com> <E87B771635882B4BA20096B589152EF643E99AAA@eusaamb107.ericsson.se>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_0068A2E4-BFFA-4897-8B4B-9E6142EAC687_="
X-Mailer: MailMate (1.9.5r5260)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01B.na.qualcomm.com (10.85.0.82) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/J4p_Rbcub-tPp1zmdU3tXo_Ipg8>
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-tram-turn-mobility.all@ietf.org" <draft-ietf-tram-turn-mobility.all@ietf.org>, IESG <iesg@ietf.org>, Tirumaleswar Reddy <tireddy@cisco.com>, "tram@ietf.org" <tram@ietf.org>
Subject: Re: [tram] GenART post-telechat comment on draft-ietf-tram-turn-mobility-08
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 16:08:11 -0000

--=_MailMate_0068A2E4-BFFA-4897-8B4B-9E6142EAC687_=
Content-Type: text/plain; format=flowed

On 9 Sep 2016, at 4:33, Suresh Krishnan wrote:

> Hi Tiru,
>
> On 09/07/2016 10:50 PM, Tirumaleswar Reddy (tireddy) wrote:
>> [TR] I propose the following text to avoid the confusion:
>>
>>    If a client wants to refresh an existing allocation and update its
>>    time-to-expiry or delete an existing allocation in case of no IP 
>> address
>> change, it will send a
>>    Refresh Request as described in Section 7.1 of [RFC5766] and MUST 
>> NOT
>>    include a MOBILITY-TICKET attribute.  If the client wants to 
>> retain
>>    the existing allocation in case of IP address change, it will 
>> include the
>>    MOBILITY-TICKET attribute received in the Allocate Success 
>> response
>>    in the Refresh Request.
>
> I have no issues with this new text. Please check with Pete if it 
> resolves
> his concerns.

Wait, now I'm even more confused. The second sentence says that you *are 
allowed* to include the MOBILITY-TICKET attribute in a Refresh Request 
if you want to retain the allocation, even though the first sentence 
says you MUST NOT. Is this because the Refresh Request with the 
MOBILITY-TICKET attribute will only be rejected if the IP address is the 
same? If so, perhaps this is what you meant:

     If a client wants to refresh an existing allocation and update its
     time-to-expiry or delete an existing allocation, it sends a Refresh
     Request as described in Section 7.1 of [RFC5766]. If IP address of
     the client has changed and the client wants to retain the existing
     allocation, the client includes the MOBILITY-TICKET attribute
     received in the Allocate Success response in the Refresh Request. 
If
     there has been no IP address change, the client MUST NOT include a
     MOBILITY-TICKET attribute, as this will be rejected by the server
     and the client would need to retransmit the Refresh Request.

If that's not what you meant, you should probably clarify.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478
--=_MailMate_0068A2E4-BFFA-4897-8B4B-9E6142EAC687_=
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">On 9 Sep 2016, at 4:33, Suresh Krishnan wrote:</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:pre-wrap"><blockquote style=3D"border-left:2px =
solid #777; color:#777; margin:0 0 5px; padding-left:5px"><div dir=3D"aut=
o">Hi Tiru,
</div><div dir=3D"auto">
</div><div dir=3D"auto">On 09/07/2016 10:50 PM, Tirumaleswar Reddy (tired=
dy) wrote:
</div><blockquote style=3D"border-left:2px solid #777; color:#999; margin=
:0 0 5px; padding-left:5px; border-left-color:#999"><div dir=3D"auto">[TR=
] I propose the following text to avoid the confusion:
</div><div dir=3D"auto">
</div><div dir=3D"auto">   If a client wants to refresh an existing alloc=
ation and update its
</div><div dir=3D"auto">   time-to-expiry or delete an existing allocatio=
n in case of no IP address
</div><div dir=3D"auto">change, it will send a
</div><div dir=3D"auto">   Refresh Request as described in Section 7.1 of=
 [RFC5766] and MUST NOT
</div><div dir=3D"auto">   include a MOBILITY-TICKET attribute.  If the c=
lient wants to retain
</div><div dir=3D"auto">   the existing allocation in case of IP address =
change, it will include the
</div><div dir=3D"auto">   MOBILITY-TICKET attribute received in the Allo=
cate Success response
</div><div dir=3D"auto">   in the Refresh Request.
</div></blockquote><div dir=3D"auto">
</div><div dir=3D"auto">I have no issues with this new text. Please check=
 with Pete if it resolves
</div><div dir=3D"auto">his concerns.
</div></blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">Wait, now I'm even more confused. The second sentence say=
s that you <em>are allowed</em> to include the MOBILITY-TICKET attribute =
in a Refresh Request if you want to retain the allocation, even though th=
e first sentence says you MUST NOT. Is this because the Refresh Request w=
ith the MOBILITY-TICKET attribute will only be rejected if the IP address=
 is the same? If so, perhaps this is what you meant:</p>

<pre style=3D"background-color:#F7F7F7; border-radius:5px 5px 5px 5px; ma=
rgin-left:15px; margin-right:15px; max-width:90vw; overflow-x:auto; paddi=
ng:5px" bgcolor=3D"#F7F7F7"><code style=3D"background-color:#F7F7F7; bord=
er-radius:3px; margin:0; padding:0" bgcolor=3D"#F7F7F7">If a client wants=
 to refresh an existing allocation and update its
time-to-expiry or delete an existing allocation, it sends a Refresh
Request as described in Section 7.1 of [RFC5766]. If IP address of
the client has changed and the client wants to retain the existing
allocation, the client includes the MOBILITY-TICKET attribute
received in the Allocate Success response in the Refresh Request. If
there has been no IP address change, the client MUST NOT include a
MOBILITY-TICKET attribute, as this will be rejected by the server
and the client would need to retransmit the Refresh Request.
</code></pre>

<p dir=3D"auto">If that's not what you meant, you should probably clarify=
=2E</p>

<p dir=3D"auto">pr<br>
-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" style=3D"co=
lor:#3983C4">http://www.qualcomm.com/~presnick/</a><br>
Qualcomm Technologies, Inc. - +1 (858)651-4478</p>
</div>
</div>
</body>
</html>

--=_MailMate_0068A2E4-BFFA-4897-8B4B-9E6142EAC687_=--


From nobody Fri Sep  9 11:20:08 2016
Return-Path: <prvs=3060f6bc97=jonathan@vidyo.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 33F1312B1B5; Fri,  9 Sep 2016 11:19:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.83
X-Spam-Level: 
X-Spam-Status: No, score=-1.83 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=0.77, 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 jIX96rEAg2FG; Fri,  9 Sep 2016 11:19:55 -0700 (PDT)
Received: from mx0b-00198e01.pphosted.com (mx0b-00198e01.pphosted.com [67.231.157.197]) (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 9DC0312B0EC; Fri,  9 Sep 2016 11:19:55 -0700 (PDT)
Received: from pps.filterd (m0073110.ppops.net [127.0.0.1]) by mx0b-00198e01.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u89IIwjE030593; Fri, 9 Sep 2016 14:19:51 -0400
Received: from mail.vidyo.com ([162.209.16.214]) by mx0b-00198e01.pphosted.com with ESMTP id 25bc3xrww4-1 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NOT); Fri, 09 Sep 2016 14:19:51 -0400
Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0195.001; Fri, 9 Sep 2016 13:19:51 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Thread-Topic: [tram] GenART post-telechat comment on draft-ietf-tram-turn-mobility-08
Thread-Index: AQHSCsYziHDkZGac+kykE7ETkhSi76Bxy8WA
Date: Fri, 9 Sep 2016 18:19:50 +0000
Message-ID: <2DC7E1A2-D2AD-472C-BE71-976757246209@vidyo.com>
References: <6ECD9A3A-0D63-421B-953D-A516D773CCBA@qti.qualcomm.com> <E87B771635882B4BA20096B589152EF643E961F1@eusaamb107.ericsson.se> <092F2B7C-4B03-4956-9C0E-1C5983D2AF72@qti.qualcomm.com> <abf54eff0f4c4d28b45db8e185e5e5c2@XCH-RCD-017.cisco.com> <E87B771635882B4BA20096B589152EF643E99AAA@eusaamb107.ericsson.se> <B4CE5A5C-3DB0-4B4B-86B9-B7AF02F7DB76@qti.qualcomm.com>
In-Reply-To: <B4CE5A5C-3DB0-4B4B-86B9-B7AF02F7DB76@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [160.79.219.114]
Content-Type: multipart/alternative; boundary="_000_2DC7E1A2D2AD472CBE71976757246209vidyocom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-09-09_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1609020000 definitions=main-1609090273
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/NpOcMKZ7YEIxh8qtwG6CHtnleno>
Cc: "tram@ietf.org" <tram@ietf.org>, General Area Review Team <gen-art@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>, Tirumaleswar Reddy <tireddy@cisco.com>, "draft-ietf-tram-turn-mobility.all@ietf.org" <draft-ietf-tram-turn-mobility.all@ietf.org>, The The IESG <iesg@ietf.org>
Subject: Re: [tram] GenART post-telechat comment on draft-ietf-tram-turn-mobility-08
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 18:19:57 -0000

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

DQpPbiBTZXAgOSwgMjAxNiwgYXQgMTI6MDggUE0sIFBldGUgUmVzbmljayA8cHJlc25pY2tAcXRp
LnF1YWxjb21tLmNvbTxtYWlsdG86cHJlc25pY2tAcXRpLnF1YWxjb21tLmNvbT4+IHdyb3RlOg0K
DQoNCk9uIDkgU2VwIDIwMTYsIGF0IDQ6MzMsIFN1cmVzaCBLcmlzaG5hbiB3cm90ZToNCg0KSGkg
VGlydSwNCk9uIDA5LzA3LzIwMTYgMTA6NTAgUE0sIFRpcnVtYWxlc3dhciBSZWRkeSAodGlyZWRk
eSkgd3JvdGU6DQpbVFJdIEkgcHJvcG9zZSB0aGUgZm9sbG93aW5nIHRleHQgdG8gYXZvaWQgdGhl
IGNvbmZ1c2lvbjoNCklmIGEgY2xpZW50IHdhbnRzIHRvIHJlZnJlc2ggYW4gZXhpc3RpbmcgYWxs
b2NhdGlvbiBhbmQgdXBkYXRlIGl0cw0KdGltZS10by1leHBpcnkgb3IgZGVsZXRlIGFuIGV4aXN0
aW5nIGFsbG9jYXRpb24gaW4gY2FzZSBvZiBubyBJUCBhZGRyZXNzDQpjaGFuZ2UsIGl0IHdpbGwg
c2VuZCBhDQpSZWZyZXNoIFJlcXVlc3QgYXMgZGVzY3JpYmVkIGluIFNlY3Rpb24gNy4xIG9mIFtS
RkM1NzY2XSBhbmQgTVVTVCBOT1QNCmluY2x1ZGUgYSBNT0JJTElUWS1USUNLRVQgYXR0cmlidXRl
LiBJZiB0aGUgY2xpZW50IHdhbnRzIHRvIHJldGFpbg0KdGhlIGV4aXN0aW5nIGFsbG9jYXRpb24g
aW4gY2FzZSBvZiBJUCBhZGRyZXNzIGNoYW5nZSwgaXQgd2lsbCBpbmNsdWRlIHRoZQ0KTU9CSUxJ
VFktVElDS0VUIGF0dHJpYnV0ZSByZWNlaXZlZCBpbiB0aGUgQWxsb2NhdGUgU3VjY2VzcyByZXNw
b25zZQ0KaW4gdGhlIFJlZnJlc2ggUmVxdWVzdC4NCkkgaGF2ZSBubyBpc3N1ZXMgd2l0aCB0aGlz
IG5ldyB0ZXh0LiBQbGVhc2UgY2hlY2sgd2l0aCBQZXRlIGlmIGl0IHJlc29sdmVzDQpoaXMgY29u
Y2VybnMuDQoNCldhaXQsIG5vdyBJJ20gZXZlbiBtb3JlIGNvbmZ1c2VkLiBUaGUgc2Vjb25kIHNl
bnRlbmNlIHNheXMgdGhhdCB5b3UgYXJlIGFsbG93ZWQgdG8gaW5jbHVkZSB0aGUgTU9CSUxJVFkt
VElDS0VUIGF0dHJpYnV0ZSBpbiBhIFJlZnJlc2ggUmVxdWVzdCBpZiB5b3Ugd2FudCB0byByZXRh
aW4gdGhlIGFsbG9jYXRpb24sIGV2ZW4gdGhvdWdoIHRoZSBmaXJzdCBzZW50ZW5jZSBzYXlzIHlv
dSBNVVNUIE5PVC4gSXMgdGhpcyBiZWNhdXNlIHRoZSBSZWZyZXNoIFJlcXVlc3Qgd2l0aCB0aGUg
TU9CSUxJVFktVElDS0VUIGF0dHJpYnV0ZSB3aWxsIG9ubHkgYmUgcmVqZWN0ZWQgaWYgdGhlIElQ
IGFkZHJlc3MgaXMgdGhlIHNhbWU/IElmIHNvLCBwZXJoYXBzIHRoaXMgaXMgd2hhdCB5b3UgbWVh
bnQ6DQoNCklmIGEgY2xpZW50IHdhbnRzIHRvIHJlZnJlc2ggYW4gZXhpc3RpbmcgYWxsb2NhdGlv
biBhbmQgdXBkYXRlIGl0cw0KdGltZS10by1leHBpcnkgb3IgZGVsZXRlIGFuIGV4aXN0aW5nIGFs
bG9jYXRpb24sIGl0IHNlbmRzIGEgUmVmcmVzaA0KUmVxdWVzdCBhcyBkZXNjcmliZWQgaW4gU2Vj
dGlvbiA3LjEgb2YgW1JGQzU3NjZdLiBJZiBJUCBhZGRyZXNzIG9mDQp0aGUgY2xpZW50IGhhcyBj
aGFuZ2VkIGFuZCB0aGUgY2xpZW50IHdhbnRzIHRvIHJldGFpbiB0aGUgZXhpc3RpbmcNCmFsbG9j
YXRpb24sIHRoZSBjbGllbnQgaW5jbHVkZXMgdGhlIE1PQklMSVRZLVRJQ0tFVCBhdHRyaWJ1dGUN
CnJlY2VpdmVkIGluIHRoZSBBbGxvY2F0ZSBTdWNjZXNzIHJlc3BvbnNlIGluIHRoZSBSZWZyZXNo
IFJlcXVlc3QuIElmDQp0aGVyZSBoYXMgYmVlbiBubyBJUCBhZGRyZXNzIGNoYW5nZSwgdGhlIGNs
aWVudCBNVVNUIE5PVCBpbmNsdWRlIGENCk1PQklMSVRZLVRJQ0tFVCBhdHRyaWJ1dGUsIGFzIHRo
aXMgd2lsbCBiZSByZWplY3RlZCBieSB0aGUgc2VydmVyDQphbmQgdGhlIGNsaWVudCB3b3VsZCBu
ZWVkIHRvIHJldHJhbnNtaXQgdGhlIFJlZnJlc2ggUmVxdWVzdC4NCg0KDQpJZiB0aGF0J3Mgbm90
IHdoYXQgeW91IG1lYW50LCB5b3Ugc2hvdWxkIHByb2JhYmx5IGNsYXJpZnkuDQoNClRvIGJlIHBy
ZWNpc2UsIOKAnElQIGFkZHJlc3PigJ0gaGVyZSBzaG91bGQgYmUg4oCcSVAgYWRkcmVzcyBvciBz
b3VyY2UgcG9ydOKAnSwgcmlnaHQ/ICBPbmUgY2FzZSBJ4oCZbSB0aGlua2luZyBvZiBpcyB3aGVy
ZSBhIGNsaWVudCBtb3ZlZCB0byBhIG5ldyBwcml2YXRlIElQIGFkZHJlc3MsIGJ1dCBpcyBzdGls
bCBiZWhpbmQgdGhlIHNhbWUgQ0dOIGFuZCBzbyBoYXMgdGhlIHNhbWUgZXh0ZXJuYWwgSVAgYWRk
cmVzcy4NCg==

--_000_2DC7E1A2D2AD472CBE71976757246209vidyocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <2993E6042AA54B4FA66FD9B9811FAEFB@vidyo.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPGRpdj4N
CjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj5PbiBTZXAg
OSwgMjAxNiwgYXQgMTI6MDggUE0sIFBldGUgUmVzbmljayAmbHQ7PGEgaHJlZj0ibWFpbHRvOnBy
ZXNuaWNrQHF0aS5xdWFsY29tbS5jb20iIGNsYXNzPSIiPnByZXNuaWNrQHF0aS5xdWFsY29tbS5j
b208L2E+Jmd0OyB3cm90ZTo8L2Rpdj4NCjxiciBjbGFzcz0iQXBwbGUtaW50ZXJjaGFuZ2UtbmV3
bGluZSI+DQo8ZGl2IGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj4NCjxkaXYgc3R5bGU9ImZvbnQt
ZmFtaWx5OnNhbnMtc2VyaWYiIGNsYXNzPSIiPg0KPGRpdiBzdHlsZT0id2hpdGUtc3BhY2U6bm9y
bWFsIiBjbGFzcz0iIj4NCjxwIGRpcj0iYXV0byIgY2xhc3M9IiI+T24gOSBTZXAgMjAxNiwgYXQg
NDozMywgU3VyZXNoIEtyaXNobmFuIHdyb3RlOjwvcD4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNz
PSJ3ZWJraXQtYmxvY2stcGxhY2Vob2xkZXIiPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXYgc3R5bGU9
IndoaXRlLXNwYWNlOnByZS13cmFwIiBjbGFzcz0iIj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3Jk
ZXItbGVmdDoycHggc29saWQgIzc3NzsgY29sb3I6Izc3NzsgbWFyZ2luOjAgMCA1cHg7IHBhZGRp
bmctbGVmdDo1cHgiIGNsYXNzPSIiPg0KPGRpdiBkaXI9ImF1dG8iIGNsYXNzPSIiPkhpIFRpcnUs
IDwvZGl2Pg0KPGRpdiBkaXI9ImF1dG8iIGNsYXNzPSIiPjwvZGl2Pg0KPGRpdiBkaXI9ImF1dG8i
IGNsYXNzPSIiPk9uIDA5LzA3LzIwMTYgMTA6NTAgUE0sIFRpcnVtYWxlc3dhciBSZWRkeSAodGly
ZWRkeSkgd3JvdGU6DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXItbGVmdDoycHgg
c29saWQgIzc3NzsgY29sb3I6Izk5OTsgbWFyZ2luOjAgMCA1cHg7IHBhZGRpbmctbGVmdDo1cHg7
IGJvcmRlci1sZWZ0LWNvbG9yOiM5OTkiIGNsYXNzPSIiPg0KPGRpdiBkaXI9ImF1dG8iIGNsYXNz
PSIiPltUUl0gSSBwcm9wb3NlIHRoZSBmb2xsb3dpbmcgdGV4dCB0byBhdm9pZCB0aGUgY29uZnVz
aW9uOg0KPC9kaXY+DQo8ZGl2IGRpcj0iYXV0byIgY2xhc3M9IiI+PC9kaXY+DQo8ZGl2IGRpcj0i
YXV0byIgY2xhc3M9IiI+SWYgYSBjbGllbnQgd2FudHMgdG8gcmVmcmVzaCBhbiBleGlzdGluZyBh
bGxvY2F0aW9uIGFuZCB1cGRhdGUgaXRzDQo8L2Rpdj4NCjxkaXYgZGlyPSJhdXRvIiBjbGFzcz0i
Ij50aW1lLXRvLWV4cGlyeSBvciBkZWxldGUgYW4gZXhpc3RpbmcgYWxsb2NhdGlvbiBpbiBjYXNl
IG9mIG5vIElQIGFkZHJlc3MNCjwvZGl2Pg0KPGRpdiBkaXI9ImF1dG8iIGNsYXNzPSIiPmNoYW5n
ZSwgaXQgd2lsbCBzZW5kIGEgPC9kaXY+DQo8ZGl2IGRpcj0iYXV0byIgY2xhc3M9IiI+UmVmcmVz
aCBSZXF1ZXN0IGFzIGRlc2NyaWJlZCBpbiBTZWN0aW9uIDcuMSBvZiBbUkZDNTc2Nl0gYW5kIE1V
U1QgTk9UDQo8L2Rpdj4NCjxkaXYgZGlyPSJhdXRvIiBjbGFzcz0iIj5pbmNsdWRlIGEgTU9CSUxJ
VFktVElDS0VUIGF0dHJpYnV0ZS4gSWYgdGhlIGNsaWVudCB3YW50cyB0byByZXRhaW4NCjwvZGl2
Pg0KPGRpdiBkaXI9ImF1dG8iIGNsYXNzPSIiPnRoZSBleGlzdGluZyBhbGxvY2F0aW9uIGluIGNh
c2Ugb2YgSVAgYWRkcmVzcyBjaGFuZ2UsIGl0IHdpbGwgaW5jbHVkZSB0aGUNCjwvZGl2Pg0KPGRp
diBkaXI9ImF1dG8iIGNsYXNzPSIiPk1PQklMSVRZLVRJQ0tFVCBhdHRyaWJ1dGUgcmVjZWl2ZWQg
aW4gdGhlIEFsbG9jYXRlIFN1Y2Nlc3MgcmVzcG9uc2UNCjwvZGl2Pg0KPGRpdiBkaXI9ImF1dG8i
IGNsYXNzPSIiPmluIHRoZSBSZWZyZXNoIFJlcXVlc3QuIDwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0K
PGRpdiBkaXI9ImF1dG8iIGNsYXNzPSIiPjwvZGl2Pg0KPGRpdiBkaXI9ImF1dG8iIGNsYXNzPSIi
PkkgaGF2ZSBubyBpc3N1ZXMgd2l0aCB0aGlzIG5ldyB0ZXh0LiBQbGVhc2UgY2hlY2sgd2l0aCBQ
ZXRlIGlmIGl0IHJlc29sdmVzDQo8L2Rpdj4NCjxkaXYgZGlyPSJhdXRvIiBjbGFzcz0iIj5oaXMg
Y29uY2VybnMuIDwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8ZGl2IHN0eWxlPSJ3aGl0
ZS1zcGFjZTpub3JtYWwiIGNsYXNzPSIiPg0KPHAgZGlyPSJhdXRvIiBjbGFzcz0iIj5XYWl0LCBu
b3cgSSdtIGV2ZW4gbW9yZSBjb25mdXNlZC4gVGhlIHNlY29uZCBzZW50ZW5jZSBzYXlzIHRoYXQg
eW91DQo8ZW0gY2xhc3M9IiI+YXJlIGFsbG93ZWQ8L2VtPiB0byBpbmNsdWRlIHRoZSBNT0JJTElU
WS1USUNLRVQgYXR0cmlidXRlIGluIGEgUmVmcmVzaCBSZXF1ZXN0IGlmIHlvdSB3YW50IHRvIHJl
dGFpbiB0aGUgYWxsb2NhdGlvbiwgZXZlbiB0aG91Z2ggdGhlIGZpcnN0IHNlbnRlbmNlIHNheXMg
eW91IE1VU1QgTk9ULiBJcyB0aGlzIGJlY2F1c2UgdGhlIFJlZnJlc2ggUmVxdWVzdCB3aXRoIHRo
ZSBNT0JJTElUWS1USUNLRVQgYXR0cmlidXRlIHdpbGwgb25seQ0KIGJlIHJlamVjdGVkIGlmIHRo
ZSBJUCBhZGRyZXNzIGlzIHRoZSBzYW1lPyBJZiBzbywgcGVyaGFwcyB0aGlzIGlzIHdoYXQgeW91
IG1lYW50OjwvcD4NCjxwcmUgc3R5bGU9ImJhY2tncm91bmQtY29sb3I6I0Y3RjdGNzsgYm9yZGVy
LXJhZGl1czo1cHggNXB4IDVweCA1cHg7IG1hcmdpbi1sZWZ0OjE1cHg7IG1hcmdpbi1yaWdodDox
NXB4OyBtYXgtd2lkdGg6OTB2dzsgb3ZlcmZsb3cteDphdXRvOyBwYWRkaW5nOjVweCIgYmdjb2xv
cj0iI0Y3RjdGNyIgY2xhc3M9IiI+PGNvZGUgc3R5bGU9ImJhY2tncm91bmQtY29sb3I6I0Y3RjdG
NzsgYm9yZGVyLXJhZGl1czozcHg7IG1hcmdpbjowOyBwYWRkaW5nOjAiIGJnY29sb3I9IiNGN0Y3
RjciIGNsYXNzPSIiPklmIGEgY2xpZW50IHdhbnRzIHRvIHJlZnJlc2ggYW4gZXhpc3RpbmcgYWxs
b2NhdGlvbiBhbmQgdXBkYXRlIGl0cw0KdGltZS10by1leHBpcnkgb3IgZGVsZXRlIGFuIGV4aXN0
aW5nIGFsbG9jYXRpb24sIGl0IHNlbmRzIGEgUmVmcmVzaA0KUmVxdWVzdCBhcyBkZXNjcmliZWQg
aW4gU2VjdGlvbiA3LjEgb2YgW1JGQzU3NjZdLiBJZiBJUCBhZGRyZXNzIG9mDQp0aGUgY2xpZW50
IGhhcyBjaGFuZ2VkIGFuZCB0aGUgY2xpZW50IHdhbnRzIHRvIHJldGFpbiB0aGUgZXhpc3RpbmcN
CmFsbG9jYXRpb24sIHRoZSBjbGllbnQgaW5jbHVkZXMgdGhlIE1PQklMSVRZLVRJQ0tFVCBhdHRy
aWJ1dGUNCnJlY2VpdmVkIGluIHRoZSBBbGxvY2F0ZSBTdWNjZXNzIHJlc3BvbnNlIGluIHRoZSBS
ZWZyZXNoIFJlcXVlc3QuIElmDQp0aGVyZSBoYXMgYmVlbiBubyBJUCBhZGRyZXNzIGNoYW5nZSwg
dGhlIGNsaWVudCBNVVNUIE5PVCBpbmNsdWRlIGENCk1PQklMSVRZLVRJQ0tFVCBhdHRyaWJ1dGUs
IGFzIHRoaXMgd2lsbCBiZSByZWplY3RlZCBieSB0aGUgc2VydmVyDQphbmQgdGhlIGNsaWVudCB3
b3VsZCBuZWVkIHRvIHJldHJhbnNtaXQgdGhlIFJlZnJlc2ggUmVxdWVzdC4NCjwvY29kZT48L3By
ZT4NCjxwIGRpcj0iYXV0byIgY2xhc3M9IiI+SWYgdGhhdCdzIG5vdCB3aGF0IHlvdSBtZWFudCwg
eW91IHNob3VsZCBwcm9iYWJseSBjbGFyaWZ5LjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KVG8gYmUgcHJlY2lzZSwg4oCcSVAgYWRkcmVzc+KAnSBo
ZXJlIHNob3VsZCBiZSDigJxJUCBhZGRyZXNzIG9yIHNvdXJjZSBwb3J04oCdLCByaWdodD8gJm5i
c3A7T25lIGNhc2UgSeKAmW0gdGhpbmtpbmcgb2YgaXMgd2hlcmUgYSBjbGllbnQgbW92ZWQgdG8g
YSBuZXcgcHJpdmF0ZSBJUCBhZGRyZXNzLCBidXQgaXMgc3RpbGwgYmVoaW5kIHRoZSBzYW1lIENH
TiBhbmQgc28gaGFzIHRoZSBzYW1lIGV4dGVybmFsIElQIGFkZHJlc3MuPC9kaXY+DQo8L2JvZHk+
DQo8L2h0bWw+DQo=

--_000_2DC7E1A2D2AD472CBE71976757246209vidyocom_--


From nobody Fri Sep  9 21:39:38 2016
Return-Path: <tireddy@cisco.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 701A612B31F; Fri,  9 Sep 2016 21:39:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.028
X-Spam-Level: 
X-Spam-Status: No, score=-16.028 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 1AsQhcVRGQOU; Fri,  9 Sep 2016 21:39:30 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 023DD12B15F; Fri,  9 Sep 2016 21:39:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13434; q=dns/txt; s=iport; t=1473482370; x=1474691970; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=u4WszooPUqkPbJSRs51OnAhCnMEfB3c4m4QYq0+sXJo=; b=mAN7jIqSmnXftoDsibrpIYKIwqAaLaGzsBJShrH8alO7DZbJbFjpGQAc 9FtPDI2D+HoQOWDxQmiwMzDx9v5KzuA6KYLAJkAzT8Qin/H2r0WlFl82J suqID+lNUkkDcvNHw9SCRRvGb8w53NhsdxwCrm88BVxlSBcQsOb1LJ87M 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CKAQDMjdNX/5ldJa1bAxYDAQEBAQEBA?= =?us-ascii?q?QEBAQGCejMBAQEBAR5XfAeNLKYJhQ2CAyCFfQKBTDgUAQIBAQEBAQEBXieEYQE?= =?us-ascii?q?BAQQtTBACAQgOAwQBASgHMhQJCAIEAQ0FCIhCDsELAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBHIYwhE+EKgYxFRGFFQWIPYcohC2FUAGPQYF1hGCHb4ElhneFXoN6AR4?= =?us-ascii?q?2gjkOghNwhScHgSh/AQEB?=
X-IronPort-AV: E=Sophos;i="5.30,308,1470700800";  d="scan'208,217";a="145615320"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Sep 2016 04:39:28 +0000
Received: from XCH-ALN-016.cisco.com (xch-aln-016.cisco.com [173.36.7.26]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u8A4dSwS023803 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 10 Sep 2016 04:39:28 GMT
Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-ALN-016.cisco.com (173.36.7.26) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 9 Sep 2016 23:39:27 -0500
Received: from xch-rcd-017.cisco.com ([173.37.102.27]) by XCH-RCD-017.cisco.com ([173.37.102.27]) with mapi id 15.00.1210.000; Fri, 9 Sep 2016 23:39:27 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>
Thread-Topic: GenART post-telechat comment on draft-ietf-tram-turn-mobility-08
Thread-Index: AQHSCFiLm4+HgrE2lU6LKYpWnDFIuqBxq9KAgAB9LPA=
Date: Sat, 10 Sep 2016 04:39:27 +0000
Message-ID: <d53f66f6ba43488eb69c89fa16c102f5@XCH-RCD-017.cisco.com>
References: <6ECD9A3A-0D63-421B-953D-A516D773CCBA@qti.qualcomm.com> <E87B771635882B4BA20096B589152EF643E961F1@eusaamb107.ericsson.se> <092F2B7C-4B03-4956-9C0E-1C5983D2AF72@qti.qualcomm.com> <abf54eff0f4c4d28b45db8e185e5e5c2@XCH-RCD-017.cisco.com> <E87B771635882B4BA20096B589152EF643E99AAA@eusaamb107.ericsson.se> <B4CE5A5C-3DB0-4B4B-86B9-B7AF02F7DB76@qti.qualcomm.com>
In-Reply-To: <B4CE5A5C-3DB0-4B4B-86B9-B7AF02F7DB76@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.72.6]
Content-Type: multipart/alternative; boundary="_000_d53f66f6ba43488eb69c89fa16c102f5XCHRCD017ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/KgEhohVvDOWv4qYUGxowBupH0p0>
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-tram-turn-mobility.all@ietf.org" <draft-ietf-tram-turn-mobility.all@ietf.org>, IESG <iesg@ietf.org>, "tram@ietf.org" <tram@ietf.org>
Subject: Re: [tram] GenART post-telechat comment on draft-ietf-tram-turn-mobility-08
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 10 Sep 2016 04:39:32 -0000

--_000_d53f66f6ba43488eb69c89fa16c102f5XCHRCD017ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

From: Pete Resnick [mailto:presnick@qti.qualcomm.com]
Sent: Friday, September 9, 2016 9:38 PM
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Cc: Tirumaleswar Reddy (tireddy) <tireddy@cisco.com>; IESG <iesg@ietf.org>;=
 General Area Review Team <gen-art@ietf.org>; draft-ietf-tram-turn-mobility=
.all@ietf.org; tram@ietf.org
Subject: Re: GenART post-telechat comment on draft-ietf-tram-turn-mobility-=
08


On 9 Sep 2016, at 4:33, Suresh Krishnan wrote:
Hi Tiru,
On 09/07/2016 10:50 PM, Tirumaleswar Reddy (tireddy) wrote:
[TR] I propose the following text to avoid the confusion:
If a client wants to refresh an existing allocation and update its
time-to-expiry or delete an existing allocation in case of no IP address
change, it will send a
Refresh Request as described in Section 7.1 of [RFC5766] and MUST NOT
include a MOBILITY-TICKET attribute. If the client wants to retain
the existing allocation in case of IP address change, it will include the
MOBILITY-TICKET attribute received in the Allocate Success response
in the Refresh Request.
I have no issues with this new text. Please check with Pete if it resolves
his concerns.

Wait, now I'm even more confused. The second sentence says that you are all=
owed to include the MOBILITY-TICKET attribute in a Refresh Request if you w=
ant to retain the allocation, even though the first sentence says you MUST =
NOT. Is this because the Refresh Request with the MOBILITY-TICKET attribute=
 will only be rejected if the IP address is the same? If so, perhaps this i=
s what you meant:

If a client wants to refresh an existing allocation and update its

time-to-expiry or delete an existing allocation, it sends a Refresh

Request as described in Section 7.1 of [RFC5766]. If IP address of

the client has changed and the client wants to retain the existing

allocation, the client includes the MOBILITY-TICKET attribute

received in the Allocate Success response in the Refresh Request. If

there has been no IP address change, the client MUST NOT include a

MOBILITY-TICKET attribute, as this will be rejected by the server

and the client would need to retransmit the Refresh Request.

If that's not what you meant, you should probably clarify.

[TR] Thanks, Looks good, will add at the end of the last line "without a MO=
BILITY-TICKET attribute".

-Tiru





pr
--
Pete Resnick http://www.qualcomm.com/~presnick/<http://www.qualcomm.com/%7E=
presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478

--_000_d53f66f6ba43488eb69c89fa16c102f5XCHRCD017ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-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=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (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:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	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
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
code
	{mso-style-priority:99;
	font-family:"Courier New";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> Pete Resnick [mailto:presnick@=
qti.qualcomm.com]
<br>
<b>Sent:</b> Friday, September 9, 2016 9:38 PM<br>
<b>To:</b> Suresh Krishnan &lt;suresh.krishnan@ericsson.com&gt;<br>
<b>Cc:</b> Tirumaleswar Reddy (tireddy) &lt;tireddy@cisco.com&gt;; IESG &lt=
;iesg@ietf.org&gt;; General Area Review Team &lt;gen-art@ietf.org&gt;; draf=
t-ietf-tram-turn-mobility.all@ietf.org; tram@ietf.org<br>
<b>Subject:</b> Re: GenART post-telechat comment on draft-ietf-tram-turn-mo=
bility-08<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">On 9 Sep 2016, =
at 4:33, Suresh Krishnan wrote:<o:p></o:p></span></p>
</div>
<div>
<blockquote style=3D"border:none;border-left:solid #777777 1.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:0in;margin-right:0in;margin-bottom:3.75pt">
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#777777">Hi Tiru,
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#777777">On 09/07/2016 10:50 PM, Tirumaleswar Reddy (tireddy) wro=
te:
<o:p></o:p></span></p>
</div>
<blockquote style=3D"border:none;border-left:solid #999999 1.5pt;padding:0i=
n 0in 0in 4.0pt;margin-left:0in;margin-right:0in;margin-bottom:3.75pt">
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#999999">[TR] I propose the following text to avoid the confusion=
:
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#999999">If a client wants to refresh an existing allocation and =
update its
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#999999">time-to-expiry or delete an existing allocation in case =
of no IP address
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#999999">change, it will send a
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#999999">Refresh Request as described in Section 7.1 of [RFC5766]=
 and MUST NOT
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#999999">include a MOBILITY-TICKET attribute. If the client wants=
 to retain
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#999999">the existing allocation in case of IP address change, it=
 will include the
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#999999">MOBILITY-TICKET attribute received in the Allocate Succe=
ss response
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#999999">in the Refresh Request.
<o:p></o:p></span></p>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#777777">I have no issues with this new text. Please check with P=
ete if it resolves
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#777777">his concerns.
<o:p></o:p></span></p>
</div>
</blockquote>
</div>
<div>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">Wait, now I'm e=
ven more confused. The second sentence says that you
<em><span style=3D"font-family:&quot;Arial&quot;,sans-serif">are allowed</s=
pan></em> to include the MOBILITY-TICKET attribute in a Refresh Request if =
you want to retain the allocation, even though the first sentence says you =
MUST NOT. Is this because the Refresh Request
 with the MOBILITY-TICKET attribute will only be rejected if the IP address=
 is the same? If so, perhaps this is what you meant:<o:p></o:p></span></p>
<pre style=3D"mso-margin-top-alt:0in;margin-right:11.25pt;margin-bottom:0in=
;margin-left:11.25pt;margin-bottom:.0001pt;background:#F7F7F7;border-radius=
:5px 5px 5px 5px;max-width:90vw;overflow-x:auto"><code><span style=3D"backg=
round:#F7F7F7">If a client wants to refresh an existing allocation and upda=
te its<o:p></o:p></span></code></pre>
<pre style=3D"mso-margin-top-alt:0in;margin-right:11.25pt;margin-bottom:0in=
;margin-left:11.25pt;margin-bottom:.0001pt;background:#F7F7F7"><code><span =
style=3D"background:#F7F7F7">time-to-expiry or delete an existing allocatio=
n, it sends a Refresh<o:p></o:p></span></code></pre>
<pre style=3D"mso-margin-top-alt:0in;margin-right:11.25pt;margin-bottom:0in=
;margin-left:11.25pt;margin-bottom:.0001pt;background:#F7F7F7"><code><span =
style=3D"background:#F7F7F7">Request as described in Section 7.1 of [RFC576=
6]. If IP address of<o:p></o:p></span></code></pre>
<pre style=3D"mso-margin-top-alt:0in;margin-right:11.25pt;margin-bottom:0in=
;margin-left:11.25pt;margin-bottom:.0001pt;background:#F7F7F7"><code><span =
style=3D"background:#F7F7F7">the client has changed and the client wants to=
 retain the existing<o:p></o:p></span></code></pre>
<pre style=3D"mso-margin-top-alt:0in;margin-right:11.25pt;margin-bottom:0in=
;margin-left:11.25pt;margin-bottom:.0001pt;background:#F7F7F7"><code><span =
style=3D"background:#F7F7F7">allocation, the client includes the MOBILITY-T=
ICKET attribute<o:p></o:p></span></code></pre>
<pre style=3D"mso-margin-top-alt:0in;margin-right:11.25pt;margin-bottom:0in=
;margin-left:11.25pt;margin-bottom:.0001pt;background:#F7F7F7"><code><span =
style=3D"background:#F7F7F7">received in the Allocate Success response in t=
he Refresh Request. If<o:p></o:p></span></code></pre>
<pre style=3D"mso-margin-top-alt:0in;margin-right:11.25pt;margin-bottom:0in=
;margin-left:11.25pt;margin-bottom:.0001pt;background:#F7F7F7"><code><span =
style=3D"background:#F7F7F7">there has been no IP address change, the clien=
t MUST NOT include a<o:p></o:p></span></code></pre>
<pre style=3D"mso-margin-top-alt:0in;margin-right:11.25pt;margin-bottom:0in=
;margin-left:11.25pt;margin-bottom:.0001pt;background:#F7F7F7"><code><span =
style=3D"background:#F7F7F7">MOBILITY-TICKET attribute, as this will be rej=
ected by the server<o:p></o:p></span></code></pre>
<pre style=3D"mso-margin-top-alt:0in;margin-right:11.25pt;margin-bottom:0in=
;margin-left:11.25pt;margin-bottom:.0001pt;background:#F7F7F7"><code><span =
style=3D"background:#F7F7F7">and the client would need to retransmit the Re=
fresh Request.<o:p></o:p></span></code></pre>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">If that's not w=
hat you meant, you should probably clarify.<o:p></o:p></span></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-ser=
if;color:#1F497D">[TR] Thanks, Looks good, will add at the end of the last =
line &#8220;without a MOBILITY-TICKET attribute&#8221;.<o:p></o:p></span></=
p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-ser=
if;color:#1F497D">-Tiru<o:p></o:p></span></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-ser=
if;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-ser=
if;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p><span style=3D"font-family:&quot;Arial&quot;,sans-serif">pr<br>
-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/"><span style=
=3D"color:#3983C4">http://www.qualcomm.com/~presnick/</span></a><br>
Qualcomm Technologies, Inc. - &#43;1 (858)651-4478<o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>

--_000_d53f66f6ba43488eb69c89fa16c102f5XCHRCD017ciscocom_--


From nobody Fri Sep  9 21:40:26 2016
Return-Path: <tireddy@cisco.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 9C57112B31F; Fri,  9 Sep 2016 21:40:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.028
X-Spam-Level: 
X-Spam-Status: No, score=-16.028 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 o8SCp7qNOvqj; Fri,  9 Sep 2016 21:40:14 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8844112B15F; Fri,  9 Sep 2016 21:40:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18998; q=dns/txt; s=iport; t=1473482414; x=1474692014; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=BaanQxBTD5LBaCKTwKDj3JA2k78S0BzCDc3TIQjKAUM=; b=QdFe0vA0pNE7tFaxrVfFQ/UU1kVY5FoMXchosVMUROMUVvsdi3MqykRw JKRjuEc/PNajHOeUYnyTKPEIpTL1D0kFmLb6pJ9LEo+5xlb5kUNh6m+Al cY7NpLm7/pC5mAJYKTRpoJ97trPoviRiPAQis7wbaaLrtwMeuekdLW2eY A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CKAQCBjdNX/5pdJa1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBgnozAQEBAQEeV3wHjSymCYUNggOGHQIcgTA4FAECAQEBAQEBAV4nhGEBAQE?= =?us-ascii?q?EIwpMEAIBCBEEAQEoAwICAjAUCQgCBAENBQiIQrRpjC8BAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEchjCET4QqBicfgkyCWgWIPYcohC2FUAGPQYF1hGCHb4ElhneFXoN?= =?us-ascii?q?6AR42gkeCE3CFJweBKH8BAQE?=
X-IronPort-AV: E=Sophos;i="5.30,308,1470700800";  d="scan'208,217";a="147424068"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Sep 2016 04:40:13 +0000
Received: from XCH-RCD-020.cisco.com (xch-rcd-020.cisco.com [173.37.102.30]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u8A4eD3R013686 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 10 Sep 2016 04:40:13 GMT
Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-RCD-020.cisco.com (173.37.102.30) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 9 Sep 2016 23:40:12 -0500
Received: from xch-rcd-017.cisco.com ([173.37.102.27]) by XCH-RCD-017.cisco.com ([173.37.102.27]) with mapi id 15.00.1210.000; Fri, 9 Sep 2016 23:40:12 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Jonathan Lennox <jonathan@vidyo.com>, Pete Resnick <presnick@qti.qualcomm.com>
Thread-Topic: [tram] GenART post-telechat comment on draft-ietf-tram-turn-mobility-08
Thread-Index: AQHSCsbDNOMPtl5/PEWoATQWm+2sR6ByJRJA
Date: Sat, 10 Sep 2016 04:40:12 +0000
Message-ID: <f2e1d00259594bd8b25b97338776deed@XCH-RCD-017.cisco.com>
References: <6ECD9A3A-0D63-421B-953D-A516D773CCBA@qti.qualcomm.com> <E87B771635882B4BA20096B589152EF643E961F1@eusaamb107.ericsson.se> <092F2B7C-4B03-4956-9C0E-1C5983D2AF72@qti.qualcomm.com> <abf54eff0f4c4d28b45db8e185e5e5c2@XCH-RCD-017.cisco.com> <E87B771635882B4BA20096B589152EF643E99AAA@eusaamb107.ericsson.se> <B4CE5A5C-3DB0-4B4B-86B9-B7AF02F7DB76@qti.qualcomm.com> <2DC7E1A2-D2AD-472C-BE71-976757246209@vidyo.com>
In-Reply-To: <2DC7E1A2-D2AD-472C-BE71-976757246209@vidyo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.72.6]
Content-Type: multipart/alternative; boundary="_000_f2e1d00259594bd8b25b97338776deedXCHRCD017ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/XtbR9j6xQG2CPJdcuWoS0L1UIeA>
Cc: "tram@ietf.org" <tram@ietf.org>, General Area Review Team <gen-art@ietf.org>, "draft-ietf-tram-turn-mobility.all@ietf.org" <draft-ietf-tram-turn-mobility.all@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>, The The IESG <iesg@ietf.org>
Subject: Re: [tram] GenART post-telechat comment on draft-ietf-tram-turn-mobility-08
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 10 Sep 2016 04:40:16 -0000

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

RnJvbTogSm9uYXRoYW4gTGVubm94IFttYWlsdG86am9uYXRoYW5AdmlkeW8uY29tXQ0KU2VudDog
RnJpZGF5LCBTZXB0ZW1iZXIgOSwgMjAxNiAxMTo1MCBQTQ0KVG86IFBldGUgUmVzbmljayA8cHJl
c25pY2tAcXRpLnF1YWxjb21tLmNvbT4NCkNjOiBTdXJlc2ggS3Jpc2huYW4gPHN1cmVzaC5rcmlz
aG5hbkBlcmljc3Nvbi5jb20+OyBHZW5lcmFsIEFyZWEgUmV2aWV3IFRlYW0gPGdlbi1hcnRAaWV0
Zi5vcmc+OyBkcmFmdC1pZXRmLXRyYW0tdHVybi1tb2JpbGl0eS5hbGxAaWV0Zi5vcmc7IFRoZSBU
aGUgSUVTRyA8aWVzZ0BpZXRmLm9yZz47IFRpcnVtYWxlc3dhciBSZWRkeSAodGlyZWRkeSkgPHRp
cmVkZHlAY2lzY28uY29tPjsgdHJhbUBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFt0cmFtXSBHZW5B
UlQgcG9zdC10ZWxlY2hhdCBjb21tZW50IG9uIGRyYWZ0LWlldGYtdHJhbS10dXJuLW1vYmlsaXR5
LTA4DQoNCg0KT24gU2VwIDksIDIwMTYsIGF0IDEyOjA4IFBNLCBQZXRlIFJlc25pY2sgPHByZXNu
aWNrQHF0aS5xdWFsY29tbS5jb208bWFpbHRvOnByZXNuaWNrQHF0aS5xdWFsY29tbS5jb20+PiB3
cm90ZToNCg0KT24gOSBTZXAgMjAxNiwgYXQgNDozMywgU3VyZXNoIEtyaXNobmFuIHdyb3RlOg0K
DQpIaSBUaXJ1LA0KT24gMDkvMDcvMjAxNiAxMDo1MCBQTSwgVGlydW1hbGVzd2FyIFJlZGR5ICh0
aXJlZGR5KSB3cm90ZToNCltUUl0gSSBwcm9wb3NlIHRoZSBmb2xsb3dpbmcgdGV4dCB0byBhdm9p
ZCB0aGUgY29uZnVzaW9uOg0KSWYgYSBjbGllbnQgd2FudHMgdG8gcmVmcmVzaCBhbiBleGlzdGlu
ZyBhbGxvY2F0aW9uIGFuZCB1cGRhdGUgaXRzDQp0aW1lLXRvLWV4cGlyeSBvciBkZWxldGUgYW4g
ZXhpc3RpbmcgYWxsb2NhdGlvbiBpbiBjYXNlIG9mIG5vIElQIGFkZHJlc3MNCmNoYW5nZSwgaXQg
d2lsbCBzZW5kIGENClJlZnJlc2ggUmVxdWVzdCBhcyBkZXNjcmliZWQgaW4gU2VjdGlvbiA3LjEg
b2YgW1JGQzU3NjZdIGFuZCBNVVNUIE5PVA0KaW5jbHVkZSBhIE1PQklMSVRZLVRJQ0tFVCBhdHRy
aWJ1dGUuIElmIHRoZSBjbGllbnQgd2FudHMgdG8gcmV0YWluDQp0aGUgZXhpc3RpbmcgYWxsb2Nh
dGlvbiBpbiBjYXNlIG9mIElQIGFkZHJlc3MgY2hhbmdlLCBpdCB3aWxsIGluY2x1ZGUgdGhlDQpN
T0JJTElUWS1USUNLRVQgYXR0cmlidXRlIHJlY2VpdmVkIGluIHRoZSBBbGxvY2F0ZSBTdWNjZXNz
IHJlc3BvbnNlDQppbiB0aGUgUmVmcmVzaCBSZXF1ZXN0Lg0KSSBoYXZlIG5vIGlzc3VlcyB3aXRo
IHRoaXMgbmV3IHRleHQuIFBsZWFzZSBjaGVjayB3aXRoIFBldGUgaWYgaXQgcmVzb2x2ZXMNCmhp
cyBjb25jZXJucy4NCldhaXQsIG5vdyBJJ20gZXZlbiBtb3JlIGNvbmZ1c2VkLiBUaGUgc2Vjb25k
IHNlbnRlbmNlIHNheXMgdGhhdCB5b3UgYXJlIGFsbG93ZWQgdG8gaW5jbHVkZSB0aGUgTU9CSUxJ
VFktVElDS0VUIGF0dHJpYnV0ZSBpbiBhIFJlZnJlc2ggUmVxdWVzdCBpZiB5b3Ugd2FudCB0byBy
ZXRhaW4gdGhlIGFsbG9jYXRpb24sIGV2ZW4gdGhvdWdoIHRoZSBmaXJzdCBzZW50ZW5jZSBzYXlz
IHlvdSBNVVNUIE5PVC4gSXMgdGhpcyBiZWNhdXNlIHRoZSBSZWZyZXNoIFJlcXVlc3Qgd2l0aCB0
aGUgTU9CSUxJVFktVElDS0VUIGF0dHJpYnV0ZSB3aWxsIG9ubHkgYmUgcmVqZWN0ZWQgaWYgdGhl
IElQIGFkZHJlc3MgaXMgdGhlIHNhbWU/IElmIHNvLCBwZXJoYXBzIHRoaXMgaXMgd2hhdCB5b3Ug
bWVhbnQ6DQoNCklmIGEgY2xpZW50IHdhbnRzIHRvIHJlZnJlc2ggYW4gZXhpc3RpbmcgYWxsb2Nh
dGlvbiBhbmQgdXBkYXRlIGl0cw0KDQp0aW1lLXRvLWV4cGlyeSBvciBkZWxldGUgYW4gZXhpc3Rp
bmcgYWxsb2NhdGlvbiwgaXQgc2VuZHMgYSBSZWZyZXNoDQoNClJlcXVlc3QgYXMgZGVzY3JpYmVk
IGluIFNlY3Rpb24gNy4xIG9mIFtSRkM1NzY2XS4gSWYgSVAgYWRkcmVzcyBvZg0KDQp0aGUgY2xp
ZW50IGhhcyBjaGFuZ2VkIGFuZCB0aGUgY2xpZW50IHdhbnRzIHRvIHJldGFpbiB0aGUgZXhpc3Rp
bmcNCg0KYWxsb2NhdGlvbiwgdGhlIGNsaWVudCBpbmNsdWRlcyB0aGUgTU9CSUxJVFktVElDS0VU
IGF0dHJpYnV0ZQ0KDQpyZWNlaXZlZCBpbiB0aGUgQWxsb2NhdGUgU3VjY2VzcyByZXNwb25zZSBp
biB0aGUgUmVmcmVzaCBSZXF1ZXN0LiBJZg0KDQp0aGVyZSBoYXMgYmVlbiBubyBJUCBhZGRyZXNz
IGNoYW5nZSwgdGhlIGNsaWVudCBNVVNUIE5PVCBpbmNsdWRlIGENCg0KTU9CSUxJVFktVElDS0VU
IGF0dHJpYnV0ZSwgYXMgdGhpcyB3aWxsIGJlIHJlamVjdGVkIGJ5IHRoZSBzZXJ2ZXINCg0KYW5k
IHRoZSBjbGllbnQgd291bGQgbmVlZCB0byByZXRyYW5zbWl0IHRoZSBSZWZyZXNoIFJlcXVlc3Qu
DQpJZiB0aGF0J3Mgbm90IHdoYXQgeW91IG1lYW50LCB5b3Ugc2hvdWxkIHByb2JhYmx5IGNsYXJp
ZnkuDQpUbyBiZSBwcmVjaXNlLCDigJxJUCBhZGRyZXNz4oCdIGhlcmUgc2hvdWxkIGJlIOKAnElQ
IGFkZHJlc3Mgb3Igc291cmNlIHBvcnTigJ0sIHJpZ2h0Pw0KDQpbVFJdIFl1cCwgd2lsbCB1cGRh
dGUuDQoNCi1UaXJ1DQoNCk9uZSBjYXNlIEnigJltIHRoaW5raW5nIG9mIGlzIHdoZXJlIGEgY2xp
ZW50IG1vdmVkIHRvIGEgbmV3IHByaXZhdGUgSVAgYWRkcmVzcywgYnV0IGlzIHN0aWxsIGJlaGlu
ZCB0aGUgc2FtZSBDR04gYW5kIHNvIGhhcyB0aGUgc2FtZSBleHRlcm5hbCBJUCBhZGRyZXNzLg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDEx
IDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcg
Um9tYW4iLHNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmNvZGUN
Cgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0K
cHJlDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiSFRNTCBQcmVm
b3JtYXR0ZWQgQ2hhciI7DQoJbWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCnAubXNvbm9y
bWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25vcm1hbDANCgl7bXNvLXN0eWxlLW5hbWU6bXNv
bm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowaW47DQoJ
bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGluOw0KCWZvbnQtc2l6
ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsc2VyaWY7fQ0Kc3Bhbi5I
VE1MUHJlZm9ybWF0dGVkQ2hhcg0KCXttc28tc3R5bGUtbmFtZToiSFRNTCBQcmVmb3JtYXR0ZWQg
Q2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFBy
ZWZvcm1hdHRlZCI7DQoJZm9udC1mYW1pbHk6Q29uc29sYXM7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjIN
Cgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmki
LHNhbnMtc2VyaWY7DQoJY29sb3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5
bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0
aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4w
aW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxl
PjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIg
c3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48
eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQi
IGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+
DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNs
YXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmIj5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj4gSm9uYXRoYW4gTGVubm94IFtt
YWlsdG86am9uYXRoYW5AdmlkeW8uY29tXQ0KPGJyPg0KPGI+U2VudDo8L2I+IEZyaWRheSwgU2Vw
dGVtYmVyIDksIDIwMTYgMTE6NTAgUE08YnI+DQo8Yj5Ubzo8L2I+IFBldGUgUmVzbmljayAmbHQ7
cHJlc25pY2tAcXRpLnF1YWxjb21tLmNvbSZndDs8YnI+DQo8Yj5DYzo8L2I+IFN1cmVzaCBLcmlz
aG5hbiAmbHQ7c3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbSZndDs7IEdlbmVyYWwgQXJlYSBS
ZXZpZXcgVGVhbSAmbHQ7Z2VuLWFydEBpZXRmLm9yZyZndDs7IGRyYWZ0LWlldGYtdHJhbS10dXJu
LW1vYmlsaXR5LmFsbEBpZXRmLm9yZzsgVGhlIFRoZSBJRVNHICZsdDtpZXNnQGlldGYub3JnJmd0
OzsgVGlydW1hbGVzd2FyIFJlZGR5ICh0aXJlZGR5KSAmbHQ7dGlyZWRkeUBjaXNjby5jb20mZ3Q7
OyB0cmFtQGlldGYub3JnPGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbdHJhbV0gR2VuQVJUIHBv
c3QtdGVsZWNoYXQgY29tbWVudCBvbiBkcmFmdC1pZXRmLXRyYW0tdHVybi1tb2JpbGl0eS0wODxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2
Pg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBw
dCI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gU2VwIDksIDIwMTYsIGF0IDEyOjA4
IFBNLCBQZXRlIFJlc25pY2sgJmx0OzxhIGhyZWY9Im1haWx0bzpwcmVzbmlja0BxdGkucXVhbGNv
bW0uY29tIj5wcmVzbmlja0BxdGkucXVhbGNvbW0uY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNw
YW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPk9uIDkg
U2VwIDIwMTYsIGF0IDQ6MzMsIFN1cmVzaCBLcmlzaG5hbiB3cm90ZTo8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFt
aWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpu
b25lO2JvcmRlci1sZWZ0OnNvbGlkICM3Nzc3NzcgMS41cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0
LjBwdDttYXJnaW4tbGVmdDowaW47bWFyZ2luLXJpZ2h0OjBpbjttYXJnaW4tYm90dG9tOjMuNzVw
dCI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3Nzc3NyI+SGkgVGlydSwNCjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOiM3Nzc3NzciPk9uIDA5LzA3LzIwMTYgMTA6NTAgUE0sIFRpcnVtYWxlc3dhciBSZWRkeSAo
dGlyZWRkeSkgd3JvdGU6DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxibG9ja3F1
b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjOTk5OTk5IDEuNXB0O3Bh
ZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQ7bWFyZ2luLWxlZnQ6MGluO21hcmdpbi1yaWdodDowaW47
bWFyZ2luLWJvdHRvbTozLjc1cHQiPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiM5
OTk5OTkiPltUUl0gSSBwcm9wb3NlIHRoZSBmb2xsb3dpbmcgdGV4dCB0byBhdm9pZCB0aGUgY29u
ZnVzaW9uOg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNh
bnMtc2VyaWY7Y29sb3I6Izk5OTk5OSI+SWYgYSBjbGllbnQgd2FudHMgdG8gcmVmcmVzaCBhbiBl
eGlzdGluZyBhbGxvY2F0aW9uIGFuZCB1cGRhdGUgaXRzDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1m
YW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojOTk5OTk5Ij50aW1lLXRv
LWV4cGlyeSBvciBkZWxldGUgYW4gZXhpc3RpbmcgYWxsb2NhdGlvbiBpbiBjYXNlIG9mIG5vIElQ
IGFkZHJlc3MNCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90Oyxz
YW5zLXNlcmlmO2NvbG9yOiM5OTk5OTkiPmNoYW5nZSwgaXQgd2lsbCBzZW5kIGENCjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiM5
OTk5OTkiPlJlZnJlc2ggUmVxdWVzdCBhcyBkZXNjcmliZWQgaW4gU2VjdGlvbiA3LjEgb2YgW1JG
QzU3NjZdIGFuZCBNVVNUIE5PVA0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0Fy
aWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izk5OTk5OSI+aW5jbHVkZSBhIE1PQklMSVRZLVRJ
Q0tFVCBhdHRyaWJ1dGUuIElmIHRoZSBjbGllbnQgd2FudHMgdG8gcmV0YWluDQo8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojOTk5
OTk5Ij50aGUgZXhpc3RpbmcgYWxsb2NhdGlvbiBpbiBjYXNlIG9mIElQIGFkZHJlc3MgY2hhbmdl
LCBpdCB3aWxsIGluY2x1ZGUgdGhlDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7
QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojOTk5OTk5Ij5NT0JJTElUWS1USUNLRVQgYXR0
cmlidXRlIHJlY2VpdmVkIGluIHRoZSBBbGxvY2F0ZSBTdWNjZXNzIHJlc3BvbnNlDQo8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjoj
OTk5OTk5Ij5pbiB0aGUgUmVmcmVzaCBSZXF1ZXN0Lg0KPG86cD48L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3
Nzc3NyI+SSBoYXZlIG5vIGlzc3VlcyB3aXRoIHRoaXMgbmV3IHRleHQuIFBsZWFzZSBjaGVjayB3
aXRoIFBldGUgaWYgaXQgcmVzb2x2ZXMNCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVv
dDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiM3Nzc3NzciPmhpcyBjb25jZXJucy4NCjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7
QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+V2FpdCwgbm93IEknbSBldmVuIG1vcmUgY29uZnVzZWQu
IFRoZSBzZWNvbmQgc2VudGVuY2Ugc2F5cyB0aGF0IHlvdQ0KPGVtPjxzcGFuIHN0eWxlPSJmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5hcmUgYWxsb3dlZDwvc3Bhbj48
L2VtPiB0byBpbmNsdWRlIHRoZSBNT0JJTElUWS1USUNLRVQgYXR0cmlidXRlIGluIGEgUmVmcmVz
aCBSZXF1ZXN0IGlmIHlvdSB3YW50IHRvIHJldGFpbiB0aGUgYWxsb2NhdGlvbiwgZXZlbiB0aG91
Z2ggdGhlIGZpcnN0IHNlbnRlbmNlIHNheXMgeW91IE1VU1QgTk9ULiBJcyB0aGlzIGJlY2F1c2Ug
dGhlIFJlZnJlc2ggUmVxdWVzdA0KIHdpdGggdGhlIE1PQklMSVRZLVRJQ0tFVCBhdHRyaWJ1dGUg
d2lsbCBvbmx5IGJlIHJlamVjdGVkIGlmIHRoZSBJUCBhZGRyZXNzIGlzIHRoZSBzYW1lPyBJZiBz
bywgcGVyaGFwcyB0aGlzIGlzIHdoYXQgeW91IG1lYW50OjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwcmUgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDowaW47bWFyZ2luLXJpZ2h0OjExLjI1cHQ7
bWFyZ2luLWJvdHRvbTowaW47bWFyZ2luLWxlZnQ6MTEuMjVwdDttYXJnaW4tYm90dG9tOi4wMDAx
cHQ7YmFja2dyb3VuZDojRjdGN0Y3O2JvcmRlci1yYWRpdXM6NXB4IDVweCA1cHggNXB4O21heC13
aWR0aDo5MHZ3O292ZXJmbG93LXg6YXV0byI+PGNvZGU+PHNwYW4gc3R5bGU9ImJhY2tncm91bmQ6
I0Y3RjdGNyI+SWYgYSBjbGllbnQgd2FudHMgdG8gcmVmcmVzaCBhbiBleGlzdGluZyBhbGxvY2F0
aW9uIGFuZCB1cGRhdGUgaXRzPG86cD48L286cD48L3NwYW4+PC9jb2RlPjwvcHJlPg0KPHByZSBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OjBpbjttYXJnaW4tcmlnaHQ6MTEuMjVwdDttYXJnaW4t
Ym90dG9tOjBpbjttYXJnaW4tbGVmdDoxMS4yNXB0O21hcmdpbi1ib3R0b206LjAwMDFwdDtiYWNr
Z3JvdW5kOiNGN0Y3RjciPjxjb2RlPjxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5kOiNGN0Y3RjciPnRp
bWUtdG8tZXhwaXJ5IG9yIGRlbGV0ZSBhbiBleGlzdGluZyBhbGxvY2F0aW9uLCBpdCBzZW5kcyBh
IFJlZnJlc2g8bzpwPjwvbzpwPjwvc3Bhbj48L2NvZGU+PC9wcmU+DQo8cHJlIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6MGluO21hcmdpbi1yaWdodDoxMS4yNXB0O21hcmdpbi1ib3R0b206MGlu
O21hcmdpbi1sZWZ0OjExLjI1cHQ7bWFyZ2luLWJvdHRvbTouMDAwMXB0O2JhY2tncm91bmQ6I0Y3
RjdGNyI+PGNvZGU+PHNwYW4gc3R5bGU9ImJhY2tncm91bmQ6I0Y3RjdGNyI+UmVxdWVzdCBhcyBk
ZXNjcmliZWQgaW4gU2VjdGlvbiA3LjEgb2YgW1JGQzU3NjZdLiBJZiBJUCBhZGRyZXNzIG9mPG86
cD48L286cD48L3NwYW4+PC9jb2RlPjwvcHJlPg0KPHByZSBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OjBpbjttYXJnaW4tcmlnaHQ6MTEuMjVwdDttYXJnaW4tYm90dG9tOjBpbjttYXJnaW4tbGVm
dDoxMS4yNXB0O21hcmdpbi1ib3R0b206LjAwMDFwdDtiYWNrZ3JvdW5kOiNGN0Y3RjciPjxjb2Rl
PjxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5kOiNGN0Y3RjciPnRoZSBjbGllbnQgaGFzIGNoYW5nZWQg
YW5kIHRoZSBjbGllbnQgd2FudHMgdG8gcmV0YWluIHRoZSBleGlzdGluZzxvOnA+PC9vOnA+PC9z
cGFuPjwvY29kZT48L3ByZT4NCjxwcmUgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDowaW47bWFy
Z2luLXJpZ2h0OjExLjI1cHQ7bWFyZ2luLWJvdHRvbTowaW47bWFyZ2luLWxlZnQ6MTEuMjVwdDtt
YXJnaW4tYm90dG9tOi4wMDAxcHQ7YmFja2dyb3VuZDojRjdGN0Y3Ij48Y29kZT48c3BhbiBzdHls
ZT0iYmFja2dyb3VuZDojRjdGN0Y3Ij5hbGxvY2F0aW9uLCB0aGUgY2xpZW50IGluY2x1ZGVzIHRo
ZSBNT0JJTElUWS1USUNLRVQgYXR0cmlidXRlPG86cD48L286cD48L3NwYW4+PC9jb2RlPjwvcHJl
Pg0KPHByZSBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OjBpbjttYXJnaW4tcmlnaHQ6MTEuMjVw
dDttYXJnaW4tYm90dG9tOjBpbjttYXJnaW4tbGVmdDoxMS4yNXB0O21hcmdpbi1ib3R0b206LjAw
MDFwdDtiYWNrZ3JvdW5kOiNGN0Y3RjciPjxjb2RlPjxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5kOiNG
N0Y3RjciPnJlY2VpdmVkIGluIHRoZSBBbGxvY2F0ZSBTdWNjZXNzIHJlc3BvbnNlIGluIHRoZSBS
ZWZyZXNoIFJlcXVlc3QuIElmPG86cD48L286cD48L3NwYW4+PC9jb2RlPjwvcHJlPg0KPHByZSBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OjBpbjttYXJnaW4tcmlnaHQ6MTEuMjVwdDttYXJnaW4t
Ym90dG9tOjBpbjttYXJnaW4tbGVmdDoxMS4yNXB0O21hcmdpbi1ib3R0b206LjAwMDFwdDtiYWNr
Z3JvdW5kOiNGN0Y3RjciPjxjb2RlPjxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5kOiNGN0Y3RjciPnRo
ZXJlIGhhcyBiZWVuIG5vIElQIGFkZHJlc3MgY2hhbmdlLCB0aGUgY2xpZW50IE1VU1QgTk9UIGlu
Y2x1ZGUgYTxvOnA+PC9vOnA+PC9zcGFuPjwvY29kZT48L3ByZT4NCjxwcmUgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDowaW47bWFyZ2luLXJpZ2h0OjExLjI1cHQ7bWFyZ2luLWJvdHRvbTowaW47
bWFyZ2luLWxlZnQ6MTEuMjVwdDttYXJnaW4tYm90dG9tOi4wMDAxcHQ7YmFja2dyb3VuZDojRjdG
N0Y3Ij48Y29kZT48c3BhbiBzdHlsZT0iYmFja2dyb3VuZDojRjdGN0Y3Ij5NT0JJTElUWS1USUNL
RVQgYXR0cmlidXRlLCBhcyB0aGlzIHdpbGwgYmUgcmVqZWN0ZWQgYnkgdGhlIHNlcnZlcjxvOnA+
PC9vOnA+PC9zcGFuPjwvY29kZT48L3ByZT4NCjxwcmUgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs
dDowaW47bWFyZ2luLXJpZ2h0OjExLjI1cHQ7bWFyZ2luLWJvdHRvbTowaW47bWFyZ2luLWxlZnQ6
MTEuMjVwdDttYXJnaW4tYm90dG9tOi4wMDAxcHQ7YmFja2dyb3VuZDojRjdGN0Y3Ij48Y29kZT48
c3BhbiBzdHlsZT0iYmFja2dyb3VuZDojRjdGN0Y3Ij5hbmQgdGhlIGNsaWVudCB3b3VsZCBuZWVk
IHRvIHJldHJhbnNtaXQgdGhlIFJlZnJlc2ggUmVxdWVzdC48bzpwPjwvbzpwPjwvc3Bhbj48L2Nv
ZGU+PC9wcmU+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LWZhbWls
eTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5JZiB0aGF0J3Mgbm90IHdoYXQgeW91IG1l
YW50LCB5b3Ugc2hvdWxkIHByb2JhYmx5IGNsYXJpZnkuPG86cD48L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5UbyBiZSBwcmVjaXNlLCDigJxJUCBhZGRyZXNz4oCdIGhlcmUgc2hvdWxkIGJl
IOKAnElQIGFkZHJlc3Mgb3Igc291cmNlIHBvcnTigJ0sIHJpZ2h0PyAmbmJzcDs8c3BhbiBzdHls
ZT0iY29sb3I6IzFGNDk3RCI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0
OTdEIj5bVFJdIFl1cCwgd2lsbCB1cGRhdGUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtj
b2xvcjojMUY0OTdEIj4tVGlydTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbmUgY2FzZSBJ4oCZbSB0aGlua2luZyBv
ZiBpcyB3aGVyZSBhIGNsaWVudCBtb3ZlZCB0byBhIG5ldyBwcml2YXRlIElQIGFkZHJlc3MsIGJ1
dCBpcyBzdGlsbCBiZWhpbmQgdGhlIHNhbWUgQ0dOIGFuZCBzbyBoYXMgdGhlIHNhbWUgZXh0ZXJu
YWwgSVAgYWRkcmVzcy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8
L2h0bWw+DQo=

--_000_f2e1d00259594bd8b25b97338776deedXCHRCD017ciscocom_--


From nobody Fri Sep  9 23:51:18 2016
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 B329612B00A; Fri,  9 Sep 2016 23:51:12 -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>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.32.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147349027272.30932.17139971714832753122.idtracker@ietfa.amsl.com>
Date: Fri, 09 Sep 2016 23:51:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/gjzuMl0xw3CekyqTzIUJQWzjW9o>
Cc: tram@ietf.org
Subject: [tram] I-D Action: draft-ietf-tram-turn-mobility-09.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 10 Sep 2016 06:51:13 -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 of the IETF.

        Title           : Mobility with TURN
        Authors         : Tirumaleswar Reddy
                          Dan Wing
                          Prashanth Patil
                          Paal-Erik Martinsen
	Filename        : draft-ietf-tram-turn-mobility-09.txt
	Pages           : 14
	Date            : 2016-09-09

Abstract:
   It is desirable to minimize traffic disruption caused by changing IP
   address during a mobility event.  One mechanism to minimize
   disruption is to expose a shorter network path to the mobility event
   so only the local network elements are aware of the changed IP
   address but the remote peer is unaware of the changed IP address.

   This draft provides such an IP address mobility solution using
   Traversal Using Relays around NAT (TURN).  This is achieved by
   allowing a client to retain an allocation on the TURN server when the
   IP address of the client changes.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-tram-turn-mobility-09

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


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 Sep 13 20:31:21 2016
Return-Path: <praspati@cisco.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 1DAF812B19E; Tue, 13 Sep 2016 20:31:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.029
X-Spam-Level: 
X-Spam-Status: No, score=-16.029 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 OKPi0-qaKsQX; Tue, 13 Sep 2016 20:31:12 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E99AE12B19C; Tue, 13 Sep 2016 20:31:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11110; q=dns/txt; s=iport; t=1473823871; x=1475033471; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=A5M/zTrgvKdVaiyj/6NS4xHP6rbKY1Zt9kNJioLDGUQ=; b=jDwB7UMtZvIx5kKE3Ctcee9+R3hzw6ll659AivsEx4VsJPFd57BNFsUJ qEVW6AHnhz9WQyzTo7bbZ/J2GGaj980Kcx227fxiIRGR30gi2XBW+Z9Hf D8mKQcSgIuFIRk6xBydBEGVejUt/ukBRgI60xRuscSwQnaJZAdjsyKQXi k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BKAQCew9hX/4QNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgzkBAQEBAR6BUweNLKkPgg+CA4YeAhyBKjgUAQIBAQEBAQEBXie?= =?us-ascii?q?EYgEBBDRFEAIBCBgEKAICMCUCBA4FiEqSM50cBow5AQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEdgQCFMIRPhB0KA4MSgmAFiDGFe4VnhVMBj1GBboRggzaFXoZ5hV+DegE?= =?us-ascii?q?eNoJ5FhiBN3CFIIEufwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.30,332,1470700800"; d="scan'208";a="323235529"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 14 Sep 2016 03:31:10 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id u8E3VALb006362 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 14 Sep 2016 03:31:10 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 13 Sep 2016 23:31:09 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Tue, 13 Sep 2016 23:31:09 -0400
From: "Prashanth Patil (praspati)" <praspati@cisco.com>
To: Ben Campbell <ben@nostrum.com>
Thread-Topic: Ben Campbell's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS and COMMENT)
Thread-Index: AQHSChJSaICpZPYmxkqQAN2wEDY0faB4KmsA
Date: Wed, 14 Sep 2016 03:31:09 +0000
Message-ID: <D3F834A3.132DD6%praspati@cisco.com>
References: <147269306853.31916.11958166980739260630.idtracker@ietfa.amsl.com> <D3EDF13E.13092C%praspati@cisco.com> <362B7B05-81DA-49D7-8452-9BA21F991D00@nostrum.com>
In-Reply-To: <362B7B05-81DA-49D7-8452-9BA21F991D00@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.8.160830
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.38.171]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <38883B3DA1B9F44C96724B9178682A47@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/y7lSb9kr8Ssj0aVO2nIDw7xD2KE>
Cc: "tram@ietf.org" <tram@ietf.org>, Simon Perreault <sperreault@jive.com>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, The IESG <iesg@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>
Subject: Re: [tram] Ben Campbell's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS and COMMENT)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 14 Sep 2016 03:31:15 -0000

SGkgQmVuLA0KDQpPbiA5LzgvMTYsIDE6NDggUE0sICJCZW4gQ2FtcGJlbGwiIDxiZW5Abm9zdHJ1
bS5jb20+IHdyb3RlOg0KDQo+SGksIHRoYW5rcyBmb3IgdGhlIHJlc3BvbnNlLiBTb21lIG1vcmUg
Y29tbWVudHMgaW5saW5lIChJIHJlbW92ZWQNCj5zZWN0aW9ucyB0aGF0IGRvIG5vdCBzZWVtIHRv
IG5lZWQgZnVydGhlciBkaXNjdXNzaW9uLikuDQo+DQo+VGhhbmtzIQ0KPg0KPkJlbi4NCj4NCj5P
biA3IFNlcCAyMDE2LCBhdCAyMjoyMiwgUHJhc2hhbnRoIFBhdGlsIChwcmFzcGF0aSkgd3JvdGU6
DQo+DQo+PiBIaSBCZW4sDQo+PiBBcG9sb2dpZXMgZm9yIHRoZSBkZWxheS4gUGxlYXNlIHNlZSBp
bmxpbmUuLg0KPj4NCj4+IE9uIDgvMzEvMTYsIDY6MjQgUE0sICJCZW4gQ2FtcGJlbGwiIDxiZW5A
bm9zdHJ1bS5jb20+IHdyb3RlOg0KPj4NCj4NCj5bLi4uXQ0KPg0KPj4NCj4+PiAtLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tDQo+Pj4gRElTQ1VTUzoNCj4+PiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+Pj4NCj4+PiAtOSwgZmlyc3Qg
cGFyYWdyYXBoIHNheXM6DQo+Pj4NCj4+PiAiVXNlIG9mIFNlc3Npb24gVHJhdmVyc2FsIFV0aWxp
dGllcyBmb3IgTkFUIChTVFVOKSBbUkZDNTM4OV0NCj4+PiAgIGF1dGhlbnRpY2F0aW9uIGlzIE9Q
VElPTkFMIGZvciBUVVJOIHNlcnZlcnMgcHJvdmlkZWQgYnkgdGhlIGxvY2FsDQo+Pj4gICBuZXR3
b3JrIG9yIGJ5IHRoZSBhY2Nlc3MgbmV0d29yay4gIEEgbmV0d29yayBwcm92aWRlZCBUVVJOIHNl
cnZlcg0KPj4+IE1BWQ0KPj4+ICAgYmUgY29uZmlndXJlZCB0byBhY2NlcHQgQWxsb2NhdGlvbiBy
ZXF1ZXN0cyB3aXRob3V0IFNUVU4NCj4+PiAgIGF1dGhlbnRpY2F0aW9uLCBhbmQgYSBUVVJOIGNs
aWVudCBNQVkgYmUgY29uZmlndXJlZCB0byBhY2NlcHQNCj4+PiAgIEFsbG9jYXRpb24gc3VjY2Vz
cyByZXNwb25zZXMgd2l0aG91dCBTVFVOIGF1dGhlbnRpY2F0aW9uIGZyb20gYQ0KPj4+ICAgbmV0
d29yayBwcm92aWRlZCBUVVJOIHNlcnZlci4gIg0KPj4+DQo+Pj4gVGhpcyBzZWVtcyB0byByZWxh
eCB0aGUgTVVTVCBsZXZlbCByZXF1aXJlbWVudCBpbiBSRkMgNTc2NiB0aGF0IHNheXMNCj4+PiBU
VVJODQo+Pj4gTVVTVCB1c2UgU1RVTiBsb25nLXRlcm0gY3JlZGVudGlhbCBhdXRoZW50aWNhdGlv
biwgb3IgdXNlIHNvbWUgb3RoZXINCj4+PiBlcXVhbGx5IHN0cm9uZyBtZWNoYW5pc20uIEZyb20g
YSBwdXJlbHkgcHJvY2VzcyBwZXJwZWN0aXZlLCB0aGlzDQo+Pj4gd291bGQNCj4+PiBlaXRoZXIg
cmVxdWlyZSBhbiB1cGRhdGUgdG8gNTc2Niwgb3IgaXQgd291bGQgcmVxdWlyZSBhbiBhcmd1bWVu
dA0KPj4+IHRoYXQNCj4+PiB0aGUgbG9jYWwvYWNjZXNzIG5ldHdvcmsgaXMgc29tZWhvdyBlcXVh
bGx5IHByb3RlY3RlZC4gSSB0aGluayB0aGUNCj4+PiBsYXR0ZXINCj4+PiB3b3VsZCBvbmx5IGJl
IHRydWUgaWYgdGhlIGFjY2VzcyBuZXR3b3JrIGhhcyBzb21lIHNvcnQgb2YgcHJvdGVjdGlvbg0K
Pj4+IGJleW9uZCBqdXN0IGJlaW5nIHRoZSBhY2Nlc3MgbmV0d29yayAoZS5nLiBhIHZwbiwgaXBz
ZWMsIG9yIHBoeXNpY2FsDQo+Pj4gaXNvbGF0aW9uLikgIEkgZG9uJ3QgcmVjYWxsIHNlZWluZyB0
ZXh0IHRoYXQgc3VnZ2VzdGVkIGFueSBvZiB0aG9zZS4NCj4+DQo+PiBUaXJ1IGFuZCBLYXRobGVl
biBoYXZlIGRpc2N1c3NlZCB0aGlzIGluIGFub3RoZXIgdGhyZWFkLiBXZSBpbnRlbmQgdG8NCj4+
IGFkZA0KPj4gdGV4dCBhcm91bmQgdGhlIGZvbGxvd2luZzoNCj4+DQo+PiAid2lsbCBhZGQgbW9y
ZSBkZXRhaWxzIHRoYXQgVFVSTiBzZXJ2ZXJzIGRlcGxveWVkIGluIERNWiBtdXN0IG9ubHkNCj4+
IHByb2Nlc3MNCj4+IFNUVU4gcmVxdWVzdHMgZnJvbSBhIHRydXN0ZWQgbmV0d29yayBhbmQgbm90
IGZyb20gZXh0ZXJuYWwgbmV0d29ya3MuDQo+PiBTaW1pbGFybHkgVFVSTiBzZXJ2ZXJzIGluIGFj
Y2VzcyBuZXR3b3JrcyBtdXN0IG9ubHkgcHJvY2VzcyBTVFVODQo+PiByZXF1ZXN0cw0KPj4gZnJv
bSBpdHMgc3Vic2NyaWJlcnMuIEFjY2VzcyBjb250cm9sIGNhbiBiZSBwcm92aWRlZCBieSBhY2Nl
c3MtY29udHJvbA0KPj4gbGlzdHMsIGZpcmV3YWxscyBhbmQvb3IgYnkgdXNlciBhdXRoZW50aWNh
dGlvbiB0byB0aGUgVFVSTiBzZXJ2ZXIuIFdlDQo+PiBjYW4NCj4+IGFsc28gZGlzY3VzcyBvdGhl
ciByZWNvbW1lbmRhdGlvbnMgbGlrZSBwZXItc3Vic2NyaWJlciBxdW90YSBsaW1pdCwNCj4+IGlu
Z3Jlc3MgZmlsdGVyaW5nLqn3DQo+Pg0KPj4gV291bGQgdGhpcyBhZGRyZXNzIHlvdXIgY29uY2Vy
bj8NCj4NCj5JdCBoZWxwcywgYnV0IGlmIEkgdW5kZXJzdGFuZCB0aGUgaW50ZW5kIGNvcnJlY3Rs
eSwgaXQgZG9lc24ndCBlbnRpcmVseQ0KPmFkZHJlc3MgbXkgY29uY2Vybi4NCj4NCj5UaGlzIGRy
YWZ0IHNlZW1zIHRvIHJlbGF4IHRoZSAiTVVTVCIgbGV2ZWwgcmVxdWlyZW1lbnQgdG8gdXNlIHN0
dW4NCj5hdXRoZW50aWNhdGlvbiAob3Igc29tZXRoaW5nIGVxdWFsbHkgc3Ryb25nKSB0byBhbiBl
ZmZlY3RpdmUgIk1BWSIsDQo+d2l0aG91dCBhbnkgcmVhbCBleHBsYW5hdGlvbiBvZiB3aHksIGFu
ZCB3aXRob3V0IHJlYWxseSBleHBsb3JpbmcgdGhlDQo+c2VjdXJpdHkgaW1wbGljYXRpb25zLiBE
byB5b3UgYXNzdW1lIHRoYXQgYSBUVVJOIHNlcnZlciB1c2VkIGluIHRoaXMNCj5jb250ZXh0IGlz
IHVzaW5nICJzb21ldGhpbmcgZXF1YWxseSBzdHJvbmciPyBBIG51bWJlciBvZiB0aGUgc2VjdXJp
dHkNCj5jb25zaWRlcmF0aW9ucyBpbiBSRkMgNTc2NiBhcmUgbWl0aWdhdGVkIGJ5IHRoZSBhc3N1
bXB0aW9uIG9mIHN0dW4NCj5hdXRoZW50aWNhdGlvbi4gSG93IGFyZSB0aGV5IGltcGFjdGVkIGJ5
IHRoaXMgcmVsYXhhdGlvbj8gRG9lcyB0aGUgbGFjaw0KPm9mIGF1dGhlbnRpY2F0aW9uIGxlYWQg
dG8gYSByaXNrIG9mIGFsbG9jYXRpb24taGlqYWNraW5nPyAoZXNwZWNpYWxseSBpZg0KPmNvbWJp
bmVkIHdpdGggdHVybiBtb2JpbGl0eT8pDQoNCldloa9sbCB0cnkgYW5kIGFkZCBzb21lIHRleHQg
Zm9yIGV4cGxhbmF0aW9uLiBUaGUgcmVhc29uIGZvciBhZGRpbmcgoa5NQVmhrw0Kd2FzIHRoYXQg
aW4gc29tZSBjYXNlcywgZWcgZ3Vlc3QgbmV0d29ya3MsIHRoZSBjbGllbnQgbWF5IG5vdCBrbm93
IGhvdyB0bw0KYXV0aGVudGljYXRlIHdpdGggdGhlIHR1cm4gc2VydmVyIGluIHRoZSBsb2NhbC9h
Y2Nlc3MgbmV0d29yay4gTWFraW5nIGl0IGENCm11c3Qgd291bGQgbGltaXQgZGlzY292ZXJ5IGFu
ZCB1c2Ugb2YgdHVybiBzZXJ2ZXJzIG9mZmVyZWQgYnkgYWNjZXNzDQpuZXR3b3Jrcy4gDQoNCj4N
Cj5TbyBJIGd1ZXNzIEkgd291bGQgbGlrZSB0byBzZWUgc29tZSB0ZXh0IHRoYXQgZXhwbGFpbnMg
d2h5IHRoaXMgY2hhbmdlDQo+aXMgbWFkZSwgYW5kIHdoeSBpdCdzIG9rYXksIGFuZCB3YXJuaW5n
IGFib3V0IHJlbGF0ZWQgcmlza3MuDQoNClN1cmUsIHdloa9sbCBhZGQgbW9yZSB0ZXh0IGFyb3Vu
ZCByaXNrcyBvciByZW9yZ2FuaXplIGEgbGl0dGxlIGJpdDsgd2Whr3ZlDQpkaXNjdXNzZWQgcmlz
a3MgaW4gcGFyYWdyYXBocyAyJjMgb2YgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMuDQogDQo+DQo+
RmluYWxseSwgSSBzdGlsbCB0aGluayB0aGlzIHNvcnQgb2Ygbm9ybWF0aXZlIGNoYW5nZSB3YXJy
YW50cyBhbg0KPiJVUERBVEVTIFJGQyA1NzY2IiBsYWJlbC4NCj4NCj4NCj4+DQo+Pj4NCj4+PiBC
dXQgaW4gYW55IGNhc2UsIEkgdGhpbmsgcmVsYXhpbmcgdGhhdCByZXF1aXJlbWVudCBuZWVkcyBz
b21lDQo+Pj4gZGlzY3Vzc2lvbg0KPj4+IGFib3V0IGhvdyB0aGUgc2VydmVyIG9yIGNsaWVudCBj
YW4gYmUgc3VyZSB0aGF0IGFsbCBjb21tdW5pY2F0aW9uIGlzDQo+Pj4gaW4NCj4+PiBmYWN0IGNv
bnN0cmFpbmVkIHRvIHRoZSBsb2NhbCBuZXR3b3JrLg0KPj4+DQo+Pj4NCj4+PiAtLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tDQo+Pj4gQ09NTUVOVDoNCj4+PiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+Pj4NCj4+PiBTdWJzdGFudGl2
ZToNCj4+Pg0KPj4+IC0gZ2VuZXJhbDogSSBhZ3JlZSB3aXRoIHRoZSBESVNDVVNTIHBvc2l0aW9u
cyBmcm9tIFRlcnJ5LCBBbGV4ZXksIGFuZA0KPj4+IEthdGhsZWVuLg0KPj4+DQo+Pj4gLTMsIHBh
cmFncmFwaCAxOiBBcmUgdGhlIE1VU1QgYW5kIE1BWSBpbiB0aGlzIHBhcmFncmFwaCBfbmV3Xw0K
Pj4+IHJlcXVpcmVtZW50cywgb3IganVzdCBzdGF0ZW1lbnRzIG9mIGZhY3QgYWJvdXQgcHJldmlv
dXNseSBleGlzdGluZw0KPj4+IHJlcXVpcmVtZW50cz8gSWYgdGhlIGxhdHRlciwgdGhleSBzaG91
bGQgbm90IHVzZSAyMTE5IGtleXdvcmRzLg0KPj4NCj4+IFRoZXNlIGFyZSBuZXcgcmVxdWlyZW1l
bnRzLg0KPg0KPkkgZmluZCB0aGF0IGNvbmZ1c2luZywgYmVjYXVzZSBpdCBzZWVtcyBsaWtlIHRo
ZSBwYXJhZ3JhcGggaXMgZGVzY3JpYmluZw0KPnRoZSBzdGF0ZSBvZiBhZmZhaXJzIHRoYXQgdGhp
cyBkcmFmdCBzZWVrcyB0byBpbXByb3ZlLiBBbHNvLCB0aGUgIkZvcg0KPmV4YW1wbGUsIiBpbiBm
cm9udCBvZiBhIHNlbnRlbmNlIHdpdGggYSAyMTE5IGtleXdvcmQgaXMgY29uZnVzaW5nIGlmIHRo
ZQ0KPnB1cnBvc2UgaXMgdG8gZGVmaW5lIGEgbmV3IHJlcXVpcmVtZW50Lg0KDQpUaGVzZSBhcmUg
bmV3IHJlcXVpcmVtZW50cyBpbiB0aGF0IKGuaWYnIGEgY2xpZW50IGlzIGNob29zZXMgdG8NCmF1
dG8tZGlzY292ZXIgVFVSTiBzZXJ2ZXJzLCB0aGUgY2xpZW50IE1VU1QgY29uc2lkZXIgYXBwbGlj
YXRpb24gY29uZmlnIGFzDQpsb2NhbCBjb25maWcgYW5kIHByb2NlZWQgd2l0aCBvdGhlciBkaXNj
b3ZlcnkgbWVjaGFuaXNtcyBkZXNjcmliZWQgaW4gdGhlDQpkcmFmdC4gVGhlIGRyYWZ0IGRvZXMg
bm90IGltcG9zZSBhcHBsaWNhdGlvbiBjb25maWcgYW5kIGhlbmNlIHRoZSBNQVkNCmFmdGVyIHRo
YXQuIE1BWSBjYW4gYmUgcmVtb3ZlZCwgcGVyaGFwcy4NCg0KSG93IGFib3V0IHJld29yZGluZyB0
byB0aGUgZm9sbG93aW5nIHRvIGF2b2lkIGNvbmZ1c2lvbjoNCg0KIlRVUk4gY2xpZW50cywgYnkg
ZGVmYXVsdCwgZGlzY292ZXIgVFVSTiBzZXJ2ZXIocykgYnkgbWVhbnMgb2YgbG9jYWwNCiAgIG9y
IG1hbnVhbCBUVVJOIGNvbmZpZ3VyYXRpb24gKGkuZS4sIFRVUk4gc2VydmVycyBjb25maWd1cmVk
IGF0IHRoZQ0KICAgc3lzdGVtIGxldmVsKS4gIENvbmZpZ3VyYXRpb24gZGlzY292ZXJlZCBmcm9t
IGFuIGFwcGxpY2F0aW9uLCBlZyBhDQogICBKYXZhIFNjcmlwdCBzcGVjaWZpZWQgVFVSTiBzZXJ2
ZXIgZm9yIFdlYiBSZWFsLVRpbWUgQ29tbXVuaWNhdGlvbg0KICAgKFdlYlJUQykgW0ktRC5pZXRm
LXJ0Y3dlYi1vdmVydmlld10gdXNhZ2VzIGFuZCByZWxhdGVkIGV4dGVuc2lvbnMsDQogICBNVVNU
IGJlIGNvbnNpZGVyZWQgYXMgbG9jYWwgY29uZmlndXJhdGlvbi4gIEFuIGltcGxlbWVudGF0aW9u
IG1heQ0KICAgZ2l2ZSB0aGUgdXNlciBhbiBvcHBvcnR1bml0eSAoZS5nLiwgYnkgbWVhbnMgb2Yg
Y29uZmlndXJhdGlvbiBmaWxlDQpvcHRpb25zIG9yIG1lbnUgaXRlbXMpIHRvIHNwZWNpZnkgYSBU
VVJOIHNlcnZlciBmb3IgZWFjaCBhZGRyZXNzoaYiDQoNCg0KDQoNCj4NCj4+DQo+Pj4NCj4+Pg0K
Pj4+IC00LjEuMiwgZmlyc3QgcGFyYWdyYXBoOiBJdCB3b3VsZCBiZSBoZWxwZnVsIHRvIGhhdmUg
YSBkaXNjdXNzaW9uDQo+Pj4gYWJvdXQNCj4+PiBjbGllbnRzIHRoYXQgbWF5IHN1cHBvcnQgbXVs
dGlwbGUgdXNlcnMsIHBvdGVudGlhbGx5IHdpdGggZGlmZmVyZW50DQo+Pj4gZG9tYWlucywgb3Ig
Zm9yIGEgc2luZ2xlIHVzZXIgdG8gdXNlIGRpZmZlcmVudCBkb21haW5zIGZvciBkaWZmZXJlbnQN
Cj4+PiBzZXJ2aWNlcy4NCj4+DQo+PiBTdXJlLiBXb3VsZCBpdCBzdWZmaWNlIGlmIHdlIGluY2x1
ZGVkIHRoZSBmb2xsb3dpbmcgdGV4dDoNCj4+DQo+PiAiQSBjbGllbnQgbWF5IHN1cHBvcnQgbXVs
dGlwbGUgdXNlcnMsIHBvdGVudGlhbGx5IHdpdGggZGlmZmVyZW50DQo+PiAgICBkb21haW5zLCBv
ciBmb3IgYSBzaW5nbGUgdXNlciB0byB1c2UgZGlmZmVyZW50IGRvbWFpbnMgZm9yDQo+PiBkaWZm
ZXJlbnQNCj4+ICAgIHNlcnZpY2VzLiAgVGhlIG1lYW5zIHRvIGNob29zZSBhbmQgZXh0cmFjdCB0
aGUgZGVzaXJlZCBkb21haW4gbmFtZQ0KPj4gbWF5DQo+PiBiZQ0KPj4gICAgZGlmZmVyZW50IGJh
c2VkIG9uIHRoZSB0eXBlIG9mIGlkZW50aWZpZXIsIHNlcnZpY2UgYmVpbmcgdXNlZCBldGMNCj4+
ICAgIHdoaWNoIGFyZSBvdXRzaWRlIHRoZSBzY29wZSBvZiB0aGlzIGRvY3VtZW50LiINCj4NCj5Z
ZXMsIHRoYW5rcy4NCj4NCj4+DQo+Pj4NCj4+PiAtNC4yLCBnZW5lcmFsOiBEbyBJIGNvcnJlY3Rs
eSB1bmRlcnN0YW5kIHRoYXQgbW9zdCBvZiB0aGlzIHNlY3Rpb24NCj4+PiBkZXNjcmliZXMgdGhl
IHJlc3VsdHMgb2YgYXBwbHlpbmcgUkZDIDU5MjggcHJvY2VkdXJlcyB0byB0aGUNCj4+PiBleHRy
YWN0ZWQNCj4+PiBkb21haW4gbmFtZT8NCj4+DQo+PiBZZXMsIHRoZSBzZWN0aW9uIGRvZXMgZXhh
Y3RseSB0aGF0Lg0KPj4NCj4+PiBJZiBzbywgaXMgaXQgbm90IGVub3VnaCByZWZlcmVuY2UgNTky
OCBhbmQgbGVhdmUgaXQgYXQgdGhhdD8NCj4+DQo+PiBTdXJlLiBXZSBjYW4gY2VydGFpbmx5IHJl
bW92ZSB0aGUgZXhhbXBsZS4NCj4NCj5PbiByZWZsZWN0aW9uLCBJIHdpbGwgbGVhdmUgdGhhdCB0
byB5b3VyIGRpc2NyZXRpb24uDQo+DQo+Wy4uLl0NCj4NCj4+DQo+Pj4NCj4+PiAtIEluZm9ybWF0
aW9uYWwgUmVmZXJlbmNlczoNCj4+PiBJLUQuaWV0Zi1ydGN3ZWItcmV0dXJuIGFuZCBSRkMgNjEy
NSBhcmUgY2l0ZWQgYXMgcGFydCBvZiBub3JtYXRpdmUNCj4+PiByZXF1aXJlbWVudHMsIHdoaWNo
IG1ha2VzIHRoZW0gYnkgZGVmaW5pdGlvbiBuZWVkIHRvIGJlIG5vcm1hdGl2ZQ0KPj4+IHJlZmVy
ZW5jZXMuIEktRC5pZXRmLXRyYW0tdHVybi1tb2JpbGl0eSwgUkZDNjAyNCwgYW5kIFJGQzcyNTAg
YXJlDQo+Pj4gYm9yZGVybGluZTsgSSB0aGluayBvbmUgY291bGQgbWFrZSBhbiBhcmd1bWVudCB0
aGF0IG9uZSBuZWVkcyB0byByZWFkDQo+Pj4gdGhlbSB0byBmdWxseSB1bmRlcnN0YW5kIHRoaXMg
ZHJhZnQuDQo+Pg0KPj4gV2UnbGwgdXBkYXRlIHRoZSBkcmFmdCB0byBjaXRlIHRoZXNlIGFzIG5v
bi1ub3JtYXRpdmUuDQo+Pg0KPg0KPkl0IG1heSBub3QgYmUgdGhhdCBzaW1wbGUuIE5vcm1hdGl2
ZSBsYW5ndWFnZSBhcm91bmQgYSBjaXRhdGlvbiBpcyBhDQo+Y2x1ZSB0aGF0IGEgcmVmZXJlbmNl
IG5lZWRzIHRvIGJlIG5vcm1hdGl2ZS4gQnV0IGxhY2sgb2YgaXQgZG9lcyBub3QNCj5uZWNlc3Nh
cmlseSBwcm92ZSB0aGUgb3Bwb3NpdGUuIFRoZSB0ZXN0IGlzIHdoZXRoZXIgc29tZW9uZSBjb3Vs
ZCBmdWxseQ0KPnVuZGVyc3RhbmQgYW5kIGltcGxlbWVudCB0aGlzIGRyYWZ0IHdpdGhvdXQgcmVh
ZGluZyB0aGUgcmVmZXJlbmNlZA0KPmRvY3VtZW50Lg0KDQpTdXJlLg0KDQpUaGUgZHJhZnQgZGVz
Y3JpYmVzIG1lY2hhbmlzbXMgZm9yIGdlbmVyYWwgVFVSTiBzZXJ2ZXIgZGlzY292ZXJ5LiBPbmUg
b25seQ0KbmVlZHMgdG8gcmVhZCBJLUQuaWV0Zi1ydGN3ZWItcmV0dXJuIGZvciBXZWJSVEMgcmVs
YXRlZCB1c2UgY2FzZXM7DQpzaW1pbGFybHkgSS1ELmlldGYtdHJhbS10dXJuLW1vYmlsaXR5IGlz
IG9ubHkgaW50ZXJlc3RpbmcgaWYgeW91IHdhbnRlZCB0bw0KYWRkcmVzcyBtb2JpbGl0eS4gVGhl
c2Ugc2hvdWxkIGJlIG5vbi1ub3JtYXRpdmUuDQpSRkM2MDI0LCBhbmQgUkZDNzI1MCBhcmUgYm9y
ZGVybGluZSBidXQgZ2l2ZW4gdGhhdCB0aGVzZSBhcmUgZG8gd2l0aA0Kc2VjdXJpdHkgY29uc2lk
ZXJhdGlvbnMsIHdlIGNvdWxkIG1ha2UgdGhlbSBub3JtYXRpdmUuDQoNCiANClRoYW5rcywNClBy
YXNoYW50aA0KDQo+DQo+Wy4uLl0NCg0K


From nobody Wed Sep 14 00:26:47 2016
Return-Path: <magnus.westerlund@ericsson.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 27DD212B026; Wed, 14 Sep 2016 00:26:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 qE4rftRRzhL8; Wed, 14 Sep 2016 00:26:44 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 049FC12B1F8; Wed, 14 Sep 2016 00:26:43 -0700 (PDT)
X-AuditID: c1b4fb3a-ab7ff7000000099a-1f-57d8fbb08903
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.183.87]) by  (Symantec Mail Security) with SMTP id 82.3A.02458.0BBF8D75; Wed, 14 Sep 2016 09:26:42 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.89) with Microsoft SMTP Server id 14.3.301.0; Wed, 14 Sep 2016 09:26:40 +0200
To: IETF AVTCore WG <avt@ietf.org>, "tram@ietf.org" <tram@ietf.org>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <a4fa9a16-b276-7b72-fe70-406ab7db64cd@ericsson.com>
Date: Wed, 14 Sep 2016 09:26:38 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpjluLIzCtJLcpLzFFi42KZGbE9XHfT7xvhBms2yFi87FnJbvFh7QU2 ByaPJUt+MgUwRnHZpKTmZJalFunbJXBl3FqqVzCXu+LRudwGxm7OLkZODgkBE4nzS+eydTFy cQgJrGeUuLbkGQuEs5xRouvlfiCHg0NEwFmi9bslSAObgIXEzR+NbCC2sICnxNr/q5hBbF4B e4kJn86AxVkEVCX27lgA1ioqECOxvi8BokRQ4uTMJ2BhZqDyB1vLQMLMAvISzVtng00REtCW aGjqYJ3AyDsLSccshI5ZSDoWMDKvYhQtTi0uzk03MtJLLcpMLi7Oz9PLSy3ZxAgMnYNbflvt YDz43PEQowAHoxIPbwLbjXAh1sSy4srcQ4wSHMxKIrzHvgKFeFMSK6tSi/Lji0pzUosPMUpz sCiJ8/47ez1cSCA9sSQ1OzW1ILUIJsvEwSnVwDhj7wnGU+Xn763gqJjIlK+dbL7odYlPlZXr V92UxNzTDtvS7j17GPLmAEPDN4PA8q++ijm/xPbelFbkF2Z9+2CqbFvk4eUVxtfnhE39dFJ5 Xl/quYCiw7sNtj5X3Pc+1/jlXYmvPzNajx8+dvacT5vyk2KNw6/+BCkGVXddiHy2f+2Gr4f5 FH4rsRRnJBpqMRcVJwIA58aGKBkCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/81uWKJq5-hMt4GJhjac_rW7WuBM>
Subject: [tram] draft-ietf-avtcore-rfc5764-mux-fixes: Change in IANA table entry
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 14 Sep 2016 07:26:46 -0000

AVTCORE and TRAM,

I would like to inform you that IANA had a post doc approval comment 
regarding the STUN Methods entry for the Reserved range which was 
originally formulated as:

    Value:   0x100-0xFFF

    Name:   Reserved (MUST be allocated with IETF Review.  For DTLS-SRTP
       multiplexing collision avoidance see RFCXXXX)

IANA reacted to the RFC2119 language in relation to the usage of 
"Reserved" which has a specified meaning. The authors, the AD and I 
agreed that respecifying "reserved" was not the intention and have 
modified the text to read:

Value: 0x100-0xFFF	
Name: Reserved (For DTLS-SRTP multiplexing collision avoidance see 
[RFC-ietf-avtcore-rfc5764-mux-fixes-11]. Cannot be made available for 
assignment without IETF Review.)	

Please see Stun Methods at
http://www.iana.org/assignments/stun-parameters

If you see issues with this please contact me the document shepherd 
immediately.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Wed Sep 14 08:59:30 2016
Return-Path: <ben@nostrum.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 EF54012B311; Wed, 14 Sep 2016 08:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.408
X-Spam-Level: 
X-Spam-Status: No, score=-3.408 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.508] 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 AkAGAEQLJFf0; Wed, 14 Sep 2016 08:59:20 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 3A77E12B335; Wed, 14 Sep 2016 08:40:38 -0700 (PDT)
Received: from [132.177.252.238] (132-177-252-238.ip.sipit.net [132.177.252.238] (may be forged)) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u8EFeWeD066453 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 14 Sep 2016 10:40:33 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 132-177-252-238.ip.sipit.net [132.177.252.238] (may be forged) claimed to be [132.177.252.238]
From: "Ben Campbell" <ben@nostrum.com>
To: "Prashanth Patil" <praspati@cisco.com>
Date: Wed, 14 Sep 2016 11:40:26 -0400
Message-ID: <C8A84B8E-AA9A-4524-8E1C-EDDAA669AC72@nostrum.com>
In-Reply-To: <D3F834A3.132DD6%praspati@cisco.com>
References: <147269306853.31916.11958166980739260630.idtracker@ietfa.amsl.com> <D3EDF13E.13092C%praspati@cisco.com> <362B7B05-81DA-49D7-8452-9BA21F991D00@nostrum.com> <D3F834A3.132DD6%praspati@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.5r5260)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/yPeoPZb3ojRMIMdPQeOBZWsuZUY>
Cc: "tram-chairs@ietf.org" <tram-chairs@ietf.org>, Simon Perreault <sperreault@jive.com>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, "tram@ietf.org" <tram@ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [tram] Ben Campbell's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS and COMMENT)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 14 Sep 2016 15:59:23 -0000

On 13 Sep 2016, at 23:31, Prashanth Patil (praspati) wrote:

> Hi Ben,
>
> On 9/8/16, 1:48 PM, "Ben Campbell" <ben@nostrum.com> wrote:
>
>> Hi, thanks for the response. Some more comments inline (I removed
>> sections that do not seem to need further discussion.).
>>
>> Thanks!
>>
>> Ben.
>>
>> On 7 Sep 2016, at 22:22, Prashanth Patil (praspati) wrote:
>>
>>> Hi Ben,
>>> Apologies for the delay. Please see inline..
>>>
>>> On 8/31/16, 6:24 PM, "Ben Campbell" <ben@nostrum.com> wrote:
>>>
>>
>> [...]
>>
>>>
>>>> ----------------------------------------------------------------------
>>>> DISCUSS:
>>>> ----------------------------------------------------------------------
>>>>
>>>> -9, first paragraph says:
>>>>
>>>> "Use of Session Traversal Utilities for NAT (STUN) [RFC5389]
>>>>   authentication is OPTIONAL for TURN servers provided by the local
>>>>   network or by the access network.  A network provided TURN server
>>>> MAY
>>>>   be configured to accept Allocation requests without STUN
>>>>   authentication, and a TURN client MAY be configured to accept
>>>>   Allocation success responses without STUN authentication from a
>>>>   network provided TURN server. "
>>>>
>>>> This seems to relax the MUST level requirement in RFC 5766 that 
>>>> says
>>>> TURN
>>>> MUST use STUN long-term credential authentication, or use some 
>>>> other
>>>> equally strong mechanism. From a purely process perpective, this
>>>> would
>>>> either require an update to 5766, or it would require an argument
>>>> that
>>>> the local/access network is somehow equally protected. I think the
>>>> latter
>>>> would only be true if the access network has some sort of 
>>>> protection
>>>> beyond just being the access network (e.g. a vpn, ipsec, or 
>>>> physical
>>>> isolation.)  I don't recall seeing text that suggested any of 
>>>> those.
>>>
>>> Tiru and Kathleen have discussed this in another thread. We intend 
>>> to
>>> add
>>> text around the following:
>>>
>>> "will add more details that TURN servers deployed in DMZ must only
>>> process
>>> STUN requests from a trusted network and not from external networks.
>>> Similarly TURN servers in access networks must only process STUN
>>> requests
>>> from its subscribers. Access control can be provided by 
>>> access-control
>>> lists, firewalls and/or by user authentication to the TURN server. 
>>> We
>>> can
>>> also discuss other recommendations like per-subscriber quota limit,
>>> ingress filtering.²
>>>
>>> Would this address your concern?
>>
>> It helps, but if I understand the intend correctly, it doesn't 
>> entirely
>> address my concern.
>>
>> This draft seems to relax the "MUST" level requirement to use stun
>> authentication (or something equally strong) to an effective "MAY",
>> without any real explanation of why, and without really exploring the
>> security implications. Do you assume that a TURN server used in this
>> context is using "something equally strong"? A number of the security
>> considerations in RFC 5766 are mitigated by the assumption of stun
>> authentication. How are they impacted by this relaxation? Does the 
>> lack
>> of authentication lead to a risk of allocation-hijacking? (especially 
>> if
>> combined with turn mobility?)
>
> We’ll try and add some text for explanation. The reason for adding 
> ‘MAY’
> was that in some cases, eg guest networks, the client may not know how 
> to
> authenticate with the turn server in the local/access network. Making 
> it a
> must would limit discovery and use of turn servers offered by access
> networks.

I'm curious why this is special for discovered TURN servers vs TURN 
servers in general. Isn't equally likely that a non-discovered server 
might want to allow credential free operation?

Also, doesn't this create a situation where a client that would prefer 
to authenticate for some reason cannot do so? (That is, the client's 
only option would be to operate without authentication or choose not to 
communicate.)

>
>>
>> So I guess I would like to see some text that explains why this 
>> change
>> is made, and why it's okay, and warning about related risks.
>
> Sure, we’ll add more text around risks or reorganize a little bit; 
> we’ve
> discussed risks in paragraphs 2&3 of Security Considerations.

To be clear, I think that discussion is incomplete. RFC 5766 discusses 
several security considerations that explicitly mention authentication 
as a mitigating factor. For example, 17.1.1, 17.1.3, 17.1.7, and 17.2.1.

Those paragraphs (and the bullet list before them) also seem to depend 
on (D)TLS to mitigate some of the issues. But even that is only a 
SHOULD.

Additionally, now that I've looked more closely at the TLS language in 
those paragraphs, I have a concern about the statement that 
communication SHOULD fall back to non-authenticated TLS if 
authentication fails. I think it's reasonable to allow that, but it 
should be a very clear administrator choice. That is, there should never 
be a situation where the administrator (and user) think they have 
authenticated TLS when they do not. This interacts with RFC 5766 section 
17.1.5.

>
>>
>> Finally, I still think this sort of normative change warrants an
>> "UPDATES RFC 5766" label.

I didn't see a response to this comment. Does that mean you agree? To 
put a finer point on this, I don't think the current draft makes it 
sufficiently obvious that it is removing an existing normative 
requirement to authenticate, and I am concerned that people reviewing 
the draft during IETF last call may not have noticed that.

So to be clear, what I'd like to see is an "Updates RFC 5766" header and 
text that explicitly calls out that the "OPTIONAL" is a downgrade of a 
MUST level authentication requirement in 5766. Once those are in place, 
I think we should consider repeating the IETF last call.


>>
>>
>>>
>>>>
>>>> But in any case, I think relaxing that requirement needs some
>>>> discussion
>>>> about how the server or client can be sure that all communication 
>>>> is
>>>> in
>>>> fact constrained to the local network.
>>>>
>>>>
>>>> ----------------------------------------------------------------------
>>>> COMMENT:
>>>> ----------------------------------------------------------------------
>>>>
>>>> Substantive:
>>>>
>>>> - general: I agree with the DISCUSS positions from Terry, Alexey, 
>>>> and
>>>> Kathleen.
>>>>
>>>> -3, paragraph 1: Are the MUST and MAY in this paragraph _new_
>>>> requirements, or just statements of fact about previously existing
>>>> requirements? If the latter, they should not use 2119 keywords.
>>>
>>> These are new requirements.
>>
>> I find that confusing, because it seems like the paragraph is 
>> describing
>> the state of affairs that this draft seeks to improve. Also, the "For
>> example," in front of a sentence with a 2119 keyword is confusing if 
>> the
>> purpose is to define a new requirement.
>
> These are new requirements in that ‘if' a client is chooses to
> auto-discover TURN servers, the client MUST consider application 
> config as
> local config and proceed with other discovery mechanisms described in 
> the
> draft. The draft does not impose application config and hence the MAY
> after that. MAY can be removed, perhaps.
>
> How about rewording to the following to avoid confusion:
>
> "TURN clients, by default, discover TURN server(s) by means of local
>    or manual TURN configuration (i.e., TURN servers configured at the
>    system level).  Configuration discovered from an application, eg a
>    Java Script specified TURN server for Web Real-Time Communication
>    (WebRTC) [I-D.ietf-rtcweb-overview] usages and related extensions,
>    MUST be considered as local configuration.  An implementation may
>    give the user an opportunity (e.g., by means of configuration file
> options or menu items) to specify a TURN server for each address…"
>

What are the practical implications of considering things as "local 
configuration"? (Since it's in the predicate of a MUST...)


[...]


From nobody Thu Sep 15 11:07:37 2016
Return-Path: <praspati@cisco.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 18B0D12B0C6; Thu, 15 Sep 2016 11:07:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.029
X-Spam-Level: 
X-Spam-Status: No, score=-16.029 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 u8JTzNb44OBP; Thu, 15 Sep 2016 11:07:32 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0E0F12B22F; Thu, 15 Sep 2016 11:07:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12736; q=dns/txt; s=iport; t=1473962851; x=1475172451; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=YDdN8I3YKkj3rQwO32ZPc+zFyrqXHYW6GeG/CSEW9eQ=; b=glzlRiic012Ybvk6JrDJ0hv6MB1GEwuqZQBjuxXe3zRu7WgvJUVkEPke qfeKIIld8pa9OijxjCdc90pROeuxdaWObK0V8Cr31x71CrdmMYd7SQOXb WhfyaxKNCFsIKuMfMHnmlBoocjUs3OIpLhn/kWog+oK6+dJNPkzOsGXdc w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AdAQAf49pX/4wNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgzoBAQEBAR6BUweNLKkZgg+CA4YeAhyBQDgUAQIBAQEBAQEBXie?= =?us-ascii?q?EYgEBBDRFEAIBCBgEKAICMCUCBA4FiEqYRp0cBow+AQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEdgQCFMYRPhB0KAy2CZYJgAQSIMpE2AY9YgW6EYokVhnyFYoN6AR42gng?= =?us-ascii?q?KFhiBN3CEVIEufwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.30,340,1470700800"; d="scan'208";a="322228934"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 15 Sep 2016 18:07:07 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id u8FI779K000309 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 15 Sep 2016 18:07:07 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 15 Sep 2016 14:07:06 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Thu, 15 Sep 2016 14:07:06 -0400
From: "Prashanth Patil (praspati)" <praspati@cisco.com>
To: Ben Campbell <ben@nostrum.com>
Thread-Topic: Ben Campbell's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS and COMMENT)
Thread-Index: AQHSChJSaICpZPYmxkqQAN2wEDY0faB5KI5ngAGI84A=
Date: Thu, 15 Sep 2016 18:07:06 +0000
Message-ID: <D40025C5.134673%praspati@cisco.com>
References: <147269306853.31916.11958166980739260630.idtracker@ietfa.amsl.com> <D3EDF13E.13092C%praspati@cisco.com> <362B7B05-81DA-49D7-8452-9BA21F991D00@nostrum.com> <D3F834A3.132DD6%praspati@cisco.com> <C8A84B8E-AA9A-4524-8E1C-EDDAA669AC72@nostrum.com>
In-Reply-To: <C8A84B8E-AA9A-4524-8E1C-EDDAA669AC72@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.8.160830
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.155.84.77]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <BF1BF25F9AAFD649907D7EE21C109B77@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/zRM73N4kZ33wsGls_9e6wgD9m2A>
Cc: "tram-chairs@ietf.org" <tram-chairs@ietf.org>, Simon Perreault <sperreault@jive.com>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, "tram@ietf.org" <tram@ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [tram] Ben Campbell's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS and COMMENT)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 15 Sep 2016 18:07:35 -0000

SGkgQmVuLA0KDQpPbiA5LzE0LzE2LCA4OjQwIEFNLCAiQmVuIENhbXBiZWxsIiA8YmVuQG5vc3Ry
dW0uY29tPiB3cm90ZToNCg0KPg0KPg0KPk9uIDEzIFNlcCAyMDE2LCBhdCAyMzozMSwgUHJhc2hh
bnRoIFBhdGlsIChwcmFzcGF0aSkgd3JvdGU6DQo+DQo+PiBIaSBCZW4sDQo+Pg0KPj4gT24gOS84
LzE2LCAxOjQ4IFBNLCAiQmVuIENhbXBiZWxsIiA8YmVuQG5vc3RydW0uY29tPiB3cm90ZToNCj4+
DQo+Pj4gSGksIHRoYW5rcyBmb3IgdGhlIHJlc3BvbnNlLiBTb21lIG1vcmUgY29tbWVudHMgaW5s
aW5lIChJIHJlbW92ZWQNCj4+PiBzZWN0aW9ucyB0aGF0IGRvIG5vdCBzZWVtIHRvIG5lZWQgZnVy
dGhlciBkaXNjdXNzaW9uLikuDQo+Pj4NCj4+PiBUaGFua3MhDQo+Pj4NCj4+PiBCZW4uDQo+Pj4N
Cj4+PiBPbiA3IFNlcCAyMDE2LCBhdCAyMjoyMiwgUHJhc2hhbnRoIFBhdGlsIChwcmFzcGF0aSkg
d3JvdGU6DQo+Pj4NCj4+Pj4gSGkgQmVuLA0KPj4+PiBBcG9sb2dpZXMgZm9yIHRoZSBkZWxheS4g
UGxlYXNlIHNlZSBpbmxpbmUuLg0KPj4+Pg0KPj4+PiBPbiA4LzMxLzE2LCA2OjI0IFBNLCAiQmVu
IENhbXBiZWxsIiA8YmVuQG5vc3RydW0uY29tPiB3cm90ZToNCj4+Pj4NCj4+Pg0KPj4+IFsuLi5d
DQo+Pj4NCj4+Pj4NCj4+Pj4+IA0KPj4+Pj4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+Pj4+PiBESVNDVVNTOg0K
Pj4+Pj4gDQo+Pj4+Pi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4+Pj4+DQo+Pj4+PiAtOSwgZmlyc3QgcGFyYWdy
YXBoIHNheXM6DQo+Pj4+Pg0KPj4+Pj4gIlVzZSBvZiBTZXNzaW9uIFRyYXZlcnNhbCBVdGlsaXRp
ZXMgZm9yIE5BVCAoU1RVTikgW1JGQzUzODldDQo+Pj4+PiAgIGF1dGhlbnRpY2F0aW9uIGlzIE9Q
VElPTkFMIGZvciBUVVJOIHNlcnZlcnMgcHJvdmlkZWQgYnkgdGhlIGxvY2FsDQo+Pj4+PiAgIG5l
dHdvcmsgb3IgYnkgdGhlIGFjY2VzcyBuZXR3b3JrLiAgQSBuZXR3b3JrIHByb3ZpZGVkIFRVUk4g
c2VydmVyDQo+Pj4+PiBNQVkNCj4+Pj4+ICAgYmUgY29uZmlndXJlZCB0byBhY2NlcHQgQWxsb2Nh
dGlvbiByZXF1ZXN0cyB3aXRob3V0IFNUVU4NCj4+Pj4+ICAgYXV0aGVudGljYXRpb24sIGFuZCBh
IFRVUk4gY2xpZW50IE1BWSBiZSBjb25maWd1cmVkIHRvIGFjY2VwdA0KPj4+Pj4gICBBbGxvY2F0
aW9uIHN1Y2Nlc3MgcmVzcG9uc2VzIHdpdGhvdXQgU1RVTiBhdXRoZW50aWNhdGlvbiBmcm9tIGEN
Cj4+Pj4+ICAgbmV0d29yayBwcm92aWRlZCBUVVJOIHNlcnZlci4gIg0KPj4+Pj4NCj4+Pj4+IFRo
aXMgc2VlbXMgdG8gcmVsYXggdGhlIE1VU1QgbGV2ZWwgcmVxdWlyZW1lbnQgaW4gUkZDIDU3NjYg
dGhhdA0KPj4+Pj4gc2F5cw0KPj4+Pj4gVFVSTg0KPj4+Pj4gTVVTVCB1c2UgU1RVTiBsb25nLXRl
cm0gY3JlZGVudGlhbCBhdXRoZW50aWNhdGlvbiwgb3IgdXNlIHNvbWUNCj4+Pj4+IG90aGVyDQo+
Pj4+PiBlcXVhbGx5IHN0cm9uZyBtZWNoYW5pc20uIEZyb20gYSBwdXJlbHkgcHJvY2VzcyBwZXJw
ZWN0aXZlLCB0aGlzDQo+Pj4+PiB3b3VsZA0KPj4+Pj4gZWl0aGVyIHJlcXVpcmUgYW4gdXBkYXRl
IHRvIDU3NjYsIG9yIGl0IHdvdWxkIHJlcXVpcmUgYW4gYXJndW1lbnQNCj4+Pj4+IHRoYXQNCj4+
Pj4+IHRoZSBsb2NhbC9hY2Nlc3MgbmV0d29yayBpcyBzb21laG93IGVxdWFsbHkgcHJvdGVjdGVk
LiBJIHRoaW5rIHRoZQ0KPj4+Pj4gbGF0dGVyDQo+Pj4+PiB3b3VsZCBvbmx5IGJlIHRydWUgaWYg
dGhlIGFjY2VzcyBuZXR3b3JrIGhhcyBzb21lIHNvcnQgb2YNCj4+Pj4+IHByb3RlY3Rpb24NCj4+
Pj4+IGJleW9uZCBqdXN0IGJlaW5nIHRoZSBhY2Nlc3MgbmV0d29yayAoZS5nLiBhIHZwbiwgaXBz
ZWMsIG9yDQo+Pj4+PiBwaHlzaWNhbA0KPj4+Pj4gaXNvbGF0aW9uLikgIEkgZG9uJ3QgcmVjYWxs
IHNlZWluZyB0ZXh0IHRoYXQgc3VnZ2VzdGVkIGFueSBvZg0KPj4+Pj4gdGhvc2UuDQo+Pj4+DQo+
Pj4+IFRpcnUgYW5kIEthdGhsZWVuIGhhdmUgZGlzY3Vzc2VkIHRoaXMgaW4gYW5vdGhlciB0aHJl
YWQuIFdlIGludGVuZA0KPj4+PiB0bw0KPj4+PiBhZGQNCj4+Pj4gdGV4dCBhcm91bmQgdGhlIGZv
bGxvd2luZzoNCj4+Pj4NCj4+Pj4gIndpbGwgYWRkIG1vcmUgZGV0YWlscyB0aGF0IFRVUk4gc2Vy
dmVycyBkZXBsb3llZCBpbiBETVogbXVzdCBvbmx5DQo+Pj4+IHByb2Nlc3MNCj4+Pj4gU1RVTiBy
ZXF1ZXN0cyBmcm9tIGEgdHJ1c3RlZCBuZXR3b3JrIGFuZCBub3QgZnJvbSBleHRlcm5hbCBuZXR3
b3Jrcy4NCj4+Pj4gU2ltaWxhcmx5IFRVUk4gc2VydmVycyBpbiBhY2Nlc3MgbmV0d29ya3MgbXVz
dCBvbmx5IHByb2Nlc3MgU1RVTg0KPj4+PiByZXF1ZXN0cw0KPj4+PiBmcm9tIGl0cyBzdWJzY3Jp
YmVycy4gQWNjZXNzIGNvbnRyb2wgY2FuIGJlIHByb3ZpZGVkIGJ5DQo+Pj4+IGFjY2Vzcy1jb250
cm9sDQo+Pj4+IGxpc3RzLCBmaXJld2FsbHMgYW5kL29yIGJ5IHVzZXIgYXV0aGVudGljYXRpb24g
dG8gdGhlIFRVUk4gc2VydmVyLg0KPj4+PiBXZQ0KPj4+PiBjYW4NCj4+Pj4gYWxzbyBkaXNjdXNz
IG90aGVyIHJlY29tbWVuZGF0aW9ucyBsaWtlIHBlci1zdWJzY3JpYmVyIHF1b3RhIGxpbWl0LA0K
Pj4+PiBpbmdyZXNzIGZpbHRlcmluZy6p9w0KPj4+Pg0KPj4+PiBXb3VsZCB0aGlzIGFkZHJlc3Mg
eW91ciBjb25jZXJuPw0KPj4+DQo+Pj4gSXQgaGVscHMsIGJ1dCBpZiBJIHVuZGVyc3RhbmQgdGhl
IGludGVuZCBjb3JyZWN0bHksIGl0IGRvZXNuJ3QNCj4+PiBlbnRpcmVseQ0KPj4+IGFkZHJlc3Mg
bXkgY29uY2Vybi4NCj4+Pg0KPj4+IFRoaXMgZHJhZnQgc2VlbXMgdG8gcmVsYXggdGhlICJNVVNU
IiBsZXZlbCByZXF1aXJlbWVudCB0byB1c2Ugc3R1bg0KPj4+IGF1dGhlbnRpY2F0aW9uIChvciBz
b21ldGhpbmcgZXF1YWxseSBzdHJvbmcpIHRvIGFuIGVmZmVjdGl2ZSAiTUFZIiwNCj4+PiB3aXRo
b3V0IGFueSByZWFsIGV4cGxhbmF0aW9uIG9mIHdoeSwgYW5kIHdpdGhvdXQgcmVhbGx5IGV4cGxv
cmluZyB0aGUNCj4+PiBzZWN1cml0eSBpbXBsaWNhdGlvbnMuIERvIHlvdSBhc3N1bWUgdGhhdCBh
IFRVUk4gc2VydmVyIHVzZWQgaW4gdGhpcw0KPj4+IGNvbnRleHQgaXMgdXNpbmcgInNvbWV0aGlu
ZyBlcXVhbGx5IHN0cm9uZyI/IEEgbnVtYmVyIG9mIHRoZSBzZWN1cml0eQ0KPj4+IGNvbnNpZGVy
YXRpb25zIGluIFJGQyA1NzY2IGFyZSBtaXRpZ2F0ZWQgYnkgdGhlIGFzc3VtcHRpb24gb2Ygc3R1
bg0KPj4+IGF1dGhlbnRpY2F0aW9uLiBIb3cgYXJlIHRoZXkgaW1wYWN0ZWQgYnkgdGhpcyByZWxh
eGF0aW9uPyBEb2VzIHRoZQ0KPj4+IGxhY2sNCj4+PiBvZiBhdXRoZW50aWNhdGlvbiBsZWFkIHRv
IGEgcmlzayBvZiBhbGxvY2F0aW9uLWhpamFja2luZz8gKGVzcGVjaWFsbHkNCj4+PiBpZg0KPj4+
IGNvbWJpbmVkIHdpdGggdHVybiBtb2JpbGl0eT8pDQo+Pg0KPj4gV2Whr2xsIHRyeSBhbmQgYWRk
IHNvbWUgdGV4dCBmb3IgZXhwbGFuYXRpb24uIFRoZSByZWFzb24gZm9yIGFkZGluZw0KPj4goa5N
QVmhrw0KPj4gd2FzIHRoYXQgaW4gc29tZSBjYXNlcywgZWcgZ3Vlc3QgbmV0d29ya3MsIHRoZSBj
bGllbnQgbWF5IG5vdCBrbm93IGhvdw0KPj4gdG8NCj4+IGF1dGhlbnRpY2F0ZSB3aXRoIHRoZSB0
dXJuIHNlcnZlciBpbiB0aGUgbG9jYWwvYWNjZXNzIG5ldHdvcmsuIE1ha2luZw0KPj4gaXQgYQ0K
Pj4gbXVzdCB3b3VsZCBsaW1pdCBkaXNjb3ZlcnkgYW5kIHVzZSBvZiB0dXJuIHNlcnZlcnMgb2Zm
ZXJlZCBieSBhY2Nlc3MNCj4+IG5ldHdvcmtzLg0KPg0KPkknbSBjdXJpb3VzIHdoeSB0aGlzIGlz
IHNwZWNpYWwgZm9yIGRpc2NvdmVyZWQgVFVSTiBzZXJ2ZXJzIHZzIFRVUk4NCj5zZXJ2ZXJzIGlu
IGdlbmVyYWwuIElzbid0IGVxdWFsbHkgbGlrZWx5IHRoYXQgYSBub24tZGlzY292ZXJlZCBzZXJ2
ZXINCj5taWdodCB3YW50IHRvIGFsbG93IGNyZWRlbnRpYWwgZnJlZSBvcGVyYXRpb24/DQo+DQo+
QWxzbywgZG9lc24ndCB0aGlzIGNyZWF0ZSBhIHNpdHVhdGlvbiB3aGVyZSBhIGNsaWVudCB0aGF0
IHdvdWxkIHByZWZlcg0KPnRvIGF1dGhlbnRpY2F0ZSBmb3Igc29tZSByZWFzb24gY2Fubm90IGRv
IHNvPyAoVGhhdCBpcywgdGhlIGNsaWVudCdzDQo+b25seSBvcHRpb24gd291bGQgYmUgdG8gb3Bl
cmF0ZSB3aXRob3V0IGF1dGhlbnRpY2F0aW9uIG9yIGNob29zZSBub3QgdG8NCj5jb21tdW5pY2F0
ZS4pDQoNCkl0oa9zIHNwZWNpYWwgZm9yIGRpc2NvdmVyZWQgVFVSTiBzZXJ2ZXJzIGluIHRoYXQg
ZGlzY292ZXJ5IGlzIGZvciByZWxheQ0KcHJvdmlkZWQgYnkgZWl0aGVyIHRoZSBsb2NhbCBvciB0
aGUgYWNjZXNzIG5ldHdvcmsuIFdloa9yZSBub3QgbWFuZGF0aW5nDQp0aGF0IHRoaXMgc2hvdWxk
IGJlIHJlbGF4ZWQgZm9yIGFsbCBUVVJOIHNlcnZlcnMsIGF0IGxlYXN0IHRoYXShr3Mgbm90IHRo
ZQ0KaW50ZW50aW9uLg0KIA0KQnV0IHllcywgaXQgaXMgYSBsaW1pdGF0aW9uLiBXZSBkbyBnbyBv
biB0byBjbGFyaWZ5IHRoYXQgYSBjbGllbnQgTUFZIGJlDQpjb25maWd1cmVkIHRvIGFjY2VwdCBB
bGxvY2F0aW9uIHN1Y2Nlc3MgcmVzcG9uc2VzIHdpdGhvdXQgU1RVTg0KYXV0aGVudGljYXRpb24u
DQoNClRoZXJlIGhhcyBiZWVuIGRpc2N1c3Npb24gaW4gdGhlIFdHIHRvIG1ha2UgdGhpcyBvcHRp
b25hbC4NCiANCj4NCj4+DQo+Pj4NCj4+PiBTbyBJIGd1ZXNzIEkgd291bGQgbGlrZSB0byBzZWUg
c29tZSB0ZXh0IHRoYXQgZXhwbGFpbnMgd2h5IHRoaXMNCj4+PiBjaGFuZ2UNCj4+PiBpcyBtYWRl
LCBhbmQgd2h5IGl0J3Mgb2theSwgYW5kIHdhcm5pbmcgYWJvdXQgcmVsYXRlZCByaXNrcy4NCj4+
DQo+PiBTdXJlLCB3ZaGvbGwgYWRkIG1vcmUgdGV4dCBhcm91bmQgcmlza3Mgb3IgcmVvcmdhbml6
ZSBhIGxpdHRsZSBiaXQ7DQo+PiB3ZaGvdmUNCj4+IGRpc2N1c3NlZCByaXNrcyBpbiBwYXJhZ3Jh
cGhzIDImMyBvZiBTZWN1cml0eSBDb25zaWRlcmF0aW9ucy4NCj4NCj5UbyBiZSBjbGVhciwgSSB0
aGluayB0aGF0IGRpc2N1c3Npb24gaXMgaW5jb21wbGV0ZS4gUkZDIDU3NjYgZGlzY3Vzc2VzDQo+
c2V2ZXJhbCBzZWN1cml0eSBjb25zaWRlcmF0aW9ucyB0aGF0IGV4cGxpY2l0bHkgbWVudGlvbiBh
dXRoZW50aWNhdGlvbg0KPmFzIGEgbWl0aWdhdGluZyBmYWN0b3IuIEZvciBleGFtcGxlLCAxNy4x
LjEsIDE3LjEuMywgMTcuMS43LCBhbmQgMTcuMi4xLg0KPg0KPlRob3NlIHBhcmFncmFwaHMgKGFu
ZCB0aGUgYnVsbGV0IGxpc3QgYmVmb3JlIHRoZW0pIGFsc28gc2VlbSB0byBkZXBlbmQNCj5vbiAo
RClUTFMgdG8gbWl0aWdhdGUgc29tZSBvZiB0aGUgaXNzdWVzLiBCdXQgZXZlbiB0aGF0IGlzIG9u
bHkgYQ0KPlNIT1VMRC4NCg0KUmlnaHQsIEkgdGhpbmsgd2UgY2FuIG1hbmRhdGUgKEQpVExTICpp
ZiogU1RVTiBhdXRoZW50aWNhdGlvbiBvcg0KdGhpcmQtcGFydHkgYXV0aG9yaXphdGlvbiBpcyBu
b3QgdXNlZC4NCg0KDQo+DQo+QWRkaXRpb25hbGx5LCBub3cgdGhhdCBJJ3ZlIGxvb2tlZCBtb3Jl
IGNsb3NlbHkgYXQgdGhlIFRMUyBsYW5ndWFnZSBpbg0KPnRob3NlIHBhcmFncmFwaHMsIEkgaGF2
ZSBhIGNvbmNlcm4gYWJvdXQgdGhlIHN0YXRlbWVudCB0aGF0DQo+Y29tbXVuaWNhdGlvbiBTSE9V
TEQgZmFsbCBiYWNrIHRvIG5vbi1hdXRoZW50aWNhdGVkIFRMUyBpZg0KPmF1dGhlbnRpY2F0aW9u
IGZhaWxzLiBJIHRoaW5rIGl0J3MgcmVhc29uYWJsZSB0byBhbGxvdyB0aGF0LCBidXQgaXQNCj5z
aG91bGQgYmUgYSB2ZXJ5IGNsZWFyIGFkbWluaXN0cmF0b3IgY2hvaWNlLg0KDQpGYWxsYmFjayB0
byB1bmF1dGhlbnRpY2F0ZWQgKEQpVExTIHNob3VsZCBvbmx5IGhhcHBlbiBpZiB0aGUgdXNlciBv
cHRzIGZvcg0Kb3Bwb3J0dW5pc3RpYy1lbmNyeXB0aW9uLiBXb3VsZCB5b3UgcHJlZmVyIHdlIGFk
ZCBhIGxpbmUgaGlnaGxpZ2h0aW5nIHRoaXMNCmZhY3Q/DQoNCj5UaGF0IGlzLCB0aGVyZSBzaG91
bGQgbmV2ZXINCj5iZSBhIHNpdHVhdGlvbiB3aGVyZSB0aGUgYWRtaW5pc3RyYXRvciAoYW5kIHVz
ZXIpIHRoaW5rIHRoZXkgaGF2ZQ0KPmF1dGhlbnRpY2F0ZWQgVExTIHdoZW4gdGhleSBkbyBub3Qu
IFRoaXMgaW50ZXJhY3RzIHdpdGggUkZDIDU3NjYgc2VjdGlvbg0KPjE3LjEuNS4NCj4NCj4+DQo+
Pj4NCj4+PiBGaW5hbGx5LCBJIHN0aWxsIHRoaW5rIHRoaXMgc29ydCBvZiBub3JtYXRpdmUgY2hh
bmdlIHdhcnJhbnRzIGFuDQo+Pj4gIlVQREFURVMgUkZDIDU3NjYiIGxhYmVsLg0KPg0KPkkgZGlk
bid0IHNlZSBhIHJlc3BvbnNlIHRvIHRoaXMgY29tbWVudC4gRG9lcyB0aGF0IG1lYW4geW91IGFn
cmVlPyBUbw0KPnB1dCBhIGZpbmVyIHBvaW50IG9uIHRoaXMsIEkgZG9uJ3QgdGhpbmsgdGhlIGN1
cnJlbnQgZHJhZnQgbWFrZXMgaXQNCj5zdWZmaWNpZW50bHkgb2J2aW91cyB0aGF0IGl0IGlzIHJl
bW92aW5nIGFuIGV4aXN0aW5nIG5vcm1hdGl2ZQ0KPnJlcXVpcmVtZW50IHRvIGF1dGhlbnRpY2F0
ZSwgYW5kIEkgYW0gY29uY2VybmVkIHRoYXQgcGVvcGxlIHJldmlld2luZw0KPnRoZSBkcmFmdCBk
dXJpbmcgSUVURiBsYXN0IGNhbGwgbWF5IG5vdCBoYXZlIG5vdGljZWQgdGhhdC4NCj4NCj5TbyB0
byBiZSBjbGVhciwgd2hhdCBJJ2QgbGlrZSB0byBzZWUgaXMgYW4gIlVwZGF0ZXMgUkZDIDU3NjYi
IGhlYWRlciBhbmQNCj50ZXh0IHRoYXQgZXhwbGljaXRseSBjYWxscyBvdXQgdGhhdCB0aGUgIk9Q
VElPTkFMIiBpcyBhIGRvd25ncmFkZSBvZiBhDQo+TVVTVCBsZXZlbCBhdXRoZW50aWNhdGlvbiBy
ZXF1aXJlbWVudCBpbiA1NzY2LiBPbmNlIHRob3NlIGFyZSBpbiBwbGFjZSwNCj5JIHRoaW5rIHdl
IHNob3VsZCBjb25zaWRlciByZXBlYXRpbmcgdGhlIElFVEYgbGFzdCBjYWxsLg0KDQpTdXJlLCB3
ZaGvbGwgbWFrZSB0aGlzIHVwZGF0ZS4NCg0KLVByYXNoYW50aA0KDQo+DQo+DQo+Pj4NCj4+Pg0K
Pj4+Pg0KPj4+Pj4NCj4+Pj4+IEJ1dCBpbiBhbnkgY2FzZSwgSSB0aGluayByZWxheGluZyB0aGF0
IHJlcXVpcmVtZW50IG5lZWRzIHNvbWUNCj4+Pj4+IGRpc2N1c3Npb24NCj4+Pj4+IGFib3V0IGhv
dyB0aGUgc2VydmVyIG9yIGNsaWVudCBjYW4gYmUgc3VyZSB0aGF0IGFsbCBjb21tdW5pY2F0aW9u
DQo+Pj4+PiBpcw0KPj4+Pj4gaW4NCj4+Pj4+IGZhY3QgY29uc3RyYWluZWQgdG8gdGhlIGxvY2Fs
IG5ldHdvcmsuDQo+Pj4+Pg0KPj4+Pj4NCj4+Pj4+IA0KPj4+Pj4tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+Pj4+
PiBDT01NRU5UOg0KPj4+Pj4gDQo+Pj4+Pi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4+Pj4+DQo+Pj4+PiBTdWJz
dGFudGl2ZToNCj4+Pj4+DQo+Pj4+PiAtIGdlbmVyYWw6IEkgYWdyZWUgd2l0aCB0aGUgRElTQ1VT
UyBwb3NpdGlvbnMgZnJvbSBUZXJyeSwgQWxleGV5LA0KPj4+Pj4gYW5kDQo+Pj4+PiBLYXRobGVl
bi4NCj4+Pj4+DQo+Pj4+PiAtMywgcGFyYWdyYXBoIDE6IEFyZSB0aGUgTVVTVCBhbmQgTUFZIGlu
IHRoaXMgcGFyYWdyYXBoIF9uZXdfDQo+Pj4+PiByZXF1aXJlbWVudHMsIG9yIGp1c3Qgc3RhdGVt
ZW50cyBvZiBmYWN0IGFib3V0IHByZXZpb3VzbHkgZXhpc3RpbmcNCj4+Pj4+IHJlcXVpcmVtZW50
cz8gSWYgdGhlIGxhdHRlciwgdGhleSBzaG91bGQgbm90IHVzZSAyMTE5IGtleXdvcmRzLg0KPj4+
Pg0KPj4+PiBUaGVzZSBhcmUgbmV3IHJlcXVpcmVtZW50cy4NCj4+Pg0KPj4+IEkgZmluZCB0aGF0
IGNvbmZ1c2luZywgYmVjYXVzZSBpdCBzZWVtcyBsaWtlIHRoZSBwYXJhZ3JhcGggaXMNCj4+PiBk
ZXNjcmliaW5nDQo+Pj4gdGhlIHN0YXRlIG9mIGFmZmFpcnMgdGhhdCB0aGlzIGRyYWZ0IHNlZWtz
IHRvIGltcHJvdmUuIEFsc28sIHRoZSAiRm9yDQo+Pj4gZXhhbXBsZSwiIGluIGZyb250IG9mIGEg
c2VudGVuY2Ugd2l0aCBhIDIxMTkga2V5d29yZCBpcyBjb25mdXNpbmcgaWYNCj4+PiB0aGUNCj4+
PiBwdXJwb3NlIGlzIHRvIGRlZmluZSBhIG5ldyByZXF1aXJlbWVudC4NCj4+DQo+PiBUaGVzZSBh
cmUgbmV3IHJlcXVpcmVtZW50cyBpbiB0aGF0IKGuaWYnIGEgY2xpZW50IGlzIGNob29zZXMgdG8N
Cj4+IGF1dG8tZGlzY292ZXIgVFVSTiBzZXJ2ZXJzLCB0aGUgY2xpZW50IE1VU1QgY29uc2lkZXIg
YXBwbGljYXRpb24NCj4+IGNvbmZpZyBhcw0KPj4gbG9jYWwgY29uZmlnIGFuZCBwcm9jZWVkIHdp
dGggb3RoZXIgZGlzY292ZXJ5IG1lY2hhbmlzbXMgZGVzY3JpYmVkIGluDQo+PiB0aGUNCj4+IGRy
YWZ0LiBUaGUgZHJhZnQgZG9lcyBub3QgaW1wb3NlIGFwcGxpY2F0aW9uIGNvbmZpZyBhbmQgaGVu
Y2UgdGhlIE1BWQ0KPj4gYWZ0ZXIgdGhhdC4gTUFZIGNhbiBiZSByZW1vdmVkLCBwZXJoYXBzLg0K
Pj4NCj4+IEhvdyBhYm91dCByZXdvcmRpbmcgdG8gdGhlIGZvbGxvd2luZyB0byBhdm9pZCBjb25m
dXNpb246DQo+Pg0KPj4gIlRVUk4gY2xpZW50cywgYnkgZGVmYXVsdCwgZGlzY292ZXIgVFVSTiBz
ZXJ2ZXIocykgYnkgbWVhbnMgb2YgbG9jYWwNCj4+ICAgIG9yIG1hbnVhbCBUVVJOIGNvbmZpZ3Vy
YXRpb24gKGkuZS4sIFRVUk4gc2VydmVycyBjb25maWd1cmVkIGF0IHRoZQ0KPj4gICAgc3lzdGVt
IGxldmVsKS4gIENvbmZpZ3VyYXRpb24gZGlzY292ZXJlZCBmcm9tIGFuIGFwcGxpY2F0aW9uLCBl
ZyBhDQo+PiAgICBKYXZhIFNjcmlwdCBzcGVjaWZpZWQgVFVSTiBzZXJ2ZXIgZm9yIFdlYiBSZWFs
LVRpbWUgQ29tbXVuaWNhdGlvbg0KPj4gICAgKFdlYlJUQykgW0ktRC5pZXRmLXJ0Y3dlYi1vdmVy
dmlld10gdXNhZ2VzIGFuZCByZWxhdGVkIGV4dGVuc2lvbnMsDQo+PiAgICBNVVNUIGJlIGNvbnNp
ZGVyZWQgYXMgbG9jYWwgY29uZmlndXJhdGlvbi4gIEFuIGltcGxlbWVudGF0aW9uIG1heQ0KPj4g
ICAgZ2l2ZSB0aGUgdXNlciBhbiBvcHBvcnR1bml0eSAoZS5nLiwgYnkgbWVhbnMgb2YgY29uZmln
dXJhdGlvbiBmaWxlDQo+PiBvcHRpb25zIG9yIG1lbnUgaXRlbXMpIHRvIHNwZWNpZnkgYSBUVVJO
IHNlcnZlciBmb3IgZWFjaCBhZGRyZXNzoaYiDQo+Pg0KPg0KPldoYXQgYXJlIHRoZSBwcmFjdGlj
YWwgaW1wbGljYXRpb25zIG9mIGNvbnNpZGVyaW5nIHRoaW5ncyBhcyAibG9jYWwNCj5jb25maWd1
cmF0aW9uIj8gKFNpbmNlIGl0J3MgaW4gdGhlIHByZWRpY2F0ZSBvZiBhIE1VU1QuLi4pDQo+DQo+
DQo+Wy4uLl0NCj4NCg0K


From nobody Sun Sep 18 23:44:30 2016
Return-Path: <gonzalo.camarillo@ericsson.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 59A6212B0A1 for <tram@ietfa.amsl.com>; Sun, 18 Sep 2016 23:44:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.221
X-Spam-Level: 
X-Spam-Status: No, score=-104.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 iPE8pqkrUzvI for <tram@ietfa.amsl.com>; Sun, 18 Sep 2016 23:44:25 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 2ACB812B064 for <tram@ietf.org>; Sun, 18 Sep 2016 23:44:24 -0700 (PDT)
X-AuditID: c1b4fb25-5405a9800000793b-73-57df8946ec34
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by  (Symantec Mail Security) with SMTP id F7.C0.31035.6498FD75; Mon, 19 Sep 2016 08:44:23 +0200 (CEST)
Received: from [131.160.126.219] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.47) with Microsoft SMTP Server id 14.3.301.0; Mon, 19 Sep 2016 08:44:21 +0200
To: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
References: <3d8524a8-95bb-d63e-0c97-9e56140fde9b@ericsson.com> <9338c4b8-3664-83a2-8e8f-d72f0ecac034@ericsson.com> <ef071e41-2d7d-09de-549b-6973ecf97056@ericsson.com> <50E8BB5D-43D3-48A9-8D4A-1334065DB006@cisco.com>
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-ID: <524fafa7-df36-e6de-20e3-fd825ab921af@ericsson.com>
Date: Mon, 19 Sep 2016 09:44:20 +0300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <50E8BB5D-43D3-48A9-8D4A-1334065DB006@cisco.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrLLMWRmVeSWpSXmKPExsUyM2K7rq575/1wgw1tbBZzp/hZXL8SavFh 7QU2B2aPKb83snosWfKTyePfnKfMAcxRXDYpqTmZZalF+nYJXBk7u3exFDzhrTj55CZrA+ME 7i5GTg4JAROJV00TmUFsIYH1jBJrlpZ1MXIB2WsZJWZu/skKkhAW8JU43XaZDcQWETCX2PO7 hQ2i6B6jRNPJgywgCWYBH4kvm6aC2WwCFhJbbt0Hs3kF7CUWPHsN1swioCqxbtpOMFtUIEZi /6yZzBA1ghInZz4Bq+cUsJV4cuMAI8RMA4kji+awQtjyEtvfzoG6VFti+bMWlgmMArOQtM9C 0jILScsCRuZVjKLFqcVJuelGxnqpRZnJxcX5eXp5qSWbGIGBenDLb9UdjJffOB5iFOBgVOLh fVB3P1yINbGsuDL3EKMEB7OSCO+kFqAQb0piZVVqUX58UWlOavEhRmkOFiVx3n9nr4cLCaQn lqRmp6YWpBbBZJk4OKUaGG2zf6dwWRTeMef7pqM0hSdu6j6mQ2s/s4iueHfDon4j1/y+65lt p2M6Tu/PEHP7emeeQICcbfvzZJH4yexymbkXe1MrloVKvmv63u8f85KZe3r2i2b7NEn+YmXx oEPf/wvzfizatXjW7lNMxgfVmL/PFH+XdOHrlT1O0081Lf40+erljs6jV5RYijMSDbWYi4oT AZpfSttQAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/k8j3GkzHbMaf4tV8U-Wqq9nRv08>
Cc: Simon Perreault <sperreault@jive.com>, tram mailing list <tram@ietf.org>
Subject: Re: [tram] Dedicated reviewers needed for draft-ietf-tram-stun-pmtud
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 06:44:27 -0000

Hi Gonzalo,

do you have an ETA for the revision?

Thanks,

Gonzalo

On 01/09/2016 4:48 PM, Gonzalo Salgueiro (gsalguei) wrote:
> Thanks for the reviews.  We will try and get a new version out shortly addressing these comments.
> 
> Thanks,
> 
> Gonzalo
> 
> 
>> On Sep 1, 2016, at 2:45 AM, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> wrote:
>>
>> Tiru, Ram: thanks for your reviews!
>>
>> Marc, Gonzalo: could you please address the comments you have received?
>>
>> Cheers,
>>
>> Gonzalo
>>
>> On 26/07/2016 7:58 PM, Gonzalo Camarillo wrote:
>>> Hi,
>>>
>>> per our session in Berlin, we are still looking for volunteers to review
>>> this draft. Please, contact the chairs if you would like to volunteer.
>>>
>>> Thanks,
>>>
>>> Gonzalo
>>>
>>> On 07/07/2016 9:06 AM, Gonzalo Camarillo wrote:
>>>> Folks,
>>>>
>>>> we would like to get the following draft in a good-enough shape so that
>>>> we can start its WGLC in the near future. For that, we need at least two
>>>> dedicated reviewers:
>>>>
>>>> https://datatracker.ietf.org/doc/draft-ietf-tram-stun-pmtud/
>>>>
>>>> If you would like to volunteer to review this draft, please let the
>>>> chairs know.
>>>>
>>>> We are after a general review of the draft. In addition, we would like
>>>> the dedicated reviewers to provide input on the two proposed Probing
>>>> Mechanisms (Simple and Complete).
>>>>
>>>> Thanks,
>>>>
>>>> Gonzalo
>>>>
>>>> _______________________________________________
>>>> 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 Sep 19 10:52:06 2016
Return-Path: <gsalguei@cisco.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 15BDA12B4A5 for <tram@ietfa.amsl.com>; Mon, 19 Sep 2016 10:52:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.837
X-Spam-Level: 
X-Spam-Status: No, score=-16.837 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 OkDkhDxDqNQw for <tram@ietfa.amsl.com>; Mon, 19 Sep 2016 10:52:03 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A191112B4B3 for <tram@ietf.org>; Mon, 19 Sep 2016 10:52:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2213; q=dns/txt; s=iport; t=1474307522; x=1475517122; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=B0IUo1IqHYgAhhN5ZZ8bi73skPZoQvNElr7oYUR51z4=; b=MNpNdW7cWfxnsECcX947ArrlgWUTL8xH5OT7Sc3wImmFeHvbguwZj3ul eT/1q7CZ4gTIvTBibwjJaMXJvK/ATRd8uGT9gJth5fj+UBfuB3x0LVSCN FpnGGZhddHUj1d6JU8hBWaGUnNFH1hwxSalrjAwq4ft/sjQA5ZDmQRBVV U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BtAQAgJeBX/4wNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgzoBAQEBAR5XfAeNLKtBggMZC4V6AoFPOBQBAgEBAQEBAQFeJ4R?= =?us-ascii?q?hAQEBAwEBAQFrCwULAgEIGC4nCyUCBA4FiEIIDr4aAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBFwWGN4F8CIJQhESDLYIvBZlvAYYliTaBboRjiRmMZIN6AR42hGpyhwN?= =?us-ascii?q?/AQEB?=
X-IronPort-AV: E=Sophos;i="5.30,362,1470700800"; d="scan'208";a="325329685"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 19 Sep 2016 17:52:01 +0000
Received: from XCH-ALN-008.cisco.com (xch-aln-008.cisco.com [173.36.7.18]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id u8JHq10V009811 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 19 Sep 2016 17:52:01 GMT
Received: from xch-aln-009.cisco.com (173.36.7.19) by XCH-ALN-008.cisco.com (173.36.7.18) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 19 Sep 2016 12:52:01 -0500
Received: from xch-aln-009.cisco.com ([173.36.7.19]) by XCH-ALN-009.cisco.com ([173.36.7.19]) with mapi id 15.00.1210.000; Mon, 19 Sep 2016 12:52:01 -0500
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Thread-Topic: [tram] Dedicated reviewers needed for draft-ietf-tram-stun-pmtud
Thread-Index: AQHSBByEBVEeJMqD6kW/sNkqomYyJKBk+rcAgBvTYQCAALqLAA==
Date: Mon, 19 Sep 2016 17:52:00 +0000
Message-ID: <1864E897-0889-40DA-B7D4-E273DB243003@cisco.com>
References: <3d8524a8-95bb-d63e-0c97-9e56140fde9b@ericsson.com> <9338c4b8-3664-83a2-8e8f-d72f0ecac034@ericsson.com> <ef071e41-2d7d-09de-549b-6973ecf97056@ericsson.com> <50E8BB5D-43D3-48A9-8D4A-1334065DB006@cisco.com> <524fafa7-df36-e6de-20e3-fd825ab921af@ericsson.com>
In-Reply-To: <524fafa7-df36-e6de-20e3-fd825ab921af@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.150.178.211]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <8E30968189DD694EB197E9FEC035257B@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/3Q9HkpdAtVczmaaWgkfZa1VbzQo>
Cc: Simon Perreault <sperreault@jive.com>, tram mailing list <tram@ietf.org>
Subject: Re: [tram] Dedicated reviewers needed for draft-ietf-tram-stun-pmtud
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 17:52:05 -0000

Apologies, but recent travel schedules and day jobs got in the way of our g=
etting together to address these reviews.  We hope to get to this shortly.

Thanks,

Gonzalo


> On Sep 19, 2016, at 2:44 AM, Gonzalo Camarillo <Gonzalo.Camarillo@ericsso=
n.com> wrote:
>=20
> Hi Gonzalo,
>=20
> do you have an ETA for the revision?
>=20
> Thanks,
>=20
> Gonzalo
>=20
> On 01/09/2016 4:48 PM, Gonzalo Salgueiro (gsalguei) wrote:
>> Thanks for the reviews.  We will try and get a new version out shortly a=
ddressing these comments.
>>=20
>> Thanks,
>>=20
>> Gonzalo
>>=20
>>=20
>>> On Sep 1, 2016, at 2:45 AM, Gonzalo Camarillo <Gonzalo.Camarillo@ericss=
on.com> wrote:
>>>=20
>>> Tiru, Ram: thanks for your reviews!
>>>=20
>>> Marc, Gonzalo: could you please address the comments you have received?
>>>=20
>>> Cheers,
>>>=20
>>> Gonzalo
>>>=20
>>> On 26/07/2016 7:58 PM, Gonzalo Camarillo wrote:
>>>> Hi,
>>>>=20
>>>> per our session in Berlin, we are still looking for volunteers to revi=
ew
>>>> this draft. Please, contact the chairs if you would like to volunteer.
>>>>=20
>>>> Thanks,
>>>>=20
>>>> Gonzalo
>>>>=20
>>>> On 07/07/2016 9:06 AM, Gonzalo Camarillo wrote:
>>>>> Folks,
>>>>>=20
>>>>> we would like to get the following draft in a good-enough shape so th=
at
>>>>> we can start its WGLC in the near future. For that, we need at least =
two
>>>>> dedicated reviewers:
>>>>>=20
>>>>> https://datatracker.ietf.org/doc/draft-ietf-tram-stun-pmtud/
>>>>>=20
>>>>> If you would like to volunteer to review this draft, please let the
>>>>> chairs know.
>>>>>=20
>>>>> We are after a general review of the draft. In addition, we would lik=
e
>>>>> the dedicated reviewers to provide input on the two proposed Probing
>>>>> Mechanisms (Simple and Complete).
>>>>>=20
>>>>> Thanks,
>>>>>=20
>>>>> Gonzalo
>>>>>=20
>>>>> _______________________________________________
>>>>> tram mailing list
>>>>> tram@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/tram
>>>>>=20
>>>>=20
>>>=20
>>> _______________________________________________
>>> tram mailing list
>>> tram@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tram
>>=20


From nobody Tue Sep 20 15:21:21 2016
Return-Path: <ben@nostrum.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 602E112B308; Tue, 20 Sep 2016 15:21:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.216
X-Spam-Level: 
X-Spam-Status: No, score=-4.216 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-2.316] 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 TJeYp2yNUWNP; Tue, 20 Sep 2016 15:21:18 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 136E812B011; Tue, 20 Sep 2016 15:21:18 -0700 (PDT)
Received: from [10.0.1.21] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u8KMLDxZ059667 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 20 Sep 2016 17:21:14 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.21]
From: "Ben Campbell" <ben@nostrum.com>
To: "Prashanth Patil" <praspati@cisco.com>
Date: Tue, 20 Sep 2016 17:21:13 -0500
Message-ID: <94397E90-8765-4AAE-81C2-49B8C5B39132@nostrum.com>
In-Reply-To: <D40025C5.134673%praspati@cisco.com>
References: <147269306853.31916.11958166980739260630.idtracker@ietfa.amsl.com> <D3EDF13E.13092C%praspati@cisco.com> <362B7B05-81DA-49D7-8452-9BA21F991D00@nostrum.com> <D3F834A3.132DD6%praspati@cisco.com> <C8A84B8E-AA9A-4524-8E1C-EDDAA669AC72@nostrum.com> <D40025C5.134673%praspati@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.5r5263)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/lxJy1xrQnROPWz4PH1yyuAYbAsg>
Cc: The IESG <iesg@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, "tram@ietf.org" <tram@ietf.org>, Simon Perreault <sperreault@jive.com>
Subject: Re: [tram] Ben Campbell's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS and COMMENT)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 22:21:19 -0000

Hi,

Some responses below.

Thanks!

Ben.

On 15 Sep 2016, at 13:07, Prashanth Patil (praspati) wrote:

[...]

>>>
>>> We’ll try and add some text for explanation. The reason for adding
>>> ‘MAY’
>>> was that in some cases, eg guest networks, the client may not know 
>>> how
>>> to
>>> authenticate with the turn server in the local/access network. 
>>> Making
>>> it a
>>> must would limit discovery and use of turn servers offered by access
>>> networks.
>>
>> I'm curious why this is special for discovered TURN servers vs TURN
>> servers in general. Isn't equally likely that a non-discovered server
>> might want to allow credential free operation?
>>
>> Also, doesn't this create a situation where a client that would 
>> prefer
>> to authenticate for some reason cannot do so? (That is, the client's
>> only option would be to operate without authentication or choose not 
>> to
>> communicate.)
>
> It’s special for discovered TURN servers in that discovery is for 
> relay
> provided by either the local or the access network. We’re not 
> mandating
> that this should be relaxed for all TURN servers, at least that’s 
> not the
> intention.

That sort of reasserts the question. Do people think that TURN servers 
that are not "discovered" will not reasonably need the same relaxation? 
(e.g. Maybe I want to widely publish the fact that I run a TURN server 
that anyone can use?)


>
> But yes, it is a limitation. We do go on to clarify that a client MAY 
> be
> configured to accept Allocation success responses without STUN
> authentication.
>
> There has been discussion in the WG to make this optional.
>
>>
>>>
>>>>
>>>> So I guess I would like to see some text that explains why this
>>>> change
>>>> is made, and why it's okay, and warning about related risks.
>>>
>>> Sure, we’ll add more text around risks or reorganize a little bit;
>>> we’ve
>>> discussed risks in paragraphs 2&3 of Security Considerations.
>>
>> To be clear, I think that discussion is incomplete. RFC 5766 
>> discusses
>> several security considerations that explicitly mention 
>> authentication
>> as a mitigating factor. For example, 17.1.1, 17.1.3, 17.1.7, and 
>> 17.2.1.
>>
>> Those paragraphs (and the bullet list before them) also seem to 
>> depend
>> on (D)TLS to mitigate some of the issues. But even that is only a
>> SHOULD.
>
> Right, I think we can mandate (D)TLS *if* STUN authentication or
> third-party authorization is not used.

I think that would help.

>
>>
>> Additionally, now that I've looked more closely at the TLS language 
>> in
>> those paragraphs, I have a concern about the statement that
>> communication SHOULD fall back to non-authenticated TLS if
>> authentication fails. I think it's reasonable to allow that, but it
>> should be a very clear administrator choice.
>
> Fallback to unauthenticated (D)TLS should only happen if the user opts 
> for
> opportunistic-encryption. Would you prefer we add a line highlighting 
> this
> fact?

Yes. Maybe I read things wrong, but I _thought_ I read the text to say 
you unconditionally SHOULD fallback.

>
>> That is, there should never
>> be a situation where the administrator (and user) think they have
>> authenticated TLS when they do not. This interacts with RFC 5766 
>> section
>> 17.1.5.
>>
>>>
>>>>
>>>> Finally, I still think this sort of normative change warrants an
>>>> "UPDATES RFC 5766" label.
>>
>> I didn't see a response to this comment. Does that mean you agree? To
>> put a finer point on this, I don't think the current draft makes it
>> sufficiently obvious that it is removing an existing normative
>> requirement to authenticate, and I am concerned that people reviewing
>> the draft during IETF last call may not have noticed that.
>>
>> So to be clear, what I'd like to see is an "Updates RFC 5766" header 
>> and
>> text that explicitly calls out that the "OPTIONAL" is a downgrade of 
>> a
>> MUST level authentication requirement in 5766. Once those are in 
>> place,
>> I think we should consider repeating the IETF last call.
>
> Sure, we’ll make this update.

Thanks!

[...]


From nobody Tue Sep 20 15:30:32 2016
Return-Path: <ben@nostrum.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 7EA8012B53C; Tue, 20 Sep 2016 15:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.216
X-Spam-Level: 
X-Spam-Status: No, score=-4.216 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-2.316] 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 fiZvyyrhjctp; Tue, 20 Sep 2016 15:30:30 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 E03C612B006; Tue, 20 Sep 2016 15:30:29 -0700 (PDT)
Received: from [10.0.1.21] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u8KMUQqJ061045 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 20 Sep 2016 17:30:27 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.21]
From: "Ben Campbell" <ben@nostrum.com>
To: "Prashanth Patil" <praspati@cisco.com>
Date: Tue, 20 Sep 2016 17:30:26 -0500
Message-ID: <23373C96-0D5F-4C0B-82EA-B93CE91ABA0F@nostrum.com>
In-Reply-To: <94397E90-8765-4AAE-81C2-49B8C5B39132@nostrum.com>
References: <147269306853.31916.11958166980739260630.idtracker@ietfa.amsl.com> <D3EDF13E.13092C%praspati@cisco.com> <362B7B05-81DA-49D7-8452-9BA21F991D00@nostrum.com> <D3F834A3.132DD6%praspati@cisco.com> <C8A84B8E-AA9A-4524-8E1C-EDDAA669AC72@nostrum.com> <D40025C5.134673%praspati@cisco.com> <94397E90-8765-4AAE-81C2-49B8C5B39132@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.5r5263)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/cMdROiu7vBjgnUkZBUTqoIM1nL0>
Cc: The IESG <iesg@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, "tram@ietf.org" <tram@ietf.org>, Simon Perreault <sperreault@jive.com>
Subject: Re: [tram] Ben Campbell's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS and COMMENT)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 22:30:32 -0000

On 20 Sep 2016, at 17:21, Ben Campbell wrote:

> To be clear, I think that discussion is incomplete. RFC 5766 discusses
>>> several security considerations that explicitly mention 
>>> authentication
>>> as a mitigating factor. For example, 17.1.1, 17.1.3, 17.1.7, and 
>>> 17.2.1.
>>>
>>> Those paragraphs (and the bullet list before them) also seem to 
>>> depend
>>> on (D)TLS to mitigate some of the issues. But even that is only a
>>> SHOULD.
>
>>
>> Right, I think we can mandate (D)TLS *if* STUN authentication or
>> third-party authorization is not used.
>
> I think that would help.

Oops, I meant to type a bit more...

Even with that addition, I still think the draft needs to address the 
impact on the issues discussed in the aforementioned sections of 5766. 
If (D)TLS solves the same issues, it would be good to say that. If there 
are things not addressed by TLS (likely true for some of the issues 
mitigated by knowing the client identity), then the draft should mention 
those, too.

Thanks!

Ben.


From nobody Wed Sep 21 22:00:45 2016
Return-Path: <wwwrun@rfc-editor.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 7C0F412BFD1; Wed, 21 Sep 2016 22:00:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.918
X-Spam-Level: 
X-Spam-Status: No, score=-104.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 bl_gwwsIeheE; Wed, 21 Sep 2016 22:00:42 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D492E12BFC8; Wed, 21 Sep 2016 22:00:42 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BFFBBB80C3E; Wed, 21 Sep 2016 22:00:41 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160922050041.BFFBBB80C3E@rfc-editor.org>
Date: Wed, 21 Sep 2016 22:00:41 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/n7c-doZurzkLDC2SzuuBXhej2wU>
Cc: drafts-update-ref@iana.org, tram@ietf.org, rfc-editor@rfc-editor.org
Subject: [tram] RFC 7982 on Measurement of Round-Trip Time and Fractional Loss Using Session Traversal Utilities for NAT (STUN)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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 Sep 2016 05:00:45 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7982

        Title:      Measurement of Round-Trip Time and 
                    Fractional Loss Using Session Traversal Utilities 
                    for NAT (STUN) 
        Author:     P. Martinsen, 
                    T. Reddy,
                    D. Wing, 
                    V. Singh
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2016
        Mailbox:    palmarti@cisco.com, 
                    tireddy@cisco.com, 
                    dwing-ietf@fuggles.com,  
                    varun@callstats.io
        Pages:      10
        Characters: 19893
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tram-stun-path-data-05.txt

        URL:        https://www.rfc-editor.org/info/rfc7982

        DOI:        http://dx.doi.org/10.17487/RFC7982

A host with multiple interfaces needs to choose the best interface for
communication.  Oftentimes, this decision is based on a static
configuration and does not consider the path characteristics, which
may affect the user experience.

This document describes a mechanism for an endpoint to measure the
path characteristics fractional loss and RTT using Session Traversal
Utilities for NAT (STUN) messages.

This document is a product of the TURN Revised and Modernized Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Fri Sep 23 04:22:26 2016
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 7078012BDA4; Fri, 23 Sep 2016 04:22:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_MULTIPLE_AT=1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=-1, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ingate.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 BIsbzSYSdCy5; Fri, 23 Sep 2016 04:22:17 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0065.outbound.protection.outlook.com [104.47.2.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FEB512BD96; Fri, 23 Sep 2016 04:22:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ingate.onmicrosoft.com; s=selector1-ingate-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Ox9xOa9FOqjTu7on8TSVmGX0q2VIUxRLjtt5zbkM02E=; b=KM+EWLKQw9X/+71s/FzsFQIAR2eQLKz88WYCJBqw6FfmSWMoUELEOORrN/HWOtW1IFXllw9Mx4XqYIpog8x22xOVmvt+v72E9zB/A8CJirG/8uorHkhM1Bdj8sV23B2L6I3Qsp1psL5rdGY0ZbeKF83I9jLwval7Rv7/VmXZo1M=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=karl@ingate.com; 
Received: from Kallei7 (90.227.80.227) by VI1PR01MB1840.eurprd01.prod.exchangelabs.com (10.166.40.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.639.5; Fri, 23 Sep 2016 11:22:13 +0000
From: Karl Stahl <karl.stahl@ingate.com>
To: 'Ben Campbell' <ben@nostrum.com>, 'Prashanth Patil' <praspati@cisco.com>
References: <147269306853.31916.11958166980739260630.idtracker@ietfa.amsl.com> <D3EDF13E.13092C%praspati@cisco.com> <362B7B05-81DA-49D7-8452-9BA21F991D00@nostrum.com> <D3F834A3.132DD6%praspati@cisco.com> <C8A84B8E-AA9A-4524-8E1C-EDDAA669AC72@nostrum.com> <D40025C5.134673%praspati@cisco.com> <94397E90-8765-4AAE-81C2-49B8C5B39132@nostrum.com>
In-Reply-To: <94397E90-8765-4AAE-81C2-49B8C5B39132@nostrum.com>
Date: Fri, 23 Sep 2016 13:22:09 +0200
Message-ID: <01e601d2158c$bb648ee0$322daca0$@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: AdITjVOJTNBn/5blTaaIYQ3PbseGigB+Bc/g
Content-Language: sv
X-Originating-IP: [90.227.80.227]
X-ClientProxiedBy: AM5PR0101CA0019.eurprd01.prod.exchangelabs.com (10.169.240.29) To VI1PR01MB1840.eurprd01.prod.exchangelabs.com (10.166.40.26)
X-MS-Office365-Filtering-Correlation-Id: 52f08ed2-3968-40a8-eeac-08d3e3a3de77
X-Microsoft-Exchange-Diagnostics: 1; VI1PR01MB1840; 2:1C6kLsVzhXNfCr1KRDY/0zqa5Ytrv6ni0HvFBwtoxsoGhfAGdYrYn9EIq7PDDnzj9uHNertcOz50uPDOCNwlbZDJaM1UcEz4C1ssgbcVu0RCYhw4zmwVDky5YhTQp2UAQ1o+ReSZTnUixjjSsKLjpL8hd8dKIHbei5VmyZDFBstK47USJpkgRXd1DeDENjEE; 3:/wDBO8QxoYrYul5PamJj41YT1iP0ST1hcb2oPioawJ7s8hcWq9cVjaoC9l0UvXsrlqofeM4iWFKSrRqnrZN/6gr8v9gZpBsdfL6IjnhoBM8Z8RO6mj9d9ewnz1HaAFty; 25:YAcYI0pLESw6RTx+XwSlPB/XeYIdWKTweh3l8MYJHLokgvViedHPnXpnxRPLauy3uOT4NK/A0+sWD4Ouvm6/Qhguk3x0kjgRJvfWGdaVB/+N+F8ezHred2+RLM5FnywW/bhSlfaKduT8d6LtkiQ/dl1H74asphneN9Hm8esD9vGQDGBbhRnKSVhoyCnf1f/M7ppGFRSAZ4IpK7dYwtLIR7XS6sbU6OUPV3eNMnl+FhTA2heafbLAK4+0+ywgmrOfM1GHYzFcSGM/7Zr2pRM/GFt9j6sp/ZsgQBup2mfETOkpvep1zsp2P79PTu4lJ+/iDzQpAbA5m0WMBrhIHRXW21pX9G1ycP3t9/xWrGy8uXBeA3/c57XGhpl5ByKupReudhBrP+xIa4H04qtPbfpoGsc62Z3B9bMnt3f2/W33cgY=
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:VI1PR01MB1840;
X-Microsoft-Exchange-Diagnostics: 1; VI1PR01MB1840; 31:MJ1cohLqJNSE1sjrl8l1o5k4/a0iP8R5jd8zGkW+3vwWSMhY/RKO57M38pTlkWDDJRv8V24/S1kEviKeYBW/iCkXIcDVzjeSxwzmUtiD+EwEVy1JPzkhpr0SeB/WXefguwwElYDTEsuCzdpG3G2uvTXxii1fU5IOvRmeyJbiWVNwKwt0pXVmfVsXVqaR4x/vc71rUrLTtxg29SNXdPufwN0PF/tNBknTL5XW1VW6Y+M=; 4:vMlHMAe6uYEBn17ypgriV6RCwhk/reNAulv1SyzSrzp0HslLZI0R0aqrZ6NMxwZ4//NhRPinZWVQGpiGmM/RaTGWe+ByoXpBFsRkGueI0OEVckcXjNEHFn+4tYgB6ll/b8q5kTIBRP/v7p0HGstERHO/7nf/7nWkASZvQ5Gh3BrDNs9hEyyc05v0XeiCQvSFTegKD1en/dLw3HYL+s83j40Jmt8i3fo3CXpa6BZKEozKCg1BZ1j0yIZwH/VNXlyXdNQpSaoox81GqFRZP4FpVzjN432sySi6i+qH8Mp4tYvPOXSwWDsHsaQv2FgKN7FKbFjL2h0aPeifc46RD8IkYinEdstGR08q7UZviYL+1Ubgc12aixwCM2e+N+wLU61nziq/bB6n4G7pI4O9m0XnKmFXVj7/aYXGoNwloBrQaUKjy5g1ANhbj/6tFHDhZND3TpPwbkBL4Lerb92/bbiP5oi0M0OEKaBh8jqaVwNtMJnCCAlnW9tEBhm3aS/S7yPy
X-Microsoft-Antispam-PRVS: <VI1PR01MB184076E605B6122D7EB3D552B1C80@VI1PR01MB1840.eurprd01.prod.exchangelabs.com>
X-Exchange-Antispam-Report-Test: UriScan:(158342451672863)(192374486261705);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6042046)(6043046); SRVR:VI1PR01MB1840; BCL:0; PCL:0; RULEID:; SRVR:VI1PR01MB1840; 
X-Forefront-PRVS: 0074BBE012
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(4630300001)(6009001)(7916002)(199003)(24454002)(38534002)(189002)(51444003)(189998001)(101416001)(66066001)(106356001)(77096005)(2950100001)(15975445007)(105586002)(14726001)(19580395003)(229853001)(96836002)(47776003)(19580405001)(36756003)(33646002)(23676002)(50466002)(3846002)(92566002)(81156014)(42186005)(4326007)(93886004)(102836003)(586003)(1420700001)(8676002)(81166006)(6116002)(68736007)(230783001)(84116002)(2906002)(50986999)(50226002)(76176999)(9686002)(5001770100001)(97736004)(61296003)(5660300001)(7736002)(305945005)(8746002)(7846002); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR01MB1840; 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?MTtWSTFQUjAxTUIxODQwOzIzOjlJNHN0SjIzbWkxeTRTbU1YeE1nZGVBUFF3?= =?utf-8?B?MDBhUEJsRVNVWlhacnFvWVdjZ3liWmpaTElKUjNGVGh2MGxJendNb3pNSDhI?= =?utf-8?B?NGpBRWJoK2p1MFJwUUJ4dGhsUmZSVjlPM0NqNyswVHBQdFpsdHBlR3FTUlc2?= =?utf-8?B?NWFhdnJodUFmbVpNMGFpNG5xWWtWRk5VTFdldWJuL0RvTnVXVFQ2REpCb2hx?= =?utf-8?B?S0kxZmR2eCs0bXpYRHUyNU5wcC9qT2xrcmdld3J2U2dXeFQ2bXpLZnBhUlZY?= =?utf-8?B?M2prOFBwLzFVb0RGc0p6TnhjZHh6c043UFk2RFNBelhpZDdWczRXbTVPNjIx?= =?utf-8?B?ekx2QXFnVDJWQ0dIa295WlFxNndMdnphMENMTUNxazA2Sk5yT1o1NjhPajFJ?= =?utf-8?B?SFdHTFg5S3FONks4NzA3REhjQ3haRkloUEc4UzVkeUZmWWl4STVpNzdhd2p2?= =?utf-8?B?bTdNbm5JVXpYL3VkVTVqSS9yN29zaXRLa2wyZFVXSWk0QTQyVmRrRDRMMEd1?= =?utf-8?B?cjdiQzY2VVMxQktMUU9RcXRpNDFWNW1OU0JLa25QUnlUTklpZURoWmRLZ2Ex?= =?utf-8?B?OHAyaHNZTnZvQjd3ZWlJaVdyYzJaOStURGhwMTRFaVFIdURJbGpKM08xOENP?= =?utf-8?B?WXZFQUdtOEFEZXFWSHhrOERaL2xpUEtYNis5RjZHWUtOM1d0OE1GakhDMkpU?= =?utf-8?B?UCtlQ0MvSXp0eVAzcVZLcWZIcjB1QzRWSDF5VmhkUDFGRHZLOVFMV3FwUytM?= =?utf-8?B?WVpVRTcraitINW9ieEJEdndNQnB2bzVBSE5YREhtQ0RGYkErM1ppSk8ybGxN?= =?utf-8?B?djRkMjRzSC9IS0RvNk9uSytJekp3VzNvSzRtZ0lwbEoybXY2RzF1V21VZjQv?= =?utf-8?B?NkZmRTRPckFtcUV3U2p4aUlsWmVHY1E1ZW1MbjF0K3JYbFVmUTlNZUkxSGhB?= =?utf-8?B?RXhNSmFSeWdlRDhYMmdPSnIzb01oSit5K293bFdpdlRFR2lHT3NlcU51cnhV?= =?utf-8?B?TkNBU0xxa0ZTSlpLOHRhc1E2M3FxZGVGb1BkUW9NdmNYTWtRMDU4cFcxYzIv?= =?utf-8?B?cHZuYkdpdUpGYmc3cVMzNUFnUHQwNTlZcEk3Y3V6WnU4Mjc3QnRIaldHZjNB?= =?utf-8?B?NmZlMGVlV0pCVy9MRDZuUDFIanp4VG5ycUlPeXN0YW0rakVGYk5QVnluQmNN?= =?utf-8?B?K2Y0cUljdmZxUU9oNWJ4Vys0dDZQQUNtRzlSb2lBeG1aSENZd0xudktTK2Ev?= =?utf-8?B?VkhsK2NQYlFoaEErUXc3Nlp0cWxpUWRTdkQzTCtldFQ1MUhKS2xIZ1RIZzhU?= =?utf-8?B?dkRRK2hCaXFlWDBIK091dGdtL2FydHRBVXpXcFZkM2txakUrSkh3Y2U4L2hy?= =?utf-8?B?bkVXemN2R3o3VCtOdm8wajRvU1Z6a0lQVGdHWitCaUxWSTBVKzlMaHpsN2xH?= =?utf-8?B?OENqQk5IUXdDS3hQZUdvWGNBSysyY3Rnem5Sc3N4YjBGRGxVNk5IL3NwTEk3?= =?utf-8?B?cVR1S2tqTEwrTDUxbjBIMlAxelpMa2NXZWdBaFBMK2JML2t6akc3TWhwblVa?= =?utf-8?B?NFBsT3E2VGdBYzNQYTQ4WTd1N2ZINWxDT0ovcHQzSjN4YUc2aEo4S3o1b3V6?= =?utf-8?B?ZldZdTJ5KzdHSHVuS0FTR1E3Tjk0Q1phaGNQTnRQbmZMYmJFd3cyaHN2b2ln?= =?utf-8?B?bVEwbWdic0QydHVHTGJQM1dKNnRiUExyNEk0aHVTMkp1RkFmb3lraTFmRWdS?= =?utf-8?B?bUtsSmtSemZkakFmaHduZz09?=
X-Microsoft-Exchange-Diagnostics: 1; VI1PR01MB1840; 6:G/gZF/0KsftGKVIV1keSTipEk+1EvfSDsaRvCk3FDDvNYeyX0e7p4dn/IY6GrYBCMxe3IiPkNvS0WwXVeXQk1XYyZyGpCXvqzKkikL+M0vRou+SNZuVfC7DcfMSaq95OlvZAF6vaWTnCiw8SlkbEgO8o7CjOvfBSpNYj/RWXq0f5NJtSADZMtrayxDr0mCAE4vVdJUxd1BbQ6gr2MJOdtH0zpboW/08u8HugTgPaRf4CDAO8XiIDTybQSc+ude/BcfeYamW6fJ+5TOT/8nX2KqoDNTU5JEre7X02k33ivD7vgRwsPH4aVMwHoV0ULvxs; 5:/S+wVGlBCoY7b/dBF9XAmF3HXNQjh9t7CsJoSk+STgUOmYolCKQV9+FCBDJhBL87u2Xvd3pdsCfOBsOl5FwcCiRnI8BZop3zetYxcuRnPE7uz4fLXalRlykaeplgD+8ffXe2bzs+ll3advMPoARDXg==; 24:FWij8Wasu866PIJQjpBysKUBoRdMkBm0/12NY5y/OGuI3SJ02flkcjyG4YbL7hDYApxoKjmKYYESGnFX0lgia9d0QS1L5KKCg4m7eKMv0UQ=; 7:0hWEOuvXpIz/OIVEfR0OW5cPrWEr6v0ZMRlrARQZoUEWFdE72H5IDpJGwLiA+3V263qnYORmF+pNwII3BasUp/MZnyhJuCg+hxO/ZN5C+YrWG+aZ/f0pEkDFl+OTcBFRaE/KF4MdNax1XKlucC3AHKDdkkx88dQ6Pa9l9iF4hTb8JCnGLGDN8RfW7UusUC80pPFzj0IczoRAuap7wLaIS504NCif8Gpoh6LstWyFnZoxQX41CiblHBu4xo7Vtvt3nV2XPLI1cBUzyc3dZiU7Kkerj47c62EWDtPjcWcoTmtn8r/+f6WCPtqu8T6+k6+r
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: ingate.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 23 Sep 2016 11:22:13.5743 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR01MB1840
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/7UND3FI8fLSgLgXp3L5kNZRrRjI>
Cc: 'Simon Perreault' <sperreault@jive.com>, tram-chairs@ietf.org, draft-ietf-tram-turn-server-discovery@ietf.org, 'The IESG' <iesg@ietf.org>, tram@ietf.org
Subject: Re: [tram] Ben Campbell's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS and COMMENT)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 23 Sep 2016 11:22:20 -0000

Regarding (from below):
Prashanth> Right, I think we can mandate (D)TLS *if* STUN authentication =
or
> third-party authorization is not used.

Ben> I think that would help.

[Karl] We cannot mandate a higher security or trust level for a TURN =
server provided by the network, paralleling the firewall/access =
router/default gateway, when the client want to place its real-time =
traffic through the turn server path, than through the default gateway =
path.

And, shall this *discovery* specification really mandate *usage*?
I am e.g. thinking about the WebRTC browser use case of =
draft-ietf-rtcweb-return-01. It must be up to that RETURN draft to =
define the *usage*, not up to a discovery draft.

The use cases I have in mind (and I don't see that TURN D(TLS) can fit) =
are:
The "autoconfiguration" of RFC 7478 (Web Real-Time Communication Use
Cases and Requirements) 2.3.5.1. or more generally:
=E2=80=9CYou need be able to use WebRTC everywhere you can surf and for =
firewall traversal and quality, you need to parallel the local =
firewall/access router/default gateway with a TURN server=E2=80=9D

This must work generally (for all services) on a LAN, Internet Caf=C3=A9 =
or GoGo WiFi, where the network provider offers us a better path for =
real-time traffic (through the TURN server).

/Karl

-----Ursprungligt meddelande-----
Fr=C3=A5n: tram [mailto:tram-bounces@ietf.org] F=C3=B6r Ben Campbell
Skickat: den 21 september 2016 00:21
Till: Prashanth Patil
Kopia: The IESG; tram-chairs@ietf.org; =
draft-ietf-tram-turn-server-discovery@ietf.org; tram@ietf.org; Simon =
Perreault
=C3=84mne: Re: [tram] Ben Campbell's Discuss on =
draft-ietf-tram-turn-server-discovery-09: (with DISCUSS and COMMENT)

Hi,

Some responses below.

Thanks!

Ben.

On 15 Sep 2016, at 13:07, Prashanth Patil (praspati) wrote:

[...]

>>>
>>> We=E2=80=99ll try and add some text for explanation. The reason for =
adding
>>> =E2=80=98MAY=E2=80=99
>>> was that in some cases, eg guest networks, the client may not know=20
>>> how
>>> to
>>> authenticate with the turn server in the local/access network.=20
>>> Making
>>> it a
>>> must would limit discovery and use of turn servers offered by access
>>> networks.
>>
>> I'm curious why this is special for discovered TURN servers vs TURN
>> servers in general. Isn't equally likely that a non-discovered server
>> might want to allow credential free operation?
>>
>> Also, doesn't this create a situation where a client that would=20
>> prefer
>> to authenticate for some reason cannot do so? (That is, the client's
>> only option would be to operate without authentication or choose not=20
>> to
>> communicate.)
>
> It=E2=80=99s special for discovered TURN servers in that discovery is =
for=20
> relay
> provided by either the local or the access network. We=E2=80=99re not=20
> mandating
> that this should be relaxed for all TURN servers, at least =
that=E2=80=99s=20
> not the
> intention.

That sort of reasserts the question. Do people think that TURN servers=20
that are not "discovered" will not reasonably need the same relaxation?=20
(e.g. Maybe I want to widely publish the fact that I run a TURN server=20
that anyone can use?)


>
> But yes, it is a limitation. We do go on to clarify that a client MAY=20
> be
> configured to accept Allocation success responses without STUN
> authentication.
>
> There has been discussion in the WG to make this optional.
>
>>
>>>
>>>>
>>>> So I guess I would like to see some text that explains why this
>>>> change
>>>> is made, and why it's okay, and warning about related risks.
>>>
>>> Sure, we=E2=80=99ll add more text around risks or reorganize a =
little bit;
>>> we=E2=80=99ve
>>> discussed risks in paragraphs 2&3 of Security Considerations.
>>
>> To be clear, I think that discussion is incomplete. RFC 5766=20
>> discusses
>> several security considerations that explicitly mention=20
>> authentication
>> as a mitigating factor. For example, 17.1.1, 17.1.3, 17.1.7, and=20
>> 17.2.1.
>>
>> Those paragraphs (and the bullet list before them) also seem to=20
>> depend
>> on (D)TLS to mitigate some of the issues. But even that is only a
>> SHOULD.
>
> Right, I think we can mandate (D)TLS *if* STUN authentication or
> third-party authorization is not used.

I think that would help.

[Karl] See above!=20

>
>>
>> Additionally, now that I've looked more closely at the TLS language=20
>> in
>> those paragraphs, I have a concern about the statement that
>> communication SHOULD fall back to non-authenticated TLS if
>> authentication fails. I think it's reasonable to allow that, but it
>> should be a very clear administrator choice.
>
> Fallback to unauthenticated (D)TLS should only happen if the user opts =

> for
> opportunistic-encryption. Would you prefer we add a line highlighting=20
> this
> fact?

Yes. Maybe I read things wrong, but I _thought_ I read the text to say=20
you unconditionally SHOULD fallback.

>
>> That is, there should never
>> be a situation where the administrator (and user) think they have
>> authenticated TLS when they do not. This interacts with RFC 5766=20
>> section
>> 17.1.5.
>>
>>>
>>>>
>>>> Finally, I still think this sort of normative change warrants an
>>>> "UPDATES RFC 5766" label.
>>
>> I didn't see a response to this comment. Does that mean you agree? To
>> put a finer point on this, I don't think the current draft makes it
>> sufficiently obvious that it is removing an existing normative
>> requirement to authenticate, and I am concerned that people reviewing
>> the draft during IETF last call may not have noticed that.
>>
>> So to be clear, what I'd like to see is an "Updates RFC 5766" header=20
>> and
>> text that explicitly calls out that the "OPTIONAL" is a downgrade of=20
>> a
>> MUST level authentication requirement in 5766. Once those are in=20
>> place,
>> I think we should consider repeating the IETF last call.
>
> Sure, we=E2=80=99ll make this update.

Thanks!

[...]

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


From nobody Mon Sep 26 13:37:02 2016
Return-Path: <iesg-secretary@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 09A28126FDC; Mon, 26 Sep 2016 13:36:52 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.34.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147492221199.5121.10215021293134571120.idtracker@ietfa.amsl.com>
Date: Mon, 26 Sep 2016 13:36:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/CyuGRvnzXn7xHGCZWm-f3C11OtA>
Cc: tram-chairs@ietf.org, tram@ietf.org, sperreault@jive.com, spencerdawkins.ietf@gmail.com, draft-ietf-tram-turn-mobility@ietf.org, rfc-editor@rfc-editor.org, The IESG <iesg@ietf.org>
Subject: [tram] Protocol Action: 'Mobility with TURN' to Proposed Standard (draft-ietf-tram-turn-mobility-09.txt)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 26 Sep 2016 20:36:52 -0000

The IESG has approved the following document:
- 'Mobility with TURN'
  (draft-ietf-tram-turn-mobility-09.txt) as Proposed Standard

This document is the product of the TURN Revised and Modernized Working
Group.

The IESG contact persons are Mirja Kühlewind and Spencer Dawkins.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-tram-turn-mobility/





Technical Summary

The intent of this document is to define a mechanism for TURN allocations to
survive a client IP address change. A new "mobility ticket" attribute allows the
client to migrate to a new IP address using a make-before-break approach.

The requested publication type is Proposed Standard because new TURN attributes
and behavior are defined.

Working Group Summary

The draft was discussed actively in the MMUSIC working group, under the name
MICE, before it was refocused and transferred to TRAM. Once in TRAM there were
few iterations: the WG was roughly happy with the document as it was. A few good
reviews were done by core WG members which resulted in small changes.

Document Quality

Interest in this document has been medium. The mechanism for TURN makes sense
but there are a number of other layers in a SIP/WebRTC stack at which IP address
mobility could be implemented, e.g., trickle ICE, re-INVITE, etc. At this moment
there is no single agreed-upon "how IP address mobility shall be accomplished"
vision and implementations have not yet picked a clear winner. Since the draft
was first proposed in MMUSIC a sort of "wait and see" response had been slowing
progress.  Today it seems like there won't be a clear decision and the consensus
is that publishing the TURN mechanism is what makes most sense at this point.

Personnel

Document shepherd: Simon Perreault <sperreault@jive.com>
Responsible Area Director: Spencer Dawkins <spencerdawkins.ietf@gmail.com>


From nobody Thu Sep 29 21:57:28 2016
Return-Path: <gsalguei@cisco.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 B740E12B047; Thu, 29 Sep 2016 21:57:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.836
X-Spam-Level: 
X-Spam-Status: No, score=-16.836 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 UG9Gnup1hg-u; Thu, 29 Sep 2016 21:57:07 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D2BA12B032; Thu, 29 Sep 2016 21:57:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13083; q=dns/txt; s=iport; t=1475211427; x=1476421027; h=from:to:cc:subject:date:message-id:references: mime-version; bh=ZZ4s4/r+awJQinkSY3NrzLAGcmXoBx4TXVPvT871aBw=; b=fFtHnqd5FDiijWRks1Mz1Jli7y82lxG5gg4SzzX38sWHMVGYLN6yJmNB jamkEuemmruP0ROTKIBo9EgFYW4dj3pSKHogEmSoXDTEQ+oHZDeW11HSt +hFIyKUfnRA+auZjWtPZn98EDZ4IFTG1iDH7iVbdO9FWlVlRSwoztbmoP U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BxAQB28O1X/4QNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgz8BAQEBAR5XfAeNK5Z/jxGFEoIGGQEKhXoCgWI4FAECAQEBAQE?= =?us-ascii?q?BAV4nhGEBAQEEAQEBSyALEAIBGQMBAg0XBAcnCgEUBwIIAgQBDQUUBwIEiCwOv?= =?us-ascii?q?hEBAQEBAQEBAQEBAQEBAQEBAQEBAQEchjeBfYJYgTyCaT8WCIJxgi8FlCCFWAG?= =?us-ascii?q?GJolJgW6EZokchwqFY4N8AQ8PNoMqJ4E4cgGEUoEggQABAQE?=
X-IronPort-AV: E=Sophos;i="5.31,418,1473120000";  d="scan'208,217";a="157581336"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 30 Sep 2016 04:56:48 +0000
Received: from XCH-RCD-008.cisco.com (xch-rcd-008.cisco.com [173.37.102.18]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id u8U4umlh028782 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 30 Sep 2016 04:56:48 GMT
Received: from xch-aln-009.cisco.com (173.36.7.19) by XCH-RCD-008.cisco.com (173.37.102.18) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 29 Sep 2016 23:56:47 -0500
Received: from xch-aln-009.cisco.com ([173.36.7.19]) by XCH-ALN-009.cisco.com ([173.36.7.19]) with mapi id 15.00.1210.000; Thu, 29 Sep 2016 23:56:48 -0500
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: "tls@ietf.org" <tls@ietf.org>, tram mailing list <tram@ietf.org>, "mmusic (E-mail)" <mmusic@ietf.org>, "ice@ietf.org" <ice@ietf.org>
Thread-Topic: [rfc-dist] RFC 7983 on Multiplexing Scheme Updates for Secure Real-time Transport Protocol (SRTP) Extension for Datagram	Transport Layer Security (DTLS)
Thread-Index: AQHSGtcMkIgOG8WjjUyLYahvQZrBPA==
Date: Fri, 30 Sep 2016 04:56:48 +0000
Message-ID: <8BBC2CED-70E8-4EB7-8D44-11054856AB7B@cisco.com>
References: <20160929234041.C84C0B81109@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.169.55]
Content-Type: multipart/alternative; boundary="_000_8BBC2CED70E84EB78D4411054856AB7Bciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/Q0Kw8kErDFHZfnZ8E9KOTkJPJ48>
Cc: IETF AVTCore WG <avt@ietf.org>
Subject: [tram] Fwd: [rfc-dist] RFC 7983 on Multiplexing Scheme Updates for Secure Real-time Transport Protocol (SRTP) Extension for Datagram	Transport Layer Security (DTLS)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
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, 30 Sep 2016 04:57:10 -0000

--_000_8BBC2CED70E84EB78D4411054856AB7Bciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Forwarding for awareness to the other relevant WGs. Thanks to all who helpe=
d get this done.

Cheers,

Gonzalo

Begin forwarded message:

From: <rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>>
Subject: [rfc-dist] RFC 7983 on Multiplexing Scheme Updates for Secure Real=
-time Transport Protocol (SRTP) Extension for Datagram Transport Layer Secu=
rity (DTLS)
Date: September 29, 2016 at 7:40:41 PM EDT
To: <ietf-announce@ietf.org<mailto:ietf-announce@ietf.org>>, <rfc-dist@rfc-=
editor.org<mailto:rfc-dist@rfc-editor.org>>
Cc: <drafts-update-ref@iana.org<mailto:drafts-update-ref@iana.org>>, <avt@i=
etf.org<mailto:avt@ietf.org>>, <rfc-editor@rfc-editor.org<mailto:rfc-editor=
@rfc-editor.org>>

A new Request for Comments is now available in online RFC libraries.


       RFC 7983

       Title:      Multiplexing Scheme Updates for Secure
                   Real-time Transport Protocol (SRTP) Extension for
                   Datagram Transport Layer Security (DTLS)
       Author:     M. Petit-Huguenin, G. Salgueiro
       Status:     Standards Track
       Stream:     IETF
       Date:       September 2016
       Mailbox:    marc@petit-huguenin.org<mailto:marc@petit-huguenin.org>,
                   gsalguei@cisco.com<mailto:gsalguei@cisco.com>
       Pages:      13
       Characters: 24894
       Updates:    RFC 5764

       I-D Tag:    draft-ietf-avtcore-rfc5764-mux-fixes-11.txt

       URL:        https://www.rfc-editor.org/info/rfc7983

       DOI:        http://dx.doi.org/10.17487/RFC7983

This document defines how Datagram Transport Layer Security (DTLS),
Real-time Transport Protocol (RTP), RTP Control Protocol (RTCP),
Session Traversal Utilities for NAT (STUN), Traversal Using Relays
around NAT (TURN), and ZRTP packets are multiplexed on a single
receiving socket.  It overrides the guidance from RFC 5764 ("SRTP
Extension for DTLS"), which suffered from four issues described and
fixed in this document.

This document updates RFC 5764.

This document is a product of the Audio/Video Transport Core Maintenance Wo=
rking Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestion=
s
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
 https://www.ietf.org/mailman/listinfo/ietf-announce
 https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org<mailto:rfc-e=
ditor@rfc-editor.org>.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org<mailto:rfc-dist@rfc-editor.org>
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org


--_000_8BBC2CED70E84EB78D4411054856AB7Bciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <4286A44DF83DD04997FF9238A01E5991@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;" class=3D"">
<div dir=3D"auto" style=3D"word-wrap: break-word; -webkit-nbsp-mode: space;=
 -webkit-line-break: after-white-space;" class=3D"">
Forwarding for awareness to the other relevant WGs. Thanks to all who helpe=
d get this done.
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Cheers,</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Gonzalo<br class=3D"">
<div><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">Begin forwarded message:</div>
<br class=3D"Apple-interchange-newline">
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">From:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D"">&lt;<a href=3D"mailto:rfc-editor@rfc-ed=
itor.org" class=3D"">rfc-editor@rfc-editor.org</a>&gt;<br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Subject:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D""><b class=3D"">[rfc-dist] RFC 7983 on Mu=
ltiplexing Scheme Updates for Secure Real-time Transport Protocol (SRTP) Ex=
tension for Datagram Transport Layer Security
 (DTLS)</b><br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Date:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D"">September 29, 2016 at 7:40:41 PM EDT<br=
 class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">To:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D"">&lt;<a href=3D"mailto:ietf-announce@iet=
f.org" class=3D"">ietf-announce@ietf.org</a>&gt;, &lt;<a href=3D"mailto:rfc=
-dist@rfc-editor.org" class=3D"">rfc-dist@rfc-editor.org</a>&gt;<br class=
=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica,=
 sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Cc:
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica Neue,=
 Helvetica, sans-serif;" class=3D"">&lt;<a href=3D"mailto:drafts-update-ref=
@iana.org" class=3D"">drafts-update-ref@iana.org</a>&gt;, &lt;<a href=3D"ma=
ilto:avt@ietf.org" class=3D"">avt@ietf.org</a>&gt;, &lt;<a href=3D"mailto:r=
fc-editor@rfc-editor.org" class=3D"">rfc-editor@rfc-editor.org</a>&gt;<br c=
lass=3D"">
</span></div>
<br class=3D"">
<div class=3D"">
<div class=3D"">A new Request for Comments is now available in online RFC l=
ibraries.<br class=3D"">
<br class=3D"">
<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;RFC 7983<br class=3D"">
<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Title: &nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;Multiplexing Scheme Updates for Secure <br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Real-time Transport Protocol (SRTP) =
Extension for <br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Datagram Transport Layer Security (D=
TLS) <br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Author: &nbsp;&nbsp;&nbsp;&nbsp;M=
. Petit-Huguenin, G. Salgueiro<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Status: &nbsp;&nbsp;&nbsp;&nbsp;S=
tandards Track<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Stream: &nbsp;&nbsp;&nbsp;&nbsp;I=
ETF<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Date: &nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;September 2016<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Mailbox: &nbsp;&nbsp;&nbsp;<a hre=
f=3D"mailto:marc@petit-huguenin.org" class=3D"">marc@petit-huguenin.org</a>=
,
<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"mailto:gsalguei@cisco.com=
" class=3D"">gsalguei@cisco.com</a><br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Pages: &nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;13<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Characters: 24894<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Updates: &nbsp;&nbsp;&nbsp;RFC 57=
64<br class=3D"">
<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;I-D Tag: &nbsp;&nbsp;&nbsp;draft-=
ietf-avtcore-rfc5764-mux-fixes-11.txt<br class=3D"">
<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;URL: &nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;<a href=3D"https://www.rfc-editor.org/info/rfc7983" class=3D"=
">https://www.rfc-editor.org/info/rfc7983</a><br class=3D"">
<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DOI: &nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;<a href=3D"http://dx.doi.org/10.17487/RFC7983" class=3D"">htt=
p://dx.doi.org/10.17487/RFC7983</a><br class=3D"">
<br class=3D"">
This document defines how Datagram Transport Layer Security (DTLS),<br clas=
s=3D"">
Real-time Transport Protocol (RTP), RTP Control Protocol (RTCP),<br class=
=3D"">
Session Traversal Utilities for NAT (STUN), Traversal Using Relays<br class=
=3D"">
around NAT (TURN), and ZRTP packets are multiplexed on a single<br class=3D=
"">
receiving socket. &nbsp;It overrides the guidance from RFC 5764 (&quot;SRTP=
<br class=3D"">
Extension for DTLS&quot;), which suffered from four issues described and<br=
 class=3D"">
fixed in this document.<br class=3D"">
<br class=3D"">
This document updates RFC 5764.<br class=3D"">
<br class=3D"">
This document is a product of the Audio/Video Transport Core Maintenance Wo=
rking Group of the IETF.<br class=3D"">
<br class=3D"">
This is now a Proposed Standard.<br class=3D"">
<br class=3D"">
STANDARDS TRACK: This document specifies an Internet Standards Track<br cla=
ss=3D"">
protocol for the Internet community, and requests discussion and suggestion=
s<br class=3D"">
for improvements. &nbsp;Please refer to the current edition of the Official=
<br class=3D"">
Internet Protocol Standards (<a href=3D"https://www.rfc-editor.org/standard=
s" class=3D"">https://www.rfc-editor.org/standards</a>) for the
<br class=3D"">
standardization state and status of this protocol. &nbsp;Distribution of th=
is <br class=3D"">
memo is unlimited.<br class=3D"">
<br class=3D"">
This announcement is sent to the IETF-Announce and rfc-dist lists.<br class=
=3D"">
To subscribe or unsubscribe, see<br class=3D"">
&nbsp;<a href=3D"https://www.ietf.org/mailman/listinfo/ietf-announce" class=
=3D"">https://www.ietf.org/mailman/listinfo/ietf-announce</a><br class=3D""=
>
&nbsp;<a href=3D"https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist" =
class=3D"">https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist</a><br =
class=3D"">
<br class=3D"">
For searching the RFC series, see <a href=3D"https://www.rfc-editor.org/sea=
rch" class=3D"">
https://www.rfc-editor.org/search</a><br class=3D"">
For downloading RFCs, see <a href=3D"https://www.rfc-editor.org/retrieve/bu=
lk" class=3D"">
https://www.rfc-editor.org/retrieve/bulk</a><br class=3D"">
<br class=3D"">
Requests for special distribution should be addressed to either the<br clas=
s=3D"">
author of the RFC in question, or to <a href=3D"mailto:rfc-editor@rfc-edito=
r.org" class=3D"">
rfc-editor@rfc-editor.org</a>. &nbsp;Unless<br class=3D"">
specifically noted otherwise on the RFC itself, all RFCs are for<br class=
=3D"">
unlimited distribution.<br class=3D"">
<br class=3D"">
<br class=3D"">
The RFC Editor Team<br class=3D"">
Association Management Solutions, LLC<br class=3D"">
<br class=3D"">
<br class=3D"">
_______________________________________________<br class=3D"">
rfc-dist mailing list<br class=3D"">
<a href=3D"mailto:rfc-dist@rfc-editor.org" class=3D"">rfc-dist@rfc-editor.o=
rg</a><br class=3D"">
https://www.rfc-editor.org/mailman/listinfo/rfc-dist<br class=3D"">
http://www.rfc-editor.org<br class=3D"">
</div>
</div>
</blockquote>
</div>
<br class=3D"">
</div>
</div>
</body>
</html>

--_000_8BBC2CED70E84EB78D4411054856AB7Bciscocom_--

