Re: [OAUTH-WG] OAuth discovery draft?

Eran Hammer-Lahav <eran@hueniverse.com> Tue, 22 June 2010 04:50 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 D343B3A6953 for <oauth@core3.amsl.com>; Mon, 21 Jun 2010 21:50:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.867
X-Spam-Level:
X-Spam-Status: No, score=-0.867 tagged_above=-999 required=5 tests=[AWL=-0.868, BAYES_50=0.001]
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 l-Iy6Hba3F01 for <oauth@core3.amsl.com>; Mon, 21 Jun 2010 21:50:16 -0700 (PDT)
Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by core3.amsl.com (Postfix) with SMTP id C25203A6954 for <oauth@ietf.org>; Mon, 21 Jun 2010 21:50:04 -0700 (PDT)
Received: (qmail 22812 invoked from network); 22 Jun 2010 04:50:10 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.19) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 22 Jun 2010 04:50:07 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT001.EX1.SECURESERVER.NET ([72.167.180.19]) with mapi; Mon, 21 Jun 2010 21:50:07 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>, "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Date: Mon, 21 Jun 2010 21:50:00 -0700
Thread-Topic: OAuth discovery draft?
Thread-Index: AcsMLfi0k1bL/UTuTyKlbQqO9cCDCgFh6zFgAAQndLA=
Message-ID: <90C41DD21FB7C64BB94121FBBC2E72343B3EC83F46@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <90C41DD21FB7C64BB94121FBBC2E72343B3EBB68D9@P3PW5EX1MB01.EX1.SECURESERVER.NET> <255B9BB34FB7D647A506DC292726F6E1126427308C@WSMSG3153V.srv.dir.telstra.com>
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1126427308C@WSMSG3153V.srv.dir.telstra.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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] OAuth discovery draft?
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, 22 Jun 2010 04:50:23 -0000

Yes, it's on my desk and not yet ready, but I am working on one. It includes your sites proposal among other things. I am trying to get the core spec stable this week and focus on that next.

EHL

> -----Original Message-----
> From: Manger, James H [mailto:James.H.Manger@team.telstra.com]
> Sent: Monday, June 21, 2010 8:03 PM
> To: Eran Hammer-Lahav; OAuth WG (oauth@ietf.org)
> Subject: OAuth discovery draft?
> 
> Eran,
> 
> There have been a few mentions recently of an OAuth discovery draft. Is
> there any such draft yet, or is this just a part that we know needs to be
> done?
> 
> The email on "OAuth meeting notes on -05 (with updates)" said:
> 
> >> 6.1.1. - describing the WWW-Authenticate response header
> >>
> >> - Discovery needed for various elements
> >
> > Yes. That's for the discovery draft.
> 
> 
> A wiki page on "Future OpenID Technical Requirements"
> <http://wiki.openid.net/Future-OpenID-Technical-Requirements> says:
> 
> > 6) IdP Discovery
> >
> >    * Much of this will be covered by OAuth2 Discovery,
> >      however OIC may need to define OpenID specific features.
> >…
> > 17) Simpler discovery
> >
> >    * See Eran's OAuth Discovery proposal
> 
> 
> There was an OAuth 1.0 Discovery draft over 2 years ago, but that is tagged:
> "expired", "marked as obsolete by its author", "discouraged from
> implementing", "no update is expected", "replaced by the OAuth 2.0 effort".
> 
> I know I should write a discovery draft myself.
> 
> --
> James Manger