[OAUTH-WG] RFC 7521 on Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants

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

        RFC 7521

        Title:      Assertion Framework for OAuth 2.0 
                    Client Authentication and Authorization Grants 
        Author:     B. Campbell, C. Mortimore,
                    M. Jones, Y. Goland
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2015
        Mailbox:    brian.d.campbell@gmail.com, 
                    cmortimore@salesforce.com, 
                    mbj@microsoft.com,
                    yarong@microsoft.com
        Pages:      20
        Characters: 44458
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-oauth-assertions-18.txt

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

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

This specification provides a framework for the use of assertions
with OAuth 2.0 in the form of a new client authentication mechanism
and a new authorization grant type.  Mechanisms are specified for
transporting assertions during interactions with a token endpoint;
general processing rules are also specified.

The intent of this specification is to provide a common framework for
OAuth 2.0 to interwork with other identity systems using assertions
and to provide alternative client authentication mechanisms.

Note that this specification only defines abstract message flows and
processing rules.  In order to be implementable, companion
specifications are necessary to provide the corresponding concrete
instantiations.

This document is a product of the Web Authorization Protocol 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