Global Routing Operations (grow) Internet Drafts

      
 Methods for Detection and Mitigation of BGP Route Leaks
 
 draft-ietf-grow-route-leak-detection-mitigation-12.txt
 Date: 25/02/2025
 Authors: Kotikalapudi Sriram, Alexander Azimov
 Working Group: Global Routing Operations (grow)
 Problem definition for route leaks and enumeration of types of route leaks are provided in RFC 7908. This document describes a new well- known Large Community that provides a way for route-leak prevention, detection, and mitigation. The configuration process for this Community can be automated with the methodology for setting BGP roles that is described in RFC 9234.
 BMP v4: TLV Support for BGP Monitoring Prtoocol (BMP) Route Monitoring and Peer Down Messages
 
 draft-ietf-grow-bmp-tlv-16.txt
 Date: 24/02/2025
 Authors: Paolo Lucente, Yunan Gu
 Working Group: Global Routing Operations (grow)
 Most of the BGP Monitoring Protocol (BMP) message types make provision for data in Type, Length, Value (TLV) format. However, Route Monitoring messages (which provide a snapshot of the monitored Routing Information Base) and Peer Down messages (which indicate that a peering session was terminated) do not. Supporting (optional) data in TLV format across all BMP message types provides consistent and extensible structures that would be useful among the various use- cases where conveying additional data to a monitoring station is required. This document updates RFC 7854 [RFC7854] to support TLV data in all message types.
 AS Path Prepending
 
 draft-ietf-grow-as-path-prepending-15.txt
 Date: 23/04/2025
 Authors: Mike McBride, Doug Madory, Jeff Tantsura, Robert Raszuk, Hongwei Li, Jakob Heitz, Gyan Mishra
 Working Group: Global Routing Operations (grow)
 Autonomous System (AS) path prepending is a tool to manipulate the BGP AS_PATH attribute through prepending one or more Autonomous System Numbers (ASNs). AS path prepending is used to deprioritize a route in the presence of a route with a shorter AS_PATH. By prepending a local ASN multiple times, ASes can make advertised AS paths appear artificially longer. However, excessive AS path prepending has caused routing issues in the Internet. This document provides guidance for the use of AS path prepending, including alternative solutions, in order to avoid negatively affecting the Internet.
 Support for Enterprise-specific TLVs in the BGP Monitoring Protocol
 
 draft-ietf-grow-bmp-tlv-ebit-06.txt
 Date: 17/01/2025
 Authors: Paolo Lucente, Yunan Gu
 Working Group: Global Routing Operations (grow)
 Message types defined by the BGP Monitoring Protocol (BMP) do provision for data in TLV - Type, Length, Value - format, either in the shape of a TLV message body, ie. Route Mirroring and Stats Reports, or optional TLVs at the end of a BMP message, ie. Peer Up and Peer Down. However the space for Type value is unique and governed by IANA. To allow the usage of vendor-specific TLVs, a mechanism to define per-vendor Type values is required. In this document we introduce an Enterprise Bit, or E-bit, for such purpose.
 Near Real Time Mirroring (NRTM) version 4
 
 draft-ietf-grow-nrtm-v4-07.txt
 Date: 14/05/2025
 Authors: Sasha Romijn, Job Snijders, Edward Shryane, Stavros Konstantaras
 Working Group: Global Routing Operations (grow)
 This document specifies a one-way synchronization protocol for Internet Routing Registry (IRR) records. The protocol allows instances of IRR database servers to mirror IRR records, specified in the Routing Policy Specification Language (RPSL), between each other.
 BMP Extension for Path Status TLV
 
 draft-ietf-grow-bmp-path-marking-tlv-03.txt
 Date: 23/04/2025
 Authors: Camilo Cardona, Paolo Lucente, Pierre Francois, Yunan Gu, Thomas Graf
 Working Group: Global Routing Operations (grow)
 The BGP Monitoring Protocol (BMP) provides an interface for obtaining BGP path information, which is is conveyed through BMP Route Monitoring (RM) messages. This document specifies a BMP extension to convey the status of a path after being processed by the BGP process.
 Logging of routing events in BGP Monitoring Protocol (BMP)
 
 draft-ietf-grow-bmp-rel-03.txt
 Date: 03/03/2025
 Authors: Paolo Lucente, Camilo Cardona
 Working Group: Global Routing Operations (grow)
 The BGP Monitoring Protocol (BMP) does provision for BGP session event logging (Peer Up, Peer Down), state synchronization (Route Monitoring), debugging (Route Mirroring) and Statistics messages, among the others. This document defines a new Route Event Logging (REL) message type for BMP with the aim of covering use-cases with affinity to alerting, reporting and on-change analysis.
 A YANG Data Model for BGP Communities
 
 draft-ietf-grow-yang-bgp-communities-04.txt
 Date: 24/03/2025
 Authors: Martin Pels
 Working Group: Global Routing Operations (grow)
 This document defines a YANG data model for the structured specification of BGP communities. The model provides operators with a way to publish their locally defined BGP communities in a standardized format.
 Definition For New BGP Monitoring Protocol (BMP) Statistics Types
 
 draft-ietf-grow-bmp-bgp-rib-stats-08.txt
 Date: 24/04/2025
 Authors: Mukul Srivastava, Yisong Liu, Changwang Lin, Jinming Li
 Working Group: Global Routing Operations (grow)
 RFC 7854 defines different BGP Monitoring Protocol (BMP) statistics message types to observe events that occur on a monitored router. This document defines new statistics type to monitor BMP Adj-RIB-In and Adj-RIB-Out Routing Information Bases (RIBs).
 Updated BGP Operations and Security
 
 draft-ietf-grow-bgpopsecupd-08.txt
 Date: 15/04/2025
 Authors: Tobias Fiebig, Nick Hilliard
 Working Group: Global Routing Operations (grow)
 The Border Gateway Protocol (BGP) is a critical component in the Internet to exchange routing information between network domains. Due to this central nature, it is important to understand the security and reliability requirements that can and should be ensured to prevent accidental or intentional routing disturbances. Previously, security considerations for BGP have been described in RFC7454 / BCP194. Since the publications of RFC7454 / BCP194, several developments and changes in operational practice took place that warrant an update of these best current practices. This document replaces RFC7454 / BCP194, focusing on the overall goals, and providing a less implementation centric set of best practices. To this end, the document describes the security requirements and goals when operating BGP for exchanging routing information with other networks. The document explicitly does not focus on specific technical implementations and requirements. Operators are advised to consult documentation and contemporary informational documents concerning methods to ensure that these properties are sufficiently ensured in their network.
 Recommendation to avoid use of BGP Extended Communities at Internet Exchange Route Servers
 
 draft-ietf-grow-ixp-ext-comms-01.txt
 Date: 07/12/2024
 Authors: Job Snijders, Stavros Konstantaras, Mo Shivji
 Working Group: Global Routing Operations (grow)
 This document outlines a recommendation to the Internet operational community to avoid the use of BGP Extended Communities at Internet Exchange Point (IXP) Route Servers. It includes guidance for both the Internet Service Provider side peering with Route Servers and IXPs operating Route Servers. This recommendation aims to help the global Internet routing system's performance and help protect Route Server participants against misconfigurations.
 TCP-AO Protection for BGP Monitoring Protocol (BMP)
 
 draft-ietf-grow-bmp-tcp-ao-01.txt
 Date: 23/02/2025
 Authors: Hemant Sharma, Jeffrey Haas
 Working Group: Global Routing Operations (grow)
 This document outlines the utilization of the TCP Authentication Option (TCP-AO), as specified in [RFC5925], for the authentication of BGP Monitoring Protocol (BMP) sessions, as specified in [RFC7854]. TCP-AO provides for the authentication of BMP sessions established between routers and BMP stations at the TCP layer. Discussion Venues This note is to be removed before publishing as an RFC. Source for this draft and an issue tracker can be found at https://github.com/hmntsharma/draft-hmntsharma-bmp-tcp-ao.
 Peering API
 
 draft-ietf-grow-peering-api-00.txt
 Date: 07/12/2024
 Authors: Carlos Aguado, Matt Griswold, Jenny Ramseyer, Arturo Servin, Tom Strickx
 Working Group: Global Routing Operations (grow)
 We propose an API standard for BGP Peering, also known as interdomain interconnection through global Internet Routing. This API offers a standard way to request public (settlement-free) peering, verify the status of a request or BGP session, and list potential connection locations. The API is backed by PeeringDB OIDC, the industry standard for peering authentication. We also propose future work to cover private peering, and alternative authentication methods.
 BMP Loc-RIB: Peer address
 
 draft-ietf-grow-bmp-loc-peer-01.txt
 Date: 16/03/2025
 Authors: Pierre Francois, Maxence Younsi, Paolo Lucente
 Working Group: Global Routing Operations (grow)
 BMP Loc-RIB [RFC9069] enforces that the BMP router sets the Peer Address value of a path information to zero. This document introduces the option to communicate the actual peer from which a path was received when advertising that path with BMP Loc-RIB.
 Currently Used Terminology in Global Routing Operations
 
 draft-ietf-grow-routing-ops-terms-00.txt
 Date: 09/04/2025
 Authors: Tobias Fiebig, Wolfgang Tremmel
 Working Group: Global Routing Operations (grow)
 Operating the global routing ecosystem entails a divers set of interacting components, while operational practice evolved over time. In that time, terms emerged, disappeared, and sometimes changed their meaning. To aid operators and implementers in reading contemporary drafts, this document provides an overview of terms and abbreviations used in the global routing operations community. The document explicitly does not serve as an authoritative source of correct terminology, but instead strives to provide an overview of practice.
 Current Options for Securing Global Routing
 
 draft-ietf-grow-routing-ops-sec-inform-00.txt
 Date: 09/04/2025
 Authors: Tobias Fiebig
 Working Group: Global Routing Operations (grow)
 The Border Gateway Protocol (BGP) is the protocol is a critical component in the Internet to exchange routing information between network domains. Due to this central nature, it is an accepted best practice to ensure basic security properties for BGP and BGP speaking routers. While these general principles are outlined in BCP194, it does not provide a list of technical and implementation options for securing BGP. This document lists available options for securing BGP, serving as a contemporary, non-exhaustive, repository of options and methods. The document explicitly does not make value statements on the efficacy of individual techniques, not does it mandate or prescribe the use of specific technique or implementations. Operators are advised to carefully consider whether the listed methods are applicable for their use-case to ensure best current practices are followed in terms of which security properties need to be ensured when operating BGP speakers. Furthermore, the listed options in this document may change over time, and should not be used as a timeless ground-truth of applicable or sufficient methods.

