IETF Logo Mail Archive

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

Julian Reschke <julian.reschke@gmx.de> Tue, 17 July 2012 18:10 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 0D19C21F86E1 for <oauth@ietfa.amsl.com>; Tue, 17 Jul 2012 11:10:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.364
X-Spam-Level:
X-Spam-Status: No, score=-104.364 tagged_above=-999 required=5 tests=[AWL=-1.765, 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 My0dvrB98sdq for <oauth@ietfa.amsl.com>; Tue, 17 Jul 2012 11:10:21 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id E807121F86CE for <oauth@ietf.org>; Tue, 17 Jul 2012 11:10:20 -0700 (PDT)
Received: (qmail invoked by alias); 17 Jul 2012 18:07:38 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp002) with SMTP; 17 Jul 2012 20:07:38 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18P56ESUSIPWzerRAZjdaXVEpDmShCti4ZbRnhs6Q iSCAP7uPSzPwKM
Message-ID: <5005A9D4.5010003@gmx.de>
Date: Tue, 17 Jul 2012 20:07:16 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Mike Jones <Michael.Jones@microsoft.com>
References: <4E1F6AAD24975D4BA5B16804296739436673769B@TK5EX14MBXC285.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436673769B@TK5EX14MBXC285.redmond.corp.microsoft.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: "draft-ietf-oauth-v2-bearer.all@tools.ietf.org" <draft-ietf-oauth-v2-bearer.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>, The IESG <iesg@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] [Gen-art] Gen-ART Telechat review of draft-ietf-oauth-v2-bearer-22.txt
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, 17 Jul 2012 18:10:22 -0000

On 2012-07-17 20:01, Mike Jones wrote:
> You should actually probably make that name change request to the HTTPbis working group.  I suspect that if they decide to change the name, that we could direct the RFC editor to make the same name change as HTTPbis does.
> ...

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.

Best regards, Julian

v2.23.0 | Report a Bug | By Email