Route-Distinguisher-Scoped BMP RIB Statistics
draft-dikshit-grow-bmp-rd-scoped-rib-stats-01

Network Working Group                                       S. Dikshit
Internet-Draft                                       Aruba Networks, HPE
Intended status: Standards Track                          M. Srivastava
Expires: 25 February 2027                     Hewlett Packard Enterprise
                                                                  C. Lin
                                                    New H3C Technologies
                                                          26 August 2026

                Route-Distinguisher-Scoped BMP RIB Statistics
              draft-dikshit-grow-bmp-rd-scoped-rib-stats-01

Abstract

   [RFC7854] defines the BGP Monitoring Protocol (BMP) and its
   Statistics Report message.  [I-D.ietf-grow-bmp-bgp-rib-stats]
   (published as [RFC9972]) extended that message with a set of
   advanced, per-AFI/SAFI BGP RIB statistics types.  Several ongoing
   individual contributions independently define additional per-
   address-family, per-instance, or per-Route-Distinguisher (RD)
   statistics on top of that base (for example, EVPN-specific RIB
   statistics and VRF Loc-RIB monitoring enhancements), each proposing
   its own ad hoc Stat Data encoding.

   This document defines a single, address-family-agnostic Stat Data
   container -- the "RD-Scoped Statistics" format -- for BMP
   statistics that are naturally scoped below the per-AFI/SAFI level,
   to a specific Route Distinguisher (VRF instance, EVPN Instance,
   MVPN instance, or equivalent).  Address-family-specific documents,
   such as EVPN-specific BMP RIB statistics, are expected to become
   thin "profiles" of this container rather than defining their own
   wire format, reducing duplication and Stat Type registry
   fragmentation across the GROW working group's BMP statistics work.

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 February 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 February 2027                [Page 1]
Internet-Draft         BMP RD-Scoped RIB Stats             August 2026

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Problem: Registry and Encoding Fragmentation . . . . . . . .   3
   3.  RD-Scoped Statistics Container . . . . . . . . . . . . . . .   4
     3.1.  Stat Data Format  . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Family Registry . . . . . . . . . . . . . . . . . . . . .   5
     3.3.  Relationship to Existing and In-Progress Documents . . .   6
   4.  Global (non-RD-scoped) Companion Statistics . . . . . . . . .   7
   5.  Applicability Guidance for Address-Family-Specific
       Profiles  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   6.  YANG Considerations  . . . . . . . . . . . . . . . . . . . . .   8
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  BMP RD-Scoped Statistics Family Registry . . . . . . . .   8
     7.2.  BMP Statistics Types  . . . . . . . . . . . . . . . . . .   9
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . .   9
   9.  Contributors and Acknowledgements  . . . . . . . . . . . . . .   9
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     10.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Appendix A.  Changes Between Revisions  . . . . . . . . . . . . .  10
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   BMP [RFC7854] Statistics Report messages carry Stat Type / Stat
   Length / Stat Data tuples.  [RFC9972] extended the base set of
   counters/gauges with per-AFI/SAFI statistics, encoding an AFI and
   SAFI directly in Stat Data.

   Operators increasingly need visibility at a finer granularity than
   "per AFI/SAFI": specifically, per virtual routing instance, where
   the instance is identified by a Route Distinguisher (RD) as used in
   BGP/MPLS IP VPNs [RFC4364], EVPN [RFC7432], and MVPN.  At the time
   of writing, at least the following in-progress or recently
   published documents independently define RD-scoped, or closely
   related instance-scoped, statistics or telemetry TLVs:

   *  [I-D.saum-grow-bmp-afi-safi-evpn] defines per-EVI EVPN route
      statistics keyed by an 8-octet Route Distinguisher, with its own
      Stat Data layout (Stat Type, Stat Subtype, RD, Gauge).

   *  [I-D.zhuang-grow-bmp-enhancement-for-vrf-loc-rib] defines a
      Remote VRF Information TLV, keyed by a remote Route
      Distinguisher, for VPNv4/VPNv6 Loc-RIB reporting.

   *  [I-D.wang-grow-bmp-bgp-rib-stats-ext] defines per-AFI/SAFI
      fine-grained filtering statistics with a distinct Flags/AFI/
      SAFI Stat Data prefix.

   Each of these efforts is solving a legitimate, distinct operational

