[tram] FW: New Version Notification for draft-patil-tram-turn-serv-disc-01.txt

["Prashanth Patil (praspati)" <[e-mail]>]

A new revision of the TURN server discovery draft has been published.
Notable updates :

* 300 (Try Alternate) response for anycast.
* Mechanism described in draft-kist-alto-3pdisc i.e. using the clients own
address to populate the DNS reverse zone (i.e., in-addr.arpa or ip6.arpa)
with appropriate NAPTR records pointing to the TURN server.
* Learning domain names from own identity.

-Prashanth


On 5/2/14 3:25 PM, "[e-mail]" <[e-mail]>
wrote:

>
>A new version of I-D, draft-patil-tram-turn-serv-disc-01.txt
>has been successfully submitted by Prashanth Patil and posted to the
>IETF repository.
>
>Name:		draft-patil-tram-turn-serv-disc
>Revision:	01
>Title:		TURN Server Auto Discovery
>Document date:	2014-05-02
>Group:		Individual Submission
>Pages:		11
>URL:            
>http://www.ietf.org/internet-drafts/draft-patil-tram-turn-serv-disc-01.txt
>Status:         
>https://datatracker.ietf.org/doc/draft-patil-tram-turn-serv-disc/
>Htmlized:       
>http://tools.ietf.org/html/draft-patil-tram-turn-serv-disc-01
>Diff:           
>http://www.ietf.org/rfcdiff?url2=draft-patil-tram-turn-serv-disc-01
>
>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 or
>   the ISP, 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 two such mechanisms for TURN
>   server discovery.
>
>                  
>        
>
>
>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.
>
>The IETF Secretariat
>