netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: "Maglione, Gregorio" <Gregorio.Maglione@city.ac.uk>,
	Kuniyuki Iwashima <kuniyu@amazon.com>,
	Jakub Kicinski <kuba@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	 Florian Westphal <fw@strlen.de>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Stephen Hemminger <stephen@networkplumber.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, 11 Jul 2023 12:06:36 +0200	[thread overview]
Message-ID: <0cb1b68794529c4d4493b5891f6dc0e9a3a03331.camel@redhat.com> (raw)
In-Reply-To: <CWLP265MB6449543ADBE7B64F5FE1D9F8C931A@CWLP265MB6449.GBRP265.PROD.OUTLOOK.COM>

Hi,

Please send plain text messages, and do proper quoting.

On Tue, 2023-07-11 at 09:31 +0000, Maglione, Gregorio wrote:
> The IETF marks MP-DCCP as EXP and is set to mark is as PS soon.
> Removing DCCP from the kernel would likely impact PS standardisation
> or better. If the reason for removal is the lack of a maintainers,
> then I have sufficient time for bug fixing and syzbot testing.

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.

> If, as Jakub suggests, DCCP has no users other than MP-DCCP, and as
> such shouldn't be maintained, 

FWIW, I agree that in kernel user would help DCCP "de-deprecation"

> then are you suggesting that we investigate this license concern to
> allow for MP-DCCP to move upstream, or did you have a patch in mind?

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.

FTR MPTCP is already there, perhaps there is some possible convergence
between the 2 protocols.

Cheers,

Paolo


  parent reply	other threads:[~2023-07-11 10:06 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 [this message]
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=0cb1b68794529c4d4493b5891f6dc0e9a3a03331.camel@redhat.com \
    --to=pabeni@redhat.com \
    --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=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).