Hi Med, > On May 6, 2025, at 11:27 PM, [email protected] wrote: > > Hi Mahesh, > > Thank you for the review. > > Please see inline. > > Cheers, > Med > >> -----Message d'origine----- >> De : Mahesh Jethanandani via Datatracker <[email protected] >> <mailto:[email protected]>> >> Envoyé : mardi 6 mai 2025 23:16 >> À : The IESG <[email protected] <mailto:[email protected]>> >> Cc : [email protected] <mailto:[email protected]>; [email protected] >> <mailto:[email protected]> >> Objet : [GROW] Mahesh Jethanandani's No Objection on charter-ietf- >> grow-04-05: (with COMMENT) >> >> >> Mahesh Jethanandani has entered the following ballot position for >> charter-ietf-grow-04-05: 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.) >> >> >> ------------------------------------------------------------------- >> COMMENT: >> ------------------------------------------------------------------- >> >> Paragraph 10 >>> * Standardize YANG data models and automation building blocks >>> related to the operations of global routing system. >> >> Wouldn't the WG where these routing protocols are being defined be >> the right place to do this work, with GROW providing the input? >> And, the YANG data models should already be defining the >> operational aspect of the protocols. >> > > [Med] The WG won't develop modules to manage generic BGP protocol machinery > as this is the territory of IDR. However, the WG focuses (and will) more on > aspects that are key for operations such as automating BGP interconnections > or providing means for operators to publish their locally defined BGP > communities. Of course, modules for protocols maintained by GROW (e.g., BMP) > will be developed here. > > Since BKK, we have Jeff (chair of IDR) as a tech advisor of GROW. Appropriate > coordination is in place. And so far, there is no overlapping on these > matters.
[mj] If this is clear between the routing ADs and GROW, great! And I do agree on examples such as BMP. It was not obvious to me reading the charter. Cheers. > >> ------------------------------------------------------------------- >> NIT >> ------------------------------------------------------------------- >> >> All comments below are about very minor potential issues that you >> may choose to address in some way - or ignore - as you see fit. >> Some were flagged by automated tools (via >> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg >> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg> >> ithub.com <http://ithub.com/>%2Flarseggert%2Fietf- >> reviewtool&data=05%7C02%7Cmohamed.boucadair%40orange.com >> <http://40orange.com/>%7C22452625 >> 84de4c07f3af08dd8ce33f68%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0 >> %7C638821629834143136%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRyd >> WUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3 >> D%3D%7C0%7C%7C%7C&sdata=sydSRxoeza5yOfmKqqJoKCey8jjqxWGZu%2FVOsaZdS >> JQ%3D&reserved=0), so there will likely be some false positives. >> There is no need to let me know what you did with these >> suggestions. >> >> Paragraph 1 >>> The working group will document the operational aspects of >>> measurement, monitoring, policy, operational global routing >> system >>> security, or safe default behavior of global IP routing protocol >>> implementations and deployments. The GROW working group will >> also >>> develop and increase awareness to mitigations to prevent >> malpractice >>> (e.g., route leaks) in the global routing system. >> >> Too many "operational" words in the first sentence?? >> >> > > [Med] That's on purpose because otherwise some of these items may fall under > the scope of other WGs. Will keep the text as it is. > > > ____________________________________________________________________________________________________________ > 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. Mahesh Jethanandani [email protected]
_______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
