draft-rigatoni-lsr-isis-fragment-timestamping currently states: The awareness of delays in the distribution of information can be incorporated further into algorithms and network tooling to improve the responsiveness and quality of decisions taken.
There was a request at the mike (Ketan) in today’s LSR session to elaborate how the awareness of distribution delays can be used in TE applications. I can give a simple distributed TE application example (there are several, but this should give a general idea how this information can be leveraged). In RSVP-TE networks, a TE path computed using a specific snapshot of TED can get rejected during signaling by a transit node because of bandwidth unavailability on a specific link (link bandwidth information in the snapshot of TED used during computation cannot always be “current”). When ingress gets notified of this “error” via RSVP signaling, the link in question is avoided in the subsequent path computation and an alternate path is sought. Most implementations tend to use a configurable “hold time” to determine how long this link needs to be avoided. The awareness of the distribution delay statistics can potentially be used by implementations to dynamically determine an appropriate “hold time” for a given TE link (instead of using a blanket topology-wide configuration). Regards, -Pavan
_______________________________________________ Lsr mailing list -- [email protected] To unsubscribe send an email to [email protected]
