From 8feff907289e1d658c7b42c1c8f60e704d363934 Mon Sep 17 00:00:00 2001
From: ID Bot <idbot@example.com>
Date: Tue, 17 Dec 2024 16:49:00 +0000
Subject: [PATCH] Script updating gh-pages from e05202b. [ci skip]

---
 draft-ietf-uta-tls13-iot-profile.html | 24 +++++++++----------
 draft-ietf-uta-tls13-iot-profile.txt  | 34 +++++++++++++--------------
 index.html                            |  2 +-
 3 files changed, 30 insertions(+), 30 deletions(-)

diff --git a/draft-ietf-uta-tls13-iot-profile.html b/draft-ietf-uta-tls13-iot-profile.html
index 71a7b14..3312bdd 100644
--- a/draft-ietf-uta-tls13-iot-profile.html
+++ b/draft-ietf-uta-tls13-iot-profile.html
@@ -1052,7 +1052,7 @@
 </tr></thead>
 <tfoot><tr>
 <td class="left">Tschofenig, et al.</td>
-<td class="center">Expires 19 June 2025</td>
+<td class="center">Expires 20 June 2025</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1068,12 +1068,12 @@
 <a href="https://www.rfc-editor.org/rfc/rfc7925" class="eref">7925</a> (if approved)</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2024-12-16" class="published">16 December 2024</time>
+<time datetime="2024-12-17" class="published">17 December 2024</time>
     </dd>
 <dt class="label-intended-status">Intended Status:</dt>
 <dd class="intended-status">Standards Track</dd>
 <dt class="label-expires">Expires:</dt>
-<dd class="expires"><time datetime="2025-06-19">19 June 2025</time></dd>
+<dd class="expires"><time datetime="2025-06-20">20 June 2025</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1125,7 +1125,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 19 June 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 20 June 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -2165,13 +2165,13 @@ <h2 id="name-ciphersuites">
 eliminate the security and availability threats related to CCM_8 while retaining
 interoperability with the larger ecosystem.<a href="#section-18-4" class="pilcrow">¶</a></p>
 <p id="section-18-5">In order to ameliorate the situation, this document RECOMMENDS that
-implementations support the following two ciphersuites:<a href="#section-18-5" class="pilcrow">¶</a></p>
+implementations support the following two ciphersuites for TLS 1.3:<a href="#section-18-5" class="pilcrow">¶</a></p>
 <ul class="compact">
 <li class="compact" id="section-18-6.1">
-          <p id="section-18-6.1.1"><code>TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256</code><a href="#section-18-6.1.1" class="pilcrow">¶</a></p>
+          <p id="section-18-6.1.1"><code>TLS_AES_128_GCM_SHA256</code><a href="#section-18-6.1.1" class="pilcrow">¶</a></p>
 </li>
         <li class="compact" id="section-18-6.2">
-          <p id="section-18-6.2.1"><code>TLS_ECDHE_ECDSA_WITH_AES_128_CCM</code><a href="#section-18-6.2.1" class="pilcrow">¶</a></p>
+          <p id="section-18-6.2.1"><code>TLS_AES_128_CCM</code><a href="#section-18-6.2.1" class="pilcrow">¶</a></p>
 </li>
       </ul>
 <p id="section-18-7">and offer them as their first choice.  These ciphersuites provide
@@ -2184,16 +2184,16 @@ <h2 id="name-ciphersuites">
 <span><a href="https://rfc-editor.org/rfc/rfc9325#section-7.2.1" class="relref">Section 7.2.1</a> of [<a href="#RFC9325" class="cite xref">RFC9325</a>]</span> related to deterministic nonce generation
 apply.  In addition, the integrity limits on key usage detailed in <span><a href="https://rfc-editor.org/rfc/rfc9325#section-4.4" class="relref">Section 4.4</a> of [<a href="#RFC9325" class="cite xref">RFC9325</a>]</span> also apply.<a href="#section-18-8" class="pilcrow">¶</a></p>
 <p id="section-18-9"><a href="#tab-cipher-reqs" class="auto internal xref">Table 1</a> summarizes the recommendations regarding ciphersuites:<a href="#section-18-9" class="pilcrow">¶</a></p>
-<span id="name-ciphersuite-requirements"></span><div id="tab-cipher-reqs">
+<span id="name-tls-13-ciphersuite-requirem"></span><div id="tab-cipher-reqs">
 <table class="left" id="table-1">
         <caption>
 <a href="#table-1" class="selfRef">Table 1</a>:
-<a href="#name-ciphersuite-requirements" class="selfRef">Ciphersuite requirements</a>
+<a href="#name-tls-13-ciphersuite-requirem" class="selfRef">TLS 1.3 Ciphersuite Requirements</a>
         </caption>
 <thead>
           <tr>
             <th class="text-left" rowspan="1" colspan="1">Ciphersuite</th>
