Script updating gh-pages from 66b77f3. [ci skip]

Author: ID Bot

draft-ietf-core-groupcomm-proxy.html

@@ -1176,6 +1176,9 @@ <h2 id="name-copyright-notice">
 </li>
                   <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.1.2.2">
                     <p id="section-toc.1-1.5.2.1.2.2.1"><a href="#section-5.1.2" class="auto internal xref">5.1.2</a>.  <a href="#name-supporting-observe" class="internal xref">Supporting Observe</a></p>
+</li>
+                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.1.2.3">
+                    <p id="section-toc.1-1.5.2.1.2.3.1"><a href="#section-5.1.3" class="auto internal xref">5.1.3</a>.  <a href="#name-cancellation-of-ongoing-res" class="internal xref">Cancellation of Ongoing Response Forwarding</a></p>
 </li>
                 </ul>
 </li>
@@ -1187,6 +1190,9 @@ <h2 id="name-copyright-notice">
 </li>
                   <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.2.2.2">
                     <p id="section-toc.1-1.5.2.2.2.2.1"><a href="#section-5.2.2" class="auto internal xref">5.2.2</a>.  <a href="#name-supporting-observe-2" class="internal xref">Supporting Observe</a></p>
+</li>
+                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.2.2.3">
+                    <p id="section-toc.1-1.5.2.2.2.3.1"><a href="#section-5.2.3" class="auto internal xref">5.2.3</a>.  <a href="#name-cancellation-of-ongoing-resp" class="internal xref">Cancellation of Ongoing Response Forwarding</a></p>
 </li>
                 </ul>
 </li>
@@ -1280,6 +1286,9 @@ <h2 id="name-copyright-notice">
 <ul class="compact toc ulBare ulEmpty">
 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.1.2.1">
                     <p id="section-toc.1-1.8.2.1.2.1.1"><a href="#section-8.1.1" class="auto internal xref">8.1.1</a>.  <a href="#name-supporting-observe-6" class="internal xref">Supporting Observe</a></p>
+</li>
+                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.1.2.2">
+                    <p id="section-toc.1-1.8.2.1.2.2.1"><a href="#section-8.1.2" class="auto internal xref">8.1.2</a>.  <a href="#name-cancellation-of-ongoing-respo" class="internal xref">Cancellation of Ongoing Response Forwarding</a></p>
 </li>
                 </ul>
 </li>
@@ -1689,6 +1698,45 @@ <h4 id="name-supporting-observe">
 <p id="section-5.1.2-2">Furthermore, the client especially follows what is specified in <span><a href="https://rfc-editor.org/rfc/rfc7641#section-5" class="relref">Section 5</a> of [<a href="#RFC7641" class="cite xref">RFC7641</a>]</span>, i.e., it registers its interest to be an observer with the proxy, as if it was communicating with the servers.<a href="#section-5.1.2-2" class="pilcrow">¶</a></p>
 </section>
 </div>
