Re: (multi6) control / load balancing of ingress traffic.

[Pekka Savola <pekkas@netcore.fi>]

On Sat, 12 Jan 2002, Masataka Ohta wrote:
> For example, your selection of addresses at a source may
> randomly distribute return traffic but unlikely balance it.
> 
> The destination may know, from routing information, some return
> path is temporaliry unavailable or some return path is five
> times more favourable than others.

A problem with this 'destination address selection'...

When sending a packet, the source must pick _one_ source address; it
cannot store more of them.  When the destination replies, it might know
which path is best but this cannot be done unless the transport protocols
are changed (or something else rather radical is done) so all addresses 
are tagged in the packets.

-- 
Pekka Savola                 "Tell me of difficulties surmounted,
Netcore Oy                   not those you stumble over and fall"
Systems. Networks. Security.  -- Robert Jordan: A Crown of Swords