From 79c731c4d580296d1a3e38e42733c7b52d88b779 Mon Sep 17 00:00:00 2001 From: Jana Iyengar Date: Wed, 13 Mar 2019 08:54:49 -0700 Subject: [PATCH 1/3] Rephrase size requirement for Initial packets --- draft-ietf-quic-transport.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index 86c46c0fbe..8b4844869a 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -1468,10 +1468,11 @@ magnitude of any amplification attack that can be mounted using spoofed source addresses. In determining this limit, servers only count the size of successfully processed packets. -Clients MUST pad UDP datagrams that contain only Initial packets to at least -1200 bytes. Once a client has received an acknowledgment for a Handshake packet -it MAY send smaller datagrams. Sending padded datagrams ensures that the server -is not overly constrained by the amplification restriction. +Clients MUST ensure that UDP datagrams containing Initial packets are sized to +at least 1200 bytes, padding packets in the datagram if necessary. Once a +client has received an acknowledgment for a Handshake packet it MAY send smaller +datagrams. Sending padded datagrams ensures that the server is not overly +constrained by the amplification restriction. Packet loss, in particular loss of a Handshake packet from the server, can cause a situation in which the server cannot send when the client has no data to send From a69e90d091a8543392d5f5452c4dd31919b06fe6 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Fri, 15 Mar 2019 13:10:33 -0700 Subject: [PATCH 2/3] Update draft-ietf-quic-transport.md Co-Authored-By: janaiyengar --- draft-ietf-quic-transport.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index 8b4844869a..1eedf298e8 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -1469,7 +1469,7 @@ addresses. In determining this limit, servers only count the size of successfully processed packets. Clients MUST ensure that UDP datagrams containing Initial packets are sized to -at least 1200 bytes, padding packets in the datagram if necessary. Once a +at least 1200 bytes, adding padding to packets in the datagram as necessary. Once a client has received an acknowledgment for a Handshake packet it MAY send smaller datagrams. Sending padded datagrams ensures that the server is not overly constrained by the amplification restriction. From 50011f231f3bb9094f85cc5953c05c64883759d4 Mon Sep 17 00:00:00 2001 From: Jana Iyengar Date: Fri, 15 Mar 2019 13:12:25 -0700 Subject: [PATCH 3/3] reflow --- 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 1eedf298e8..bf5a5a8ac2 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -1469,10 +1469,10 @@ addresses. In determining this limit, servers only count the size of successfully processed packets. Clients MUST ensure that UDP datagrams containing Initial packets are sized to -at least 1200 bytes, adding padding to packets in the datagram as necessary. Once a -client has received an acknowledgment for a Handshake packet it MAY send smaller -datagrams. Sending padded datagrams ensures that the server is not overly -constrained by the amplification restriction. +at least 1200 bytes, adding padding to packets in the datagram as necessary. +Once a client has received an acknowledgment for a Handshake packet it MAY send +smaller datagrams. Sending padded datagrams ensures that the server is not +overly constrained by the amplification restriction. Packet loss, in particular loss of a Handshake packet from the server, can cause a situation in which the server cannot send when the client has no data to send