Network Working Group M. Srivastava Internet-Draft Hewlett Packard Enterprise Intended status: Informational 16 November 2026 Expires: 20 May 2027 Benchmarking Methodology for BGP Monitoring Protocol (BMP) Convergence and Scaling draft-msri-bpm-bmp-convergence-benchmarking-00 Abstract The BGP Monitoring Protocol (BMP) is widely used by operators to stream BGP routing state from routers to monitoring and automation systems. Although BGP convergence has well-established benchmarking methodologies, there is no standardized way to measure how quickly and how completely a router exports BGP state over BMP, or how the BMP export affects the router and the collector. This document defines terminology, a reference test setup, metrics, and test procedures to benchmark the BMP convergence of a router (the Device Under Test) in a vendor-independent and repeatable way. It covers all five BMP monitoring views (Adj-RIB-In pre-policy and post-policy, Loc-RIB, and Adj-RIB-Out pre-policy and post-policy), initial table dump speed, convergence during routing events and churn, impact on BGP itself, scaling with the number of monitored views, the Adj-RIB- Out scale, and BMP stations, and behavior under TCP backpressure. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on 20 May 2027. Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. Srivastava Expires 20 May 2027 [Page 1] Internet-Draft BMP Convergence Benchmarking November 2026 This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Motivation . . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.3. Requirements Language . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.1. Terms Defined Elsewhere . . . . . . . . . . . . . . . . . 5 2.2. Terms Defined in This Document . . . . . . . . . . . . . 6 3. Test Setup . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.1. Reference Topology . . . . . . . . . . . . . . . . . . . 8 3.2. Multiple BMP Stations . . . . . . . . . . . . . . . . . . 9 3.3. BMP Station Types and Measurement Points . . . . . . . . 9 3.4. Time Reference and Timestamping . . . . . . . . . . . . . 10 4. Test Considerations . . . . . . . . . . . . . . . . . . . . . 11 4.1. Number of Peers, Address Families, and Routes . . . . . . 11 4.2. Policy . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.3. Configured Parameters . . . . . . . . . . . . . . . . . . 14 4.4. Tracing, Logging, and Other Processes . . . . . . . . . . 14 4.5. High Availability . . . . . . . . . . . . . . . . . . . . 15 4.6. Repeatability and Statistics . . . . . . . . . . . . . . 15 5. Metrics and Measurement Methods . . . . . . . . . . . . . . . 15 5.1. BMP Convergence Time . . . . . . . . . . . . . . . . . . 15 5.2. BMP Initial Dump Time and Dump Rate . . . . . . . . . . . 15 5.3. BMP Event Latency . . . . . . . . . . . . . . . . . . . . 16 5.4. BMP Fan-Out and Per-Peer Spread . . . . . . . . . . . . . 17 5.5. BGP Propagation Time and BMP Overhead . . . . . . . . . . 17 5.6. Detecting Completion of a Dump or of Convergence . . . . 17 5.6.1. Method A: Reference-State Completeness (Primary) . . 17 5.6.2. Method B: End-of-RIB Markers . . . . . . . . . . . . 18 5.6.3. Method C: Quiescence of the BMP Stream . . . . . . . 18 5.6.4. Method D: Control-Plane CPU . . . . . . . . . . . . . 18 5.6.5. Method E: Canary Routes (for Churn Conditions) . . . 19 5.6.6. Precondition Verification with Statistics Reports . . 19 5.7. Resource and Stability Metrics . . . . . . . . . . . . . 19 5.8. Scaling Metrics . . . . . . . . . . . . . . . . . . . . . 20 6. Test Cases . . . . . . . . . . . . . . . . . . . . . . . . . 20 6.1. Common Procedure . . . . . . . . . . . . . . . . . . . . 20 6.2. Initial Dump in Steady State . . . . . . . . . . . . . . 21 Srivastava Expires 20 May 2027 [Page 2] Internet-Draft BMP Convergence Benchmarking November 2026 6.2.1. Single-View Initial Dump . . . . . . . . . . . . . . 21 6.2.2. Initial Dump after BMP Session Re-establishment . . . 21 6.2.3. Time to Visibility after DUT Restart . . . . . . . . 21 6.3. Initial Dump during Churn . . . . . . . . . . . . . . . . 22 6.4. BMP Convergence after BGP Events . . . . . . . . . . . . 22 6.4.1. Route Advertisement . . . . . . . . . . . . . . . . . 22 6.4.2. Route Withdrawal . . . . . . . . . . . . . . . . . . 23 6.4.3. Path Attribute Change and Best-Path Change . . . . . 23 6.4.4. BGP Peer Down . . . . . . . . . . . . . . . . . . . . 23 6.4.5. BGP Peer Up with Full Table . . . . . . . . . . . . . 23 6.4.6. Physical Link Failure . . . . . . . . . . . . . . . . 24 6.4.7. Policy Change and Route Refresh . . . . . . . . . . . 24 6.4.8. Next-Hop or IGP Metric Change . . . . . . . . . . . . 24 6.5. Sustained Churn and Loss-Free Churn Rate . . . . . . . . 24 6.6. Impact of BMP on BGP Convergence . . . . . . . . . . . . 25 6.7. Scaling with the Number of Monitoring Views . . . . . . . 25 6.8. Scaling of the Adj-RIB-Out Views . . . . . . . . . . . . 26 6.9. Scaling with the Number of BMP Stations . . . . . . . . . 27 6.10. Effect of the Collector (Sink versus Processing Station) . . . . . . . . . . . . . . . . . . . . . . . . 27 6.11. BMP TCP Backpressure and Buffer Behavior . . . . . . . . 28 7. Reporting Format . . . . . . . . . . . . . . . . . . . . . . 29 7.1. DUT and Test Bed Description . . . . . . . . . . . . . . 29 7.2. Test Configuration . . . . . . . . . . . . . . . . . . . 29 7.3. Results . . . . . . . . . . . . . . . . . . . . . . . . . 30 8. Security Considerations . . . . . . . . . . . . . . . . . . . 31 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 32 10.1. Normative References . . . . . . . . . . . . . . . . . . 32 10.2. Informative References . . . . . . . . . . . . . . . . . 33 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 33 1. Introduction The BGP Monitoring Protocol (BMP) [RFC7854] allows a monitored router to stream its BGP state, over a TCP connection, to one or more BMP stations. The base protocol has been extended to cover the Adj-RIB- Out [RFC8671] and the Loc-RIB [RFC9069], and additional statistics have been defined [RFC9972]. Operators use the resulting feed for troubleshooting, anomaly detection, auditing, and increasingly as real-time input to automated traffic engineering and path computation systems. Benchmarking methodologies exist for BGP control-plane convergence [RFC4098] and BGP data-plane convergence [RFC7747]. These documents measure how fast a router processes routing changes and updates its forwarding state. They say nothing about how fast the same router tells a BMP station about those changes. BMP is an observer of BGP, Srivastava Expires 20 May 2027 [Page 3] Internet-Draft BMP Convergence Benchmarking November 2026 but it is also a consumer of the router's control-plane resources and, through TCP backpressure, a potential source of interference with BGP itself. 1.1. Motivation No published standard describes how to benchmark the performance or scale of a BMP implementation. The IETF has standardized the BMP data formats and state reporting, but the performance of BMP implementations across vendors is not characterized in a uniform way. In practice, operators and vendors each build their own private test plans, which makes results incomparable. Telemetry protocols have historically been treated as secondary management-plane functions rather than core routing functions. That view no longer holds. Automated systems now make routing and traffic engineering decisions based on BMP data, and the usefulness of those decisions depends on how fresh and how complete the BMP feed is. Operators therefore need answers to questions such as: * After a router reboots or a BMP session is (re)established, how long until a collector has a complete view of the router's tables? * During a routing event or a routing churn period, how far behind the router's real BGP state is the BMP feed? * Does enabling BMP, or enabling more BMP monitoring views or more BMP stations, slow down BGP convergence or exhaust control-plane resources? * What happens to the router when a BMP collector cannot keep up and the TCP connection applies backpressure? * How fast can a collector itself absorb the feed when it does real work with it, such as storing it in a database? A common methodology allows these questions to be answered consistently, and allows different implementations to be compared under the same conditions. 1.2. Scope This document defines a methodology for benchmarking, in a laboratory environment, the following aspects of a BMP-capable router acting as the Device Under Test (DUT): * Initial dump speed for each BMP monitoring view. Srivastava Expires 20 May 2027 [Page 4] Internet-Draft BMP Convergence Benchmarking November 2026 * BMP convergence after BGP events, and during churn. * Impact of BMP on BGP convergence and on control-plane resources. * Scaling with the number of enabled monitoring views, the Adj-RIB- Out scale (number of peers advertised to), and the number of BMP stations. * Behavior with a slow or stalled BMP station (TCP backpressure). The following are out of scope: the correctness of the BMP encoding, the BMP Route Mirroring function, the benchmarking of BMP collector products as such (except as needed to isolate the DUT from collector effects), the accuracy of router-internal clocks, and data-plane convergence. The methodology is intended for controlled laboratory use only. 1.3. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. 2. Terminology 2.1. Terms Defined Elsewhere This document does not redefine existing terms. The following terms are used as defined in the referenced documents. * Monitored Router, BMP Station, Initiation Message, Peer Up Notification, Peer Down Notification, Route Monitoring Message, Statistics Report, Termination Message, Per-Peer Header, and Adj- RIB-In (pre-policy and post-policy): [RFC7854]. The terms "producer" and "collector" are used in some documents as synonyms for "Monitored Router" and "BMP Station" [RFC9972]; this document uses "BMP Station". * Adj-RIB-Out (pre-policy and post-policy): [RFC8671]. * Loc-RIB and the Loc-RIB Instance Peer Type: [RFC4271] and [RFC9069]. * End-of-RIB marker: [RFC4724]. Srivastava Expires 20 May 2027 [Page 5] Internet-Draft BMP Convergence Benchmarking November 2026 * Route packing, route mixture, minimal policy, and BGP control- plane convergence: [RFC4098]. * Device Under Test (DUT) and benchmarking terminology in general: [RFC1242], [RFC2544], and [RFC7747]. 2.2. Terms Defined in This Document Monitoring View (View): One of the five BMP-exportable RIB views. The abbreviations in Table 1 are used throughout this document. Peering Router (PR): A router, or a tester emulating a router, that establishes BGP sessions with the DUT and generates or receives BGP routes. Test Controller: The entity that orchestrates the test, provides the reference clock, triggers events, and records measurements. Sink Station: A BMP Station that accepts the TCP connection, acknowledges all data promptly and discards the content, without doing any processing that could create backpressure (see Section 3.3). Processing Station: A BMP Station that performs real collector work with the feed, for example parsing it fully and storing it in a database or forwarding it to a message bus. Trigger: The stimulus that starts a measurement, for example the start of a BMP session, an UPDATE burst, a BGP session reset, or a link failure. Reference State: For a given View and a given moment, the exact set of routes (and attributes, as relevant) that the DUT is expected to export through BMP. Because the Test Controller generates all BGP stimuli, it knows the Reference State without needing to query the DUT. View State: The state of a View as reconstructed by a BMP Station by applying the received Route Monitoring and Peer Down messages. Srivastava Expires 20 May 2027 [Page 6] Internet-Draft BMP Convergence Benchmarking November 2026 BMP Convergence: The condition in which the View State of a given View, for all monitored peers and AFI/SAFIs, is equal to the Reference State following a Trigger and remains equal until the next Trigger. BMP Convergence Time (BCT): The time from a Trigger until BMP Convergence is reached for a given View. BMP Initial Dump: The set of Route Monitoring messages that a DUT generates to report the existing content of a View after a BMP session is established (or a View is enabled on an established session). BMP Initial Dump Time (BIDT): The time from the start of the BMP Initial Dump until BMP Convergence for that View (see Section 5). BMP Event Latency (BEL): For a single event, the time from the moment the event is injected by the Test Controller until the BMP message that reports that event is received by the BMP Station. An event is either a route event (announcement, withdrawal, attribute change) or a BGP session event (session down, session up). Quiescence Interval (QI): A configured period without any BMP message from the DUT, used by some completion-detection methods. BGP Propagation Time (BPT): The time for a routing event injected at one Peering Router to be re-advertised by the DUT and observed at another Peering Router. This is the control-plane convergence metric used as the reference for measuring the impact of BMP on BGP (see [RFC4098]). Loss-Free Churn Rate (LFCR): The highest sustained BGP event rate at which BMP Convergence is reached, with no BMP message loss, no BMP session reset, and a bounded BEL. Receive-Only Peer: A Peering Router that has a BGP session with the DUT and receives the DUT's advertisements, but advertises no routes to the DUT. It adds to the Adj-RIB-Out scale without changing the Adj-RIB-In or Loc-RIB scale. Srivastava Expires 20 May 2027 [Page 7] Internet-Draft BMP Convergence Benchmarking November 2026 BMP Fan-Out: For a single routing event and a given View, the number of BMP messages that the DUT generates to report the event (see Section 5.4). +==============+==========================+============+ | Abbreviation | Monitoring View | Defined in | +==============+==========================+============+ | IN-PRE | Adj-RIB-In, pre-policy | [RFC7854] | +--------------+--------------------------+------------+ | IN-POST | Adj-RIB-In, post-policy | [RFC7854] | +--------------+--------------------------+------------+ | LOC | Loc-RIB | [RFC9069] | +--------------+--------------------------+------------+ | OUT-PRE | Adj-RIB-Out, pre-policy | [RFC8671] | +--------------+--------------------------+------------+ | OUT-POST | Adj-RIB-Out, post-policy | [RFC8671] | +--------------+--------------------------+------------+ Table 1: Monitoring Views and Abbreviations 3. Test Setup 3.1. Reference Topology The reference topology has three types of nodes: the DUT, one or more Peering Routers, and a BMP Station. A Test Controller, which may be implemented in the same tester as the Peering Routers and the BMP Station, provides time reference and orchestration. +-----------------+ | Test Controller | | (clock, trigger,| | measurement) | +--+----+------+--+ | | | +--------------+ | +--------------+ | | | +-------+-------+ +-------+-------+ +---------+-----+ | Peering | | DUT | | BMP Station | | Router(s) |<->| (Monitored |-->| (Sink or | | PR-1..PR-n | | Router) | | Processing) | +---------------+ +---------------+ +---------------+ BGP sessions BMP over TCP Figure 1: Reference Topology Srivastava Expires 20 May 2027 [Page 8] Internet-Draft BMP Convergence Benchmarking November 2026 The Peering Routers establish the BGP sessions to the DUT, inject routes and events, and receive the DUT's advertisements. The BGP sessions and the BMP session MAY use different interfaces. The BMP TCP session is initiated by the DUT toward the BMP Station, as defined in [RFC7854]. A Peering Router may be a real router or an emulation function of a tester. Using a tester is RECOMMENDED because it allows precise control of route generation and timestamping. 3.2. Multiple BMP Stations For the tests that scale the number of BMP stations (Section 6.9), the topology in Figure 2 is used. All stations are configured on the DUT with the same monitoring views, unless the test case specifies otherwise. +-----------------+ +--->| BMP Station 1 | +---------------+ +---------+ | +-----------------+ | Peering | | |----+ | Router(s) |<->| DUT |--------> ... | PR-1..PR-n | | |----+ +---------------+ +---------+ | +-----------------+ BGP sessions +--->| BMP Station M | +-----------------+ BMP over TCP (one per station) Figure 2: Topology with Multiple BMP Stations 3.3. BMP Station Types and Measurement Points A principal goal of the methodology is to separate the performance of the DUT from the performance of the collector. The BMP Station therefore has to be able to operate in two modes. Sink Station: The Sink Station is used to measure the true BMP export performance of the DUT. It MUST NOT cause TCP backpressure under any load in the test. Three levels of processing are defined, in increasing order of cost: * Level 0 (raw): the station reads and discards the TCP byte stream. Timestamps are taken from a packet capture on the Test Controller's interface (see Section 3.4) and the messages are decoded offline after the test. This level is RECOMMENDED for all benchmarks whose purpose is to measure the DUT. Srivastava Expires 20 May 2027 [Page 9] Internet-Draft BMP Convergence Benchmarking November 2026 * Level 1 (framing): the station parses only the BMP Common Header and the Per-Peer Header, and records message type, peer, and arrival time in memory. * Level 2 (decode): the station fully decodes each message in memory, to count and verify routes online. No disk or network I/O is permitted in the receive path. Processing Station: The Processing Station is used to measure the effect of a realistic collector on the system. It does the real work, for example storing the feed in a database, and is therefore allowed to create backpressure. The nature of the processing (decoding, storage engine, hardware, and so on) MUST be fully described in the report. Unless a test case states otherwise, it MUST be performed with a Sink Station first, and MAY be repeated with a Processing Station (see Section 6.10). A Sink Station MUST have its TCP receive buffers sized so that it never advertises a closed window during a test, except in the backpressure test (Section 6.11), where the window is manipulated on purpose. 3.4. Time Reference and Timestamping All timestamps used to compute the metrics in this document MUST be taken by the Test Controller, from a single clock, or from multiple clocks synchronized to a common reference. The synchronization uncertainty MUST be at least an order of magnitude smaller than the smallest time reported and MUST be documented. Timestamps carried in BMP messages, such as the timestamp in the Per-Peer Header, are produced by the DUT's clock and MAY be recorded for diagnostic purposes, but MUST NOT be used to compute the benchmark metrics defined here. The two principal observation points are: Injection timestamp (T_inj): The time at which the first byte of the BGP UPDATE (or other BGP message or physical event) that constitutes the Trigger leaves the Peering Router. For a bulk event this is the time of the first UPDATE; the time of the last UPDATE is also recorded (T_inj_last). For BMP-session Triggers, it is the time at which the TCP SYN from the DUT arrives at the BMP Station (T_syn) and, when available, the time at which the BMP configuration was committed on the DUT (T_cfg). Srivastava Expires 20 May 2027 [Page 10] Internet-Draft BMP Convergence Benchmarking November 2026 Reception timestamp (T_rx): The time at which the last TCP segment carrying a given BMP message arrives at the BMP Station's interface. A hardware or packet-capture timestamp is RECOMMENDED; application-layer timestamps are acceptable only if their error is documented. 4. Test Considerations This section lists the parameters that have to be fixed, or at least documented, for every test. The default values define the "Basic Configuration". Each test case in Section 6 uses the Basic Configuration, and then adds its own configuration and Trigger. 4.1. Number of Peers, Address Families, and Routes The following scale profiles are defined. The Basic Profile is REQUIRED for all tests. The numbers are initial recommendations and are expected to evolve with the operational state of the art. Srivastava Expires 20 May 2027 [Page 11] Internet-Draft BMP Convergence Benchmarking November 2026 +======================+=====================+=====================+ | Parameter | Basic Profile | Full-Table Profile | | | (REQUIRED) | (OPTIONAL) | +======================+=====================+=====================+ | BGP peers | 10 eBGP | 4 eBGP | +----------------------+---------------------+---------------------+ | Address families | IPv4 unicast, IPv6 | IPv4 unicast, IPv6 | | | unicast | unicast | +----------------------+---------------------+---------------------+ | IPv4 routes per peer | 100,000 (unique per | approx. 1,000,000 | | | peer) | (same prefixes on | | | | all peers) | +----------------------+---------------------+---------------------+ | IPv6 routes per peer | 20,000 (unique per | approx. 200,000 | | | peer) | (same prefixes on | | | | all peers) | +----------------------+---------------------+---------------------+ | Resulting Adj-RIB-In | 1,000,000 IPv4 and | approx. 4,000,000 | | paths | 200,000 IPv6 | IPv4 and 800,000 | | | | IPv6 | +----------------------+---------------------+---------------------+ | Resulting Loc-RIB | 1,000,000 IPv4 and | approx. 1,000,000 | | routes | 200,000 IPv6 | IPv4 and 200,000 | | | | IPv6 | +----------------------+---------------------+---------------------+ | Routes advertised by | 100,000 IPv4 and | approx. 250,000 | | the DUT to each peer | 20,000 IPv6 (the | IPv4 and 50,000 | | (post-policy Adj- | routes learned from | IPv6 (one quarter | | RIB-Out per peer) | one other peer) | of the Loc-RIB, | | | | selected by prefix) | +----------------------+---------------------+---------------------+ | Resulting post- | 1,000,000 IPv4 and | approx. 1,000,000 | | policy Adj-RIB-Out | 200,000 IPv6 | IPv4 and 200,000 | | paths, all peers | | IPv6 | +----------------------+---------------------+---------------------+ Table 2: Scale Profiles The report MUST give the route mixture (prefix length distribution), route packing (prefixes per UPDATE) and the AS_PATH length distribution, as defined in [RFC4098]. The time sequence in which multiple peers advertise their routes MUST be documented. When more than one eBGP peer advertises the same prefix, the policy MUST make the best path deterministic, so that the Reference State is known in advance. Srivastava Expires 20 May 2027 [Page 12] Internet-Draft BMP Convergence Benchmarking November 2026 The scale of the Adj-RIB-Out views (OUT-PRE and OUT-POST) is the number of routes the DUT advertises to its BGP peers, and it is independent of the Adj-RIB-In scale. It is the product of the number of peers that receive routes and the number of routes advertised to each of them. In Table 2, the outbound policy advertises to each peer a fixed subset of the Loc-RIB, called the advertised set of that peer, so that the total of the post-policy Adj-RIB-Out is of the same order as the total of the Adj-RIB-In. In the Basic Profile, the advertised set of peer i is the set of routes learned from peer (i+1), the last peer wrapping around to the first. In the Full- Table Profile, the Loc-RIB is split by prefix into four equal parts, and each peer is advertised one of them. The advertised sets MUST be documented. The advertised sets MUST NOT contain a route learned from the peer it is advertised to. OUT-POST contains the advertised sets. OUT-PRE is the result before the outbound policy is applied and, as defined in [RFC8671], it normally matches the Loc-RIB, so it can be larger than OUT-POST, up to the size of the Loc-RIB for each peer. The size of OUT-PRE as reported by the DUT MUST be documented, and the Reference State of OUT-PRE is the content that the DUT is expected to report for it. With an outbound policy that additionally rejects a fraction of the advertised set, OUT-POST is smaller by the rejection ratio. Because the Adj-RIB-Out size grows with the number of receiving peers, and not with the Loc-RIB size, the tests that involve OUT-PRE and OUT-POST SHOULD be repeated with a varying number of peers that only receive routes (they advertise nothing to the DUT), to measure the effect of the Adj-RIB-Out scale alone, as specified in Section 6.8. The number of such receive-only peers MUST be documented. 4.2. Policy The DUT MUST be tested first with the minimal policy defined in [RFC4098], modified as follows so that the pre-policy and post-policy views carry different information: * The inbound policy accepts all routes and modifies at least one attribute (for example, sets LOCAL_PREF or adds a community). * The outbound policy accepts only the advertised set of the peer (see Section 4.1) and modifies at least one attribute (for example, AS_PATH prepending). Srivastava Expires 20 May 2027 [Page 13] Internet-Draft BMP Convergence Benchmarking November 2026 Additional runs MAY use policies that reject a fraction of the routes. The rejection ratio MUST then be documented, and the Reference State for IN-POST and OUT-POST MUST be adjusted accordingly. The policy settings MUST be fully documented and MUST be identical across all iterations of a test. 4.3. Configured Parameters The parameters in [RFC7747] that influence BGP behavior (keepalive timer, hold time, update delay timer, ConnectRetry timer, MRAI, MAOI, route flap damping, TCP segment size, TCP authentication, MTU) apply here too. The values recommended in Section 4.4 of [RFC7747] are the Basic Configuration defaults. In addition, the following BMP-related parameters MUST be documented, and MUST remain constant across iterations: * The set of Views enabled on each BMP session, and the set of monitored peers. * Any BMP statistics reporting interval and the list of Statistics Report types enabled. * BMP TCP parameters: local/remote ports, MSS, send buffer size, receive window of the station, any BMP-specific buffering or queue limit configured on the DUT, and the BMP session reconnect timer. * Any BMP rate limiting, batching, or throttling feature configured on the DUT. These features SHOULD be disabled in the Basic Configuration; if they cannot be disabled, their settings MUST be reported. * Whether BMP is carried over an in-band or out-of-band (management) interface. * Whether any transport security or TCP authentication is used with the BMP session. If used, it MUST be applied to all iterations of a test and to its baseline. The effect of any such mechanism can be assessed by repeating a test with and without it. 4.4. Tracing, Logging, and Other Processes Debug tracing and verbose logging on the DUT, and on the BMP Station (other than what is needed to record the measurement), MUST be disabled during all tests, as they can have a significant effect on timing. Any logging that cannot be disabled MUST be documented. Srivastava Expires 20 May 2027 [Page 14] Internet-Draft BMP Convergence Benchmarking November 2026 The DUT MUST be loaded only with the configuration necessary for the test. Unless a test case says otherwise, all other routing protocols MUST have converged and be stable before the Trigger, and no configuration change, software upgrade, or management query that is not part of the measurement is allowed during the test. Management access used to collect CPU and memory samples (see Section 5.7) MUST be documented, since it too consumes control-plane resources. 4.5. High Availability As in [RFC7747], redundancy features of the routing engine (for example, non-stop routing) SHOULD be disabled. If they cannot be, the results may not be comparable with other devices and that MUST be stated in the report. 4.6. Repeatability and Statistics Each test MUST be repeated at least 10 times, with identical configuration, starting from the same initial state. For every metric the report MUST give the minimum, maximum, mean, median, and standard deviation. For per-event metrics such as BEL, the 95th and 99th percentiles over all events and all iterations MUST also be given. Outlier handling MUST be documented, and no result may be silently dropped. 5. Metrics and Measurement Methods 5.1. BMP Convergence Time BMP Convergence Time for a View is: BCT(view) = T_converged(view) - T_inj where T_converged is the time at which the View State first equals the Reference State (and stays equal), observed using one of the methods in Section 5.6. When the Trigger is a bulk event, T_inj is the time of the first message of the stimulus; the report SHOULD also give BCT measured from T_inj_last. The BCT is reported separately for each View, each peer, and each AFI/SAFI, as well as for the whole DUT (the maximum over all of them). 5.2. BMP Initial Dump Time and Dump Rate BIDT(view) = T_complete(view) - T_init Dump Rate(view) = N_routes(view) / BIDT(view) [routes per second] Srivastava Expires 20 May 2027 [Page 15] Internet-Draft BMP Convergence Benchmarking November 2026 where T_init is the time the Initiation message is received by the BMP Station, T_complete is the time at which the dump is determined to be complete by one of the methods in Section 5.6, and N_routes is the number of route entries in the Reference State for the View. When T_syn and T_cfg are available, the report SHOULD also give the start-up delays (T_init - T_syn) and (T_syn - T_cfg), because they may account for a significant portion of the time to visibility. 5.3. BMP Event Latency BEL(e) = T_rx(m(e)) - T_inj(e) where m(e) is the first BMP message that reports event e itself: * Route event: m(e) is the first Route Monitoring message reporting that route change in the View under test. BEL is reported per View. * Session event: m(e) is the Peer Down or Peer Up Notification for that peer. It reports session state independent of the Views [RFC8671], so BEL is reported once per event and peer, not per View. The BEL of a session event measures only the delay of the Peer Down or Peer Up Notification. It does not include the delay of any route changes that the session event causes. Those are separate route events, measured per View as above, and MUST NOT be reported as the BEL of the session event. A Peer Down Notification implicitly withdraws all routes associated with the peer, and an implementation MAY omit explicit withdrawals [RFC7854]. The View State is computed by treating a Peer Down Notification as the withdrawal of all routes of that peer. The report MUST state whether explicit withdrawals were observed. Each event that is injected MUST be identified. Before an announcement is sent, the Test Controller SHOULD stamp it with a sequence value, which is a unique, monotonically increasing number carried in an attribute that is preserved by the configured policies (for example, a BGP Large Community [RFC8092]). The sequence value allows each Route Monitoring message to be traced back to the event that caused it, and allows loss, duplication, and re-ordering to be identified even during churn. Withdrawals are correlated by prefix and by their time relative to the event. If the DUT removes or rewrites the stamp in some Views, the correlation method MUST be documented. Srivastava Expires 20 May 2027 [Page 16] Internet-Draft BMP Convergence Benchmarking November 2026 5.4. BMP Fan-Out and Per-Peer Spread One routing event can lead to several BMP messages, in particular in the Adj-RIB-Out Views, where each receiving peer has its own Adj-RIB- Out and is reported with its own Per-Peer Header [RFC8671]. For an event e and a View: Fan-Out(e) = number of BMP messages generated for e Spread(e) = T_rx(last message for e) - T_rx(first message for e) Fan-Out is counted per View and per peer. Spread shows how unevenly the DUT serves the peers, and it is the difference between the BEL of the last peer and of the first peer reported. Both MUST be reported for the tests in Section 6.8, and SHOULD be reported for all event tests that involve the Adj-RIB-Out Views. 5.5. BGP Propagation Time and BMP Overhead To determine the effect of BMP on BGP convergence, the BPT of the DUT is measured with BMP disabled (BPT_off) and with BMP enabled (BPT_on), for the same event. BMP Overhead (absolute) = BPT_on - BPT_off BMP Overhead (relative) = (BPT_on - BPT_off) / BPT_off BPT is measured at the Peering Routers as defined in [RFC4098]: from the injection of the event at the source Peering Router to the receipt of the corresponding UPDATE at the destination Peering Router. 5.6. Detecting Completion of a Dump or of Convergence A dump or a convergence period is complete when the BMP Station has received everything that it is supposed to receive. This is not trivial to detect externally. The following methods are defined. The method used MUST be reported. More than one method SHOULD be applied to the same run and the results compared. 5.6.1. Method A: Reference-State Completeness (Primary) The Test Controller knows the Reference State. T_complete is the time T_rx of the BMP message by which the View State first equals the Reference State. This requires the decoding of every BMP message, in the receive path (Sink Station Level 2) or offline from a packet capture (Level 0). This method does not depend on any signal sent by the DUT, and is therefore the REQUIRED reference method for steady- state tests. It also detects routes that are missing, duplicated, or stale. The method applies to churn, too, as long as the Reference Srivastava Expires 20 May 2027 [Page 17] Internet-Draft BMP Convergence Benchmarking November 2026 State is defined at each point in time from the sequence-stamped events. 5.6.2. Method B: End-of-RIB Markers T_complete is the time of the last End-of-RIB marker [RFC4724], carried in a BMP Route Monitoring message, for all monitored peers and AFI/SAFIs in the View. BIDT is then measured from the Initiation message to this marker. *Caveat:* The End-of-RIB marker is generated by BGP and it may be generated as soon as the BGP process has finished enumerating a table, and not when the BMP messages for that table have actually been serialized and written to the TCP socket. An implementation can send an End-of-RIB marker before the dump is complete or, in some cases, not send it at all. The EoR time therefore has to be regarded as an indication, or at most as a lower bound, and MUST be checked against Method A before it is reported as a dump time. A result obtained only through Method B MUST be labeled as such. 5.6.3. Method C: Quiescence of the BMP Stream T_complete is the time of the last Route Monitoring message before a period of at least one Quiescence Interval (QI) in which the DUT sends no Route Monitoring message. The report MUST give the QI, and the computed times MUST NOT include it. This method is suitable only for steady-state tests with no background churn, because any churn would reset the quiescence period. A DUT that pauses during a dump (for example because it is yielding the CPU) for longer than QI would give a false completion time; therefore QI SHOULD be chosen larger than the longest observed intra-dump pause. 5.6.4. Method D: Control-Plane CPU In steady state, with BMP being the only activity on the DUT, the dump appears as a rise of the CPU utilization (of the routing engine or of the process or processes responsible for BMP) above its baseline. T_complete is the time at which the utilization comes back within a tolerance of the pre-test baseline and remains there for a hold time. The baseline, tolerance, hold time, sampling method, and sampling interval MUST be documented. This method does not depend on BMP messages, but its resolution is limited by the sampling interval, and it is not suitable when other protocols, or BGP churn, are contributing to the CPU load. It SHOULD be used as a cross-check only. Srivastava Expires 20 May 2027 [Page 18] Internet-Draft BMP Convergence Benchmarking November 2026 5.6.5. Method E: Canary Routes (for Churn Conditions) When a dump or convergence period happens during churn, the methods B, C, and D are not reliable. In this case, in addition to Method A, the Test Controller injects canary routes: uniquely-identified routes, on a dedicated set of prefixes and at a low rate (for example one per second per View), from the start of the test. The BEL of the canary routes shows the delay in the BMP export pipeline at that point in time. When the BMP export queue is FIFO, the BEL of a canary equals the time it takes to drain the backlog that was in front of it. Canary routes MUST be included in the Reference State, and the churn level in which they were measured MUST be reported. Whether the DUT delivers BMP messages in strict order is implementation-specific, and so canary measurements describe the latency of the pipeline, not necessarily the dump completion time. 5.6.6. Precondition Verification with Statistics Reports Before each run, the Test Controller MUST verify that the DUT holds the expected state, i.e. that the Reference State matches the DUT. The counts in the DUT's BGP tables, as read through the management interface, and optionally, the Statistics Report counters [RFC7854] [RFC9972], can be used for that purpose. These counters report what the DUT holds, and not what the DUT has exported over BMP, so they MUST NOT be used as a measure of completeness of the BMP feed. 5.7. Resource and Stability Metrics For each run, the following DUT-side quantities MUST be collected at a documented sampling interval, with minimal impact on the DUT: * CPU utilization of the control plane, overall and, if available, of the BGP and the BMP processes, and peak value during the test. * Memory utilization of the control plane, overall and, if available, of the BGP and the BMP processes; peak value and value after the test. * Time for the CPU utilization to return to the baseline after the Trigger. * The number of BGP session flaps (any session reset, any Notification, any hold timer expiry) and the number of BMP session resets during the test. Both MUST be zero for a test to be considered successful, unless the test is intended to cause them. * The BMP queue depth, drop counters, or any similar BMP internal counters that the DUT exposes. Srivastava Expires 20 May 2027 [Page 19] Internet-Draft BMP Convergence Benchmarking November 2026 5.8. Scaling Metrics When a test is repeated while varying a scaling parameter (the number of Views, the number of receiving peers, or the number of BMP Stations), the following are reported, where X(k) is a benchmark metric (BCT, BIDT, peak CPU, ...) at k units of the parameter: Scaling Ratio SR(k) = X(k) / X(1) Incremental Cost IC(k) = X(k) - X(k-1) SR(k) = 1 means that the parameter has no effect, SR(k) = k means that cost increases linearly with k (each additional unit is as expensive as the first), SR(k) less than k indicates that a part of the work is shared (for example, a single route lookup used for several Views or stations), and SR(k) greater than k indicates a super-linear degradation (for example, contention for a common queue or memory). The report MUST present the whole series X(1)..X(K) and MAY include a fitted curve. 6. Test Cases All test cases start from the Basic Configuration described in Section 3 and Section 4, and use the Sink Station (Level 0 or Level 2) unless stated. Unless otherwise noted, every test case is performed once for each of the five Views in Table 1, with that View alone enabled, and in addition for the combinations specified in Section 6.7. 6.1. Common Procedure 1. Configure the DUT, the Peering Routers, and the BMP Station as in the Basic Configuration. Disable BMP (or, for event tests, configure BMP as required by the test case). 2. Establish all BGP sessions and have the Peering Routers advertise their routes. Verify that the DUT holds the Reference State (Section 5.6.6). 3. Wait until the DUT is in a stable state: no BGP messages are exchanged other than keepalives, and the CPU and memory utilization have been constant within the tolerance for a hold time. Record the baseline. 4. Start packet capture and resource sampling. 5. Apply the Trigger of the test case and record T_inj. Srivastava Expires 20 May 2027 [Page 20] Internet-Draft BMP Convergence Benchmarking November 2026 6. Wait for BMP Convergence by the methods that apply (Section 5.6), then for the resource utilization to be back to the baseline. 7. Verify that the View State equals the Reference State and record any deviation (missing, duplicate, stale, or out-of-order routes). 8. Record the metrics in Section 5, restore the initial state, and repeat the test (Section 4.6). 6.2. Initial Dump in Steady State 6.2.1. Single-View Initial Dump *Objective:* Measure the BIDT and the Dump Rate of the DUT for each View, when BMP is the only activity. *Procedure:* BMP is disabled at the start. The Trigger is the commit of the BMP configuration that enables a single View toward one Sink Station. Perform the Common Procedure for each View. Measure BIDT by Methods A (REQUIRED), and B, C, and D (RECOMMENDED), and report all of them. Also report the time from T_cfg to T_syn to T_init. *Reporting:* BIDT and Dump Rate per View, per AFI/SAFI, per method; resource peak values; any difference between the methods and its probable cause (for example, an EoR sent before the dump is complete). 6.2.2. Initial Dump after BMP Session Re-establishment *Objective:* Measure the time to visibility after a BMP session failure on an otherwise unchanged DUT. *Procedure:* The BMP session is established and converged. The Trigger is the abrupt closure of the TCP connection by the BMP Station (TCP reset), followed by the Station accepting a new connection. Measure T_syn and the resulting BIDT. The DUT's BMP reconnect behavior (timer, backoff) MUST be documented, and the delay between the reset and T_syn reported separately from BIDT. Repeat with a graceful close, if the implementation supports it. 6.2.3. Time to Visibility after DUT Restart *Objective:* Measure the time to complete visibility after a restart of the DUT. This is the main figure for traffic-engineering controllers. Srivastava Expires 20 May 2027 [Page 21] Internet-Draft BMP Convergence Benchmarking November 2026 *Procedure:* BMP and BGP are both configured in the startup configuration. The Trigger is the restart of the routing software (or a reload) of the DUT. Record the time at which each BGP session is established, the time of the Initiation message, and the BIDT. Report the time from the restart Trigger to BMP Convergence, and the part of it that is attributable to BGP convergence (for example, the time for the last BGP session to reach established state, and to receive its EoR). This test is OPTIONAL. 6.3. Initial Dump during Churn *Objective:* Measure the BIDT when the DUT is concurrently processing BGP changes. *Procedure:* A set of Peering Routers generates background churn (a continuous, repeating series of announcements and withdrawals of routes that are not part of the dump verification set, or that are sequence-stamped) at a rate R. The tests are run for R of 0 (as in Section 6.2.1) and at increasing rates, up to, at least, the LFCR found in Section 6.5. While the churn is in progress, the Trigger of Section 6.2.1 is applied. Methods A and E are REQUIRED; B and D are not reliable under churn, but MAY be reported, with that statement. *Reporting:* BIDT as a function of R, the canary BEL distribution over time, and the time-to-drain of the backlog after the churn stops. 6.4. BMP Convergence after BGP Events For the tests in this section BMP is already established and in sync, with the View or Views under test enabled, before the Trigger. For each test, T_inj, BCT (from T_inj and from T_inj_last), and BEL distribution are reported for each enabled View. 6.4.1. Route Advertisement A Peering Router advertises N new routes (N = 1, 1,000, 10,000, 100,000), in a single burst, to the DUT. IN-PRE, IN-POST, and LOC views show the new routes; OUT-PRE is expected to show them for all peers other than the sender, and OUT-POST only for the peers whose advertised set includes them. Srivastava Expires 20 May 2027 [Page 22] Internet-Draft BMP Convergence Benchmarking November 2026 6.4.2. Route Withdrawal A Peering Router withdraws N routes in a burst (N as above). The BMP convergence for the Adj-RIB-In view is the time at which the withdrawals are reported; for LOC, OUT-PRE and OUT-POST, the time at which the resulting changes are reported (withdrawals, or replacement by alternative paths where available). 6.4.3. Path Attribute Change and Best-Path Change A Peering Router re-advertises N routes with changed attributes. Two cases are tested: (a) the change does not affect the best path (visible in IN-PRE and IN-POST only); and (b) the change makes the route the new best path (visible in all Views). Case (b) requires a second path to the same prefixes, from another Peering Router, and the Full-Table profile has this by construction. 6.4.4. BGP Peer Down The Trigger is the loss of one BGP session (hard reset from the Peering Router, or session shutdown by the Test Controller). Measure and report separately: a. Session event: the BEL of the Peer Down Notification, with its reason code. This is a single-message result. b. Route events caused by the session event: for LOC, and for OUT- PRE and OUT-POST of the other peers, the BEL, BCT and Fan-Out of the resulting withdrawals or replacements. For IN-PRE, IN-POST and the failed peer's own Adj-RIB-Out Views, the Peer Down Notification itself removes the routes, so BCT equals the BEL in (a). If explicit withdrawals follow, BCT is the arrival of the last one. Results (a) and (b) measure different things and MUST NOT be compared or added. 6.4.5. BGP Peer Up with Full Table The Trigger is the establishment of an additional BGP session, on which the Peering Router advertises its full set of routes. Measure the BEL of the Peer Up Notification (session event). Report the BIDT and BCT of the Views for that peer separately, as route-level results. This test measures the dump of one peer in the middle of normal operation, as opposed to the dump of the entire router in Section 6.2. Srivastava Expires 20 May 2027 [Page 23] Internet-Draft BMP Convergence Benchmarking November 2026 6.4.6. Physical Link Failure The Trigger is the failure of the physical link between the DUT and a Peering Router (carrier loss at the tester). The DUT's interface failure detection timer MUST be documented (see [RFC7747]). The measured BCT includes the failure detection time; the report SHOULD give the point where the DUT detected the event, if it can be observed. 6.4.7. Policy Change and Route Refresh The Trigger is a change of the inbound or outbound policy on the DUT that changes the post-policy content of N routes, or the sending of a Route Refresh request by a Peering Router. The test applies primarily to IN-POST, LOC, and OUT-POST; the IN-PRE and OUT-PRE views are expected not to change for a policy-only change, and it SHOULD be verified and reported that no messages are sent for them. 6.4.8. Next-Hop or IGP Metric Change This test is OPTIONAL. The Trigger is a change to the IGP metric or reachability of the BGP next hop, which changes the best path for N routes without any BGP message from a Peering Router. This is visible only in the LOC and the Adj-RIB-Out Views. A Peering Router or the Test Controller emulates the IGP change. 6.5. Sustained Churn and Loss-Free Churn Rate *Objective:* Determine the highest event rate that the BMP export keeps up with, and how it degrades beyond. *Procedure:* With BMP established and in sync, the Peering Routers generate a sustained stream of sequence-stamped announcements, withdrawals, and attribute changes at rate R (events per second, summed over all peers), for a duration D (at least 5 minutes). R is increased in steps (a binary search is RECOMMENDED) between 0 and the rate at which BGP itself stops converging. For each R, record: BEL distribution; the number of events not reported (lost), reported more than once, or reported out of order; BMP and BGP session stability; resource utilization; and the time after the stop of the churn at which BMP Convergence is reached (backlog drain time). *Reporting:* The LFCR for each View (and for all Views together), plus the curves of BEL percentiles, CPU, and backlog drain time as functions of R. A rate is loss-free only if no event is lost, no session resets, and the BEL at the 99th percentile is stable over time (no unbounded growth). Srivastava Expires 20 May 2027 [Page 24] Internet-Draft BMP Convergence Benchmarking November 2026 The churn profile (the share of announcements, withdrawals, and attribute changes; whether it is spread uniformly or in bursts; and the number of peers it comes from) MUST be documented. 6.6. Impact of BMP on BGP Convergence *Objective:* Determine whether, and by how much, enabling BMP slows down the DUT's BGP convergence. *Procedure:* Select one or more of the events from Section 6.4, and the sustained churn of Section 6.5 at a fixed rate. For each, measure the BPT with BMP disabled (BPT_off), then with each View enabled individually and with all Views enabled, to a Sink Station (BPT_on). Keep everything else equal. Repeat with the Processing Station. The test is also performed with all Views enabled at the largest Adj-RIB-Out scale of Section 6.8. *Reporting:* BPT_off, BPT_on, and BMP Overhead (Section 5.5), CPU and memory impact, and any BGP session instability. 6.7. Scaling with the Number of Monitoring Views *Objective:* Characterize the cost of each additional View, and determine whether it is linear, shared, or super-linear. *Procedure:* Repeat the initial dump tests (Section 6.2.1), the dump- under-churn test (Section 6.3), the event tests (Section 6.4), and the BMP/BGP impact tests (Section 6.6), enabling Views cumulatively on the same BMP session, in the following order: IN-PRE; IN-PRE + IN- POST; + LOC; + OUT-PRE; + OUT-POST. The test MUST be repeated with at least one other order, for example the reverse, to expose any order dependence. The Views that are common in operation (for example, IN-PRE and LOC) SHOULD also be tested as sets. The Adj-RIB- Out scale is that of the Basic Profile in this test; its variation is covered in Section 6.8. *Reporting:* X(k), SR(k), and IC(k) as defined in Section 5.8 for BIDT, BCT, the Dump Rate, peak CPU, and peak memory, for each k = 1..5; and, in addition, the time at which each individual View finishes, as the DUT may serialize or interleave the Views. The report MUST state whether Views are sent sequentially or concurrently, if it can be determined. Srivastava Expires 20 May 2027 [Page 25] Internet-Draft BMP Convergence Benchmarking November 2026 6.8. Scaling of the Adj-RIB-Out Views *Objective:* Characterize the cost of the OUT-PRE and OUT-POST Views as a function of the Adj-RIB-Out scale, that is, the number of peers the DUT advertises to and the number of routes it advertises to each of them, with the Adj-RIB-In and Loc-RIB scale held constant. *Procedure:* The Basic Profile peers advertise their routes as in Table 2. The Adj-RIB-Out scale is then varied along two independent dimensions, each with the Views OUT-PRE alone, OUT-POST alone, and both together: a. Number of receiving peers. Receive-only Peering Routers, which advertise nothing to the DUT, are added to the Basic Profile peers to reach a total of P = 10, 20, 50, and 100 peers, or the largest number the DUT supports. Each receive-only peer is advertised a set of the same size as the per-peer advertised set of the Basic Profile, with the outbound policy of Section 4.2. b. Outbound policy rejection ratio. With the Basic Profile peers, the outbound policy additionally rejects 0%, 10%, 50%, and 90% of the routes in the advertised set of each peer. The OUT-PRE content stays the same, while the OUT-POST content shrinks. This shows whether the cost of the DUT follows the pre-policy or the post-policy size. For each point, the following tests are repeated: the initial dump of Section 6.2.1; the route advertisement, withdrawal, and best-path change events of Section 6.4; the peer-up of an additional receive- only peer on an already converged DUT (the dump of one Adj-RIB-Out in normal operation); and the sustained churn of Section 6.5 at a fixed rate. The Reference State of OUT-PRE and OUT-POST can be checked in two ways: against what the Test Controller computes from the policy, and, for OUT-POST, against what the receive-only Peering Routers actually receive, since the post-policy Adj-RIB-Out is defined to convey what is sent to the peer [RFC8671]. Any discrepancy MUST be reported. A single change in the Loc-RIB can lead to one BMP message for each receiving peer that is advertised the route, so the number of BMP messages generated for one injected event grows with P. Per-peer data MUST therefore be recorded: the BEL and BCT for the first and the last peer reported, and the number of BMP messages generated per injected event (the BMP Fan-Out and the Spread of Section 5.4). This holds even if the DUT generates a single BGP UPDATE for a group of peers. Srivastava Expires 20 May 2027 [Page 26] Internet-Draft BMP Convergence Benchmarking November 2026 *Reporting:* BIDT, Dump Rate (in total Adj-RIB-Out route entries per second), BCT, BEL percentiles, LFCR, and peak CPU and memory for each point, as X(P) with SR(P) and IC(P) for dimension (a) (Section 5.8), and as a function of the rejection ratio for dimension (b); the fan- out per event; per-peer first and last values; and the BPT overhead of Section 6.6 at the largest P tested. 6.9. Scaling with the Number of BMP Stations *Objective:* Determine how BMP convergence and DUT resource usage change as the number of BMP stations grows. *Procedure:* Using the topology of Figure 2, and the same View set on each station, repeat the initial dump (Section 6.2.1), the event (Section 6.4), sustained churn (Section 6.5), and BMP/BGP impact (Section 6.6) tests with M = 1, 2, 4, 8, and, if supported, 16 Sink Stations, started simultaneously, first with the Views of the Basic Configuration and then with all five Views enabled at the largest Adj-RIB-Out scale of Section 6.8, since that is the largest BMP load that each additional Station has to receive. The test SHOULD be repeated with Stations started in staggered fashion (a new Station connects while the others are in sync) to measure the cost of an additional dump during normal operation. All stations MUST be measured, and the report MUST include the BCT or BIDT of the first and of the last station to converge, as the DUT might serve them unevenly. *Reporting:* X(M), SR(M), and IC(M) for BIDT, BCT, LFCR, and resource peak values, per Station, plus the maximum number of Stations at which the DUT meets the loss-free criteria. 6.10. Effect of the Collector (Sink versus Processing Station) *Objective:* Separate the performance of the DUT from the performance of a collector, and quantify the latter. *Procedure:* Repeat selected tests from this section with a Processing Station in place of the Sink Station, in the same topology and with the same configuration. The Sink Station results are the baseline for the DUT. The Processing Station is allowed to perform its work in the usual way (for example, decoding, normalization, and storage in a database). The Processing Station SHOULD record, for each message, the time it was received (T_rx) and the time its content was available to the consumers (T_commit). *Reporting:* The difference in the BIDT, BCT, and LFCR between the Processing and the Sink Station; the collector-side lag distribution (T_commit - T_rx); the TCP receive window behavior (the time it was Srivastava Expires 20 May 2027 [Page 27] Internet-Draft BMP Convergence Benchmarking November 2026 reduced or closed), which is the cause of any backpressure on the DUT; and the full description of the collector, its hardware, and its software. 6.11. BMP TCP Backpressure and Buffer Behavior *Objective:* Characterize how the DUT behaves when the BMP Station reads the stream slower than the DUT writes it. *Procedure:* With BMP established and in sync, the Peering Routers generate churn at a fixed rate R (which SHOULD be a rate below the LFCR, and a rate at or above the LFCR), with all five Views enabled, at the Basic Profile and at the largest Adj-RIB-Out scale of Section 6.8, because the amount of data buffered during a stall depends on both. The Test Controller then reduces the rate at which the Station reads the TCP stream, without closing the connection, as follows: a. Complete stall (receive window to zero) for a duration D, with D = 10 s, 60 s, 300 s, and 1,800 s, and then resume at full rate. b. Constant slow reading at a fraction of the rate at which the DUT generates BMP data (for example 90%, 50%, and 10%) for a duration D. c. Repeat (a), with a full initial dump pending. For each case, record: * Whether the DUT keeps the BMP session, resets it, or sends a Termination Message, and the time elapsed before it does that. * Whether messages are dropped, aggregated, or delayed, and how it can be observed by the Station (for example, by a gap in the sequence-stamped events or by the Reference-State differences after recovery). * The growth of the DUT's memory over time, and the peak value; whether the memory is released after recovery (possible leak). * The effect on BGP: sessions flaps, BPT (Section 5.5), and CPU. BGP processing MUST NOT be adversely impacted by a stalled BMP Station, and any impact is a significant finding. * The time to BMP Convergence after the Station resumes, and whether the DUT recovers by sending the backlog, or by resetting the session and doing a new Initial Dump. Srivastava Expires 20 May 2027 [Page 28] Internet-Draft BMP Convergence Benchmarking November 2026 * Any limit, configured or hard-coded, on BMP buffering or queue size that is observed. 7. Reporting Format The report for each test MUST include the following, so that others can reproduce the test and compare it with other results. 7.1. DUT and Test Bed Description +===========================================================+=======+ | Parameter | Value | +===========================================================+=======+ | DUT hardware platform, routing | | | engine / CPU model, memory | | +-----------------------------------------------------------+-------+ | DUT software release, BMP feature | | | version / draft or RFC level | | +-----------------------------------------------------------+-------+ | Redundancy features (disabled/ | | | enabled) | | +-----------------------------------------------------------+-------+ | Peering Router / tester model and | | | software | | +-----------------------------------------------------------+-------+ | BMP Station type (Sink L0 / L1 / | | | L2, Processing), hardware, software | | +-----------------------------------------------------------+-------+ | Timestamping point and clock | | | synchronization uncertainty | | +-----------------------------------------------------------+-------+ | Interfaces: type, speed, in-band / | | | out-of-band for BMP | | +-----------------------------------------------------------+-------+ | Logging / tracing state on DUT and | | | Station | | +-----------------------------------------------------------+-------+ Table 3: Test Bed Parameters 7.2. Test Configuration +==============================================+=======+ | Parameter | Value | +==============================================+=======+ | Scale profile; number of BGP peers (iBGP / | | | eBGP) | | +----------------------------------------------+-------+ Srivastava Expires 20 May 2027 [Page 29] Internet-Draft BMP Convergence Benchmarking November 2026 | Address families; routes per peer, route | | | mixture, route packing, AS_PATH distribution | | +----------------------------------------------+-------+ | Inbound / outbound policy; rejection ratio | | +----------------------------------------------+-------+ | Adj-RIB-Out scale: number of receiving peers | | | (of which receive-only), routes advertised | | | per peer, advertised-set assignment | | +----------------------------------------------+-------+ | BGP timers (keepalive, hold, MRAI, ...), TCP | | | parameters, authentication | | +----------------------------------------------+-------+ | BMP Views enabled; monitored peers; | | | statistics interval | | +----------------------------------------------+-------+ | Number of BMP stations; BMP rate-limit or | | | batching features | | +----------------------------------------------+-------+ | Background churn rate and profile (if any) | | +----------------------------------------------+-------+ | Number of iterations | | +----------------------------------------------+-------+ Table 4: Test Configuration Parameters 7.3. Results +====+========+=============+======+===+===+====+======+====+===+===+ |Test|View | Metric |Method|Min|Max|Mean|Median|Std.|P95|P99| |case| | | | | | | |dev.| | | +====+========+=============+======+===+===+====+======+====+===+===+ |6.x |IN-PRE | BIDT (s) |A | | | | | | | | +----+--------+-------------+------+---+---+----+------+----+---+---+ |6.x |IN-PRE | Dump Rate |A | | | | | | | | | | | (routes/ | | | | | | | | | | | | s) | | | | | | | | | +----+--------+-------------+------+---+---+----+------+----+---+---+ |6.x |LOC | BCT (s) |A | | | | | | | | +----+--------+-------------+------+---+---+----+------+----+---+---+ |6.x |OUT-POST| BEL (ms) |A | | | | | | | | +----+--------+-------------+------+---+---+----+------+----+---+---+ |6.x |OUT-PRE | BIDT (s) |A | | | | | | | | | | | at P | | | | | | | | | | | | receiving | | | | | | | | | | | | peers | | | | | | | | | +----+--------+-------------+------+---+---+----+------+----+---+---+ |6.x |OUT-POST| Fan-Out |A | | | | | | | | | | | (messages | | | | | | | | | Srivastava Expires 20 May 2027 [Page 30] Internet-Draft BMP Convergence Benchmarking November 2026 | | | per | | | | | | | | | | | | event) | | | | | | | | | +----+--------+-------------+------+---+---+----+------+----+---+---+ |6.x |OUT-POST| Spread |A | | | | | | | | | | | (ms) | | | | | | | | | +----+--------+-------------+------+---+---+----+------+----+---+---+ |6.x |n/a | BEL, |A | | | | | | | | | |(session| session | | | | | | | | | | |event) | event | | | | | | | | | | | | (ms): | | | | | | | | | | | | peer-down | | | | | | | | | | | | and peer- | | | | | | | | | | | | up, with | | | | | | | | | | | | Peer Down | | | | | | | | | | | | reason | | | | | | | | | | | | code | | | | | | | | | +----+--------+-------------+------+---+---+----+------+----+---+---+ Table 5: Result Reporting Template (one row per View and metric) In addition, the following MUST be reported: the method used to detect completion (Section 5.6) for each figure, with any discrepancy between the methods; the CPU and memory baseline, peak, and time-to- baseline; the number of lost, duplicated, and out-of-order BMP- reported routes; the BMP Fan-Out and Spread for the Adj-RIB-Out Views; the BGP and BMP session stability statistics; and, for scaling tests, the series X(k), SR(k), and IC(k). 8. Security Considerations Benchmarking activities as described in this document are limited to technology characterization of a DUT using controlled stimuli in a laboratory environment, with dedicated address space and the constraints specified here. The test setup MUST be isolated from production networks and from the Internet. Routes, AS numbers, and address space used in the tests MUST NOT be advertised outside of the test bed. See also [RFC6815] on the use of benchmarking methodologies on production networks. The security considerations of BMP [RFC7854], [RFC8671] and [RFC9069] apply. The tests in this document, especially those with a stalled BMP Station and those with a high rate of churn, can exhaust the resources of the DUT, and could be used as a denial-of-service technique against a production device. They MUST NOT be applied to production devices. The BMP data used or obtained in the tests can reveal the complete routing state of the DUT, and it SHOULD be handled as sensitive when it comes from a non-lab configuration. Srivastava Expires 20 May 2027 [Page 31] Internet-Draft BMP Convergence Benchmarking November 2026 This document does not define any protocol or protocol extension and has no direct impact on the security of the Internet. 9. IANA Considerations This document has no IANA actions. 10. References 10.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC4098] Berkowitz, H., Davies, E., Ed., Hares, S., Krishnaswamy, P., and M. Lepp, "Terminology for Benchmarking BGP Device Convergence in the Control Plane", RFC 4098, DOI 10.17487/RFC4098, June 2005, . [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, DOI 10.17487/RFC4271, January 2006, . [RFC4724] Sangli, S., Chen, E., Fernando, R., Scudder, J., and Y. Rekhter, "Graceful Restart Mechanism for BGP", RFC 4724, DOI 10.17487/RFC4724, January 2007, . [RFC7854] Scudder, J., Ed., Fernando, R., and S. Stuart, "BGP Monitoring Protocol (BMP)", RFC 7854, DOI 10.17487/RFC7854, June 2016, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [RFC8671] Evens, T., Bayraktar, S., Lucente, P., Mi, P., and S. Zhuang, "Support for Adj-RIB-Out in the BGP Monitoring Protocol (BMP)", RFC 8671, DOI 10.17487/RFC8671, November 2019, . Srivastava Expires 20 May 2027 [Page 32] Internet-Draft BMP Convergence Benchmarking November 2026 [RFC9069] Evens, T., Bayraktar, S., Bhardwaj, M., and P. Lucente, "Support for Local RIB in the BGP Monitoring Protocol (BMP)", RFC 9069, DOI 10.17487/RFC9069, February 2022, . 10.2. Informative References [RFC1242] Bradner, S., "Benchmarking Terminology for Network Interconnection Devices", RFC 1242, DOI 10.17487/RFC1242, July 1991, . [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for Network Interconnect Devices", RFC 2544, DOI 10.17487/RFC2544, March 1999, . [RFC6815] Bradner, S., Dubray, K., McQuaid, J., and A. Morton, "Applicability Statement for RFC 2544: Use on Production Networks Considered Harmful", RFC 6815, DOI 10.17487/RFC6815, November 2012, . [RFC7747] Papneja, R., Parise, B., Hares, S., Lee, D., and I. Varlashkin, "Basic BGP Convergence Benchmarking Methodology for Data-Plane Convergence", RFC 7747, DOI 10.17487/RFC7747, April 2016, . [RFC8092] Heitz, J., Ed., Snijders, J., Ed., Patel, K., Bagdonas, I., and N. Hilliard, "BGP Large Communities Attribute", RFC 8092, DOI 10.17487/RFC8092, February 2017, . [RFC9972] Srivastava, M., Ed., Liu, Y., Lin, C., Ed., and J. Li, "Advanced BGP Monitoring Protocol (BMP) Statistics Types", RFC 9972, DOI 10.17487/RFC9972, May 2026, . Author's Address Mukul Srivastava Hewlett Packard Enterprise 10 Technology Park Dr Westford, MA 01886 United States of America Email: mukul.srivastava@hpe.com Srivastava Expires 20 May 2027 [Page 33]