Script updating gh-pages from 46ed1fd. [ci skip]

Author: ID Bot

draft-ietf-tls-keylogfile.html

@@ -21,15 +21,15 @@
 <meta content="draft-ietf-tls-keylogfile-latest" name="ietf.draft">
 <!-- Generator version information:
   xml2rfc 3.25.0
-    Python 3.12.7
+    Python 3.12.8
     ConfigArgParse 1.7
     google-i18n-address 3.1.1
     intervaltree 3.1.0
-    Jinja2 3.1.4
+    Jinja2 3.1.5
     lxml 5.3.0
     platformdirs 4.3.6
-    pycountry 22.3.5
-    PyYAML 6.0.1
+    pycountry 24.6.1
+    PyYAML 6.0.2
     requests 2.32.3
     setuptools 70.3.0
     wcwidth 0.2.13
@@ -1051,11 +1051,11 @@
 <thead><tr>
 <td class="left">Internet-Draft</td>
 <td class="center">SSLKEYLOGFILE</td>
-<td class="right">December 2024</td>
+<td class="right">January 2025</td>
 </tr></thead>
 <tfoot><tr>
 <td class="left">Thomson, et al.</td>
-<td class="center">Expires 14 June 2025</td>
+<td class="center">Expires 1 August 2025</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1068,12 +1068,12 @@
 <dd class="internet-draft">draft-ietf-tls-keylogfile-latest</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2024-12-11" class="published">11 December 2024</time>
+<time datetime="2025-01-28" class="published">28 January 2025</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="2025-06-14">14 June 2025</time></dd>
+<dd class="expires"><time datetime="2025-08-01">1 August 2025</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1134,7 +1134,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 14 June 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 1 August 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -1143,7 +1143,7 @@ <h2 id="name-copyright-notice">
 <a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
         </h2>
 <p id="section-boilerplate.2-1">
-            Copyright (c) 2024 IETF Trust and the persons identified as the
+            Copyright (c) 2025 IETF Trust and the persons identified as the
             document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
 <p id="section-boilerplate.2-2">
             This document is subject to BCP 78 and the IETF Trust's Legal
@@ -1242,8 +1242,8 @@ <h2 id="name-introduction">
 adoption of TLS as the name of the protocol.<a href="#section-1-2" class="pilcrow">¶</a></p>
 <p id="section-1-3">This document describes the SSLKEYLOGFILE format.  This format can be used for
 TLS 1.2 <span>[<a href="#TLS12" class="cite xref">TLS12</a>]</span> and TLS 1.3 <span>[<a href="#TLS13" class="cite xref">TLS13</a>]</span>.  The format also
-supports earlier TLS versions, though use of earlier versions is forbidden
-<span>[<a href="#RFC8996" class="cite xref">RFC8996</a>]</span>.  This format can also be used with DTLS <span>[<a href="#DTLS13" class="cite xref">DTLS13</a>]</span>, QUIC
+supports earlier TLS versions, though use of earlier versions is strongly discouraged
+<span>[<a href="#RFC8996" class="cite xref">RFC8996</a>]</span><span>[<a href="#RFC9325" class="cite xref">RFC9325</a>]</span>.  This format can also be used with DTLS <span>[<a href="#DTLS13" class="cite xref">DTLS13</a>]</span>, QUIC
 <span>[<a href="#RFC9000" class="cite xref">RFC9000</a>]</span><span>[<a href="#RFC9001" class="cite xref">RFC9001</a>]</span>, and other protocols that also use the TLS key
 schedule.  Use of this format could complement other protocol-specific logging
 such as QLOG <span>[<a href="#QLOG" class="cite xref">QLOG</a>]</span>.<a href="#section-1-3" class="pilcrow">¶</a></p>
