Any reason to keep print-otv.c?

[fxlb]

• This is not a security issue (See first line).

Any reason to keep print-otv.c?

specification: draft-hasmit-otv-04
"This Internet-Draft is no longer active."
(https://datatracker.ietf.org/doc/draft-hasmit-otv/)

OTV defines UDP port 8472

udp.h:237:#define OTV_PORT            8472    /* draft-hasmit-otv-04 */

But:

Linux, drivers/net/vxlan/vxlan_core.c

/* UDP port for VXLAN traffic.
 * The IANA assigned port is 4789, but the Linux default is 8472
 * for compatibility with early adopters.
 */
static unsigned short vxlan_port __read_mostly = 8472;

[fxlb]

Wireshark:

epan/dissectors/packet-vxlan.c:22:#define UDP_PORT_VXLAN  "4789,8472" /* The IANA assigned port is 4789, but Linux default is 8472 for compatibility with early adopters */

[infrastation]

From mcr#54 it seems VXLAN was originally meant to be a case of OTV, but eventually swallowed it, then the file no longer has a purpose. @ffatghub, if you see a good reason to keep the notion of OTV in tcpdump, please comment.