From f77bd1e5395bbac2bd1fe2ab575f1beac4c8bf32 Mon Sep 17 00:00:00 2001 From: ianswett Date: Thu, 19 Sep 2019 17:30:24 -0400 Subject: [PATCH 1/3] Clients send datagrams with 1200 byte payloads I was a bit unsure. I think this is clearer. --- 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 eefa38afd3..01799740d4 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -1592,10 +1592,10 @@ 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 ensure that UDP datagrams containing only Initial packets are sized -to at least 1200 bytes, adding padding to packets in the datagram as necessary. -Sending padded datagrams ensures that the server is not overly constrained by -the amplification restriction. +Clients MUST ensure that UDP datagrams containing only Initial packets have +payloads of at least 1200 bytes, adding padding to packets in the datagram as +necessary. 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 3801ebda3af7418505f1aed87138ae72a3178829 Mon Sep 17 00:00:00 2001 From: ianswett Date: Fri, 20 Sep 2019 08:48:32 -0400 Subject: [PATCH 2/3] More UDP --- 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 01799740d4..18904317da 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -1592,7 +1592,7 @@ 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 ensure that UDP datagrams containing only Initial packets have +Clients MUST ensure that UDP datagrams containing only Initial packets have UDP payloads of at least 1200 bytes, adding padding to packets in the datagram as necessary. Sending padded datagrams ensures that the server is not overly constrained by the amplification restriction. From 6cfcbe26385f17072ccd330aea619f65bf3bdcb4 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Sat, 21 Sep 2019 15:03:28 +1000 Subject: [PATCH 3/3] Closes #3053 too --- 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 18904317da..26fec9c109 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -1592,7 +1592,7 @@ 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 ensure that UDP datagrams containing only Initial packets have UDP +Clients MUST ensure that UDP datagrams containing Initial packets have UDP payloads of at least 1200 bytes, adding padding to packets in the datagram as necessary. Sending padded datagrams ensures that the server is not overly constrained by the amplification restriction.