Re: [OAUTH-WG] Which draft to use as a starting point for 'using a token'?

Eran Hammer-Lahav <eran@hueniverse.com> Tue, 09 February 2010 16:14 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 74C3428C219 for <oauth@core3.amsl.com>; Tue, 9 Feb 2010 08:14:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.434
X-Spam-Level:
X-Spam-Status: No, score=-2.434 tagged_above=-999 required=5 tests=[AWL=0.165, 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 uf99QCZWZ5OH for <oauth@core3.amsl.com>; Tue, 9 Feb 2010 08:14:27 -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 D16F128C214 for <oauth@ietf.org>; Tue, 9 Feb 2010 08:14:27 -0800 (PST)
Received: (qmail 8098 invoked from network); 9 Feb 2010 16:15:34 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.20) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 9 Feb 2010 16:15:34 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT002.EX1.SECURESERVER.NET ([72.167.180.20]) with mapi; Tue, 9 Feb 2010 09:15:19 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Date: Tue, 09 Feb 2010 09:15:40 -0700
Thread-Topic: Which draft to use as a starting point for 'using a token'?
Thread-Index: AcqmNNn9ICKDZvAtSGS8T1z8KSpllwDbj7+Q
Message-ID: <90C41DD21FB7C64BB94121FBBC2E723437DFDDE1DC@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <ADB082E11CEB5D49A3CC03E49DCECE02378CB8868D@P3PW5EX1MB01.EX1.SECURESERVER.NET>
In-Reply-To: <ADB082E11CEB5D49A3CC03E49DCECE02378CB8868D@P3PW5EX1MB01.EX1.SECURESERVER.NET>
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] Which draft to use as a starting point for 'using a token'?
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: Tue, 09 Feb 2010 16:14:29 -0000

No one cares?

EHL

> -----Original Message-----
> From: Eran Hammer-Lahav
> Sent: Thursday, February 04, 2010 11:29 PM
> To: OAuth WG (oauth@ietf.org)
> Subject: Which draft to use as a starting point for 'using a token'?
> 
> On the call today I clarified what is going on with all the different drafts. In
> brief:
> 
> draft-hammer-oauth - documentation of the OAuth 1.0 Rev A (with changes)
> protocol. This is done and should be approved by the IESG shortly for
> publication.
> 
> draft-ietf-oauth-authentication - the part of OAuth 1.0 dealing with 'how to
> use a token after you obtain it'.
> draft-ietf-oauth-web-delegation - the part of OAuth 1.0 rev A dealing with
> 'getting a token'.
> 
> draft-hammer-http-token-auth - an alternative proposal (meant to replace
> draft-ietf-oauth-authentication) which builds on top of OAuth 1.0 but cleans
> up the structure and removes the client credentials when accessing
> protected resources. It also changes how the request is normalized into a
> string before signing.
> 
> We have three options for moving forward with 'how to use a token'. Start
> with:
> 
> 1. draft-ietf-oauth-authentication
> 2. draft-hammer-http-token-auth
> 3. something else*
> 
> * Do not suggest something else unless you are going to submit a proposal. It
> doesn't have to be an I-D, I am happy to do the editorial work but I will need
> a detailed proposal that is enough to turn into a specification.
> 
> Pick.
> 
> EHL