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:  10.17487/RFC8155

Discuss this RFC: Send questions or comments to the mailing list tram@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 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.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.