Bruno - Inline.
From: [email protected] <[email protected]> Sent: Tuesday, August 3, 2021 1:41 AM To: Les Ginsberg (ginsberg) <[email protected]> Cc: [email protected] Subject: IS-IS flooding Les, Thank you for the implementation and test results. I have some clarification questions on your test results S6: What burst size did you use? And distributions of reals values if possible, if not (min, max, average, median) would be useful. What scheduling frequency/period did you use on the sender? [LES:] I did speak to this point during the presentation. At faster flooding speeds (let's use 1000 LSPs/second as an example), it is unrealistic to expect that the IS-IS TX thread can expect to be scheduled 1000 times/sec - so a model of sending 1 LSP each interval is unlikely to achieve the desired rate. (Something that is far more likely to work at 33 LSPs/second.) So we try to compensate for irregular scheduling to achieve the target Tx rate/second. There is no fixed burst - what we do is adaptive so that in the course of a second we can achieve the current target rate. S9: Given that the sender seems to react after 1 second, it seems clear that feedback (PSNPs) was received before. - How fast does the receiver sends PSNP? Is this default value or was that changed? - What value did you use for you configured parameter "Receiver ACK Delay"? [LES:] We have tried a variety of PSNP delay intervals because we expect that in the real world different implementations are currently using different values and while we agree with you that we want to advocate using shorter PSNP delay timers - we do not want to require it in order to have the faster flooding work. All of the test results presented used 0 PSNP delay plus a fixed propagation delay of 500 ms. Les Thank you, --Bruno _________________________________________________________________________________________________________________________ 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] https://www.ietf.org/mailman/listinfo/lsr
