metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 5766: Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8656.

Current document in this lineage: RFC 8656 — Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC5766
Published
April 2010
Authors
R. Mahy; P. Matthews; J. Rosenberg
Status
PROPOSED STANDARD
Stream
IETF
Area
tsv
Pages
67
Also known as
—
Obsoleted by:
RFC 8656
Updated by:
RFC 8155, RFC 8553

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 5766 (2010)
  2. RFC 6156 (2011)
  3. RFC 8656 (2020) ✓

Read the full history of Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN) →

Referenced by

3 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/5766-traversal-using-relays-around-nat-turn-relay-extensions-to-session-traversal-uti