Re: [OAUTH-WG] Issue: Authorization endpoint parameter extension policy

Eran Hammer-Lahav <eran@hueniverse.com> Mon, 19 April 2010 18:50 UTC

Return-Path: <eran@hueniverse.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 73C193A696E for <oauth@core3.amsl.com>; Mon, 19 Apr 2010 11:50:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.469
X-Spam-Level:
X-Spam-Status: No, score=-2.469 tagged_above=-999 required=5 tests=[AWL=0.130, 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 psajFR+nOLXO for <oauth@core3.amsl.com>; Mon, 19 Apr 2010 11:50:50 -0700 (PDT)
Received: from p3plex1out01.prod.phx3.secureserver.net (p3plex1out01.prod.phx3.secureserver.net [72.167.180.17]) by core3.amsl.com (Postfix) with SMTP id ED6623A6951 for <oauth@ietf.org>; Mon, 19 Apr 2010 11:50:47 -0700 (PDT)
Received: (qmail 25188 invoked from network); 19 Apr 2010 18:50:39 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.20) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 19 Apr 2010 18:50:39 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT002.EX1.SECURESERVER.NET ([72.167.180.20]) with mapi; Mon, 19 Apr 2010 11:50:39 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Marius Scurtescu <mscurtescu@google.com>
Date: Mon, 19 Apr 2010 11:50:34 -0700
Thread-Topic: [OAUTH-WG] Issue: Authorization endpoint parameter extension policy
Thread-Index: Acrf5VVFpsr7NIynS8eLTOE4G68tGQAC8lhw
Message-ID: <90C41DD21FB7C64BB94121FBBC2E723438E5C7F1B7@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <s2m74caaad21004161758scdd1ab27t486ef22b8f12911d@mail.gmail.com> <C7EE5805.3244E%eran@hueniverse.com> <2513A610118CC14C8E622C376C8DEC93D54D66DD94@SC-MBXC1.TheFacebook.com> <o2s74caaad21004181338kbc3e0f29m5c77fb3ddfa55d56@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E723438E30A37A3@P3PW5EX1MB01.EX1.SECURESERVER.NET> <v2p74caaad21004191025t7db11ea7t592a1dca3dcc41af@mail.gmail.com>
In-Reply-To: <v2p74caaad21004191025t7db11ea7t592a1dca3dcc41af@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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Issue: Authorization endpoint parameter extension policy
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:50:51 -0000

> -----Original Message-----
> From: Marius Scurtescu [mailto:mscurtescu@google.com]
> Sent: Monday, April 19, 2010 10:25 AM

> Maybe we should consider passing parameters some other way, and not part
> of query strings. JSON?

Please propose text.

EHL