TURN Server Auto Discovery
draft-patil-tram-turn-serv-disc-01

Document Type Replaced Internet-Draft (individual)
Last updated 2014-07-29 (latest revision 2014-05-02)
Replaced by draft-ietf-tram-turn-server-discovery
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html 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)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
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)
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.)