Script updating gh-pages from b977de2. [ci skip]

draft-ietf-quic-qpack.html

@@ -1112,9 +1112,9 @@ <h1 id="rfc.section.5">
 
 <dl>
 <dt>SETTINGS_QPACK_MAX_TABLE_CAPACITY (0x1):</dt>
-<dd style="margin-left: 8">An integer with a maximum value of 2^30 - 1.  The default value is zero bytes.  See <a href="#table-dynamic" class="xref">Section 3.2</a> for usage.  This is the equivalent of the SETTINGS_HEADER_TABLE_SIZE from HTTP/2.</dd>
+<dd style="margin-left: 8">The default value is zero.  See <a href="#table-dynamic" class="xref">Section 3.2</a> for usage.  This is the equivalent of the SETTINGS_HEADER_TABLE_SIZE from HTTP/2.</dd>
 <dt>SETTINGS_QPACK_BLOCKED_STREAMS (0x7):</dt>
-<dd style="margin-left: 8">An integer with a maximum value of 2^16 - 1.  The default value is zero.  See <a href="#overview-hol-avoidance" class="xref">Section 2.1.3</a>.</dd>
+<dd style="margin-left: 8">The default value is zero.  See <a href="#overview-hol-avoidance" class="xref">Section 2.1.3</a>.</dd>
 </dl>
 <h1 id="rfc.section.6">
 <a href="#rfc.section.6">6.</a> <a href="#error-handling" id="error-handling">Error Handling</a>

draft-ietf-quic-qpack.txt

@@ -1383,13 +1383,13 @@ Internet-Draft                    QPACK                        June 2019
    QPACK defines two settings which are included in the HTTP/3 SETTINGS
    frame.
 
-   SETTINGS_QPACK_MAX_TABLE_CAPACITY (0x1):  An integer with a maximum
-      value of 2^30 - 1.  The default value is zero bytes.  See
-      Section 3.2 for usage.  This is the equivalent of the
+   SETTINGS_QPACK_MAX_TABLE_CAPACITY (0x1):  The default value is zero.
+      See Section 3.2 for usage.  This is the equivalent of the
       SETTINGS_HEADER_TABLE_SIZE from HTTP/2.
 
-   SETTINGS_QPACK_BLOCKED_STREAMS (0x7):  An integer with a maximum
-      value of 2^16 - 1.  The default value is zero.  See Section 2.1.3.
+   SETTINGS_QPACK_BLOCKED_STREAMS (0x7):  The default value is zero.
+      See Section 2.1.3.
+
 
 
 

draft-ietf-quic-transport.html

@@ -2603,8 +2603,8 @@ <h3 id="rfc.section.17.3.1">
 </h3>
 <p id="rfc.section.17.3.1.p.1">The latency spin bit enables passive latency monitoring from observation points on the network path throughout the duration of a connection. The spin bit is only present in the short packet header, since it is possible to measure the initial RTT of a connection by observing the handshake. Therefore, the spin bit is available after version negotiation and connection establishment are completed. On-path measurement and use of the latency spin bit is further discussed in <a href="#QUIC-MANAGEABILITY" class="xref">[QUIC-MANAGEABILITY]</a>.</p>
 <p id="rfc.section.17.3.1.p.2">The spin bit is an OPTIONAL feature of QUIC. A QUIC stack that chooses to support the spin bit MUST implement it as specified in this section.</p>
-<p id="rfc.section.17.3.1.p.3">Each endpoint unilaterally decides if the spin bit is enabled or disabled for a connection. Implementations MUST allow administrators of clients and servers to disable the spin bit either globally or on a per-connection basis. Even when the spin bit is not disabled by the administrator, implementations MUST disable the spin bit for a given connection with a certain likelihood. The random selection process SHOULD be designed such that on average the spin bit is disabled for at least one eighth of connections. The selection process performed at the beginning of the connection SHOULD be applied for all paths used by the connection.</p>
-<p id="rfc.section.17.3.1.p.4">In case multiple connections share the same five-tuple, that is, have the same source and destination IP address and UDP ports, endpoints should try to co-ordinate across all connections to ensure a clear signal to any on-path measurement points.</p>
+<p id="rfc.section.17.3.1.p.3">Each endpoint unilaterally decides if the spin bit is enabled or disabled for a connection. Implementations MUST allow administrators of clients and servers to disable the spin bit either globally or on a per-connection basis. Even when the spin bit is not disabled by the administrator, implementations MUST disable the spin bit for a given connection with a certain likelihood. The random selection process SHOULD be designed such that on average the spin bit is disabled for at least one eighth of network paths. The selection process performed at the beginning of the connection SHOULD be applied for all paths used by the connection.</p>
+<p id="rfc.section.17.3.1.p.4">In case multiple connections share the same network path, as determined by having the same source and destination IP address and UDP ports, endpoints should try to co-ordinate across all connections to ensure a clear signal to any on-path measurement points.</p>
 <p id="rfc.section.17.3.1.p.5">When the spin bit is disabled, endpoints MAY set the spin bit to any value, and MUST ignore any incoming value. It is RECOMMENDED that endpoints set the spin bit to a random value either chosen independently for each packet or chosen independently for each connection ID.</p>
 <p id="rfc.section.17.3.1.p.6">If the spin bit is enabled for the connection, the endpoint maintains a spin value and sets the spin bit in the short header to the currently stored value when a packet with a short header is sent out. The spin value is initialized to 0 in the endpoint at connection start.  Each endpoint also remembers the highest packet number seen from its peer on the connection.</p>
 <p id="rfc.section.17.3.1.p.7">When a server receives a short header packet that increments the highest packet number seen by the server from the client, it sets the spin value to be equal to the spin bit in the received packet.</p>

draft-ietf-quic-transport.txt

@@ -5277,14 +5277,14 @@ Internet-Draft           QUIC Transport Protocol               June 2019
    the administrator, implementations MUST disable the spin bit for a
    given connection with a certain likelihood.  The random selection
    process SHOULD be designed such that on average the spin bit is
-   disabled for at least one eighth of connections.  The selection
+   disabled for at least one eighth of network paths.  The selection
    process performed at the beginning of the connection SHOULD be
    applied for all paths used by the connection.
 
-   In case multiple connections share the same five-tuple, that is, have
-   the same source and destination IP address and UDP ports, endpoints
-   should try to co-ordinate across all connections to ensure a clear
-   signal to any on-path measurement points.
+   In case multiple connections share the same network path, as
+   determined by having the same source and destination IP address and
+   UDP ports, endpoints should try to co-ordinate across all connections
+   to ensure a clear signal to any on-path measurement points.
 
    When the spin bit is disabled, endpoints MAY set the spin bit to any
    value, and MUST ignore any incoming value.  It is RECOMMENDED that