[Http-well-known] Revising the Well-Known URI registration policy (tldr; new draft, new list)

Mark Nottingham <mnot@mnot.net> Mon, 07 May 2018 12:16 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: http-well-known@ietfa.amsl.com
Delivered-To: http-well-known@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69DC012DA1D; Mon, 7 May 2018 05:16:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=OP7DwgTo; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=cBtboBhs
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 q_Jsk9QUlkLC; Mon, 7 May 2018 05:16:38 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAAD412DA11; Mon, 7 May 2018 05:16:34 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id C4DF222624; Mon, 7 May 2018 08:16:33 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 07 May 2018 08:16:33 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-transfer-encoding:content-type:date:from:message-id :mime-version:reply-to:subject:to:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=/K5SgmcH+Gw5k4m83mNWiPTqGPnUwuLLWKXT4Ed2W 4k=; b=OP7DwgTobmuLps/RW3KohUd6GXomcls8mws3XY4w4c/QZK1w04Mligzmq RI6/3Sy4lwrKoqURBCWoSfbionVnC6Kznk0/xnMgBcSNpSKpitvvhBZHhvNSW+FB vC2wQNq7MYET/5g06Pmw1svnr4fMEAOx4pOc+ahVfYIsWSPb5K6UAHIQwkZUFCS2 kV1rnZgYLI20ByuGlsFZJy4hMUrJV219TdkLJJ/fVoWYDNoH48m9Drl6KZkKqiNK /uS+AEYU03MzhNG8LFeAkmx0YiR2TVPoq5QY4AAZC996VkT4QHv/JNetAGss4NYU +pm5TyQzgeo8bXfVKIMOGNsf5sqiw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:reply-to:subject:to :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=/K5SgmcH+Gw5k4m83 mNWiPTqGPnUwuLLWKXT4Ed2W4k=; b=cBtboBhsomflLwHtTJ6Q2jAU9sbFFr5jo /KfAxFS2c2N+pw7paStGpN6E7Mzq0byXCos3/V4TeMaLV4yf33NC/YFyc+r0J8UN ++Pw+2lxYaHmjv3IRG3uKc8hQ1YOlY46NP5oJRMKhvgQ2wBgLWkwId0zFJ6Bv/sA UrJC7hy6VnXpofMDxGkX9HDAa5W59F3HGDw2NgTpqdJiolF83kw1Ka3rgSEIvXp1 7irtB4MJ5AvUZf9RQ7PIXe/vSeBwMjF7W1CVLL1+RKuDrGYfDyFA17NHRFKdpXxt hgRr8srpxOx//nB/XGMl/RlDvsoc6UWRKDbFWvm0BQOTLEnWWAk0Q==
X-ME-Sender: <xms:oUPwWjeR_ok89KG1PyQ_x4KCdyZ96yLwCiyAHcRdbF0pIii0dwlF1Q>
Received: from [192.168.1.25] (unknown [144.136.175.28]) by mail.messagingengine.com (Postfix) with ESMTPA id 3E41C102DA; Mon, 7 May 2018 08:16:31 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Reply-To: http-well-known@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Mon, 7 May 2018 22:16:29 +1000
Message-Id: <272B547C-35B1-46C0-90A2-D6167C346115@mnot.net>
Cc: Alexey Melnikov <aamelnikov@fastmail.fm>, http-well-known@ietf.org
To: DISPATCH list <dispatch@ietf.org>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/http-well-known/mgLgqd87Lqev2ovg75xFKC1xVLU>
Subject: [Http-well-known] Revising the Well-Known URI registration policy (tldr; new draft, new list)
X-BeenThere: http-well-known@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussion of HTTP Well-Known URIs <http-well-known.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/http-well-known>, <mailto:http-well-known-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/http-well-known/>
List-Post: <mailto:http-well-known@ietf.org>
List-Help: <mailto:http-well-known-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-well-known>, <mailto:http-well-known-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2018 12:16:46 -0000

Hi everyone,

At the DISPATCH session in London, it became clear that the consensus recorded in RFC5785 about the scope of use for Well-Known URIs didn't match that in the room; while the intended uses in 2010 were focused on site-specific policy and metadata, the mechanism has become attractive for other uses as well.

So, in consultation with Alexey, I reached out to the W3C Technical Architecture Group to see if they had any concerns about opening upon Well-known URI registrations to use cases beyond what's countenanced by RFC5785, since the TAG was originally consulted when we established the registry:
  https://github.com/w3ctag/design-reviews/issues/237

The answer seems to be that they're not too concerned about architectural issues here. That being the case, I think it's reasonable to revise 5785 to allow broader use, and would like to confirm that direction with the broader community.

I've started to reflect that in a revision of my draft:
  https://mnot.github.io/I-D/rfc5785bis/

Diff from previous:
  https://tools.ietf.org/rfcdiff?url2=draft-nottingham-rfc5785bis-05.txt#diff0001

Alexey has created a mailing list to discuss the future of Well-Known URIs here:
  https://www.ietf.org/mailman/listinfo/http-well-known

If you have suggestions or feedback on this draft, concerns about this change, or other input, please head on over there to discuss.

Cheers,

P.S. Note that Reply-To is set to that list.

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