Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-urn-sub-ns-03.txt

Hannes Tschofenig <hannes.tschofenig@gmx.net> Sat, 23 June 2012 12:39 UTC

Return-Path: <hannes.tschofenig@gmx.net>
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 875BE21F8503 for <oauth@ietfa.amsl.com>; Sat, 23 Jun 2012 05:39:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.516
X-Spam-Level:
X-Spam-Status: No, score=-102.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 73dWSqYrHAXY for <oauth@ietfa.amsl.com>; Sat, 23 Jun 2012 05:39:10 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 709FA21F8507 for <oauth@ietf.org>; Sat, 23 Jun 2012 05:39:10 -0700 (PDT)
Received: (qmail invoked by alias); 23 Jun 2012 12:39:09 -0000
Received: from a88-115-216-191.elisa-laajakaista.fi (EHLO [192.168.100.109]) [88.115.216.191] by mail.gmx.net (mp017) with SMTP; 23 Jun 2012 14:39:09 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/2N2l3cPP2oy+BdowkJM0K5uf8z08Kd5OWL/+Z3h RqWbXxYVP+TDF2
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943665637A0@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Sat, 23 Jun 2012 15:39:08 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <1555CD18-316D-4293-9D13-8BC241F6CB38@gmx.net>
References: <20120621175317.32545.76545.idtracker@ietfa.amsl.com> <CAC4RtVAcnGwv7yp=zwwAM--w-DubHfFpHFrKyHRzfe8Fjfg0Rg@mail.gmail.com> <CA+k3eCS0DYEqk4SDNpWJKJvWZgTqHAkojQVTPuZKmySHPxBR1A@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943665637A0@TK5EX14MBXC283.redmond.corp.microsoft.com>
To: Mike Jones <Michael.Jones@microsoft.com>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 0
Cc: OAuth WG <oauth@ietf.org>, Barry Leiba <barryleiba@computer.org>
Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-urn-sub-ns-03.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: Sat, 23 Jun 2012 12:39:11 -0000

Hi Mike, 

in a previous mail you wanted to even be more flexible by having not only two levels but potentially three levels. 
Now, you say one registry is sufficient. 

That does not make sense. 

Ciao
Hannes

On Jun 21, 2012, at 11:29 PM, Mike Jones wrote:

> I agree that one registry is sufficient.  The number of registrations won't be huge and so having sub-registries seems like overkill.
> 
> 				-- Mike
> 
> -----Original Message-----
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf Of Brian Campbell
> Sent: Thursday, June 21, 2012 12:55 PM
> To: Barry Leiba
> Cc: OAuth WG
> Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-urn-sub-ns-03.txt
> 
> I honestly don't understand the push to have additional registries under urn:ietf:params:oauth?
> 
> On Thu, Jun 21, 2012 at 1:28 PM, Barry Leiba <barryleiba@computer.org> wrote:
>> This one's mostly there.  As Mike and Hannes are discussing, the WG 
>> needs to sort out exactly what goes under "oauth" here.
>> 
>> Here's a suggestion:
>> Have Section 3 specify that what comes after "oauth" are one or more 
>> tokens, delimited by ":".
>> Have Section 3 create the registry for the first-level token, "class".
>>  In your example, that's "grant-type".
>> Have Section 3 specify that the definition of each "class" token 
>> specifies what comes after it -- how many tokens, and the meaning(s).
>> Have Section 3 note that certain classes might create new 
>> sub-registries for what goes under them, if necessary.
>> Have Section 3 note that certain classes might have *no* further 
>> tokens under them.
>> 
>> I realize that there might not be any use cases envisioned right now 
>> for that last one, but it might be a bad idea to forbid it.
>> 
>> Section 5:
>> 
>>   o  Repository: [[not sure about this? this document or
>>      http://www.iana.org/assignments/oauth]]
>> 
>> Yeh, I've never been sure about that either.  I think what you want 
>> here is "[[The registry created in Section 3.]]".
>> See RFC 6134 for how I did this with the "sieve" namespace.
>> 
>> Barry
>> _______________________________________________
>> 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