[quicwg/base-drafts] Limit retransmission of closing packet (#1905)

Martin Thomson <notifications@github.com> Wed, 24 October 2018 23:19 UTC

Date: Wed, 24 Oct 2018 16:19:52 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab9e1f7d61b1c6901ec477c003a30490769cad4c0892cf0000000117e8c01892a169ce16466c4c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1905@github.com>
Subject: [quicwg/base-drafts] Limit retransmission of closing packet (#1905)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bd0fe187af7a_7d203ff4bc2d45c414495f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/bNPV70q4cblT5LjBGjDpDGZ_lOE>

@mikkelfj observes that we permit rate limiting of connection close frames, but they might be used to create an amplification attack if the closing endpoint is naive in its handling.  The fix is easy - the endpoint needs to remember a validated address for its peer along with the closing packet.  Packets from other remote addresses need to be dropped or only responded to if the size of the incoming packet is > 1/3 of the closing packet.  In most cases, this won't change anything.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/1905

[quicwg/base-drafts] Limit retransmission of clos… Martin Thomson
Re: [quicwg/base-drafts] Limit retransmission of … Martin Thomson