[apps-discuss] R: Webfinger & acct: draft

Goix Laurent Walter <laurentwalter.goix@telecomitalia.it> Mon, 21 November 2011 10:14 UTC

Return-Path: <laurentwalter.goix@telecomitalia.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 57D2F21F8B76 for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 02:14:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.269
X-Spam-Level:
X-Spam-Status: No, score=0.269 tagged_above=-999 required=5 tests=[AWL=0.687, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
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 rpI-mYrMX7bs for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 02:14:26 -0800 (PST)
Received: from GRFEDG701BA020.telecomitalia.it (grfedg701ba020.telecomitalia.it [156.54.233.200]) by ietfa.amsl.com (Postfix) with ESMTP id EA1A921F8B73 for <apps-discuss@ietf.org>; Mon, 21 Nov 2011 02:14:25 -0800 (PST)
Content-Type: multipart/mixed; boundary="_023dfe26-0d0a-4271-9c98-d203f31a29d9_"
Received: from GRFHUB702BA020.griffon.local (10.188.101.112) by GRFEDG701BA020.telecomitalia.it (10.188.45.100) with Microsoft SMTP Server (TLS) id 8.2.254.0; Mon, 21 Nov 2011 11:14:24 +0100
Received: from GRFMBX704BA020.griffon.local ([10.188.101.16]) by GRFHUB702BA020.griffon.local ([10.188.101.112]) with mapi; Mon, 21 Nov 2011 11:14:23 +0100
From: Goix Laurent Walter <laurentwalter.goix@telecomitalia.it>
To: Blaine Cook <romeda@gmail.com>, =?utf-8?B?TXlreXRhIFlldnN0aWZleWV2ICjQnC4g0ITQstGB0YLRltGE0LXRlNCyKQ==?= <evnikita2@gmail.com>
Date: Mon, 21 Nov 2011 11:14:19 +0100
Thread-Topic: [apps-discuss] Webfinger & acct: draft
Thread-Index: AcymtkGkZ8pA6hY0STyw9QQ/TdX8DgBfvA+Q
Message-ID: <A09A9E0A4B9C654E8672D1DC003633AE4057005F1E@GRFMBX704BA020.griffon.local>
References: <A09A9E0A4B9C654E8672D1DC003633AE4056F73E86@GRFMBX704BA020.griffon.local> <047c01cca646$f32f8100$d98e8300$@packetizer.com> <740878FD-AA49-4F62-8612-7AE76CA36710@cisco.com> <CAAz=sc=K1m8dEZQ2BfWG2eVZSiMkMZFa+zPgM-aEOZLg=0OjrQ@mail.gmail.com> <4EC754A8.3090408@gmail.com> <CAAz=sc=X8NTuDi_cgPtgSLt6-+1oaOAVyFk24Q1P+EnLOHJOkg@mail.gmail.com>
In-Reply-To: <CAAz=sc=X8NTuDi_cgPtgSLt6-+1oaOAVyFk24Q1P+EnLOHJOkg@mail.gmail.com>
Accept-Language: en-US, it-IT
Content-Language: it-IT
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, it-IT
MIME-Version: 1.0
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: [apps-discuss] R: Webfinger & acct: draft
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 10:14:27 -0000

Da: apps-discuss-bounces@ietf.org [mailto:apps-discuss-bounces@ietf.org] Per conto di Blaine Cook

2011/11/19 "Mykyta Yevstifeyev (М. Євстіфеєв)" <evnikita2@gmail.com<mailto:evnikita2@gmail.com>>
19.11.2011 8:58, Blaine Cook wrote:
+1; defining the actual link relations should be done outside the webfinger spec, most likely as part of RFC 5988 as Paul mentioned.

The relations are perhaps the trickiest bit of webfinger to standardise, but thankfully 5988 offers guidance; new relations should be defined as specifically as possible, with obvious relation overlap being aggregated into more general identifiers, and eventually being submitted to the registry once sufficient deployment mandates it.

How many of them will we have to define?  Can we at all predict how will Webfinger be used?

We don't know, and no. :-)

We can make educated guesses, but it would be folly to start defining shared, generic terminology before implementation. The XMPP specs are a great example of too much definition stifling actual implementations from growing and evolving.

[walter] from what i’ve seen most webfinger implementations use the “profile-page” and “avatar” link rels to help better identify when subscribing to that user, i.e. after inserting the acct: URI of that user, typically a “confirmation” page is displayed to the user prior to actually subscribe to that user, that shows its avatar and a link to its profile-page. But of course the “describedby” rel may also be used in that context: depending on its type it may suggest whether this is a depiction of that user (more than the “icon” rel) rather than a web page pointing to his profile. Anyway from the webfinger spec perspective it may be good to suggest some specific type of information and update the examples consistently. Then we may discuss further possible values for this, at least their semantics in the webfinger context.

walter

b.
Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

[cid:00000000000000000000000000000001@TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non è necessario.