Re: [webfinger] [appsawg] #12: Semantic gap for the client side

'Stephane Bortzmeyer' <bortzmeyer@nic.fr> Fri, 14 June 2013 14:28 UTC

Return-Path: <bortzmeyer@nic.fr>
X-Original-To: webfinger@ietfa.amsl.com
Delivered-To: webfinger@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 884B921F9CC8 for <webfinger@ietfa.amsl.com>; Fri, 14 Jun 2013 07:28:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level:
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
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 dljnxs2DRJ7C for <webfinger@ietfa.amsl.com>; Fri, 14 Jun 2013 07:28:42 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id A957421F9CC6 for <webfinger@ietf.org>; Fri, 14 Jun 2013 07:28:42 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id D5EAD2803DE; Fri, 14 Jun 2013 16:28:05 +0200 (CEST)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id CF42D28023F; Fri, 14 Jun 2013 16:28:05 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:2219:8::6:113]) by relay1.nic.fr (Postfix) with ESMTP id CC7DB4C0053; Fri, 14 Jun 2013 16:27:35 +0200 (CEST)
Date: Fri, 14 Jun 2013 16:27:35 +0200
From: 'Stephane Bortzmeyer' <bortzmeyer@nic.fr>
To: "Paul E. Jones" <paulej@packetizer.com>
Message-ID: <20130614142735.GA10799@nic.fr>
References: <071.1f5cc037d908127f5ac6f4afd3d8842a@trac.tools.ietf.org> <026701ce5cdb$2e7d2630$8b777290$@packetizer.com> <CAKaEYhLX5o9XM-t0iX5fMAXBrcmv1f2pYbPhP+DVNK=OUjSe=w@mail.gmail.com> <024301ce5d92$f7d06080$e7712180$@packetizer.com> <51B9E0AC.5070508@qti.qualcomm.com> <002a01ce68a3$8501aac0$8f050040$@packetizer.com> <20130614065904.GA30932@nic.fr> <005f01ce68ce$2665a3b0$7330eb10$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <005f01ce68ce$2665a3b0$7330eb10$@packetizer.com>
X-Operating-System: Debian GNU/Linux 7.0
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: 'Pete Resnick' <presnick@qti.qualcomm.com>, 'Stephane Bortzmeyer' <bortzmeyer@nic.fr>, draft-ietf-appsawg-webfinger@tools.ietf.org, 'Melvin Carvalho' <melvincarvalho@gmail.com>, 'salvatore loreto' <salvatore.loreto@ericsson.com>, 'webfinger' <webfinger@ietf.org>
Subject: Re: [webfinger] [appsawg] #12: Semantic gap for the client side
X-BeenThere: webfinger@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the Webfinger protocol proposal in the Applications Area <webfinger.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webfinger>, <mailto:webfinger-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/webfinger>
List-Post: <mailto:webfinger@ietf.org>
List-Help: <mailto:webfinger-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webfinger>, <mailto:webfinger-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jun 2013 14:28:48 -0000

On Fri, Jun 14, 2013 at 03:09:44AM -0400,
 Paul E. Jones <paulej@packetizer.com> wrote 
 a message of 31 lines which said:

> I don't mind adding a statement that makes it explicitly clear that
> the example is not an IETF-approved means of provisioning an email
> client.

Then saying clearly that the example is not an example of present and
actual use: it's brainstorming about what WebFinger could do in the
future.
 
> With the examples in the spec, there have been comments ranging from
> "the example is too abstract" to "the example looks like it could be
> real" (the case with this email provisioning example).  We could
> remove all examples,

Indeed, some of the examples are wrong. In -14:

> Locating a User's Blog

OK for me (except the erroneous "en-us" that I already mentioned here)

> Identity Provider Discovery for OpenID Connect

OK for me (I assume not OK for Pete Resnick because there are no
details about the possible "rel" in the query and the possible links
in the response)

> Auto-Configuration of Email Clients

Useless and dangerous. 

> Retrieving Device Information

Dangerous, for security reasons, as mentioned in the IESG ballot