[OpenID] ENUM, XRI hierarchical names, i-services forwarding

[Peter Williams]

In the world of phones, we have got used to number portability - denied one until only a few years ago. How soon we forget! But, portability tends to be a very national affair - for lots of legacy reasons.

Id there any work going on in openid/XRI land to use XRI's alias-making framework and its hierarchical authoritative naming apapratus sync with the various issues to di with the management of E.164 names, especially when interacting with private or carrier ENUM work? 

For example, rather than have one's phone number merely attached as an attribute to the XRI or stored in an hcard, the XRI embeds the E.164 name of the SIM'ed device, in its OpenID.

I imagaining that the openid would have the form of xri://rapmls.com/@MLS.Corp*ES*ATT*987654321 and may delegate the openid in its DNS-friendly forwarding i-service using an openid of the form http://1.2.3.4.5.6.7.8.9.4.3.e164.arpa/. 

Is anyone working on this kind of device integration, combining openid with ENUM in both the XRI reoslver and the ENUM resolver contexts?  One thing US MLS services providers are thinking of doing is running the SIP2-enabled PBXs for all the local realty associations and smaller brokers, and thus understanding the "phone issues" related to openid are vital to making the right infrastructure choices.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20080404/e0571754/attachment-0002.htm>