Re: modules of a mh solution (was RE: New multi6 draft: WIMP)

[senthil ayyasamy <saq66@umkc.edu>]

At 11:53 AM 2/18/2004 +0100, marcelo bagnulo wrote:
> For instance, most of the modules that you describe below are basically
> focused in preserving established communication through outages in
> multihomed environments.
...
> I mean, I would say that there is a significant amount of potential IPv6
> multihoming users that don't really have many critical established
> communications that have to survive a outage that occurred in one of their
> non directly connected link. (moreover, probably currently IPv4 multihoming
> solution fails to provide this for many apps in some scenarios where BGP
> reconvergence takes a while)

For now, connection preservation (fail over etc) should be the only goal.
LB/multi paths is a difficult problem (both at transport and routing.) It
has to be done after multi6 standardization. If we support MA, concurrent
multi transfer has to be standardized within tsv. If we support routing
based solutions(locator rewriting or BGP related,) load balancing needs
an algorithm approach (which should be done within routing area.) OTOH,
host centric solutions can depend on DNS for LB etc (which is not a
multi6 issue.)

or you meant something else?