[OAUTH-WG] OpenID Connect specs being reviewed as Implementer's Drafts

Mike Jones <Michael.Jones@microsoft.com> Mon, 26 December 2011 21:40 UTC

Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id E4B9621F8C4E for <oauth@ietfa.amsl.com>; Mon, 26 Dec 2011 13:40:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.865
X-Spam-Status: No, score=-1.865 tagged_above=-999 required=5 tests=[AWL=-0.867, BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id xLdQVo39SRel for <oauth@ietfa.amsl.com>; Mon, 26 Dec 2011 13:40:08 -0800 (PST)
Received: from VA3EHSOBE008.bigfish.com (va3ehsobe001.messaging.microsoft.com []) by ietfa.amsl.com (Postfix) with ESMTP id 7EFDC21F8C50 for <oauth@ietf.org>; Mon, 26 Dec 2011 13:40:08 -0800 (PST)
Received: from mail23-va3-R.bigfish.com ( by VA3EHSOBE008.bigfish.com ( with Microsoft SMTP Server id; Mon, 26 Dec 2011 21:39:48 +0000
Received: from mail23-va3 (localhost []) by mail23-va3-R.bigfish.com (Postfix) with ESMTP id 8A971801DB for <oauth@ietf.org>; Mon, 26 Dec 2011 21:39:13 +0000 (UTC)
X-SpamScore: -4
X-BigFish: VS-4(zzc85fh1b0bMzz1202hzz8275ch8275eh8275bh8275dha1495iz2fh2a8h668h839h)
X-Forefront-Antispam-Report: CIP:; KIP:(null); UIP:(null); IPV:NLI; H:TK5EX14HUBC102.redmond.corp.microsoft.com; RD:none; EFVD:NLI
Received-SPF: pass (mail23-va3: domain of microsoft.com designates as permitted sender) client-ip=; envelope-from=Michael.Jones@microsoft.com; helo=TK5EX14HUBC102.redmond.corp.microsoft.com ; icrosoft.com ;
Received: from mail23-va3 (localhost.localdomain []) by mail23-va3 (MessageSwitch) id 1324935551442542_23001; Mon, 26 Dec 2011 21:39:11 +0000 (UTC)
Received: from VA3EHSMHS025.bigfish.com (unknown []) by mail23-va3.bigfish.com (Postfix) with ESMTP id 5C94A2A0042 for <oauth@ietf.org>; Mon, 26 Dec 2011 21:39:11 +0000 (UTC)
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com ( by VA3EHSMHS025.bigfish.com ( with Microsoft SMTP Server (TLS) id; Mon, 26 Dec 2011 21:39:45 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([]) by TK5EX14HUBC102.redmond.corp.microsoft.com ([]) with mapi id 14.02.0247.005; Mon, 26 Dec 2011 13:40:03 -0800
From: Mike Jones <Michael.Jones@microsoft.com>
To: "oauth@ietf.org" <oauth@ietf.org>
Thread-Topic: OpenID Connect specs being reviewed as Implementer's Drafts
Thread-Index: AczEFuuhaYjI8faFQoiOqgTjHef8nA==
Date: Mon, 26 Dec 2011 21:39:59 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739435F78D06E@TK5EX14MBXC283.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739435F78D06ETK5EX14MBXC283r_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
Subject: [OAUTH-WG] OpenID Connect specs being reviewed as Implementer's Drafts
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, 26 Dec 2011 21:40:10 -0000

FYI, the OpenID Connect<http://openid.net/connect/> specs began a 45 day public review period for adoption as Implementer's Drafts last week.  An Implementer's Drafts is a stable draft that is not yet final, but that is intended for implementation, evaluation, and trial deployment.  Intellectual property protections are granted to implementers for these drafts as well.

These drafts can be thought of as a profile of the OAuth 2.0 and JOSE specs that enables single-sign-on and exchange of claims through the use of JSON and JWT.  They use these OAuth- and JOSE-related specs:

OAuth 2.0 Core
OAuth 2.0 Bearer
OAuth 2.0 Assertions
OAuth 2.0 JWT Assertions Profile
OAuth 2.0 Threat Model
Simple Web Discovery (SWD)
JSON Web Token (JWT)
JSON Web Signature (JWS)
JSON Web Encryption (JWE)
JSON Web Key (JWK)

See these pages for more details:

                                                            -- Mike