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

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

Michel;

> Let me try to explain this.
> - Site S is multihomed to providers A,B and C.
> - Site S has received aggregatable PA addresses from all three
> providers.
> - The multihoming solution is a multi-address one, which means that each
> host on site S has several addresses, one for each provider and possibly
> a PI address as well.
> - In the cloud, during the transport of the packet, one of the PA
> addresses
> is going to be used. This effectively assures load balancing among the
> different providers by the choice of the destination address by the
> source.
> - So, the provider used at the destination is controlled by the source
> when
> the multihoming protocol chooses among the different possible
> destinations.
> - If that multihoming protocol bases its decisions on info provided by
> the
> destination, you can truly says that the destination controls its own
> ingress traffic. DESTINATION ADDRESS SELECTION is the key here, not
> routing.

Looking at your proposal, I feel we should add one more
requirement that:

	A proposal must be for large scale policy rich Internet with
	highly assymmetric routing.

	Namely, routing informaion at a source gives no information
	or hint about how or whether the source can be reached from
	destination.

							Masataka Ohta