Re: [OAUTH-WG] Proposal for single JSON response format
Dick Hardt <dick.hardt@gmail.com> Thu, 10 June 2010 20:34 UTC
Return-Path: <dick.hardt@gmail.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 1CA8C3A6784 for <oauth@core3.amsl.com>; Thu, 10 Jun 2010 13:34:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.19
X-Spam-Level:
X-Spam-Status: No, score=-2.19 tagged_above=-999 required=5 tests=[AWL=0.409, BAYES_00=-2.599]
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 3NdICgnXZTtp for <oauth@core3.amsl.com>; Thu, 10 Jun 2010 13:34:38 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id 2D4813A6783 for <oauth@ietf.org>; Thu, 10 Jun 2010 13:34:38 -0700 (PDT)
Received: by pwi8 with SMTP id 8so150739pwi.31 for <oauth@ietf.org>; Thu, 10 Jun 2010 13:34:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=agpvgcTTPksoQE5SymUDlgjPoZz3sWRR630dFtFb09U=; b=WoaFOfT74DimHVMIvgZ8tHhmJ5NnywQGS7TP5VJ2Eceq1aovIrl/lB86oNfSeYW58v 5rMqNsJ7nEH7WV0gCUETR1s5HHyASzJ/DcoY4K5D7BiMnA9W4E10bEjdkLdIlg9TCg34 JVyMnvWq3b15hDf0hEslU1KVy++pCr/ma4m4g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=Lt00tqYjZzMIewmxVvjh/KLuRkjTWgYxeKVfqhXn0l/j4feTbtDFmZgmnVQteJQjLT ZP6fUwf8RfEUU6ylM59Ws66GGUgw7WcijsEKKIjYqRm6RciSDXIfqEAaAjrIMEeJAc46 O+vhlYK0RP0ooEmeQCsJG1WuxPmqXxK/FC8U0=
Received: by 10.141.88.14 with SMTP id q14mr517799rvl.183.1276202078047; Thu, 10 Jun 2010 13:34:38 -0700 (PDT)
Received: from [10.0.1.15] (c-24-130-32-55.hsd1.ca.comcast.net [24.130.32.55]) by mx.google.com with ESMTPS id k17sm381329rvh.5.2010.06.10.13.34.37 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 10 Jun 2010 13:34:37 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset="us-ascii"
From: Dick Hardt <dick.hardt@gmail.com>
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E72343B3EAF73EF@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Date: Thu, 10 Jun 2010 13:34:36 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <09258F6B-9AB7-4318-A2C1-AB29C495842C@gmail.com>
References: <90C41DD21FB7C64BB94121FBBC2E72343B3EAF73EF@P3PW5EX1MB01.EX1.SECURESERVER.NET>
To: Eran Hammer-Lahav <eran@hueniverse.com>
X-Mailer: Apple Mail (2.1078)
Cc: "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Proposal for single JSON response format
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: Thu, 10 Jun 2010 20:34:39 -0000
+1
On 2010-06-10, at 1:29 PM, Eran Hammer-Lahav wrote:
> After taking a break from our previous debate(s) on the issue of which response format to support, I would like to suggest the following:
>
> - Support a single response format (including in the user-agent fragment) using JSON.
>
> My reason for this is very simple, while right now we have a very limited need (key/value pairs), we already have a few proposals which require a richer syntax. As OAuth matures, I expect more and more extensions to make use of the server response to include additional parameters (flat or structured). By using JSON, we can very easily support "namespaces" (i.e. { "access_token":"xyz","ext":{...} }), multiple token in a single response, etc.
>
> I appreciate the simplicity in using form-encoded (both code and library dependency wise), but long term, it will create a real limitation and will require extensions to also specify a different response format.
>
> Those worried about the need to include a JSON library in cases where it will be hard to do (embedded devices, etc.), can always extend the protocol to provide a way to receive key/value form-encoded pairs. However, they will need to figure out how to accommodate structured responses if they wish support it. I am certain that the vast majority of implementations will have no problem including a JSON library.
>
> Please respond only with yes or no (+/- 1). If you have a different proposal, please post it in a new thread. If you are going to vote against this, please indicate if your objection is blocking (i.e. you are opposed to it and will block a consensus call with this approach).
>
> EHL
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
- [OAUTH-WG] Proposal for single JSON response form… Eran Hammer-Lahav
- Re: [OAUTH-WG] Proposal for single JSON response … Justin Hart
- Re: [OAUTH-WG] Proposal for single JSON response … Eran Hammer-Lahav
- Re: [OAUTH-WG] Proposal for single JSON response … Brian Eaton
- Re: [OAUTH-WG] Proposal for single JSON response … Dick Hardt
- Re: [OAUTH-WG] Proposal for single JSON response … Dick Hardt
- Re: [OAUTH-WG] Proposal for single JSON response … Michael D Adams
- Re: [OAUTH-WG] Proposal for single JSON response … David Recordon
- Re: [OAUTH-WG] Proposal for single JSON response … Justin Richer
- Re: [OAUTH-WG] Proposal for single JSON response … Torsten Lodderstedt
- Re: [OAUTH-WG] Proposal for single JSON response … Chuck Mortimore
- Re: [OAUTH-WG] Proposal for single JSON response … Brian Eaton
- Re: [OAUTH-WG] Proposal for single JSON response … Nat
- Re: [OAUTH-WG] Proposal for single JSON response … Manger, James H
- Re: [OAUTH-WG] Proposal for single JSON response … Luke Shepard
- Re: [OAUTH-WG] Proposal for single JSON response … Naitik Shah
- Re: [OAUTH-WG] Proposal for single JSON response … Robert Sayre
- Re: [OAUTH-WG] Proposal for single JSON response … Evan Gilbert
- Re: [OAUTH-WG] Proposal for single JSON response … Eran Hammer-Lahav
- Re: [OAUTH-WG] Proposal for single JSON response … Evan Gilbert
- Re: [OAUTH-WG] Proposal for single JSON response … Dick Hardt
- Re: [OAUTH-WG] Proposal for single JSON response … Evan Gilbert
- Re: [OAUTH-WG] Proposal for single JSON response … Dick Hardt
- Re: [OAUTH-WG] Proposal for single JSON response … Eran Hammer-Lahav
- Re: [OAUTH-WG] Proposal for single JSON response … Evan Gilbert
- Re: [OAUTH-WG] Proposal for single JSON response … Dirk Balfanz