Dikshit, et al.        Expires 25 February 2027                [Page 2]
Internet-Draft         BMP RD-Scoped RIB Stats             August 2026

   problem, but each has (or is likely to end up with) its own Stat
   Data prefix conventions.  Left unaddressed, this fragmentation
   increases implementation cost (every collector needs bespoke
   parsing per document) and increases the likelihood of avoidable
   Stat Type registry collisions or near-duplicate allocations as more
   AFI/SAFI-specific statistics documents are proposed in GROW.

   This document extracts the common shape shared by these efforts --
   a statistic that is scoped to one Route Distinguisher, optionally
   further scoped by a per-family Subtype -- into a single reusable
   Stat Data container.  Address-family-specific documents SHOULD
   reference this container instead of defining a new one, supplying
   only the family-specific Subtype values and statistic semantics.

   This document does not obsolete or replace any of the drafts
   referenced above; it proposes a shared substrate that a future
   revision of each could adopt, and defines the substrate so that new
   RD-scoped statistics proposals (e.g., for MVPN or plain L3VPN
   address families) have an existing, reviewed pattern to reuse
   rather than inventing another one.

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: Registry and Encoding Fragmentation

   Three independent, concurrently active GROW contributions
   (Section 1) each define a Stat Data (or TLV Value) layout that
   begins with some combination of {Stat Subtype, AFI, SAFI, Route
   Distinguisher} followed by a value.  None of the three currently
   references either of the others' encodings.  If each proceeds to
   WGLC independently:

   *  A BMP collector implementer supporting all three must implement
      three separate, incompatible Stat Data parsers for what is
      conceptually the same idea: "a gauge, scoped to one RD, possibly
      further scoped by a route-type Subtype."

   *  Future per-family statistics documents (for MVPN, for plain
      L3VPN Loc-RIB, for SR-TE policies keyed by a color/endpoint
      instead of an RD) have no existing convention to reuse and are
      likely to define a fourth, fifth, and sixth ad hoc encoding.

   *  IANA "BMP Statistics Types" registrations end up describing the
      full Stat Data shape in free-text registry comments, rather
      than pointing to one shared format definition.

Dikshit, et al.        Expires 25 February 2027                [Page 3]
Internet-Draft         BMP RD-Scoped RIB Stats             August 2026

   This document proposes that new work defining RD-scoped statistics
   (while still allocating new Stat Types for new use cases as needed)
   reuse a single Stat Data container definition for the "scoped to
   one RD" case, described in Section 3.

3.  RD-Scoped Statistics Container

3.1.  Stat Data Format

   The RD-Scoped Statistics Stat Data format is as follows.  It is
   used as the Stat Data (value) field of the Stat Type TLV defined in
   Section 4.8 of [RFC7854], in place of a family-specific encoding.

       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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |    Family     |   Subtype     |             AFI               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |    SAFI       |                                               |
      +-+-+-+-+-+-+-+-+                                               +
      |                    Route Distinguisher (8 octets)             |
      +                                                                +
      |                                                                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                       Gauge (64 bits)                         |
      ~                                                                ~
      |                                                                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   *  Family (1 octet): Identifies which address-family "profile" of
      this container applies (e.g., EVPN, L3VPN, MVPN), taken from the
      "BMP RD-Scoped Statistics Family" registry defined in
      Section 7.1.  A BMP implementation MUST ignore Stat Data with an
      unrecognized Family value on receipt.

   *  Subtype (1 octet): A Family-specific discriminator, e.g., an
      EVPN route type as defined in [I-D.saum-grow-bmp-afi-safi-evpn],
      or 0 (Reserved) when the statistic does not need a Subtype.  The
      set of valid Subtype values, and whether Subtype applies at all,
      is defined by the Family-specific profile document, not by this
      document.

   *  AFI (2 octets), SAFI (1 octet): The Address Family Identifier
      and Subsequent Address Family Identifier [RFC4760] of the routes
      the statistic pertains to.  This is included even though Family
      already implies a typical AFI/SAFI, so that a single Family
      value can be reused across closely related SAFIs (e.g., an
      "L3VPN" Family used for both VPN-IPv4 and VPN-IPv6) without
      requiring a new Family registration per SAFI.

