Re: [OAUTH-WG] auth-param syntax, was: OK to post OAuth Bearer draft 15?

Julian Reschke <julian.reschke@gmx.de> Wed, 04 January 2012 22:22 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D904B21F860F for <oauth@ietfa.amsl.com>; Wed, 4 Jan 2012 14:22:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.824
X-Spam-Level:
X-Spam-Status: No, score=-103.824 tagged_above=-999 required=5 tests=[AWL=-1.225, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RIIgKXY50Fz8 for <oauth@ietfa.amsl.com>; Wed, 4 Jan 2012 14:22:13 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id B5A3721F860E for <oauth@ietf.org>; Wed, 4 Jan 2012 14:22:12 -0800 (PST)
Received: (qmail invoked by alias); 04 Jan 2012 22:22:11 -0000
Received: from p5DCC2522.dip.t-dialin.net (EHLO [192.168.178.36]) [93.204.37.34] by mail.gmx.net (mp025) with SMTP; 04 Jan 2012 23:22:11 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX188hSpHTu48pbSk2G1IsW89G1i+1LpxPXdY3KtVqI h9iIkIvMuiHjfC
Message-ID: <4F04D111.9060702@gmx.de>
Date: Wed, 04 Jan 2012 23:22:09 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Mike Jones <Michael.Jones@microsoft.com>
References: <4E1F6AAD24975D4BA5B16804296739435F763122@TK5EX14MBXC283.redmond.corp.microsoft.com> <4EEF13F1.7030409@gmx.de> <4E1F6AAD24975D4BA5B16804296739435F78F5BB@TK5EX14MBXC283.redmond.corp.microsoft.com> <4EFD91B4.5050904@gmx.de> <4E1F6AAD24975D4BA5B16804296739435F790386@TK5EX14MBXC283.redmond.corp.microsoft.com> <1325619340.463.YahooMailNeo@web31808.mail.mud.yahoo.com> <4E1F6AAD24975D4BA5B16804296739435F7936E7@TK5EX14MBXC283.redmond.corp.microsoft.com> <1325620772.48511.YahooMailNeo@web31802.mail.mud.yahoo.com> <4E1F6AAD24975D4BA5B16804296739435F79376F@TK5EX14MBXC283.redmond.corp.microsoft.com> <1325621624.9908.YahooMailNeo@web31808.mail.mud.yahoo.com> <4E1F6AAD24975D4BA5B16804296739435F793829@TK5EX14MBXC283.redmond.corp.microsoft.com> <1325623068.88228.YahooMailNeo@web31816.mail.mud.yahoo.com> <5E5EA7F9-B4A0-4DCB-801C-3C0F4EC36A1E@ve7jtb.com> <4E1F6AAD24975D4BA5B16804296739435F7A9464@TK5EX14MBXC284.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739435F7A9464@TK5EX14MBXC284.redmond.corp.microsoft.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: Barry Leiba <barryleiba@computer.org>, Mark Nottingham <mnot@mnot.net>, OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] auth-param syntax, was: OK to post OAuth Bearer draft 15?
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 04 Jan 2012 22:22:17 -0000

On 2012-01-04 23:17, Mike Jones wrote:
> There are actually two parts to “this” as I see it:
>
> 1. Defining the syntax for the acceptable contents of the scope, error,
> error_description, and error_uri parameters.
>
> 2. Defining the means by which these values are transmitted in
> WWW-Authenticate response header fields for Bearer tokens.
>
> I would be fine seeing part 1 added to the core spec. (In fact, there is
> a tracked issue OAuth ticket 27
> <http://trac.tools.ietf.org/wg/oauth/trac/ticket/27> requiring that this
> occur for the scope parameter.) Given that the core spec is, by design,
> agnostic of the method used to access protected resource (including
> being agnostic of the use of the WWW-Authenticate field by the Bearer
> spec), I believe that it would be inappropriate to add part 2 to the
> core spec.
> ...

+1