[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The state of IPv6 multihoming development
Iljitsch van Beijnum wrote:
The basic idea is simple: the IP addresses the transport layer uses
become the identifiers of a session. In transit, these identifiers
may/must be replaced by locators, but they identifiers are restored
before the packet reaches the transport layer at the other end.
The idea is that identifiers are also valid "regular" IP addresses that
can be used whenever multi-address multihoming isn't supported by both
ends or otherwise not desired.
Why does this so much sound like Mobile IPv6 to me?
Making this functionality "portable" so it can be located either inside
the host, or at a border router or some intermediate device would
greatly help in easy deployment and makes it possible to better address
the needs to implement multihoming or traffic engineering policies and
address management in large networks.
And why does this statement make me think that the lessons
we learned during the Mobile IPv6 security process might
be good to remember here?
I am probably biased here, but IMHO once you start to really
ponder the security consequences, you pretty much come to the
idea that maybe, after all, it might be better to introduce
a new cryptographic name space instead of once more overloading
the IP name space with some IP addresses that are end-point
identifiers (and locators) and some that are (just) locators.
The resulting aliasing problems are nasty, security wise.
The NSRG report still makes a good reading.
If you are going to require changes to the end-host and the
introduction of a mudem box anyway, the HIP design might
be a good place to start with. The more recent variants of
HIP already support end-host multi-homing, and they contain
a "mudem" which is able to perform prefix translation, function
as a mobility home agent, and as a mobility anchor point.
Probably the LIN6/LINA design can do most of what HIP does as well,
but I haven't followed their recent changes, and I don't know if
they have already solved the scalability problems in their