Traversal Using Relay NAT (TURN)
draft-rosenberg-midcom-turn-08
| Document | Type |
Replaced Internet-Draft
(individual in tsv area)
Expired & archived
|
|
|---|---|---|---|
| Author | Jonathan Rosenberg | ||
| Last updated | 2006-03-23 (Latest revision 2005-09-12) | ||
| Replaced by | draft-ietf-behave-turn | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | WG state | (None) | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-behave-turn | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Jon Peterson | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Traversal Using Relay NAT (TURN) is a protocol that allows for an element behind a NAT or firewall to receive incoming data over TCP or UDP connections. It is most useful for elements behind symmetric NATs or firewalls that wish to be on the receiving end of a connection to a single peer. TURN does not allow for users to run servers on well known ports if they are behind a nat; it supports the connection of a user behind a nat to only a single peer. In that regard, its role is to provide the same security functions provided by symmetric NATs and firewalls, but to "turn" them into port- restricted NATs.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)