IETF Logo Mail Archive

Re: Request for well-known URI: matrix

"J. Ryan Stinnett" <jryans@matrix.org> Tue, 09 April 2019 09:46 UTC

Return-Path: <jryans@matrix.org>
X-Original-To: wellknown-uri-review@ietfa.amsl.com
Delivered-To: wellknown-uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C755E12079C for <wellknown-uri-review@ietfa.amsl.com>; Tue, 9 Apr 2019 02:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=matrix.org
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 0_8Tu4Bl-vuC for <wellknown-uri-review@ietfa.amsl.com>; Tue, 9 Apr 2019 02:46:05 -0700 (PDT)
Received: from hermes.matrix.org (hermes.matrix.org [83.136.254.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8B32120792 for <wellknown-uri-review@ietf.org>; Tue, 9 Apr 2019 02:46:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=matrix.org; s=hermes; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version:Content-Type; bh=oI7JiBWlhZ2lTk/b9/cK9ZbCH2TH8cp42j77kLeEtQs=; b=aHrTZjb+nwgQsqzChKudMsTm/CXaseDM7i1BGn7CXIs1tdV7gTopImk/OpdkWEumJOIqr47P8YSN9ZKUwTC75IdV9/PBM/+2uJzsZlUSWdbp1hqrl2Xvp2e39SMtz80faGeUHw12b5T7upvlVfaE0HBfazwRRAT+U0S12ti7xLQe1YsdXb5AvClXdqRIkTIDgRh/l11r6N7LjOGPaakG1ASrkFiMjWHy91srZM4JuYq8w1wqg+qvpbCLlR4GXFujy/bLFlCERgqHTwxXKI9bEqd3uRudF6kz1Xb8AC9He079F4jgYEZfgLElBkumaLCBujwAJeqYtMYEVaS8HoXfbQ==;
Received: from [80.250.101.234] (helo=[192.168.1.127]) by hermes.matrix.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <jryans@matrix.org>) id 1hDnKN-0004AQ-Lu; Tue, 09 Apr 2019 09:46:03 +0000
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Subject: Re: Request for well-known URI: matrix
From: "J. Ryan Stinnett" <jryans@matrix.org>
In-Reply-To: <7C3D1C2E-09FB-42DA-B168-E442F2310D8A@mnot.net>
Date: Tue, 09 Apr 2019 10:46:03 +0100
Cc: wellknown-uri-review@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <03DB9FA1-CD98-4CD9-857A-F9CE66638ED9@matrix.org>
References: <97A8B53E-6127-4E72-AAEF-9D74E4A976AB@matrix.org> <7C3D1C2E-09FB-42DA-B168-E442F2310D8A@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wellknown-uri-review/wMPmgoLhF65AgEPqVo8Qv-OMlZk>
X-BeenThere: wellknown-uri-review@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Well-Known URI review list <wellknown-uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wellknown-uri-review>, <mailto:wellknown-uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wellknown-uri-review/>
List-Post: <mailto:wellknown-uri-review@ietf.org>
List-Help: <mailto:wellknown-uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wellknown-uri-review>, <mailto:wellknown-uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2019 09:46:10 -0000

> On 8 Apr 2019, at 01:55, Mark Nottingham <mnot@mnot.net> 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 Matrix.org Foundation C.I.C.
  https://matrix.org
Specification document(s):
  Matrix Client-Server API
  https://matrix.org/docs/spec/client_server/latest.html#well-known-uri
  Matrix Server-Server API
  https://matrix.org/docs/spec/server_server/latest.html#get-well-known-matrix-server

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

v2.23.0 | Report a Bug | By Email