From e789eb186a8f12fe2517d1b30c8e38989d3c3b5f Mon Sep 17 00:00:00 2001 From: Richard van der Hoff Date: Mon, 12 Nov 2018 14:02:44 +0000 Subject: [PATCH] link to MSC1711 --- proposals/1708-well-known-for-federation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/1708-well-known-for-federation.md b/proposals/1708-well-known-for-federation.md index bd2f32b8..8fa66c7a 100644 --- a/proposals/1708-well-known-for-federation.md +++ b/proposals/1708-well-known-for-federation.md @@ -7,7 +7,8 @@ Currently, mapping from a server name to a hostname for federation is done via them, and there may be other practical difficulties in their deployment such as poor support from hosting providers. [^1] - * It is likely that we will soon require valid X.509 certificates on the + * [MSC1711](https://github.com/matrix-org/matrix-doc/pull/1711) proposes + requiring valid X.509 certificates on the federation endpoint. It will then be necessary for the homeserver to present a certificate which is valid for the server name. This presents difficulties for hosted server offerings: BigCorp may be reluctant to hand over the @@ -140,4 +141,3 @@ will allow greater flexibility in deploying homeservers. [^1] For example, Cloudflare automatically "flattens" SRV record responses. -