From 1aa54c5ecb88ef5ce9a3760ccc6b5cf6316ae2af Mon Sep 17 00:00:00 2001 From: Jason Volk Date: Mon, 8 Sep 2025 06:22:18 +0000 Subject: [PATCH] MSC4344: Strike deprecated SRV service name. Signed-off-by: Jason Volk --- proposals/4344-strike-deprecated-srv.md | 36 +++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 proposals/4344-strike-deprecated-srv.md diff --git a/proposals/4344-strike-deprecated-srv.md b/proposals/4344-strike-deprecated-srv.md new file mode 100644 index 00000000000..676aec079c5 --- /dev/null +++ b/proposals/4344-strike-deprecated-srv.md @@ -0,0 +1,36 @@ +# MSC4344: Strike deprecated SRV service name + +The SRV service name `matrix` was deprecated by +[MSC4040](https://github.com/matrix-org/matrix-spec-proposals/pull/4040) +due to adverse possession. The replacement service name `matrix-fed` +became active on the same date of August 19, 2023. After an elapsed +grace-period of two years, the deprecated service name is to be stricken +from the specification. + +Upon activation of this change by the appropriate release-version of the +specification, implementations MUST NOT query for records using the +deprecated service name. Implementations MAY perform a Server Name +Resolution seeking their own domain for the purpose of alerting +administrators to the stricken record's use, and encourage removal. + +### Potential Issues + +Deployments which have not updated their name service records during the +grace-period will no longer be reachable over the federation. + +### Alternatives + +The service name retains its deprecated-but-active status quo: this +maintains a considerable amount of wasteful overhead within the Server +Name Resolution process. Due to the lack of necessity for this method of +indirection after the introduction of +[MSC1708](https://github.com/matrix-org/matrix-spec-proposals/pull/1708), +both the replacement and deprecated service names are often queried with +negative results, potentially doubling the load on the name service. + +### Security Considerations + +Deployments which are made unreachable by this proposal (see: Potential +Issues) will no longer have their federation public keys directly +obtainable, introducing non-zero exposure to matrix-spec/#383 during the +window of domain record replacement.