On Thu, Jan 5, 2023 at 2:10 PM Dino Farinacci <farinacci@xxxxxxxxx> wrote:
> I suppose that you have to question whether IP is the ideal base for multicast?
There are many ways to provide a group communication model to applications.
> Our networks are no longer mono-protocol and multicast tends to be domain specific.
Yes, but the IP headers are the same in all of them.
> Many of the original uses for multicast are now dominated by unicast packet duplication with edge computing making this less of a bandwidth hog, so it is not clear what the long term future of multicast is.
Not on Wall Street. But you will say that is domain specific, and that's okay.
Should we really be building an IP header or have semantics on an IP header for different domains?
Wall street is likely to be in a unique class here.
I don't think we need to consider multicast a failure if it doesn't end up being used because the functionality is being provided at a higher level in the stack.
At some point we should do a QUIC like transport for Multicast/Packet Duplication.
