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

John Bradley <ve7jtb@ve7jtb.com> Mon, 23 April 2012 21:14 UTC

Return-Path: <ve7jtb@ve7jtb.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 4381A11E807F for <apps-discuss@ietfa.amsl.com>; Mon, 23 Apr 2012 14:14:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.54
X-Spam-Level:
X-Spam-Status: No, score=-3.54 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 tKb5GAWdtJck for <apps-discuss@ietfa.amsl.com>; Mon, 23 Apr 2012 14:14:29 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 698F411E8088 for <apps-discuss@ietf.org>; Mon, 23 Apr 2012 14:14:29 -0700 (PDT)
Received: by qcsq13 with SMTP id q13so8662778qcs.31 for <apps-discuss@ietf.org>; Mon, 23 Apr 2012 14:14:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=IPNifQi9PzsRTW0rzEhtwgmuPj+v2W42tmeyqzUrC7I=; b=RfoYqiN5fMBvH2ydXMDRRwE+sNTb3gQT+eGNEs0JaXdycKBaGtHx3UQI8RBe4OExZO DzHE7j8ydDaIgGn5EgFqXJARAyrWW9T6sFdaeQkY5tJcli0vRE8B4lNCW1lQaZgncdZ4 TFGtzMsRY0T8JkY3O/pPoT6Dd/pVy+wPEJlBajxJBTeEcefZLiga30CGB71l4iWBVn+y vZ+l+IHf4BF8xlAcP60LcxM9zkvz3Bels7AcFPeGdY5AphqMXwfP8yvf++u7hrcltPU/ 5Ooinm2R1kXLjrqsZApBeY8fzVCl5n7Yna2rO8NYYjycBeHtA2WIMLzBnaHq+eI96NPH Lpzw==
Received: by 10.224.222.145 with SMTP id ig17mr9363058qab.11.1335215668845; Mon, 23 Apr 2012 14:14:28 -0700 (PDT)
Received: from [192.168.1.213] (190-20-21-61.baf.movistar.cl. [190.20.21.61]) by mx.google.com with ESMTPS id g10sm23577976qae.11.2012.04.23.14.14.26 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 23 Apr 2012 14:14:27 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/signed; boundary="Apple-Mail=_2E7B814B-1258-4755-9A86-B5C3CFF98713"; protocol="application/pkcs7-signature"; micalg="sha1"
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <4F95A0C9.3020303@stpeter.im>
Date: Mon, 23 Apr 2012 18:14:24 -0300
Message-Id: <EA409E1D-18EB-4CF3-ABF8-3D1BDF206EE5@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> <CAA1s49V4CA0+pi4Y4LGZFfXp-OXy-=7ZtMWSCX3M6JOWi0E48g@mail.gmail.com> <599EB342-8023-453D-977E-DC318637B6E9@ve7jtb.com> <4F95A0C9.3020303@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1257)
X-Gm-Message-State: ALoCoQmmWgT1od4ZLk39zf15sbwIwFZ7y7BlTXkVAMQ8rN14wVUN2L2w1O2ZaxJnzMCqb8ExNpgM
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
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: Mon, 23 Apr 2012 21:14:30 -0000

It is not my assumption.   

From a practical point of view with openID Connect, you couldn't host a IdP on a server that only supports static pages.

I think that Paul's example of a site supporting
curl -v https://packetizer.com/.well-known/host-meta.json?resource=acct:paulej@packetizer.com

Is the bar.   There are several ways to do that, so I don't think it is unreasonable.

John B.

On 2012-04-23, at 3:34 PM, Peter Saint-Andre wrote:

> Picking on a minor point here...
> 
> On 4/23/12 12:27 PM, John Bradley wrote:
> 
>> That way large sites can optimize and small sites could still use static
>> files.
> 
> Is there evidence for the assumption that large services will serve
> their data via an API whereas small services will serve their data via
> static files? It seems clear to me that many small services might not
> host static files, e.g., because they use a content management system or
> community software application that automatically pulls data out of a
> database of users and serves up some of that information in the form
> defined by the WebFinger spec (or SWD or whatever). I rather doubt that
> large services will host static files, but let's not base our design
> decisions on a false premise about smaller services.
> 
> Peter
> 
> -- 
> Peter Saint-Andre
> https://stpeter.im/
> 
>