From fdbcf92516ce1df82b096c22fc96c33e154fae05 Mon Sep 17 00:00:00 2001
From: ID Bot <idbot@example.com>
Date: Thu, 7 Mar 2024 00:17:11 +0000
Subject: [PATCH] Script updating gh-pages from c93e4a6. [ci skip]

---
 draft-ietf-mls-architecture.html | 18 ++++++++----------
 draft-ietf-mls-architecture.txt  | 14 ++++++--------
 index.html                       |  2 +-
 3 files changed, 15 insertions(+), 19 deletions(-)

diff --git a/draft-ietf-mls-architecture.html b/draft-ietf-mls-architecture.html
index f5ca086..432f75f 100644
--- a/draft-ietf-mls-architecture.html
+++ b/draft-ietf-mls-architecture.html
@@ -1050,7 +1050,7 @@
 </tr></thead>
 <tfoot><tr>
 <td class="left">Beurdouche, et al.</td>
-<td class="center">Expires 7 September 2024</td>
+<td class="center">Expires 8 September 2024</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1063,12 +1063,12 @@
 <dd class="internet-draft">draft-ietf-mls-architecture-latest</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2024-03-06" class="published">6 March 2024</time>
+<time datetime="2024-03-07" class="published">7 March 2024</time>
     </dd>
 <dt class="label-intended-status">Intended Status:</dt>
 <dd class="intended-status">Informational</dd>
 <dt class="label-expires">Expires:</dt>
-<dd class="expires"><time datetime="2024-09-07">7 September 2024</time></dd>
+<dd class="expires"><time datetime="2024-09-08">8 September 2024</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1144,7 +1144,7 @@ <h2 id="name-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."<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
 <p id="section-boilerplate.1-4">
-        This Internet-Draft will expire on 7 September 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 8 September 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -2298,8 +2298,8 @@ <h3 id="name-access-control">
 <a href="#section-6.4" class="section-number selfRef">6.4. </a><a href="#name-access-control" class="section-name selfRef">Access Control</a>
         </h3>
 <p id="section-6.4-1">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 @@ <h3 id="name-access-control">
 collect the signatures on the handshake messages and use them for tracking.<a href="#section-6.4-3" class="pilcrow">¶</a></p>
 <ul class="normal ulEmpty">
 <li class="normal ulEmpty" id="section-6.4-4.1">
-            <p id="section-6.4-4.1.1"><strong>RECOMMENDATION:</strong> 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.<a href="#section-6.4-4.1.1" class="pilcrow">¶</a></p>
+            <p id="section-6.4-4.1.1"><strong>RECOMMENDATION:</strong> Prefer using encrypted group operation messages to avoid
+privacy issues related to non-encrypted signatures.<a href="#section-6.4-4.1.1" class="pilcrow">¶</a></p>
 </li>
         </ul>
 <p id="section-6.4-5">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 @@ <h2>Preview for branch <a href="revert-247-brendan/enc-rec">revert-247-brendan/e
       <tr>
         <td><a href="revert-247-brendan/enc-rec/draft-ietf-mls-architecture.html" class="html draft-ietf-mls-architecture" title="The Messaging Layer Security (MLS) Architecture (HTML)">MLS Architecture</a></td>
         <td><a href="revert-247-brendan/enc-rec/draft-ietf-mls-architecture.txt" class="txt draft-ietf-mls-architecture" title="The Messaging Layer Security (MLS) Architecture (Text)">plain text</a></td>
-        <td><a href="https://author-tools.ietf.org/api/iddiff?url_1=https://mlswg.github.io/mls-architecture/draft-ietf-mls-architecture.txt&amp;url_2=https://mlswg.github.io/mls-architecture/revert-247-brendan/enc-rec/draft-ietf-mls-architecture.txt" class="diff draft-ietf-mls-architecture">diff with main</a></td>
+        <td>same as main</td>
       </tr>
     </table>
     <script>