@@ -1779,9 +1779,13 @@ <h3 id="name-informative-references">
 <span class="refAuthor">Barnes, R.</span>, <span class="refAuthor">Bhargavan, K.</span>, <span class="refAuthor">Lipp, B.</span>, and <span class="refAuthor">C. Wood</span>, <span class="refTitle">"Hybrid Public Key Encryption"</span>, <span class="seriesInfo">RFC 9180</span>, <span class="seriesInfo">DOI 10.17487/RFC9180</span>, <time datetime="2022-02" class="refDate">February 2022</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc9180">https://www.rfc-editor.org/rfc/rfc9180</a>&gt;</span>. </dd>
 <dd class="break"></dd>
 <dt id="RFC9261">[RFC9261]</dt>
-      <dd>
+        <dd>
 <span class="refAuthor">Sullivan, N.</span>, <span class="refTitle">"Exported Authenticators in TLS"</span>, <span class="seriesInfo">RFC 9261</span>, <span class="seriesInfo">DOI 10.17487/RFC9261</span>, <time datetime="2022-07" class="refDate">July 2022</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc9261">https://www.rfc-editor.org/rfc/rfc9261</a>&gt;</span>. </dd>
 <dd class="break"></dd>
+<dt id="RFC9325">[RFC9325]</dt>
+      <dd>
+<span class="refAuthor">Sheffer, Y.</span>, <span class="refAuthor">Saint-Andre, P.</span>, and <span class="refAuthor">T. Fossati</span>, <span class="refTitle">"Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)"</span>, <span class="seriesInfo">BCP 195</span>, <span class="seriesInfo">RFC 9325</span>, <span class="seriesInfo">DOI 10.17487/RFC9325</span>, <time datetime="2022-11" class="refDate">November 2022</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc9325">https://www.rfc-editor.org/rfc/rfc9325</a>&gt;</span>. </dd>
+<dd class="break"></dd>
 </dl>
 </section>
 </div>

draft-ietf-tls-keylogfile.txt

@@ -5,10 +5,10 @@
 Transport Layer Security                                      M. Thomson
 Internet-Draft                                                   Mozilla
 Intended status: Informational                              Y. Rosomakho
-Expires: 14 June 2025                                            Zscaler
+Expires: 1 August 2025                                           Zscaler
                                                            H. Tschofenig
                                                                    H-BRS
-                                                        11 December 2024
+                                                         28 January 2025
 
 
                     The SSLKEYLOGFILE Format for TLS
@@ -53,11 +53,11 @@ 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 14 June 2025.
+   This Internet-Draft will expire on 1 August 2025.
 
 Copyright Notice
 
-   Copyright (c) 2024 IETF Trust and the persons identified as the
+   Copyright (c) 2025 IETF Trust and the persons identified as the
    document authors.  All rights reserved.
 
    This document is subject to BCP 78 and the IETF Trust's Legal
@@ -107,10 +107,10 @@ Table of Contents
    This document describes the SSLKEYLOGFILE format.  This format can be
    used for TLS 1.2 [TLS12] and TLS 1.3 [TLS13].  The format also
    supports earlier TLS versions, though use of earlier versions is
-   forbidden [RFC8996].  This format can also be used with DTLS
-   [DTLS13], QUIC [RFC9000][RFC9001], and other protocols that also use
-   the TLS key schedule.  Use of this format could complement other
-   protocol-specific logging such as QLOG [QLOG].
+   strongly discouraged [RFC8996][RFC9325].  This format can also be
+   used with DTLS [DTLS13], QUIC [RFC9000][RFC9001], and other protocols
+   that also use the TLS key schedule.  Use of this format could
+   complement other protocol-specific logging such as QLOG [QLOG].
 
    This document also defines labels that can be used to log information
    about exchanges that use Encrypted Client Hello (ECH) [ECH].
@@ -522,6 +522,12 @@ Table of Contents
               DOI 10.17487/RFC9261, July 2022,
               <https://www.rfc-editor.org/rfc/rfc9261>.
 
+   [RFC9325]  Sheffer, Y., Saint-Andre, P., and T. Fossati,
+              "Recommendations for Secure Use of Transport Layer
+              Security (TLS) and Datagram Transport Layer Security
+              (DTLS)", BCP 195, RFC 9325, DOI 10.17487/RFC9325, November
+              2022, <https://www.rfc-editor.org/rfc/rfc9325>.
+
 Appendix A.  Example
 
    The following is a sample of a file in this format, including secrets