From 609641636dcd9fa3008f3a815af10886410443c9 Mon Sep 17 00:00:00 2001 From: Hubert Chathi Date: Tue, 13 Apr 2021 12:29:58 -0400 Subject: [PATCH] decouple from MSC1849/MSC2674 --- proposals/2241-e2e-verification-in-dms.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/proposals/2241-e2e-verification-in-dms.md b/proposals/2241-e2e-verification-in-dms.md index 46f303c2..dc2797f2 100644 --- a/proposals/2241-e2e-verification-in-dms.md +++ b/proposals/2241-e2e-verification-in-dms.md @@ -89,9 +89,6 @@ verification itself. To accept a key verification, Bob will send an `m.key.verification.ready` event with the following properties in its contents: -TODO: MSC1849 may use `m.relationship` rather than `m.relates_to`, in which -case this proposal should follow suit. - - `m.relates_to`: an object with the properties: - `rel_type`: `m.reference` - `event_id`: the event ID of the key verification request that is being @@ -100,6 +97,10 @@ case this proposal should follow suit. - `from_device`: Bob's device ID. This is required since some verification methods may use the device IDs as part of the verification process. +(Note: the form of the `m.relates_to` property is based on the current state of +[MSC2674](https://github.com/matrix-org/matrix-doc/pull/2674), but is +independent from it since this MSC does not rely on any aggregations features.) + Clients should ignore `m.key.verification.ready` events that correspond to verification requests that they did not send.