IETF Logo Mail Archive

Re: [OAUTH-WG] Issue: prefixing parameters with oauth_

John Kemp <john@jkemp.net> Tue, 20 April 2010 10:38 UTC

Return-Path: <john@jkemp.net>
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 225AD3A67D7 for <oauth@core3.amsl.com>; Tue, 20 Apr 2010 03:38:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.88
X-Spam-Level:
X-Spam-Status: No, score=-0.88 tagged_above=-999 required=5 tests=[AWL=-0.474, BAYES_20=-0.74, IP_NOT_FRIENDLY=0.334]
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 EcckB9Akq9am for <oauth@core3.amsl.com>; Tue, 20 Apr 2010 03:38:19 -0700 (PDT)
Received: from outbound-mail-158.bluehost.com (cpoproxy2-pub.bluehost.com [67.222.39.38]) by core3.amsl.com (Postfix) with SMTP id 2192E3A6801 for <oauth@ietf.org>; Tue, 20 Apr 2010 03:38:10 -0700 (PDT)
Received: (qmail 22677 invoked by uid 0); 20 Apr 2010 10:38:01 -0000
Received: from unknown (HELO box320.bluehost.com) (69.89.31.120) by cpoproxy2.bluehost.com with SMTP; 20 Apr 2010 10:38:01 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=jkemp.net; h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-Identified-User; b=xLd97U797ccWgADHLB+dqPDluypwtOE2FMwho/qvhml5uirVcGcV4s9xmncId42n/0W0Jl5Ler3LnK3GvK4PSO9YXOONbMSQwVlUjWIxbd6RhfBqSU1GTT5dFcszDVKt;
Received: from cpe-69-205-56-47.nycap.res.rr.com ([69.205.56.47] helo=[192.168.1.103]) by box320.bluehost.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <john@jkemp.net>) id 1O4Aq9-00029I-7r; Tue, 20 Apr 2010 04:38:01 -0600
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset="us-ascii"
From: John Kemp <john@jkemp.net>
In-Reply-To: <4BCD31BF.5090701@stpeter.im>
Date: Tue, 20 Apr 2010 06:37:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0420973C-FE87-4969-9986-889173D74342@jkemp.net>
References: <14411661-A227-4DCA-86B3-A9C5FB8055D7@gmail.com> <4BCD31BF.5090701@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1078)
X-Identified-User: {1122:box320.bluehost.com:jkempnet:jkemp.net} {sentby:smtp auth 69.205.56.47 authed with john+jkemp.net}
Cc: Marius Scurtescu <marius.scurtescu@gmail.com>, OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Issue: prefixing parameters with oauth_
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: Tue, 20 Apr 2010 10:38:20 -0000

On Apr 20, 2010, at 12:46 AM, Peter Saint-Andre wrote:

> On 4/18/10 6:46 PM, Dick Hardt wrote:
> 
>> Given the practice that the authorization endpoint and the redirect_uri
>> can contain URI query parameters, then differentiating between
>> application specific query parameters and OAuth protocol parameters by
>> prefixing the OAuth parameters with oauth_ would seem a useful way to
>> minimize conflicts.
> 
> Can't application developers avoid conflicts by giving their parameters
> names other than those already used in OAuth?

Is every application developer (those using an OAuth library, or product) familiar with the names that are used in the OAuth spec?

- johnk

v2.23.0 | Report a Bug | By Email