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

John Bradley <ve7jtb@ve7jtb.com> Wed, 04 January 2012 22:11 UTC

Return-Path: <ve7jtb@ve7jtb.com>
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 4DE9521F85B3 for <oauth@ietfa.amsl.com>; Wed, 4 Jan 2012 14:11:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 nnfSQ6QMBE3k for <oauth@ietfa.amsl.com>; Wed, 4 Jan 2012 14:11:10 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2954B21F85AF for <oauth@ietf.org>; Wed, 4 Jan 2012 14:10:47 -0800 (PST)
Received: by ggnk5 with SMTP id k5so11913423ggn.31 for <oauth@ietf.org>; Wed, 04 Jan 2012 14:10:47 -0800 (PST)
Received: by 10.101.174.1 with SMTP id b1mr23181379anp.1.1325715047355; Wed, 04 Jan 2012 14:10:47 -0800 (PST)
Received: from [192.168.1.213] ([190.22.74.206]) by mx.google.com with ESMTPS id s12sm140055004and.15.2012.01.04.14.10.42 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 04 Jan 2012 14:10:46 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/signed; boundary="Apple-Mail=_F644511A-14A4-4C49-9753-B4D687C19782"; protocol="application/pkcs7-signature"; micalg="sha1"
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <4F04CC2D.1080805@gmx.de>
Date: Wed, 04 Jan 2012 19:10:38 -0300
Message-Id: <7570AAA5-3C7B-409B-99AE-BC9C91F729FB@ve7jtb.com>
References: <4E1F6AAD24975D4BA5B16804296739435F763122@TK5EX14MBXC283.redmond.corp.microsoft.com> <F6FCE30E-20FE-4FCD-AC31-AB227A42F2D2@mnot.net> <4E1F6AAD24975D4BA5B16804296739435F772D1D@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.c om> <4F04CC2D.1080805@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.1251.1)
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:11:11 -0000

Don't get me wrong, I agree that it should be in core.

I just don't want to hold up core for something that only bearer seems to care about.

If there is consensus that it should be fixed in core then lets do that rather than leaving it up to bearer,  MAC and token types not yet imagined to do it independently.

John B.
On 2012-01-04, at 7:01 PM, Julian Reschke wrote:

> On 2012-01-04 22:40, John Bradley wrote:
>> You are correct. the Core spec should include this. However for one
>> reason or another it is not in the core spec and probably will not be,
>> given that it is in last call.
>> ...
> 
> The datatracker says:
> 
> "AD Evaluation::Revised ID Needed" (<https://datatracker.ietf.org/doc/draft-ietf-oauth-v2/>)
> 
> As far as I recall, this includes other changes needed by the bearer spec.
> 
> Best regards, Julian