From 0e4ec859a98eeffce8f9fcc89a3583f83bb4e76b Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Wed, 27 Nov 2024 16:42:01 -0700 Subject: [PATCH] off by one --- ...ss-control.md => 4232-attribute-based-access-control.md} | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) rename proposals/{4231-attribute-based-access-control.md => 4232-attribute-based-access-control.md} (98%) diff --git a/proposals/4231-attribute-based-access-control.md b/proposals/4232-attribute-based-access-control.md similarity index 98% rename from proposals/4231-attribute-based-access-control.md rename to proposals/4232-attribute-based-access-control.md index de26635d3..62984d0e0 100644 --- a/proposals/4231-attribute-based-access-control.md +++ b/proposals/4232-attribute-based-access-control.md @@ -1,4 +1,4 @@ -# MSC4231: Attribute-Based Access Control (ABAC) +# MSC4232: Attribute-Based Access Control (ABAC) Within Matrix rooms it is important to be able to grant specific actions to users with more trust or capability to embody a role, such as giving a concept of "moderators" the kick and ban permissions. In @@ -166,9 +166,9 @@ TBD ## Unstable prefix While this MSC is not included in a stable room version, it MUST only be implemented in an unstable -room version using the following format: `org.matrix.msc4231.`. For example, if an +room version using the following format: `org.matrix.msc4232.`. For example, if an implementation implements this proposal using room version `11` as a base, the unstable room version -would be `org.matrix.msc4231.11`. +would be `org.matrix.msc4232.11`. For valid consideration under the MSC process, an implementation must base itself off the latest stable room version available at time of FCP.