Re: Request for well-known URI: matrix

Mark Nottingham <> Wed, 10 April 2019 00:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 030431200B6; Tue, 9 Apr 2019 17:07:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
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: (amavisd-new); dkim=pass (2048-bit key) header.b=DxXkGEnv; dkim=pass (2048-bit key) header.b=pFtDmwIe
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id kZHVMo3kGjiO; Tue, 9 Apr 2019 17:07:18 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B37401200F7; Tue, 9 Apr 2019 17:07:18 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal []) by mailout.west.internal (Postfix) with ESMTP id E573A2F2; Tue, 9 Apr 2019 20:07:17 -0400 (EDT)
Received: from mailfrontend2 ([]) by compute3.internal (MEProxy); Tue, 09 Apr 2019 20:07:18 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=R kftIcGPTeM5VyN8eb+8w62Rg9EGFQQdjkivqqNXjKQ=; b=DxXkGEnvi+NmLagUw LBnEU/TFxv9slSGzfVDQAalL29DO35MV0fi9T3dvSBba0zxsP+RuUvO3JEk3XeXG Yv0paylBwNjFO8nXEuxWBqFfq8wpKzcY/DQ3ej/nkAVMneEFyye+YRZHlo5cZuep NUaev0cSUaXzNCPRBpTwxmISdHqBZ80MmGSfDp4VdghpdTN9xEVCBwV0pjDFV4xg 9mqf5fbdNcdQGk77/RoSbywWbRmi/KGQGbPCn6aVRSmUkeakW+sfU/Jvnn5og8x8 pYh4aCPLxGztzXwCxBE0otFYk/XXozReuaTJjR+d6vCsj9qwF1WpVdShUAiI+H6c Q9mUQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=; 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=fm2; bh=RkftIcGPTeM5VyN8eb+8w62Rg9EGFQQdjkivqqNXj KQ=; b=pFtDmwIepS8+uSqX1hl8cDeRr1/nm4HR8CJOyyo9ak1v5l9q576UYppZ2 LRemIKVWoRizKi6NR8U6jQMWB5BpERyIkNMuGGaad4q3xg2sMgL5OOawkyPxCogE 3+sCKKt7fO8Ho6yRzSs1BdlBs5mKuR9EqHCH+CToC+IWwUTmOU2zthBcrJEUJgBk 7A1/JicNozipapnZm1USlvw1K9+dpqgfMFrqUMgLd10CgxQNy1cUvD/EWcPN9OVL arYr82nyj7YcfosDjibMfQm7pLupGo8MWx4c94C/gevC4t22DJ2oN4OBn7gUoOx6 nGi/Qfvf+YnKuN9GLpj9+HbJx/d+Q==
X-ME-Sender: <xms:tDOtXAOSv_OZ9pzypqYef9X94yQ5hb1me1Xnuap_LLY7vK_psAR7BA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudeigdeftdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurheptggguffhjgffgffkfhfvofesthhqmh dthhdtvdenucfhrhhomhepofgrrhhkucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhn ohhtrdhnvghtqeenucffohhmrghinhepmhhnohhtrdhnvghtpdhmrghtrhhigidrohhrgh enucfkphepudeggedrudefiedrudejhedrvdeknecurfgrrhgrmhepmhgrihhlfhhrohhm pehmnhhothesmhhnohhtrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:tDOtXN6XWBz_9Jb8Zio_8KlZYJeKZ_TPzLvRnSGOrYQ4_WsFWOvcqQ> <xmx:tDOtXANTRfmYqJj6R8wqwF5-4oiYoIIgAjZHx_g4AuZC0myBQvJgyA> <xmx:tDOtXAgCq-iZiW-Uw7g-Q1YO7eAjET1s-9VC7rpwacuJSw9iXAqfJA> <xmx:tTOtXLDTtLiUEzMkb32J69Eg2fl1APlF-MXg3xIMHrUtJ9IqnFIVGg>
Received: from (unknown []) by (Postfix) with ESMTPA id 001BC10319; Tue, 9 Apr 2019 20:07:14 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Subject: Re: Request for well-known URI: matrix
From: Mark Nottingham <>
In-Reply-To: <>
Date: Wed, 10 Apr 2019 10:07:12 +1000
Cc:, ART Area <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <>
To: "J. Ryan Stinnett" <>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Well-Known URI review list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 10 Apr 2019 00:07:20 -0000

Sounds good. 

There's a new field in the template that needs to be filled - "status" (added by RFC5785bis, currently approved and at the RFC Editor).

My inclination here is to make it "permanent". 5785bis requires consultation with the community for that (since AFAICT is not recognised by the IETF as an Open Standards body, in the sense of RFC2026). I've copied here to see if anyone has an issue with that. 

If we don't hear pushback over the next few days, we'll get IANA to register it.


> On 9 Apr 2019, at 7:46 pm, J. Ryan Stinnett <> wrote:
>> On 8 Apr 2019, at 01:55, Mark Nottingham <> wrote:
>> This request looks good, but I wonder if you could provide a more stable URI for the specification document? If not, you'll need to make a request to update the entry each time it changes.
> Thanks for the initial review and feedback. I agree a stable URI does sound simpler. Let's go with the following then:
> URI suffix: matrix
> Change controller:
>  The Foundation C.I.C.
> Specification document(s):
>  Matrix Client-Server API
>  Matrix Server-Server API
> The "latest.html" path points to the latest versioned release of each spec document, so that seems like a better fit for the .well-known registry.
> Thanks,
> J. Ryan Stinnett

Mark Nottingham