From: Jakub Kicinski <kuba@kernel.org>
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: Gregorio Maglione <Gregorio.Maglione@city.ac.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Florian Westphal <fw@strlen.de>,
<netdev@vger.kernel.org>
Subject: Re: DCCP Deprecation
Date: Mon, 10 Jul 2023 12:01:01 -0700 [thread overview]
Message-ID: <20230710120101.4b6d78af@kernel.org> (raw)
In-Reply-To: <20230710182253.81446-1-kuniyu@amazon.com>
On Mon, 10 Jul 2023 11:22:53 -0700 Kuniyuki Iwashima wrote:
> From: "Maglione, Gregorio" <Gregorio.Maglione@city.ac.uk>
> Date: Mon, 10 Jul 2023 12:06:11 +0000
> > Hi Kuniyuki,
> >
> > I saw the deprecation notice on the DCCP. We are working with a multipath
> > extension of the protocol, and this would likely impact us in the
> > standardisation effort. Do you know whom I must contact to know how I can
> > volunteer to maintain the protocol, and to get more information about
> > the maintenance process?
>
> I think it would be better to review others' patches or post patches before
> stepping up as a maintainer.
Yes, I think we should document the expectations more clearly. I asked
on workflows@ if others already have docs.
https://lore.kernel.org/workflows/20230710115239.3f9e2c24@kernel.org/T/#u
For DCCP specifically I think we'd like to see some effort around
improving syzbot testing and addressing the bugs?
> However, this repo seems to have a license issue that cannot be upstreamed
> as is.
> https://github.com/telekom/mp-dccp
Right, in theory maintenance of the code already upstream is orthogonal
to protocol extensions. But if there is no user of the pure upstream
code then it seems hard to justify the effort of keeping it.
next prev parent reply other threads:[~2023-07-10 19:01 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 [this message]
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
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=20230710120101.4b6d78af@kernel.org \
--to=kuba@kernel.org \
--cc=Gregorio.Maglione@city.ac.uk \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kuniyu@amazon.com \
--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).