[OpenID] OpenID for non-HTTP applications?

[Bob Wyman]

My apologies if I've missed the appropriate discussions somewhere... But, I
would appreciate it greatly if someone could comment on the problem of
getting non-HTTP applications to use OpenID. For instance, I'd like to use
OpenID for things like my identifier (JID, username, etc.) in Jabber, POP,
SMTP, FTP, Gopher, etc... But, many of these protocols are well established
and resistant to change. Also, protocols like Jabber/XMPP and SMTP extract
useful routing information from the ids that they currently assign to me. To
these applications, identifiers are not simply opaque strings. (For
instance, in both Jabber and SMTP, my id includes the name of my server.)

My guess is that there is a small set of standard "patterns" that non-HTTP
applications would need to support in order to support OpenID. Have these
been defined or otherwise discussed?

bob wyman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20070117/6bc0094a/attachment-0001.htm>