IETF Logo Mail Archive

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

"Paul E. Jones" <paulej@packetizer.com> Sun, 01 April 2012 17:40 UTC

Return-Path: <paulej@packetizer.com>
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 9586421F884B for <apps-discuss@ietfa.amsl.com>; Sun, 1 Apr 2012 10:40:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 HQkYc9jUyTfw for <apps-discuss@ietfa.amsl.com>; Sun, 1 Apr 2012 10:40:51 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id C71DC21F8848 for <apps-discuss@ietf.org>; Sun, 1 Apr 2012 10:40:51 -0700 (PDT)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id q31HenB0004840 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 1 Apr 2012 13:40:49 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1333302050; bh=dhNnLVE0OpCi0LZYHfN6hdCCQUa4TdxJbiTOSMQVPfA=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=cpBm6kuXiY7dcZrhaHQ72ArMXCGCS2h+o8LZq5QDEmCcfjQsksZnCC3aJ3jh/H4uE TMueMB85EdfIhvJCcP2HvMZi68DB1mI91Kd/eBu9Ceg159WO6aUeaeDZVjyJXY5n8a yWLT1YlZ/u5PRkZjzsGlwYhs79Xs9+BOeGjmJcTU=
From: "Paul E. Jones" <paulej@packetizer.com>
To: 'Alessandro Vesely' <vesely@tana.it>, 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> <4F782DB3.7050509@tana.it>
In-Reply-To: <4F782DB3.7050509@tana.it>
Date: Sun, 01 Apr 2012 13:40:50 -0400
Message-ID: <00a301cd102e$94d61310$be823930$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQEg174HJISLlkWDD0VVkXSpmVuZQwKMareXAWwgTx8BwaaRJQGG5wouAU3B5AYBuFTkWgIDrH2CAm7QUeQCPbK1PwHttm20Akw553QBo30rsQFSEdX1ANEHVMWXFu5pEA==
Content-Language: en-us
Cc: 'Blaine Cook' <romeda@gmail.com>
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 17:40:52 -0000

I don't know.. I wasn't there.

Blaine?

Paul

> -----Original Message-----
> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-bounces@ietf.org]
> On Behalf Of Alessandro Vesely
> Sent: Sunday, April 01, 2012 6:28 AM
> To: apps-discuss@ietf.org
> Subject: Re: [apps-discuss] What auth server supplies email addresses? Was
> webfinger discussion
> 
> 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.
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss

v2.23.0 | Report a Bug | By Email