| Internet-Draft | BMP Stats Ext | December 2025 |
| Wang, et al. | Expires 4 July 2026 | [Page] |
[RFC7854], [RFC8671] and [I-D.ietf-grow-bmp-bgp-rib-stats] define different BGP Monitoring Protocol (BMP) statistics message types to observe events that occur on a monitored router. This document defines some additional statistics type to monitor BMP Adj-RIB-In, Loc-RIB and Adj-RIB-Out Routing Information Bases (RIBs).¶
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.¶
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 4 July 2026.¶
Copyright (c) 2025 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.¶
.¶
Section 4.8 of [RFC7854] and section 6.2 of [RFC8671] define a number of different BGP Monitoring Protocol (BMP) statistics types to observe major events that occur on a monitored router, and [I-D.ietf-grow-bmp-bgp-rib-stats] defines some new statistics type to monitor BMP Adj-RIB-In and Adj-RIB-Out Routing Information Bases (RIBs). This document defines some additional statistics type to monitor BMP Adj-RIB-In, Loc-RIB and Adj-RIB-Out Routing Information Bases (RIBs).¶
This section defines different statistics type for Adj-RIB-In and Adj-RIB-Out monitoring type. Some of these statistics are also applicable to Loc-RIB, The Statistics Format follows the definition in Section 3.1 of [I-D.ietf-grow-bmp-bgp-rib-stats].¶
Type = TBD1: Number of routes currently in per-AFI/SAFI pre-policy Adj-RIB-In rejected due to exceeding the received route threshold.¶
Type = TBD2: Number of routes currently in per-AFI/SAFI pre-policy Adj-RIB-In rejected due to insufficient memory.¶
Type = TBD3: Number of routes currently in per-AFI/SAFI pre-policy Adj-RIB-In that cannot be downloaded to the FIB module due to insufficient forwarding resources.¶
Type = TBD4: Number of routes currently in per-AFI/SAFI pre-policy Adj-RIB-In that cannot be downloaded to the FIB module due to insufficient label resources or SID resources.¶
Type = TBD5: Number of routes currently in per-AFI/SAFI pre-policy Adj-RIB-In rejected due to invalid next-hop.¶
Type = TBD6: Number of routes currently in per-AFI/SAFI pre-policy Adj-RIB-In rejected due to next-hop unreachable.¶
Type = TBD7: Number of routes currently in per-AFI/SAFI pre-policy Adj-RIB-In that are inactive due to the inability to resolve the next-hop tunnel.¶
Type = TBD8: Number of routes currently in per-AFI/SAFI pre-policy Adj-RIB-In rejected due to Type 1 Route Leak as defined in [RFC7908]: Hairpin Turn with Full Prefix.¶
Type = TBD9: Number of routes currently in per-AFI/SAFI pre-policy Adj-RIB-In rejected due to Type 2 Route Leak as defined in [RFC7908]: Lateral ISP-ISP-ISP Leak.¶
Type = TBD10: Number of routes currently in per-AFI/SAFI pre-policy Adj-RIB-In rejected due to Type 3 Route Leak as defined in [RFC7908]: Leak of Transit-Provider Prefixes to Peer.¶
Type = TBD11: Number of routes currently in per-AFI/SAFI pre-policy Adj-RIB-In rejected due to Type 4 Route Leak as defined in [RFC7908]: Leak of Peer Prefixes to Transit Provider.¶
Type = TBD12: Number of routes currently in per-AFI/SAFI pre-policy Adj-RIB-In rejected due to Type 5 Route Leak as defined in [RFC7908]: Prefix Re-origination with Data Path to Legitimate Origin.¶
Type = TBD13: Number of routes currently in per-AFI/SAFI pre-policy Adj-RIB-In rejected due to Type 6 Route Leak as defined in [RFC7908]: Accidental Leak of Internal Prefixes and More- Specific Prefixes.¶
Type = TBD14: (64-bit Gauge) Current number of routes in per-AFI/SAFI post-policy Adj-RIB-In invalidated through the AS_PATH Verification [I-D.ietf-sidrops-aspa-verification]. This is total number of routes invalidated due to AS_PATH Verification. The value is structured as: 2-byte AFI, 1-byte SAFI, followed by a 64-bit Gauge.¶
Type = TBD15: (64-bit Gauge) Current number of routes in per-AFI/SAFI post-policy Adj-RIB-In validated through the AS_PATH Verification [I-D.ietf-sidrops-aspa-verification]. This is total number of routes validated due to AS_PATH Verification. The value is structured as: 2-byte AFI, 1-byte SAFI, followed by a 64-bit Gauge.¶
Type = TBD16: (64-bit Gauge) Current number of routes in per-AFI/SAFI post-policy Adj-RIB-In whose AS_PATH Verification state is Unknown due to the AS_PATH Verification [I-D.ietf-sidrops-aspa-verification]. The value is structured as: 2-byte AFI, 1-byte SAFI, followed by a 64-bit Gauge.¶
Type = TBD17: Number of routes currently in per-AFI/SAFI pre-policy Adj-RIB-Out rejected due to exceeding the sent route threshold.¶
Type = TBD18: Number of routes currently in per-AFI/SAFI pre-policy Adj-RIB-Out that cannot be advertised to its peer due to insufficient label resources or SID resources.¶
Type = TBD19: (64-bit Gauge) Current number of routes in per-AFI/SAFI post-policy Adj-RIB-Out invalidated through the AS_PATH Verification [I-D.ietf-sidrops-aspa-verification] [I-D.zhang-sidrops-aspa-egress]. This is total number of routes invalidated due to AS_PATH Verification. The value is structured as: 2-byte AFI, 1-byte SAFI, followed by a 64-bit Gauge.¶
Type = TBD20: (64-bit Gauge) Current number of routes in per-AFI/SAFI post-policy Adj-RIB-Out validated through the AS_PATH Verification [I-D.ietf-sidrops-aspa-verification] [I-D.zhang-sidrops-aspa-egress]. This is total number of routes validated due to AS_PATH Verification. The value is structured as: 2-byte AFI, 1-byte SAFI, followed by a 64-bit Gauge.¶
Type = TBD21: (64-bit Gauge) Current number of routes in per-AFI/SAFI post-policy Adj-RIB-Out whose AS_PATH Verification state is Unknown due to the AS_PATH Verification [I-D.ietf-sidrops-aspa-verification] [I-D.zhang-sidrops-aspa-egress]. The value is structured as: 2-byte AFI, 1-byte SAFI, followed by a 64-bit Gauge.¶
This document requests that IANA assign the following new parameters to the BMP parameters name space (https://www.iana.org/assignments/ bmp-parameters/bmp-parameters.xhtml).¶
They will be added in subsequent versions.¶
Procedures and protocol extensions defined in this document do not affect the BMP security model. All security and authentication mechanisms required by Section 11 of [RFC7854], Section 8 of [RFC8671], and Section 7 of [RFC9069] are also applicable to the gauges defined in this document. This document does not add any additional security considerations.¶
Monitored devices SHOULD be configured to implement rate-limited reporting of new gauges.¶
The following people made significant contributions to this document:¶
To be added.¶
The authors would like to acknowledge the review and inputs from xxx.¶