Re: [OAUTH-WG] OAuth WG Re-Chartering
Igor Faynberg <igor.faynberg@alcatel-lucent.com> Wed, 14 March 2012 20:26 UTC
Return-Path: <igor.faynberg@alcatel-lucent.com>
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 3265221F8828 for <oauth@ietfa.amsl.com>; Wed, 14 Mar 2012 13:26:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.549
X-Spam-Level:
X-Spam-Status: No, score=-9.549 tagged_above=-999 required=5 tests=[AWL=1.050, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 msB3+8REsBVD for <oauth@ietfa.amsl.com>; Wed, 14 Mar 2012 13:26:09 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 2467C21F8826 for <oauth@ietf.org>; Wed, 14 Mar 2012 13:26:08 -0700 (PDT)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id q2EKQ8Qw007743 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <oauth@ietf.org>; Wed, 14 Mar 2012 15:26:08 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q2EKQ7xs008465 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <oauth@ietf.org>; Wed, 14 Mar 2012 15:26:08 -0500
Received: from [135.222.134.168] (USMUYN0L055118.mh.lucent.com [135.222.134.168]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q2EKQ7Z0029122; Wed, 14 Mar 2012 15:26:07 -0500 (CDT)
Message-ID: <4F60FEDF.1030600@alcatel-lucent.com>
Date: Wed, 14 Mar 2012 16:26:07 -0400
From: Igor Faynberg <igor.faynberg@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: oauth@ietf.org
References: <B327D847-B059-41D7-A468-8B8A5DB8BFCE@gmx.net>
In-Reply-To: <B327D847-B059-41D7-A468-8B8A5DB8BFCE@gmx.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Subject: Re: [OAUTH-WG] OAuth WG Re-Chartering
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: igor.faynberg@alcatel-lucent.com
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: Wed, 14 Mar 2012 20:26:10 -0000
Looks good and comprehensive to me. Igor On 3/14/2012 4:21 PM, Hannes Tschofenig wrote: > So, here is a proposal: > > ------- > > Web Authorization Protocol (oauth) > > Description of Working Group > > The Web Authorization (OAuth) protocol allows a user to grant > a third-party Web site or application access to the user's protected > resources, without necessarily revealing their long-term credentials, > or even their identity. For example, a photo-sharing site that supports > OAuth could allow its users to use a third-party printing Web site to > print their private pictures, without allowing the printing site to > gain full control of the user's account and without having the user > sharing his or her photo-sharing sites' long-term credential with the > printing site. > > The OAuth protocol suite encompasses > * a procedure for allowing a client to discover a resource server, > * a protocol for obtaining authorization tokens from an authorization > server with the resource owner's consent, > * protocols for presenting these authorization tokens to protected > resources for access to a resource, and > * consequently for sharing data in a security and privacy respective way. > > In April 2010 the OAuth 1.0 specification, documenting pre-IETF work, > was published as an informational document (RFC 5849). With the > completion of OAuth 1.0 the working group started their work on OAuth 2.0 > to incorporate implementation experience with version 1.0, additional > use cases, and various other security, readability, and interoperability > improvements. An extensive security analysis was conducted and the result > is available as a stand-alone document offering guidance for audiences > beyond the community of protocol implementers. > > The working group also developed security schemes for presenting authorization > tokens to access a protected resource. This led to the publication of > the bearer token as well as the message authentication code (MAC) access > authentication specification. > > OAuth 2.0 added the ability to trade a SAML assertion against an OAUTH token with > the SAML 2.0 bearer assertion profile. This offers interworking with existing > identity management solutions, in particular SAML based deployments. > > OAuth has enjoyed widespread adoption by the Internet application service provider > community. To build on this success we aim for nothing more than to make OAuth the > authorization framework of choice for any Internet protocol. Consequently, the > ongoing standardization effort within the OAuth working group is focused on > enhancing interoperability of OAuth deployments. While the core OAuth specification > truly is an important building block it relies on other specifications in order to > claim completeness. Luckily, these components already exist and have been deployed > on the Internet. Through the IETF standards process they will be improved in > quality and will undergo a rigorous review process. > > Goals and Milestones > > [Editor's Note: Here are the completed items.] > > Done Submit 'OAuth 2.0 Threat Model and Security Considerations' as a working group item > Done Submit 'HTTP Authentication: MAC Authentication' as a working group item > Done Submit 'The OAuth 2.0 Protocol: Bearer Tokens' to the IESG for consideration as a Proposed Standard > Done Submit 'The OAuth 2.0 Authorization Protocol' to the IESG for consideration as a Proposed Standard > > [Editor's Note: Finishing existing work. Double-check the proposed dates - are they realistic?] > > Jun. 2012 Submit 'HTTP Authentication: MAC Authentication' to the IESG for consideration as a Proposed Standard > Apr. 2012 Submit 'SAML 2.0 Bearer Assertion Profiles for OAuth 2.0' to the IESG for consideration as a Proposed Standard > Apr. 2012 Submit 'OAuth 2.0 Assertion Profile' to the IESG for consideration as a Proposed Standard > Apr. 2012 Submit 'An IETF URN Sub-Namespace for OAuth' to the IESG for consideration as a Proposed Standard > May 2012 Submit 'OAuth 2.0 Threat Model and Security Considerations' to the IESG for consideration as an Informational RFC > > [Editor's Note: New work for the group. 5 items maximum! ] > > Aug. 2012 Submit 'Token Revocation' to the IESG for consideration as a Proposed Standard > > [Starting point for the work will be http://datatracker.ietf.org/doc/draft-lodderstedt-oauth-revocation/] > > Nov. 2012 Submit 'JSON Web Token (JWT)' to the IESG for consideration as a Proposed Standard > > [Starting point for the work will be http://tools.ietf.org/html/draft-jones-json-web-token] > > Nov. 2012 Submit 'JSON Web Token (JWT) Bearer Token Profiles for OAuth 2.0' to the IESG for consideration as a Proposed Standard > > [Starting point for the work will be http://tools.ietf.org/html/draft-jones-oauth-jwt-bearer] > > Jan. 2013 Submit 'OAuth Dynamic Client Registration Protocol' to the IESG for consideration as a Proposed Standard > > [Starting point for the work will be http://tools.ietf.org/html/draft-hardjono-oauth-dynreg] > > Sep. 2012 Submit 'OAuth Use Cases' to the IESG for consideration as an Informational RFC > > [Starting point for the work will be http://tools.ietf.org/html/draft-zeltsan-oauth-use-cases] > > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth
- [OAUTH-WG] OAuth WG Re-Chartering Hannes Tschofenig
- Re: [OAUTH-WG] OAuth WG Re-Chartering Igor Faynberg
- Re: [OAUTH-WG] OAuth WG Re-Chartering Eran Hammer
- Re: [OAUTH-WG] OAuth WG Re-Chartering Richer, Justin P.
- Re: [OAUTH-WG] OAuth WG Re-Chartering Mike Jones
- Re: [OAUTH-WG] OAuth WG Re-Chartering Eran Hammer
- Re: [OAUTH-WG] OAuth WG Re-Chartering Richer, Justin P.
- Re: [OAUTH-WG] OAuth WG Re-Chartering Eran Hammer
- Re: [OAUTH-WG] OAuth WG Re-Chartering Anthony Nadalin
- Re: [OAUTH-WG] OAuth WG Re-Chartering Eran Hammer
- Re: [OAUTH-WG] OAuth WG Re-Chartering Nat Sakimura
- Re: [OAUTH-WG] OAuth WG Re-Chartering Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [OAUTH-WG] OAuth WG Re-Chartering Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [OAUTH-WG] OAuth WG Re-Chartering Paul Madsen
- Re: [OAUTH-WG] OAuth WG Re-Chartering John Bradley
- Re: [OAUTH-WG] OAuth WG Re-Chartering Paul Madsen
- Re: [OAUTH-WG] OAuth WG Re-Chartering Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [OAUTH-WG] OAuth WG Re-Chartering John Bradley
- Re: [OAUTH-WG] OAuth WG Re-Chartering Blaine Cook
- Re: [OAUTH-WG] OAuth WG Re-Chartering Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [OAUTH-WG] OAuth WG Re-Chartering Paul Madsen
- Re: [OAUTH-WG] OAuth WG Re-Chartering Richer, Justin P.
- Re: [OAUTH-WG] OAuth WG Re-Chartering Paul Madsen
- Re: [OAUTH-WG] OAuth WG Re-Chartering Eran Hammer
- Re: [OAUTH-WG] OAuth WG Re-Chartering Zeltsan, Zachary (Zachary)
- Re: [OAUTH-WG] OAuth WG Re-Chartering Mike Jones
- Re: [OAUTH-WG] OAuth WG Re-Chartering Blaine Cook
- Re: [OAUTH-WG] OAuth WG Re-Chartering John Bradley
- Re: [OAUTH-WG] OAuth WG Re-Chartering Phil Hunt
- Re: [OAUTH-WG] OAuth WG Re-Chartering John Bradley
- Re: [OAUTH-WG] OAuth WG Re-Chartering Torsten Lodderstedt
- Re: [OAUTH-WG] OAuth WG Re-Chartering Torsten Lodderstedt
- Re: [OAUTH-WG] OAuth WG Re-Chartering Torsten Lodderstedt
- Re: [OAUTH-WG] OAuth WG Re-Chartering John Bradley
- Re: [OAUTH-WG] OAuth WG Re-Chartering Eran Hammer
- Re: [OAUTH-WG] OAuth WG Re-Chartering George Fletcher
- Re: [OAUTH-WG] OAuth WG Re-Chartering Torsten Lodderstedt
- Re: [OAUTH-WG] OAuth WG Re-Chartering Torsten Lodderstedt
- Re: [OAUTH-WG] OAuth WG Re-Chartering John Bradley
- Re: [OAUTH-WG] OAuth WG Re-Chartering George Fletcher
- Re: [OAUTH-WG] OAuth WG Re-Chartering Mike Jones
- Re: [OAUTH-WG] OAuth WG Re-Chartering Phil Hunt
- Re: [OAUTH-WG] OAuth WG Re-Chartering Eran Hammer
- Re: [OAUTH-WG] OAuth WG Re-Chartering John Bradley
- Re: [OAUTH-WG] OAuth WG Re-Chartering Phil Hunt
- Re: [OAUTH-WG] OAuth WG Re-Chartering Mike Jones
- Re: [OAUTH-WG] OAuth WG Re-Chartering Justin Richer
- Re: [OAUTH-WG] OAuth WG Re-Chartering Phil Hunt