Re: [OAUTH-WG] Simple Web Discovery

Dick Hardt <dick.hardt@gmail.com> Wed, 27 October 2010 04:39 UTC

Return-Path: <dick.hardt@gmail.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 94F433A69A3 for <oauth@core3.amsl.com>; Tue, 26 Oct 2010 21:39:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.515
X-Spam-Level:
X-Spam-Status: No, score=-2.515 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, HTML_MESSAGE=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 Fxk+INFRuFED for <oauth@core3.amsl.com>; Tue, 26 Oct 2010 21:38:43 -0700 (PDT)
Received: from mail-px0-f172.google.com (mail-px0-f172.google.com [209.85.212.172]) by core3.amsl.com (Postfix) with ESMTP id AA8223A68F7 for <oauth@ietf.org>; Tue, 26 Oct 2010 21:38:26 -0700 (PDT)
Received: by pxi13 with SMTP id 13so45292pxi.31 for <oauth@ietf.org>; Tue, 26 Oct 2010 21:38:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:message-id:references:to :x-mailer; bh=42mpLXVMkMl1ecaAdE7icgNUm9FmWKPFZ/cpkmmtRw4=; b=skGUHw7Hyruu59b/MCsGp1q5RgHdxyKaKQzL7ncofwiJ0+Gt2KcazyExqoRHT8HiKB EEmylJdRaJ+my2cFx5jGCYwDvgWs27lIrgUaoLfpIGh3jjjPL1kL/oqap/ZP0pI4yyRA FEUXId3Fcg/KmQx7RndrqVEbAzYcEZL5yqCfc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer; b=x7fydV93w0ME/Xro0l4sTx9+zUNqtHD47yK/ZlYJGVNeMae348Lk+CoCgYVNt3xv9y ueGHRSLSvBQNVYvXLoZKtNM+JmYnCzmJ1nsD8TiC5O3y18odjEgJKcBM2nuXTXBa7/+W ggE2uilVK3ExPxZyTyIG6UlSOxXmweAGYKDnI=
Received: by 10.143.156.4 with SMTP id i4mr7282965wfo.371.1288154309686; Tue, 26 Oct 2010 21:38:29 -0700 (PDT)
Received: from [192.168.1.16] ([24.130.35.170]) by mx.google.com with ESMTPS id v19sm14168565wfh.0.2010.10.26.21.38.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 26 Oct 2010 21:38:28 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: multipart/alternative; boundary=Apple-Mail-25-609460336
From: Dick Hardt <dick.hardt@gmail.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739432459E77D@TK5EX14MBXC207.redmond.corp.microsoft.com>
Date: Tue, 26 Oct 2010 21:38:25 -0700
Message-Id: <44E8DE65-84D7-4FD9-BACF-1E2F58E4FD82@gmail.com>
References: <4E1F6AAD24975D4BA5B16804296739432459E77D@TK5EX14MBXC207.redmond.corp.microsoft.com>
To: Mike Jones <Michael.Jones@microsoft.com>
X-Mailer: Apple Mail (2.1081)
Cc: "openid-specs-ab@lists.openid.net" <openid-specs-ab@lists.openid.net>, "oauth@ietf.org" <oauth@ietf.org>
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: Wed, 27 Oct 2010 04:39:59 -0000
X-List-Received-Date: Wed, 27 Oct 2010 04:39:59 -0000

On 2010-10-26, at 4:33 PM, Mike Jones wrote:

> Having a simple discovery method for services and resources is key to enabling many Internet scenarios that require interactions among parties that do not have pre-established relationships.  For instance, if Joe, with e-mail address joe@example.com, wants to share his calendar with Mary, then Mary’s calendar service, in the general case, will need to discover the location of Joe’s calendar service.  For example, Mary’s calendar service might discover that Joe’s calendar service is located at http://calendars.proseware.com/calendar/joseph by doing discovery for a service named urn:adatum.com:calendar  at example.com for the account joe.

I think it would be really useful to complete the scenario. What happens when Mary's service discovers Joe's calendar service? How does Joe give Mary's calendar service permission to access his calendar? How does Joe identify Mary?

-- Dick