Script updating gh-pages from 43c0516. [ci skip]

Author: ID Bot

Diff for: 75-update-spec/draft-agntcy-ads.html

@@ -1189,7 +1189,15 @@ <h2 id="name-copyright-notice">
             <p id="section-toc.1-1.5.1"><a href="#section-5" class="auto internal xref">5</a>.  <a href="#name-iana-considerations" class="internal xref">IANA Considerations</a></p>
 </li>
           <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6">
-            <p id="section-toc.1-1.6.1"><a href="#section-6" class="auto internal xref">6</a>.  <a href="#name-normative-references" class="internal xref">Normative References</a></p>
+            <p id="section-toc.1-1.6.1"><a href="#section-6" class="auto internal xref">6</a>.  <a href="#name-references" class="internal xref">References</a></p>
+<ul class="compact toc ulBare ulEmpty">
+<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.1">
+                <p id="section-toc.1-1.6.2.1.1"><a href="#section-6.1" class="auto internal xref">6.1</a>.  <a href="#name-normative-references" class="internal xref">Normative References</a></p>
+</li>
+              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.2">
+                <p id="section-toc.1-1.6.2.2.1"><a href="#section-6.2" class="auto internal xref">6.2</a>.  <a href="#name-informative-references" class="internal xref">Informative References</a></p>
+</li>
+            </ul>
 </li>
           <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7">
             <p id="section-toc.1-1.7.1"><a href="#appendix-A" class="auto internal xref"></a><a href="#name-authors-addresses" class="internal xref">Authors' Addresses</a></p>
@@ -1236,8 +1244,8 @@ <h2 id="name-naming">
 <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-naming" class="section-name selfRef">Naming</a>
       </h2>
 <p id="section-3-1">In distributed systems, a reliable and collision-resistant naming scheme is
-crucial. The agent directory uses cryptographic hashes to generate globally
-unique identifiers for data records.<a href="#section-3-1" class="pilcrow">¶</a></p>
+crucial. The agent directory uses cryptographic hashes <span>[<a href="#RFC7838" class="cite xref">RFC7838</a>]</span> to generate
+globally unique identifiers for data records.<a href="#section-3-1" class="pilcrow">¶</a></p>
 <p id="section-3-2">ADS leverages OCI as object storage, and therefore identifiers are made
 available as described in [OCI digest].<a href="#section-3-2" class="pilcrow">¶</a></p>
 </section>
@@ -1285,7 +1293,7 @@ <h3 id="name-discovery-process">
             <p id="section-4.2-5.2.1">Server location information: Determines optimal data sources.<a href="#section-4.2-5.2.1" class="pilcrow">¶</a></p>
 </li>
         </ol>
-<p id="section-4.2-6">ADS uses libp2p [Kad-DHT] for server and content discovery.<a href="#section-4.2-6" class="pilcrow">¶</a></p>
+<p id="section-4.2-6">ADS uses libp2p <span><a href="#DHT" class="internal xref">Kad-DHT</a> [<a href="#DHT" class="cite xref">DHT</a>]</span> for server and content discovery.<a href="#section-4.2-6" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="distributed-object-storage">
@@ -1349,27 +1357,51 @@ <h2 id="name-iana-considerations">
 <p id="section-5-1">This document has no IANA actions.<a href="#section-5-1" class="pilcrow">¶</a></p>
 </section>
 </div>
-<div id="sec-normative-references">
+<div id="sec-combined-references">
 <section id="section-6">
-      <h2 id="name-normative-references">
-<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
+      <h2 id="name-references">
+<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-references" class="section-name selfRef">References</a>
       </h2>
+<div id="sec-normative-references">
+<section id="section-6.1">
+        <h3 id="name-normative-references">
+<a href="#section-6.1" class="section-number selfRef">6.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
+        </h3>
 <dl class="references">
 <dt id="RFC2119">[RFC2119]</dt>
-      <dd>
+        <dd>
 <span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03" class="refDate">March 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc2119">https://www.rfc-editor.org/rfc/rfc2119</a>&gt;</span>. </dd>
 <dd class="break"></dd>
 <dt id="RFC6920">[RFC6920]</dt>
