Internet-Draft BMP Route Change Stats November 2026
Dikshit, et al. Expires 24 May 2027 [Page]
Workgroup:
Network Working Group
Internet-Draft:
draft-smc-grow-bmp-route-change-stats-04
Published:
Intended Status:
Standards Track
Expires:
Authors:
S. Dikshit
Hewlett Packard Enterprise
M. Srivastava
Hewlett Packard Enterprise
C. Lin
New H3C Technologies

BMP Route Change Statistics Based on Routing Policy

Abstract

This document defines few generic BGP Monitoring Protocol (BMP) statistics for monitoring route modifications or changes due to applying Routing Policy. These statistics are reported per BGP peer using the BMP Statistics Report message.

This revision (-02) 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 policy-driven telemetry and invites coordination with their authors, adds a worked example, and strengthens Security Considerations. No statistics semantics, Stat Type allocations, or wire formats defined in -01 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 24 May 2027.

▲

Table of Contents

1. Introduction

[RFC7854] and [RFC8671] defines different BMP statistics, and [RFC9972] extends these BMP statistics to provide more insights into the BGP RIBs.

Routing Policy are widely used in BGP to modify route attributes. Monitoring which route attributes are modified and how often can provide valuable insights for network operators.

This document defines few BMP statistics to report such route modifications in a generic and address-family-independent manner. The format of the BMP statistics message remains same as defined in [RFC7854]. Besides address family and gauge in the Stat Data (value) [RFC7854], these statistics also provide attribute types of route changes. This route attribute could be the BGP path attributes [RFC4271] or additional route attributes for QoS and forwarding-related parameters.

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. The BCP14 is used to stress importance for operators but are not required as formal implementation requirement.

2. Motivation and Use Cases

The ability to track route modifications via Routing Policy enables operators to understand policy impact, detect misconfigurations, and analyze routing behavior. The attribute type and gauge allow external collectors to derive distribution insights.

3. Per-Peer Reporting

The BMP peer statistics report message is reported per BGP peer. Therefore, each route attribute modification count is associated with a specific peer, enabling peer-level policy analysis.

For locally originated routes applying routing policy, the peer is regarded as the local router itself, per Section 8.2 of [RFC7854].

4. Route Change Statistics based on Routing Policy

4.1. Statistics Format

The statistics defined in this document indicate which route attributes were modified by routing policy, using a 2-octet Attribute Type value followed by a 64-bit Gauge. They are applicable to all BGP address families, represented by an Address Family Identifier (AFI) and Subsequent Address Family Identifier (SAFI) [RFC4760]. The Stat Data (value) carries a 2-octet AFI, a 1-octet SAFI, and a 1-octet NUM count, followed by NUM repetitions of a 2-octet Attribute Type and a 64-bit Gauge. The full BMP Statistics Report TLV, including its Stat Type and Stat Length header, is shown below:

BMP Stat Type TLV header (Section 4.8 of RFC 7854):

  Field                 Size       Value
  -------------------   --------   ---------------------------
  Stat Type             2 octets   TBD_01 or TBD_02
  Stat Length           2 octets   4 + 10 * NUM

Stat Data (value):

  Field                 Size       Meaning
  -------------------   --------   ---------------------------
  AFI                   2 octets   address family
  SAFI                  1 octet    subsequent address family
  NUM                   1 octet    number of attribute entries
  Attribute Type        2 octets   attribute that changed
  Gauge                 8 octets   route count

The Attribute Type and Gauge fields repeat as a pair, NUM times, with no padding between entries. Each entry is 10 octets, so Stat Length is 4 + (10 * NUM) octets, counting the AFI field through the last Gauge.

  • AFI: The AFI value is defined in IANA Address Family Numbers.

  • SAFI: The SAFI value is defined in IANA SAFI Values.

  • NUM: Indicates that the number of attribute types included in the same message.

  • Attribute Type: Indicates which route attribute was modified by applying routing policy. The attribute type supports up to 2^16 types. In addition to the types defined in this document, new attribute types of route change may be defined in the future. The attribute type defined in this document is as follows:

    • Attribute Type = 0x0001: Local Preference.

    • Attribute Type = 0x0002: AS Path.

    • Attribute Type = 0x0003: MED.

    • Attribute Type = 0x0004: Community.

    • Attribute Type = 0x0005: Extended Community.

    • Attribute Type = 0x0006: Large Community.

    • Attribute Type = 0x0007: Origin.

    • Attribute Type = 0x0008: Next Hop.

    • Attribute Type = 0x0009: ESI.

    • Attribute Type = 0x000A: AIGP.

    • Attribute Type = 0x000B: Prefix SID.

    • Attribute Type = 0x000C: DSCP.

    • Attribute Type = 0x000D: VPN Peer ID.

    • Attribute Type = 0x000E: Preferred Value.

    • Attribute Type = 0x000F: IP Precedence.

    • Attribute Type = 0x0010: QoS Local ID.

    • Attribute Type = 0x0011: Traffic Index.

    • Attribute Type = 0x0012: MPLS EXP.

    • Attribute Type = 0x0013-0xFFFF: Reserved, Vendor-specific route attribute range.

