From 54a3d93d983d4c55ca2cf1a52c63e92521c0f9d9 Mon Sep 17 00:00:00 2001 From: ianswett Date: Wed, 24 Feb 2021 09:13:31 -0500 Subject: [PATCH] 1-RTT, not ApplicationData --- draft-ietf-quic-recovery.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/draft-ietf-quic-recovery.md b/draft-ietf-quic-recovery.md index c48ecafa9d..b364996e7d 100644 --- a/draft-ietf-quic-recovery.md +++ b/draft-ietf-quic-recovery.md @@ -666,9 +666,9 @@ sent, the server's PTO timer MUST NOT be armed until datagrams have been received from the client, because packets sent on PTO count against the anti-amplification limit. The server's PTO timer could be re-armed to a time in the past after being amplification limited, in which case it is executed -immediately. Doing so avoids sending new packets in ApplicationData prior to -packets critical to the completion of the handshake. Note that the server -could fail to validate the client's address even if 0-RTT is accepted. +immediately. Doing so avoids sending new 1-RTT packets prior to packets +critical to the completion of the handshake. Note that the server could fail +to validate the client's address even if 0-RTT is accepted. Since the server could be blocked until more datagrams are received from the client, it is the client's responsibility to send packets to unblock the server