+<div id="ssec-cancel-forwarding">
+<section id="section-5.1.3">
+          <h4 id="name-cancellation-of-ongoing-res">
+<a href="#section-5.1.3" class="section-number selfRef">5.1.3. </a><a href="#name-cancellation-of-ongoing-res" class="section-name selfRef">Cancellation of Ongoing Response Forwarding</a>
+          </h4>
+<p id="section-5.1.3-1">After having sent the unicast request to the proxy but before timeout expiration, the client might become not interested in receiving further corresponding responses, i.e., from that point in time until T seconds have elapsed since the request was sent to the proxy.<a href="#section-5.1.3-1" class="pilcrow">¶</a></p>
+<p id="section-5.1.3-2">In such a case the client <span class="bcp14">MAY</span> ask the proxy for an early stop of the ongoing response forwarding, i.e., to not forward to the client any further response received to the forwarded group request from the servers.<a href="#section-5.1.3-2" class="pilcrow">¶</a></p>
+<p id="section-5.1.3-3">To this end, the client can rely on one of the following two approaches.<a href="#section-5.1.3-3" class="pilcrow">¶</a></p>
+<ul class="normal">
+<li class="normal" id="section-5.1.3-4.1">
+              <p id="section-5.1.3-4.1.1">The client acts like it would at timeout expiration (see <a href="#ssec-resp-proc-client-steps" class="auto internal xref">Section 5.5.1</a>), i.e., it simply frees up its local Token value associated with the original unicast request sent to the proxy.<a href="#section-5.1.3-4.1.1" class="pilcrow">¶</a></p>
+<p id="section-5.1.3-4.1.2">
+Consequently, further responses forwarded by the proxy would result in the client sending a CoAP Reset message (RST), which the proxy would interpret as a loss of interest from the client.<a href="#section-5.1.3-4.1.2" class="pilcrow">¶</a></p>
+<p id="section-5.1.3-4.1.3">
+While this approach would work when using CoAP over UDP between the client and the proxy, it might not be suitable in case a different transport is used instead.<a href="#section-5.1.3-4.1.3" class="pilcrow">¶</a></p>
+</li>
+            <li class="normal" id="section-5.1.3-4.2">
+              <p id="section-5.1.3-4.2.1">The client sends to the proxy a new CoAP unicast request, namely Early Stop Request, such that:<a href="#section-5.1.3-4.2.1" class="pilcrow">¶</a></p>
+<ul class="normal">
+<li class="normal" id="section-5.1.3-4.2.2.1">
+                  <p id="section-5.1.3-4.2.2.1.1">It <span class="bcp14">MUST</span> use the method GET.<a href="#section-5.1.3-4.2.2.1.1" class="pilcrow">¶</a></p>
+</li>
+                <li class="normal" id="section-5.1.3-4.2.2.2">
+                  <p id="section-5.1.3-4.2.2.2.1">It <span class="bcp14">MUST</span> use the same Token value of the original unicast request sent to the proxy. This explicitly relates the present Early Stop Request to the original unicast request.<a href="#section-5.1.3-4.2.2.2.1" class="pilcrow">¶</a></p>
+</li>
+                <li class="normal" id="section-5.1.3-4.2.2.3">
+                  <p id="section-5.1.3-4.2.2.3.1">It <span class="bcp14">MUST</span> include the Multicast-Timeout Option, specifying 0 as option value. This explicitly indicates the client's wish to stop receiving further responses to the original unicast request.<a href="#section-5.1.3-4.2.2.3.1" class="pilcrow">¶</a></p>
+</li>
+                <li class="normal" id="section-5.1.3-4.2.2.4">
+                  <p id="section-5.1.3-4.2.2.4.1">It <span class="bcp14">MUST NOT</span> include any of the following: the Proxy-Uri Option or the Proxy-Cri Option; the Proxy-Scheme Option or the Proxy-Scheme-Number Option, together with the Uri-* options. This explicitly indicates the proxy to not forward the Early Stop Request.<a href="#section-5.1.3-4.2.2.4.1" class="pilcrow">¶</a></p>
+</li>
+              </ul>
+<p id="section-5.1.3-4.2.3">
+After sending the Early Stop Request, the client frees up its local Token value associated with the original unicast request sent to the proxy.<a href="#section-5.1.3-4.2.3" class="pilcrow">¶</a></p>
+</li>
+          </ul>
+<p id="section-5.1.3-5">Note that, irrespective of the approach used by the client, freeing up the Token value does not make it eligible for possible reuse yet (see <a href="#ssec-req-send-steps" class="auto internal xref">Section 5.1.1</a>).<a href="#section-5.1.3-5" class="pilcrow">¶</a></p>
+</section>
+</div>
 </section>
 </div>
 <div id="ssec-req-proc-proxy">
