Script updating gh-pages from 3644a03. [ci skip]

ianswett-smaller-stateless-resets/draft-ietf-quic-transport.html

@@ -1823,7 +1823,7 @@ <h2 id="rfc.section.10.4">
 <p class="figure">Figure 6: Stateless Reset Packet</p>
 <p id="rfc.section.10.4.p.5">This design ensures that a stateless reset packet is - to the extent possible - indistinguishable from a regular packet with a short header.</p>
 <p id="rfc.section.10.4.p.6">A stateless reset uses an entire UDP datagram, starting with the first two bits of the packet header.  The remainder of the first byte and an arbitrary number of bytes following it that are set to unpredictable values.  The last 16 bytes of the datagram contain a Stateless Reset Token.</p>
-<p id="rfc.section.10.4.p.7">To entities other than its intended recipient, a stateless reset will appear to be a packet with a short header.  For the stateless reset to appear as a valid QUIC packet and be smaller than the received packet, the Unpredictable Bits field needs to include at least 46 bits of data (or 6 bytes, less the two fixed bits), because packets that are smaller than 21 bytes are never valid.  To ensure the stateless reset packet is not smaller than other packets received on the connection, the an endpoint SHOULD also ensure the total packet length is at least the minimum chosen CID length + 19 bytes.  19 bytes allows for 1 type byte, 1 data byte, the 16 byte authentication tag byte, and the one extra byte lost when the peer sends a smaller stateless reset than the packet it receives.</p>
+<p id="rfc.section.10.4.p.7">To entities other than its intended recipient, a stateless reset will appear to be a packet with a short header.  For the stateless reset to appear as a valid QUIC packet and be smaller than the received packet, the Unpredictable Bits field needs to include at least 48 bits of data (or 6 bytes, less the two fixed bits).  To ensure the stateless reset packet is not smaller than other packets received on the connection, an endpoint SHOULD also ensure the total packet length is at least the minimum chosen CID length + 22 bytes.  22 bytes allows for 1 type byte, 4 packet number and data bytes, the 16 byte authentication tag, and the one extra byte to allow the peer to send a smaller stateless reset than the packet it receives.</p>
 <p id="rfc.section.10.4.p.8">The Stateless Reset Token corresponds to the minimum expansion of the packet protection AEAD.  More unpredictable bytes might be necessary if the endpoint could have negotiated a packet protection scheme with a larger minimum AEAD expansion.</p>
 <p id="rfc.section.10.4.p.9">An endpoint SHOULD NOT send a stateless reset that is significantly larger than the packet it receives.  Endpoints MUST discard packets that are too small to be valid QUIC packets.  With the set of AEAD functions defined in <a href="#QUIC-TLS" class="xref">[QUIC-TLS]</a>, packets that are smaller than 21 bytes are never valid.  When a packet is b</p>
 <p id="rfc.section.10.4.p.10">Endpoints MUST send stateless reset packets formatted as a packet with a short header.  However, endpoints MUST treat any packet ending in a valid stateless reset token as a stateless reset, as other QUIC versions might allow the use of a long header.</p>

ianswett-smaller-stateless-resets/draft-ietf-quic-transport.txt

@@ -3179,13 +3179,13 @@ Internet-Draft           QUIC Transport Protocol               July 2019
    To entities other than its intended recipient, a stateless reset will
    appear to be a packet with a short header.  For the stateless reset
    to appear as a valid QUIC packet and be smaller than the received
-   packet, the Unpredictable Bits field needs to include at least 46
-   bits of data (or 6 bytes, less the two fixed bits), because packets
-   that are smaller than 21 bytes are never valid.  To ensure the
+   packet, the Unpredictable Bits field needs to include at least 48
+   bits of data (or 6 bytes, less the two fixed bits).  To ensure the
    stateless reset packet is not smaller than other packets received on
-   the connection, the an endpoint SHOULD also ensure the total packet
-   length is at least the minimum chosen CID length + 19 bytes.  19
-   bytes allows for 1 type byte, 1 data byte, the 16 byte authentication
+   the connection, an endpoint SHOULD also ensure the total packet
+   length is at least the minimum chosen CID length + 22 bytes.  22
+   bytes allows for 1 type byte, 4 packet number and data bytes, the 16
+
 
 
 
@@ -3194,8 +3194,8 @@ Iyengar & Thomson       Expires January 24, 2020               [Page 57]
 Internet-Draft           QUIC Transport Protocol               July 2019
 
 
-   tag byte, and the one extra byte lost when the peer sends a smaller
-   stateless reset than the packet it receives.
+   byte authentication tag, and the one extra byte to allow the peer to
+   send a smaller stateless reset than the packet it receives.
 
    The Stateless Reset Token corresponds to the minimum expansion of the
    packet protection AEAD.  More unpredictable bytes might be necessary