John, Thank you for your review and your suggestion.
We have posted -11 which reflect your suggestion. A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-lsr-isis-fast-flooding-11 --Bruno From: John Scudder <[email protected]> Sent: Thursday, May 9, 2024 7:38 PM To: Acee Lindem <[email protected]> Cc: The IESG <[email protected]>; [email protected]; lsr-chairs <[email protected]>; lsr <[email protected]>; Zaheduzzaman Sarker <[email protected]> Subject: Re: Zaheduzzaman Sarker's No Objection on draft-ietf-lsr-isis-fast-flooding-10: (with COMMENT) CAUTION : This email originated outside the company. Do not click on any links or open attachments unless you are expecting them from the sender. ATTENTION : Cet e-mail provient de l'extérieur de l'entreprise. Ne cliquez pas sur les liens ou n'ouvrez pas les pièces jointes à moins de connaitre l'expéditeur. Thanks for the ping, Acee. Looking at the latest version I have one question. The revised Section 6.2.2 says, Whereas flow control prevents the sender from overwhelming the receiver, congestion control prevents senders from overwhelming the network. For an IS-IS adjacency, the network between two IS-IS neighbors is relatively limited in scope and includes a single link which is typically over-sized compared to the capability of the IS-IS speakers. Only implementing flow control Section 6.2.1 is expected to give good results and be enough if the internals or the receiver is not significantly dropping LSP. Otherwise, adding congestion control will help handling congestion of LSPs in the receiver. I don’t understand what the new “only implementing flow control” sentence means. Maybe it means something like, “In situations where the probability of LSP drop is low, flow control [Section 6.2.1] is expected to give good results, without the need to implement congestion control”. But maybe it doesn’t mean that, I can’t tell for sure. I’d appreciate a clarification from the authors (or someone else who knows!) and probably one more revision to make the sentence more understandable. After that, let’s ship it. Thanks, —John On May 9, 2024, at 12:27 PM, Acee Lindem <[email protected]<mailto:[email protected]>> wrote: Hey John, Is there anything more that needs to be done by the authors? Thanks, Acee On May 2, 2024, at 9:05 AM, Zaheduzzaman Sarker via Datatracker <[email protected]<mailto:[email protected]>> wrote: Zaheduzzaman Sarker has entered the following ballot position for draft-ietf-lsr-isis-fast-flooding-10: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://urldefense.com/v3/__https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/__;!!NEt6yMaO-gk!FeiWW24FwHcnwOkXm0kSg8nkuiR_EXpMYeXN5C4TXj_zmXX_sX6BykCYqyqe2WgI8bRUzsJGsOcpqsM$<https://urldefense.com/v3/__https:/www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/__;!!NEt6yMaO-gk!FeiWW24FwHcnwOkXm0kSg8nkuiR_EXpMYeXN5C4TXj_zmXX_sX6BykCYqyqe2WgI8bRUzsJGsOcpqsM$> for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-lsr-isis-fast-flooding/__;!!NEt6yMaO-gk!FeiWW24FwHcnwOkXm0kSg8nkuiR_EXpMYeXN5C4TXj_zmXX_sX6BykCYqyqe2WgI8bRUzsJGEt32q7I$<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-ietf-lsr-isis-fast-flooding/__;!!NEt6yMaO-gk!FeiWW24FwHcnwOkXm0kSg8nkuiR_EXpMYeXN5C4TXj_zmXX_sX6BykCYqyqe2WgI8bRUzsJGEt32q7I$> ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks for addressing my discuss points and comments. It was great to work with you all. I think the current version of this document is better, hence, cleared my discuss. ____________________________________________________________________________________________________________ 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]
