Paul E. Jones wrote:
Perhaps it is important to say, though, that I do not think it requires
the e-mail providers to get on board with this (in my view) simpler
notation. I could use an ID like [EMAIL PROTECTED] and that should
work, if myopenid.com would publish the appropriate NAPTR
Paul E. Jones wrote:
I’ll give you that one: that’s certainly easier. But, does not cause
some confusion? After all, one’s identity is not yahoo.com, but that is
the identity provider. Perhaps the prompts around the Internet ought to
Say “OpenID Provider:” instead? :-)
I propose
This would require defining an OpenID SRV record in DNS. Would make
sense for someone to get this formally defined as part of IETF. Could
kinda be done in the same way that Boeing is moving forward definition
of XRI in LDAP..
-Original Message-
Message: 1
Date: Mon, 07 Apr 2008 18:56:57
What about having an ENUM e164.org record holding not only the IP of
an SIP-Broker, but the OpenID ID. Whatever format and syntax it might
have.
The appropriate IETF RFC 2916 E.164 number and DNS could provide
not only mangling with eMail addresses but also with telephone
numbers: this
