IETF Logo Mail Archive

Re: [OAUTH-WG] Proposed resolution for issue 26

"Manger, James H" <James.H.Manger@team.telstra.com> Tue, 27 September 2011 00:17 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 31B6811E80AA for <oauth@ietfa.amsl.com>; Mon, 26 Sep 2011 17:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.84
X-Spam-Level:
X-Spam-Status: No, score=-2.84 tagged_above=-999 required=5 tests=[AWL=-1.939, 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 fl+zpTroHVYM for <oauth@ietfa.amsl.com>; Mon, 26 Sep 2011 17:17:53 -0700 (PDT)
Received: from ipxbno.tcif.telstra.com.au (ipxbno.tcif.telstra.com.au [203.35.82.204]) by ietfa.amsl.com (Postfix) with ESMTP id 09D9211E808A for <oauth@ietf.org>; Mon, 26 Sep 2011 17:17:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.68,447,1312120800"; d="scan'208";a="46732315"
Received: from unknown (HELO ipccni.tcif.telstra.com.au) ([10.97.216.208]) by ipobni.tcif.telstra.com.au with ESMTP; 27 Sep 2011 10:20:33 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,6481"; a="38075200"
Received: from wsmsg3707.srv.dir.telstra.com ([172.49.40.81]) by ipccni.tcif.telstra.com.au with ESMTP; 27 Sep 2011 10:20:33 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by wsmsg3707.srv.dir.telstra.com ([172.49.40.81]) with mapi; Tue, 27 Sep 2011 10:20:33 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Mike Jones <Michael.Jones@microsoft.com>, "oauth@ietf.org" <oauth@ietf.org>
Date: Tue, 27 Sep 2011 10:20:31 +1000
Thread-Topic: Proposed resolution for issue 26
Thread-Index: Acx5+RoYuC5sLQs0Spy/pi+T441Q9AAxktNwAG+nNNAACm0CwA==
Message-ID: <255B9BB34FB7D647A506DC292726F6E1128FE19FB2@WSMSG3153V.srv.dir.telstra.com>
References: <4E1F6AAD24975D4BA5B16804296739435C1FC6A1@TK5EX14MBXC285.redmond.corp.microsoft.com> <255B9BB34FB7D647A506DC292726F6E1128E5D883D@WSMSG3153V.srv.dir.telstra.com> <4E1F6AAD24975D4BA5B16804296739435C214906@TK5EX14MBXC285.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739435C214906@TK5EX14MBXC285.redmond.corp.microsoft.com>
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] Proposed resolution for issue 26
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: Tue, 27 Sep 2011 00:17:54 -0000

> While you take the viewpoint that the bearer spec is restricting scope values, in fact,
> the spec intentionally allows all characters that can be safely communicated in an HTTP
> response header parameter to be used.

But "all characters that can be safely communicated in an HTTP response header parameter" is only a subset of the characters that OAuth Core allows in a scope value (any Unicode string excluding space). I don't understand how this isn't the Bearer spec restricting scope values.


P.S. You recognize here that non-ASCII chars cannot be safely communicated in an HTTP response header parameter. This is why Julian was concerned about the spec saying the error_description holds raw UTF-8.
[Actually the ABNF for error_description restricts it to 93 ASCII chars so when the text says it is UTF-8 encoded it is raising the potential problem of arbitrary UTF-8 in HTTP headers unnecessarily.]

--
James Manger

v2.46.0 | Report a Bug | By Email | System Status