> For encapsulation there is good news and bad news. When we're > encapsulating over UDP we can affect the path simply by twiddling the > source port a little, so having application reopen connection might > not be necessary response to bad path. Bad news is that it may be > infeasible to get the feedback from a third party guest about path > quality. If the encapsulation layer wants to perform path selection > somehow inband signaling and per flow might be needed at that layer.
This is why in LISP the ITR simply RLOC-probes each RLOC in the locator-set and not concerned with the multiple paths to each RLOC. So if RLOC-probing or echo-noncing determines an RLOC is unreachable, we just switch to another RLOC. I am not sure if the LISP overlay had Segment Routing underneath it, that it could really stay with an RLOC that has just gone down if it could select another SR path to that RLOC. Maybe we are just splitting hairs too thinly here. Dino _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
