I wanted to explicitly call out that draft -03 of the Bearer Token
Specification establishes the OAuth Errors registry to increase
interoperability among the related OAuth specifications. Eran, when you
produce draft -14 of the framework specification, please register the errors in
the specification to comply with this new requirement. Errors in other OAuth
specifications should likewise be registered in updated drafts.
I also wanted to call out that draft -03 augments the OAuth Parameters registry
by adding two additional parameter usage locations: "resource request" and
"resource response". Like parameters for the parameter usage locations
authorization request, authorization response, token request, and token
response, parameters for these usage locations must also be registered.
Eran, if you would prefer, on an editorial basis, to move these OAuth registry
requirements into the framework spec, I would be fine with that. If you do so
in your draft -14, I will remove them from my draft -04.
Best wishes,
-- Mike
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
