Sending to the right place.
On Oct 18, 2011, at 20:36, "qijun83"
mailto:qiju...@gmail.com>> wrote:
Dear Sir,
It's really very pleasure for me to write to you for asking some questions
about oauth-v2-22 as follows.
In section 2.3 (Client Authentication), it is recommended to use the HTTP Basic
Hi Mike,
based on our discussion I suggest to make the following minor editorial changes
to the specification. Let me provide specific text proposals.
I recommend to extend the abstract a little bit. The current text does not tell
the reader a lot and the RFC editor will require more text (be
Anyone objecting here?
From: Mike Jones
To: William Mills ; John Bradley ;
Eran Hammer-Lahav
Cc: OAuth WG
Sent: Monday, October 17, 2011 3:25 PM
Subject: RE: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Open Issues & Proposed
Resolutions
+1
From:oauth-bou
On 2011-10-18 17:38, Eran Hammer-Lahav wrote:
Space is allowed inside a quoted string and is already not allowed inside each
scope string.
EHL
...
a) yes.
b) well:
The value of the scope parameter is expressed as a list of space-
delimited, case sensitive strings. The strings are def
Space is allowed inside a quoted string and is already not allowed inside each
scope string.
EHL
> -Original Message-
> From: Julian Reschke [mailto:julian.resc...@gmx.de]
> Sent: Tuesday, October 18, 2011 6:50 AM
> To: Eran Hammer-Lahav
> Cc: Hannes Tschofenig; OAuth WG
> Subject: Re: [
On 2011-10-17 20:53, Eran Hammer-Lahav wrote:
All I agree with is to limit the scope character-set in the v2 spec to the subset of
ASCII allowed in HTTP header quoted-string, excluding " and \ so no escaping is
needed, ever.
You also need to have one character reserved as delimiter for multip
