From: Vishnu Pavan Beeram <[email protected]> Sent: Thursday, November 7, 2024 10:53 AM
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). By « delay » do you mean the IS-IS flooding time across the flooding domain or do you mean something else? If this is the flooding time, what distribution delay statistics do you have in mind? In current deployment and as a goal in order to neglect this flooding time? e.g., if flooding time could be reduced to 50 ms would you still need this timestamp? Thanks, Regards, --Bruno Regards, -Pavan ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ Lsr mailing list -- [email protected] To unsubscribe send an email to [email protected]