@@ -1745,6 +1793,16 @@ <h4 id="name-supporting-observe-2">
 <p id="section-5.2.2-2">When doing so, the proxy especially follows what is specified for the client in <span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-groupcomm-bis-13#section-3.7" class="relref">Section 3.7</a> of [<a href="#I-D.ietf-core-groupcomm-bis" class="cite xref">I-D.ietf-core-groupcomm-bis</a>]</span>, by forwarding the group request to the servers over IP multicast as defined in <a href="#ssec-req-proc-proxy-steps" class="auto internal xref">Section 5.2.1</a> of this document.<a href="#section-5.2.2-2" class="pilcrow">¶</a></p>
 </section>
 </div>
+<div id="ssec-cancel-forwarding-proxy">
+<section id="section-5.2.3">
+          <h4 id="name-cancellation-of-ongoing-resp">
+<a href="#section-5.2.3" class="section-number selfRef">5.2.3. </a><a href="#name-cancellation-of-ongoing-resp" class="section-name selfRef">Cancellation of Ongoing Response Forwarding</a>
+          </h4>
+<p id="section-5.2.3-1">As defined in <a href="#ssec-cancel-forwarding" class="auto internal xref">Section 5.1.3</a>, the client might ask the proxy for an early stop of the ongoing response forwarding, i.e., to stop forwarding to the client any further responses received to the forwarded group request from the servers.<a href="#section-5.2.3-1" class="pilcrow">¶</a></p>
+<p id="section-5.2.3-2">Consistently, the proxy stops forwarding such responses to the client, after receiving a CoAP Reset message (RST) in reply to one of such responses, or after receiving an Early Stop Request related to the ongoing response forwarding (i.e., using the same Token value of the original unicast request from the client).<a href="#section-5.2.3-2" class="pilcrow">¶</a></p>
+<p id="section-5.2.3-3">After that, in case the proxy receives further responses to the forwarded group request from the servers, the proxy <span class="bcp14">MUST NOT</span> forward those responses to the client. In fact, the proxy can safely free up its local Token value associated with that group request, which results in discarding any further responses to the same group request received from then on from the servers.<a href="#section-5.2.3-3" class="pilcrow">¶</a></p>
+</section>
+</div>
 </section>
 </div>
 <div id="ssec-req-resp-proc-server">
@@ -2410,6 +2468,16 @@ <h4 id="name-supporting-observe-6">
 <p id="section-8.1.1-2">Any other proxy in the chain acts as a client and registers its own interest to observe the target resource with the next hop towards the origin servers, as per <span><a href="https://rfc-editor.org/rfc/rfc7641#section-5" class="relref">Section 5</a> of [<a href="#RFC7641" class="cite xref">RFC7641</a>]</span>.<a href="#section-8.1.1-2" class="pilcrow">¶</a></p>
 </section>
 </div>
+<div id="ssec-cancel-forwarding-proxy-chain">
+<section id="section-8.1.2">
+          <h4 id="name-cancellation-of-ongoing-respo">
+<a href="#section-8.1.2" class="section-number selfRef">8.1.2. </a><a href="#name-cancellation-of-ongoing-respo" class="section-name selfRef">Cancellation of Ongoing Response Forwarding</a>
+          </h4>
+<p id="section-8.1.2-1">Consistently with what is described in <a href="#ssec-cancel-forwarding-proxy" class="auto internal xref">Section 5.2.3</a>, a proxy might be asked by the (previous hop proxy closer to the) origin client for an early stop of the ongoing response forwarding.<a href="#section-8.1.2-1" class="pilcrow">¶</a></p>
+<p id="section-8.1.2-2">That is, the proxy is asked to stop forwarding to the (previous hop proxy closer to the) origin client any further responses received to the forwarded group request from the (next hop proxy towards the) origin servers.<a href="#section-8.1.2-2" class="pilcrow">¶</a></p>
+<p id="section-8.1.2-3">When this happens, the proxy proceeds as described in <a href="#ssec-cancel-forwarding-proxy" class="auto internal xref">Section 5.2.3</a>. Furthermore, if the proxy is not the last one in the chain, the proxy <span class="bcp14">MAY</span> send to the next hop proxy towards the origin servers an Early Stop Request (see <a href="#ssec-req-proc-proxy-steps" class="auto internal xref">Section 5.2.1</a>), with the same Token value of the group request that the proxy forwarded to the next hop proxy towards the origin servers.<a href="#section-8.1.2-3" class="pilcrow">¶</a></p>
+</section>
+</div>
 </section>
 </div>
 <div id="sec-proxy-chain-response-processing">
