Re: [OAUTH-WG] draft-richer-oauth-introspection-01 scope syntax

Craig McClanahan <craigmcc@gmail.com> Wed, 30 January 2013 22:48 UTC

Return-Path: <craigmcc@gmail.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 46B9221F8702 for <oauth@ietfa.amsl.com>; Wed, 30 Jan 2013 14:48:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MJ9je9CL855w for <oauth@ietfa.amsl.com>; Wed, 30 Jan 2013 14:48:01 -0800 (PST)
Received: from mail-lb0-f176.google.com (mail-lb0-f176.google.com [209.85.217.176]) by ietfa.amsl.com (Postfix) with ESMTP id 8D9D521F86F6 for <oauth@ietf.org>; Wed, 30 Jan 2013 14:48:00 -0800 (PST)
Received: by mail-lb0-f176.google.com with SMTP id s4so2730748lbc.35 for <oauth@ietf.org>; Wed, 30 Jan 2013 14:47:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=GEYL1nuJE3gxhOOKRLCT3MT0XfO7+aXKuS3b270uGso=; b=SEt63S8zq/duybI/19snwD2GNQK1h5xHR0gPVMmAKB/GH3FuXFAEbcKLzxWWB8ned2 +T9vi8cY5qo22YtzEDhW8oDFI3vTLkxioH/i4K1aiPAzrzTNgkI+ZxiOx0LBlZq3B+cD MMQmfhv9LRwwNJt9HLYIk/IoBZdB76agM5Dp3nGlLqUeaalGnOqcYNgkjpQxPlfX13QM TTXNFNNuJKPBN+ysO4l4dtCpCqoT9P45utFxvnuzhBNKv04nu1Qh74xSRSgrjrXPRCLq aYrKBaibanEBTVhRy3uACPHF0tEOyKk2ImTLFcnQnz45vo7edehCKsXPmT3FfU53b9kj nonQ==
MIME-Version: 1.0
X-Received: by 10.152.147.103 with SMTP id tj7mr6024820lab.54.1359586074411; Wed, 30 Jan 2013 14:47:54 -0800 (PST)
Received: by 10.152.21.199 with HTTP; Wed, 30 Jan 2013 14:47:54 -0800 (PST)
In-Reply-To: <51099EBD.5050204@mitre.org>
References: <OF3031393A.750F4AB2-ON85257B03.007AD84B-85257B03.007B56E7@us.ibm.com> <51099EBD.5050204@mitre.org>
Date: Wed, 30 Jan 2013 14:47:54 -0800
Message-ID: <CANgkmLCR+mNFPHBQZfKsDDdUwcArJcSSOpYewqKNhGbhJEZByQ@mail.gmail.com>
From: Craig McClanahan <craigmcc@gmail.com>
To: Justin Richer <jricher@mitre.org>
Content-Type: multipart/alternative; boundary="e89a8f234d2b01c36604d4894d73"
Cc: IETF oauth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] draft-richer-oauth-introspection-01 scope syntax
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: craigmcc@gmail.com
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, 30 Jan 2013 22:48:02 -0000

On Wed, Jan 30, 2013 at 2:29 PM, Justin Richer <jricher@mitre.org> wrote:

> We could fairly easily define it as the same space-delimited string if
> enough people want to keep the scope format consistent.
>
>
Can't we have our cake and eat it too, and accept either syntax?  JSON
makes it pretty easy to introspect what's there and deal with either
version appropriately.

I am one of those that finds the array version of things like this more
convenient, but for the folks who are used to dealing with the
space-delimited string version of scopes, we could easily support that too.


>  -- Justin
>
> Craig McClanahan