From: Stephen Hemminger <stephen@networkplumber.org>
To: "Maglione, Gregorio" <Gregorio.Maglione@city.ac.uk>
Cc: Paolo Abeni <pabeni@redhat.com>,
Kuniyuki Iwashima <kuniyu@amazon.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Florian Westphal <fw@strlen.de>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Rakocevic, Veselin" <Veselin.Rakocevic.1@city.ac.uk>,
"Markus.Amend@telekom.de" <Markus.Amend@telekom.de>,
"nathalie.romo-moreno@telekom.de"
<nathalie.romo-moreno@telekom.de>
Subject: Re: DCCP Deprecation
Date: Wed, 16 Aug 2023 08:00:00 -0700 [thread overview]
Message-ID: <20230816080000.333b39c2@hermes.local> (raw)
In-Reply-To: <CWLP265MB644915995F6D87F6F186BEF7C915A@CWLP265MB6449.GBRP265.PROD.OUTLOOK.COM>
On Wed, 16 Aug 2023 09:38:21 +0000
"Maglione, Gregorio" <Gregorio.Maglione@city.ac.uk> wrote:
> >As Kuniyuki noted, a relevant record of contributions to netdev would
> >help/be appreciated/customary before proposing stepping-in as
> >maintainer of some networking components.
>
> Admittedly I have minimal netdev experience, I thought helping with an unmaintained protocol with no users would have been good experience. However, if we're looking to upstream MP-DCCP then our project would no longer require a DCCP maintainer.
>
> >IMHO solving the license concerns and move MP-DCCP upstream (in this
> >order) would be the better solution. That would allow creating the
> >contributions record mentioned above.
>
> MP-DCCP is open source under GPL-2. The scheduling and reordering algorithms are proprietary, however, they are not necessary to MP-DCCP and can be omitted. Is that enough to solve the license concern?
Is the scheduling in the kernel? If so yes, it will cause a MP-DCCP not to be accepted.
If it is all done in userspace, then it leaves option for someone to reinvent their own open source version.
next prev parent reply other threads:[~2023-08-16 15:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CWLP265MB6449FC7D80FB6DDEE9D76DA9C930A@CWLP265MB6449.GBRP265.PROD.OUTLOOK.COM>
2023-07-10 18:22 ` DCCP Deprecation Kuniyuki Iwashima
2023-07-10 19:01 ` Jakub Kicinski
2023-07-10 20:31 ` Stephen Hemminger
[not found] ` <CWLP265MB6449543ADBE7B64F5FE1D9F8C931A@CWLP265MB6449.GBRP265.PROD.OUTLOOK.COM>
2023-07-11 10:06 ` Paolo Abeni
2023-08-16 9:38 ` Maglione, Gregorio
2023-08-16 15:00 ` Stephen Hemminger [this message]
2023-08-16 15:26 ` Maglione, Gregorio
2023-08-16 17:15 ` Stephen Hemminger
2023-08-18 9:35 ` Maglione, Gregorio
2023-08-18 16:20 ` Stephen Hemminger
2023-08-29 15:17 ` Maglione, Gregorio
2023-08-30 0:38 ` Jakub Kicinski
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230816080000.333b39c2@hermes.local \
--to=stephen@networkplumber.org \
--cc=Gregorio.Maglione@city.ac.uk \
--cc=Markus.Amend@telekom.de \
--cc=Veselin.Rakocevic.1@city.ac.uk \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=nathalie.romo-moreno@telekom.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).