Re: Architectural approaches to multi6

[Kurt Erik Lindqvist <kurtis@kurtis.pp.se>]

> >  However, I also think that there currently are to many views on what 
> > the architecture should be based on.
> The only architectural approach that I've seen on this list in recent
> months is the notion of deprecating the concept of an "address",
> in favour of using "locator" and "identifier" for the separate purposes
> of routing and identity.  Maybe I've overlooked something ?
Well, there is also Christians multiple address solution and on other 
lists there have been suggestions on using mobility based solutions.

> If there is another architectural approach in the wings, maybe someone
> would be kind enough to summarise that alternate approach to the list ?
Well, I want to give people a few days to present their solutions 
(there are also a few personal drafts submitted to the IETF) or 'ask' 
to have them reviewed. Then we need to start to move on.

But in principal the division of solution space could be

- multiaddress
- Mobility based
- Location/Identifier separation
- Based on today (basically improved routing, but I haven't seen any 
real proposals on this).

- kurtis -