General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Educate colleges on tcp vs udp
Date: Sun, 23 May 2021 23:42:22 +0200	[thread overview]
Message-ID: <1a730631-6cc4-8f5d-fa1a-92f9d71ef606@unix-ag.uni-kl.de> (raw)
In-Reply-To: <A9AA2031-68FA-4CF4-B198-5A798802719C@gmail.com>

Hi,

On 23.05.21 23:02, Jonathan Morton wrote:
>> On 23 May, 2021, at 9:47 pm, Erik Auerswald <auerswal@unix-ag.uni-kl.de> wrote:
>>
>> As an additional point to consider when pondering whether to
>> use TCP or UDP:
>>
>> To mitigate that simple request-response protocols using UDP
>> lend themselves to being abused for reflection and amplification…
> 
> I suspect such considerations are well beyond the level of education requested here.  I think what was being asked for was "how do these protocols work, and why do they work that way, in language suitable for people working in a different field", rather than "which one should I use for X application".

Yes, I do think so as well.

Nevertheless, I want to raise awareness of the risks
inherent in building protocols based on UDP.

As an optimist, I do believe that it may be possible
that in future less new protocols are created that
are useful for amplification attacks, by often raising
awareness of the risks and how to mitigate them.

I would have preferred if the current DDoS attacks using
STUN could have been avoided, by allowing standard
compliant STUN implementations to have an amplification
factor < 1, or at least ≤ 1, and by building response
rate limits into the standard.

(See, e.g., 
https://mail.jabber.org/pipermail/operators/2021-April/003130.html)

Thanks,
Erik

  reply	other threads:[~2021-05-23 21:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21  6:01 Taraldsen Erik
2021-05-23 10:23 ` Jonathan Morton
2021-05-23 18:47   ` Erik Auerswald
2021-05-23 21:02     ` Jonathan Morton
2021-05-23 21:42       ` Erik Auerswald [this message]
2021-05-26 22:44     ` Mark Andrews
2021-05-27  3:11       ` Erik Auerswald
2021-05-24 18:51 ` Erik Auerswald
2021-05-25  6:38   ` Taraldsen Erik
2021-05-26 18:09     ` Dave Taht
2021-05-27  6:32       ` Taraldsen Erik
2021-05-27  7:42 Hal Murray
2021-05-27 12:15 ` Jonathan Morton
2021-05-27 22:17 ` Kenneth Porter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1a730631-6cc4-8f5d-fa1a-92f9d71ef606@unix-ag.uni-kl.de \
    --to=auerswal@unix-ag.uni-kl.de \
    --cc=bloat@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox