Re: The state of IPv6 multihoming development

["J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>]

    > From: "Craig A. Huegen" <chuegen@cisco.com>

    > Noel asked if I could suggest any other mechanisms. So far, all of the
    > multi-homing solutions I can think of that are implementable with
    > current code

I'd rather not get into the swamp of "current code only". Either way, I think
it's very useful to know what the technical alternatives are, and then you
can assess the entire cost/benefit balance of each (and yes, changing code is
a cost).

So, I'll ask again:

  there are a number of basically feasible paths you can take to support
  *widescale* multi-homing. ..
  First, you can use multiple connectivity-based addresses. .. Second, you
  can re-use a mobility mechanism. Third, you could use a radical addressing
  architecture that assigns addresses automatically, based on actual
  connectivity topology.

I've since remembered another, one that Dave Clark came up with in the early
80's (IIRC), which was "route fragments" - i.e. when you look someone up in
the DNS, you don't get back just an address, but also some partial source
routes which lead from something major (e.g. a large ISP which everyone will
have in their routing table) to the destination. There's an equivalent for
Map-Distribution based routing architectures.

Can you suggest any others (not including "let the routing do it")?

	Noel