[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a41352e8-6845-1031-98ab-6a8c62e44884@gmail.com>
Date: Sat, 20 Mar 2021 14:35:18 -0600
From: David Ahern <dsahern@...il.com>
To: Ishaan Gandhi <ishaangandhi@...il.com>,
Andreas Roeseler <andreas.a.roeseler@...il.com>
Cc: David Miller <davem@...emloft.net>,
Network Development <netdev@...r.kernel.org>,
Stephen Hemminger <stephen@...workplumber.org>,
Willem de Bruijn <willemdebruijn.kernel@...il.com>
Subject: rfc5837 and rfc8335
On 3/19/21 10:24 PM, David Ahern wrote:
> At the end of the day, what is the value of this feature vs the other
> ICMP probing set?
Merging the conversations about both of these RFCs since my comments and
questions are the same for both.
What is the motivation for adding support for these RFCs? Is the push
from a company or academia (e.g., a CS project)?
Realistically, who is expected to use this feature and why given the
information it leaks about the networking configuration of the node. Why
is this tool expected to be more useful than a network operator using
existing protocols like lldp, collecting that data across nodes and
analyzing, or using tools like suzieq[1]?
RFC 5837 has been out for 11 years. Do any operating systems support it
— e.g., networking vendors like Cisco, Juniper, etc.? If not, why not?
This one seems to me the most dubious at this point in time.
Similarly for RFC 8335, what is the current support for it?
Linux does not need to support an RFC just because it exists. I am
really questioning the value of both of them
[1] https://github.com/netenglabs/suzieq
Powered by blists - more mailing lists