These statistics apply only to the AFI/SAFIs that a BGP speaker supports and has negotiated with its peer [RFC4760]. The following counting rules apply:

  • An Attribute Type that has not been modified by routing policy MUST NOT be included in the TLV.

  • Routes that are rejected or dropped by inbound or outbound policy MUST NOT increment any attribute gauge.

The statistics defined in this document report aggregate post-commit policy modifications. They complement pre-commit policy evaluation ([I-D.wang-grow-bmp-policy-preview]) and per-event route logging ([I-D.ietf-grow-bmp-rel]); Section 5 maps these relationships in detail.

An implementation MAY additionally report these statistics scoped to a routing instance such as a VRF or EVI; see Section 4.4.

4.2. Statistics Definition

  • Stat Type = TBD_01: (64-bit Gauge) Number of routes with specific change attribute in per-AFI/SAFI post-policy Adj-RIB-In due to the application of inbound policy.

  • Stat Type = TBD_02: (64-bit Gauge) Number of routes with specific change attribute in per-AFI/SAFI post-policy Adj-RIB-Out due to the application of outbound policy.

4.3. Worked Example

This non-normative example illustrates a Statistics Report message for a peer negotiated for IPv4 unicast (AFI=1, SAFI=1), where the outbound policy modified two attributes across the current Adj-RIB-Out:

AFI  = 1 (IPv4)
SAFI = 1 (unicast)
NUM  = 2
Stat Type = TBD_02 (rib-out-post-policy-attr-change-stats)
  Attribute Type = 0x0001 (Local Preference), Gauge = 128
  Attribute Type = 0x0004 (Community),        Gauge = 47

This indicates that, at the time of reporting, 128 routes in the
post-policy Adj-RIB-Out for this peer/AFI/SAFI had their Local
Preference modified by outbound policy, and 47 had a Community
modified, since the counters were last reset.  See Section 5 for
how this per-peer, post-commit accounting relates to the
pre-commit, per-event deltas proposed in
[I-D.wang-grow-bmp-policy-preview].

4.4. Optional Instance-Scoped Reporting

The statistics above are reported per peer and per AFI/SAFI. On a Route Reflector or an inter-AS border router, a per-peer, per-AFI/SAFI counter records that an attribute such as an Extended Community, a Next Hop, or an ESI was changed by policy, but not which routing instance the affected routes belong to. An implementation MAY additionally report these statistics scoped to a Route Distinguisher, for example through a Family profile of the RD-scoped Stat Data container (Section 3.1 of [I-D.dikshit-grow-bmp-rd-scoped-rib-stats]) in which the Attribute Type is carried in that container's Subtype space, so that each (Route Distinguisher, Attribute Type) pair is reported as one gauge and a policy change can be attributed to the specific VRF or EVI affected. A producer that does not maintain these statistics per instance continues to report them per peer and per AFI/SAFI as defined above.

4.5. Receiver Behavior for Unknown Selectors

Consistent with Section 3 of [RFC9972], a collector that does not recognize the Stat Type MUST ignore the entire TLV by skipping (4 + Stat Length) octets and continue parsing subsequent TLVs.

Each attribute entry inside the Stat Data has a fixed length of 10 octets (a 2-octet Attribute Type and an 8-octet Gauge). A collector that recognizes the Stat Type but encounters an unrecognized Attribute Type MUST ignore that 10-octet entry, advance to the next entry, and continue processing the remaining entries in the TLV, without resetting the BMP session.

5. Relationship to Other Work and Call for Collaboration

Several documents currently active in GROW address policy-driven route changes or telemetry from complementary angles. 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 4.

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 the Attribute Type registry and Flags conventions can be aligned before multiple, mutually incompatible variants reach working group last call.

6. Operational Considerations

When these statistics are exported from an Adj-RIB-In or Adj-RIB-Out on a Route Reflector or Route Server, the counts reflect only the routes present in that RIB after inbound or outbound policy, Route Target Constrain [RFC4684], and best-path or Add-Path selection have been applied. Such counts describe the constrained or selected subset seen by that node rather than the entire fabric. A producer SHOULD be able to rate-limit the reporting interval, and, where instance-scoped reporting (Section 4.4) is used, SHOULD allow an operator to select a subset of instances, so that a high-cardinality deployment does not emit an unbounded volume of statistics.

7. Security Considerations

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], and Section 8 of [RFC8671] are also applicable to the gauges defined in this document.

