Re: [OAUTH-WG] OAuth specs in IETF last call

Stephen Farrell <stephen.farrell@cs.tcd.ie> Mon, 23 January 2012 17:32 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B76721F86CF for <oauth@ietfa.amsl.com>; Mon, 23 Jan 2012 09:32:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sDeSVWPecMdA for <oauth@ietfa.amsl.com>; Mon, 23 Jan 2012 09:32:58 -0800 (PST)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 5839221F84A2 for <oauth@ietf.org>; Mon, 23 Jan 2012 09:32:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 76C71171C08 for <oauth@ietf.org>; Mon, 23 Jan 2012 17:32:57 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1327339976; bh=BHX2MChT1bUlX7 L/tdPEG3yIJiL6K5Cmf39XFjCZdoU=; b=cHm/+M4Zumw3huTC+olkp9ahFieDgy vqOZEJiWOTjHUceVjao93JzztmIy1rOnNOk9b8bEYzoks9qNcOm2zWiq3FRyf3m8 6hBI5XttABlZviU6BZlPPzk6w6Ql1tmIWLcjjJxiM6O2fkz7IC7cKDReAumtUOvi RYZM9CTTSm1Zi9q0Q1Xps/jHQnwTmW5TJDaj1Mfi6lv0XewctF9v4he0We4BhGp7 srXsbeLtq7pElzBMpdFlpNhApsihRos5vyo2XNnWSRp0Ful6FOb13LCzEQ7ED6pc QmyO1VvR3qsSR8v/U4Yc0hh8LEcgqL3v1PTmKL2OHJ98PtUcMJROhvMw==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id FvTgWZzZBfCZ for <oauth@ietf.org>; Mon, 23 Jan 2012 17:32:56 +0000 (GMT)
Received: from [10.1.1.138] (wifi.ist.utl.pt [193.136.128.57]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 14362171C06 for <oauth@ietf.org>; Mon, 23 Jan 2012 17:32:56 +0000 (GMT)
Message-ID: <4F1D99C7.7050606@cs.tcd.ie>
Date: Mon, 23 Jan 2012 17:32:55 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: oauth@ietf.org
References: <4E1F6AAD24975D4BA5B168042967394366375EB9@TK5EX14MBXC284.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B168042967394366375EB9@TK5EX14MBXC284.redmond.corp.microsoft.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [OAUTH-WG] OAuth specs in IETF last call
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jan 2012 17:32:59 -0000

On 01/23/2012 05:11 PM, Mike Jones wrote:
> FYI, the OAuth Core and Bearer specifications have reached IETF last call status - the last step before becoming RFCs.  See the following notes from the Internet Engineering Steering Group (IESG).

Not quite the last step. There may be directorate reviews,
then IESG evaluation follows, then the RFC editor queue.

But we're getting there:-)

S

>
> 				-- Mike
>
> -----Original Message-----
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf Of The IESG
> Sent: Monday, January 23, 2012 7:44 AM
> To: IETF-Announce
> Cc: oauth@ietf.org
> Subject: [OAUTH-WG] Last Call:<draft-ietf-oauth-v2-23.txt>  (The OAuth 2.0 Authorization Protocol) to Proposed Standard
>
>
> The IESG has received a request from the Web Authorization Protocol WG
> (oauth) to consider the following document:
> - 'The OAuth 2.0 Authorization Protocol'
>    <draft-ietf-oauth-v2-23.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 ietf@ietf.org mailing lists by 2012-02-06. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     The OAuth 2.0 authorization protocol enables a third-party
>     application to obtain limited access to an HTTP service, either on
>     behalf of a resource owner by orchestrating an approval interaction
>     between the resource owner and the HTTP service, or by allowing the
>     third-party application to obtain access on its own behalf.  This
>     specification replaces and obsoletes the OAuth 1.0 protocol described
>     in RFC 5849.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-oauth-v2/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-oauth-v2/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
>
> -----Original Message-----
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf Of The IESG
> Sent: Monday, January 23, 2012 7:47 AM
> To: IETF-Announce
> Cc: oauth@ietf.org
> Subject: [OAUTH-WG] Last Call:<draft-ietf-oauth-v2-bearer-15.txt>  (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard
>
>
> 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 ietf@ietf.org mailing lists by 2012-02-06. Exceptionally, comments may be sent to iesg@ietf.org 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.
>
>
>
>
> 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.
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>