Skip to content

MSC4040: Update SRV service name to IANA registration #4040

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
turt2live merged 5 commits into from
Aug 19, 2023
Merged

MSC4040: Update SRV service name to IANA registration #4040

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
5dd5cc8
Update SRV service name to IANA registation
turt2live Aug 4, 2023
4622477
rrrrrrrrrr
turt2live Aug 4, 2023
bbfb967
Clarify step 3 changes
turt2live Aug 9, 2023
d68651a
Fix security considerations
turt2live Aug 9, 2023
3b75971
Update SRV steps per https://github.com/matrix-org/matrix-spec/pull/1615
turt2live Aug 9, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update SRV steps per matrix-org/matrix-spec#1615
  • Loading branch information
@turt2live
turt2live committed Aug 9, 2023
commit 3b75971cbf6118718918045215f9479618b3b6e0
12 changes: 6 additions & 6 deletions proposals/4040-update-srv-service-name.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,15 +71,15 @@ The new steps thus become:
are then made to the resolve IP address and a port of 8448, using a `Host` header of `<delegated_hostname>`.
The target server must present a valid certificate for `<delegated_hostname>`.

4. **(ADDED)** If the `/.well-known` request resulted in an error response, a server is found by resolving an
SRV record for `_matrix-fed._tcp.<hostname>`. This may result in a hostname (to be resolved using AAAA or A
records) and port. Requests are made to the resolved IP address and port, using 8448 as a default port, with
a `Host` header of `<hostname>`. The target server must present a valid certificate for `<hostname>`.
4. **(ADDED)** If the `/.well-known` request resulted in an error response, a server is found by resolving
an SRV record for `_matrix-fed._tcp.<hostname>`. This may result in a hostname (to be resolved using AAAA or A
records) and port. Requests are made to the resolved IP address and port, with a `Host` header of `<hostname>`.
The target server must present a valid certificate for `<hostname>`.

5. **(DEPRECATED)** If the `/.well-known` request resulted in an error response, a server is found by resolving
an SRV record for `_matrix._tcp.<hostname>`. This may result in a hostname (to be resolved using AAAA or A
records) and port. Requests are made to the resolved IP address and port, using 8448 as a default port, with a
`Host` header of `<hostname>`. The target server must present a valid certificate for `<hostname>`.
records) and port. Requests are made to the resolved IP address and port, with a `Host` header of `<hostname>`.
The target server must present a valid certificate for `<hostname>`.

6. (unchanged) If the `/.well-known` request returned an error response, and the SRV record was not found, an IP
address is resolved using CNAME, AAAA and A records. Requests are made to the resolved IP address using port
Expand Down