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

Julian Reschke <julian.reschke@gmx.de> Thu, 12 April 2012 08:54 UTC

Return-Path: <julian.reschke@gmx.de>
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 4492C21F8664 for <gen-art@ietfa.amsl.com>; Thu, 12 Apr 2012 01:54:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.897
X-Spam-Level:
X-Spam-Status: No, score=-103.897 tagged_above=-999 required=5 tests=[AWL=-1.297, 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 vFR9XZw14cm1 for <gen-art@ietfa.amsl.com>; Thu, 12 Apr 2012 01:54:36 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 4556621F865D for <gen-art@ietf.org>; Thu, 12 Apr 2012 01:54:36 -0700 (PDT)
Received: (qmail invoked by alias); 12 Apr 2012 08:54:35 -0000
Received: from p57A6EA96.dip.t-dialin.net (EHLO [192.168.178.36]) [87.166.234.150] by mail.gmx.net (mp036) with SMTP; 12 Apr 2012 10:54:35 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+jjXw75uijlbuoBXu+sASyCksWPaiMYWSlxOSlFH dW3jrdQkFsDo3a
Message-ID: <4F869849.1060508@gmx.de>
Date: Thu, 12 Apr 2012 10:54:33 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Eran Hammer <eran@hueniverse.com>
References: <4E1F6AAD24975D4BA5B16804296739436646237B@TK5EX14MBXC283.redmond.corp.microsoft.com> <4F8616D1.2080003@ieca.com> <D5321BE6-806D-4EF1-A2DF-EA4284B29B95@hueniverse.com>
In-Reply-To: <D5321BE6-806D-4EF1-A2DF-EA4284B29B95@hueniverse.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
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-18.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: Thu, 12 Apr 2012 08:54:37 -0000

Citing from Sean's dicuss 
(<https://datatracker.ietf.org/doc/draft-ietf-oauth-v2-bearer/ballot/#sean-turner>):

> 1) I'm hoping the answer to this one is "there's no problem" but I gotta ask and
> maybe the APPs ADs can confirm:  Is there any issue with this specification
> using ABNF from [I-D.ietf-httpbis-p1-messaging] while OAUTH 2.0 uses [RFC5234]?

The ABNF from HTTPbis is a superset of RFC 5234 in that it defines a 
list rule for readability. I don't think that this rule is used anymore 
in the bearer spec, so it can just say it's using RFC 5234.

Best regards, Julian