Re: [apps-discuss] What auth server supplies email addresses? Was webfinger discussion

[Alessandro Vesely <[e-mail]>]

On Fri 30/Mar/2012 08:51:12 +0200 Paul E. Jones wrote:

> I still do not understand :-(
> 
> Can you elaborate for me a bit more?

I may be conflating webfinger, openid, browserid, webid, and some other
protocols of that sort.  At any rate, it was said that a functionality
relevant to some of those is to certify a generic claim, for example whether
someone is legally allowed to drive a lorry in France.  The user would
indicate the kind-of-claim (driving license) and a trusted certifier (the
French motoring authority) without revealing his/her identity.  The relaying
party would then let the user login at the certifier's site in order to
eventually obtain the certificate.

By the same logic, given that example.com should be universally trusted for
email addresses that end with "@example.com", its server would be able to
provide a certified, anonymous email address ([e-mail]) to a shop,
on behalf of a customer who wishes to protect his/her main address.

>> -----Original Message-----
>> From: [e-mail] [mailto:[e-mail]]
>> On Behalf Of Alessandro Vesely
>> Sent: Thursday, March 29, 2012 7:57 AM
>> To: [e-mail]
>> Subject: Re: [apps-discuss] What auth server supplies email addresses? Was
>> webfinger discussion
>>
>> On Thu 29/Mar/2012 13:55:12 +0200 Paul E. Jones wrote:
>>>
>>> Get an email address from what ID?  A Webfinger "acct" URI?
>>
>> In general, the opaque token would be kind-of-claim @ claim-provider
>>
>>>>
>>>> That implies the address is known.  Couldn't one use just
>>>>
>>>>    http://example.org/.well-known/finger/{opaque-token}
>>>>
>>>> and, possibly,
>>>>
>>>>    http://example.org/.well-known/finger/{opaque-token}/email-addr?