From 3a56ee49f91a803ae694bf177b8a1d4576254b8b Mon Sep 17 00:00:00 2001 From: Jana Iyengar Date: Thu, 15 Oct 2020 16:44:50 -0700 Subject: [PATCH] datagram not packet --- draft-ietf-quic-transport.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index 6cb3784962..1b85be27ed 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -4089,11 +4089,11 @@ fragmentation on the path. ## Initial Datagram Size {#initial-size} A client MUST expand the payload of all UDP datagrams carrying Initial packets -to at least the smallest allowed maximum datagram size (1200 bytes) by adding +to at least the smallest allowed maximum datagram size of 1200 bytes by adding PADDING frames to the Initial packet or by coalescing the Initial packet; see {{packet-coalesce}}. Similarly, a server MUST expand the payload of all UDP datagrams carrying ack-eliciting Initial packets to at least the smallest -allowed maximum packet size (1200 bytes). Sending UDP datagrams of this size +allowed maximum datagram size of 1200 bytes. Sending UDP datagrams of this size ensures that the network path supports a reasonable Path Maximum Transmission Unit (PMTU), in both directions. Additionally, a client that expands Initial packets helps reduce the amplitude of amplification attacks caused by server