You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Section 2.1 of server-to-server API describes the usage of a _matrix._tcp SRV record to discover the service hostname and port. However the matrix service name is already registered for use with the MATRIX Remote AV Switching protocol, as per the Service Name and Transport Protocol Port Number Registry of IANA.
To avoid conflicts with existing infrastructure, Matrix s2s should use a different service name, examples could be matrix-server or matrix-org. Also, please make sure to register the new service name with the registry to avoid future conflicts.
The text was updated successfully, but these errors were encountered:
turt2live
added
the
feature
Suggestion for a significant extension which needs considerable consideration
label
Dec 11, 2018
richvdh
transferred this issue from matrix-org/matrix-spec-proposals
Mar 1, 2022
turt2live
added
meta
Something that is not a spec change/request and is not related to the build tools
and removed
feature
Suggestion for a significant extension which needs considerable consideration
A-S2S
Server-to-Server API (federation)
labels
Jun 16, 2023
Section 2.1 of server-to-server API describes the usage of a
_matrix._tcp
SRV record to discover the service hostname and port. However thematrix
service name is already registered for use with theMATRIX Remote AV Switching
protocol, as per the Service Name and Transport Protocol Port Number Registry of IANA.To avoid conflicts with existing infrastructure, Matrix s2s should use a different service name, examples could be
matrix-server
ormatrix-org
. Also, please make sure to register the new service name with the registry to avoid future conflicts.The text was updated successfully, but these errors were encountered: