Re: [Gen-art] [OAUTH-WG] Gen-ART Telechat review of draft-ietf-oauth-v2-bearer-22.txt

"Manger, James H" <James.H.Manger@team.telstra.com> Wed, 18 July 2012 00:27 UTC

Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C238C11E80F6; Tue, 17 Jul 2012 17:27:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.956
X-Spam-Level:
X-Spam-Status: No, score=-0.956 tagged_above=-999 required=5 tests=[AWL=-0.055, 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 treaI7iuDqP1; Tue, 17 Jul 2012 17:27:27 -0700 (PDT)
Received: from ipxano.tcif.telstra.com.au (ipxano.tcif.telstra.com.au [203.35.82.200]) by ietfa.amsl.com (Postfix) with ESMTP id 4909411E80F5; Tue, 17 Jul 2012 17:27:25 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,606,1336312800"; d="scan'208";a="87682939"
Received: from unknown (HELO ipcbni.tcif.telstra.com.au) ([10.97.216.204]) by ipoani.tcif.telstra.com.au with ESMTP; 18 Jul 2012 10:28:14 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,6775"; a="77242677"
Received: from wsmsg3751.srv.dir.telstra.com ([172.49.40.172]) by ipcbni.tcif.telstra.com.au with ESMTP; 18 Jul 2012 10:28:13 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3751.srv.dir.telstra.com ([172.49.40.172]) with mapi; Wed, 18 Jul 2012 10:28:12 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Julian Reschke <julian.reschke@gmx.de>, Alexey Melnikov <alexey.melnikov@isode.com>
Date: Wed, 18 Jul 2012 10:28:10 +1000
Thread-Topic: [OAUTH-WG] [Gen-art] Gen-ART Telechat review of draft-ietf-oauth-v2-bearer-22.txt
Thread-Index: Ac1kR5MkkfAq4EaNRjmv2hIjueeUCAAMpy3g
Message-ID: <255B9BB34FB7D647A506DC292726F6E114F7C98546@WSMSG3153V.srv.dir.telstra.com>
References: <4E1F6AAD24975D4BA5B16804296739436673769B@TK5EX14MBXC285.redmond.corp.microsoft.com> <5005A9D4.5010003@gmx.de>
In-Reply-To: <5005A9D4.5010003@gmx.de>
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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 17 Jul 2012 17:37:36 -0700
Cc: General Area Review Team <gen-art@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-oauth-v2-bearer.all@tools.ietf.org" <draft-ietf-oauth-v2-bearer.all@tools.ietf.org>, "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [Gen-art] [OAUTH-WG] Gen-ART Telechat review of draft-ietf-oauth-v2-bearer-22.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2012 00:27:27 -0000

>> can you please rename the production to something which is clearly not a base64 string.

> HTTPbis describes the production as:
> 
> "The "b64token" syntax allows the 66 unreserved URI characters
> ([RFC3986]), plus a few others, so that it can hold a base64, base64url
> (URL and filename safe alphabet), base32, or base16 (hex) encoding,
> with
> or without padding, but excluding whitespace ([RFC4648])." --
> <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p7-auth-
> 20.html#rfc.section.2.1.p.4>
> 
> I think that's sufficiently clear, and "b64token" is actually a good
> name for that ABNF production.

The *text* is clear, but Alexey isn't the first (or last) person see the label "b64token" and assume it always holds a base64-encoding.
How about renaming the production to "token68", reflecting the fact that it supports an alphabet of 68 characters (plus equal signs at the end)?

--
James Manger