Guidance on the request URI structure needed?

[Torsten Lodderstedt]

BC QUESTION: should there some more guidance provided on or requirements around the structure of the URI value? For example it could use the RFC6755 subnamespace and registry and be of the form urn:ietf:params:oauth:request_uri:<<random-part>>, which gives a clear indication of what it is and would keep people from inventing their own URIs.

[Filip Skokan]

I think implementers should be free to either use their own URIs (gives them flexibility), but also have the option to use a registered urn: subnamespace as Brian suggested.

[Brian Campbell]

RFC6755 is arguably one of the most important and impactful documents ever written.

[Torsten Lodderstedt]

transferred to new repo for IETF draft https://github.com/oauthstuff/draft-oauth-par/issues/1