Re: [OAUTH-WG] IETF #89 OAuth Meeting Notes

Phil Hunt <phil.hunt@oracle.com> Thu, 06 March 2014 13:59 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 7ABA61A0156 for <oauth@ietfa.amsl.com>; Thu, 6 Mar 2014 05:59:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.747
X-Spam-Level:
X-Spam-Status: No, score=-4.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 45RajGI1pHlv for <oauth@ietfa.amsl.com>; Thu, 6 Mar 2014 05:59:44 -0800 (PST)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 3C2D61A0078 for <oauth@ietf.org>; Thu, 6 Mar 2014 05:59:44 -0800 (PST)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s26Dxcmf010500 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 6 Mar 2014 13:59:39 GMT
Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by ucsinet22.oracle.com (8.14.5+Sun/8.14.5) with ESMTP id s26Dxbeo010197 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Mar 2014 13:59:38 GMT
Received: from abhmp0019.oracle.com (abhmp0019.oracle.com [141.146.116.25]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s26Dxb7T022141; Thu, 6 Mar 2014 13:59:37 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 05:59:37 -0800
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Phil Hunt <phil.hunt@oracle.com>
In-Reply-To: <b36ff76316f94f95ba387e2054888a95@BLUPR03MB309.namprd03.prod.outlook.com>
Date: Thu, 6 Mar 2014 13:59:36 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <641CC82B-0599-49AB-9515-632EDCD9192F@oracle.com>
References: <531729EB.8050802@gmx.net> <346018d1df7534a815c267bfcc920cd8@lodderstedt.net> <19fab520a70b4065b587a32a31f69470@BLUPR03MB309.namprd03.prod.outlook.com> <4E1F6AAD24975D4BA5B16804296739439A0C3D8F@TK5EX14MBXC286.redmond.corp.microsoft.com> <b36ff76316f94f95ba387e2054888a95@BLUPR03MB309.namprd03.prod.outlook.com>
To: Anthony Nadalin <tonynad@microsoft.com>
X-Mailer: Apple Mail (2.1510)
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/dOCzhom97KjbZzmtzbKzgGdd8t0
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] IETF #89 OAuth Meeting Notes
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 13:59:46 -0000

I'm getting the impression you don't want the particular meta data that's been specified. Hence why you want the separate spec.

What's the issue?  Maybe we should change the metadata?

I'd rather not see people do similar things that are done different ways. Whatever we do is already breaking for us, so nows the time to change it.

Phil

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

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

> +1  should not be merged
> 
> -----Original Message-----
> From: Mike Jones 
> Sent: Thursday, March 6, 2014 5:19 AM
> To: Anthony Nadalin; torsten@lodderstedt.net; oauth@ietf.org
> Subject: RE: [OAUTH-WG] IETF #89 OAuth Meeting Notes
> 
> I also disagree with moving "scope" into the core registration spec.  The metadata values in the core spec are those that are essential to use to achieve registration.  Those in the metadata spec are those that are useful in some applications but not needed by some others.  "scope" is of the second class.
> 
> 				-- Mike
> 
> -----Original Message-----
> From: OAuth [mailto:oauth-bounces@ietf.org] On Behalf Of Anthony Nadalin
> Sent: Thursday, March 06, 2014 1:37 AM
> To: torsten@lodderstedt.net; oauth@ietf.org
> Subject: Re: [OAUTH-WG] IETF #89 OAuth Meeting Notes
> 
> I'm not convinced that scope should be in core
> 
> -----Original Message-----
> From: OAuth [mailto:oauth-bounces@ietf.org] On Behalf Of torsten@lodderstedt.net
> Sent: Thursday, March 6, 2014 12:38 AM
> To: oauth@ietf.org
> Subject: Re: [OAUTH-WG] IETF #89 OAuth Meeting Notes
> 
> Hi,
> 
> regarding dynamic client registration: it has been suggested to merge core and meta data, or at least move some elements (such as scopes) to the core spec. Would you please add this?
> 
> regards,
> Torsten.
> 
> Am 05.03.2014 13:43, schrieb Hannes Tschofenig:
>> Hi al
>> 
>> here are the notes from the OAuth f2f meeting this week:
>> http://www.ietf.org/proceedings/89/minutes/minutes-89-oauth
>> 
>> They are rather short! If someone took some more detailed notes please 
>> send us a mail.
>> 
>> Ciao
>> Hannes & Derek
>> 
>> 
>> _______________________________________________
>> 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
> 
> _______________________________________________
> 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