From: Jakub Kicinski <kuba@kernel.org>
To: "Maglione, Gregorio" <Gregorio.Maglione@city.ac.uk>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Paolo Abeni <pabeni@redhat.com>,
Kuniyuki Iwashima <kuniyu@amazon.com>,
"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: Tue, 29 Aug 2023 17:38:19 -0700 [thread overview]
Message-ID: <20230829173819.5ddb6497@kernel.org> (raw)
In-Reply-To: <CWLP265MB64494218BFFF89EFB445543EC9E7A@CWLP265MB6449.GBRP265.PROD.OUTLOOK.COM>
On Tue, 29 Aug 2023 15:17:08 +0000 Maglione, Gregorio wrote:
> For the purpose of upstreaming, the repository was forked
> [https://github.com/GREGORIO-M/mp-dccp] to remove non-GPL components
> and to update the license to show GPL-2.0. Is this enough to solve
> the license issue? If so, is it still agreeable for us to upstream
> and maintain MP-DCCP, so that, once DCCP deprecates, MP-DCCP becomes
> the sole DCCP enabler in the kernel? What steps would the upstreaming
> involve? Do you require any information about the MP?
Who is going to use it? Your earlier responses gave me the impression
that you just need a number of implementations for the standardization
process - apologies if I'm mistaken - but we suffered thru maintaining
the unused DCCP code for years, we need real users who will care.
Please use a sane email client you're responses are very hard to parse.
prev parent reply other threads:[~2023-08-30 0:38 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
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 [this message]
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=20230829173819.5ddb6497@kernel.org \
--to=kuba@kernel.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=kuniyu@amazon.com \
--cc=nathalie.romo-moreno@telekom.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).