Re: [apps-discuss] Webfinger / SWD Issue #3: direct versus indirect discovery

Blaine Cook <romeda@gmail.com> Wed, 25 April 2012 21:45 UTC

Return-Path: <romeda@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 64AAD21E803C for <apps-discuss@ietfa.amsl.com>; Wed, 25 Apr 2012 14:45:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.524
X-Spam-Level:
X-Spam-Status: No, score=-103.524 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 BRyrMI2685xI for <apps-discuss@ietfa.amsl.com>; Wed, 25 Apr 2012 14:45:27 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 585C421E8037 for <apps-discuss@ietf.org>; Wed, 25 Apr 2012 14:45:27 -0700 (PDT)
Received: by lagj5 with SMTP id j5so482258lag.31 for <apps-discuss@ietf.org>; Wed, 25 Apr 2012 14:45:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=xbmJLRPvfFBNpF0VjHW70ts3jx2v5oS8nxrINEdpD2E=; b=cd8qEMffBBQgkaf+Z0v5b4upcAk44pDfn3tplYm3Sus8sco4Vh1EWo4/daa9YyhuSL vdI/ulthZWpaaPsnsFF4AMdXANBQpKW2nJ9rRemcBzhBQVnDNHj1MzVbN7CpJ9FZFYSp ExQw0IwRNzW4aDZ5qlTVEQzM58RMaGxaGZ+Mpbk8p6jPptzz0XlOSrB6E9kjgkrdoR9M GPwNiOCLkDaACMKFBrz8vV+oFA0G7Xxu4rIsyJdemf1Cb1y/uk6Y6frQz3XS9aowHcog PFA5sQRmZK7QOgNxi0m/6J4srGBT3CsJDGZTx4qv8fHcwo1JOg6lbd13yOVRgOdAD3lT sJVw==
Received: by 10.112.84.202 with SMTP id b10mr2177372lbz.7.1335390326151; Wed, 25 Apr 2012 14:45:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.152.24.229 with HTTP; Wed, 25 Apr 2012 14:45:05 -0700 (PDT)
In-Reply-To: <4CC716F1-F6A4-46CF-86FD-6636B1F84500@ve7jtb.com>
References: <4E1F6AAD24975D4BA5B168042967394366492EE5@TK5EX14MBXC284.redmond.corp.microsoft.com> <7AF88E80-2515-49A5-92F8-8C0CB9ED7F47@ve7jtb.com> <CAA1s49Xj8BinguuJcopsf6PpgX-ntfyMEJpGZfGYWHZPS=SGSA@mail.gmail.com> <943DD28B-D2AB-4247-B486-06C074C4BA12@ve7jtb.com> <054901cd2311$87a24fb0$96e6ef10$@packetizer.com> <4CC716F1-F6A4-46CF-86FD-6636B1F84500@ve7jtb.com>
From: Blaine Cook <romeda@gmail.com>
Date: Wed, 25 Apr 2012 22:45:05 +0100
Message-ID: <CAAz=scmAzFqmSSspAGQEWWr_LSr30MFDBXu80rKq2BGcZUKSxQ@mail.gmail.com>
To: apps-discuss@ietf.org
Content-Type: multipart/alternative; boundary="f46d04016c6d06db9104be87ca45"
Subject: Re: [apps-discuss] Webfinger / SWD Issue #3: direct versus indirect discovery
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: Wed, 25 Apr 2012 21:45:28 -0000

*sigh*

This is crazy. There are a half-dozen of us debating theoretical ways to
structure a thing that may or may not ever get used, so that some specs can
get finalised so that *maybe* Microsoft and Google can ship a new version
of OpenID (that doesn't adequately address one of the core usability
shortcomings of the first two OpenIDs).

I don't know if Evan Prodromou or anyone from Diaspora or anyone else who
has *actually tried to deploy* similar things is watching this thread, but
if they are, I hope they pipe up, because there is absolutely zero
consideration for actual implementations happening in this discussion.

Also, keep in mind that if *we're* confused about the host-meta processing
rules, or if my "single-code-path" arguments are being dismissed because
"it's easy either way", then we're in a lot of trouble. Refer to the fact
that we've switched from XML to JSON because XML is too hard for most
developers.

The point of all this is to make it accessible and easy, since we have a
chicken-and-egg problem. If this is going to work, it's going to take the
whole long tail, not just Microsoft and Google. The specs we have right now
clearly don't work, but idle speculation on our part isn't going to make
any of this work.

b.