Script updating gh-pages from 752f22c. [ci skip]

draft-ietf-quic-transport.html

@@ -2606,11 +2606,14 @@ <h4 id="name-issuing-connection-ids">
 <p id="section-5.1.1-4">An endpoint SHOULD ensure that its peer has a sufficient number of available and
 unused connection IDs.  Endpoints store received connection IDs for future use
 and advertise the number of connection IDs they are willing to store with the
-active_connection_id_limit transport parameter.  An endpoint SHOULD NOT provide
-more connection IDs than the peer's limit.<a href="#section-5.1.1-4" class="pilcrow">¶</a></p>
-<p id="section-5.1.1-5">An endpoint SHOULD supply a new connection ID when it receives a packet with a
-previously unused connection ID or when the peer retires one, unless providing
-the new connection ID would exceed the peer's limit.  An endpoint MAY limit the
+active_connection_id_limit transport parameter.  An endpoint MUST NOT provide
+more connection IDs than the peer's limit.  An endpoint that receives more
+connection IDs than its advertised active_connection_id_limit MUST close the
+connection with an error of type CONNECTION_ID_LIMIT_ERROR.<a href="#section-5.1.1-4" class="pilcrow">¶</a></p>
+<p id="section-5.1.1-5">An endpoint SHOULD supply a new connection ID when the peer retires a connection
+ID. If an endpoint provided fewer connection IDs than the peer's
+active_connection_id_limit, it MAY supply a new connection ID when it receives
+a packet with a previously unused connection ID.  An endpoint MAY limit the
 frequency or the total number of connection IDs issued for each connection to
 avoid the risk of running out of connection IDs; see <a href="#reset-token" class="xref">Section 10.4.2</a>.<a href="#section-5.1.1-5" class="pilcrow">¶</a></p>
 <p id="section-5.1.1-6">An endpoint that initiates migration and requires non-zero-length connection IDs
@@ -2639,10 +2642,12 @@ <h4 id="name-consuming-and-retiring-conn">
 longer plans to use that address.<a href="#section-5.1.2-3" class="pilcrow">¶</a></p>
 <p id="section-5.1.2-4">An endpoint can cause its peer to retire connection IDs by sending a
 NEW_CONNECTION_ID frame with an increased Retire Prior To field.  Upon receipt,
-the peer MUST retire the corresponding connection IDs using RETIRE_CONNECTION_ID
-frames.  Failure to retire the connection IDs within approximately one PTO can
-cause packets to be delayed, lost, or cause the original endpoint to send a
-stateless reset in response to a connection ID it can no longer route correctly.<a href="#section-5.1.2-4" class="pilcrow">¶</a></p>
+the peer MUST first retire the corresponding connection IDs using
+RETIRE_CONNECTION_ID frames and then add the newly provided connection ID to the
+set of active connection IDs.  Failure to retire the connection IDs within
+approximately one PTO can cause packets to be delayed, lost, or cause the
+original endpoint to send a stateless reset in response to a connection ID it
+can no longer route correctly.<a href="#section-5.1.2-4" class="pilcrow">¶</a></p>
 <p id="section-5.1.2-5">An endpoint MAY discard a connection ID for which retirement has been requested
 once an interval of no less than 3 PTO has elapsed since an acknowledgement is
 received for the NEW_CONNECTION_ID frame requesting that retirement.  Until
@@ -6514,8 +6519,14 @@ <h3 id="name-transport-parameter-definit">
           <dt id="section-18.2-6.1">active_connection_id_limit (0x000e):</dt>
           <dd id="section-18.2-6.2">
   The maximum number of connection IDs from the peer that an endpoint is willing
-to store. This value includes only connection IDs sent in NEW_CONNECTION_ID
-frames. If this parameter is absent, a default of 0 is assumed.<a href="#section-18.2-6.2" class="pilcrow">¶</a>
+to store. This value includes the connection ID received during the handshake,
+that received in the preferred_address transport parameter, and those received
+in NEW_CONNECTION_ID frames.
+Unless a zero-length connection ID is being used, the value of the
+active_connection_id_limit parameter MUST be no less than 2. If this
+transport parameter is absent, a default of 2 is assumed.
+When a zero-length connection ID is being used, the active_connection_id_limit
+parameter MUST NOT be sent.<a href="#section-18.2-6.2" class="pilcrow">¶</a>
 </dd>
 </dl>
 <p id="section-18.2-7">If present, transport parameters that set initial flow control limits
