RFC 8155: Traversal Using Relays around NAT (TURN) Server Auto Discovery
In plain English — editorial summary, not part of the RFC
Current Traversal Using Relays around NAT (TURN) server discovery mechanisms are relatively static and limited to explicit configuration. These are usually under the administrative control of the application or TURN service provider, and not the enterprise, ISP, or the network in which the client is located. Enterprises and ISPs wishing to provide their own TURN servers need auto-discovery mechanisms that a TURN client could use with minimal or no configuration. This document describes three such mechanisms for TURN server discovery. This document updates RFC 5766 to relax the requirement for mutual authentication in certain cases.
Document record
- Document ID
- RFC8155
- Published
- April 2017
- Authors
- P. Patil; T. Reddy; D. Wing
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 16
- Also known as
- —
- Updates:
- RFC 5766
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8087The Benefits of Using Explicit Congestion Notification (ECN)Current
March 2017
- RFC 8041Use Cases and Operational Experience with Multipath TCPCurrent
January 2017
- RFC 8034Active Queue Management (AQM) Based on Proportional Integral Controller Enhanced (PIE) for Data-Over-Cable Service Interface Specifications (DOCSIS) Cable ModemsCurrent
February 2017
- RFC 8033Proportional Integral Controller Enhanced (PIE): A Lightweight Control Scheme to Address the Bufferbloat ProblemCurrent
February 2017
- RFC 8289Controlled Delay Active Queue ManagementCurrent
January 2018
- RFC 8290The Flow Queue CoDel Packet Scheduler and Active Queue Management AlgorithmCurrent
January 2018
- RFC 8016Mobility with Traversal Using Relays around NAT (TURN)Current
November 2016
- RFC 8298Self-Clocked Rate Adaptation for MultimediaCurrent
December 2017
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?