General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Stephen Hemminger <stephen@networkplumber.org>,
	Stephen Hemminger via Bloat <bloat@lists.bufferbloat.net>,
	"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 23:27:46 +0200	[thread overview]
Message-ID: <A0010D20-BCC6-41EC-9517-685012F042EE@gmx.de> (raw)
In-Reply-To: <20230710133540.1cbe20bd@hermes.local>

[-- Attachment #1: Type: text/plain, Size: 1615 bytes --]

For what it is worth, the tsv working group is considering whether to process mp-dccp on the standards track, but then the IETF seems not to care too deeply about open-source licence compliance. Or recent kernel implementations or implementations that have a realistic path towards mainline inclusion... but I digress.

Regards
        Sebastian





On 10 July 2023 22:35:40 CEST, Stephen Hemminger via Bloat <bloat@lists.bufferbloat.net> wrote:
>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
>_______________________________________________
>Bloat mailing list
>Bloat@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/bloat

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 2252 bytes --]

  reply	other threads:[~2023-07-10 21:27 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
2023-07-10 21:27   ` Sebastian Moeller [this message]
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=A0010D20-BCC6-41EC-9517-685012F042EE@gmx.de \
    --to=moeller0@gmx.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