Re: Issue: Simultaneous movements (#2)

 In your previous mail you wrote:

   There seems to be a number of different cases here:
   
   (a) Two mobile nodes getting a new address at the
        same time, and then being unable to tell each
        other where they are. This problem is called the
        rendevouz problem, and is traditionally solved
        using home agents (Mobile IPv6) or forwarding
        agents (Host Identity Protocol). Essentially,
        solving this problem requires the existence of
        a stable infrastructure node somewhere.
   
        Example: roaming laptop to another roaming laptop,
        no SGW involved.
   
=> this is a well known problem with a well known solution
clearly outside the charter.

   (b) Simultanous changes to addresses such that at
        least one of the new addresses was known by
        both peers before the change occurred. The
        primary problem in case (a) was not knowing
        the new addresses beforehand.
   
        Example 1: two SGWs failover to another path.
        Example 2: roaming laptop gets a new address
        at the same time as its SGW's primary interface
        goes down.
   
=> in fact this is the same problem than (a) but in a multi-homing
context (in place of a mobility one). (a) solution works of course
but a simple policy (just try all the other peer addresses you know)
too. So I agree to keep (b) but I'd like to put the requirement
over policies, not mechanisms (as soon as they provide the other
peer address list of course).

Regards

[email protected]

PS: the simple policy is simple to describe but not so simple to use
because of the source (i.e., own peer address) selection...