TURN Server Auto Discovery
draft-patil-tram-turn-serv-disc-01
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Prashanth Patil , Tirumaleswar Reddy.K , Dan Wing | ||
| Last updated | 2014-07-29 (latest revision 2014-05-02) | ||
| Replaced by | RFC 8155 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-tram-turn-server-discovery | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-patil-tram-turn-serv-disc-01.txt
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.
Authors
Prashanth Patil
(praspati@cisco.com)
Tirumaleswar Reddy.K
(tireddy@cisco.com)
Dan Wing
(dwing@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)