@@ -7625,25 +7636,30 @@ <h2 id="name-transport-error-codes">
 an invalid value, was absent even though it is mandatory, was present though
 it is forbidden, or is otherwise in error.<a href="#section-20-3.18" class="pilcrow">¶</a>
 </dd>
-<dt id="section-20-3.19">PROTOCOL_VIOLATION (0xA):</dt>
+<dt id="section-20-3.19">CONNECTION_ID_LIMIT_ERROR (0x9):</dt>
         <dd id="section-20-3.20">
-  An endpoint detected an error with protocol compliance that was not covered by
-more specific error codes.<a href="#section-20-3.20" class="pilcrow">¶</a>
+  The number of connection IDs provided by the peer exceeds the advertised
+active_connection_id_limit.<a href="#section-20-3.20" class="pilcrow">¶</a>
 </dd>
-<dt id="section-20-3.21">INVALID_TOKEN (0xB):</dt>
+<dt id="section-20-3.21">PROTOCOL_VIOLATION (0xA):</dt>
         <dd id="section-20-3.22">
-  A server received a Retry Token in a client Initial that is invalid.<a href="#section-20-3.22" class="pilcrow">¶</a>
+  An endpoint detected an error with protocol compliance that was not covered by
+more specific error codes.<a href="#section-20-3.22" class="pilcrow">¶</a>
 </dd>
-<dt id="section-20-3.23">CRYPTO_BUFFER_EXCEEDED (0xD):</dt>
+<dt id="section-20-3.23">INVALID_TOKEN (0xB):</dt>
         <dd id="section-20-3.24">
-  An endpoint has received more data in CRYPTO frames than it can buffer.<a href="#section-20-3.24" class="pilcrow">¶</a>
+  A server received a Retry Token in a client Initial that is invalid.<a href="#section-20-3.24" class="pilcrow">¶</a>
 </dd>
-<dt id="section-20-3.25">CRYPTO_ERROR (0x1XX):</dt>
+<dt id="section-20-3.25">CRYPTO_BUFFER_EXCEEDED (0xD):</dt>
         <dd id="section-20-3.26">
+  An endpoint has received more data in CRYPTO frames than it can buffer.<a href="#section-20-3.26" class="pilcrow">¶</a>
+</dd>
+<dt id="section-20-3.27">CRYPTO_ERROR (0x1XX):</dt>
+        <dd id="section-20-3.28">
   The cryptographic handshake failed.  A range of 256 values is reserved for
 carrying error codes specific to the cryptographic handshake that is used.
 Codes for errors occurring when TLS is used for the crypto handshake are
-described in Section 4.8 of <span>[<a href="#QUIC-TLS" class="xref">QUIC-TLS</a>]</span>.<a href="#section-20-3.26" class="pilcrow">¶</a>
+described in Section 4.8 of <span>[<a href="#QUIC-TLS" class="xref">QUIC-TLS</a>]</span>.<a href="#section-20-3.28" class="pilcrow">¶</a>
 </dd>
 </dl>
 <p id="section-20-4">See <a href="#iana-error-codes" class="xref">Section 22.3</a> for details of registering new error codes.<a href="#section-20-4" class="pilcrow">¶</a></p>
@@ -8230,6 +8246,14 @@ <h3 id="name-quic-transport-error-codes-">
               <td class="text-left" rowspan="1" colspan="1">Error in transport parameters</td>
               <td class="text-left" rowspan="1" colspan="1">
                 <a href="#error-codes" class="xref">Section 20</a>
+</td>
+            </tr>
+            <tr>
+              <td class="text-left" rowspan="1" colspan="1">0x9</td>
+              <td class="text-left" rowspan="1" colspan="1">CONNECTION_ID_LIMIT_ERROR</td>
+              <td class="text-left" rowspan="1" colspan="1">Too many connection IDs received</td>
+              <td class="text-left" rowspan="1" colspan="1">
+                <a href="#error-codes" class="xref">Section 20</a>
 </td>
             </tr>
             <tr>