Saku Ytti writes:
> We don't need to extend IPv4, we need to figure out why we are in this
> dual-stack mess, which was never intended, and how to get out of it.
Few have figured out how to reliably deliver IPv4 over a IPv6 network,
and customers need IPv4 more than they need IPv6.
There is no
Mark Tinka writes:
> Oh? What is it then, if it's not spraying successive packets across
> member links?
It sprays the packets more or less randomly across links, and each link
then does individual buffering. It introduces an unnecessary random
delay to each packet, when it could just place them
Mark Tinka writes:
> set interfaces ae2 aggregated-ether-options load-balance per-packet
>
> I ran per-packet on a Juniper LAG 10 years ago. It produced 100%
> perfect traffic distribution. But the reordering was insane, and the
> applications could not tolerate it.
Unfortunately that is not
Mark Tinka writes:
> And just because I said per-flow load balancing has been the gold
> standard for the last 25 years, does not mean it is the best
> solution. It just means it is the gold standard.
TCP looks quite different in 2023 than it did in 1998. It should handle
packet reordering quite
4 matches
Mail list logo
