Re: [OAUTH-WG] Typos and language in -21
Eran Hammer-Lahav <eran@hueniverse.com> Tue, 20 September 2011 18:46 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 7A5481F0C57 for <oauth@ietfa.amsl.com>; Tue, 20 Sep 2011 11:46:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level:
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.038, 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 BuiBgsUQA3Mb for <oauth@ietfa.amsl.com>; Tue, 20 Sep 2011 11:46:25 -0700 (PDT)
Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by ietfa.amsl.com (Postfix) with SMTP id C66741F0C3E for <oauth@ietf.org>; Tue, 20 Sep 2011 11:46:24 -0700 (PDT)
Received: (qmail 23907 invoked from network); 20 Sep 2011 18:47:20 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.47) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 20 Sep 2011 18:47:19 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.19]) by P3PW5EX1HT005.EX1.SECURESERVER.NET ([72.167.180.134]) with mapi; Tue, 20 Sep 2011 11:47:04 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Niv Steingarten <nivstein@gmail.com>, OAuth WG <oauth@ietf.org>
Date: Tue, 20 Sep 2011 11:46:55 -0700
Thread-Topic: [OAUTH-WG] Typos and language in -21
Thread-Index: Acxxjx5k25dHaeFxQkS0cB5JxH/z2QGNnYlw
Message-ID: <90C41DD21FB7C64BB94121FBBC2E72345213D92CA3@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <CACEVmuohcOT1Y84Z0c0-t03gKK3_n_MwaxVkpF77AAeRoRar3g@mail.gmail.com>
In-Reply-To: <CACEVmuohcOT1Y84Z0c0-t03gKK3_n_MwaxVkpF77AAeRoRar3g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] Typos and language in -21
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, 20 Sep 2011 18:46:25 -0000
Thanks. EHL > -----Original Message----- > From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf > Of Niv Steingarten > Sent: Monday, September 12, 2011 2:01 PM > To: OAuth WG > Subject: [OAUTH-WG] Typos and language in -21 > > In section 10.12 (CSRF): > > 5th paragraph: "A CSRF attack against the against the authorization server's > authorization endpoint" > > One "against the" is redundant. > > 4th paragraph: "The binding value enables the client to validate the validity of > the request by matching the binding value to the user-agent's authenticated > state." > > The phrase "validate the validity of the request" sounds a bit awkward in > my opinion. I'd personally go with either "establish the validity of the > request" or simply "validate the request". > > > -- Niv > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth
- [OAUTH-WG] Typos and language in -21 Niv Steingarten
- Re: [OAUTH-WG] Typos and language in -21 Eran Hammer-Lahav