@@ -3719,10 +3787,13 @@ <h3 id="name-version-03-to-04">
             <p id="appendix-B.1-1.2.1">More precise semantics for the Reply-From Option.<a href="#appendix-B.1-1.2.1" class="pilcrow">¶</a></p>
 </li>
           <li class="normal" id="appendix-B.1-1.3">
-            <p id="appendix-B.1-1.3.1">Suggested value ranges for codepoints to register.<a href="#appendix-B.1-1.3.1" class="pilcrow">¶</a></p>
+            <p id="appendix-B.1-1.3.1">Defined early cancellation of ongoing response forwarding.<a href="#appendix-B.1-1.3.1" class="pilcrow">¶</a></p>
 </li>
           <li class="normal" id="appendix-B.1-1.4">
-            <p id="appendix-B.1-1.4.1">Clarifications and editorial improvements.<a href="#appendix-B.1-1.4.1" class="pilcrow">¶</a></p>
+            <p id="appendix-B.1-1.4.1">Suggested value ranges for codepoints to register.<a href="#appendix-B.1-1.4.1" class="pilcrow">¶</a></p>
+</li>
+          <li class="normal" id="appendix-B.1-1.5">
+            <p id="appendix-B.1-1.5.1">Clarifications and editorial improvements.<a href="#appendix-B.1-1.5.1" class="pilcrow">¶</a></p>
 </li>
         </ul>
 </section>

draft-ietf-core-groupcomm-proxy.txt

@@ -79,9 +79,11 @@ Table of Contents
      5.1.  Request Sending at the Client
        5.1.1.  Request Sending
        5.1.2.  Supporting Observe
+       5.1.3.  Cancellation of Ongoing Response Forwarding
      5.2.  Request Processing at the Proxy
        5.2.1.  Request Processing
        5.2.2.  Supporting Observe
+       5.2.3.  Cancellation of Ongoing Response Forwarding
      5.3.  Request and Response Processing at the Server
        5.3.1.  Request and Response Processing
        5.3.2.  Supporting Observe
@@ -107,6 +109,7 @@ Table of Contents
    8.  Chain of Proxies
      8.1.  Request Processing at the Proxy
        8.1.1.  Supporting Observe
+       8.1.2.  Cancellation of Ongoing Response Forwarding
      8.2.  Response Processing at the Proxy
        8.2.1.  Supporting Observe
    9.  HTTP-to-CoAP Proxies
@@ -500,6 +503,61 @@ Table of Contents
    Section 5 of [RFC7641], i.e., it registers its interest to be an
    observer with the proxy, as if it was communicating with the servers.
 
