Update draft-ietf-quic-transport.md

quicwg · Oct 2, 2018 · ea331de · ea331de
1 parent 3ccf315
commit ea331de
Showing 1 changed file with 5 additions and 5 deletions.
diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md
@@ -882,11 +882,11 @@ a NEW_TOKEN frame) or by processing any message from the client encrypted using
 the Handshake keys.  This limit exists to mitigate amplification attacks.
 
 In order to prevent this limit causing a handshake deadlock, the client SHOULD
-send a packet as large as the Initial containing only PADDING if it has no
-other data to send and does not yet have the Handshake keys.  If the client
-has no data to send and the Handshake keys are available, it SHOULD send a
-packet with a single byte of padding.  Details on when to send these PADDING
-packets are in {{QUIC-RECOVERY}}.
+always send a packet upon a handshake timeout, as described in
+{{QUIC-RECOVERY}}.  If the client has no data to retransmit and does not have
+Handshake keys, it should send a packet as large as the Initial containing
+only PADDING.  If the client has Handshake keys, it SHOULD send a packet
+containing only PADDING.
 
 The payload of this packet contains CRYPTO frames and could contain PADDING, or
 ACK frames. Handshake packets MAY contain CONNECTION_CLOSE or APPLICATION_CLOSE