Skip to content

Commit

Permalink
Script updating gh-pages from b660d2b. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Apr 30, 2019
1 parent eb19f89 commit dfd3156
Show file tree
Hide file tree
Showing 3 changed files with 1,776 additions and 1,776 deletions.
2 changes: 1 addition & 1 deletion draft-ietf-quic-transport.html
Expand Up @@ -1807,7 +1807,7 @@ <h2 id="rfc.section.10.4">
<p class="figure">Figure 6: Stateless Reset Packet</p>
<p id="rfc.section.10.4.p.4">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.5">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.6">To entities other than its intended recipient, a stateless reset will be appear to be a packet with a short header. For the packet to appear as valid, the Unpredictable Bits field needs to include at least 182 bits of data (or 23 bytes, less the two fixed bits). This is intended to allow for a Destination Connection ID of the maximum length permitted, with a minimal packet number, and payload. 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.6">To entities other than its intended recipient, a stateless reset will appear to be a packet with a short header. For the packet to appear as valid, the Unpredictable Bits field needs to include at least 182 bits of data (or 23 bytes, less the two fixed bits). This is intended to allow for a Destination Connection ID of the maximum length permitted, with a minimal packet number, and payload. 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.7">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.</p>
<p id="rfc.section.10.4.p.8">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>
<p id="rfc.section.10.4.p.9">An endpoint MAY send a stateless reset in response to a packet with a long header. Sending a stateless reset is not effective prior to the stateless reset token being available to a peer. In this QUIC version, packets with a long header are only used during connection establishment. Because the stateless reset token is not available until connection establishment is complete or near completion, ignoring an unknown packet with a long header might be as effective than sending a stateless reset.</p>
Expand Down
8 changes: 4 additions & 4 deletions draft-ietf-quic-transport.txt
Expand Up @@ -3109,10 +3109,10 @@ Internet-Draft QUIC Transport Protocol April 2019
Stateless Reset Token.

To entities other than its intended recipient, a stateless reset will
be appear to be a packet with a short header. For the packet to
appear as valid, the Unpredictable Bits field needs to include at
least 182 bits of data (or 23 bytes, less the two fixed bits). This
is intended to allow for a Destination Connection ID of the maximum
appear to be a packet with a short header. For the packet to appear
as valid, the Unpredictable Bits field needs to include at least 182
bits of data (or 23 bytes, less the two fixed bits). This is
intended to allow for a Destination Connection ID of the maximum
length permitted, with a minimal packet number, and payload. The
Stateless Reset Token corresponds to the minimum expansion of the
packet protection AEAD. More unpredictable bytes might be necessary
Expand Down

0 comments on commit dfd3156

Please sign in to comment.