+5.1.3.  Cancellation of Ongoing Response Forwarding
+
+   After having sent the unicast request to the proxy but before timeout
+   expiration, the client might become not interested in receiving
+   further corresponding responses, i.e., from that point in time until
+   T seconds have elapsed since the request was sent to the proxy.
+
+   In such a case the client MAY ask the proxy for an early stop of the
+   ongoing response forwarding, i.e., to not forward to the client any
+   further response received to the forwarded group request from the
+   servers.
+
+   To this end, the client can rely on one of the following two
+   approaches.
+
+   *  The client acts like it would at timeout expiration (see
+      Section 5.5.1), i.e., it simply frees up its local Token value
+      associated with the original unicast request sent to the proxy.
+
+      Consequently, further responses forwarded by the proxy would
+      result in the client sending a CoAP Reset message (RST), which the
+      proxy would interpret as a loss of interest from the client.
+
+      While this approach would work when using CoAP over UDP between
+      the client and the proxy, it might not be suitable in case a
+      different transport is used instead.
+
+   *  The client sends to the proxy a new CoAP unicast request, namely
+      Early Stop Request, such that:
+
+      -  It MUST use the method GET.
+
+      -  It MUST use the same Token value of the original unicast
+         request sent to the proxy.  This explicitly relates the present
+         Early Stop Request to the original unicast request.
+
+      -  It MUST include the Multicast-Timeout Option, specifying 0 as
+         option value.  This explicitly indicates the client's wish to
+         stop receiving further responses to the original unicast
+         request.
+
+      -  It MUST NOT include any of the following: the Proxy-Uri Option
+         or the Proxy-Cri Option; the Proxy-Scheme Option or the Proxy-
+         Scheme-Number Option, together with the Uri-* options.  This
+         explicitly indicates the proxy to not forward the Early Stop
+         Request.
+
+      After sending the Early Stop Request, the client frees up its
+      local Token value associated with the original unicast request
+      sent to the proxy.
+
+   Note that, irrespective of the approach used by the client, freeing
+   up the Token value does not make it eligible for possible reuse yet
+   (see Section 5.1.1).
+
 5.2.  Request Processing at the Proxy
 
    This section defines the operations performed by the proxy, when
@@ -572,6 +630,26 @@ Table of Contents
    the group request to the servers over IP multicast as defined in
    Section 5.2.1 of this document.
 
+5.2.3.  Cancellation of Ongoing Response Forwarding
+
+   As defined in Section 5.1.3, the client might ask the proxy for an
+   early stop of the ongoing response forwarding, i.e., to stop
+   forwarding to the client any further responses received to the
+   forwarded group request from the servers.
+
+   Consistently, the proxy stops forwarding such responses to the
+   client, after receiving a CoAP Reset message (RST) in reply to one of
+   such responses, or after receiving an Early Stop Request related to
+   the ongoing response forwarding (i.e., using the same Token value of
+   the original unicast request from the client).
+
+   After that, in case the proxy receives further responses to the
+   forwarded group request from the servers, the proxy MUST NOT forward
+   those responses to the client.  In fact, the proxy can safely free up
+   its local Token value associated with that group request, which
+   results in discarding any further responses to the same group request
+   received from then on from the servers.
+
 5.3.  Request and Response Processing at the Server
 
    This section defines the operations performed by the server, when
@@ -1515,6 +1593,24 @@ Table of Contents
    interest to observe the target resource with the next hop towards the
    origin servers, as per Section 5 of [RFC7641].
 
+8.1.2.  Cancellation of Ongoing Response Forwarding
+
+   Consistently with what is described in Section 5.2.3, a proxy might
+   be asked by the (previous hop proxy closer to the) origin client for
+   an early stop of the ongoing response forwarding.
+
+   That is, the proxy is asked to stop forwarding to the (previous hop
+   proxy closer to the) origin client any further responses received to
+   the forwarded group request from the (next hop proxy towards the)
+   origin servers.
+
+   When this happens, the proxy proceeds as described in Section 5.2.3.
+   Furthermore, if the proxy is not the last one in the chain, the proxy
+   MAY send to the next hop proxy towards the origin servers an Early
+   Stop Request (see Section 5.2.1), with the same Token value of the
+   group request that the proxy forwarded to the next hop proxy towards
+   the origin servers.
+
 8.2.  Response Processing at the Proxy
 
    Upon receiving a response matching with the group request before the
@@ -2839,6 +2935,8 @@ B.1.  Version -03 to -04
 
    *  More precise semantics for the Reply-From Option.
 
+   *  Defined early cancellation of ongoing response forwarding.
+
    *  Suggested value ranges for codepoints to register.
 
    *  Clarifications and editorial improvements.