Re: [OAUTH-WG] Gen-ART Telechat review of draft-ietf-oauth-v2-bearer-18.txt

Hi Alexey, About your issue 1: The OAuth Core spec, where "scope" is primarily defined, includes the sentence "The [scope] strings are defined by the authorization server" (see http://tools.ietf.org/html/draft-ietf-oauth-v2-25#section-3.3). I could add that clarification to the Bearer spec as

Re: [OAUTH-WG] Gen-ART Telechat review of draft-ietf-oauth-v2-bearer-18.txt

The "scope" attribute is a space-delimited list of scope values indicating the required scope of the access token for accessing the requested resource. In some cases, the "scope" value will be used when requesting a new access token with sufficient scope of access to utilize the

[OAUTH-WG] Gen-ART Telechat review of draft-ietf-oauth-v2-bearer-18.txt

I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at . Please resolve these comments along with any other Last Call comments you may receive. Document: draft-ietf-oauth-v2-bearer-18.txt Rev

[OAUTH-WG] Fwd: Gen-ART Telechat review of draft-ietf-oauth-v2-25

FYI in case some aren't on i...@ietf.org Having responses to these before Thursday would be good. Its often the case that some AD will turn some of these points into a DISCUSS so good to know what can be cleared up easily and what might need further discussion before the telechat. S O

Re: [OAUTH-WG] [Gen-art] Gen-ART review of draft-ietf-oauth-v2-bearer-15.txt

Hi Mike, On 31/01/2012 10:33, Alexey Melnikov wrote: On 30/01/2012 05:20, Mike Jones wrote: Thanks for your useful feedback, Alexey. Hi Mike, Below, I'll respond to each of your comments. I've also added the OAuth working group to the thread, so they are aware of them as well and can par