Re: [OAUTH-WG] Working Group Versions of Refactored OAuth Dynamic Client Registration Specs

Phil Hunt <phil.hunt@oracle.com> Thu, 06 March 2014 16:25 UTC

Return-Path: <phil.hunt@oracle.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 804891A0092 for <oauth@ietfa.amsl.com>; Thu, 6 Mar 2014 08:25:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.746
X-Spam-Level:
X-Spam-Status: No, score=-4.746 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 krTOg6-Zhofm for <oauth@ietfa.amsl.com>; Thu, 6 Mar 2014 08:25:06 -0800 (PST)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id 55FA11A0051 for <oauth@ietf.org>; Thu, 6 Mar 2014 08:25:06 -0800 (PST)
Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s26GP1nW028023 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 6 Mar 2014 16:25:02 GMT
Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s26GP1T6024525 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 6 Mar 2014 16:25:01 GMT
Received: from abhmp0011.oracle.com (abhmp0011.oracle.com [141.146.116.17]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s26GP0mw024417; Thu, 6 Mar 2014 16:25:00 GMT
Received: from dhcp-a680.meeting.ietf.org (/31.133.166.128) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 06 Mar 2014 08:25:00 -0800
Content-Type: multipart/alternative; boundary="Apple-Mail=_01F377B2-1BE5-470F-9910-20084E328084"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Phil Hunt <phil.hunt@oracle.com>
In-Reply-To: <370d79ce16e24a4997ac444591829e35@BLUPR03MB309.namprd03.prod.outlook.com>
Date: Thu, 6 Mar 2014 16:25:00 +0000
Message-Id: <99FD6D99-DB50-4DB8-AAA6-977742CE1A1E@oracle.com>
References: <4E1F6AAD24975D4BA5B16804296739438B1882D3@TK5EX14MBXC288.redmond.corp.microsoft.com> <532782efb0bd4dd8b69e26905d5250a1@BLUPR03MB309.namprd03.prod.outlook.com> <370d79ce16e24a4997ac444591829e35@BLUPR03MB309.namprd03.prod.outlook.com>
To: Anthony Nadalin <tonynad@microsoft.com>
X-Mailer: Apple Mail (2.1510)
X-Source-IP: ucsinet21.oracle.com [156.151.31.93]
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/xCzDNbwZZftnskYdS-L-Dr87meE
Cc: "oauth@ietf.org list" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Working Group Versions of 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: Thu, 06 Mar 2014 16:25:08 -0000

Where is registration_client_uri  in the spec?

Phil

@independentid
www.independentid.com
phil.hunt@oracle.com

On 2014-03-06, at 4:00 PM, Anthony Nadalin <tonynad@microsoft.com> wrote:

> Same is true for the registration_client_uri as I may not need/want this, should be optional
>  
> From: OAuth [mailto:oauth-bounces@ietf.org] On Behalf Of Anthony Nadalin
> Sent: Thursday, March 6, 2014 7:02 AM
> To: Mike Jones; oauth@ietf.org list
> Subject: Re: [OAUTH-WG] Working Group Versions of Refactored OAuth Dynamic Client Registration Specs
>  
> So the current core makes the registration_access_token  required and there are open registration endpoints, so this should be optional, there are also cases where the client_id is signed and that becomes the right to the registration endpoint
>  
> From: OAuth [mailto:oauth-bounces@ietf.org] On Behalf Of Mike Jones
> Sent: Friday, February 7, 2014 10:58 AM
> To: oauth@ietf.org list
> Subject: [OAUTH-WG] Working Group Versions of Refactored OAuth Dynamic Client Registration Specs
>  
> There are now OAuth working group versions of the refactored OAuth Dynamic Client Registration specifications:
> ·         OAuth 2.0 Dynamic Client Registration Core Protocol
> ·         OAuth 2.0 Dynamic Client Registration Metadata
> ·         OAuth 2.0 Dynamic Client Registration Management Protocol
>  
> These versions address review comments by Phil Hunt and Tony Nadalin.  Phil is now also an author.  The data structures and messages used are the same as the previous versions.
>  
> The drafts are available at:
> ·         http://tools.ietf.org/html/draft-ietf-oauth-dyn-reg-16
> ·         http://tools.ietf.org/html/draft-ietf-oauth-dyn-reg-metadata-00
> ·         http://tools.ietf.org/html/draft-ietf-oauth-dyn-reg-management-00
>  
> HTML formatted versions are also available at:
> ·         https://self-issued.info/docs/draft-ietf-oauth-dyn-reg-16.html
> ·         https://self-issued.info/docs/draft-ietf-oauth-dyn-reg-metadata-00.html
> ·         https://self-issued.info/docs/draft-ietf-oauth-dyn-reg-management-00.html
>  
>                                                             -- Mike
>  
> P.S.  I also posted this notice at http://self-issued.info/?p=1180 and as @selfissued.
>  
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth