Network Working Group S. Dikshit Internet-Draft Aruba Networks, HPE Intended status: Standards Track M. Srivastava Expires: 25 January 2027 Hewlett Packard Enterprise C. Lin New H3C Technologies 25 July 2026 EVPN-Specific BMP RIB Statistics Extensions draft-saum-grow-bmp-afi-safi-evpn-06 Abstract This document defines new EVPN-specific BGP Monitoring Protocol (BMP) statistics types. These extensions include scalar counters for EVPN route types specifically, while also keeping scope for defining counters which are EVPN route-type agnostic but related to BGP-EVPN RIB like, number of multihoming Ethernet Segments, number of multihomed EVIs, number of aliased paths, number of dynamic inter-VRF route leaking (IVRL). This revision (-06) firms up the specification for working group consideration: it adds a Relationship to Other Work section that explicitly maps this document to concurrently circulating GROW contributions on BMP statistics and TLV extensions and invites coordination with their authors, corrects the YANG alignment reference, strengthens Security Considerations, and adds a worked example. No statistics semantics, Stat Type/Subtype allocations, or wire formats defined in -05 are changed. 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 25 January 2027. 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. Dikshit, et al. Expires 25 January 2027 [Page 1] Internet-Draft EVPN-Specific BMP RIB Stats July 2026 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 2. EVPN-Specific BMP Statistics Extensions . . . . . . . . . . 3 2.1. Global EVPN Route Statistics . . . . . . . . . . . . . . 3 2.1.1. Statistics Definitions . . . . . . . . . . . . . . . 3 2.1.2. Statistics Format . . . . . . . . . . . . . . . . . . 4 2.2. Per-EVI EVPN Route Statistics . . . . . . . . . . . . . 5 2.2.1. Statistics Definitions . . . . . . . . . . . . . . . 5 2.2.2. Statistics Format . . . . . . . . . . . . . . . . . . 5 2.3. Worked Example . . . . . . . . . . . . . . . . . . . . . 6 3. Relationship to Other Work and Call for Collaboration . . . 6 4. YANG Model Alignment . . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 9 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 9.1. Normative References . . . . . . . . . . . . . . . . . . 10 9.2. Informative References . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 1. Introduction [RFC7854] defines different BMP statistics message types and [RFC9972] extends the BMP statistics to provide more insights into the BGP RIBs. This document extends the BMP RIB statistics by adding EVPN-specific statistics types to monitor EVPN-related events in Adj-RIB-In, Adj-RIB-Out, and Local-RIB for the EVPN address family (AFI=25, SAFI=70) as defined in [RFC7432] and extended by [RFC9135] for integrated routing and bridging, forms the basis for these statistics. The format of the BMP statistics message remains same as defined in [RFC7854]. 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. EVPN-Specific BMP Statistics Extensions This section defines EVPN-specific statistics types for BMP, applicable to the EVPN address family (AFI=25, SAFI=70). These statistics type for all 5 RIB views: Adj-RIB-In-Pre, Adj-RIB-In-Post, Local-RIB, Adj-RIB-Out-Pre and Adj-RIB-Out-Pre. and to define more specific counters other than the route-types in future. Dikshit, et al. Expires 25 January 2027 [Page 2] Internet-Draft EVPN-Specific BMP RIB Stats July 2026 2.1. Global EVPN Route Statistics The section defines global EVPN route or other information statistics, e.g., the overall Ethernet Auto-discovery Route counters. 2.1.1. Statistics Definitions This section defines different statistics type for global EVPN monitoring type. * Type=TBD_01: Statistics for global EVPN routes received in Adj-RIB-In before inbound policy is applied. * Type=TBD_02: Statistics for global EVPN routes in Adj-RIB-In after inbound policy is applied. * Type=TBD_03: Statistics for global EVPN routes in the local RIB. * Type=TBD_04: Statistics for global EVPN routes in Adj-RIB-Out before outbound policy is applied. * Type=TBD_05: Statistics for global EVPN routes in Adj-RIB-Out after outbound policy is applied. * Type=TBD_06: Statistics for global EVPN information of ESs/EVIs/aliased paths. 2.1.2. Statistics Format The statistics values are encoded as 1-octet Stats types, 1-octet Stats Subtype followed by 64-bit gauges. The statistics values are encoded in Stat Data as defined in 4.8 of [RFC7854]. Each counter is encoded as follows: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Stats Type | Stats Subtype | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Gauge (64 bits) | ~ ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ * Stats Type (1 octet): EVPN stats type. Defined types are: - Type = 0: EVPN route statistics in the RIB. - Type = 1: EVPN leaked route statistics in the local RIB. - Type = 2: EVPN multihoming Ethernet Segments (ESs) statistics. - Type = 3: EVPN multihomed EVPN instances (EVIs) statistics. - Type = 4: EVPN aliased paths statistics. Dikshit, et al. Expires 25 January 2027 [Page 3] Internet-Draft EVPN-Specific BMP RIB Stats July 2026 * Stats Subtype (1 octet): Indicates the EVPN route type associated with this statistic, as defined in: - Subtype = 0: Reserved. - Subtype = 1: EVPN route type 1 (Ethernet Auto-discovery). - Subtype = 2: EVPN route type 2 (MAC/IP Advertisement). - Subtype = 3: EVPN route type 3 (Inclusive Multicast Ethernet Tag Route). - Subtype = 4: EVPN route type 4 (Ethernet Segment Route). - Subtype = 5: EVPN route type 5 (IP Prefix Route). - Subtype = 6: EVPN route type 6 (Selective Multicast Ethernet Tag Route). - Subtype = 7: EVPN route type 7 (IGMP Join Synchronization Route). - Subtype = 8: EVPN route type 8 (IGMP Leave Synchronization Route). - Subtype = 9: EVPN route type 9 (Per-Region I-PMSI A-D route). - Subtype = 10: EVPN route type 10 (S-PMSI A-D route). - Subtype = 11: EVPN route type 11 (Leaf A-D route). Stats Subtype is only used when Stats Type is set to 0 and 1; otherwise, Stats Subtype is omitted. A BMP implementation MUST ignore unrecognized stat types on receipt, and likewise MUST ignore unexpected data in the Stat Data field. 2.2. Per-EVI EVPN Route Statistics The section defines specific EVI EVPN route statistics, e.g., per-EVI IP Prefix Route counters. 2.2.1. Statistics Definitions This section defines different statistics type for per-EVI EVPN monitoring type. * Type=TBD_07: Statistics for per-EVI EVPN routes received in Adj-RIB-In before inbound policy is applied. * Type=TBD_08: Statistics for per-EVI EVPN routes in Adj-RIB-In after inbound policy is applied. * Type=TBD_09: Statistics for per-EVI EVPN routes in the local RIB. * Type=TBD_10: Statistics for per-EVI EVPN routes in Adj-RIB-Out before outbound policy is applied. * Type=TBD_11: Statistics for per-EVI EVPN routes in Adj-RIB-Out after outbound policy is applied. Dikshit, et al. Expires 25 January 2027 [Page 4] Internet-Draft EVPN-Specific BMP RIB Stats July 2026 2.2.2. Statistics Format The statistics values are encoded as 1-octet Stats types, 1-octet Stats Subtype, and 8-octet Route Distinguisher (RD) followed by 64-bit gauges. The statistics values are encoded in Stat Data as defined in 4.8 of [RFC7854]. Each counter is encoded as follows: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Stats Type | Stats Subtype | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Route Distinguisher (RD) | | (8 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Gauge (64 bits) | ~ ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ * Stats Type (1 octet): EVPN stats type, as defined in Section 2.1.2. * Stats Subtype (1 octet): Indicates the EVPN route type associated with this statistic, as defined in Section 2.1.2. * Route Distinguisher (RD) (8 octets): Indicates source EVI associated with the EVPN route. The Route Distinguisher (RD) field MUST be populated with the corresponding source EVI's RD of the EVPN route. 2.3. Worked Example This non-normative example illustrates a Statistics Report message carrying a per-EVI IP Prefix Route counter (Section 2.2) for a PE with EVI Route Distinguisher 65001:100, reporting 42 active EVPN route type 5 prefixes in its Local-RIB: Stats Type = TBD_09 (loc-rib-evpn-route-per-evi-stats) Stats Subtype = 5 (EVPN route type 5, IP Prefix Route) RD = 65001:100 Gauge = 42 A collector receiving this Stat Data, together with the per-EVI Remote VRF Information carried by a companion mechanism such as [I-D.zhuang-grow-bmp-enhancement-for-vrf-loc-rib] (see Section 3), can attribute the 42 routes both to a count (this document) and, where available, to the specific remote VRF/EVI instance they were learned from (that document's TLV). Dikshit, et al. Expires 25 January 2027 [Page 5] Internet-Draft EVPN-Specific BMP RIB Stats July 2026 3. Relationship to Other Work and Call for Collaboration Several documents currently active in GROW define statistics or TLV extensions to BMP that intersect with the scope of this document. This section maps this document explicitly against that work and records specific collaboration proposals; it does not change the semantics or wire format of any statistic defined in Section 2. * [I-D.zhuang-grow-bmp-enhancement-for-vrf-loc-rib] defines a Remote VRF Information TLV that lets a BMP Loc-RIB [RFC9069] report identify the remote VRF/EVI a VPN route was learned from. That document's Section 1 example is structurally identical to the dynamic inter-VRF route leaking (IVRL) scenario this document's Type=1 (EVPN leaked route statistics) counter is intended to quantify: their TLV supplies the "from which remote instance" topology detail, while our Type=1/Type=3 counters supply the "how many, and how often" volumetric detail. Today, an operator has no single-document way to correlate the two. We propose to the authors of that document (S. Zhuang, N. Geng, H. Wang) that a joint follow-up either (a) adds an EVPN-scoped counterpart to their Remote VRF Information TLV referencing this document's per-EVI statistics types, or (b) is captured by generalizing this document's per-EVI Stat Data format, as outlined in [I-D.dikshit-grow-bmp-rd-scoped-rib-stats]. We welcome co-authorship or contributed text on this point. * [I-D.wang-grow-bmp-bgp-rib-stats-ext] introduces a 4-bit Flags field (Triggered/Differential bits) into the Stat Type TLV header used for its fine-grained filtering statistics. The per-EVI and global EVPN counters defined in Section 2 of this document use the unmodified [RFC7854]/[RFC9972] Stat Data layout and do not currently have an equivalent triggered/differential reporting capability. Rather than this document defining a second, incompatible flags convention, we propose that the Flags field defined in [I-D.wang-grow-bmp-bgp-rib-stats-ext] Section 2 be generalized (in that document, or in a shared companion document) so that EVPN statistics types defined here can also set the Triggered/Differential bits when a future revision of this document adopts them. We invite L. Wang, N. Geng, L. Li, and S. Zhuang to discuss whether that flags octet should be lifted out into its own short, reusable BMP Stat Type TLV extension document that both efforts can reference. * [I-D.ietf-grow-bmp-stats-informational-tlv], already adopted by the GROW working group and co-authored by two of this document's authors (M. Srivastava, C. Lin) together with S. Kolenchery, defines a Statistics Information TLV carrying minimum, maximum, average, and median values alongside a gauge. The per-EVI and global EVPN gauges defined in Section 2 of this document are directly applicable inputs to that TLV; implementations reporting EVPN statistics SHOULD consider also applying [I-D.ietf-grow-bmp-stats-informational-tlv] to smooth short-term EVI-level churn (e.g., during mass Ethernet Segment failover) for collector consumption. Dikshit, et al. Expires 25 January 2027 [Page 6] Internet-Draft EVPN-Specific BMP RIB Stats July 2026 * [I-D.dikshit-grow-bmp-rd-scoped-rib-stats], authored by the same authors as this document, proposes generalizing the Stat Data format of Section 2.2 (Stats Type, Stats Subtype, 8-octet RD, Gauge) into a family-agnostic "RD-Scoped Statistics" container applicable beyond EVPN to L3VPN and MVPN. A future revision of this document may adopt that container as the wire format for Section 2.2, registering EVPN as Family=2 in that document's registry, without changing any Stat Type allocation requested in Section 5 of this document. Authors of the documents referenced above are encouraged to bring any of these coordination points to the GROW mailing list or to a future GROW session so that Stat Type TLV conventions and registry entries can be aligned before multiple, mutually incompatible variants reach working group last call. 4. YANG Model Alignment The counters defined in this document are intended to align with a YANG model for EVPN monitoring. The -05 revision of this document referenced [I-D.ietf-bess-evpn-yang-07] for that alignment; that document has since expired (it was last updated in March 2019) and SHOULD NOT be relied upon as a current reference. Route type counters are intended to map to YANG leaves for EVPN route statistics, multihoming and IVRL counters are intended to align with Ethernet Segment and VRF-related leaves, and segment failure impact is intended to align with failure event counters, but no currently maintained EVPN YANG module implements these leaves. Separately, [I-D.ietf-grow-bmp-yang], the active GROW working group YANG model for BMP itself, does not yet model [RFC9972]'s advanced statistics types or the EVPN-specific statistics types defined in this document. The authors intend to propose a YANG augmentation of [I-D.ietf-grow-bmp-yang] covering both, and, if [I-D.dikshit-grow-bmp-rd-scoped-rib-stats] proceeds, to model that document's generalized container instead of a one-off EVPN-specific augmentation. Implementations SHOULD treat both YANG alignment statements in this section as informative and subject to revision as that augmentation work proceeds. 5. IANA Considerations This document requests that IANA assign new BMP statistics types from the "BMP Statistics Type" registry for the following: * Type TBD_01: rib-in-pre-evpn-route-stats: Statistics for global EVPN routes received before inbound policy is applied. * Type TBD_02: rib-in-post-evpn-route-stats: Statistics for global EVPN routes after inbound policy is applied. * Type TBD_03: loc-rib-evpn-route-stats: Statistics for global EVPN routes in the local RIB. * Type TBD_04: rib-out-pre-evpn-route-stats: Statistics for global EVPN routes before outbound policy is applied. Dikshit, et al. Expires 25 January 2027 [Page 7] Internet-Draft EVPN-Specific BMP RIB Stats July 2026 * Type TBD_05: rib-out-post-evpn-route-stats: Statistics for global EVPN routes after outbound policy is applied. * Type TBD_06: rib-out-post-evpn-info-stats: Statistics for global EVPN information of ESs/EVIs/aliased paths. * Type TBD_07: rib-in-pre-evpn-route-per-evi-stats: Statistics for per-EVI EVPN routes received before inbound policy is applied. * Type TBD_08: rib-in-post-evpn-route-per-evi-stats: Statistics for per-EVI EVPN routes after inbound policy is applied. * Type TBD_09: loc-rib-evpn-route-per-evi-stats: Statistics for per-EVI EVPN routes in the local RIB. * Type TBD_10: rib-out-pre-evpn-route-per-evi-stats: Statistics for per-EVI EVPN routes before outbound policy is applied. * Type TBD_11: rib-out-post-evpn-route-per-evi-stats: Statistics for per-EVI EVPN routes after outbound policy is applied. The 11 types are sufficient to provide generic monitoring of EVPN route types across Adj-RIB-In, Adj-RIB-Out, and Local-RIB. 6. Security Considerations The security considerations of [RFC7854] apply to this document. The per-EVI statistics defined in Section 2.2 reveal, per Route Distinguisher, the volume of EVPN routes, leaked routes, and multihoming state associated with a specific EVI. Where an EVI corresponds to a customer-facing tenant instance, this is customer-instance-level operational detail comparable in sensitivity to the remote-VRF topology information discussed in the Security Considerations of [I-D.zhuang-grow-bmp-enhancement-for-vrf-loc-rib]. As with that document, implementations SHOULD restrict BMP session access to authorized and trusted monitoring devices and SHOULD use transport security (e.g., TCP-AO [RFC5925] or a TLS profile for BMP) consistent with Section 11 of [RFC7854]. No new protocol interactions beyond the BMP Statistics Report message defined in [RFC7854] are introduced by this document. 7. Contributors The following people made significant contributions to this document: To be added. 8. Acknowledgements The authors would like to acknowledge the GROW working group and the authors of the related documents cited in Section 3 for their ongoing work in this space; specific review credit will be added as discussion on the coordination points in Section 3 progresses. Dikshit, et al. Expires 25 January 2027 [Page 8] Internet-Draft EVPN-Specific BMP RIB Stats July 2026 9. References 9.1. Normative References [RFC7854] Scudder, J., Ed., Fernando, R., and S. Stuart, "BGP Monitoring Protocol (BMP)", RFC 7854, DOI 10.17487/RFC7854, June 2016, . [RFC7432] Sajassi, A., Aggarwal, R., Bitar, N., Isaac, A., Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February 2015, . [RFC9135] Sajassi, A., Drake, J., Boutros, S., and J. Rabadan, "Integrated Routing and Bridging in Ethernet VPN (EVPN)", RFC 9135, DOI 10.17487/RFC9135, October 2021, . [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, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [RFC5925] Touch, J., Mankin, A., and R. Bonica, "The TCP Authentication Option", RFC 5925, DOI 10.17487/RFC5925, June 2010, . 9.2. Informative References [I-D.ietf-bess-evpn-yang-07] Brissette, P., Shah, H., Chen, I., and K. Patel, "Yang Data Model for EVPN", Work in Progress, Internet-Draft, draft-ietf-bess-evpn-yang-07, March 2019 (expired). [I-D.ietf-grow-bmp-yang] Work in Progress, Internet-Draft, draft-ietf-grow-bmp- yang-09, 15 June 2026. [I-D.ietf-grow-bmp-stats-informational-tlv] Srivastava, M., Kolenchery, S., and C. Lin, "BMP Statistics Information TLV", Work in Progress, Internet- Draft, draft-ietf-grow-bmp-stats-informational-tlv-00, 12 May 2026. [I-D.wang-grow-bmp-bgp-rib-stats-ext] Wang, L., Geng, N., Li, L., and S. Zhuang, "BGP RIB Fine-Grained Filtering Statistics Extensions for BGP Monitoring Protocol (BMP)", Work in Progress, Internet- Draft, draft-wang-grow-bmp-bgp-rib-stats-ext-01, 5 July 2026. Dikshit, et al. Expires 25 January 2027 [Page 9] Internet-Draft EVPN-Specific BMP RIB Stats July 2026 [I-D.zhuang-grow-bmp-enhancement-for-vrf-loc-rib] Zhuang, S., Geng, N., and H. Wang, "Enhancement for Monitoring VRF's Loc-RIB", Work in Progress, Internet- Draft, draft-zhuang-grow-bmp-enhancement-for-vrf-loc- rib-01, 6 July 2026. [I-D.dikshit-grow-bmp-rd-scoped-rib-stats] Dikshit, S., Srivastava, M., and C. Lin, "Route-Distinguisher-Scoped BMP RIB Statistics", Work in Progress, Internet-Draft, draft-dikshit-grow-bmp-rd- scoped-rib-stats-00, 25 July 2026. Authors' Addresses Saumya Dikshit Aruba Networks, HPE Mahadevpura Bangalore 560 048 Karnataka India Email: saumya.dikshit@hpe.com Mukul Srivastava Hewlett Packard Enterprise 10 Technology Park Dr Westford, MA 01886 United States of America Email: mukul.srivastava@hpe.com Changwang Lin New H3C Technologies 8 Yongjia North Road Beijing Haidian District, 100094 China Email: linchangwang.04414@h3c.com Dikshit, et al. Expires 25 January 2027 [Page 10]