Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
Script updating gh-pages from 56b7cfa. [ci skip]
  • Loading branch information
ID Bot committed Feb 4, 2020
1 parent f643b94 commit fdf1727
Show file tree
Hide file tree
Showing 3 changed files with 1,624 additions and 1,624 deletions.
2 changes: 1 addition & 1 deletion draft-ietf-quic-transport.html
Expand Up @@ -4095,7 +4095,7 @@ <h3 id="name-idle-timeout">
<p id="section-10.2-4">An endpoint that sends packets near the end of the idle timeout period
risks having those packets discarded if its peer enters the draining state
before the packets arrive. If a peer could time out within a Probe Timeout
(PTO; see Section 6.2.2 of <span>[<a href="#QUIC-RECOVERY" class="xref">QUIC-RECOVERY</a>]</span>), it is advisable to test for
(PTO; see Section 6.6 of <span>[<a href="#QUIC-RECOVERY" class="xref">QUIC-RECOVERY</a>]</span>), it is advisable to test for
liveness before sending any data that cannot be retried safely. Note that it
is likely that only applications or application protocols will know what
information can be retried.<a href="#section-10.2-4" class="pilcrow">¶</a></p>
Expand Down
24 changes: 12 additions & 12 deletions draft-ietf-quic-transport.txt
Expand Up @@ -3276,11 +3276,10 @@ Internet-Draft QUIC Transport Protocol February 2020
An endpoint that sends packets near the end of the idle timeout
period risks having those packets discarded if its peer enters the
draining state before the packets arrive. If a peer could time out
within a Probe Timeout (PTO; see Section 6.2.2 of [QUIC-RECOVERY]),
it is advisable to test for liveness before sending any data that
cannot be retried safely. Note that it is likely that only
applications or application protocols will know what information can
be retried.
within a Probe Timeout (PTO; see Section 6.6 of [QUIC-RECOVERY]), it
is advisable to test for liveness before sending any data that cannot
be retried safely. Note that it is likely that only applications or
application protocols will know what information can be retried.

10.3. Immediate Close

Expand All @@ -3297,7 +3296,8 @@ Internet-Draft QUIC Transport Protocol February 2020
with another packet containing a CONNECTION_CLOSE frame. Such an
endpoint SHOULD limit the number of packets it generates containing a
CONNECTION_CLOSE frame. For instance, an endpoint could wait for a

progressively increasing number of received packets or amount of time
before responding to a received packet.



Expand All @@ -3306,9 +3306,6 @@ Iyengar & Thomson Expires 7 August 2020 [Page 59]
Internet-Draft QUIC Transport Protocol February 2020


progressively increasing number of received packets or amount of time
before responding to a received packet.

An endpoint is allowed to drop the packet protection keys when
entering the closing period (Section 10.1) and send a packet
containing a CONNECTION_CLOSE in response to any UDP datagram that is
Expand Down Expand Up @@ -3354,6 +3351,9 @@ Internet-Draft QUIC Transport Protocol February 2020
will process the frame. Generally, this means sending the frame in a
packet with the highest level of packet protection to avoid the
packet being discarded. After the handshake is confirmed (see
Section 4.1.2 of [QUIC-TLS]), an endpoint MUST send any
CONNECTION_CLOSE frames in a 1-RTT packet. However, prior to
confirming the handshake, it is possible that more advanced packet



Expand All @@ -3362,9 +3362,6 @@ Iyengar & Thomson Expires 7 August 2020 [Page 60]
Internet-Draft QUIC Transport Protocol February 2020


Section 4.1.2 of [QUIC-TLS]), an endpoint MUST send any
CONNECTION_CLOSE frames in a 1-RTT packet. However, prior to
confirming the handshake, it is possible that more advanced packet
protection keys are not available to the peer, so the frame MAY be
replicated in a packet that uses a lower packet protection level.

Expand Down Expand Up @@ -3413,6 +3410,9 @@ Internet-Draft QUIC Transport Protocol February 2020






Iyengar & Thomson Expires 7 August 2020 [Page 61]

Internet-Draft QUIC Transport Protocol February 2020
Expand Down

0 comments on commit fdf1727

Please sign in to comment.