Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-dyn-reg-04.txt

Mike Jones <Michael.Jones@microsoft.com> Wed, 09 January 2013 20:06 UTC

Return-Path: <Michael.Jones@microsoft.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 BEB4611E8099 for <oauth@ietfa.amsl.com>; Wed, 9 Jan 2013 12:06:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E3JNwKcItppX for <oauth@ietfa.amsl.com>; Wed, 9 Jan 2013 12:06:48 -0800 (PST)
Received: from NA01-BY2-obe.outbound.protection.outlook.com (na01-by2-obe.ptr.protection.outlook.com [207.46.100.25]) by ietfa.amsl.com (Postfix) with ESMTP id ED2BE21F88B4 for <oauth@ietf.org>; Wed, 9 Jan 2013 12:06:47 -0800 (PST)
Received: from BL2FFO11FD013.protection.gbl (10.173.161.201) by BL2FFO11HUB038.protection.gbl (10.173.160.242) with Microsoft SMTP Server (TLS) id 15.0.596.13; Wed, 9 Jan 2013 20:06:45 +0000
Received: from TK5EX14HUBC104.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD013.mail.protection.outlook.com (10.173.160.221) with Microsoft SMTP Server (TLS) id 15.0.596.13 via Frontend Transport; Wed, 9 Jan 2013 20:06:45 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.24]) by TK5EX14HUBC104.redmond.corp.microsoft.com ([157.54.80.25]) with mapi id 14.02.0318.003; Wed, 9 Jan 2013 20:06:15 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: "Richer, Justin P." <jricher@mitre.org>, "oauth@ietf.org WG" <oauth@ietf.org>
Thread-Topic: [OAUTH-WG] I-D Action: draft-ietf-oauth-dyn-reg-04.txt
Thread-Index: AQHN7e9TFLgrew5pC06P/kOSRWPYophBbFcAgAABFdA=
Date: Wed, 09 Jan 2013 20:06:14 +0000
Message-ID: <4E1F6AAD24975D4BA5B168042967394366A095BB@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <20130108222628.27497.4360.idtracker@ietfa.amsl.com> <B33BFB58CCC8BE4998958016839DE27E06873ECB@IMCMBX01.MITRE.ORG>
In-Reply-To: <B33BFB58CCC8BE4998958016839DE27E06873ECB@IMCMBX01.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.74]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(24454001)(51704002)(377424002)(377454001)(50854002)(13464002)(4396001)(54356001)(46406002)(51856001)(5343655001)(76482001)(31966008)(23726001)(59766001)(55846006)(47776002)(74662001)(53806001)(77982001)(16406001)(56816002)(79102001)(47736001)(33656001)(47976001)(54316002)(46102001)(74502001)(50986001)(50466001)(44976002)(15202345001)(56776001)(49866001)(47446002); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB038; H:TK5EX14HUBC104.redmond.corp.microsoft.com; LANG:en;
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 07215D0470
Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-dyn-reg-04.txt
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: Wed, 09 Jan 2013 20:06:48 -0000

No.  It unnecessarily increases the implementation footprint for servers without providing any essential functionality.

				-- Mike

-----Original Message-----
From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf Of Richer, Justin P.
Sent: Wednesday, January 09, 2013 12:01 PM
To: oauth@ietf.org WG
Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-dyn-reg-04.txt

Someone in the OIDC working group has proposed that we add an explicit "read" function to allow a client to get its registration information from the AS, protected by the Registration Access Token. I'm not opposed to this change, but I personally don't see much utility in it. So, question to the group: Should we support this function?

 -- Justin

On Jan 8, 2013, at 5:26 PM, internet-drafts@ietf.org wrote:

> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Web Authorization Protocol Working Group of the IETF.
> 
> 	Title           : OAuth Dynamic Client Registration Protocol
> 	Author(s)       : Justin Richer
>                          John Bradley
>                          Michael B. Jones
>                          Maciej Machulak
> 	Filename        : draft-ietf-oauth-dyn-reg-04.txt
> 	Pages           : 20
> 	Date            : 2013-01-08
> 
> Abstract:
>   This specification defines an endpoint and protocol for dynamic
>   registration of OAuth Clients at an Authorization Server.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-oauth-dyn-reg
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-oauth-dyn-reg-04
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-oauth-dyn-reg-04
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> 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