Open issue #9: Dead Peer Discovery Issues: Dead peers (e.g., AR (or FA), CRN, HA or MN ) can occur either because a link or a network node failed, or MN moved away without informing NTLP/NSLP (e.g., QoS- or NAT/FW-NSLP). GIMPS discovery will detect the problem after some time: it says that GIMPS discovery might be slow (?). Question: How can dead peers be detected in a fast and efficient manner in mobility scenarios? GIMPS discovery? Do some “dead peer” cases need to be identified? e.g., MN’ moving-away, CRN failure, CARs’ failure, FA/HA’s failure, and so on. |