From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <david@lang.hm>
Received: from mail.lang.hm (unknown [66.167.227.145])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by lists.bufferbloat.net (Postfix) with ESMTPS id 3C29C3B29D;
 Tue, 27 Jun 2023 15:47:02 -0400 (EDT)
Received: from dlang-mobile (unknown [10.2.2.69])
 by mail.lang.hm (Postfix) with ESMTP id 32B91199CF8;
 Tue, 27 Jun 2023 12:47:01 -0700 (PDT)
Date: Tue, 27 Jun 2023 12:47:01 -0700 (PDT)
From: David Lang <david@lang.hm>
To: "David P. Reed" <dpreed@deepplum.com>
cc: stephen@networkplumber.org, cake@lists.bufferbloat.net, 
 bloat@lists.bufferbloat.net
In-Reply-To: <1687837319.447910185@mobile.rackspace.com>
Message-ID: <4np8q9q1-on99-rn94-5s1p-55643oo11037@ynat.uz>
References: <1687837319.447910185@mobile.rackspace.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Subject: Re: [Bloat] Two questions re high speed congestion management
 anddatagram protocols
X-BeenThere: bloat@lists.bufferbloat.net
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: General list for discussing Bufferbloat <bloat.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/bloat>,
 <mailto:bloat-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/bloat>
List-Post: <mailto:bloat@lists.bufferbloat.net>
List-Help: <mailto:bloat-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/bloat>,
 <mailto:bloat-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Tue, 27 Jun 2023 19:47:02 -0000

On Mon, 26 Jun 2023, David P. Reed via Bloat wrote:

> Sorry for top posting, but ... Bigger question:
> Why would DCCP be deprecated by Linux kernel?
> Who makes that decision? Who argues against it?

Linus or the networking maintaners make the decision.

Usually things get pulled from the kernel because there are updates that need to 
be made to the code (to match changes elsewhere in the kernel or because of 
security issues) and there isn't a maintainer who works on the code in a 
resonable time. This means that the maintainers for the general code area (in 
this case networking maintainers) will need to do extra work in an area they 
aren't that interested in (and, especially in the case of hardware, may not have 
the ability to test). They do some of it, especially if it's commonly used, but 
eventually either another maintainer steps up, or it goes away

David Lang