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

ech-in-enterprise/draft-ietf-uta-tls13-iot-profile.html

@@ -1054,7 +1054,7 @@
 </tr></thead>
 <tfoot><tr>
 <td class="left">Tschofenig &amp; Fossati</td>
-<td class="center">Expires 13 March 2024</td>
+<td class="center">Expires 17 March 2024</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1070,12 +1070,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="2023-09-10" class="published">10 September 2023</time>
+<time datetime="2023-09-14" class="published">14 September 2023</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="2024-03-13">13 March 2024</time></dd>
+<dd class="expires"><time datetime="2024-03-17">17 March 2024</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1122,7 +1122,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 13 March 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 17 March 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -1448,7 +1448,7 @@ <h2 id="name-server-name-indication">
 Encryption (HPKE) <span>[<a href="#I-D.irtf-cfrg-hpke" class="cite xref">I-D.irtf-cfrg-hpke</a>]</span> and additional protocols require
 further protocol exchanges and cryptographic operations, there is a certain
 overhead associated with this privacy feature.<a href="#section-10-2" class="pilcrow">¶</a></p>
-<p id="section-10-3">Note that in environments where protection against malware is essential (e.g., enterprise networks, industrial IoT deployments), using ECH may not be an option because network administrators want to be able to filter the DNS traffic generated by IoT devices in order to prevent access to potentially malicious content.<a href="#section-10-3" class="pilcrow">¶</a></p>
+<p id="section-10-3">Note that in industrial IoT deployments the use of ECH may not be an option because network administrators inspect DNS traffic generated by IoT devices in order to detect malicious behaviour<a href="#section-10-3" class="pilcrow">¶</a></p>
 <p id="section-10-4">Besides, to avoid leaking DNS lookups from network inspection altogether further
 protocols are needed, including DoH <span>[<a href="#RFC8484" class="cite xref">RFC8484</a>]</span> and DPRIVE <span>[<a href="#RFC7858" class="cite xref">RFC7858</a>]</span> <span>[<a href="#RFC8094" class="cite xref">RFC8094</a>]</span>.
 For use of such techniques in managed networks, the reader is advised to keep up to date with the protocols defined by the Adaptive DNS Discovery (add) working group.<a href="#section-10-4" class="pilcrow">¶</a></p>

ech-in-enterprise/draft-ietf-uta-tls13-iot-profile.txt

@@ -6,7 +6,7 @@ UTA                                                        H. Tschofenig
 Internet-Draft                                                          
 Updates: 7925 (if approved)                                   T. Fossati
 Intended status: Standards Track                                  Linaro
-Expires: 13 March 2024                                 10 September 2023
+Expires: 17 March 2024                                 14 September 2023
 
 
             TLS/DTLS 1.3 Profiles for the Internet of Things
@@ -40,7 +40,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 13 March 2024.
+   This Internet-Draft will expire on 17 March 2024.
 
 Copyright Notice
 
@@ -238,11 +238,9 @@ Table of Contents
    operations, there is a certain overhead associated with this privacy
    feature.
 
-   Note that in environments where protection against malware is
-   essential (e.g., enterprise networks, industrial IoT deployments),
-   using ECH may not be an option because network administrators want to
-   be able to filter the DNS traffic generated by IoT devices in order
-   to prevent access to potentially malicious content.
+   Note that in industrial IoT deployments the use of ECH may not be an
+   option because network administrators inspect DNS traffic generated
+   by IoT devices in order to detect malicious behaviour
 
    Besides, to avoid leaking DNS lookups from network inspection
    altogether further protocols are needed, including DoH [RFC8484] and