Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)
draft-johnston-tram-turnbis-01

Document Type Expired Internet-Draft (individual)
Last updated 2015-02-11 (latest revision 2014-08-10)
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 Expired
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-johnston-tram-turnbis-01.txt

Abstract

If a host is located behind a NAT, then in certain situations it can be impossible for that host to communicate directly with other hosts (peers). In these situations, it is necessary for the host to use the services of an intermediate node that acts as a communication relay. This specification defines a protocol, called TURN (Traversal Using Relays around NAT), that allows the host to control the operation of the relay and to exchange packets with its peers using the relay. TURN differs from some other relay control protocols in that it allows a client to communicate with multiple peers using a single relay address. The TURN protocol was designed to be used as part of the ICE (Interactive Connectivity Establishment) approach to NAT traversal, though it also can be used without ICE.

Authors

Reddy K (tireddy@cisco.com)
Alan Johnston (alan.b.johnston@gmail.com)
Rohan Mahy (rohan@ekabal.com)
Philip Matthews (philip_matthews@magma.ca)
Jonathan Rosenberg (jdrosen@jdrosen.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)