Charlie Perkins wrote:
I guess the Mobile IPv6 specification is not supposed to cover
cases where the mobile node is not using Mobile IPv6. Then,
if a mobile node wants to use visited site-local addresses for
communication within the visited site, that should be O.K.
If the mobile node IS using Mobile IPv6 with a global care-of
address, then ...? should it use that global care-of address for
other communications (e.g., very short term) for which the
home address is not involved?
The issue was simultaneous use of site-local addresses both
at the home site and at the visited site. I think the problem
is that when we see a site local address in the stack and
expect to do, say, a TCP connect to it, we don't know where
that address came from. If it came from home-site DNS then
we should somehow get to the home site. If it came from visited
network http link, then we should use it locally. I don't
think solving the problem by picking the right source address
is quite enough. This is because we may not have enough
information to do this selection. On the other hand the problem
also appears more general than just MIPv6 specific, because
other types of tunnels have similar problems.
Jari
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
