IETF Logo Mail Archive

Re: [apps-discuss] WebFinger compromises

Dick Hardt <dick.hardt@gmail.com> Thu, 01 November 2012 05:35 UTC

Return-Path: <dick.hardt@gmail.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 3727621F8527 for <apps-discuss@ietfa.amsl.com>; Wed, 31 Oct 2012 22:35:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, 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 sNZH4T6rqrTv for <apps-discuss@ietfa.amsl.com>; Wed, 31 Oct 2012 22:35:08 -0700 (PDT)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3FAC321F84EF for <apps-discuss@ietf.org>; Wed, 31 Oct 2012 22:35:08 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id fb11so1483994pad.31 for <apps-discuss@ietf.org>; Wed, 31 Oct 2012 22:35:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=VI4CE4+3rDSPKPZXDCHWU6J8F1Gmv60dZaNcqR01TEs=; b=Sngy7VDpTB+ohE3YiPoevf+EcOaUHwdPAUkYBhm3o8gqTQym1S4k/UevwNZxV/ACff 9nG9ogDukD+CcOOgkmzigQz3vwGnvKnU7NkLlYb31gsPQdPJW5vF6OXyAfY/Yme9D/nc KubE79VVXOgkUBInny9xhxJF7Wbop+PMQp8+hA8eIRioxXgcfYdZM1F6opOB3o8+cE0J BNJ6cmGq22/Ez7o8r9nsJQDrWVW0Gvl94UzBET/y60YNcUAKQ/+pOgF6IEMD69MRGWIe aD8u/zDwQjb0ZgJX8m7qb9Ya6A2MgPtiqAdIttC4mWK5XV/JOQTufmQGyCWoYZQKGIg4 moXQ==
Received: by 10.66.90.36 with SMTP id bt4mr108248120pab.54.1351748104062; Wed, 31 Oct 2012 22:35:04 -0700 (PDT)
Received: from [10.0.0.4] (c-24-5-69-173.hsd1.ca.comcast.net. [24.5.69.173]) by mx.google.com with ESMTPS id ru4sm3467356pbc.25.2012.10.31.22.34.53 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 31 Oct 2012 22:35:03 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_DC055B66-3C3C-4913-B4BB-7D91765829BA"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Dick Hardt <dick.hardt@gmail.com>
In-Reply-To: <00e201cdb7e7$a5a67390$f0f35ab0$@packetizer.com>
Date: Wed, 31 Oct 2012 22:34:51 -0700
Message-Id: <F7642135-C776-4622-A1C3-E87F64523041@gmail.com>
References: <CAAkTpCqcijuj9m6yVgWXeZqrBWLDSbhbsDNfM1JmsmESa307qg@mail.gmail.com> <00c401cdb7c0$55fe5eb0$01fb1c10$@packetizer.com> <CAAkTpCqHb_L=xEN67AS69wisbQ2wDPi_y+Ta4h4rFdeqfSOY-Q@mail.gmail.com> <00e201cdb7e7$a5a67390$f0f35ab0$@packetizer.com>
To: webfinger@googlegroups.com
X-Mailer: Apple Mail (2.1499)
X-Mailman-Approved-At: Thu, 01 Nov 2012 08:02:47 -0700
Cc: public-fedsocweb@w3.org, apps-discuss@ietf.org
Subject: Re: [apps-discuss] WebFinger compromises
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 05:35:10 -0000

On Oct 31, 2012, at 9:16 PM, "Paul E. Jones" <paulej@packetizer.com> wrote:

> Brad,
>  
> Comments in green: 

that is fairly random!

> PEJ: Yeah, so how do we get to that thing we can build on?  Current requirements … bare bone … are:
> ·         Servers must support JSON, may support XRD (or TLV or whatever)

Only one.

> ·         Servers must make /.well-known/host-meta and /.well-known/host-meta.json resources accessible

Only one.

> ·         Servers must support the “resource” parameter

Discuss.

> This means the vanilla client on the Internet will query only for JSON.  Client developers have mostly said they want the simplest possible solution, which means most will send requests with the “resource” parameter. 

As a resource developer, I want a simple solution as well.

> More than one has expressed a desire to be able to cache /.well-known/host-meta to speed processing of resource-specific queries.

Early optimization in my opinion.

>  
> Personally, I think we have the solution in hand. If I change one thing, there is somebody who will not be happy. 

Trying to please everyone leads to a mediocre standard. Have we not learned anything from Apple? Not having a keypad on a phone was going to make some people unhappy. Worked out well at the end of the day.

> As compromises go, I think we’ve done pretty well.  I say that, because I know one can build both a client and server implementation quite easily and only one format they need to consider.

Not true. The server needs to know both.

-- Dick

v2.23.0 | Report a Bug | By Email