From: Stephen Hemminger <stephen@networkplumber.org>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: bloat@lists.bufferbloat.net, cake@lists.bufferbloat.net
Subject: Re: [Bloat] Two questions re high speed congestion management anddatagram protocols
Date: Tue, 27 Jun 2023 07:56:28 -0700 [thread overview]
Message-ID: <20230627075628.1d8d3b7d@hermes.local> (raw)
In-Reply-To: <1687837319.447910185@mobile.rackspace.com>
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.
next prev parent reply other threads:[~2023-06-27 14:56 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 [this message]
2023-06-28 9:43 ` Erik Auerswald
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=20230627075628.1d8d3b7d@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