Skip to content

Commit

Permalink
Script updating gh-pages from 8b6065e. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Jun 18, 2024
1 parent 9591101 commit 470ab31
Show file tree
Hide file tree
Showing 2 changed files with 18 additions and 11 deletions.
7 changes: 5 additions & 2 deletions svcb-docpath/draft-ietf-core-dns-over-coap.html
Original file line number Diff line number Diff line change
Expand Up @@ -1481,7 +1481,7 @@ <h3 id="name-discovery-using-svcb-resour">
octets.<a href="#section-3.1-2" class="pilcrow"></a></p>
<p id="section-3.1-3">To use the service binding from a SVCB RR, the DoC client <span class="bcp14">MUST</span> send any DoC request to the CoAP
resource identifier constructed from the SvcParams including "docpath". A rough construction
algorithm could be as follows.
algorithm could be as follows, going through the provided records in order of their priority.
- If the "alpn" SvcParam value for the service is "coap", construct a CoAP request for CoAP over TCP,
if it is "co", construct one for CoAP over DTLS.
- The destination address for the request should be taken from additional information about the
Expand All @@ -1494,7 +1494,10 @@ <h3 id="name-discovery-using-svcb-resour">
the request.
- If a "port" SvcParam value is provided or if a port was queried, and if either differs from either
the default port of the transport or the destination port selected above, set that port in the
URI-Port option.<a href="#section-3.1-3" class="pilcrow"></a></p>
URI-Port option.
- If this request receives a response, use that for future DoC queries, until it becomes
unreachable. If not, or if it becomes unreachable, repeat with the SVCB record with the next
highest priority.<a href="#section-3.1-3" class="pilcrow"></a></p>
<p id="section-3.1-4">A more generalized construction algorithm can be found in <span>[<a href="#I-D.ietf-core-transport-indication" class="cite xref">I-D.ietf-core-transport-indication</a>]</span>.<a href="#section-3.1-4" class="pilcrow"></a></p>
</section>
</div>
Expand Down
22 changes: 13 additions & 9 deletions svcb-docpath/draft-ietf-core-dns-over-coap.txt
Original file line number Diff line number Diff line change
Expand Up @@ -250,21 +250,25 @@ Table of Contents
To use the service binding from a SVCB RR, the DoC client MUST send
any DoC request to the CoAP resource identifier constructed from the
SvcParams including "docpath". A rough construction algorithm could
be as follows. - If the "alpn" SvcParam value for the service is
"coap", construct a CoAP request for CoAP over TCP, if it is "co",
construct one for CoAP over DTLS. - The destination address for the
request should be taken from additional information about the target,
e.g. from an AAAA record associated to the target or from am
"ipv6hint" SvcParam value, or, as a fallback, by querying an address
for the queried host name of the SVCB record. - The destination port
for the address is taken from the "port" SvcParam value, if present.
be as follows, going through the provided records in order of their
priority. - If the "alpn" SvcParam value for the service is "coap",
construct a CoAP request for CoAP over TCP, if it is "co", construct
one for CoAP over DTLS. - The destination address for the request
should be taken from additional information about the target, e.g.
from an AAAA record associated to the target or from am "ipv6hint"
SvcParam value, or, as a fallback, by querying an address for the
queried host name of the SVCB record. - The destination port for the
address is taken from the "port" SvcParam value, if present.
Otherwise, take the default port of the CoAP transport. - Set the
queried host name of SVCB record in the URI-Host option. - For each
element in the CBOR sequence of the "docpath" SvcParam value, add a
Uri-Path option to the request. - If a "port" SvcParam value is
provided or if a port was queried, and if either differs from either
the default port of the transport or the destination port selected
above, set that port in the URI-Port option.
above, set that port in the URI-Port option. - If this request
receives a response, use that for future DoC queries, until it
becomes unreachable. If not, or if it becomes unreachable, repeat
with the SVCB record with the next highest priority.

A more generalized construction algorithm can be found in
[I-D.ietf-core-transport-indication].
Expand Down

0 comments on commit 470ab31

Please sign in to comment.