UNLIMITED FREE
ACCESS TO THE WORLD'S BEST IDEAS

SUBMIT
Already a GlobalSpec user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your GlobalSpec Experience

Select Your Free Newsletters

Industry Newsletters

Select Your Free Product Alerts

Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

IETF RFC 7635

Session Traversal Utilities for NAT (STUN) Extension for Third-Party Authorization

active, Most Current
Buy Now
Organization: IETF
Publication Date: 1 August 2015
Status: active
Page Count: 24
scope:

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 History

IETF RFC 7635
August 1, 2015
Session Traversal Utilities for NAT (STUN) Extension for Third-Party Authorization
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...

References

This document references:
IETF RFC 4648 - The Base16, Base32, and Base64 Data Encodings
Published by IETF on October 1, 2006
This document describes the commonly used base 64, base 32, and base 16 encoding schemes. It also discusses the use of line-feeds in encoded data, use of padding in encoded data, use of non-alphabet...
This document references:
IETF RFC 4868 - Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 with IPsec
Published by IETF on May 1, 2007
This specification describes the use of Hashed Message Authentication Mode (HMAC) in conjunction with the SHA-256, SHA-384, and SHA-512 algorithms in IPsec. These algorithms may be used as the basis...
This document references:
IETF RFC 5116 - An Interface and Algorithms for Authenticated Encryption
Published by IETF on January 1, 2008
This document defines algorithms for Authenticated Encryption with Associated Data (AEAD), and defines a uniform interface and a registry for such algorithms. The interface and registry can be used...
This document is referenced by:
IETF RFC 7982 - Measurement of Round-Trip Time and Fractional Loss Using Session Traversal Utilities for NAT (STUN)
Published by IETF on September 1, 2016
A host with multiple interfaces needs to choose the best interface for communication. Oftentimes, this decision is based on a static configuration and does not consider the path characteristics,...
This document is referenced by:
IETF RFC 8016 - Mobility with Traversal Using Relays around NAT (TURN)
Published by IETF on November 1, 2016
It is desirable to minimize traffic disruption caused by changing IP address during a mobility event. One mechanism to minimize disruption is to expose a shorter network path to the mobility event so...
This document is referenced by:
IETF RFC 8155 - Traversal Using Relays around NAT (TURN) Server Auto Discovery
Published by IETF on April 1, 2017
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...
This document is referenced by:
IETF RFC 8656 - Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)
Published by IETF on February 1, 2020
Abstract If a host is located behind a NAT, it can be impossible for that host to communicate directly with other hosts (peers) in certain situations. In these situations, it is necessary for the...
This document is referenced by:
TS 133 203 - Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; 3G security; Access security for IP-based services
Published by ETSI on May 1, 2022
The scope for this technical specification is to specify the security features and mechanisms for secure access to the IM subsystem (IMS) for the 3G mobile telecommunication system. Since the scope...
View Less
View All
Advertisement