[OAUTH-WG] Refactored OAuth Dynamic Client Registration Specs
Mike Jones <Michael.Jones@microsoft.com> Tue, 28 January 2014 10:14 UTC
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 634F21A023A for <oauth@ietfa.amsl.com>; Tue, 28 Jan 2014 02:14:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8wTlw67FZitm for <oauth@ietfa.amsl.com>; Tue, 28 Jan 2014 02:13:59 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0189.outbound.protection.outlook.com [207.46.163.189]) by ietfa.amsl.com (Postfix) with ESMTP id E693B1A01ED for <oauth@ietf.org>; Tue, 28 Jan 2014 02:13:58 -0800 (PST)
Received: from DM2PR03CA007.namprd03.prod.outlook.com (10.141.52.155) by BLUPR03MB151.namprd03.prod.outlook.com (10.255.212.25) with Microsoft SMTP Server (TLS) id 15.0.859.15; Tue, 28 Jan 2014 10:13:54 +0000
Received: from BN1BFFO11FD035.protection.gbl (2a01:111:f400:7c10::1:195) by DM2PR03CA007.outlook.office365.com (2a01:111:e400:2414::27) with Microsoft SMTP Server (TLS) id 15.0.859.15 via Frontend Transport; Tue, 28 Jan 2014 10:13:54 +0000
Received: from mail.microsoft.com (131.107.125.37) by BN1BFFO11FD035.mail.protection.outlook.com (10.58.144.98) with Microsoft SMTP Server (TLS) id 15.0.856.14 via Frontend Transport; Tue, 28 Jan 2014 10:13:53 +0000
Received: from TK5EX14MBXC288.redmond.corp.microsoft.com ([169.254.3.129]) by TK5EX14HUBC106.redmond.corp.microsoft.com ([157.54.80.61]) with mapi id 14.03.0174.002; Tue, 28 Jan 2014 10:13:17 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: "oauth@ietf.org" <oauth@ietf.org>
Thread-Topic: Refactored OAuth Dynamic Client Registration Specs
Thread-Index: Ac8cEYoyNPJ4Z7PMTzysfZ8oqcBcxQ==
Date: Tue, 28 Jan 2014 10:13:16 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739438A6BD38E@TK5EX14MBXC288.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.32]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739438A6BD38ETK5EX14MBXC288r_"
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009001)(199002)(189002)(46102001)(51856001)(53806001)(81816001)(84326002)(76176001)(85306002)(76482001)(92726001)(87266001)(87936001)(85852003)(2656002)(93136001)(83072002)(16236675002)(92566001)(90146001)(56816005)(81686001)(54356001)(86362001)(54316002)(77096001)(56776001)(93516002)(76786001)(76796001)(80976001)(74876001)(83322001)(19580395003)(47446002)(74706001)(74662001)(31966008)(44976005)(512954002)(59766001)(77982001)(55846006)(66066001)(80022001)(65816001)(63696002)(20776003)(33656001)(6806004)(69226001)(19300405004)(79102001)(81542001)(94316002)(71186001)(74366001)(74502001)(4396001)(47976001)(15202345003)(16297215004)(49866001)(15975445006)(47736001)(50986001)(81342001)(6606295002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR03MB151; H:mail.microsoft.com; CLIP:131.107.125.37; FPR:; InfoDomainNonexistentA:1; MX:1; LANG:en;
X-O365ENT-EOP-Header: Message processed by - O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0105DAA385
X-OriginatorOrg: microsoft.com
Subject: [OAUTH-WG] Refactored OAuth Dynamic Client Registration Specs
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 28 Jan 2014 10:14:01 -0000
I've posted an updated set of OAuth Dynamic Client Registration specifications that refactors the previous single specification into three specs: * OAuth 2.0 Dynamic Client Registration Core Protocol * OAuth 2.0 Dynamic Client Registration Metadata * OAuth 2.0 Dynamic Client Registration Management Protocol This refactoring was the result of discussions at IETF 88 in Vancouver, BC<http://www.ietf.org/meeting/88/>. These refactored specifications are compatible with the previous single specification. The Core specification contains only the definitions needed to perform dynamic registrations. It contains a completely rewritten Use Cases appendix, intended to clarify the different ways that dynamic registration can be performed. It also adds the Software Statement abstraction invented by Phil Hunt - enabling assertions to be made and used about the client software being registered. The Metadata specification defines useful client metadata values that are nonetheless not essential to the core, such as "client_name", "logo_uri", and "software_id". These were previously defined in the single dynamic registration spec. The Management specification defines the client management operations Read, Update, and Delete, and addresses client secret rotation. These were previously defined in the single dynamic registration spec. The drafts are available at: * http://tools.ietf.org/html/draft-ietf-oauth-dyn-reg-15 * http://tools.ietf.org/html/draft-jones-oauth-dyn-reg-metadata-00 * http://tools.ietf.org/html/draft-jones-oauth-dyn-reg-management-00 HTML formatted versions are also available at: * https://self-issued.info/docs/draft-ietf-oauth-dyn-reg-15.html * https://self-issued.info/docs/draft-jones-oauth-dyn-reg-metadata-00.html * https://self-issued.info/docs/draft-jones-oauth-dyn-reg-management-00.html These versions build upon prior restructuring work done by both Justin Richer and Phil Hunt. -- Mike P.S. This announcement was also posted at http://self-issued.info/?p=1171 and on Twitter as @selfissued.