fixup! fixup! Add "docpath" SVCB ParamKey definition

draft-ietf-core-dns-over-coap.md

@@ -213,7 +213,7 @@ octets.
 
 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.
+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
@@ -227,9 +227,13 @@ algorithm could be as follows.
 - 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.
+- 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 {{-transport-indication}}.
 
+
 Basic Message Exchange
 ======================