Script updating gh-pages from 5de8682. [ci skip]

Author: ID Bot

overview-diagrams/draft-davidben-tls-merkle-tree-certs.html

@@ -1051,7 +1051,7 @@
 </tr></thead>
 <tfoot><tr>
 <td class="left">Benjamin, et al.</td>
-<td class="center">Expires 22 February 2026</td>
+<td class="center">Expires 23 February 2026</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1064,12 +1064,12 @@
 <dd class="internet-draft">draft-davidben-tls-merkle-tree-certs-latest</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2025-08-21" class="published">21 August 2025</time>
+<time datetime="2025-08-22" class="published">22 August 2025</time>
     </dd>
 <dt class="label-intended-status">Intended Status:</dt>
 <dd class="intended-status">Experimental</dd>
 <dt class="label-expires">Expires:</dt>
-<dd class="expires"><time datetime="2026-02-22">22 February 2026</time></dd>
+<dd class="expires"><time datetime="2026-02-23">23 February 2026</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1129,7 +1129,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 22 February 2026.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 23 February 2026.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -1557,7 +1557,7 @@ <h3 id="name-terminology-and-roles">
       <h2 id="name-overview">
 <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-overview" class="section-name selfRef">Overview</a>
       </h2>
-<p id="section-3-1">In Certificate Transparency, a CA first certifies information by signing it, then submits the resulting certificate to logs for logging. Merkle Tree Certificates inverts this process: the CA certifies information by logging it, then submits the log to cosigners to verify log operation. A certificate is assembled from the result and proves the information is in the CA's log.<a href="#section-3-1" class="pilcrow">¶</a></p>
+<p id="section-3-1">In Certificate Transparency, a CA first certifies information by signing it, then submits the resulting certificate (or precertificate) to logs for logging. Merkle Tree Certificates inverts this process: the CA certifies information by logging it, then submits the log to cosigners to verify log operation. A certificate is assembled from the result and proves the information is in the CA's log.<a href="#section-3-1" class="pilcrow">¶</a></p>
 <span id="name-a-diagram-of-the-issuance-a"></span><div id="fig-issuance-overview">
 <figure id="figure-1">
         <div id="section-3-2.1">

overview-diagrams/draft-davidben-tls-merkle-tree-certs.txt

@@ -5,13 +5,13 @@
 Network Working Group                                        D. Benjamin
 Internet-Draft                                                Google LLC
 Intended status: Experimental                                 D. O'Brien
-Expires: 22 February 2026                                               
+Expires: 23 February 2026                                               
                                                         B. E. Westerbaan
                                                               L. Valenta
                                                               Cloudflare
                                                              F. Valsorda
                                                                   Geomys
-                                                          21 August 2025
+                                                          22 August 2025
 
 
                         Merkle Tree Certificates
@@ -58,7 +58,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 22 February 2026.
+   This Internet-Draft will expire on 23 February 2026.
 
 Copyright Notice
 
@@ -304,11 +304,12 @@ Table of Contents
 3.  Overview
 
    In Certificate Transparency, a CA first certifies information by
-   signing it, then submits the resulting certificate to logs for
-   logging.  Merkle Tree Certificates inverts this process: the CA
-   certifies information by logging it, then submits the log to
-   cosigners to verify log operation.  A certificate is assembled from
-   the result and proves the information is in the CA's log.
+   signing it, then submits the resulting certificate (or
+   precertificate) to logs for logging.  Merkle Tree Certificates
+   inverts this process: the CA certifies information by logging it,
+   then submits the log to cosigners to verify log operation.  A
+   certificate is assembled from the result and proves the information
+   is in the CA's log.
 
    +-- Certificate Authority -----+    +--  Authenticating Party ----+
    |                              |    |                             |