-      <dd>
+        <dd>
 <span class="refAuthor">Farrell, S.</span>, <span class="refAuthor">Kutscher, D.</span>, <span class="refAuthor">Dannewitz, C.</span>, <span class="refAuthor">Ohlman, B.</span>, <span class="refAuthor">Keranen, A.</span>, and <span class="refAuthor">P. Hallam-Baker</span>, <span class="refTitle">"Naming Things with Hashes"</span>, <span class="seriesInfo">RFC 6920</span>, <span class="seriesInfo">DOI 10.17487/RFC6920</span>, <time datetime="2013-04" class="refDate">April 2013</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc6920">https://www.rfc-editor.org/rfc/rfc6920</a>&gt;</span>. </dd>
 <dd class="break"></dd>
+<dt id="RFC7838">[RFC7838]</dt>
+        <dd>
+<span class="refAuthor">Nottingham, M.</span>, <span class="refAuthor">McManus, P.</span>, and <span class="refAuthor">J. Reschke</span>, <span class="refTitle">"HTTP Alternative Services"</span>, <span class="seriesInfo">RFC 7838</span>, <span class="seriesInfo">DOI 10.17487/RFC7838</span>, <time datetime="2016-04" class="refDate">April 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc7838">https://www.rfc-editor.org/rfc/rfc7838</a>&gt;</span>. </dd>
+<dd class="break"></dd>
 <dt id="RFC8174">[RFC8174]</dt>
-    <dd>
+      <dd>
 <span class="refAuthor">Leiba, B.</span>, <span class="refTitle">"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 8174</span>, <span class="seriesInfo">DOI 10.17487/RFC8174</span>, <time datetime="2017-05" class="refDate">May 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc8174">https://www.rfc-editor.org/rfc/rfc8174</a>&gt;</span>. </dd>
 <dd class="break"></dd>
 </dl>
 </section>
 </div>
+<div id="sec-informative-references">
+<section id="section-6.2">
+        <h3 id="name-informative-references">
+<a href="#section-6.2" class="section-number selfRef">6.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
+        </h3>
+<dl class="references">
+<dt id="DHT">[DHT]</dt>
+      <dd>
+<span class="refTitle">"*** BROKEN REFERENCE ***"</span>. </dd>
+<dd class="break"></dd>
+</dl>
+</section>
+</div>
+</section>
+</div>
 <div id="authors-addresses">
 <section id="appendix-A">
       <h2 id="name-authors-addresses">

Diff for: 75-update-spec/draft-agntcy-ads.txt

@@ -71,7 +71,9 @@ Table of Contents
        4.3.1.  Simplified Content Retrieval
        4.3.2.  OCI Integration
    5.  IANA Considerations
-   6.  Normative References
+   6.  References
+     6.1.  Normative References
+     6.2.  Informative References
    Authors' Addresses
 
 1.  Conventions and Definitions
@@ -106,8 +108,8 @@ Table of Contents
 3.  Naming
 
    In distributed systems, a reliable and collision-resistant naming
-   scheme is crucial.  The agent directory uses cryptographic hashes to
-   generate globally unique identifiers for data records.
+   scheme is crucial.  The agent directory uses cryptographic hashes
+   [RFC7838] to generate globally unique identifiers for data records.
 
    ADS leverages OCI as object storage, and therefore identifiers are
    made available as described in [OCI digest].
@@ -141,7 +143,7 @@ Table of Contents
 
    2.  Server location information: Determines optimal data sources.
 
-   ADS uses libp2p [Kad-DHT] for server and content discovery.
+   ADS uses libp2p Kad-DHT [DHT] for server and content discovery.
 
 4.3.  Distributed Object Storage
 
@@ -180,7 +182,9 @@ Table of Contents
 
    This document has no IANA actions.
 
-6.  Normative References
+6.  References
+
+6.1.  Normative References
 
    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
               Requirement Levels", BCP 14, RFC 2119,
@@ -192,10 +196,18 @@ Table of Contents
               Hashes", RFC 6920, DOI 10.17487/RFC6920, April 2013,
               <https://www.rfc-editor.org/rfc/rfc6920>.
 
+   [RFC7838]  Nottingham, M., McManus, P., and J. Reschke, "HTTP
+              Alternative Services", RFC 7838, DOI 10.17487/RFC7838,
+              April 2016, <https://www.rfc-editor.org/rfc/rfc7838>.
+
    [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
               2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
               May 2017, <https://www.rfc-editor.org/rfc/rfc8174>.
 
+6.2.  Informative References
+
+   [DHT]      "*** BROKEN REFERENCE ***".
+
 Authors' Addresses
 
    Luca Muscariello