Dikshit, et al.        Expires 25 February 2027                [Page 4]
Internet-Draft         BMP RD-Scoped RIB Stats             August 2026

   *  Route Distinguisher (8 octets): The RD of the VRF, EVI, or
      equivalent routing instance the statistic is scoped to, encoded
      per [RFC4364].

   *  Gauge (64 bits): The statistic value, encoded as a 64-bit gauge
      per Section 4.8 of [RFC7854], consistent with [RFC9972].
      Family-specific profiles MAY instead specify that the value is a
      monotonic counter; this must be stated explicitly in the profile
      document.

   This container is deliberately restricted to the single-RD,
   single-gauge case that covers the documents surveyed in Section 2.
   It does not attempt to also subsume the Flags/rate-of-change
   mechanism proposed in [I-D.wang-grow-bmp-bgp-rib-stats-ext]; that
   mechanism addresses a different, orthogonal concern (triggered /
   differential reporting) and MAY be layered independently on top of
   a Stat Type using this container, e.g. by also applying the
   Statistics Information TLV of
   [I-D.ietf-grow-bmp-stats-informational-tlv] to a Stat Type defined
   using this format.

3.2.  Family Registry

   The Family field (Section 3.1) is allocated from a new "BMP RD-
   Scoped Statistics Family" registry (Section 7.1).  This document
   requests IANA to create that registry and to populate it with the
   following initial values, corresponding to already-circulating
   proposals:

   +=======+=================================================+=========+
   | Value | Family                                          | Ref.    |
   +=======+=================================================+=========+
   |   0   | Reserved                                        | RFC-TBD |
   +-------+-------------------------------------------------+---------+
   |   1   | L3VPN (VPN-IPv4 / VPN-IPv6 Loc-RIB)             | RFC-TBD |
   +-------+-------------------------------------------------+---------+
   |   2   | EVPN                                             | RFC-TBD |
   +-------+-------------------------------------------------+---------+
   |   3   | MVPN                                             | RFC-TBD |
   +-------+-------------------------------------------------+---------+
   | 4-127 | Unassigned (Standards Action)                    | --      |
   +-------+-------------------------------------------------+---------+
   |128-254| Unassigned (First Come First Served)             | --      |
   +-------+-------------------------------------------------+---------+
   |  255  | Reserved                                          | RFC-TBD |
   +-------+-------------------------------------------------+---------+

                                 Table 1

   Family value 2 (EVPN) is intended to be claimed by a future
   revision of [I-D.saum-grow-bmp-afi-safi-evpn], re-expressed as a
   profile of this container (Section 3.3); its existing Subtype

Dikshit, et al.        Expires 25 February 2027                [Page 5]
Internet-Draft         BMP RD-Scoped RIB Stats             August 2026

   values (EVPN route types 1-11, as well as the ES/EVI/aliased-path
   information types) map directly onto the Subtype field defined
   here.  Family value 1 (L3VPN) is offered for
   [I-D.zhuang-grow-bmp-enhancement-for-vrf-loc-rib] or a companion
   document to adopt as a statistics (as opposed to TLV-only)
   complement to that draft's Remote VRF Information TLV.  Family
   value 3 (MVPN) is reserved for future work and is not otherwise
   defined by this document.

