[OpenID] host-meta and "acct:"

[Eran Hammer-Lahav]

Not really.

DNS URIs are defined to be about the DNS *records* not about what the records point to or mean. It is a pointer into the DNS system. An XRD with a DNS URI subject would express information about that record such as who updated it and when, and potentially some security related properties. I don't really see any value in such an XRD at this point (since DNS is a self containing data source), but that's what such an XRD would mean semantically.

EHL

From: openid-general-bounces at lists.openid.net [mailto:openid-general-bounces at lists.openid.net] On Behalf Of Peter Davis
Sent: Monday, November 09, 2009 5:28 AM
To: John Panzer
Cc: openid-general at lists.openid.net
Subject: Re: [OpenID] host-meta and "acct:"

On Nov 6, 2009, at 12:42 PM, John Panzer wrote:


We have one compelling use case already where the existing <Subject> doesn't work: host-meta is "about" a host, and there is no URI scheme to represent Hosts (see IIW notes at https://docs.google.com/a/johnpanzer.com/Doc?docid=0AZojn6fzr_tFZGRqNjhzcXZfOWY1cXA3emY5&hl=en for alternatives considered). The simplest thing that anyone can come up with for this use case that doesn't run into tripwires or pitfalls is a separate element, <hm:Host>, that contains a hostname.

One possible alternative it to use the dns URI scheme (RFC4501), which, i think, for the purposes need here, would likely take the form:

          dns:www.example.org

you can, of course, use other aspects which might be interesting for use cases with host-meta such as forming dns queries in the URI to a dns authority of a zone returning RR types, but i do not know use cases for that.

=peterd

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20091109/a25bb3b3/attachment.htm>