Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Open Issues & Proposed Resolutions

[Julian Reschke <[e-mail]>]

On 2011-10-14 17:42, Mike Jones wrote:
> Thanks for the useful discussion and the write-up, Hannes. For context,
> Hannes and I discussed how to resolve the remaining Bearer spec issues
> in a manner that meets the needs of implementations and will not
> generate objections during the IESG or IETF Last Call reviews. A few
> additional comments…
>
> 1. Error Description – Nothing to add to Hannes’ write-up.
>
> 2. Scope – I was planning to allow a broader set of ASCII characters
> than the “token” set, as these characters are inadequate for the use of
> URIs/URLs as scope elements. In particular, scope elements need to
> permit the full sets of “reserved”
> <http://tools.ietf.org/html/rfc3986#section-2.2>and “unreserved”
> <http://tools.ietf.org/html/rfc3986#section-2.3>characters in RFC 3986
> <http://tools.ietf.org/html/rfc3986>. The draft I am working on will say
> that scope is a space separated set of elements, where the elements
> consist of one or more characters from the union of the “reserved” and
> “unreserved” sets.
> ...

If you do that, you'll need to be careful with the encoding in case you 
stick with x-www-url-encoded (SP -> "+" etc).

Best regards, Julian