3.3.  Relationship to Existing and In-Progress Documents

   This document is intentionally scoped as a thin, reusable
   substrate.  It does not itself define any new operator-visible
   statistic; instead it defines the shape that other documents'
   statistics can be expressed in.  Three concrete migration paths are
   anticipated, and authors of the referenced documents are invited to
   pursue whichever (if any) they find useful:

   *  A future [I-D.saum-grow-bmp-afi-safi-evpn] revision could
      redefine its per-EVI statistics (currently Section 2.2 of that
      document, with its own Stat Type/Subtype/RD/Gauge layout) as
      Family=2 (EVPN) instances of the container in Section 3.1,
      without changing the operational semantics of any counter
      already defined there.  The document's global (non-per-EVI)
      statistics (Section 2.1 of that document) are unaffected and
      remain outside the scope of this container; see Section 4.

   *  [I-D.zhuang-grow-bmp-enhancement-for-vrf-loc-rib], which
      currently defines only a Remote VRF Information TLV (no
      counters), could add a companion Stat Type using Family=1
      (L3VPN) to report, e.g., the number of routes leaked into a VRF
      from each remote RD -- directly reusing the Remote Route
      Distinguisher concept that draft already established, and
      addressing the "dynamic inter-VRF route leaking (IVRL)" gap
      noted for the EVPN case in [I-D.saum-grow-bmp-afi-safi-evpn].

   *  New GROW contributions proposing RD-scoped statistics for
      address families not listed in Table 1 (e.g., MVPN) SHOULD
      request a new Family value from IANA (Section 7.1) rather than
      defining a new Stat Data layout.

   No normative change to any of the referenced in-progress documents
   is implied or required by this document; the mappings above are
   offered as non-binding guidance to reduce duplicate encoding work,
   pending discussion with the respective authors.

4.  Global (non-RD-scoped) Companion Statistics

   Some statistics that are conceptually related to an address family
   are not scoped to a single RD -- for example, a global count of
   routes of a given EVPN route type across all EVIs on a router (as

Dikshit, et al.        Expires 25 February 2027                [Page 6]
Internet-Draft         BMP RD-Scoped RIB Stats             August 2026

   defined in Section 2.1 of [I-D.saum-grow-bmp-afi-safi-evpn]).  Such
   statistics remain out of scope for the container defined in
   Section 3.1 and continue to be defined directly against [RFC9972]'s
   existing per-AFI/SAFI Stat Data convention (2-byte AFI, 1-byte
   SAFI, Gauge), optionally with a Family-specific Subtype octet
   appended, without requiring a Route Distinguisher field.  This
   document does not change that convention.

5.  Applicability Guidance for Address-Family-Specific Profiles

   A document profiling this container (a "Family document") is
   expected to specify at least:

   *  The Family value it claims (registered per Section 7.1).

   *  Whether Subtype is used, and if so, its value space and
      semantics (e.g., route-type enumeration).

   *  Whether AFI/SAFI is redundant with Family for that profile (and
      therefore fixed to a single well-known pair) or genuinely
      variable (e.g., a family spanning both an IPv4 and IPv6 SAFI).

   *  Which specific Stat Type code point(s), allocated from the "BMP
      Statistics Types" registry [RFC7854], carry Stat Data in this
      container's format, and what each Stat Type's Gauge counts.

   *  Whether the counters are gauges or monotonic counters (Section
      3.1 defaults to gauge, consistent with the majority of existing
      RFC 9972-style statistics).

   A Family document is NOT required to duplicate the wire-format
   figure in Section 3.1; it MAY simply reference this document and
   list only the Family-specific parameters above.

6.  YANG Considerations

   [I-D.ietf-grow-bmp-yang] defines a YANG data model for BMP.  At the
   time of writing, this reviewer-observed gap applies: none of
   [RFC9972]'s advanced statistics, the EVPN-specific statistics of
   [I-D.saum-grow-bmp-afi-safi-evpn], or the routing-policy change
   statistics of [I-D.smc-grow-bmp-route-change-stats] appear to be
   modeled in the published revisions of [I-D.ietf-grow-bmp-yang]
   available to the authors when this document was written.  Authors
   of this document intend to propose a YANG augmentation, generic
   over the Family registry defined in Section 7.1, so that RD-scoped
   statistics defined against this container can be represented in
   that model without each Family document needing to define its own
   YANG augmentation independently.  This is noted here as a
   dependency to be tracked, not as a normative requirement of this
   document.

Dikshit, et al.        Expires 25 February 2027                [Page 7]
Internet-Draft         BMP RD-Scoped RIB Stats             August 2026

