From c550cb4399b41241f7394d8a2d5728fb87b9f72b Mon Sep 17 00:00:00 2001 From: janaiyengar Date: Thu, 15 Oct 2020 10:39:45 +0900 Subject: [PATCH] editorial --- draft-ietf-quic-transport.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index 891e88ad1d..6185e3f8dd 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -4085,12 +4085,11 @@ A client MUST expand the payload of all UDP datagrams carrying Initial packets to at least the smallest allowed maximum packet size (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. 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 padding -Initial packets helps reduce the amplitude of amplification attacks caused by -server responses toward an unverified client address; see -{{address-validation}}. +datagrams carrying ack-eliciting Initial packets to at least the smallest +allowed maximum packet size (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 responses +toward an unverified client address; see {{address-validation}}. Datagrams containing Initial packets MAY exceed 1200 bytes if the sender believes that the network path and peer both support the size that it chooses.