Job: Hi!
Thanks for addressing my comments! I have just a couple more things: - The use of "Internet networks" doesn't sound right...perhaps "Internet- connected networks"? Looking at the rest of the charter, I assume that, for example, the operations of BGP in a non-Internet-connected network (a data center, for example) is not within the scope of grow. Is that the intent, or am I reading too much into it? - [nit] The last goal talks about "preventing malpractice in the global routing system". I'm not sure documentation can stop someone from doing the wrong thing -- especially if they want to. Maybe this goal can be worded positively: Document best practices and recommendations to assist in the proper operation of the global routing system. Thanks! Alvaro. On July 29, 2020 at 1:07:06 PM, Job Snijders (j...@ntt.net(mailto:j...@ntt.net)) wrote: > Dear all, > > Below is a third revision of the charter proposal, we attempted to > incorporate all the feedback received so far, specifically Alvaro's. > > Please let us know your feedback! > > Kind regards, > > Job & Chris > > ------------------------------------------------------ > > Charter for Working Group > ========================== > > The purpose of GROW is to consider the operational problems associated > with the Internet Protocol (IP) global routing systems, including but > not limited to default-free zone routing table growth, effects of the > interactions between interior and exterior routing protocols, the effect > of address allocation policies, or practices on the global routing > system. Where appropriate, GROW documents the operational aspects of > measurement, monitoring, policy, routing system security, VPN > infrastructures, or safe default behavior of IP routing protocol > implementations and deployments. > > GROW will also advise various working groups, specifically IDR and > SIDROPS, with respect to whether it is addressing the relevant > operational and routing security requirements of Internet networks, > and where appropriate, suggest course corrections. Finally, operational > requirements developed in GROW can also be used by any working group > chartered with standardizing a next generation inter-domain routing > protocol. > > GOALS > ----- > > * Provide stewardship and maintenance for the BGP Monitoring Protocol (BMP) > * Provide stewardship and maintenance for the Multi-Threaded Routing > Toolkit (MRT) Routing Information Export Format > * Document Best Current Practises for operations of the Internet global > routing system. > * Analyze aspects for supporting new applications, including extending > existing routing protocols or creating new ones. This includes risk, > interference, and application fit. > * Document the operational aspects of securing the Internet routing > system, and provide recommendations to other WGs. > * Provide documentation to assist in preventing malpractice in the > global routing system. > > Milestones > ---------- > > 2020 - "Support for Local RIB in BGP Monitoring Protocol (BMP)" to IESG > 2020 - "BMP Peer Up Message Namespace" to IESG > 2020 - "Revision to Registration Procedures for Multiple BMP Registries" to > IESG. > 2021 - "Document negative consequences of de-aggregating received routes for > traffic engineering purposes" - to IESG > 2021 - "TLV support for BMP Route Monitoring and Peer Down Messages" to IESG. > 2021 - "A BCP on using IRR and RPKI data to improve filtering of BGP peering > sessions" to IESG or via "Evolving Documents" > > > _______________________________________________ > GROW mailing list > GROW@ietf.org > https://www.ietf.org/mailman/listinfo/grow _______________________________________________ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
