Script updating gh-pages from 5161e99. [ci skip]

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

@@ -1448,10 +1448,13 @@ <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 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-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>
+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 <span>[<a href="#ADD" class="cite xref">ADD</a>]</span>.<a href="#section-10-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="maximum-fragment-length-negotiation">
@@ -1872,6 +1875,10 @@ <h3 id="name-informative-references">
 <a href="#section-23.2" class="section-number selfRef">23.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
         </h3>
 <dl class="references">
+<dt id="ADD">[ADD]</dt>
+        <dd>
+<span class="refAuthor">IETF</span>, <span class="refTitle">"Adaptive DNS Discovery (add) Working Group"</span>, <time datetime="2023-09" class="refDate">September 2023</time>, <span>&lt;<a href="https://datatracker.ietf.org/wg/add/about/">https://datatracker.ietf.org/wg/add/about/</a>&gt;</span>. </dd>
+<dd class="break"></dd>
 <dt id="Ambrose2017">[Ambrose2017]</dt>
         <dd>
 <span class="refAuthor">Ambrose, C.</span>, <span class="refAuthor">Bos, J. W.</span>, <span class="refAuthor">Fay, B.</span>, <span class="refAuthor">Joye, M.</span>, <span class="refAuthor">Lochter, M.</span>, and <span class="refAuthor">B. Murray</span>, <span class="refTitle">"Differential Attacks on Deterministic Signatures"</span>, <time datetime="2017" class="refDate">2017</time>, <span>&lt;<a href="https://eprint.iacr.org/2017/975.pdf">https://eprint.iacr.org/2017/975.pdf</a>&gt;</span>. </dd>

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

@@ -246,7 +246,7 @@ Table of Contents
    altogether further protocols are needed, including DoH [RFC8484] and
    DPRIVE [RFC7858] [RFC8094].  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.
+   defined by the Adaptive DNS Discovery (add) working group [ADD].
 
 11.   Maximum Fragment Length Negotiation
 
@@ -578,6 +578,10 @@ Table of Contents
 
 23.2.  Informative References
 
+   [ADD]      IETF, "Adaptive DNS Discovery (add) Working Group",
+              September 2023,
+              <https://datatracker.ietf.org/wg/add/about/>.
+
    [Ambrose2017]
               Ambrose, C., Bos, J. W., Fay, B., Joye, M., Lochter, M.,
               and B. Murray, "Differential Attacks on Deterministic