| Internet-Draft | EVPN BMP Statistics | August 2025 |
| Dikshit | Expires 13 February 2026 | [Page] |
This document defines EVPN-specific BMP statistics types that extend the generic BMP RIB statistics defined in draft-ietf-grow-bmp-bgp-rib-stats. It includes counters for EVPN multihoming for both layer-2 and layer-3 (IP aliasing), dynamic IVRL, route-map application on routes, and EVPN route-type visibility for all route-types from 1 to 8.¶
The Border Gateway Protocol Monitoring Protocol (BMP) provides a convenient interface for obtaining BGP-related data. This document extends BMP RIB statistics to include EVPN-specific counters and metrics, enabling enhanced visibility into EVPN route processing and behavior.¶
This document registers new EVPN BMP statistic type identifiers in the BMP Statistics Type registry. These identifiers are used to represent EVPN-specific counters in BMP messages.¶
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 13 February 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.¶
RFC 7854 defined different BMP statistics message types to observe events on the router. The statistics are defined as counters or gauges to provide insights into BGP processing. This document extends the BMP RIB statistics defined in [I-D.draft-ietf-grow-bmp-bgp-rib-stats] by adding EVPN-specific statistics types to monitor EVPN-related events in RIB-In and RIB-Out for the EVPN address family (AFI=25, SAFI=70).¶
These EVPN-specific statistics provide enhanced visibility into multihoming, IP aliasing, dynamic inter-VRF route leaking (IVRL), route-map applications, and route-type specific counters, among others.¶
The statistics defined herein are gauges (64-bit unsigned integers) unless otherwise specified, following the conventions in [RFC7854]. They apply specifically to to the EV bombing in the EVPN SAFI and extend the per-AFI/SAFI structure where applicable.¶
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 section defines EVPN-specific statistics types for BMP. These statistics are applicable to the EVPN address family (AFI=25, SAFI=70) and extend the RIB statistics framework in [I-D.draft-ietf-grow-bmp-bgp-rib-stats]. Each statistic is a 64-bit gauge unless noted otherwise, and the value can increase or decrease based on route processing events. The counters provide bits and bitmap to indicate Rib-In, Rib-Out and Pre, Post policy indicators if applicable.¶
Consolidated counter for Standard EVPN route types (Type-1 to Type-8) across RIB-In and RIB-Out, Pre-policy and Post-policy stages.¶
Extends BMP RIB statistics defined in [I-D.draft-ietf-grow-bmp-bgp-rib-stats].¶
This statistic is specific to AFI=25, SAFI=70 and includes breakdowns for:¶
Number of EVPN routes are only originated by the router and not relayed. It's helpful to keep a count of hosted EVI's (IMET for layer-2 EVIs) and Ethernet Segments (ESI and I-ESI) via Type-1 and Type-4).¶
The first byte is used for indicating the route-type. As of today, standard route types for EVPN are numbered from 1 to 8¶
Number of Ethernet Segments (ESI) configured for multihoming. Based on [RFC7432] and [RFC9135].¶
The first two bit indicates if its a segment representing layer-2 multihoming or layer-3 multihoming or I-ESI.¶
Number of EVIs tied to an ESI or I-ESI. The first two bit indicate type of Ethernet Segment. The next 80 bits (10 bytes) can represent the ESI value.¶
Number of Aliased path per-EVI. First 4 bytes represent the EVI.¶
Number of EVPN routes leaked across VRFs due to matching route-targets. Related to RIB-In Post-policy (Type 2) as defined in [I-D.draft-ietf-grow-bmp-bgp-rib-stats].¶
The first bit makes a distinction if the leak is indicated by MAC-VRF or layer-3, routing VRF.¶
TBD: if need be, each counter can be indexed with Combination of source VRF and destination VRF.¶
Bitmap indicating which route attributes were modified by route-map (e.g., local-preference, AS-path, MED, community).¶
The 2-byte bitmap includes flags for following attributes and many more, TBD. The exact bitmap for each category can be assigned later:¶
This statistic provides visibility into route-map modifications applied to EVPN routes on a per-attribute basis.¶
IANA is requested to assign the following new parameters to the "BMP Statistics Type" registry:¶
The EVPN-specific statistics defined in this document do not introduce any new security considerations beyond those already specified in [RFC7854] for BMP and in [I-D.draft-ietf-grow-bmp-bgp-rib-stats] for RIB statistics. BMP sessions should be protected using mechanisms such as TCP-AO or TLS to prevent unauthorized access to monitoring data.¶