Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Open Issues & Proposed Resolutions
Eran Hammer-Lahav <eran@hueniverse.com> Wed, 19 October 2011 17:38 UTC
Return-Path: <eran@hueniverse.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71D7B11E80AA for <oauth@ietfa.amsl.com>; Wed, 19 Oct 2011 10:38:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.428
X-Spam-Level:
X-Spam-Status: No, score=-2.428 tagged_above=-999 required=5 tests=[AWL=0.171, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oYfwhUOTdPuy for <oauth@ietfa.amsl.com>; Wed, 19 Oct 2011 10:38:10 -0700 (PDT)
Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by ietfa.amsl.com (Postfix) with SMTP id CB2B821F8AA8 for <oauth@ietf.org>; Wed, 19 Oct 2011 10:38:09 -0700 (PDT)
Received: (qmail 8112 invoked from network); 19 Oct 2011 17:38:08 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.21) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 19 Oct 2011 17:38:08 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.19]) by P3PW5EX1HT003.EX1.SECURESERVER.NET ([72.167.180.21]) with mapi; Wed, 19 Oct 2011 10:37:52 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Marius Scurtescu <mscurtescu@google.com>, Mike Jones <Michael.Jones@microsoft.com>
Date: Wed, 19 Oct 2011 10:37:45 -0700
Thread-Topic: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Open Issues & Proposed Resolutions
Thread-Index: AcyOhOb3g/TR3CRHRq2vcVSflBdr8wAANHtg
Message-ID: <90C41DD21FB7C64BB94121FBBC2E723452631E8F4C@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <4E1F6AAD24975D4BA5B16804296739435C24A747@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAGdjJpJE4djD6SRM1d+NDHCPRF6oOcEPJzHoBF8Mdy5a6HJiLw@mail.gmail.com>
In-Reply-To: <CAGdjJpJE4djD6SRM1d+NDHCPRF6oOcEPJzHoBF8Mdy5a6HJiLw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Open Issues & Proposed Resolutions
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2011 17:38:11 -0000
I don't think defining them as URI's is helpful here. But the set must be inclusive of URI characters. EHL > -----Original Message----- > From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf > Of Marius Scurtescu > Sent: Wednesday, October 19, 2011 10:31 AM > To: Mike Jones > Cc: OAuth WG > Subject: Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Open Issues & > Proposed Resolutions > > On Wed, Oct 19, 2011 at 10:26 AM, Mike Jones > <Michael.Jones@microsoft.com> wrote: > > Yes, it covers all the characters legal in URIs. Per earlier discussion on the > list, scopes are not restricted to being URIs, as existing practice includes > scope elements that are not URIs such as "email" "profile", and "openid". > > All those simple words are URIs. They are relative URIs (just the path), but > URIs nonetheless. > > Marius > > > > > -- Mike > > > > -----Original Message----- > > From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf > > Of Marius Scurtescu > > Sent: Wednesday, October 19, 2011 10:24 AM > > To: Julian Reschke > > Cc: OAuth WG > > Subject: Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Open Issues & > > Proposed Resolutions > > > > Marius > > > > > > > > On Tue, Oct 18, 2011 at 9:39 AM, Julian Reschke <julian.reschke@gmx.de> > wrote: > >> 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 defined by the > >> authorization server. If the value contains multiple > >> space-delimited > >> strings, their order does not matter, and each string adds an > >> additional access range to the requested scope. > >> > >> That certainly implies that you can't have a space inside a token, > >> but it could be clearer. > >> > >> Optimally, state the character repertoire precisely: > >> > >> scopetokenchar = %x21 / %x23-5B / %x5D-7E > >> ; HTTPbis P1 qdtext except whitespace, restricted to US-ASCII > >> > >> ? > > > > Is this covering all characters allowed in a URI? Why not define scopes as a > list of URIs? > > > >> > >> Best regards, Julian > >> _______________________________________________ > >> OAuth mailing list > >> OAuth@ietf.org > >> https://www.ietf.org/mailman/listinfo/oauth > >> > > _______________________________________________ > > OAuth mailing list > > OAuth@ietf.org > > https://www.ietf.org/mailman/listinfo/oauth > > > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth
- [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Open Is… Hannes Tschofenig
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Mike Jones
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Julian Reschke
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Eran Hammer-Lahav
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Julian Reschke
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Mike Jones
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… William Mills
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Mike Jones
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Julian Reschke
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Eran Hammer-Lahav
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Hannes Tschofenig
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Mike Jones
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Hannes Tschofenig
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Mike Jones
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Hannes Tschofenig
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Mike Jones
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… John Bradley
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Julian Reschke
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Mike Jones
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Julian Reschke
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Mike Jones
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Julian Reschke
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Eran Hammer-Lahav
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… John Bradley
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Richer, Justin P.
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Julian Reschke
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… John Bradley
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Eran Hammer-Lahav
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… William Mills
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Hannes Tschofenig
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Eran Hammer-Lahav
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… John Bradley
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… William Mills
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Mike Jones
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Phil Hunt
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Julian Reschke
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Eran Hammer-Lahav
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Julian Reschke
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… William Mills
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Marius Scurtescu
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Mike Jones
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Marius Scurtescu
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Eran Hammer-Lahav
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Julian Reschke
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… William Mills
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Marius Scurtescu
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… William Mills
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Julian Reschke
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Mike Jones
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Eran Hammer
- Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Ope… Eran Hammer