

## Secure channel
@ -882,29 +882,29 @@ A threat analysis has been done within each of the key layers in the proposal ab
While this feature is in development the new API endpoints should be exposed using the following unstable prefix:
- `/_matrix/client/unstable/io.element.mscYYYY/rendezvous` instead of `/_matrix/client/v1/rendezvous`
- `/_matrix/client/unstable/io.element.msc4388rendezvous` instead of `/_matrix/client/v1/rendezvous`
Additionally, the feature is to be advertised as unstable feature in the `GET /_matrix/client/versions` response, with the
key `io.element.mscYYYY` set to true. So, the response could look then as following:
key `io.element.msc4388` set to true. So, the response could look then as following:
```json
{
"versions": ["..."],
"unstable_features": {
"io.element.mscYYYY": true
"io.element.msc4388": true
}
}
```
### Unstable QR code format
The unstable value of `IO_ELEMENT_MSCYYYY` should be used instead of `MATRIX` in the QR code.
The unstable value of `IO_ELEMENT_MSC4388` should be used instead of `MATRIX` in the QR code.
A full example for an existing device using ephemeral public key `2IZoarIZe3gOMAqdSiFHSAcA15KfOasxueUUNwJI7Ws` (base64
encoded), at rendezvous session ID `e8da6355-550b-4a32-a193-1619d9830668` on homeserver `https://matrix-client.matrix.org` is as follows: (Whitespace is for readability only)