Re: The state of IPv6 multihoming development

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

Huegen;

> As for the original multi-PA multihoming solution, it doesn't fly in an
> enterprise.  The selection of source and destination addresses by the
> originating host keeps enterprises from managing bandwidth on circuits,
> because the routing infrastructure has no idea of possible alternate paths
> for the packet.

According to your theory, the Internet today is not working, because
bandwidth of TCP is managed by individual hosts and the routing
infrastructure has no idea on it.

The reality is that L2/3 traffic engineering is a fallacy. It was
invented by people insisting on MPLS, even after they must admit
an obvious fact that MPLS routers are more expensive but no faster
than plain routers.

The real traffic engineering is that, if there is not enough link
capacity, add more fiber.

> BGP isn't perfect either, but it's much better than how
> many bits a particular address has in common with another.  Managing n+1
> prefixes per subnet where n is number of providers serving a site is a
> nightmare.  The list of problems goes on...

The nightmare is to manage n ASes where n is the number of multihomed
sites in the world.

							Masataka Ohta