Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-26.txt

Eran Hammer <eran@hueniverse.com> Wed, 02 May 2012 17:19 UTC

Return-Path: <eran@hueniverse.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 07D1711E809A for <oauth@ietfa.amsl.com>; Wed, 2 May 2012 10:19:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.528
X-Spam-Level:
X-Spam-Status: No, score=-2.528 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599]
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 dhioVmposOZ7 for <oauth@ietfa.amsl.com>; Wed, 2 May 2012 10:19:09 -0700 (PDT)
Received: from p3plex2out01.prod.phx3.secureserver.net (p3plex2out01.prod.phx3.secureserver.net [184.168.131.12]) by ietfa.amsl.com (Postfix) with ESMTP id 975AB11E8086 for <oauth@ietf.org>; Wed, 2 May 2012 10:19:09 -0700 (PDT)
Received: from P3PWEX2HT001.ex2.secureserver.net ([184.168.131.9]) by p3plex2out01.prod.phx3.secureserver.net with bizsmtp id 55K91j0020CJzpC015K9i9; Wed, 02 May 2012 10:19:09 -0700
Received: from P3PWEX2MB008.ex2.secureserver.net ([169.254.8.88]) by P3PWEX2HT001.ex2.secureserver.net ([184.168.131.9]) with mapi id 14.02.0247.003; Wed, 2 May 2012 10:19:08 -0700
From: Eran Hammer <eran@hueniverse.com>
To: Phil Harvey <Phil.Harvey@daveramsey.com>, "oauth@ietf.org" <oauth@ietf.org>
Thread-Topic: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-26.txt
Thread-Index: Ac0od4GhlNHZtS1ZRomSD1074YbVfQAEBX9Q
Date: Wed, 2 May 2012 17:19:08 +0000
Message-ID: <0CBAEB56DDB3A140BA8E8C124C04ECA20101848F@P3PWEX2MB008.ex2.secureserver.net>
References: <8DAB9C3BD441244FBC2FE5D294624535656CE9D3@FPP1W2K8-EXNG1.peace.daveramsey.com>
In-Reply-To: <8DAB9C3BD441244FBC2FE5D294624535656CE9D3@FPP1W2K8-EXNG1.peace.daveramsey.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [64.74.213.174]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-26.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: Wed, 02 May 2012 17:19:11 -0000

Thanks Phil.

These will be corrected in -27 (if we publish one to close IESG issues) or during AUTH48.

EH

> -----Original Message-----
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf
> Of Phil Harvey
> Sent: Wednesday, May 02, 2012 8:24 AM
> To: oauth@ietf.org
> Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-26.txt
> 
> Hello,
> 
> I noticed draft 26 was published and found a few typos while reading the diff
> against draft 25:
> 
> 1) Where the word SHALL was inserted into the paragraph under "2. Client
> Registration", I noticed that the first word of each bullet point in the list that
> follows it needs to be altered to flow properly:
> 
> When registering a client, the client developer SHALL:
> 
>    o  specifies the client type as described in Section 2.1,
>    o  provides its client redirection URIs as described in
>       Section 3.1.2, and
>    o  includes any other information required by the authorization
>       server (e.g. application name, website, description, logo image,
>       the acceptance of legal terms).
> 
> To read like this:
> 
> When registering a client, the client developer SHALL:
> 
>    o  specify the client type as described in Section 2.1,
>    o  provide its client redirection URIs as described in
>       Section 3.1.2, and
>    o  include any other information required by the authorization
>       server (e.g. application name, website, description, logo image,
>       the acceptance of legal terms).
> 
> 2) under "10.3 Access Tokens" (delineated by brackets):
> 
> This specification does not provide any methods for the resource
> server to ensure that an access token presented to it by a given
> client, was issued to [the that] client by the authorization server.
> 
> Which was probably intended to read like this?:
> 
> This specification does not provide any methods for the resource
> server to ensure that an access token presented to it by a given
> client, was issued to that client by the authorization server.
> 
> 3) under both "11.1 The OAuth Access Token Type Registry" and "11.2 The
> OAuth Parameters Registry", there are two instances where it says "two
> weeks" when it should say "two week" in a sentence like this:
> 
> "...after a two weeks review period..."
> 
> Hope that helps,
> 
> Phil Harvey
> eBiz Web Developer
> The Lampo Group, Inc.
> http://www.daveramsey.com
> 
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Tuesday, May 01, 2012 2:13 AM
> To: i-d-announce@ietf.org
> Cc: oauth@ietf.org
> Subject: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-26.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Web Authorization Protocol Working Group of
> the IETF.
> 
> 	Title           : The OAuth 2.0 Authorization Framework
> 	Author(s)       : Eran Hammer
>                           David Recordon
>                           Dick Hardt
> 	Filename        : draft-ietf-oauth-v2-26.txt
> 	Pages           : 66
> 	Date            : 2012-05-01
> 
>    The OAuth 2.0 authorization framework enables a third-party
>    application to obtain limited access to an HTTP service, either on
>    behalf of a resource owner by orchestrating an approval interaction
>    between the resource owner and the HTTP service, or by allowing the
>    third-party application to obtain access on its own behalf.  This
>    specification replaces and obsoletes the OAuth 1.0 protocol described
>    in RFC 5849.
> 
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-oauth-v2-26.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-oauth-v2-26.txt
> 
> The IETF datatracker page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-oauth-v2/
> 
> 
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth