From 84178b1d39f428a23d2100d3f345e8d246fe8c74 Mon Sep 17 00:00:00 2001 From: Patrick Cloke Date: Thu, 1 Jul 2021 12:54:00 -0400 Subject: [PATCH] Add notes about the via key and authorised servers being out of sync. --- proposals/3083-restricted-rooms.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/proposals/3083-restricted-rooms.md b/proposals/3083-restricted-rooms.md index bd6b0a7e3..19ea0ab9c 100644 --- a/proposals/3083-restricted-rooms.md +++ b/proposals/3083-restricted-rooms.md @@ -206,6 +206,24 @@ restricting access via: These are just examples are not fully thought through for this MSC, but it should be possible to add these behaviors in the future. +### Interaction with `m.space.child` events + +[MSC1772](https://github.com/matrix-org/matrix-doc/pull/1772) defines a `via` +key in the content of `m.space.child` events: + +> the content must contain a via `key` which gives a list of candidate servers +> that can be used to join the room. + +It is possible for the candidate servers and the list of authorised servers to +not be in sync. In the case where there's no overlap between these lists, it may +not be possible for a server to complete the request. + +If there is some overlap between the lists of servers the join request should +complete successfully. + +A future MSC may define a way to override or update the `via` key in a coherent +manner. + ## Footnotes [1]: The converse restriction, "anybody can join, provided they are not members