IETF Logo Mail Archive

Re: [OAUTH-WG] I-D Action:draft-ietf-oauth-v2-12.txt

Eran Hammer-Lahav <eran@hueniverse.com> Wed, 26 January 2011 22:27 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 A2A6B3A69ED for <oauth@core3.amsl.com>; Wed, 26 Jan 2011 14:27:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.559
X-Spam-Level:
X-Spam-Status: No, score=-2.559 tagged_above=-999 required=5 tests=[AWL=0.040, 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 2iWsgUrkAIoL for <oauth@core3.amsl.com>; Wed, 26 Jan 2011 14:26:59 -0800 (PST)
Received: from p3plex1out01.prod.phx3.secureserver.net (p3plex1out01.prod.phx3.secureserver.net [72.167.180.17]) by core3.amsl.com (Postfix) with SMTP id BDE8D3A69EE for <oauth@ietf.org>; Wed, 26 Jan 2011 14:26:58 -0800 (PST)
Received: (qmail 11342 invoked from network); 26 Jan 2011 22:30:00 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.21) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 26 Jan 2011 22:30:00 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.19]) by P3PW5EX1HT003.EX1.SECURESERVER.NET ([72.167.180.21]) with mapi; Wed, 26 Jan 2011 15:29:56 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Marius Scurtescu <mscurtescu@google.com>
Date: Wed, 26 Jan 2011 15:29:39 -0700
Thread-Topic: [OAUTH-WG] I-D Action:draft-ietf-oauth-v2-12.txt
Thread-Index: Acu9oIx5P73VJYhFToOghQQlM3/M2AAB9Sjg
Message-ID: <90C41DD21FB7C64BB94121FBBC2E723445A8D62744@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <20110121004501.28103.96097.idtracker@localhost> <90C41DD21FB7C64BB94121FBBC2E723445A8D61C8E@P3PW5EX1MB01.EX1.SECURESERVER.NET> <90C41DD21FB7C64BB94121FBBC2E723445A8D61CBA@P3PW5EX1MB01.EX1.SECURESERVER.NET> <AANLkTimzOErQhT_gjdQrcawVgfsnr_2RVtTOYRoP-fcR@mail.gmail.com> <1296051184.9984.5.camel@pulse> <FFDFD7371D517847AD71FBB08F9A31563848E7CD74@SP2-EX07VS06.ds.corp.yahoo.com> <155BD4E7-F8B3-4B4A-B02D-EAE2048A2F51@kiva.org> <90C41DD21FB7C64BB94121FBBC2E723445A8D6262E@P3PW5EX1MB01.EX1.SECURESERVER.NET> <AANLkTi=gHJ6kvOs8d_p=z60JE+V73=nGvmyci80kTWPU@mail.gmail.com>
In-Reply-To: <AANLkTi=gHJ6kvOs8d_p=z60JE+V73=nGvmyci80kTWPU@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@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] I-D Action:draft-ietf-oauth-v2-12.txt
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: Wed, 26 Jan 2011 22:27:00 -0000

How about turn the MUST to a SHOULD for using the x_ prefix?

EHL

> -----Original Message-----
> From: Marius Scurtescu [mailto:mscurtescu@google.com]
> Sent: Wednesday, January 26, 2011 1:32 PM
> To: Eran Hammer-Lahav
> Cc: oauth@ietf.org
> Subject: Re: [OAUTH-WG] I-D Action:draft-ietf-oauth-v2-12.txt
> 
> On Wed, Jan 26, 2011 at 9:48 AM, Eran Hammer-Lahav
> <eran@hueniverse.com> wrote:
> > This is not aimed at anyone in particular.
> >
> > Replying +1 is not justification for a major breaking change. This was raised
> in the past and consensus was that this is not a major concern. Over the past
> 10 months not a single actual issue was raised about conflicts in legacy
> platforms. If you have an *actual* issue with a platform, please provide the
> full details, including why known mechanisms such as Apache rewrite rules
> can't solve the it.
> 
> I just raised an actual issue.
> 
> Because OAuth 2 parameters are not prefixed, starting with v11 the spec
> requires all other parameters to use the "x_" prefix. Google cannot comply
> with that.
> 
> Dropping the x_ requirement is good enough IMO. If you are worried about
> that, then you are probably afraid of an actual issue as well.
> 
> 
> Marius

v2.23.0 | Report a Bug | By Email