7.  IANA Considerations

   The registration procedures referenced in this section ("Standards
   Action" and "First Come First Served") are to be interpreted as
   described in [RFC8126].

7.1.  BMP RD-Scoped Statistics Family Registry

   IANA is requested to create a new registry, "BMP RD-Scoped
   Statistics Family", within the "BGP Monitoring Protocol (BMP)
   Parameters" registry group.  Registration procedures for this
   registry are:

   *  Values 0, 255: Reserved.

   *  Values 4-127: Standards Action.

   *  Values 128-254: First Come First Served.

   Initial values are as listed in Table 1 (Section 3.2).

7.2.  BMP Statistics Types

   This document does not itself request any new Stat Type code
   points from the "BMP Statistics Types" registry [RFC7854]; it
   defines a Stat Data format that Family-specific documents use when
   they request their own Stat Type code points.  Such documents
   SHOULD note, in their IANA Considerations section, that the
   requested Stat Type's Stat Data is encoded per Section 3.1 of this
   document.

8.  Security Considerations

   This document defines a Stat Data encoding convention; it does not
   change the BMP session security model.  The security considerations
   of [RFC7854] apply.  As with any RD-scoped statistic, exposing per-
   VRF or per-EVI route counts and leak counts to a BMP collector
   reveals customer-instance-level operational detail; deployments
   SHOULD restrict BMP session access to authorized collectors and
   SHOULD use transport security (e.g., TCP-AO [RFC5925] or a TLS
   profile for BMP) consistent with the guidance already given in the
   Family documents referenced in this document.

9.  Contributors and Acknowledgements

   The authors thank the authors of
   [I-D.saum-grow-bmp-afi-safi-evpn],
   [I-D.zhuang-grow-bmp-enhancement-for-vrf-loc-rib], and
   [I-D.wang-grow-bmp-bgp-rib-stats-ext] for the analysis that
   motivated this document; this document does not speak on their
   behalf and any errors in characterizing their proposals are the
   present authors' own.

Dikshit, et al.        Expires 25 February 2027                [Page 8]
Internet-Draft         BMP RD-Scoped RIB Stats             August 2026

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,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC4364]  Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
              Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364,
              February 2006, <https://www.rfc-editor.org/info/rfc4364>.

   [RFC4760]  Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
              "Multiprotocol Extensions for BGP-4", RFC 4760,
              DOI 10.17487/RFC4760, January 2007,
              <https://www.rfc-editor.org/info/rfc4760>.

   [RFC7854]  Scudder, J., Ed., Fernando, R., and S. Stuart, "BGP
              Monitoring Protocol (BMP)", RFC 7854,
              DOI 10.17487/RFC7854, June 2016,
              <https://www.rfc-editor.org/info/rfc7854>.

   [RFC8126]  Cotton, M., Leiba, B., and T. Narten, "Guidelines for
              Writing an IANA Considerations Section in RFCs", BCP 26,
              RFC 8126, DOI 10.17487/RFC8126, June 2017,
              <https://www.rfc-editor.org/info/rfc8126>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

10.2.  Informative References

   [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.saum-grow-bmp-afi-safi-evpn]
              Dikshit, S., Srivastava, M., and C. Lin, "EVPN-Specific
              BMP RIB Statistics Extensions", Work in Progress,
              Internet-Draft, draft-saum-grow-bmp-afi-safi-evpn-06,
              25 July 2026.

   [I-D.smc-grow-bmp-route-change-stats]
              Dikshit, S., Srivastava, M., and C. Lin, "BMP Route

Dikshit, et al.        Expires 25 February 2027                [Page 9]
Internet-Draft         BMP RD-Scoped RIB Stats             August 2026

              Change Statistics Based on Routing Policy", Work in
              Progress, Internet-Draft, draft-smc-grow-bmp-route-
              change-stats-02, 25 July 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.

   [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.

   [RFC5925]  Touch, J., Mankin, A., and R. Bonica, "The TCP
              Authentication Option", RFC 5925, DOI 10.17487/RFC5925,
              June 2010, <https://www.rfc-editor.org/info/rfc5925>.

   [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, <https://www.rfc-editor.org/info/rfc7432>.

Appendix A.  Changes Between Revisions

   This section is to be removed before publishing as an RFC.

   v00 -> v01

   *  Added an introductory sentence to Section 7 citing [RFC8126] for
      the "Standards Action" and "First Come First Served" terms used
      in Section 7.1, and added [RFC8126] to Normative References.
      Neither the new registry definition nor its initial values
      (Table 1) changed.

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

Dikshit, et al.        Expires 25 February 2027               [Page 10]
Internet-Draft         BMP RD-Scoped RIB Stats             August 2026

   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