[apps-discuss] R: WebFinger Draft Updated - draft-ietf-appsawg-webfinger-01

Goix Laurent Walter <laurentwalter.goix@telecomitalia.it> Mon, 29 October 2012 15:04 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 DE41821F8705 for <apps-discuss@ietfa.amsl.com>; Mon, 29 Oct 2012 08:04:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.718
X-Spam-Level:
X-Spam-Status: No, score=-1.718 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XXVOoe5ICypn for <apps-discuss@ietfa.amsl.com>; Mon, 29 Oct 2012 08:04:25 -0700 (PDT)
Received: from GRFEDG701BA020.telecomitalia.it (grfedg701ba020.telecomitalia.it [156.54.233.200]) by ietfa.amsl.com (Postfix) with ESMTP id 7236B21F85D4 for <apps-discuss@ietf.org>; Mon, 29 Oct 2012 08:04:23 -0700 (PDT)
Content-Type: multipart/mixed; boundary="_54391536-a095-4cf2-b23b-7ecb0f74e58a_"
Received: from grfhub704ba020.griffon.local (10.188.101.117) by GRFEDG701BA020.telecomitalia.it (10.188.45.100) with Microsoft SMTP Server (TLS) id 8.3.279.5; Mon, 29 Oct 2012 16:04:14 +0100
Received: from GRFMBX704BA020.griffon.local ([10.188.101.15]) by grfhub704ba020.griffon.local ([10.188.101.117]) with mapi; Mon, 29 Oct 2012 16:04:02 +0100
From: Goix Laurent Walter <laurentwalter.goix@telecomitalia.it>
To: Melvin Carvalho <melvincarvalho@gmail.com>, "Paul E. Jones" <paulej@packetizer.com>
Date: Mon, 29 Oct 2012 16:04:00 +0100
Thread-Topic: [apps-discuss] WebFinger Draft Updated - draft-ietf-appsawg-webfinger-01
Thread-Index: Ac21RWrvlsEjkAqcSCOEJDmYfRakbgAn0csw
Message-ID: <A09A9E0A4B9C654E8672D1DC003633AE53A4EE495A@GRFMBX704BA020.griffon.local>
References: <025b01cdae61$591e9690$0b5bc3b0$@packetizer.com> <5082C526.3050100@status.net> <00c501cdaf13$13ef6d30$3bce4790$@packetizer.com> <20121021093728.590d2898@bogo> <CAKaEYhLvKhn6HH936OF-wgVCtKFQg0Ak136qhk4vJ5NKB5XGgQ@mail.gmail.com> <CAAz=scky8Fd+=O=2pyBHE-=QffQZ80Nu9-xXrV9PYg1L9bU1mg@mail.gmail.com> <CAKaEYhKystbkU4fTshtWM7+tJXHQKC6079os-8PqCY55z44BvA@mail.gmail.com> <094c01cdb4b3$6f78b620$4e6a2260$@packetizer.com> <CAKaEYhKe=o73NX4oabg8zF8cu+k0=ZmDjeujzoJ3QcsseMspMA@mail.gmail.com> <616511fcbbf92d7b8c63aaadf7dc7b86@packetizer.com> <CAKaEYhLG8i9oBjcUJ8jZwHCQh_VY2uyKRVwKtz2Fh8Sf1+mxyg@mail.gmail.com>
In-Reply-To: <CAKaEYhLG8i9oBjcUJ8jZwHCQh_VY2uyKRVwKtz2Fh8Sf1+mxyg@mail.gmail.com>
Accept-Language: en-US
Content-Language: it-IT
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
x-ti-disclaimer: Disclaimer1
MIME-Version: 1.0
Cc: "webfinger@googlegroups.com" <webfinger@googlegroups.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: [apps-discuss] R: WebFinger Draft Updated - draft-ietf-appsawg-webfinger-01
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, 29 Oct 2012 15:04:28 -0000

[snip]



Tel URIs are not useful for WebFinger since, as you note, there is
no associated host information.  However, we should allow any URI
that does have a domain part.  After all, the purpose is to go to
the server and say "tell me about this URI".  If the server knows,
it will provide an answer.  If the server has no information on the
URI, it will return a 404.
Sure, tho im not sure the language in the spec, but I guess it
should point out the WF is only oriented at those that have a domain
part, or list the ones that are valid?

I think this is pretty clear in the spec already, if not obvious on the face of it.  For example, bullet point 3 in Section 3 speaks of "URI at the host" and gives examples.  However, if we add text, I think the right place would be Section 5.4 where we talk about WebFinger and URIs. Perhaps we could add a sentence to the end of the first paragraph where we talk about WebFinger being URI scheme agnostic?  I'm not sure what to add, though.  Suggestions?

Unsure on this one.  I guess if the reviewers at the IETF think it's self evident, that should be fine.  There's so many URI schemes today that it's hard to even know if there are grey areas on this one.

[walter] I guess the current "uri scheme-agnostic" text in 5.4 is fine. in general i would avoid formally restricting URI types through white- or blacklisting. This would allow a richer usage of this spec imo although it may not always be "meaningful". Specifically on tel URIs I'd like to recall the enum draft [1] that aims at converting phone numbers into accounts to further perform webfinger requests. Yet in an alternative approach a "default" server (eg whose name is built based on mobile network information) could probably handle wf requests to tel: URIs, whatever process rules are applied at the server to answer or not that query and how (eg to "proxy" the request to the authoritative server/operator for that number)

[1] http://tools.ietf.org/html/draft-goix-appsawg-enum-acct-uri-00
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:00000000000000000000000000000003@TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario.