GROW Working Group Y. Liu Internet-Draft China Mobile Intended status: Standards Track C. Lin Expires: 22 May 2027 New H3C Technologies M. Srivastava Hewlett Packard Enterprise P. Narasimha D. Patki Cisco Systems, Inc. 18 November 2026 Efficient BMP Route Monitoring Messages draft-liu-grow-bmp-rm-aggregated-07 Abstract This document proposes two complementary optimizations for the BGP Monitoring Protocol (BMP) Route Monitoring message to significantly reduce network overhead and improve monitoring efficiency. The first optimization defines an aggregated BMP Route Monitoring message based on the Multi-Peer Header mechanism, which compresses multiple BMP Route Monitoring messages into a single aggregated message by leveraging BGP group packaging technology. The second optimization introduces a Common Update TLV that eliminates redundant transmission of routes unchanged by inbound or outbound policies across different RIB views. These optimizations work together to reduce the number of reported BMP messages, decrease bandwidth consumption, and improve processing efficiency for both monitored routers and monitoring stations. 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 22 May 2027. Liu, et al. Expires 22 May 2027 [Page 1] Internet-Draft BMP RM Message Aggregation November 2026 Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. 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. Requirements Language . . . . . . . . . . . . . . . . . . 3 2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Multi-Peer Redundancy . . . . . . . . . . . . . . . . . . 3 2.2. RIB-View Redundancy . . . . . . . . . . . . . . . . . . . 5 2.2.1. BMP Convergence . . . . . . . . . . . . . . . . . . . 5 3. Solution . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.1. Multi-Peer Compression . . . . . . . . . . . . . . . . . 6 3.1.1. Current BGP Group Packaging . . . . . . . . . . . . . 6 3.1.2. BMP Send Batching Optimization . . . . . . . . . . . 8 3.2. RIB-View Compression . . . . . . . . . . . . . . . . . . 9 4. Aggregated Route Monitoring Message . . . . . . . . . . . . . 9 4.1. Message Definition . . . . . . . . . . . . . . . . . . . 9 4.2. Message Format for BMPv3 and BMPv4 . . . . . . . . . . . 9 4.3. Route Monitoring Message . . . . . . . . . . . . . . . . 13 4.4. Support for various RIB-Views . . . . . . . . . . . . . . 13 4.5. Examples of Multiple Peers . . . . . . . . . . . . . . . 13 5. Common Update TLV . . . . . . . . . . . . . . . . . . . . . . 17 5.1. Definition . . . . . . . . . . . . . . . . . . . . . . . 17 5.2. BMP Messages . . . . . . . . . . . . . . . . . . . . . . 18 5.2.1. Route Monitoring . . . . . . . . . . . . . . . . . . 18 5.2.2. Aggregated Route Monitoring . . . . . . . . . . . . . 19 5.2.3. Statistics Report . . . . . . . . . . . . . . . . . . 19 5.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . 20 6. Security Considerations . . . . . . . . . . . . . . . . . . . 20 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 7.1. Aggregated Route Monitoring Message Registry . . . . . . 20 7.2. Common Update TLV Registry . . . . . . . . . . . . . . . 21 7.2.1. Addition to BMP Route Monitoring TLVs . . . . . . . . 21 7.2.2. Additions to BMP Statistics Types Registry . . . . . 21 8. Normative References . . . . . . . . . . . . . . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 Liu, et al. Expires 22 May 2027 [Page 2] Internet-Draft BMP RM Message Aggregation November 2026 1. Introduction The BGP Monitoring Protocol (BMP) defined in [RFC7854] provides a mechanism for monitoring BGP sessions by transmitting route information from routers to monitoring stations. The Route Monitoring message is a fundamental BMP message type used to send incremental routes advertised and withdrawn by peers. As networks grow in scale and complexity, the volume of BMP Route Monitoring messages has increased significantly, leading to several inefficiencies: * Multi-Peer Redundancy: In scenarios like route reflection where multiple peers receive identical or similar routes, traditional BMP sends separate messages for each peer, even when the route information overlaps substantially. * RIB-View Redundancy: When monitoring both pre-policy and post- policy Adj-RIB-In or Adj-RIB-Out views, routes unchanged by policy are transmitted twice - once for each view. This document addresses these inefficiencies through two complementary compression optimizations that can be implemented independently or together for maximum benefit. 1.1. 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. Problem Statement Current BMP implementation faces the following two main sources of redundancy. These redundancies consume unnecessary bandwidth, router processing resources, and monitoring station processing capacity. 2.1. Multi-Peer Redundancy [RFC7854] defines the BMP Route Monitoring message consisting of Common Header, Per-Peer Header and BGP Update PDU. Among them, Common Header and Per-Peer Header are defined in [RFC7854], and the BGP Update PDU contains the BGP PATH attribute and prefix, as shown in Figure 1. Liu, et al. Expires 22 May 2027 [Page 3] Internet-Draft BMP RM Message Aggregation November 2026 +------------------------------+ | Common Header | +------------------------------+ | Per-Peer Header | +------------------------------+ | BGP Update PDU | |+----------------------------+| || BGP PATH Attributes || |+----------------------------+| || Prefixes || |+----------------------------+| +------------------------------+ Figure 1: BMP Route Monitoring Message Structure [I-D.ietf-grow-bmp-tlv] changes the structure of BMP Route Monitoring message where the Per-Peer Header is followed by one BGP Message TLV and optional TLVs, as shown in Figure 2. The BGP Update PDU is enclosed in the BGP Message TLV, and a Route Monitoring message MUST contain one BGP Message TLV. +------------------------------+ | Common Header | +------------------------------+ | Per-Peer Header | +------------------------------+ | BGP Message TLV | |+----------------------------+| || BGP Update PDU || ||+--------------------------+|| ||| BGP PATH Attributes ||| ||+--------------------------+|| ||| Prefixes ||| ||+--------------------------+|| |+----------------------------+| +------------------------------+ | Optional TLVs | +------------------------------+ Figure 2: BMPv4 Route Monitoring Message Structure Currently, a piece of BMP Route Monitoring message can contain one Common Header, one Per-Peer Header, and one BGP Update PDU or one BGP Message TLV including one BGP Update PDU, and the BGP Update PDU can contain multiple non-repeatable BGP PATH attributes and prefixes. Each route update is packaged separately for each peer and each RIB view, even when the content is identical or highly similar. Liu, et al. Expires 22 May 2027 [Page 4] Internet-Draft BMP RM Message Aggregation November 2026 2.2. RIB-View Redundancy [RFC7854] defined Pre-Policy and Post-Policy Adj-RIB-In Route Monitoring messages, whereas [RFC8671] defined Pre-Policy and Post- Policy Adj-RIB-Out Route Monitoring messages. If both Pre-Policy and Post-Policy Route Monitoring modes are enabled on a device for a RIB (Adj-RIB-In or Adj-RIB-Out), the routes are included in both Pre- Policy and Post-Policy Route Monitoring messages, even if the routes remains unmodified as a result of the application of policy. Routes unchanged by inbound or outbound policies are transmitted separately for pre-policy and post-policy views. 2.2.1. BMP Convergence The monitored routers may have policies that modify none, some or several attributes of prefixes learnt from a few to many BGP peers. For example, a Route Reflector Inbound policy may modify very few of the received attributes. Whereas, a Provider Edge router Inbound policy may modify more attributes in the prefixes learnt across several peers. Consider a monitored router that learns 1,000,000 prefixes from various peers and, in different cases, 100%, 50%, 10% and none of the prefixes are modified by the policies. For the sake of simplicity, consider that 10 prefixes are packed in a single Route-Monitoring message and the average size of Route-Monitoring messages is 200 bytes. The following illustration shows the number of Route-Monitoring messages sent in each of these cases. +==========+==========+===========+========+===========+===========+ | Prefixes |Pre-Policy|Post-Policy| Common | Total |Total Bytes| | modified | Messages | Messages |Messages| Messages |Transmitted| |by inbound| | | |Transmitted| | | policy | | | | | | +==========+==========+===========+========+===========+===========+ |100% = | 100,000 | 100,000 | 0 | 200,000 | 40 MB | |1,000,000 | | | | | | +----------+----------+-----------+--------+-----------+-----------+ |50% = | 50,000 | 50,000 | 50,000 | 150,000 | 30 MB | |500,000 | | | | | | +----------+----------+-----------+--------+-----------+-----------+ |10% = | 10,000 | 10,000 | 90,000 | 110,000 | 22 MB | |100,000 | | | | | | +----------+----------+-----------+--------+-----------+-----------+ |None | 0 | 0 |100,000 | 100,000 | 20 MB | +----------+----------+-----------+--------+-----------+-----------+ Table 1: Route-Monitoring messages generated for inbound policy variations Liu, et al. Expires 22 May 2027 [Page 5] Internet-Draft BMP RM Message Aggregation November 2026 While there can be multi-dimensional variations that determine the number of messages sent, the above simplified cases broadly illustrates that the number or Route-Monitoring messages can be reduced by a factor of two in the best case. This can therefore reduce the transmission processing, number of transmit buffers required for sending the BMP updates and internal queuing delays in the monitored router and load on the network connecting to the monitoring station; thereby improving the overall BMP convergence. This can also reduce the number of messages processed by the monitoring station. 3. Solution 3.1. Multi-Peer Compression 3.1.1. Current BGP Group Packaging The rapid growth of existing network routing tables and the complexity of network topology have led to the need for BGP to support more peers. In particular, in scenarios with a large number of peers and a large amount of routes, the router needs to send routes to a large number of BGP peers, and most of the peers have the same configuration, which requires higher packaging and sending performance. The BGP group packaging technology treats all BGP peers with common configurations as a packaging group. In this way, each route to be sent is packaged only once and then sent to all neighbors in the packaging group, which exponentially improves the packaging efficiency. Before the group packaging feature was supported, each route to be sent had to be packaged separately for each peer. Group packaging enables unified packaging and separate sending, that is, each route to be sent is packaged only once and then sent to all peers in the packaging group, which exponentially improves the efficiency of packaging and sending. In scenarios with a large number of neighbors and a large amount of routes, as shown in Figure 3, group packaging greatly improves the performance of BGP packaging and sending. Liu, et al. Expires 22 May 2027 [Page 6] Internet-Draft BMP RM Message Aggregation November 2026 +---------------------------------------------------------------+ | +----------+ AS | | | RR1 | | | +-+-+-+-+--+ | | | | | | IBGP | | | | | +---------------------------------------------+ | | | | +------------------------------+ | | | | +---------------+ | | | | | | | | | | +-+------+ +--+-----+ +--+-----+ +--+-----+ | | | Client | ... | Client | ... | Client | ... | Client | | | +-+------+ +--+-----+ +--+-----+ +--+-----+ | | | | | | | | | +---------------+ | | | | | | +------------------------------+ | | | | | | +---------------------------------------------+ | | | | | | IBGP | | +-+-+-+-+--+ | | | RR2 | | | +----------+ | +---------------------------------------------------------------+ Figure 3: Typical Application Scenario for Group Packaging Figure 3 is a typical network diagram of reflectors with multiple clients, RR routers need to send routes to a large number of BGP client peers, and most of the client peers have the same configuration. Suppose an RR reflector has 100 clients and 100,000 routes to be reflected. If each neighbor is packaged separately, when the reflector RR sends routes to 100 clients, the total number of times all routes are packaged is 100,000 x 100. The group packaging technology reduces this process to 100,000 x 1, which is equivalent to a 100-fold improvement in performance. The comparison of packet assembly by peer and peer packaging group is shown in Figure 4. It can be clearly seen that assembling packets by peer packaging group can greatly improve packet performance. +----------------------------------------------------------------+ | Encapsulation by Peer | Encapsulation by Peer Packaging Group | +----------------------------------------------------------------+ | N Peers | N Peers of Peer Packaging Group | +----------------------------------------------------------------+ | N Times Packaging | 1 Times Packaging | +----------------------------------------------------------------+ | N Times Sending | N Times Sending | +----------------------------------------------------------------+ Liu, et al. Expires 22 May 2027 [Page 7] Internet-Draft BMP RM Message Aggregation November 2026 Figure 4: Comparison of Two Packaging Methods 3.1.2. BMP Send Batching Optimization Currently, network devices have implemented BGP send batching technology. This allows messages with the same attributes to be batched together and sent to multiple neighbors simultaneously. However, BMP Route Monitoring message is handled on a per-peer basis, which means they cannot take advantage of the BGP send batching functionality. From the perspective of BMP Route Monitoring packet format, if BMP Route Monitoring packets are also assembled according to peers, they need to be assembled once for each peer, and the assembly performance will also be limited. Moreover, the BMP Route Monitoring message information may be different depending on the peer, and needs to be sent to the monitoring server multiple times, which increases the network overhead. In multiple BMP Route Monitoring messages, if the prefixes are the same but the Per-Peer Header and BGP PATH attributes are different, according to the way of packet assembly by peer packaging group, the different BGP attributes can be extracted, combined with the corresponding Per-Peer Header, and reuse of the same BGP PATH attributes, which together form a aggregated BMP Route Monitoring message. See Section 4.2 for detailed format of the aggregated BMP Route Monitoring message. As shown in Figure 5 and Figure 6, compared with the original multiple BMP Route Monitoring message, the aggregated BMP Route Monitoring message exponentially reduces the Common Header and the same BGP PATH attributes and prefixes, and is only assembled once, which not only effectively the network overhead is reduced and the assembly performance is further improved. +--------+ +---------------------+ +-----------------+ | |----->|Packaging for Peer 1 |----->|Sending to Server| | | +---------------------+ +-----------------+ | | ~ |Prefixes| ~ | | +---------------------+ +-----------------+ | |----->|Packaging for Peer N |----->|Sending to Server| +--------+ +---------------------+ +-----------------+ Figure 5: BMP Encapsulation by Per-Peer +--------+ +-------------------------+ +-----------------+ |Prefixes|--->|Packaging for Multi-Peers|--->|Sending to Server| +--------+ +-------------------------+ +-----------------+ Liu, et al. Expires 22 May 2027 [Page 8] Internet-Draft BMP RM Message Aggregation November 2026 Figure 6: BMP Encapsulation by Multi-Peers This document defines this aggregated BMP Route Monitoring message, and its format has been defined based on the Multi-Peer Header message format defined in Section 4 of [I-D.liu-grow-bmp-multiple-peer-header], see Section 4.2 for its detailed format. 3.2. RIB-View Compression To avoid sending duplicate unmodified routes in the Post-Policy Route Monitoring messages, this document introduce a method based on Common Update TLV as defined in [I-D.ietf-grow-bmp-tlv]. The Common Update TLV optimization addresses redundancy across different RIB views for the same peer. When a route is unchanged by inbound or outbound policy, it appears identically in both pre-policy and post-policy views. Without optimization, the router sends two nearly identical BMP Route Monitoring messages. The Common Update TLV attaches to a BMP Route Monitoring message and uses flags to indicate which RIB views share the same route information. This allows a single message to serve multiple RIB views, eliminating duplicate transmissions. 4. Aggregated Route Monitoring Message 4.1. Message Definition This section adds a new BMP Multi-Peer Message Type for BMP Route Monitoring, which is populated in the Multi-Peer Message Type field of the BMP Common Multi-Peer Header defined in Section 5 of [I-D.liu-grow-bmp-multiple-peer-header]. Multi-Peer Message Type = TBD0: Aggregated Route Monitoring, Recommended value 0. 4.2. Message Format for BMPv3 and BMPv4 This section defines two aggregated BMP Route Monitoring message formats, according to the Route Monitoring message format of [RFC7854] and [I-D.ietf-grow-bmp-tlv]. Liu, et al. Expires 22 May 2027 [Page 9] Internet-Draft BMP RM Message Aggregation November 2026 Figure 7 shows one aggregated Route Monitoring message format, based on the Route Monitoring message format of [RFC7854], including Common Header, Common Multi-Peer Header, and BGP Update PDU. Among them, the Common Header is the same as that defined in Section 4.1 of [RFC7854], the BGP Update PDU contains the same BGP PATH attribute and prefixes, and the Common Multi-Peer Header will be defined below. +--------------------------------------------------+ | Common Header (Type = Multi-Peer Header) | +--------------------------------------------------+ | Common Multi-Peer Header | ~ ~ +--------------------------------------------------+ | BGP Update PDU | |+----------------------------+ | || BGP PATH Attributes | | |+----------------------------+ | || Prefixes | | |+----------------------------+ | +--------------------------------------------------+ Figure 7: BMP Aggregated Route Monitoring Message Format Figure 8 shows another aggregated Route Monitoring message format, based on the BMPv4 Route Monitoring message format of [I-D.ietf-grow-bmp-tlv], including Common Header, Common Multi-Peer Header, BGP Message TLV including BGP Update PDU, and optional TLVs. Among them, the Common Header and the Common Multi-Peer Header are the same as the above, the BGP Update PDU of the BGP Message TLV also contains the same BGP PATH attribute and prefixes, and the Optional TLVs can be shared TLVs or TLVs specific to a particular prefix. Liu, et al. Expires 22 May 2027 [Page 10] Internet-Draft BMP RM Message Aggregation November 2026 +--------------------------------------------------+ | Common Header (Type = Multi-Peer Header) | +--------------------------------------------------+ | Common Multi-Peer Header | ~ ~ +--------------------------------------------------+ | BGP Message TLV | ++------------------------------------------+ | || BGP Update PDU | | ||+----------------------------+ | | ||| BGP PATH Attributes | | | ||+----------------------------+ | | ||| Prefixes | | | ||+----------------------------+ | | |+------------------------------------------+ | +--------------------------------------------------+ | Optional TLVs | +--------------------------------------------------+ Figure 8: BMPv4 Aggregated Route Monitoring Message Format As shown in Figure 9, the format of the Common Multi-Peer Header in the aggregated Route Monitoring message is defined, which contains multiple Wild Card Per-Peer Headers defined in Section 5 of [I-D.liu-grow-bmp-multiple-peer-header]. The Multi-Peer Message Length is the length of Common Multi-Peer Header in bytes (including all Wild Card Per-Peer Headers, Per-Peer Information Lengths, and Per-Peer BGP PATH Attributes). Each Wild Card Per-Peer Header could be followed by the unique Per-Peer BGP PATH attribute of the corresponding peer route. If no Per-Peer BGP PATH attribute follows, the corresponding Per-Peer Information length MUST be set to 0. Liu, et al. Expires 22 May 2027 [Page 11] Internet-Draft BMP RM Message Aggregation November 2026 +--------------------------------------------------------+ | Multi-Peer Message Type (TBD0) (1 byte) | +--------------------------------------------------------+ | Multi-Peer Message Length (2 byte) | +--------------------------------------------------------+ | Wild Card Per-Peer Header 1 | +--------------------------------------------------------+ | Per-Peer Information Length 1 (2 bytes) | +--------------------------------------------------------+ | Per-Peer BGP PATH Attributes 1 | +--------------------------------------------------------+ ~ ~ +--------------------------------------------------------+ | Wild Card Per-Peer Header N | +--------------------------------------------------------+ | Per-Peer Information Length N (2 bytes) | +--------------------------------------------------------+ | Per-Peer BGP PATH Attributes N | +--------------------------------------------------------+ Figure 9: Common Multi-Peer Header Format for Route Monitoring In the Common Multi-Peer Header format, the Wild Card Per-Peer Header format is the same as that defined in [I-D.liu-grow-bmp-multiple-peer-header]. Per-Peer Information Length (2 bytes) indicates the length of the Per-Peer BGP PATH Attributes in the Common Multi-Peer Header. The format of the Per-Peer BGP PATH Attribute in the Common Multi- Peer Header is the same as BGP PATH Attribute in the BGP Update PDU. The Per-Peer BGP PATH Attribute field does not need to be filled in when the route attributes corresponding to each peer are exactly the same. Only when the routing attributes corresponding to the peers are different to a certain extent, different parts of the routing attributes need to be filled in Per-Peer BGP PATH Attribute field according to the peers. The same parts of the routing attributes are filled in the BGP Update PDU. If the routing attributes corresponding to each peer are completely different, the routing attributes (BGP PATH Attribute) in the BGP Update PDU will be empty. If the Per-Peer BGP PATH Attribute in Common Multi-Peer Header exists, it means that the BGP PATH Attribute of the BGP Update PDU needs to be integrated with the Per-Peer BGP PATH Attribute of Common Multi-Peer Header to obtain the complete BGP PATH Attribute of BGP UPDATE PDU sent or received to the corresponding peer. Otherwise, the BGP PATH Attribute of the BGP UPDATE PDU is the complete BGP PATH Attribute. Liu, et al. Expires 22 May 2027 [Page 12] Internet-Draft BMP RM Message Aggregation November 2026 The Per-Peer BGP PATH Attributes in Common Multi-Peer Header is optional. A Common Multi-Peer Header may just include the Per-Peer Header(s) without any PATH attributes following them. Multiple aggregated Route Monitoring messages can be used for same or different set of BGP Update prefixes. 4.3. Route Monitoring Message Sender MUST send either the Route Monitoring Message (type 0) as defined in [RFC7854] OR the aggregated Route Monitoring Message and MUST NOT combine the two message formats in the updates. 4.4. Support for various RIB-Views Aggregated Route Monitoring messages can be used for any of the RIB- views (Adj-RIB-In pre, Adj-RIB-In post, Adj-RIB-Out pre, Adj-RIB-Out post & Local-RIB) when batching is feasible. Batching across RIB-views with aggregated Route Monitoring Message can be used leveraging methods defined in [I-D.patki-grow-bmp-common-updates]. 4.5. Examples of Multiple Peers This section lists some examples to show how to use the aggregated Route Monitoring Message based on the Route Monitoring Message format of [RFC7854]. For the BMPv4 aggregated Route Monitoring Message, its usage is similar to these examples. As shown in Figure 10, there are three peers with no per-peer BGP PATH attributes along with all PATH attributes from BGP Update PDU being shared. Liu, et al. Expires 22 May 2027 [Page 13] Internet-Draft BMP RM Message Aggregation November 2026 +-----------------------------------------------+ | Multi-Peer Message Type (TBD0) | +-----------------------------------------------+ | Multi-Peer Message Length | +-----------------------------------------------+ | Wild Card Per-Peer Header 1 | +-----------------------------------------------+ | Per-Peer Information Length 1 (0) | +-----------------------------------------------+ | Wild Card Per-Peer Header 2 | +-----------------------------------------------+ | Per-Peer Information Length 2 (0) | +-----------------------------------------------+ | Wild Card Per-Peer Header 3 | +-----------------------------------------------+ | Per-Peer Information Length 3 (0) | +-----------------------------------------------+ | BGP Update PDU | |+----------------------------+ | || BGP PATH Attributes | | |+----------------------------+ | || Prefixes | | |+----------------------------+ | +-----------------------------------------------+ Figure 10: Three Peers with No Per-Peer BGP PATH Attributes As shown in Figure 11, there are three peers with one of the peers having different PATH attribute along with shared PATH attributes in the BGP Update PDU. Liu, et al. Expires 22 May 2027 [Page 14] Internet-Draft BMP RM Message Aggregation November 2026 +-----------------------------------------------+ | Multi-Peer Message Type (TBD0) | +-----------------------------------------------+ | Multi-Peer Message Length | +-----------------------------------------------+ | Wild Card Per-Peer Header 1 | +-----------------------------------------------+ | Per-Peer Information Length 1 | +-----------------------------------------------+ | Per-Peer BGP PATH Attributes 1 | +-----------------------------------------------+ | Wild Card Per-Peer Header 2 | +-----------------------------------------------+ | Per-Peer Information Length 2 (0) | +-----------------------------------------------+ | Wild Card Per-Peer Header 3 | +-----------------------------------------------+ | Per-Peer Information Length 3 (0) | +-----------------------------------------------+ | BGP Update PDU | |+----------------------------+ | || BGP PATH Attributes | | |+----------------------------+ | || Prefixes | | |+----------------------------+ | +-----------------------------------------------+ Figure 11: Three Peers with One Peer Having Different PATH Attribute As shown in Figure 12, there are three peers with all the peers having different PATH attributes along with shared PATH attributes in BGP Update PDU. Liu, et al. Expires 22 May 2027 [Page 15] Internet-Draft BMP RM Message Aggregation November 2026 +-----------------------------------------------+ | Multi-Peer Message Type (TBD0) | +-----------------------------------------------+ | Multi-Peer Message Length | +-----------------------------------------------+ | Wild Card Per-Peer Header 1 | +-----------------------------------------------+ | Per-Peer Information Length 1 | +-----------------------------------------------+ | Per-Peer BGP PATH Attributes 1 | +-----------------------------------------------+ | Wild Card Per-Peer Header 2 | +-----------------------------------------------+ | Per-Peer Information Length 2 | +-----------------------------------------------+ | Per-Peer BGP PATH Attributes 2 | +-----------------------------------------------+ | Wild Card Per-Peer Header 3 | +-----------------------------------------------+ | Per-Peer Information Length 3 | +-----------------------------------------------+ | Per-Peer BGP PATH Attributes 3 | +-----------------------------------------------+ | BGP Update PDU | |+----------------------------+ | || BGP PATH Attributes | | |+----------------------------+ | || Prefixes | | |+----------------------------+ | +-----------------------------------------------+ Figure 12: Three Peers with All Having Different PATH Attributes As shown in Figure 13, there are three peers with all the peers having different PATH attributes along with no shared PATH attributes in BGP Update PDU. Liu, et al. Expires 22 May 2027 [Page 16] Internet-Draft BMP RM Message Aggregation November 2026 +-----------------------------------------------+ | Multi-Peer Message Type (TBD0) | +-----------------------------------------------+ | Multi-Peer Message Length | +-----------------------------------------------+ | Wild Card Per-Peer Header 1 | +-----------------------------------------------+ | Per-Peer Information Length 1 | +-----------------------------------------------+ | Per-Peer BGP PATH Attributes 1 | +-----------------------------------------------+ | Wild Card Per-Peer Header 2 | +-----------------------------------------------+ | Per-Peer Information Length 2 | +-----------------------------------------------+ | Per-Peer BGP PATH Attributes 2 | +-----------------------------------------------+ | Wild Card Per-Peer Header 3 | +-----------------------------------------------+ | Per-Peer Information Length 3 | +-----------------------------------------------+ | Per-Peer BGP PATH Attributes 3 | +-----------------------------------------------+ | BGP Update PDU | |+----------------------------+ | || Prefixes | | |+----------------------------+ | +-----------------------------------------------+ Figure 13: Three Peers with All Having Different PATH Attributes along without Shared Path Attributes 5. Common Update TLV 5.1. Definition Here we define a new TLV named Common Update TLV using the TLV construct defined in Section 4.2 of [I-D.ietf-grow-bmp-tlv]. In addition to allowing sharing a common BGP Update PDU between Pre- Policy and Post-Policy modes of Adj-RIB-In and the same for Adj-RIB- Out, this method is extensible in allowing sharing across Adj-RIB-In and Adj-RIB-Out views, though we see it being used rarely. The TLV has Index zero (0) which specifies that a TLV applies to all NLRIs contained in the BGP Update PDU. The value of the TLV defines flags that are described below. Liu, et al. Expires 22 May 2027 [Page 17] Internet-Draft BMP RM Message Aggregation November 2026 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type=TBD1 | Length = 3 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Index=0 |I|J|O|P| Resv | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 14: Common Update TLV * When I flag is set, it indicates that the BGP Update PDU reflects the Pre-Policy Adj-RIB-In view of all contained NLRIs * When J flag is set, it indicates that the BGP Update PDU reflects the Post-Policy Adj-RIB-In view of all contained NLRIs * When O flag is set, it indicates that the BGP Update PDU reflects the Pre-Policy Adj-RIB-Out view of all contained NLRIs * When P flag is set, it indicates that the BGP Update PDU reflects the Post-Policy Adj-RIB-Out view of all contained NLRIs * The remaining bits are reserved for future use. They MUST be transmitted as 0 and their values MUST be ignored on receipt. 5.2. BMP Messages The Common Update TLV is used in the context of BGP Update PDU, and has no significance for Peer-Up, Peer-Down, Initiation, Termination and Statistics Report messages. Though the Route Mirroring message contains a BGP Update PDU, as there is no policy execution involved in its transmission, the Common Update TLV has no significance. In all messages except the Route-Monitoring message, the Common Update TLV MUST NOT be included during transmission and MUST be ignored if found on reception. 5.2.1. Route Monitoring The Common Update TLV is of relevance only in the Adj-RIB-In and Adj- RIB-Out Route-Monitoring messages and not in the Loc-RIB Route- Monitoring messages. A Route-Monitoring Update message containing the Common Update TLV MAY also include Adj-In Time and Adj-Out Time Timestamp TLVs defined in [I-D.younsi-grow-bmp-snts]. The Adj-In Timestamp TLV MUST NOT be included if the Common Update TLV does not have I flag or J flag set, and, the Adj-Out Timestamp TLV MUST NOT be included if the Common Update TLV does not have O flag or P flag set. If included, the same must be ignored by the receiver. Liu, et al. Expires 22 May 2027 [Page 18] Internet-Draft BMP RM Message Aggregation November 2026 5.2.2. Aggregated Route Monitoring The Common Update TLV can also be used in the Aggregated BMP Route- Monitoring Message defined in Section 4 of this document. This TLV is of relevance only in the Adj-RIB-In and Adj-RIB-Out Aggregated Route-Monitoring messages and not in the Loc-RIB Aggregated Route- Monitoring messages. An Aggregated Route-Monitoring Update message containing the Common Update TLV MAY also include Adj-In Time and Adj-Out Time Timestamp TLVs defined in [I-D.younsi-grow-bmp-snts]. The Adj-In Timestamp TLV MUST NOT be included if the Common Update TLV does not have I flag or J flag set, and, the Adj-Out Timestamp TLV MUST NOT be included if the Common Update TLV does not have O flag or P flag set. If included, the same must be ignored by the receiver. 5.2.3. Statistics Report This document defines new statistics types that use the following bitmap which is used to indicate a combination of Route-Monitoring views for which routes are the same, i.e. unmodified by policy. +-+-+-+-+-+-+-+-+ |I|J|O|P| Resv | +-+-+-+-+-+-+-+-+ Figure 15: Bitmap of Route-Monitoring views * I bit - Pre-Policy Adj-RIB-In * J bit - Post-Policy Adj-RIB-In * O bit - Pre-Policy Adj-RIB-Out * P bit - Post-Policy Adj-RIB-Out * The remaining bits are reserved for future use. They MUST be transmitted as 0 and their values MUST be ignored on receipt. The following new statistics types are defined. * Stat Type = TBD2: Number of routes common across a combination of Route-Monitoring views. The value is structured as follows: Bitmap of Route-Monitoring views, Number of routes (64-bit Gauge) common between the views indicated by the bitmap. Multiple instances of this statistics type MAY be included in the same Statistics Report message, each for a unique value of the bitmap. Liu, et al. Expires 22 May 2027 [Page 19] Internet-Draft BMP RM Message Aggregation November 2026 * Stat Type = TBD3: Number of routes common across a combination of Route-Monitoring views per-AFI/SAFI. The value is structured as follows: 2-byte Address Family Identifier (AFI), 1-byte Subsequent Address Family Identifier (SAFI), Bitmap of Route-Monitoring views, Number of routes (64-bit Gauge) common between the views indicated by the bitmap. Multiple instances of this statistics type MAY be included in the same Statistics Report message, each for a unique value of AFI/SAFI and the bitmap. 5.3. Examples * When I=1, J=1, O=0, P=0 it indicates that the BGP Update PDU is the same for Pre-Policy and Post-Policy Adj-RIB-In views. * When I=0, J=0, O=1, P=1 it indicates that the BGP Update PDU is the same for Pre-Policy and Post-Policy Adj-RIB-Out views. The following examples demonstrate sharing across Adj-RIB-In and Adj- RIB-Out views as well, but we anticipate this not to be used * When I=0, J=1, O=1, P=0 it indicates that the BGP Update PDU is the same for Post-Policy Adj-RIB-In and Pre-Policy Adj-RIB-Out views. * When I=0, J=1, O=1, P=1 it indicates that the BGP Update PDU is the same for Post-Policy Adj-RIB-In, and Pre-Policy and Post- Policy Adj-RIB-Out views. 6. Security Considerations The considerations in Section 11 of [RFC7854] apply to this document. It is also believed that this document does not add any additional security considerations. 7. IANA Considerations 7.1. Aggregated Route Monitoring Message Registry This document requests IANA to define one new "BMP Multi-Peer Message Type" registry to the BMP parameters name space (https://www.iana.org/assignments/bmp-parameters/bmp- parameters.xhtml). The new "BMP Multi-Peer Message Type" registry is seeded with the following new type (Section 4.1): Type = TBD0: Aggregated Route Monitoring Liu, et al. Expires 22 May 2027 [Page 20] Internet-Draft BMP RM Message Aggregation November 2026 7.2. Common Update TLV Registry IANA also needs to assign the following new parameters to the "BGP Monitoring Protocol (BMP) Parameters" registry (https://www.iana.org/assignments/bmp-parameters/). 7.2.1. Addition to BMP Route Monitoring TLVs IANA needs to make the following assignment for the "Common Update TLV" in the "BMP Route Monitoring TLVs" registry. Type = TBD1 (15 Bits): Common Update TLV 7.2.2. Additions to BMP Statistics Types Registry IANA needs to make the following assignment for the statistics types defined in Section 5.2.3 of this document: +===========+==============================================+ | Stat Type | Description | +===========+==============================================+ | TBD2 | Number of routes common across a combination | | | of Route-Monitoring views. | +-----------+----------------------------------------------+ | TBD3 | Number of routes common across a combination | | | of Route-Monitoring views per-AFI/SAFI. | +-----------+----------------------------------------------+ Table 2: Additions to the "BMP Statistics Types" Registry 8. Normative References [I-D.ietf-grow-bmp-tlv] Lucente, P., Gu, Y., Younsi, M., and P. Francois, "BMP v4: Extended TLV Support for BGP Monitoring Protocol (BMP)", Work in Progress, Internet-Draft, draft-ietf-grow-bmp-tlv- 20, 2 March 2026, . [I-D.liu-grow-bmp-multiple-peer-header] Liu, Y., Lin, C., Prasad, N., and M. K. Srivastava, "Definition for BMP Multiple Peer Header", Work in Progress, Internet-Draft, draft-liu-grow-bmp-multiple- peer-header-02, 25 April 2026, . Liu, et al. Expires 22 May 2027 [Page 21] Internet-Draft BMP RM Message Aggregation November 2026 [I-D.patki-grow-bmp-common-updates] Patki, D. and N. Prasad, "Common BMP Route-Monitoring Messages for Routes Unchanged by Policy", Work in Progress, Internet-Draft, draft-patki-grow-bmp-common- updates-02, 20 October 2025, . [I-D.younsi-grow-bmp-snts] Younsi, M. and P. Francois, "BMP Sequence Number, Timestamp and Flags TLVs", Work in Progress, Internet- Draft, draft-younsi-grow-bmp-snts-01, 17 October 2025, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [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, . Authors' Addresses Yisong Liu China Mobile China Email: liuyisong@chinamobile.com Changwang Lin New H3C Technologies China Email: linchangwang.04414@h3c.com Liu, et al. Expires 22 May 2027 [Page 22] Internet-Draft BMP RM Message Aggregation November 2026 Mukul Srivastava Hewlett Packard Enterprise 10 Technology Park Dr Westford, MA 01886 United States of America Email: mukul.srivastava@hpe.com Prasad S. Narasimha Cisco Systems, Inc. Email: snprasad@cisco.com Dhananjay Patki Cisco Systems, Inc. Cessna Business Park SEZ, Kadubeesanahalli Bangalore 560103 Karnataka India Email: dhpatki@cisco.com Liu, et al. Expires 22 May 2027 [Page 23]