From 70dcd4af391f969c04924aeec4ac0b2ebaa0eaaf Mon Sep 17 00:00:00 2001 From: Jana Iyengar Date: Tue, 3 Jul 2018 16:38:16 -0700 Subject: [PATCH] Add text to handle PADDING and CC --- draft-ietf-quic-transport.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index 904ed84ce2..4afa2fdda7 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -3489,6 +3489,14 @@ even if there are packet gaps which precede the received packet. The endpoint MUST acknowledge packets containing only ACK or PADDING frames in the next ACK frame that it sends. +While PADDING frames do not elicit an ACK frame from a receiver, they are +considered to be in flight for congestion control purposes +{{QUIC-RECOVERY}}. Sending only PADDING frames might cause the sender to become +limited by the congestion controller (as described in {{QUIC-RECOVERY}}) with no +acknowledgments forthcoming from the receiver. Therefore, a sender should ensure +that other frames are sent in addition to PADDING frames to elicit +acknowledgments from the receiver. + Strategies and implications of the frequency of generating acknowledgments are discussed in more detail in {{QUIC-RECOVERY}}.