-            <th class="text-left" rowspan="1" colspan="1">Requirement</th>
+            <th class="text-left" rowspan="1" colspan="1">MTI Requirement</th>
           </tr>
         </thead>
         <tbody>
@@ -2205,13 +2205,13 @@ <h2 id="name-ciphersuites">
           </tr>
           <tr>
             <td class="text-left" rowspan="1" colspan="1">
-              <code>TLS_ECDHE_ECDSA_WITH_AES_128_CCM</code>
+              <code>TLS_AES_128_CCM</code>
 </td>
             <td class="text-left" rowspan="1" colspan="1">SHOULD+</td>
           </tr>
           <tr>
             <td class="text-left" rowspan="1" colspan="1">
-              <code>TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256</code>
+              <code>TLS_AES_128_GCM_SHA256</code>
 </td>
             <td class="text-left" rowspan="1" colspan="1">SHOULD+</td>
           </tr>
diff --git a/draft-ietf-uta-tls13-iot-profile.txt b/draft-ietf-uta-tls13-iot-profile.txt
index b4f1bc9..6f9b981 100644
--- a/draft-ietf-uta-tls13-iot-profile.txt
+++ b/draft-ietf-uta-tls13-iot-profile.txt
@@ -6,9 +6,9 @@ UTA                                                        H. Tschofenig
 Internet-Draft                                                     H-BRS
 Updates: 7925 (if approved)                                   T. Fossati
 Intended status: Standards Track                                  Linaro
-Expires: 19 June 2025                                      M. Richardson
+Expires: 20 June 2025                                      M. Richardson
                                                 Sandelman Software Works
-                                                        16 December 2024
+                                                        17 December 2024
 
 
             TLS/DTLS 1.3 Profiles for the Internet of Things
@@ -43,7 +43,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 19 June 2025.
+   This Internet-Draft will expire on 20 June 2025.
 
 Copyright Notice
 
@@ -893,10 +893,10 @@ Table of Contents
    to CCM_8 while retaining interoperability with the larger ecosystem.
 
    In order to ameliorate the situation, this document RECOMMENDS that
-   implementations support the following two ciphersuites:
+   implementations support the following two ciphersuites for TLS 1.3:
 
-   *  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
-   *  TLS_ECDHE_ECDSA_WITH_AES_128_CCM
+   *  TLS_AES_128_GCM_SHA256
+   *  TLS_AES_128_CCM
 
    and offer them as their first choice.  These ciphersuites provide
    confidentiality and integrity limits that are considered acceptable
@@ -913,17 +913,17 @@ Table of Contents
 
    Table 1 summarizes the recommendations regarding ciphersuites:
 
-   +=========================================+=============+
-   | Ciphersuite                             | Requirement |
-   +=========================================+=============+
-   | TLS_AES_128_CCM_8_SHA256                | MUST-       |
-   +-----------------------------------------+-------------+
-   | TLS_ECDHE_ECDSA_WITH_AES_128_CCM        | SHOULD+     |
-   +-----------------------------------------+-------------+
-   | TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | SHOULD+     |
-   +-----------------------------------------+-------------+
-
-               Table 1: Ciphersuite requirements
+   +==========================+=================+
+   | Ciphersuite              | MTI Requirement |
+   +==========================+=================+
+   | TLS_AES_128_CCM_8_SHA256 | MUST-           |
+   +--------------------------+-----------------+
+   | TLS_AES_128_CCM          | SHOULD+         |
+   +--------------------------+-----------------+
+   | TLS_AES_128_GCM_SHA256   | SHOULD+         |
+   +--------------------------+-----------------+
+
+     Table 1: TLS 1.3 Ciphersuite Requirements
 
 19.  Fault Attacks on Deterministic Signature Schemes
 
diff --git a/index.html b/index.html
index 8d9d975..3e72f56 100644
--- a/index.html
+++ b/index.html
@@ -37,7 +37,7 @@ <h2>Preview for branch <a href="consistency">consistency</a></h2>
       <tr>
         <td><a href="consistency/draft-ietf-uta-tls13-iot-profile.html" class="html draft-ietf-uta-tls13-iot-profile" title="TLS/DTLS 1.3 Profiles for the Internet of Things (HTML)">TLS/DTLS 1.3 IoT Profiles</a></td>
         <td><a href="consistency/draft-ietf-uta-tls13-iot-profile.txt" class="txt draft-ietf-uta-tls13-iot-profile" title="TLS/DTLS 1.3 Profiles for the Internet of Things (Text)">plain text</a></td>
-        <td>same as master</td>
+        <td><a href="https://author-tools.ietf.org/api/iddiff?url_1=https://thomas-fossati.github.io/draft-tls13-iot/draft-ietf-uta-tls13-iot-profile.txt&amp;url_2=https://thomas-fossati.github.io/draft-tls13-iot/consistency/draft-ietf-uta-tls13-iot-profile.txt" class="diff draft-ietf-uta-tls13-iot-profile">diff with master</a></td>
       </tr>
     </table>
     <script>