Dear group, Taking Alvaro's and other people's feedback into account, here is the fourth version of the charter.
OK? good to go? Warren Kumari? :-) Kind regards, Job GROW co-chair ==== 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, mainly IDR and SIDROPS, with respect to whether it is addressing the relevant operational and routing security requirements of Internet-connected 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 ---------- Nov 2020 - "Support for Local RIB in BGP Monitoring Protocol (BMP)" to IESG Jun 2021 - "BMP Peer Up Message Namespace" to IESG Jun 2021 - "Revision to Registration Procedures for Multiple BMP Registries" to IESG. Jul 2021 - “Document negative consequences of de-aggregating received routes for traffic engineering purposes” - to IESG Nov 2021 - "TLV support for BMP Route Monitoring and Peer Down Messages" to IESG. Jan 2022 - “A BCP on using IRR and RPKI data to improve filtering of BGP peering sessions” to IESG or via “Evolving Documents” _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
