Because all clients within a group (members) have access to the shared -cryptographic material, the MLS protocol allows each member of the messaging group -to perform operations. However, every service/infrastructure has control over +cryptographic material, MLS protocol allows each member of the messaging group +to perform operations, However, every service/infrastructure has control over policies applied to its own clients. Applications managing MLS clients can be configured to allow for specific group operations. On the one hand, an application could decide that a group administrator will be the only member to @@ -2313,10 +2313,8 @@
RECOMMENDATION: Prefer using encrypted group operation messages unless a -Delivery Service explicitly needs plaintext handshake messages to provide -additional features. In this case, ensure that transport-layer encryption is -always used.¶
+RECOMMENDATION: Prefer using encrypted group operation messages to avoid +privacy issues related to non-encrypted signatures.¶
If handshake messages are encrypted, any access diff --git a/draft-ietf-mls-architecture.txt b/draft-ietf-mls-architecture.txt index 4232d33..2d2430c 100644 --- a/draft-ietf-mls-architecture.txt +++ b/draft-ietf-mls-architecture.txt @@ -5,14 +5,14 @@ Network Working Group B. Beurdouche Internet-Draft Inria & Mozilla Intended status: Informational E. Rescorla -Expires: 7 September 2024 Mozilla +Expires: 8 September 2024 Mozilla E. Omara S. Inguva A. Duric Wire - 6 March 2024 + 7 March 2024 The Messaging Layer Security (MLS) Architecture @@ -68,7 +68,7 @@ Status of This Memo time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on 7 September 2024. + This Internet-Draft will expire on 8 September 2024. Copyright Notice @@ -850,8 +850,8 @@ Welcome (Charlie) -----------------------------------------> | Step 4 6.4. Access Control Because all clients within a group (members) have access to the - shared cryptographic material, the MLS protocol allows each member of - the messaging group to perform operations. However, every service/ + shared cryptographic material, MLS protocol allows each member of the + messaging group to perform operations, However, every service/ infrastructure has control over policies applied to its own clients. Applications managing MLS clients can be configured to allow for specific group operations. On the one hand, an application could @@ -869,9 +869,7 @@ Welcome (Charlie) -----------------------------------------> | Step 4 for tracking. *RECOMMENDATION:* Prefer using encrypted group operation messages - unless a Delivery Service explicitly needs plaintext handshake - messages to provide additional features. In this case, ensure - that transport-layer encryption is always used. + to avoid privacy issues related to non-encrypted signatures. If handshake messages are encrypted, any access control policies must be applied at the client, so the application must ensure that the diff --git a/index.html b/index.html index f34c627..d918ecf 100644 --- a/index.html +++ b/index.html @@ -30,7 +30,7 @@