In addition, an observer of the aggregated per-peer,
per-attribute-type counters defined in Section 4.2 can infer, over
time, which route attributes a network operator actively adjusts
via policy and how often, which is a coarser-grained but analogous
disclosure concern to the one raised for the pre-commit policy
deltas in the Security Considerations of
[I-D.wang-grow-bmp-policy-preview].  As with that document, BMP
sessions carrying these statistics SHOULD be protected using
TCP-AO [RFC5925] or a TLS profile for BMP, consistent with
Section 11 of [RFC7854].

8. IANA Considerations

IANA has assigned the following new parameters in the BMP Statistics Types registry, part of the BMP parameters registry group.

This document requests IANA to update these entries as follows. Also, the document requests IANA to update the reference cited for the entries.

9. Contributors

The following people made significant contributions to this document:

To be added.

10. Acknowledgements

The authors would like to acknowledge the GROW working group and the authors of the related documents cited in Section 5 for their ongoing work in this space; specific review credit will be added as discussion on the coordination points in Section 5 progresses.

11. References

11.1. Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
[RFC4271]
Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, DOI 10.17487/RFC4271, , <https://www.rfc-editor.org/info/rfc4271>.
[RFC4760]
Bates, T., Chandra, R., Katz, D., and Y. Rekhter, "Multiprotocol Extensions for BGP-4", RFC 4760, DOI 10.17487/RFC4760, , <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, , <https://www.rfc-editor.org/info/rfc7854>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.
[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, , <https://www.rfc-editor.org/info/rfc8671>.
[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, , <https://www.rfc-editor.org/info/rfc9972>.
[RFC5925]
Touch, J., Mankin, A., and R. Bonica, "The TCP Authentication Option", RFC 5925, DOI 10.17487/RFC5925, , <https://www.rfc-editor.org/info/rfc5925>.

11.2. Informative References

[I-D.wang-grow-bmp-policy-preview]
Wang, L., Geng, N., Li, L., and S. Zhuang, "BGP Route Policy Pre-view and Intent Verification Using BGP Monitoring Protocol", Work in Progress, Internet-Draft, draft-wang-grow-bmp-policy-preview-00, , <https://datatracker.ietf.org/doc/html/draft-wang-grow-bmp-policy-preview-00>.
[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, , <https://datatracker.ietf.org/doc/html/draft-wang-grow-bmp-bgp-rib-stats-ext-01>.
[I-D.saum-grow-bmp-afi-safi-evpn]
Dikshit, D., Srivastava, M. K., and C. Lin, "EVPN-Specific BMP RIB Statistics Extensions", Work in Progress, Internet-Draft, draft-saum-grow-bmp-afi-safi-evpn-06, , <https://datatracker.ietf.org/doc/html/draft-saum-grow-bmp-afi-safi-evpn-06>.
[I-D.ietf-grow-bmp-stats-informational-tlv]
Srivastava, M. K., Kolenchery, S., and C. Lin, "BMP Statistics Information TLV", Work in Progress, Internet-Draft, draft-ietf-grow-bmp-stats-informational-tlv-02, , <https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-stats-informational-tlv-02>.
[I-D.geng-grow-bmp-rel-enhancement]
Geng, N., Gao, Y., Zhuang, S., and H. Wang, "Log More Routing Events in the BGP Monitoring Protocol (BMP)", Work in Progress, Internet-Draft, draft-geng-grow-bmp-rel-enhancement-03, , <https://datatracker.ietf.org/doc/html/draft-geng-grow-bmp-rel-enhancement-03>.
[I-D.ietf-grow-bmp-rel]
Lucente, P. and C. Cardona, "Logging of routing events in BGP Monitoring Protocol (BMP)", Work in Progress, Internet-Draft, draft-ietf-grow-bmp-rel-06, , <https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-rel-06>.
[I-D.dikshit-grow-bmp-rd-scoped-rib-stats]
Dikshit, D., Srivastava, M. K., and C. Lin, "Route-Distinguisher-Scoped BMP RIB Statistics", Work in Progress, Internet-Draft, draft-dikshit-grow-bmp-rd-scoped-rib-stats-01, , <https://datatracker.ietf.org/doc/html/draft-dikshit-grow-bmp-rd-scoped-rib-stats-01>.
[RFC4684]
Marques, P., Bonica, R., Fang, L., Martini, L., Raszuk, R., Patel, K., and J. Guichard, "Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs)", RFC 4684, DOI 10.17487/RFC4684, , <https://www.rfc-editor.org/info/rfc4684>.

Appendix A. Changes Between Revisions

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

v03 -> v04

v02 -> v03

Authors' Addresses

Saumya Dikshit
Hewlett Packard Enterprise
Mahadevpura
Bangalore 560 048
Karnataka
India
Mukul Srivastava
Hewlett Packard Enterprise
10 Technology Park Dr
Westford, MA 01886
United States of America
Changwang Lin
New H3C Technologies
8 Yongjia North Road
Beijing
Haidian District, 100094
China