IETF Logo Mail Archive

Re: [OAUTH-WG] AD review of draft-ietf-oauth-bearer-13

"Manger, James H" <James.H.Manger@team.telstra.com> Wed, 02 November 2011 23:21 UTC

Return-Path: <James.H.Manger@team.telstra.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 C59F211E80E1 for <oauth@ietfa.amsl.com>; Wed, 2 Nov 2011 16:21:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.623
X-Spam-Level:
X-Spam-Status: No, score=-3.623 tagged_above=-999 required=5 tests=[AWL=-2.722, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
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 EBHZOmTUeEcv for <oauth@ietfa.amsl.com>; Wed, 2 Nov 2011 16:21:57 -0700 (PDT)
Received: from ipxcvo.tcif.telstra.com.au (ipxcvo.tcif.telstra.com.au [203.35.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id 7090511E80AD for <oauth@ietf.org>; Wed, 2 Nov 2011 16:21:56 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.69,446,1315144800"; d="scan'208";a="52839757"
Received: from unknown (HELO ipccvi.tcif.telstra.com.au) ([10.97.217.208]) by ipocvi.tcif.telstra.com.au with ESMTP; 03 Nov 2011 10:21:54 +1100
X-IronPort-AV: E=McAfee;i="5400,1158,6518"; a="40975875"
Received: from wsmsg3755.srv.dir.telstra.com ([172.49.40.196]) by ipccvi.tcif.telstra.com.au with ESMTP; 03 Nov 2011 10:21:53 +1100
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3755.srv.dir.telstra.com ([172.49.40.196]) with mapi; Thu, 3 Nov 2011 10:21:53 +1100
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, "oauth@ietf.org" <oauth@ietf.org>
Date: Thu, 03 Nov 2011 10:21:52 +1100
Thread-Topic: [OAUTH-WG] AD review of draft-ietf-oauth-bearer-13
Thread-Index: AcyZfuJ0qW0WG7WhQre+j+LY1N0ITAANJSpg
Message-ID: <255B9BB34FB7D647A506DC292726F6E112925965A8@WSMSG3153V.srv.dir.telstra.com>
References: <4EB173A1.6040209@cs.tcd.ie>
In-Reply-To: <4EB173A1.6040209@cs.tcd.ie>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] AD review of draft-ietf-oauth-bearer-13
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, 02 Nov 2011 23:21:58 -0000

> 5) Section 3 ABNF allows "realm=foo;realm=bar;scope=baz;error=123"
> is that ok? Is processing clear for all cases? I don't think it
> is.


The ABNF does not allow that.
It requires commas as separators, not semi-colons.
It requires double quotes around values.
The only possible ambiguity in this example is the duplicate realms, but that parameter isn't even defined in this spec (it is defined in draft-ietf-httpbis-p7-auth)! I guess that spec could try to explicitly define behaviour in the case of this particular error, but it may have to explicitly describe a lot of other error cases as well.

--
James Manger

v2.23.0 | Report a Bug | By Email