RFC 8155: Traversal Using Relays around NAT (TURN) Server Auto Discovery

Current Traversal Using Relays around NAT (TURN) server discovery mechanisms are relatively static and limited to explicit configuration. These are usually…

Read RFC 8155 on the RFC Editor

Outgoing relationships (14 related RFCs)

Updates, Normative reference — RFC 5766: Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 2132: DHCP Options and BOOTP Vendor Extensions
Normative reference — RFC 2136: Dynamic Updates in the Domain Name System (DNS UPDATE)
Normative reference — RFC 6762: Multicast DNS
Normative reference — RFC 7250: Using Raw Public Keys in Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
Normative reference — RFC 6890: Special-Purpose IP Address Registries
Normative reference — RFC 5986: Discovering the Local Location Information Server (LIS)
Normative reference — RFC 5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism
Normative reference — RFC 6024: Trust Anchor Management Requirements
Informative reference — RFC 7469: Public Key Pinning Extension for HTTP
Informative reference — RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)
Informative reference — RFC 3188: Using National Bibliography Numbers as Uniform Resource Names
Informative reference — RFC 8016: Mobility with Traversal Using Relays around NAT (TURN)

Incoming relationships (3 related RFCs)

Informatively referenced by — RFC 8825: Overview: Real-Time Protocols for Browser-Based Applications
Informatively referenced by — RFC 8835: Transports for WebRTC
Informatively referenced by — RFC 8656: Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)