RFC 7635: Session Traversal Utilities for NAT (STUN) Extension for Third-Party Authorization
In plain English — editorial summary, not part of the RFC
This document proposes the use of OAuth 2.0 to obtain and validate ephemeral tokens that can be used for Session Traversal Utilities for NAT (STUN) authentication. The usage of ephemeral tokens ensures that access to a STUN server can be controlled even if the tokens are compromised.
Document record
- Document ID
- RFC7635
- Published
- August 2015
- Authors
- T. Reddy; P. Patil; R. Ravindranath; J. Uberti
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- 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 6062Traversal Using Relays around NAT (TURN) Extensions for TCP AllocationsCurrent
November 2010
- 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 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 8016Mobility with Traversal Using Relays around NAT (TURN)Current
November 2016
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?