IETF Logo Mail Archive

Re: [OAUTH-WG] 'Scope' parameter proposal

Marius Scurtescu <mscurtescu@google.com> Mon, 19 April 2010 18:04 UTC

Return-Path: <mscurtescu@google.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AB6023A692F for <oauth@core3.amsl.com>; Mon, 19 Apr 2010 11:04:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.883
X-Spam-Level:
X-Spam-Status: No, score=-105.883 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Itc07e9zogK1 for <oauth@core3.amsl.com>; Mon, 19 Apr 2010 11:04:08 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 4422F3A68E6 for <oauth@ietf.org>; Mon, 19 Apr 2010 11:04:07 -0700 (PDT)
Received: from hpaq1.eem.corp.google.com (hpaq1.eem.corp.google.com [10.3.21.1]) by smtp-out.google.com with ESMTP id o3JI3sOm031953 for <oauth@ietf.org>; Mon, 19 Apr 2010 11:03:58 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1271700238; bh=UCyXC49gfClMU5o4jlS6XaatmGw=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=utvInZ+VLKCMM4SjSd0cAtRO0ttTojO03k4borLd7vwo6BzkTt0tT9rY3apYqgQpB NOUVAvsujwB4+yuR0qBfg==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:from:date:message-id: subject:to:cc:content-type:x-system-of-record; b=sVjqIDuGVOp1eQnlq+I6IiXwVT5cyCfI5H/URHzKIFiB08jdSRBZt9oaUZk3VxgTP uS0UlhM8hNytaKwCKDu4Q==
Received: from pvg6 (pvg6.prod.google.com [10.241.210.134]) by hpaq1.eem.corp.google.com with ESMTP id o3JI3q4a005679 for <oauth@ietf.org>; Mon, 19 Apr 2010 20:03:53 +0200
Received: by pvg6 with SMTP id 6so3104650pvg.15 for <oauth@ietf.org>; Mon, 19 Apr 2010 11:03:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.141.107.2 with HTTP; Mon, 19 Apr 2010 11:03:32 -0700 (PDT)
In-Reply-To: <C7F1D1FC.32809%eran@hueniverse.com>
References: <C7F1D1FC.32809%eran@hueniverse.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Mon, 19 Apr 2010 11:03:32 -0700
Received: by 10.140.251.10 with SMTP id y10mr4544819rvh.260.1271700232093; Mon, 19 Apr 2010 11:03:52 -0700 (PDT)
Message-ID: <j2q74caaad21004191103l488ae334j78d5546479f66cb8@mail.gmail.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] 'Scope' parameter proposal
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 19 Apr 2010 18:04:08 -0000

On Mon, Apr 19, 2010 at 9:25 AM, Eran Hammer-Lahav <eran@hueniverse.com> wrote:
> Proposal:
>
> 'scope' is defined as a comma-separated list of resource URIs or resource
> groups (e.g. contacts, photos).

How will commas in URIs be escaped? We just forbid them?

If the scope elements are URIs then a space separated list is much
safer, URIs cannot contain spaces.

But, I still don't see the point on trying to define the scope structure.

Marius

v2.23.0 | Report a Bug | By Email