From: Stephen Hemminger <stephen@networkplumber.org>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: "Dave Taht via Cake" <cake@lists.bufferbloat.net>,
bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Cake] Two questions re high speed congestionmanagement anddatagram protocols
Date: Mon, 10 Jul 2023 13:35:40 -0700 [thread overview]
Message-ID: <20230710133540.1cbe20bd@hermes.local> (raw)
In-Reply-To: <1687962752.39077378@mobile.rackspace.com>
On Wed, 28 Jun 2023 10:32:32 -0400 (EDT)
"David P. Reed" <dpreed@deepplum.com> wrote:
> How to find a kernel maintainer to care about DCCP, seems to be the question for Linux.
> I am tempted... Not to get involved with IETF "barriers" (what a mess, given the folks in IETF who resisted in AQM, I wouldn't last a minute), but to keep DCCP support alive.
> The barrier here is getting accepted as a Linux maintainer, which is a different issue entirely, looking at my last two experiences with submitting simple bug fixes to the kernel, which were nightmares. I don't have the commitment to become accepted as a maintainer.
> But it seems good to maintain DCCP, despite its lack of popularity as an IETF standard. It does deal with CC in a way that simplifies use of UDP for serious work.
Interesting that there is an out of tree DCCP, complete with likely GPL license violation.
https://github.com/telekom/mp-dccp
next prev parent reply other threads:[~2023-07-10 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 14:32 David P. Reed
2023-06-28 21:53 ` Toke Høiland-Jørgensen
2023-07-10 20:35 ` Stephen Hemminger [this message]
2023-07-10 21:27 ` Sebastian Moeller
2023-07-10 22:55 ` Stephen Hemminger
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=20230710133540.1cbe20bd@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