Re: Issue: Should MOBIKE react to problems not known locally (#NEW)

 In your previous mail you wrote:

   Should MOBIKE only react to problems that are known
   to the nodes locally? For instance, if an interface
   in a host goes down, or it is assigned a new address,
   then the node knows about this and can tell its peer.
   
   Or should MOBIKE also deal with other problems, typically
   based on the symptom of not getting packets through?
   For instance, should MOBIKE attempt to do a failover
   upon seeing
   
   - DPD failure
   - ICMP error
   - No response to the MOBIKE protocol messages

=> of course you mean "No responde to the IKE protocol messages"

   - No incoming payload packets
   
=> first this is a policy issue as we don't want to define an extra
problem detection mechanism. Second IMHO this is a generic issue,
i.e., this should be handled by generic (in opposion to MOBIKE
specific) mobility or multi-homing control mechanisms. BTW we'll share
the possible security issues of these mechanisms too. And of course
MOBIKE mechanisms and policies have to follow indications from
this generic control stuff (i.e., my opinion is yes to everything).

Regards

[email protected]