From 30b0e7f51476081e183e805eea030d80b0294a42 Mon Sep 17 00:00:00 2001
From: ID Bot <idbot@example.com>
Date: Thu, 20 Jun 2024 14:17:55 +0000
Subject: [PATCH] Script updating gh-pages from 9319c93. [ci skip]

---
 dnr-dtls-cleanup/draft-lenders-core-dnr.html | 24 ++++++++++----------
 dnr-dtls-cleanup/draft-lenders-core-dnr.txt  | 12 +++++-----
 2 files changed, 18 insertions(+), 18 deletions(-)

diff --git a/dnr-dtls-cleanup/draft-lenders-core-dnr.html b/dnr-dtls-cleanup/draft-lenders-core-dnr.html
index 87f4314..fed6fba 100644
--- a/dnr-dtls-cleanup/draft-lenders-core-dnr.html
+++ b/dnr-dtls-cleanup/draft-lenders-core-dnr.html
@@ -24,17 +24,17 @@
 <meta content="draft-lenders-core-dnr-latest" name="ietf.draft">
 <!-- Generator version information:
   xml2rfc 3.21.0
-    Python 3.11.9
+    Python 3.12.3
     ConfigArgParse 1.7
     google-i18n-address 3.1.0
     intervaltree 3.1.0
-    Jinja2 3.1.2
-    lxml 4.9.3
-    platformdirs 4.2.1
+    Jinja2 3.1.4
+    lxml 4.9.4
+    platformdirs 4.2.2
     pycountry 22.3.5
     PyYAML 6.0.1
     requests 2.31.0
-    setuptools 68.2.2
+    setuptools 69.5.1
     six 1.16.0
     wcwidth 0.2.13
 -->
@@ -1035,11 +1035,11 @@
 <thead><tr>
 <td class="left">Internet-Draft</td>
 <td class="center">CoRE DNR</td>
-<td class="right">May 2024</td>
+<td class="right">June 2024</td>
 </tr></thead>
 <tfoot><tr>
 <td class="left">Lenders, et al.</td>
-<td class="center">Expires 7 November 2024</td>
+<td class="center">Expires 22 December 2024</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1052,12 +1052,12 @@
 <dd class="internet-draft">draft-lenders-core-dnr-latest</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2024-05-06" class="published">6 May 2024</time>
+<time datetime="2024-06-20" class="published">20 June 2024</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="2024-11-07">7 November 2024</time></dd>
+<dd class="expires"><time datetime="2024-12-22">22 December 2024</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1121,7 +1121,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 7 November 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 22 December 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -1220,8 +1220,8 @@ <h2 id="name-introduction">
 The Constrained Application Protocol (CoAP) <span>[<a href="#RFC7252" class="cite xref">RFC7252</a>]</span>, the transfer protocol for DoC, is mostly
 agnostic to the transport layer, i.e., CoAP can be transported over UDP, TCP, or WebSockets
 <span>[<a href="#RFC8323" class="cite xref">RFC8323</a>]</span>, and even less common transports such as Bluetooth GATT <span>[<a href="#I-D.amsuess-core-coap-over-gatt" class="cite xref">I-D.amsuess-core-coap-over-gatt</a>]</span> or SMS
-<span>[<a href="#lwm2m" class="cite xref">lwm2m</a>]</span> are discussed. <span>[<a href="#I-D.ietf-core-transport-indication" class="cite xref">I-D.ietf-core-transport-indication</a>]</span> covers the selection of this transport via SVCB
-records.<a href="#section-1-2" class="pilcrow">¶</a></p>
+<span>[<a href="#lwm2m" class="cite xref">lwm2m</a>]</span> are discussed. A future iteration of <span>[<a href="#I-D.ietf-core-transport-indication" class="cite xref">I-D.ietf-core-transport-indication</a>]</span> will cover the selection of this
+transport via SVCB records.<a href="#section-1-2" class="pilcrow">¶</a></p>
 <p id="section-1-3">However, CoAP offers three security modes:<a href="#section-1-3" class="pilcrow">¶</a></p>
 <ul class="normal">
 <li class="normal" id="section-1-4.1">
diff --git a/dnr-dtls-cleanup/draft-lenders-core-dnr.txt b/dnr-dtls-cleanup/draft-lenders-core-dnr.txt
index bbe2774..e1f7617 100644
--- a/dnr-dtls-cleanup/draft-lenders-core-dnr.txt
+++ b/dnr-dtls-cleanup/draft-lenders-core-dnr.txt
@@ -5,12 +5,12 @@
 Constrained RESTful Environments                           M. S. Lenders
 Internet-Draft                                                TU Dresden
 Intended status: Informational                                 C. Amsüss
-Expires: 7 November 2024                                                
+Expires: 22 December 2024                                               
                                                            T. C. Schmidt
                                                              HAW Hamburg
                                                              M. Wählisch
                                         TU Dresden & Barkhausen Institut
-                                                              6 May 2024
+                                                            20 June 2024
 
 
    Problem Statement for Discovery of Network-designated OSCORE-based
@@ -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 7 November 2024.
+   This Internet-Draft will expire on 22 December 2024.
 
 Copyright Notice
 
@@ -113,9 +113,9 @@ Table of Contents
    transfer protocol for DoC, is mostly agnostic to the transport layer,
    i.e., CoAP can be transported over UDP, TCP, or WebSockets [RFC8323],
    and even less common transports such as Bluetooth GATT
-   [I-D.amsuess-core-coap-over-gatt] or SMS [lwm2m] are discussed.
-   [I-D.ietf-core-transport-indication] covers the selection of this
-   transport via SVCB records.
+   [I-D.amsuess-core-coap-over-gatt] or SMS [lwm2m] are discussed.  A
+   future iteration of [I-D.ietf-core-transport-indication] will cover
+   the selection of this transport via SVCB records.
 
    However, CoAP offers three security modes: