Search RFCs
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 listbehave@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 canbe impossible for that host to communicate directly with other hosts(peers). In these situations, it is necessary for the host to usethe services of an intermediate node that acts as a communicationrelay. This specification defines a protocol, called TURN (TraversalUsing Relays around NAT), that allows the host to control theoperation of the relay and to exchange packets with its peers usingthe relay. TURN differs from some other relay control protocols inthat it allows a client to communicate with multiple peers using asingle relay address. [STANDARDS-TRACK]
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.