[tram] RFC 7635 on Session Traversal Utilities for NAT (STUN) Extension for Third-Party Authorization

A new Request for Comments is now available in online RFC libraries.

        RFC 7635

        Title:      Session Traversal Utilities for NAT 
                    (STUN) Extension for Third-Party Authorization 
        Author:     T. Reddy, P. Patil,
                    R. Ravindranath, J. Uberti
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2015
        Mailbox:    tireddy@cisco.com, 
                    praspati@cisco.com, 
                    rmohanr@cisco.com,
                    justin@uberti.name
        Pages:      24
        Characters: 51753
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tram-turn-third-party-authz-16.txt

        URL:        https://www.rfc-editor.org/info/rfc7635

        DOI:        http://dx.doi.org/10.17487/RFC7635

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.

This document is a product of the TURN Revised and Modernized Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC