RFC 5766
Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN), April 2010
- File formats:
- Status:
- PROPOSED STANDARD
- Obsoleted by:
- RFC 8656
- Updated by:
- RFC 8155, RFC 8553
- Authors:
- R. Mahy
P. Matthews
J. Rosenberg - Stream:
- IETF
- Source:
- behave (tsv)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC5766
Discuss this RFC: Send questions or comments to the mailing list behave@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 5766
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. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.