Re: [art] Against BCP 190

Tony Finch <dot@dotat.at> Wed, 24 July 2019 12:57 UTC

Return-Path: <dot@dotat.at>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9281D120071 for <art@ietfa.amsl.com>; Wed, 24 Jul 2019 05:57:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5eu0tDVDi1Uo for <art@ietfa.amsl.com>; Wed, 24 Jul 2019 05:57:16 -0700 (PDT)
Received: from ppsw-30.csi.cam.ac.uk (ppsw-30.csi.cam.ac.uk [131.111.8.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AD04120058 for <art@ietf.org>; Wed, 24 Jul 2019 05:57:16 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:54616) by ppsw-30.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) id 1hqGpU-001oqW-fn (Exim 4.92) (return-path <dot@dotat.at>); Wed, 24 Jul 2019 13:57:12 +0100
Date: Wed, 24 Jul 2019 13:57:12 +0100
From: Tony Finch <dot@dotat.at>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
cc: Adam Roach <adam@nostrum.com>, Leif Johansson <leifj@mnt.se>, art@ietf.org
In-Reply-To: <3699ce1f-10bb-a1c0-8417-549284d18c49@cs.tcd.ie>
Message-ID: <alpine.DEB.2.20.1907241226330.8471@grey.csi.cam.ac.uk>
References: <791b33b8-4696-f69c-aca3-8838b2caafd8@sectigo.com> <6.2.5.6.2.20190713054207.0bbd9b58@elandnews.com> <008901d5410d$90607b00$b1217100$@gmail.com> <529b1f23-75e7-c426-f884-8dd07825182d@nostrum.com> <f834b9cd-0dff-7725-a959-6514c22d3ae4@mnt.se> <eb6485fa-d3dd-8eb9-7886-b17ef9d10f81@nostrum.com> <1e6e3567-59d8-b868-4917-603b848ae984@mnt.se> <c8e5c099-fd38-e206-7145-81eb2b3d467a@nostrum.com> <3699ce1f-10bb-a1c0-8417-549284d18c49@cs.tcd.ie>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/GRhsWaTO9u8QGiQUTEsHao6I7uo>
Subject: Re: [art] Against BCP 190
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jul 2019 12:57:19 -0000

Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> On 23/07/2019 16:46, Adam Roach wrote:
> >
> > The purpose of BCP 190 has never been to provide advantages to protocol
> > designers. That is, in fact, the opposite of its purpose. The purpose of
> > BCP 190 is to provide protections to the URI namespace and the people
> > who own its governance (e.g., domain owners) against protocol designers.
>
> Right. The difference with trans is that there aren't a mass
> of domain owners involved here, just a tiny tightly curated
> list of them and they're basically the ones who designed the
> protocol (give or take). There is no harm accruing here that
> I can see.

The problem that trans has also applies in circumstances where we might
expect much wider population of servers. It's a problem for any protocol
implemented as a server-side web app.

I have personal web space under https://www.chiark.greenend.org.uk/~fanf/
where I can install web apps, and paths under that prefix have been
delegated to me. I can't use that web space to deploy anything restricted
by BCP 190, so BCP 190 has the opposite of its intended effect of allowing
web server admins and their users to control their URL space, and allowing
them to decide where they would like to install apps.

I understand the point of using .well-known for information about the
server itself or about the server's domain name. I don't understand the
value of forcing an app to use .well-known when (like trans) it has a
completely configurable URL prefix.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Rattray Head to Berwick upon Tweed: South or southeast 3 to 5, but variable 2
for a time. Smooth or slight. Thundery showers at first in north, otherwise
fair. Moderate or good, occasionally poor.