Hi Job, Very good input regarding „Devise a BGP Community Description System to IESG.
I think a YANG informational BGP community modell might be the right thing to do. I would volunteer to support such an approach. I think it is good to keep the charter generic. I like your proposal. I would be interested to know if others on the mailing list share my opinion on using YANG information model. Best Wishes Thomas > On 22 Nov 2019, at 09:44, Job Snijders <j...@ntt.net> wrote: > > Dear all, > > Below is a revision of the charter proposal. > > Kind regards, > > Job > > Charter for GROW Working Group > =============================== > > The Border Gateway Protocol (BGP) is fundamental to the operation of the > Internet. In recent years, occurrences of BGP related operational issues > have increased, and while overall understanding of the default-free > routing system has improved, there is still a long and growing list of > concerns. Among these are routing table growth rates, interaction of > interior and exterior routing protocols, dynamic properties of the > routing system, and the effects of routing policy on both the size and > dynamic nature of the routing table. In addition, new and innovative > uses of BGP, such as the use of BGP as a signaling protocol for some > types of Virtual Private Networks, have created new and unexpected > operational issues. > > The purpose of the GROW is to consider the operational problems > associated with the IPv4 and IPv6 global routing systems, including but > not limited to routing table growth, the effects of the interactions > between interior and exterior routing protocols, and the effect of > address allocation policies and practices on the global routing system. > Finally, where appropriate, the GROW documents the operational aspects > of measurement, monitoring, policy, security, and VPN infrastructures, > and safe default behavior of implementations. > > GROW will also advise various working groups, specifically the IDR and > SIDROPS working groups, with respect to whether it is addressing the > relevant operational and routing security needs of networks, and where > appropriate, suggest course corrections or intervene. Finally, > operational requirements developed in GROW can also be used by any new > working group charged with standardizing a next generation inter-domain > routing protocol. > > Goals > ===== > > * Develop and document Best Current Practises for operations in the > Internet routing system. > * Develop and document the operational aspects of securing the Internet > routing system including management of filtering and routing leaks. > * Analyse, document and provide best practice characteristics of running > BGP at large scale > * Provide analysis, feedback and assistance for other IETF working > groups when their subject matter impacts on the global Internet > routing ecosystem. > * Provide stewardship and maintenance for the BGP Monitoring Protocol (BMP) > * Provide stewardship and maintenance for the Multi-Threaded Routing Toolkit > (MRT) > > Milestones > ========== > > Jan 2020 - "Support for Local RIB in BGP Monitoring Protocol (BMP)" to IESG > Apr 2020 - "BMP Peer Up Message Namespace" to IESG > Jun 2020 - "Revision to Registration Procedures for Multiple BMP Registries" > to IESG. > Oct 2020 - "Document negative consequences of de-aggregating received routes > for traffic engineering purposes" to IESG > Jan 2021 - "A BCP on using IRR and RPKI data to improve filtering of BGP > peering sessions" to IESG or via "Evolving Documents" > Mar 2021 - "TLV support for BMP Route Monitoring and Peer Down Messages" to > IESG. > Jul 2021 - "Devise a BGP Community Description System" to IESG > > _______________________________________________ > GROW mailing list > GROW@ietf.org > https://www.ietf.org/mailman/listinfo/grow
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
