IETF Logo Mail Archive

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

Julian Reschke <julian.reschke@gmx.de> Tue, 17 July 2012 16:40 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 DB13B21F8505 for <oauth@ietfa.amsl.com>; Tue, 17 Jul 2012 09:40:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.66
X-Spam-Level:
X-Spam-Status: No, score=-104.66 tagged_above=-999 required=5 tests=[AWL=-2.061, 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 DOkqgMafy2bL for <oauth@ietfa.amsl.com>; Tue, 17 Jul 2012 09:40:37 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 6C4B621F8656 for <oauth@ietf.org>; Tue, 17 Jul 2012 09:40:33 -0700 (PDT)
Received: (qmail invoked by alias); 17 Jul 2012 16:41:19 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp019) with SMTP; 17 Jul 2012 18:41:19 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19Wv2MlmoBW60Y7g2nspdbEGvbE5luXNNq20seyZ+ BfwL1On2aeMzxO
Message-ID: <50059598.3030304@gmx.de>
Date: Tue, 17 Jul 2012 18:40:56 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Mike Jones <Michael.Jones@microsoft.com>
References: <4F2575CE.9040001@isode.com> <4E1F6AAD24975D4BA5B16804296739436638B7AD@TK5EX14MBXC284.redmond.corp.microsoft.com> <4F27C37C.1090008@isode.com> <4F843A22.4020908@isode.com> <4F843DA1.8080703@isode.com> <500546C5.6080102@isode.com>, <50054897.3070108@cs.tcd.ie> <4E1F6AAD24975D4BA5B1680429673943667370D7@TK5EX14MBXC285.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943667370D7@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: The IESG <iesg@ietf.org>, General Area Review Team <gen-art@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>, "draft-ietf-oauth-v2-bearer.all@tools.ietf.org" <draft-ietf-oauth-v2-bearer.all@tools.ietf.org>
Subject: Re: [OAUTH-WG] 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 16:40:38 -0000

On 2012-07-17 18:10, Mike Jones wrote:
> FYI, the b64 token definition is identical to the one in
> draft-ietf-httpbis-p7-auth-20.  If it works there, it should work for
> OAuth Bearer.
> ...

+1; not every constraint needs to be expressed in the ABNF. "b64token" 
is here so recipients can parse the header field; it's up to the auth 
scheme to state what the addition constraints are; and that can happen 
in prose.

Best regards, Julian

v2.15.0 | Report a Bug | By Email