[OpenID] A Case for OpenEmailID

[Greg Rolan]

 >So, to use HTML discovery terms, you'd point openid2.provider but not 
openid2.local_id, and that provider would need to be pre-configured to 
understand
 > identifiers in your domain.

And that's pretty much how the Glynx implementation works.  We can 
verify a number of different sorts of IDs  - including email addresses - 
any of which can be used as part of a (contrived & encoded) OpenID URI.  
Oncethe URI request hits the Glynx gateway we do our private, encrypted, 
no password, peer-to-peer authentication thing and translate the result 
back into the OpenID response.  Therefore a Glynx subscriber can choose 
from a number of different identifiers to be their primary OpenID.

Of course we're closed source at the moment, though we hope to open up 
the gateway in time - so that anyone can run one :-)

regards,

Greg.