Re: [apps-discuss] Webfinger

"Paul E. Jones" <paulej@packetizer.com> Mon, 21 November 2011 19:13 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 1F0F221F8B6F for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 11:13:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.518
X-Spam-Level:
X-Spam-Status: No, score=-2.518 tagged_above=-999 required=5 tests=[AWL=0.081, 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 ENZn4zt+rNaH for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 11:13:36 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id EF12221F8B67 for <apps-discuss@ietf.org>; Mon, 21 Nov 2011 11:13:35 -0800 (PST)
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 pALJDSFf031051 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 21 Nov 2011 14:13:29 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1321902809; bh=UJBexzKjroGjaDUmyX5Jeq2Z/NEwnPGLzFXtNgFaxDM=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=QPKjLZLts26nW32NOMlxQ/0vLn9MCmssPVwyXS8kFzsafRyoYDReYKgnRvZVtgnzq DAyjw1Rd3KbWS7g0oojgJ80QOJzO8+dEmsE5Gw+JBwzIXHD9mGUCffX6+euNEZAA3r bb2QPw9YD3GMoPlGOqOAwsmxHjlmQQXAn3elF+Bo=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Simon Perreault'" <simon.perreault@viagenie.ca>
References: <032101cc9288$e3a06910$aae13b30$@packetizer.com> <4ECA97FA.3040309@viagenie.ca>
In-Reply-To: <4ECA97FA.3040309@viagenie.ca>
Date: Mon, 21 Nov 2011 14:13:25 -0500
Message-ID: <076301cca881$a599cf30$f0cd6d90$@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: AQI/v0XgjFwdy9sXrXmTVWBMa/eIuQJR8CDWlL7zQnA=
Content-Language: en-us
Cc: 'Joseph Smarr' <jsmarr@google.com>, apps-discuss@ietf.org
Subject: Re: [apps-discuss] Webfinger
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: Mon, 21 Nov 2011 19:13:41 -0000

Simon,

There is certainly some overlap with the kinds of information Webfinger
provides and vcard provides.  However, Webfinger solves a problem vcard was
not designed to solve: finding the user's information in the first place.
If I already have a vcard in hand, that's great, but I usually do not.

You can imagine a point in the future where one may not even need to have an
address book containing anything more than email (er, "acct" URIs).  The
email client, phone application, web portal, etc. could grab all of the
other information as needed via Webfinger.  I would hope vcard would be a
part of that.

As Blane mentioned separately, some data that might be provided via
Webfinger (i.e., some link relations) may not be appropriate for a vcard.
For example, my list of identity providers may not be secret, but probably
not what I'd want to publish via a vcard.

We've had some discussion on whether link relations should be defined as a
part of the Webfinger spec or separately.  It seems most people are of the
opinion that they should be defined in a separate document.  Thus, I'd
invite you to work on the vcard link relation spec. This would be added to
the registry established by RFC 5988, I believe.

Paul

> -----Original Message-----
> From: Simon Perreault [mailto:simon.perreault@viagenie.ca]
> Sent: Monday, November 21, 2011 1:27 PM
> To: Paul E. Jones
> Cc: apps-discuss@ietf.org; Joseph Smarr; Gonzalo Salgueiro
> Subject: Re: [apps-discuss] Webfinger
> 
> Paul E. Jones wrote, on 10/24/2011 04:09 PM:
> > We just submitted this:
> >
> > http://www.ietf.org/internet-drafts/draft-jones-appsawg-webfinger-00.t
> > xt
> 
> One general comment I have is that there seems to be a lot of overlap
> with features already in vCard or that could be defined as extensions to
> vCard. Let's take for example one example from the draft:
> 
>      <?xml version="1.0" encoding="UTF-8"?>
>      <XRD xmlns="http://docs.oasis-open.org/ns/xri/xrd-1.0">
>        <Subject>acct:bob@example.com</Subject>
>        <Link rel="http://webfinger.net/rel/avatar"
>              href="http://example.com/bob/images/avatar.jpg"/>
>        <Link rel="blog"
>              href="http://example.net/bob/blog/"/>
>        <Link rel="vcard"
>              href="http://example.com/bob/vcard.vcf"/>
>        <Link rel="http://specs.openid.net/auth/2.0/provider"
>              href="https://openid.example.com/bob"/>
>        <Link rel="share" href="http://example.com/bob/public/"/>
>        <Link rel="http://webfinger.net/rel/profile-page"
>              href="http://example.com/bob/profile/"/>
>      </XRD>
> 
> All of the <Link> elements, except the one pointing to the vCard itself,
> could be contained inside the vCard.
> 
> Did you look at vCard and find it inappropriate for your needs?
> 
> Simon
> --
> DTN made easy, lean, and smart --> http://postellation.viagenie.ca
> NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
> STUN/TURN server               --> http://numb.viagenie.ca