Re: [tram] I-D Action: draft-ietf-tram-turn-server-discovery-12.txt

Just so it's clear on the list ...

The new text in this draft does indeed represent the compromise position 
re: (D)TLS that I had previously proposed on the list, and I agree with 
Tiru and the chairs that it should clear the remaining DISCUSS. [I know 
I'm a little late to chime in on that last point, but later discussion 
on the list suggests that a supportive comment might still be useful.]

--Brandon

On 01/12/2017 10:59 PM, Tirumaleswar Reddy (tireddy) wrote:
> This revision addresses comments from Brandon.
>
> -Tiru
>
>
>> -----Original Message-----
>> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of internet-
>> drafts@ietf.org
>> Sent: Friday, January 13, 2017 9:28 AM
>> To: i-d-announce@ietf.org
>> Cc: tram@ietf.org
>> Subject: [tram] I-D Action: draft-ietf-tram-turn-server-discovery-12.txt
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> This draft is a work item of the TURN Revised and Modernized of the IETF.
>>
>>         Title           : TURN Server Auto Discovery
>>         Authors         : Prashanth Patil
>>                           Tirumaleswar Reddy
>>                           Dan Wing
>> 	Filename        : draft-ietf-tram-turn-server-discovery-12.txt
>> 	Pages           : 16
>> 	Date            : 2017-01-12
>>
>> Abstract:
>>    Current Traversal Using Relays around NAT (TURN) server discovery
>>    mechanisms are relatively static and limited to explicit
>>    configuration.  These are usually under the administrative control of
>>    the application or TURN service provider, and not the enterprise,
>>    ISP, or the network in which the client is located.  Enterprises and
>>    ISPs wishing to provide their own TURN servers need auto discovery
>>    mechanisms that a TURN client could use with no or minimal
>>    configuration.  This document describes three such mechanisms for
>>    TURN server discovery.
>>
>>    This draft updates [RFC5766] to relax the requirement for mutual
>>    authentication in certain cases.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-tram-turn-server-discovery/
>>
>> There's also a htmlized version available at:
>> https://tools.ietf.org/html/draft-ietf-tram-turn-server-discovery-12
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-tram-turn-server-discovery-12
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> tram mailing list
>> tram@ietf.org
>> https://www.ietf.org/mailman/listinfo/tram
>
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram
>

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