One more time, with feeling... > Do you mean if there is an identifiier collision during mobility, one should > be killed even though it is communicating with somebody else?
No, we're saying that it is the administrator's responsibility to ensure that there is no identifier collision. > If a mobile node change the session association from its permenant id to its > temperary id, the session is broken. No, there is no provision to change the identifier that a particular transport connection is associated with. > Before distinguishing the two identities, how could the last-hop router > determine which node a given link layer address is corresponding to? It seem > like a egg-chicken issue. Not at all. Suppose that we have identifier I, and two link layer addresses, A1 and A2. Suppose that the router has a binding in its neighbor cache for (I, A1), but that this entry has reached the point of being stale. Now, the router sees a packet (e.g., ND - RS) for (I, A2). It's well within the router's purview to now make use of this association. Tony _______________________________________________ rrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/rrg
