From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Cc: Michael Welzl <michawe@ifi.uio.no>
Subject: [Cerowrt-devel] The miserable state of udp-lite, dccp, etc, along the edge
Date: Fri, 20 Mar 2020 12:07:43 -0700 [thread overview]
Message-ID: <CAA93jw6TYCAsB4Edv6um6yCf5ON_-ZArvKXi2rF_8TyWe8OgsQ@mail.gmail.com> (raw)
https://www.researchgate.net/publication/339850966_On_the_Usability_of_Transport_Protocols_other_than_TCP_A_Home_Gateway_and_Internet_Path_Traversal_Study
I note that it was certainly possible to make udp-lite through nat
back when we started cerowrt. I'd added patches to netperf to be able
to
test it, and it's just a kernel module.
I worry a bit about people hitting udp too hard in the post-quic era,
and was very happy when my dns servers mostly started speaking ipv6.
It is very easy on a busy network to run yourself out of udp ports on
your natted firewall, particularly if you run with the default
timeouts.
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729
reply other threads:[~2020-03-20 19:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw6TYCAsB4Edv6um6yCf5ON_-ZArvKXi2rF_8TyWe8OgsQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=michawe@ifi.uio.no \
/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