Merge pull request #18 from quicwg/tfpauly-patch-1

Note about pacing

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