Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 5766

Authors:

P. Patil
T. Reddy
D. Wing

Stream:

IETF

Source:

tram (tsv)

Cite this RFC:TXT  | XML  |  BibTeX

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

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 8155

Abstract

Current Traversal Using Relays around NAT (TURN) server discoverymechanisms are relatively static and limited to explicitconfiguration. These are usually under the administrative control ofthe application or TURN service provider, and not the enterprise,ISP, or the network in which the client is located. Enterprises andISPs wishing to provide their own TURN servers need auto-discoverymechanisms that a TURN client could use with minimal or noconfiguration. This document describes three such mechanisms forTURN server discovery.

This document updates RFC 5766 to relax the requirement for mutualauthentication in certain cases.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.