Subject: Re: REVISED Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard

From: Stephen Farrell <[email-masked]>
Date: Tue, 24 Jan 2012 15:06:37 +0000

Folks,

The OAuth bearer and base last calls had to be re-done
since I forgot to include some downref information. Other
than adding a day to IETF LC, there should be no other
difference.

Sorry about that.

S

On 01/24/2012 03:00 PM, The IESG wrote:
>
> The IESG has received a request from the Web Authorization Protocol WG
> (oauth) to consider the following document:
> - 'The OAuth 2.0 Authorization Protocol: Bearer Tokens'
>    <draft-ietf-oauth-v2-bearer-15.txt>  as a Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> [email-masked] mailing lists by 2012-02-07. Exceptionally, comments may be
> sent to [email-masked] instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This specification describes how to use bearer tokens in HTTP
>     requests to access OAuth 2.0 protected resources.  Any party in
>     possession of a bearer token (a "bearer") can use it to get access to
>     the associated resources (without demonstrating possession of a
>     cryptographic key).  To prevent misuse, bearer tokens need to be
>     protected from disclosure in storage and in transport.
>
>
> * There is a normative reference to RFC 2246 (TLS 1.0), which has been
> obsoleted by RFC 5246 (TLS 1.2).  The document uses this reference to
> note that TLS 1.0 is, at this writing, the most widely deployed
> version.  The working group believes it is necessary to note that, and
> that the reference be normative.
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-oauth-v2-bearer/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-oauth-v2-bearer/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> IETF-Announce mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/ietf-announce
>