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

[Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>]

Pekka;

> > 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.

That is not a problem at all.

					Masataka Ohta