[Openid-specs-ab] Simple Web Discovery
Michael.Jones at microsoft.com
Wed Oct 27 17:58:37 UTC 2010
These posts of Yaron's outline the basic vision and flows:
We hope to also come out with a description in Internet-draft style soon to provide concrete details about possible implementation choices for this kind of end-to-end scenario. But if you dig into these posts, I believe you'll find there's a lot there already at the conceptual level.
From: Dick Hardt [mailto:dick.hardt at gmail.com]
Sent: Tuesday, October 26, 2010 9:38 PM
To: Mike Jones
Cc: oauth at ietf.org; openid-specs-ab at lists.openid.net
Subject: Re: Simple Web Discovery
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 at example.com<mailto:joe at 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<http://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?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openid-specs-ab