From: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
To: Stephen Hemminger <stephen@networkplumber.org>,
"David P. Reed" <dpreed@deepplum.com>
Cc: cake@lists.bufferbloat.net, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Two questions re high speed congestion management anddatagram protocols
Date: Wed, 28 Jun 2023 11:43:13 +0200 [thread overview]
Message-ID: <20230628094313.GA18471@unix-ag.uni-kl.de> (raw)
In-Reply-To: <20230627075628.1d8d3b7d@hermes.local>
Hi,
On Tue, Jun 27, 2023 at 07:56:28AM -0700, Stephen Hemminger via Bloat wrote:
> On Mon, 26 Jun 2023 23:41:59 -0400 (EDT)
> "David P. Reed" <dpreed@deepplum.com> wrote:
>
> > Sorry for top posting, but ... Bigger question:
> > Why would DCCP be deprecated by Linux kernel?
> > Who makes that decision? Who argues against it?
>
> No one uses it, and unused protocols are targeted by hackers.
> And there are few tests and no maintainer.
Perhaps the telephony (3GPP) people use it, there even seems
to be some work on extending DCCP with multi-path capabilities:
<https://multipath-dccp.org/>. [That's all I know about this.]
Thanks,
Erik
--
A distributed system is one in which the failure of a computer you didn't
even know existed can render your own computer unusable.
-- Leslie Lamport
next prev parent reply other threads:[~2023-06-28 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 3:41 David P. Reed
2023-06-27 14:56 ` Stephen Hemminger
2023-06-28 9:43 ` Erik Auerswald [this message]
2023-06-27 19:47 ` David Lang
2023-06-27 22:49 ` Stephen Hemminger
2023-06-28 2:03 ` [Bloat] [Cake] " Dave Taht
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=20230628094313.GA18471@unix-ag.uni-kl.de \
--to=auerswal@unix-ag.uni-kl.de \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=dpreed@deepplum.com \
--cc=stephen@networkplumber.org \
/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