data-group-menu-data-url="/group/groupmenu.json">

Global Routing Operations (grow)

WG Name Global Routing Operations
Acronym grow
Area Operations and Management Area (ops)
State Active
Charter charter-ietf-grow-05 Approved
Document dependencies
Additional resources Issue tracker, Wiki, Zulip stream
Personnel Chairs Job Snijders, Paolo Lucente
Area Director Mohamed Boucadair
Tech Advisor Jeffrey Haas
Mailing list Address grow@ietf.org
To subscribe https://www.ietf.org/mailman/listinfo/grow
Archive https://mailarchive.ietf.org/arch/browse/grow/
Chat Room address https://zulip.ietf.org/#narrow/stream/grow

Charter for Working Group

The Border Gateway Protocol (BGP) is fundamental to the operation
of the global IP routing system and ensuring global reachability
on the Internet.

The purpose of the GROW working group is to consider the operational
challenges associated with the global IP routing system (both IPv4 and
IPv6), including but not limited to default-free zone routing table
growth, forwarding tables growth, effects of the interactions between
interior and exterior routing protocols, and effects of IPv4/IPv6
address allocation policies on the global routing system.

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.

The GROW working group will develop data models and building blocks
for automating the operation of the global routing system.

The GROW working group will collaborate with other working groups,
primarily IDR working group, that are developing solutions for the
global IP routing system. When solicited, the working group will
review the solutions being developed for the global routing system by
these other working groups and provide inputs related to operational
implications. The working group will also provide inputs for
addressing operational and routing security requirements of Internet-
connected networks, and, where appropriate, recommend work to be
taken up by those working groups. Likewise, the working group will
solicit inputs for its chartered work from those other working groups
to strive for an optimal balance between objectives related to ease
of operations and deployability, sustain scaling, enhance robustness,
and optimize performance.

