[apps-discuss] An alteration to the WebFinger Spec

"Paul E. Jones" <paulej@packetizer.com> Thu, 01 November 2012 06: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 3370821F8519 for <apps-discuss@ietfa.amsl.com>; Wed, 31 Oct 2012 23:40:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.155
X-Spam-Level:
X-Spam-Status: No, score=-2.155 tagged_above=-999 required=5 tests=[AWL=0.443, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 aA8zqP4qJyts for <apps-discuss@ietfa.amsl.com>; Wed, 31 Oct 2012 23:40:08 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id CAD9621F8516 for <apps-discuss@ietf.org>; Wed, 31 Oct 2012 23:40:05 -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 qA16e2vi018577 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 1 Nov 2012 02:40:02 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1351752003; bh=2VtAS8UXg5rqszksVtJOdNHjZIoTJYVBd0VB8ylQHWE=; h=From:To:Subject:Date:Message-ID:MIME-Version:Content-Type; b=df3MbXhhVBTdKKblSDtXT1Nul6uT7Anz6Dj+k5Ni3i79Yz3r05KXaTFnMQnEaKcI9 JhlTg98332YEo1WXf0lIZM87sxdcROiAZBDky219aBzQRNFOhEjARHkVZ4fECUnor0 IoKrl+Db1C4CZqNsyJVqYi0PXgN0foTIKiG1c74U=
From: "Paul E. Jones" <paulej@packetizer.com>
To: apps-discuss@ietf.org, webfinger@googlegroups.com
Date: Thu, 01 Nov 2012 02:40:08 -0400
Message-ID: <011a01cdb7fb$bca72f80$35f58e80$@packetizer.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_011B_01CDB7DA.359652D0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac23+u3YVAhN5wz+SoC7W4GHhl67bg==
Content-Language: en-us
Subject: [apps-discuss] An alteration to the WebFinger Spec
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: Thu, 01 Nov 2012 06:40:10 -0000

Folks,

 

Here's a proposal that some might find acceptable and others will probably
love.  It's just a proposal, so no bazookas, please, from those who will
find it troubling ;-)

 

http://hive.packetizer.com/users/paulej/internet-drafts/draft-ietf-appsawg-w
ebfinger-03-ALT.txt

 

What I did with this text is the following:

.         Included all of the current -03 text (not yet published, but text
folks proposed on the list)

.         Removed every reference to XML and XRD

.         Stated that the default format for /.well-known/host-meta.json is
JRD

.         Stated that the default format for /.well-known/host-meta is
implementation-dependent, so clients MUST use the Accept header to
explicitly request the desired representation when using that resource (this
is key to backward/forward compatibility and proper use of HTTP and Accept)

.         Removed the "account link relation" section

.         Removed the interop considerations section, since some feel there
is no need and I think requiring use of "Accept" on host-meta will address
any interop concerns

.         Removed the XML appendix that gave some people heartburn

 

This shaved off 6 pages of text, I think will still give us
backward-compatibility for those who have asked for it, but more clearly
positions JSON / JRD as the only format developers need to worry with.

 

Tell me what you think.

 

Paul