All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kirjanov <dkirjanov@suse.de>
To: Paolo Abeni <pabeni@redhat.com>, Lynne <dev@lynne.ee>,
	Netdev <netdev@vger.kernel.org>
Cc: Kuniyu <kuniyu@amazon.com>,
	Willemdebruijn Kernel <willemdebruijn.kernel@gmail.com>
Subject: Re: Regarding UDP-Lite deprecation and removal
Date: Mon, 18 Mar 2024 13:49:44 +0300	[thread overview]
Message-ID: <b89274d1-e8c9-4f2c-a6ce-998129b1b699@suse.de> (raw)
In-Reply-To: <658523650c342e7ffd2fcc136ac950baca6cf565.camel@redhat.com>



On 3/18/24 13:36, Paolo Abeni wrote:
> On Sun, 2024-03-17 at 01:34 +0100, Lynne wrote:
>> UDP-Lite was scheduled to be removed in 2025 in commit
>> be28c14ac8bbe1ff due to a lack of real-world users, and
>> a long-outstanding security bug being left undiscovered.
>>
>> I would like to open a discussion to perhaps either avoid this,
>> or delay it, conditionally.
> 
> I'm not very familiar to the deprecation process, but I guess this kind
> of feedback is the sort of thing that could achieve delaying or avoid
> the deprecation.
> 
> What will help more IMHO is someone stepping in to actually maintain
> the protocol. It should not be an high load activity, but a few things
> would be required: e.g. writing self-tests and ensuring that 3rd party
> changes would not break it. And reviewing patches - but given the
> protocol history that would probably be once in a lifetime.

That's sounds good enough to try

> 
> Cheers,
> 
> Paolo
> 
> 

  reply	other threads:[~2024-03-18 10:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-17  0:34 Regarding UDP-Lite deprecation and removal Lynne
2024-03-18 10:36 ` Paolo Abeni
2024-03-18 10:49   ` Denis Kirjanov [this message]
2024-03-18 14:10 ` Florian Westphal
2024-03-18 17:58   ` Lynne
2024-03-21 10:31     ` Paolo Abeni
2024-03-21 15:41     ` Jakub Kicinski
2024-03-21  8:29 ` Lynne
2024-03-21 11:43   ` Denis Kirjanov

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=b89274d1-e8c9-4f2c-a6ce-998129b1b699@suse.de \
    --to=dkirjanov@suse.de \
    --cc=dev@lynne.ee \
    --cc=kuniyu@amazon.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemdebruijn.kernel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.