Agenda time at GROW sessions at IETF meetings should allow for
presentations and discussions of operator issues and experience, and
other work within scope for the working group.

The current GROW working group objectives are:

  • Present and discuss operational issues faced by the global routing
    system.

  • Document common terminology relevant to the maintenance and
    operation of the global routing system.

  • Document Best Current Practices for operations of the global
    routing system.

  • Document the operational aspects of securing the Internet routing
    system.

  • Provide guidance and recommendations for operating the global
    routing system.

  • Standardize YANG data models and automation building blocks
    related to the operations of global routing system.

  • Document BGP operational aspects of IP interconnection.

  • Provide documentation to assist in preventing malpractice in the
    global routing system.

  • Determine the effect of IGP extensions on the stability of the
    global routing system.

  • Provide maintenance for the BGP Monitoring Protocol (BMP),
    including fixes, extensions, and future versions.

  • Provide maintenance for the Multi-Threaded Routing Toolkit (MRT)
    Routing Information Export Format.

Work related to SIDR operations (consisting of RPKI, Origin Validation of
BGP announcements, and BGPSEC operations) will occur in SIDROPS working group.

Milestones

Date Milestone Associated documents
Dec 2026 Submit Peering API to the IESG draft-ietf-grow-peering-api
Apr 2026 Submit Terminology in Global Routing Operations to the IESG draft-ietf-grow-routing-ops-terms
Apr 2026 Submit Updated BGP Operations and Security to the IESG draft-ietf-grow-bgpopsecupd
Feb 2026 Submit Near Real Time Mirroring (NRTM) version 4 to the IESG draft-ietf-grow-nrtm-v4
Dec 2025 Submit TCP-AO Protection for BMP to the IESG draft-ietf-grow-bmp-tcp-ao
Nov 2025 TLV support for BMP Route Monitoring and Peer Down Messages to IESG draft-ietf-grow-bmp-tlv
Nov 2025 Submit BMP Extensions to the IESG draft-ietf-grow-bmp-rel
draft-ietf-grow-bmp-loc-peer
Oct 2025 Submit a YANG Data Model for BMP to the IESG draft-ietf-grow-bmp-yang
Sep 2025 Submit a Recommendation to avoid use of BGP Extended Communities at Internet Exchange Route Servers to the IESG draft-ietf-grow-ixp-ext-comms
Jul 2025 Submit AS Path Prepending to the IESG draft-ietf-grow-as-path-prepending
Jul 2025 Submit New BGP Monitoring Protocol (BMP) Statistics Types to the IESG draft-ietf-grow-bmp-bgp-rib-stats
Jul 2025 Submit a YANG Data Model for BGP Communities to the IESG draft-ietf-grow-yang-bgp-communities

Done milestones

Date Milestone Associated documents
Done "Revision to Registration Procedures for Multiple BMP Registries" to IESG rfc9515 (was draft-ietf-grow-bmp-registries-change)
Done "BMP Peer Up Message Namespace" to IESG rfc9736 (was draft-ietf-grow-bmp-peer-up)
Done "Support for Local RIB in BGP Monitoring Protocol (BMP)" to IESG rfc9069 (was draft-ietf-grow-bmp-local-rib)