Load balancing by per-packet multipath routing was generally disfavored due to the impact of rapidly changing latency, packet reordering and maximum transmission unit (MTU) differences within a network flow, which could disrupt the operation of many Internet protocols, most notably TCP and path MTU discovery. RFC 2992 analyzed one particular multipath routing strategy involving the assignment of flows through hashing flow-related data in the packet header. This solution is designed to avoid these problems by sending all packets from any particular network flow through the same path while balancing multiple flows over multiple paths in general.2
Multipath Issues in Unicast and Multicast Next-Hop Selection. doi:10.17487/RFC2991. RFC 2991. Retrieved 16 December 2013. https://tools.ietf.org/html/rfc2991 ↩
Analysis of an Equal-Cost Multi-Path Algorithm. doi:10.17487/RFC2992. RFC 2992. https://datatracker.ietf.org/doc/html/rfc2992 ↩