IETF Logo Mail Archive

Re: [art] On BCP 190

Mark Nottingham <mnot@mnot.net> Wed, 24 July 2019 18:03 UTC

Return-Path: <mnot@mnot.net>
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 4271012015B for <art@ietfa.amsl.com>; Wed, 24 Jul 2019 11:03:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=Ig0nA0jt; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=0CpcbIlA
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 ZcNAKPa5czsO for <art@ietfa.amsl.com>; Wed, 24 Jul 2019 11:03:28 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0BA7120059 for <art@ietf.org>; Wed, 24 Jul 2019 11:03:28 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id BFB253CC; Wed, 24 Jul 2019 14:03:27 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Wed, 24 Jul 2019 14:03:28 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=P NZw09Sb7joyVPnlYJvAphF0MW7jqiyxIC9ISt7H3Ts=; b=Ig0nA0jt5MxGLDh/p DAtBWfbYo4xO9QxXU2VSc2fAPlzQSgmedCT0mbQEhk/m82rw1/ZcIPBTpEm9C8yR BlNwgW0K9THYw9zVTzatKQkMjeLoi7sKH/fHKszxqV87BGg+R5cYmVJD93iWbKcI SnhSTyx/q0I2cS756Ds2GZAmNg8si0uV6kk0XUxus/zQX9odTFZg/pDnGVS9EAXa WSjxA3vf7+YPFxji53k8vBpQXQmHQqd/FLYnlacvsZdWqdHNO38nj9pbnD/w1BfM GgQj2MZN5iB+coligNGsIL7WTTuRQw9LM1inJp8YIcyB2JyRr+xSVnnjsLjyQMAy d9ooQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=PNZw09Sb7joyVPnlYJvAphF0MW7jqiyxIC9ISt7H3 Ts=; b=0CpcbIlA2JtXjD3Bds2pHcJd3eD/77AelqvnichL/1HaP0DgH6wupYz5e OUt3z1zIygoZTApYC9jhcNJB45CjrjhlO00sMgc/bmWGs+apvo6pwMk1qZhoPSHN jsz+2D16GqvYyZW5n0MU10mVXEgGrDXmGdB8U3xuS8V/U5Lmy5UuTx+kqx0CuXB5 0E5dPVjfFm++Vz8NncPWIY14ZyzFNsQGmiQSo30bPmExMevzHDrXhglV/CkvwP4Z +U3Nn6+GSqFLSZSyxayULg4/DkVR2nZ7ygLLH8zYYxAvuDHFdg//11rKGyXTVdBA RQxcsal4xiceVNovigxB5z1wDeQiw==
X-ME-Sender: <xms:bp04XT22laUhe9mTwyo7YrAlxr7HwRBP9oh_IKT_TK5lg1RbwTXH8g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrkedtgdduudehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhk ucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinh epughothgrthdrrghtpdhmnhhothdrnhgvthenucfkphepfedurddufeefrdduheehrddv geeknecurfgrrhgrmhepmhgrihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvghtnecuve hluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:bp04XWUy3bofoZvudUUUfPnal4XjUxOzPOX9vsgilXpptnfqoPnx0w> <xmx:bp04XQ3reGAtJfnGDf5gfp1K70ZAsXn_pg9J2a0bHQECbIzjP3LbwQ> <xmx:bp04XXhDNZB2wjJbIA0pKJ1lBaVFEA1aEqhJm6UeO6U4vzPF_1KbFA> <xmx:b504XdNJ3iWvjCuxlcDl8my7X6pgIxO9ZKQUYDsECGYvGiaougwRKQ>
Received: from dhcp-9bf8.meeting.ietf.org (dhcp-9bf8.meeting.ietf.org [31.133.155.248]) by mail.messagingengine.com (Postfix) with ESMTPA id C0F11380076; Wed, 24 Jul 2019 14:03:25 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <alpine.DEB.2.20.1907241829200.8471@grey.csi.cam.ac.uk>
Date: Wed, 24 Jul 2019 14:03:24 -0400
Cc: Jacob Hoffman-Andrews <jsha@letsencrypt.org>, ART Area <art@ietf.org>, Devon O'Brien <devon.obrien@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B21F2C42-FCF5-4F54-BB28-9C8D57ED4A3D@mnot.net>
References: <58BF6171-03BB-4F83-940F-3A101EFDD67F@mnot.net> <CAN3x4Q=Jo1uBvfCG6CSrociYgdG+E4jq+4cB1txPjgboth2q9g@mail.gmail.com> <372FA049-7B33-4981-A0E0-41BD454CB770@mnot.net> <alpine.DEB.2.20.1907241829200.8471@grey.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/L0E-xV3cZaSGE9zlsaI4xcNPJCQ>
Subject: Re: [art] On 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 18:03:30 -0000

The applicable text is:

"""
At the same time, it has become more popular to use HTTP as a
 substrate for non-Web protocols.  Sometimes, such protocols need a
 way to locate one or more resources on a given host.
"""

(Not particularly defending the clarity of that text overall -- we were trying to graft an expanded set of use cases onto an existing spec).

Cheers,


> On 24 Jul 2019, at 2:00 pm, Tony Finch <dot@dotat.at> wrote:
> 
> Mark Nottingham <mnot@mnot.net> wrote:
>> 
>> 1) Using .well-known. This is precisely what well-known is for,
> 
> I'm still having difficulty understanding this. RFC 8615 says:
> 
>   Some applications on the Web require the discovery of information
>   about an origin [RFC6454] (sometimes called "site-wide metadata")
>   before making a request. [...]
> 
>   When this happens, one solution is to designate a "well-known
>   location" for data or services related to the origin overall, so that
>   it can be easily located. [...]
> 
> But CT isn't providing metadata about the origin overall. And CT has a
> separate mechanism for finding out where an endpointis located so it
> doesn't need a fixed well-known location.
> 
> Tony.
> -- 
> f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
> Irish Sea: South or southeast 3 to 5. Slight, occasionally moderate. Showers
> later. Good occasionally poor.

--
Mark Nottingham   https://www.mnot.net/

v2.23.0 | Report a Bug | By Email