Hi Barry, let me describe what we are trying to do here:
1.) This document creates a new URN with urn:ietf:params:oauth. There are procedures for creating new entries under urn:ietf:params, as described in RFC 3553, and we have them in the document. 2.) We provide guidance on how others then define new sub-registries under urn:ietf:params:oauth. Class refers to concepts like 'grant-type'. This document does not create these sub-registries. Instead, it only provides guidance for doing that and leaves it to other documents, such as to the bearer document. [Note: We should have created these child registries in the document ourselves as well.] Ciao Hannes On Jun 20, 2012, at 9:34 PM, Barry Leiba wrote: > I'd like to see the new version, since there appear to be a bunch of > changes, but first here are some issues that I don't think have been > brought up yet: > > The URN registration stuff seems very incompletely baked. The title > of 5.1 correctly says it's registering a sub-namespace, but the text > incorrectly says that it's creating a registry. Perhaps IANA will > understand, but I think you need to do this in two parts. The first > part would register the "oauth" sub-namespace, and the second would > create a new registry for the things that go into it. > > Now, as to what goes into it: What is "class"? Is there meant to be a > registry of classes? Is that what section 5.1 is trying to create > (which should be done in a new section 5.2)? What initial values are > registered there? > > 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
