IETF Logo Mail Archive

Re: [OAUTH-WG] Draft -12 feedback deadline

Eran Hammer-Lahav <eran@hueniverse.com> Wed, 16 February 2011 16:34 UTC

Return-Path: <eran@hueniverse.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 385513A6E80 for <oauth@core3.amsl.com>; Wed, 16 Feb 2011 08:34:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.581
X-Spam-Level:
X-Spam-Status: No, score=-2.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IuAu0W5ZGqFO for <oauth@core3.amsl.com>; Wed, 16 Feb 2011 08:34:26 -0800 (PST)
Received: from p3plex1out01.prod.phx3.secureserver.net (p3plex1out01.prod.phx3.secureserver.net [72.167.180.17]) by core3.amsl.com (Postfix) with SMTP id 5EE0D3A6E7D for <oauth@ietf.org>; Wed, 16 Feb 2011 08:34:26 -0800 (PST)
Received: (qmail 10295 invoked from network); 16 Feb 2011 16:34:54 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.21) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 16 Feb 2011 16:34:54 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.19]) by P3PW5EX1HT003.EX1.SECURESERVER.NET ([72.167.180.21]) with mapi; Wed, 16 Feb 2011 09:34:41 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Marius Scurtescu <mscurtescu@google.com>
Date: Wed, 16 Feb 2011 09:34:34 -0700
Thread-Topic: [OAUTH-WG] Draft -12 feedback deadline
Thread-Index: Acu9lPsVs7t+NAwoS3mCAH3DITsxMQQYQ/+w
Message-ID: <90C41DD21FB7C64BB94121FBBC2E723445A91D3ED3@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <90C41DD21FB7C64BB94121FBBC2E723445A8D6254D@P3PW5EX1MB01.EX1.SECURESERVER.NET> <AANLkTinMjQW26mLkoN7oMdLWLGAHp0_O9LbVi13RpMJB@mail.gmail.com>
In-Reply-To: <AANLkTinMjQW26mLkoN7oMdLWLGAHp0_O9LbVi13RpMJB@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
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Draft -12 feedback deadline
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 16 Feb 2011 16:34:27 -0000

> -----Original Message-----
> From: Marius Scurtescu [mailto:mscurtescu@google.com]
> Sent: Wednesday, January 26, 2011 12:09 PM

> - 4.3. Resource Owner Password Credentials. The 3rd paragraph states that
> the client MUST discard the credentials once it obtains an access token. I
> think it SHOULD discard once it obtains a *refresh* token.

Since this MUST cannot be confirmed, it serves as a community educational tool more than anything else. I rather leave it without conditions.
 
> - 4.5. Extensions. For new grant types, we are not using a registry. Is that OK?

No need. The registry is only to prevent name collisions and since we are using URIs, they already have built-in namespaces.
 
> - 5.2. Error Response. The fist part of the first paragraph talks about 401 and
> client credentials in the Authorization header. Since this was dropped from
> core, this looks strange.

This is specific to client authentication, not grant verification or protected resources. I'll clarify.

EHL

v2.23.0 | Report a Bug | By Email