From 56569b9dcce3788d24b3dfc6576603f6ffca1da9 Mon Sep 17 00:00:00 2001 From: Kazuho Oku Date: Fri, 9 Oct 2020 08:58:12 +0900 Subject: [PATCH] wordwrap --- draft-ietf-quic-transport.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index 4098dae418..85dce60b14 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -1943,10 +1943,10 @@ the client during connection establishment with a Retry packet (see {{validate-retry}}) or in a previous connection using the NEW_TOKEN frame (see {{validate-future}}). -Until the client address is validated, a server SHOULD ensure that all -packets it sends, with the exception of Retry packets, have a UDP payload -size of at least 1200 bytes. Doing so ensures that the handshake progresses -only if the path is capable of handling QUIC traffic; see {{packet-size}}. +Until the client address is validated, a server SHOULD ensure that all packets +it sends, with the exception of Retry packets, have a UDP payload size of at +least 1200 bytes. Doing so ensures that the handshake progresses only if the +path is capable of handling QUIC traffic; see {{packet-size}}. In addition to sending limits imposed prior to address validation, servers are also constrained in what they can send by the limits set by the congestion