Folks,
I have just uploaded the latest rev of the UMA Core spec.
(draft-hardjono-oauth-umacore-01.txt).
NB. The list of all the co-authors are now at the end of the document.
/thomas/
__
-Original Message-
From: internet-dra...@ietf.org [mailto:
+1
Phil
@independentid
www.independentid.com
phil.h...@oracle.com
On 2011-10-17, at 11:53 AM, 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
+1
From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf Of
William Mills
Sent: Monday, October 17, 2011 1:53 PM
To: John Bradley; Eran Hammer-Lahav
Cc: OAuth WG
Subject: Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Open Issues & Proposed
Resolutions
+1
__
+1
From: John Bradley
To: Eran Hammer-Lahav
Cc: OAuth WG
Sent: Monday, October 17, 2011 12:13 PM
Subject: Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Open Issues & Proposed
Resolutions
+1
On 2011-10-17, at 11:53 AM, Eran Hammer-Lahav wrote:
> All I agree
+1
On 2011-10-17, at 11:53 AM, 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.
>
> EHL
>
>> -Original Message-
>> From: Han
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.
EHL
> -Original Message-
> From: Hannes Tschofenig [mailto:hannes.tschofe...@gmx.net]
> Sent: Monday, Octobe
It is good that we have an agreement among a few people that more text needs to
be provided in the core specification on the issue of the scope element.
Now, there is still the question of what the text should say. The questions
from my earlier mails are therefore still applicable and need an a
What's the current leaning in the core spec. Is there a direction emerging for
this answer?
From: Eran Hammer-Lahav
To: John Bradley ; "Richer, Justin P."
Cc: OAuth WG
Sent: Monday, October 17, 2011 7:27 AM
Subject: Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-
I agree.
EHL
> -Original Message-
> From: John Bradley [mailto:ve7...@ve7jtb.com]
> Sent: Monday, October 17, 2011 6:07 AM
> To: Richer, Justin P.
> Cc: Eran Hammer-Lahav; OAuth WG
> Subject: Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Open Issues &
> Proposed Resolutions
>
> The scope
The scopes cross all of the profiles.
I expect that restricting the character sets for bearer tokens, MAC, and other
future variants should be dealt with in those profiles.
Without restricting scope in core, we leave the possibility of coming up with
different rules in different profiles e.g.
On 2011-10-17 00:54, Eran Hammer-Lahav wrote:
It's an open question for the list.
EHL
...
Well, as long as it is not restricted in the core spec, the bearer spec
will have to handle the case (or document this as known technical
omission, I guess).
Best regards, Julian
_
11 matches
Mail list logo
