Script updating gh-pages from 2981819. [ci skip]

thomas-fossati · Feb 23, 2024 · 0905480 · 0905480
1 parent 2b8a792
commit 0905480
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/hannestschofenig-patch-1/draft-ietf-uta-tls13-iot-profile.html b/hannestschofenig-patch-1/draft-ietf-uta-tls13-iot-profile.html
@@ -1334,7 +1334,7 @@ <h2 id="name-introduction">
 <li class="compact" id="section-1-4.1">
           <p id="section-1-4.1.1">TLS 1.3 introduced the concept of post-handshake authentication messages, which
 partially replaced the need for the re-negotiation feature <span>[<a href="#RFC5746" class="cite xref">RFC5746</a>]</span> available
-in earlier TLS versions. However, rekeying defined in Section 4.6.3 of TLS 1.3
+in earlier TLS versions. However, rekeying defined in <span><a href="https://rfc-editor.org/rfc/rfc8446#section-4.6.3" class="relref">Section 4.6.3</a> of [<a href="#TLS13" class="cite xref">TLS13</a>]</span>
 does not provide forward secrecy and post-handshake authentication defined in
 Section 4.6.2 of TLS 1.3 only offers client-to-server authentication.
 <span>[<a href="#RFC9261" class="cite xref">RFC9261</a>]</span> later added support for mutual, post-handshake authentication but

diff --git a/hannestschofenig-patch-1/draft-ietf-uta-tls13-iot-profile.txt b/hannestschofenig-patch-1/draft-ietf-uta-tls13-iot-profile.txt
@@ -137,7 +137,7 @@ Table of Contents
    *  TLS 1.3 introduced the concept of post-handshake authentication
       messages, which partially replaced the need for the re-negotiation
       feature [RFC5746] available in earlier TLS versions.  However,
-      rekeying defined in Section 4.6.3 of TLS 1.3 does not provide
+      rekeying defined in Section 4.6.3 of [TLS13] does not provide
       forward secrecy and post-handshake authentication defined in
       Section 4.6.2 of TLS 1.3 only offers client-to-server
       authentication.  [RFC9261] later added support for mutual, post-