Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 8656

Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN),February 2020

File formats:

icon for HTMLicon for text fileicon for v3pdficon for XML
Also available:XML file for editing
 
Status:
PROPOSED STANDARD
Obsoletes:
RFC 5766,RFC 6156
Authors:
T. Reddy, Ed.
A. Johnston, Ed.
P. Matthews
J. Rosenberg
Stream:
IETF
Source:
tram (tsv)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8656

Discuss this RFC: Send questions or comments to the mailing listtram@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8656


Abstract

If a host is located behind a NAT, it can be impossible for that hostto communicate directly with other hosts (peers) in certainsituations. 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 "Traversal UsingRelays around NAT" (TURN), that allows the host to control theoperation of the relay and to exchange packets with its peers usingthe relay. TURN differs from other relay control protocols in that itallows a client to communicate with multiple peers using a singlerelay address.

The TURN protocol was designed to be used as part of the InteractiveConnectivity Establishment (ICE) approach to NAT traversal, though itcan also be used without ICE.

This document obsoletes RFCs 5766 and 6156.


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp