Script updating gh-pages from 7a854cf. [ci skip]

svcb-docpath/draft-ietf-core-dns-over-coap.html

@@ -1448,13 +1448,12 @@ <h2 id="name-selection-of-a-doc-server">
 Automatic configuration <span class="bcp14">SHOULD</span> only be done from a trusted source.<a href="#section-3-1" class="pilcrow">¶</a></p>
 <p id="section-3-2">A DoC server can also be discovered using SVCB Resource Records <span>[<a href="#RFC9460" class="cite xref">RFC9460</a>]</span>, <span>[<a href="#RFC9461" class="cite xref">RFC9461</a>]</span> or DNR
 Service Parameters <span>[<a href="#RFC9463" class="cite xref">RFC9463</a>]</span>.
-<span>[<a href="#I-D.lenders-core-dnr" class="cite xref">I-D.lenders-core-dnr</a>]</span> [TBD: change to draft-lenders-core-coap-dtls-svcb when published] provides solutions
+[TBD: draft-lenders-core-coap-dtls-svcb] provides solutions
 to discover CoAP over (D)TLS servers using the "alpn" SvcParam. This document specifies "docpath" as
-a single-valued SvcParamKey whose value (in both presentation and wire format) <span class="bcp14">MUST</span> be a CoAP
-resource path. The DoC client <span class="bcp14">MUST</span> send any DoC request to the CoAP resource identified with the
-scheme associated with protocol identified with the "alpn" SvcParam or a comparable SvcParam, the
-authentication name as the host, the port from the "port" SvcParam (if present), and the path from
-the "docpath" SvcParam.<a href="#section-3-2" class="pilcrow">¶</a></p>
+a single-valued SvcParamKey whose value (in both presentation and wire format) <span class="bcp14">MUST</span> be a URI
+reference (<span>[<a href="#RFC3986" class="cite xref">RFC3986</a>]</span>) in its path-abempty form. The DoC client <span class="bcp14">MUST</span> send any DoC request to the CoAP
+resource identified by the URI constructed from the "docpath" SvcParam as described in
+[TBD: draft-lenders-core-coap-dtls-svcb].<a href="#section-3-2" class="pilcrow">¶</a></p>
 <p id="section-3-3">When discovering the DNS resource through a link mechanism that allows describing a resource type
 (e.g., the Resource Type Attribute in <span>[<a href="#RFC6690" class="cite xref">RFC6690</a>]</span>), the resource type "core.dns" can be
 used to identify a generic DNS resolver that is available to the client.<a href="#section-3-3" class="pilcrow">¶</a></p>

svcb-docpath/draft-ietf-core-dns-over-coap.txt

@@ -211,17 +211,15 @@ Table of Contents
    configuration SHOULD only be done from a trusted source.
 
    A DoC server can also be discovered using SVCB Resource Records
-   [RFC9460], [RFC9461] or DNR Service Parameters [RFC9463].
-   [I-D.lenders-core-dnr] [TBD: change to draft-lenders-core-coap-dtls-
-   svcb when published] provides solutions to discover CoAP over (D)TLS
-   servers using the "alpn" SvcParam.  This document specifies "docpath"
-   as a single-valued SvcParamKey whose value (in both presentation and
-   wire format) MUST be a CoAP resource path.  The DoC client MUST send
-   any DoC request to the CoAP resource identified with the scheme
-   associated with protocol identified with the "alpn" SvcParam or a
-   comparable SvcParam, the authentication name as the host, the port
-   from the "port" SvcParam (if present), and the path from the
-   "docpath" SvcParam.
+   [RFC9460], [RFC9461] or DNR Service Parameters [RFC9463].  [TBD:
+   draft-lenders-core-coap-dtls-svcb] provides solutions to discover
+   CoAP over (D)TLS servers using the "alpn" SvcParam.  This document
+   specifies "docpath" as a single-valued SvcParamKey whose value (in
+   both presentation and wire format) MUST be a URI reference
+   ([RFC3986]) in its path-abempty form.  The DoC client MUST send any
+   DoC request to the CoAP resource identified by the URI constructed
+   from the "docpath" SvcParam as described in [TBD: draft-lenders-core-
+   coap-dtls-svcb].
 
    When discovering the DNS resource through a link mechanism that
    allows describing a resource type (e.g., the Resource Type Attribute