Script updating gh-pages from 88d091a. [ci skip]

define-terms/draft-ietf-quic-transport.html

@@ -290,13 +290,13 @@
 <link href="#rfc.section.2.1" rel="Chapter" title="2.1 Stream Types and Identifiers">
 <link href="#rfc.section.2.2" rel="Chapter" title="2.2 Sending and Receiving Data">
 <link href="#rfc.section.2.3" rel="Chapter" title="2.3 Stream Prioritization">
+<link href="#rfc.section.2.4" rel="Chapter" title="2.4 Required Operations on Streams">
 <link href="#rfc.section.3" rel="Chapter" title="3 Stream States">
 <link href="#rfc.section.3.1" rel="Chapter" title="3.1 Sending Stream States">
 <link href="#rfc.section.3.2" rel="Chapter" title="3.2 Receiving Stream States">
 <link href="#rfc.section.3.3" rel="Chapter" title="3.3 Permitted Frame Types">
 <link href="#rfc.section.3.4" rel="Chapter" title="3.4 Bidirectional Stream States">
 <link href="#rfc.section.3.5" rel="Chapter" title="3.5 Solicited State Transitions">
-<link href="#rfc.section.3.6" rel="Chapter" title="3.6 Required Operations on Streams">
 <link href="#rfc.section.4" rel="Chapter" title="4 Flow Control">
 <link href="#rfc.section.4.1" rel="Chapter" title="4.1 Data Flow Control">
 <link href="#rfc.section.4.2" rel="Chapter" title="4.2 Flow Credit Increments">
@@ -541,6 +541,8 @@ <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
 </li>
 <li>2.3.   <a href="#rfc.section.2.3">Stream Prioritization</a>
 </li>
+<li>2.4.   <a href="#rfc.section.2.4">Required Operations on Streams</a>
+</li>
 </ul><li>3.   <a href="#rfc.section.3">Stream States</a>
 </li>
 <ul><li>3.1.   <a href="#rfc.section.3.1">Sending Stream States</a>
@@ -553,8 +555,6 @@ <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
 </li>
 <li>3.5.   <a href="#rfc.section.3.5">Solicited State Transitions</a>
 </li>
-<li>3.6.   <a href="#rfc.section.3.6">Required Operations on Streams</a>
-</li>
 </ul><li>4.   <a href="#rfc.section.4">Flow Control</a>
 </li>
 <ul><li>4.1.   <a href="#rfc.section.4.1">Data Flow Control</a>
@@ -1062,6 +1062,12 @@ <h2 id="rfc.section.2.3">
 <p id="rfc.section.2.3.p.1">Stream multiplexing can have a significant effect on application performance if resources allocated to streams are correctly prioritized.</p>
 <p id="rfc.section.2.3.p.2">QUIC does not provide a mechanism for exchanging prioritization information.  Instead, it relies on receiving priority information from the application that uses QUIC.</p>
 <p id="rfc.section.2.3.p.3">A QUIC implementation SHOULD provide ways in which an application can indicate the relative priority of streams.  When deciding which streams to dedicate resources to, the implementation SHOULD use the information provided by the application.</p>
+<h2 id="rfc.section.2.4">
+<a href="#rfc.section.2.4">2.4.</a> <a href="#required-operations-on-streams" id="required-operations-on-streams">Required Operations on Streams</a>
+</h2>
+<p id="rfc.section.2.4.p.1">There are certain operations which an application MUST be able to perform when interacting with QUIC streams.  This document does not specify an API, but any implementation of this version of QUIC MUST expose the ability to perform the operations described in this section on a QUIC stream.</p>
+<p id="rfc.section.2.4.p.2">On the sending part of a stream: - Attempt to write data, understanding when stream flow control credit (<a href="#data-flow-control" class="xref">Section 4.1</a>) has successfully been reserved to send the written data or possibly discovering that the stream has been closed because the peer sent a STOP_SENDING frame (<a href="#frame-stop-sending" class="xref">Section 19.5</a>) - Cleanly terminate the stream, resulting in a STREAM frame (<a href="#frame-stream" class="xref">Section 19.8</a>) with the FIN bit set - Abruptly terminate the stream, resulting in a RESET_STREAM frame (<a href="#frame-reset-stream" class="xref">Section 19.4</a>), even if the stream was cleanly terminated previously</p>
+<p id="rfc.section.2.4.p.3">On the receiving part of a stream: - Attempt to read data, possibly discovering that the peer has terminated the stream either cleanly or abruptly - Abort reading of the stream and request closure, resulting in a STOP_SENDING frame (<a href="#frame-stop-sending" class="xref">Section 19.5</a>)</p>
 <h1 id="rfc.section.3">
 <a href="#rfc.section.3">3.</a> <a href="#stream-states" id="stream-states">Stream States</a>
 </h1>
@@ -1268,12 +1274,6 @@ <h2 id="rfc.section.3.5">
 <p id="rfc.section.3.5.p.6">STOP_SENDING SHOULD only be sent for a stream that has not been reset by the peer. STOP_SENDING is most useful for streams in the &#8220;Recv&#8221; or &#8220;Size Known&#8221; states.</p>
 <p id="rfc.section.3.5.p.7">An endpoint is expected to send another STOP_SENDING frame if a packet containing a previous STOP_SENDING is lost.  However, once either all stream data or a RESET_STREAM frame has been received for the stream - that is, the stream is in any state other than &#8220;Recv&#8221; or &#8220;Size Known&#8221; - sending a STOP_SENDING frame is unnecessary.</p>
 <p id="rfc.section.3.5.p.8">An endpoint that wishes to terminate both directions of a bidirectional stream can terminate one direction by sending a RESET_STREAM, and it can encourage prompt termination in the opposite direction by sending a STOP_SENDING frame.</p>
-<h2 id="rfc.section.3.6">
-<a href="#rfc.section.3.6">3.6.</a> <a href="#required-operations-on-streams" id="required-operations-on-streams">Required Operations on Streams</a>
-</h2>
-<p id="rfc.section.3.6.p.1">There are certain operations which an application MUST be able to perform when interacting with QUIC streams.  This document does not specify an API, but any implementation of this version of QUIC MUST expose the ability to perform the operations described in this section on a QUIC stream.</p>
-<p id="rfc.section.3.6.p.2">On the sending part of a stream: - Attempt to write data, understanding when stream flow control credit (<a href="#data-flow-control" class="xref">Section 4.1</a>) has successfully been reserved to send the written data or possibly discovering that the stream has been closed because the peer sent a STOP_SENDING frame (<a href="#frame-stop-sending" class="xref">Section 19.5</a>) - Cleanly terminate the stream, resulting in a STREAM frame (<a href="#frame-stream" class="xref">Section 19.8</a>) with the FIN bit set - Abruptly terminate the stream, resulting in a RESET_STREAM frame (<a href="#frame-reset-stream" class="xref">Section 19.4</a>), even if the stream was cleanly terminated previously</p>
-<p id="rfc.section.3.6.p.3">On the receiving part of a stream: - Attempt to read data, possibly discovering that the peer has terminated the stream either cleanly or abruptly - Abort reading of the stream and request closure, resulting in a STOP_SENDING frame (<a href="#frame-stop-sending" class="xref">Section 19.5</a>)</p>
 <h1 id="rfc.section.4">
 <a href="#rfc.section.4">4.</a> <a href="#flow-control" id="flow-control">Flow Control</a>
 </h1>