The removal of the route cache caused a notable change in behaviour for equal cost routes. When there was a cache, you got a kind of session stickiness for fre

The removal of the route cache caused a notable change in behaviour for equal cost routes. When there was a cache, you got a kind of session stickiness for free. Which meant you could do some fairly good load balancing at the network layer by advertising multiple routes to the same IP locally. The router would choose one of the routes when it saw the first packet, cache the decision and send the rest of the packets to it (the cache key was configurable and could include src address, amongst other things). Now you just get round robin between all the advertised paths - no good for tcp load balancing.