nsis-8----Page:15
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
|
Rerouting and Path Repair Points of Commonality: Detection Trigger from NTLP (may need to be passed peer-to-peer at NTLP level if not detected at ‘local’ NTLP) From NSLP peer change (like a PHOP change in RSVP) Repair Install new reservation and remove on old path (somehow) Open Issues: What changes are significant (e.g. i/f change but same peer)? How is a change in NSLP peer identified (NTLP support?) What other methods of route change detection can be used (e.g. at NSLP level from data flow monitoring)? Should an explicit tear be sent, and if so how? Requires the ability to invoke the ‘old path’ explicitly at the NTLP |