From 8f89667469b8e925a3f5ad4e64d68a02e46921aa Mon Sep 17 00:00:00 2001 From: Hubert Chathi Date: Tue, 18 Jul 2023 22:34:31 -0400 Subject: [PATCH] use MSC number --- proposals/{xxxx-mls-key-backup.md => 4038-mls-key-backup.md} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename proposals/{xxxx-mls-key-backup.md => 4038-mls-key-backup.md} (98%) diff --git a/proposals/xxxx-mls-key-backup.md b/proposals/4038-mls-key-backup.md similarity index 98% rename from proposals/xxxx-mls-key-backup.md rename to proposals/4038-mls-key-backup.md index 0fca9fef84..75d821ee21 100644 --- a/proposals/xxxx-mls-key-backup.md +++ b/proposals/4038-mls-key-backup.md @@ -1,4 +1,4 @@ -# MSCxxxx: MLS with key backup +# MSC4038: Key backup for MLS [MSC2883](https://github.com/matrix-org/matrix-spec-proposals/pull/2883) defines how to use [Messaging Layer Security @@ -103,7 +103,7 @@ privacy or convenience. ## Unstable prefix Until this MSC is accepted, clients should use -`org.matrix.mscxxxx.v0.aes-hmac-sha2` as the backup version. Note that the +`org.matrix.msc4038.v0.aes-hmac-sha2` as the backup version. Note that the session data contains an `algorithm` property giving the encryption algorithm for the key. Until MSC2883 is accepted, the unstable identifier from that MSC should be used as the algorithm name, rather than the stable identifier.