Forgot to cc IPng again !
> -----Original Message-----
> From: Hesham Soliman (EPA)
> Sent: Saturday, 14 October 2000 2:54
> To: [EMAIL PROTECTED]
> Subject: RE: [MOBILE-IP] MIPv6 node location detection
>
> Hi Fred
> I am not the most knowledgeable on the subject, and my betters may correct
> me. But I would think this has to be answered in the exchange with the
> Home
> Agent.
>
> First, the Mobile Node has a number of limitations on its knowledge. It
> doesn't know its own prefix beyond what it received in a router
> advertisement, for example - if the router advertisement has changed
> prefix, that may well mean that the device has changed subnet within its
> home domain and should just use that address, or as you suggest, it may
> mean that somebody is renumbering the network. Since it doesn't know the
> site prefix, it cannot distinguish between the home domain (which is
> larger
> than the prefix for a particular subnet) and a foreign domain.
>
> It also has a responsibility. It must keep the Home Agent apprised both of
> its own current address and its current care-of address. So if its address
> changes, or if a new address is added to its list on some interface, it is
> going to have to advise the Home Agent of that.
>
> It is from the Home Agent's response that it will determine what's
> happening. If the Home Agent expresses the opinion that it needs to use
> the
> COA, it probably does, and if the Home Agent thinks its address is just
> fine...
>
> Now, I haven't read the latest specifications to tell you how the Home
> Agent expresses that. But I think it is in that context that the
> information is going to have to be derived and communicated.
>
> => Well according to my memory there is no such expression
> from the HA. Of course if the MN receives the new router
> advertisement from the HA (router on the link), then it will
> know that the default router is still the same and that there is
> no need to move. But that is not a fault proof solution because
> the link-local address may be duplicated between links.
>
> Another way of looking at it is that the "new" Ruter advertisement
> should inform hosts that this subnet is "being renumbered".
> I think this is a clean option. I don't think this should be a MIP
> issue. MIPv6 solves the problem when the MN is away from
> home, which is when MIPv6 is espected to solve it.
> I would suggest that this is a ND-MIP interaction issue.
>
> Hesham
>
> At 10:37 AM 10/12/00 +0900, SungJin Lee wrote:
> >I got confisued while i was reading MIPv6 standards and
> >have a couple of question with cases like following. The
> >It is assumed that the MIPv6 node use stateless autoconfiguration.
> >Let me know if I lost some in MIPv6 and IPv6 RFC.
> >
> >Q.1 A MIPv6 node moved to foreign link. The MIPv6 node restarts
> > the system there and receives router advertisements with
> > foreign network prefix.
> >
> > How do the MIPv6 node detect if it is located in foreign link?
> > isn't it could be normal autoconfiguration as in the home llink?
> >
> >Q.2 A MIPv6 node located in it's home link. The node got an IP address
> > with stateless autoconfiguration. At a time the router changed
> the
> > home link
> > prefix and multicast the router advertisement with new prefix.
> > After the home link prefix ifetime expired or before the life
> time
> > expired, it received router advertisement with new prefix.
> >
> > Why doesn't the IPv6 node think it's located in foreign link when
> it
> > received? isn't it possible the IPv6 node to think it's moved to
> a
> > foreign
> > link and start MIPv6 process?
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
