From: Stephen Hemminger <stephen@networkplumber.org>
To: "David P. Reed via Bloat" <bloat@lists.bufferbloat.net>
Cc: "David P. Reed" <dpreed@deepplum.com>,
"Cake List" <cake@lists.bufferbloat.net>
Subject: Re: [Bloat] Two questions re high speed congestion management and datagram protocols
Date: Sun, 25 Jun 2023 11:51:13 -0700 [thread overview]
Message-ID: <20230625115113.2291f7d6@hermes.local> (raw)
In-Reply-To: <1687632112.01524513@apps.rackspace.com>
On Sat, 24 Jun 2023 14:41:52 -0400 (EDT)
"David P. Reed via Bloat" <bloat@lists.bufferbloat.net> wrote:
> I also was looking back to DCCP as a useful way to get a UDP that handled congestion without engaging the higher layers, and preserving the other flexibility of UDP.
DCCP never got widely used, and Linux is on the path of deprecating it.
prev parent reply other threads:[~2023-06-25 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 18:41 David P. Reed
2023-06-25 18:51 ` Stephen Hemminger [this message]
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=20230625115113.2291f7d6@hermes.local \
--to=stephen@networkplumber.org \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=dpreed@deepplum.com \
/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