RFC 6062: Traversal Using Relays around NAT (TURN) Extensions for TCP Allocations
In plain English — editorial summary, not part of the RFC
This specification defines an extension of Traversal Using Relays around NAT (TURN), a relay protocol for Network Address Translator (NAT) traversal. This extension allows a TURN client to request TCP allocations, and defines new requests and indications for the TURN server to open and accept TCP connections with the client\'s peers. TURN and this extension both purposefully restrict the ways in which the relayed address can be used. In particular, it prevents users from running general-purpose servers from ports obtained from the TURN server. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6062
- Published
- November 2010
- Authors
- S. Perreault; J. Rosenberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5766Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)Obsoleted
April 2010
- RFC 5389Session Traversal Utilities for NAT (STUN)Obsoleted
October 2008
- RFC 8656Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)Current
February 2020
- RFC 6156Traversal Using Relays around NAT (TURN) Extension for IPv6Obsoleted
April 2011
- RFC 7635Session Traversal Utilities for NAT (STUN) Extension for Third-Party AuthorizationCurrent
August 2015
- RFC 7983Multiplexing Scheme Updates for Secure Real-time Transport Protocol (SRTP) Extension for Datagram Transport Layer Security (DTLS)Updated
September 2016
- RFC 9443Multiplexing Scheme Updates for QUICCurrent
July 2023
- RFC 6052IPv6 Addressing of IPv4/IPv6 TranslatorsCurrent
October 2010
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?