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

Hi Jari,

Jari Arkko 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
> - No incoming payload packets

I think that there's obviously an issue with
using a mechanism which isn't in itself secured
to indicate changes.

This may prevent generic ICMP being used.

The incoming payload packets or MOBIKE messages
may be another matter, although it's worth
considering that an orchestrated DoS attack
against devices on the path between the two endpoints
could be used to force selection of another path
which is preferable to the attackers.

I think these are generic concerns with such backup
procedures though, not just for MOBIKE.

Greg