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

[Mike Jones <[e-mail]>]

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: [e-mail] [mailto:[e-mail]] 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 <[e-mail]> 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
> [e-mail]
> https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________
OAuth mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/oauth