IETF Logo Mail Archive

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

Dick Hardt <dick.hardt@gmail.com> Tue, 20 April 2010 04:51 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 3F8043A689D for <oauth@core3.amsl.com>; Mon, 19 Apr 2010 21:51:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.43
X-Spam-Level:
X-Spam-Status: No, score=-2.43 tagged_above=-999 required=5 tests=[AWL=0.169, 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 ULchOoV3kz+Q for <oauth@core3.amsl.com>; Mon, 19 Apr 2010 21:51:04 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id 4C5583A6817 for <oauth@ietf.org>; Mon, 19 Apr 2010 21:51:04 -0700 (PDT)
Received: by gyh4 with SMTP id 4so3057457gyh.31 for <oauth@ietf.org>; Mon, 19 Apr 2010 21:50:53 -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=OaEaAqVs2DU6KhOcICdvsGxeUOFFJDtgYiWUhrtrOug=; b=Rqvf4z4EFp0NQVR5Da/IGXoYQaroTUEbfgz6V7sVF+Nae7v7C9UjAnZhokNS2yaIVg MxhWH+KFWHg7uG2v2wGx21JOrb8nGvwFa3id+RWiOnzRDZ64zOSOAHo12zuypmCPanff Jt1UcJl3dNs2C4Cfd5NwvyuIVStZ9JUoW/MqE=
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=klwEolA6EsWpCFqNmSWVK7dE6dmY8ngoI8Iqv/o+HwhJb2PzxM5mTN3Qo5wC8nnTm4 DztJ899qvCpgagZgtBGgPNrRm7ZX9P59F86MyHWhNWbu108/KisZzld5DYIyd5I9U9ch blkyjXD4U4+Mc4aYon3fNQ39KNYDMpvYi0Ugo=
Received: by 10.101.136.1 with SMTP id o1mr14799525ann.226.1271739048582; Mon, 19 Apr 2010 21:50:48 -0700 (PDT)
Received: from [10.0.1.4] (c-67-180-195-167.hsd1.ca.comcast.net [67.180.195.167]) by mx.google.com with ESMTPS id i8sm53205459ana.9.2010.04.19.21.50.46 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 19 Apr 2010 21:50:47 -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: <4BCD31BF.5090701@stpeter.im>
Date: Mon, 19 Apr 2010 21:50:42 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <CB3B4494-2A0B-4CEC-9BE4-0EF06FA6AB94@gmail.com>
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)
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 04:51:05 -0000

On 2010-04-19, at 9:46 PM, 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?

If changing the parameters is available to them. They may be trying to shimmy OAuth into an existing system. 

I don't know how common the issue is, just pointing out why the prefix was there in the past.

-- Dick

v2.23.0 | Report a Bug | By Email