IETF Logo Mail Archive

Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-08 HTTP syntax comments

Julian Reschke <julian.reschke@gmx.de> Mon, 26 September 2011 19:24 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 715E91F0C79 for <oauth@ietfa.amsl.com>; Mon, 26 Sep 2011 12:24:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.142
X-Spam-Level:
X-Spam-Status: No, score=-104.142 tagged_above=-999 required=5 tests=[AWL=-1.543, 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 Chr4rSR8S1Jk for <oauth@ietfa.amsl.com>; Mon, 26 Sep 2011 12:24:12 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 6848B1F0C77 for <oauth@ietf.org>; Mon, 26 Sep 2011 12:24:12 -0700 (PDT)
Received: (qmail invoked by alias); 26 Sep 2011 19:26:54 -0000
Received: from p508F9B39.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.155.57] by mail.gmx.net (mp002) with SMTP; 26 Sep 2011 21:26:54 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19VB49UdShVSx3hji6cvk59KwB2tMaVkcjsUyZtAE 4tTWjntAWfBRbA
Message-ID: <4E80D1FD.5020305@gmx.de>
Date: Mon, 26 Sep 2011 21:26:53 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
MIME-Version: 1.0
To: William Mills <wmills@yahoo-inc.com>
References: <4E1F6AAD24975D4BA5B16804296739435C1FD669@TK5EX14MBXC285.redmond.corp.microsoft.com> <4E7DC7DD.5010407@gmx.de> <4E1F6AAD24975D4BA5B16804296739435C2148AE@TK5EX14MBXC285.redmond.corp.microsoft.com> <1317064846.35814.YahooMailNeo@web31805.mail.mud.yahoo.com>
In-Reply-To: <1317064846.35814.YahooMailNeo@web31805.mail.mud.yahoo.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-08 HTTP syntax comments
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: Mon, 26 Sep 2011 19:24:13 -0000

On 2011-09-26 21:20, William Mills wrote:
> I'm gonna top reply...
>
>  >> Is that intended and acceptable?
>>
>>  No, b64token isn’t always there; the syntax specifies that either a
> b64token OR one or more auth-params will be present. Yes, that’s intended.
>
> If the token can be transported in auth-params then I think you must
> define how that will happen. It's too loose otherwise. Go with this
> obvious and say if auth-parames are used then there must be a token=
> parameter that carries the token. That way you are always guaranteed the
> token is present in the protocol.
> ...

+1

In which case the syntax can get rid of the b64token special case 
altogether.

Best regards, Julian

v2.23.0 | Report a Bug | By Email