IETF Logo Mail Archive

[Http-well-known] Speculative registrations

Mark Nottingham <mnot@mnot.net> Thu, 19 July 2018 15:29 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 1ACAC130D7A for <http-well-known@ietfa.amsl.com>; Thu, 19 Jul 2018 08:29:58 -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, HTML_MESSAGE=0.001, 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=rDlMTsDa; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=qUvjjgUz
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 wVc1YvheZq0a for <http-well-known@ietfa.amsl.com>; Thu, 19 Jul 2018 08:29:54 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93112130E28 for <http-well-known@ietf.org>; Thu, 19 Jul 2018 08:29:54 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id E322D21E9E for <http-well-known@ietf.org>; Thu, 19 Jul 2018 11:29:53 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 19 Jul 2018 11:29:53 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:date:from:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=LsaUAZ v7RXs+TDLMEHO2go2i7n3BBwsEte++xatZRLs=; b=rDlMTsDan4CVvvIynUWeyD S/MoKQ54GDqm0fLokXwL6bOj65PA4mGzIg5lYBh0tSH4pW6SGeASZTGitZMek7eO 19sneXq8ldueS1kJJ0BtOCktUj3WhriHnZFlXw8zCwRsfnRxxQsbuSmIVK8Be7qW 0yYUZ4YPIgjbTwaWNM+e0fNMeTjugynNeaTpviA35rvrxkOTjYY5/uLoEYZPfxZd 5zPo0u7lxf7rA4tcS39d0km8ce4grpLeTWivSUkzMIei+ffytRCRkTxsSrDBbMmh /sPnG0oh+caqbTrfGOFVtUbrKWfSqwda6NNpcYFRKtugcShllTGXyxxjhYpJZgFw ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:references:subject:to:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=LsaUAZv7RXs+TDLMEHO2go2i7n3BBwsEte++xatZR Ls=; b=qUvjjgUzJuaEnDZJVAS7UXC7E+XhO+fkyIM8yaGy4gR44kOL8TyR2/hW/ Kn9qlg1VgNFl9B4/CAr3avqW/ADYLTe1ghRjzcI2poedHfQB7qQszYHuKpwiCemf kRBmkLEur5Wbh49Cz8kN1oitUpdL9cjuntNvbIDeStoylEb0Bqps5MfoeDrSOrZS gA6hkSVwmADwCztSP3IwWiQpG1Jp9qBSyUZMmllLjcpAMnzpFUKtEu7gpT+Yoyn2 kx/1HxGZxjzyrgKttbiBF54vcKvrVoDqw9yVfnsAWGf5D8KKu5vKBTs5cSSi2X8b lK4zRyCRDpcL6OuUbxQl6nnCiSp/w==
X-ME-Proxy: <xmx:ca5QW-eN9SOiIRCaKsq5XjTGOkeqe04d_iTjzMCyPX-x5QM5mYOEwg> <xmx:ca5QW1lev6NA4guxvIBnf6cA_gCOgkqeyyKJHBe0X5mSN77uA1RXvA> <xmx:ca5QW5AyvZE-q3lKiKHnlNIpxZhI7gEil6SgRTc0PbOoON7DiTSaag> <xmx:ca5QW3OpNg8uiQGenJQaixiXk4fGMtX8WWJ0NbogIWdm7J0OzDgpLw> <xmx:ca5QWwP-_-hG2JmAg1gh38_g-u031at1UHOQmM3fXrgWZLrh3v2jlA> <xmx:ca5QW9BLhBaO5KfgQtiYxuaxULXP45rp1jHa76s6SWhE2hvkOAJ7Cg>
X-ME-Sender: <xms:cK5QW6lNSM9ErMBFQqsX3WDJlBKJAvOSav5Cdh8t_gaD1XbhzWfrxg>
Received: from dhcp-873a.meeting.ietf.org (dhcp-873a.meeting.ietf.org [31.133.135.58]) by mail.messagingengine.com (Postfix) with ESMTPA id B86F010268 for <http-well-known@ietf.org>; Thu, 19 Jul 2018 11:29:52 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B93FD98D-B54E-45CA-866C-25BC9FF4D7C3"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Message-Id: <0EA43FD1-E32B-47D7-8DAA-24EC74C3EA39@mnot.net>
References: <CAC+nZg74Brw0HC=yVjr_zdrSaSuitKvGxsqNg4DFoYBL88zwKA@mail.gmail.com>
To: http-well-known@ietf.org
Date: Thu, 19 Jul 2018 11:29:51 -0400
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/http-well-known/HEIaKnuD_2q8qKAJn1n85-qAznM>
Subject: [Http-well-known] Speculative registrations
X-BeenThere: http-well-known@ietf.org
X-Mailman-Version: 2.1.27
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: Thu, 19 Jul 2018 15:29:58 -0000

Question for folks ---

The registration request below is not unusual basically, someone has had an idea, written up a pseudo-spec (here, on GitHub), and requested registration.

Under both RFC5785 and the proposed bis, I don't think there are strong grounds for refusing this request. 

In particular, there is no evidence of deployment here, or even collaboration with others. Does that cause any discomfort? 

On the one hand, we want to be open and have a low bar for registration; on the other, speculative requests like this are likely to grow, and if there are too many (especially with overlapping or competing semantics), it can make the registry less useful. 

Any thoughts about this?

My inclination is to encourage collaboration / demonstrate at least interest in deployment before registration, but that would just be advice, not reason for refusal. I do wonder if we need a "provisional" status, with the understanding that if no deployment is demonstrated within (say) a year, it is de-registered.

Cheers,


> Begin forwarded message:
> 
> From: matthew churcher <matt@churcher.me>
> Subject: Request for well-known URI: anti-phishing.json
> Date: 17 July 2018 at 5:56:07 pm GMT-4
> To: wellknown-uri-review@ietf.org
> Archived-At: <https://mailarchive.ietf.org/arch/msg/wellknown-uri-review/lCkGMjHVQsMdRLbCHJjbqUh5uuU>
> 
> URI suffix: 
> anti-phishing.json
> 
> Change controller: 
> Matthew Churcher <matt@churcher.me <mailto:matt@churcher.me>>
> 
> Specification document(s): https://github.com/SecureFrom/anti-phishing.json <https://github.com/SecureFrom/anti-phishing.json>
> 
> Related information: This is a new initiative which currently has no citations. I'm looking to provisionally secure a well-known uri in preparation to circulate a draft specification for wider discussion. Any comment is welcome via email or GitHub.
> 
> _______________________________________________
> wellknown-uri-review mailing list
> wellknown-uri-review@ietf.org
> https://www.ietf.org/mailman/listinfo/wellknown-uri-review

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

v2.1.27 | Report a Bug | By Email