From c83cd94d6d8281a2d2efaabaa080bf4a96ca8c10 Mon Sep 17 00:00:00 2001 From: Tommy Pauly Date: Thu, 4 Mar 2021 06:46:17 -0800 Subject: [PATCH] Note about pacing Warn against the pathological case of dropping packets due to pacing. Closes #16 --- draft-ietf-quic-datagram.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/draft-ietf-quic-datagram.md b/draft-ietf-quic-datagram.md index 0f68fca..b3096d5 100644 --- a/draft-ietf-quic-datagram.md +++ b/draft-ietf-quic-datagram.md @@ -254,7 +254,10 @@ result, a connection might be unable to send a DATAGRAM frame generated by the application until the congestion controller allows it {{!I-D.ietf-quic-recovery}}. The sender implementation MUST either delay sending the frame until the controller allows it or drop the frame without -sending it (at which point it MAY notify the application). +sending it (at which point it MAY notify the application). Implementations +that use packet pacing SHOULD support delaying the transmission of DATAGRAM +frames for at least the time it takes to send the paced packets allowed by the +congestion controller to avoid dropping frames excessively. Implementations can optionally support allowing the application to specify a sending expiration time, beyond which a congestion-controlled DATAGRAM