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

Alessandro Vesely <vesely@tana.it> Sun, 01 April 2012 10:28 UTC

Return-Path: <vesely@tana.it>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BAB921F8685 for <apps-discuss@ietfa.amsl.com>; Sun, 1 Apr 2012 03:28:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level:
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BEPN28XXSB69 for <apps-discuss@ietfa.amsl.com>; Sun, 1 Apr 2012 03:28:07 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 0F72521F864F for <apps-discuss@ietf.org>; Sun, 1 Apr 2012 03:28:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1333276083; bh=GFd9QWCv/M47uQTn6zfpZdzAy/Tkf6mNOs/xnMbu/DM=; l=1503; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=QKKaVG10PPPMiu9cW9A6ZIP+z/4DkNunbec3WNmEiO5U4Qs3+5YjCZZJrEOAdsfc/ XR5Oj2FtlDgrb9sltHUI69CHZtAS466I8qzeD+Obb90adAofavGFbCcLyy6Ix0SXhc Gwcot0qXTOq/rJiqtbabOrx5s60nT5fbLU48KPoc=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Sun, 01 Apr 2012 12:28:03 +0200 id 00000000005DC039.000000004F782DB3.00007C14
Message-ID: <4F782DB3.7050509@tana.it>
Date: Sun, 01 Apr 2012 12:28:03 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: apps-discuss@ietf.org
References: <053201cd0b5d$c08c80f0$41a582d0$@packetizer.com> <20120326150556.GC3557@mail.yitter.info> <CAA1s49V0M7N1pLua+ORxGWmsrd_yAA_KQ0Piqjg8VuWJ5=G+Lg@mail.gmail.com> <20120327084709.GB11491@mail.yitter.info> <00ac01cd0c34$cfc96f10$6f5c4d30$@packetizer.com> <CABP7RbdtMYtqgV=NepJMNintjF9hb4h6wv2ttc5bDVqE=yAvPA@mail.gmail.com> <00d201cd0c3a$b3672410$1a356c30$@packetizer.com> <CABP7Rbdcb_xTjLv+Y8brzvhuNiae0pOJKm-9qhHrQMg+xUYPVw@mail.gmail.com> <4F72F5C0.70106@tana.it> <024101cd0d30$06d70ac0$14852040$@packetizer.com> <4F744E1D.6080101@tana.it> <041d01cd0e3b$7d9d1bc0$78d75340$@packetizer.com> <4F757D47.8060704@tana.it> <04f101cd0e9f$67616f00$36244d00$@packetizer.com>
In-Reply-To: <04f101cd0e9f$67616f00$36244d00$@packetizer.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: [apps-discuss] What auth server supplies email addresses? Was webfinger discussion
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Apr 2012 10:28:08 -0000

On 30/Mar/12 20:03, Paul E. Jones wrote:
> What you describe sounds a bit like JWT:
> http://openid.net/specs/draft-jones-json-web-token-07.html
> 
> Or, it might be OpenID Connect, which uses JWT.  (What you describe is not
> in OpenID 2.0.)

Aha, thanks.  So JWT is how the claim is (supposed to be) transferred
to the RP, correct?  I'm trying to make sense of a presentation of
anonymous claims that Blaine Cook gave on last Thursday (with the
drive-in-France example).  Is it not specified or implemented, yet?

>> -----Original Message-----
>> From: Alessandro Vesely [mailto:vesely@tana.it]
>> 
>> 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 (opaque@example.com) to a
>> shop, on behalf of a customer who wishes to protect his/her main address.