Re: [OAUTH-WG] Simple Web Discovery

Lukas Rosenstock <lr@lukasrosenstock.net> Fri, 29 October 2010 11:02 UTC

Return-Path: <lr@lukasrosenstock.net>
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 0940D3A6962 for <oauth@core3.amsl.com>; Fri, 29 Oct 2010 04:02:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.618
X-Spam-Level:
X-Spam-Status: No, score=-1.618 tagged_above=-999 required=5 tests=[AWL=0.359, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 EDjLV0fHLayP for <oauth@core3.amsl.com>; Fri, 29 Oct 2010 04:02:47 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id CA95D3A6940 for <oauth@ietf.org>; Fri, 29 Oct 2010 04:02:46 -0700 (PDT)
Received: by qwb7 with SMTP id 7so3116839qwb.31 for <oauth@ietf.org>; Fri, 29 Oct 2010 04:04:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.201.194 with SMTP id fb2mr2001443qab.7.1288350280700; Fri, 29 Oct 2010 04:04:40 -0700 (PDT)
Received: by 10.229.181.213 with HTTP; Fri, 29 Oct 2010 04:04:40 -0700 (PDT)
X-Originating-IP: [134.176.178.24]
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739432459E77D@TK5EX14MBXC207.redmond.corp.microsoft.com>
References: <4E1F6AAD24975D4BA5B16804296739432459E77D@TK5EX14MBXC207.redmond.corp.microsoft.com>
Date: Fri, 29 Oct 2010 13:04:40 +0200
Message-ID: <AANLkTimAdES43rtkEA55x6uSE1N2irUZ=_6WHreLH9n0@mail.gmail.com>
From: Lukas Rosenstock <lr@lukasrosenstock.net>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "openid-specs-ab@lists.openid.net" <openid-specs-ab@lists.openid.net>, "oauth@ietf.org" <oauth@ietf.org>, "openid-specs-connect@lists.openid.net" <openid-specs-connect@lists.openid.net>
Subject: Re: [OAUTH-WG] Simple Web Discovery
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: Fri, 29 Oct 2010 11:02:48 -0000

Hello!
This draft is looking nice, the idea and specification is simple and
straightforward. I would like to draw the connection to other
discovery approaches.

The introductory example in the draft was this one:
GET /.well-known/simple-web-discovery?principal=mailto:joe@example.com&service=urn:adatum.com:calendar
HTTP/1.1

This returns the following response:
{
 "locations":["http://calendars.proseware.com/calendars/joseph"]
}

As per my understanding - please correct me if I'm wrong - this should
be semantically equivalent to the following:
1) Perform host-meta discovery for example.com, which returns an XRD
with the webfinger endpoint.
2) Do webfinger for joe@example.com.
3) The final XRD contains the following:
<XRD>
[...]
<Link rel="urn:adatum.com:calendar"
href="http://calendars.proseware.com/calendars/joseph" />
[...]
</XRD>

Both approaches work, but SWD is a shortcut removes parsing
requirements and fetching roundtrips from the client.

Thoughts, anyone?!

Regards,
 Lukas Rosenstock

2010/10/27 Mike Jones <Michael.Jones@microsoft.com>om>:
> Yaron Goland and I are submitting this Simple Web Discovery (SWD) draft
> (attached and at
> http://self-issued.info/docs/draft-jones-simple-web-discovery-00.html) for
> consideration by the community to address this need.  SWD is simple to
> understand and implement, enables different permissions to be applied to
> discovery of different services, and is JSON-based.  I look forward to
> discussing this with many of you next week at IIW.
>
>
>
>                                                                 -- Mike