Internet-Draft BMP RD-Scoped RIB Stats November 2026
Dikshit, et al. Expires 24 May 2027 [Page]
Workgroup:
Network Working Group
Internet-Draft:
draft-dikshit-grow-bmp-rd-scoped-rib-stats-04
Published:
Intended Status:
Standards Track
Expires:
Authors:
S. Dikshit
Hewlett Packard Enterprise
M. Srivastava
Hewlett Packard Enterprise
C. Lin
New H3C Technologies

Route-Distinguisher-Scoped BMP RIB Statistics

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 24 May 2027.

▲

Table of Contents

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.

Existing BMP statistics stop at the peer boundary ([RFC7854]) or the address-family boundary (RFC 9972). Counting one level finer, per routing instance, needs an instance scope key inside the Stat Data, which is what this document defines:

  Router  -->  Peer        -->  AFI/SAFI     -->  Instance
               (RFC 7854)       (RFC 9972)        (this document)

  up to AFI/SAFI:  per-family aggregate
  Instance level:  per VRF or EVI, keyed by the RD in the Stat Data

When multiple VRFs or EVIs share a single BMP session, where the Per-Peer Header's Peer Distinguisher is zero, the instance key must travel inside the Stat Data, because the header no longer identifies the instance.

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:

Each of these efforts is solving a legitimate, distinct operational 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:

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.

  • Route Distinguisher (8 octets): The RD of the VRF, EVI, or equivalent routing instance the statistic is scoped to, encoded per [RFC4364]. The RD identifies the instance exactly as it appears in the monitored RIB. On a Local-RIB a locally configured instance usually has a single RD, so an RD-scoped count there is also a per-instance count. On an Adj-RIB-In or Adj-RIB-Out, and in particular on a Route Reflector or Route Server, one instance that spans several originators can appear under several RDs, so an RD-scoped count is a per-RD slice rather than a per-instance total. A Family profile (Section 5) states, for its family, how RDs are expected to map to instances in each RIB.

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

Family and AFI/SAFI are two different axes, and both are needed. AFI/SAFI identifies the protocol address family of the routes a statistic counts (for example VPN-IPv4, or EVPN). Family identifies which profile, and therefore which rulebook, a receiver uses to interpret the Subtype octet and the Gauge. A single Family can span more than one AFI/SAFI: an "L3VPN" Family, for instance, applies to both VPN-IPv4 (AFI 1, SAFI 128) and VPN-IPv6 (AFI 2, SAFI 128), so one Family registration covers both and the AFI/SAFI field records which of the two a given Stat Data instance is about. Keying a profile on AFI/SAFI alone would require a separate registration per SAFI and would overload a protocol identifier with statistics semantics; keying on Family keeps the two concerns apart. For a family whose address family is a single fixed pair, such as EVPN (AFI 25, SAFI 70), Family and AFI/SAFI coincide, and the AFI/SAFI field is carried for uniformity.

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 |
+-------+-------------------------------------------------+---------+
Figure 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
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.

3.4. Worked Examples

These non-normative examples show the container carried as the Stat Data (value) of a Stat Type TLV (Section 4.8 of [RFC7854]) inside a Statistics Report message. The container is 21 octets, so Stat Length is 21 in each case. The Stat Type code point and the Per-Peer Header come from the profiling document and from [RFC7854] and [RFC9069]; they are shown only for context.

Example 1: EVPN, per-EVI IP-Prefix route count, Local-RIB

Statistics Report
  Per-Peer Header: Loc-RIB Instance Peer (RFC 9069)
  Stat TLV
    Stat Type = <EVPN per-EVI Local-RIB code point>
    Stat Len  = 21
    Stat Data (RD-Scoped container):
      Family  = 2    (EVPN)
      Subtype = 5    (EVPN route type 5, IP-Prefix)
      AFI     = 25   SAFI = 70
      RD      = 65001:100
      Gauge   = 42
  => 42 EVPN type-5 routes in EVI 65001:100

Example 2: L3VPN, one VRF, IPv4 and IPv6 route counts

Statistics Report
  Per-Peer Header: Loc-RIB Instance Peer, Peer Distinguisher 65001:100
  Stat TLV (VPN-IPv4)
    Stat Type = <L3VPN per-RD code point>   Stat Len = 21
    Stat Data: Family=1 (L3VPN) Subtype=0 AFI=1 SAFI=128
               RD=65001:100 Gauge=500
  Stat TLV (VPN-IPv6)
    Stat Type = <L3VPN per-RD code point>   Stat Len = 21
    Stat Data: Family=1 (L3VPN) Subtype=0 AFI=2 SAFI=128
               RD=65001:100 Gauge=120
  => 500 VPN-IPv4 and 120 VPN-IPv6 routes in VRF 65001:100
     one Family (L3VPN); the AFI field selects v4 vs v6

On a shared Route Reflector session the Per-Peer Header would be a Global Instance Peer with a zero Peer Distinguisher; the RD inside the container is then the only field that names the instance.

3.5. BMP Version Compatibility and Receiver Rules

The container is agnostic to the underlying BMP protocol version. It is carried as the Stat Data of a Stat Type entry in a Statistics Report, both in the base BMP protocol [RFC7854] and in the TLV-based BMP extensions being developed in the working group (informally, BMPv4):

BMP (RFC 7854):
  [Common Hdr] [Per-Peer Hdr] [Stats Count]
    [Stat Type | Stat Length | Stat Data = container]

BMP TLV extensions (BMPv4):
  [Common Hdr] [Per-Peer Hdr] [Stats Count]
    [Stats TLV: Type | Length | Stat Data = container] [optional TLVs]

A collector applies two levels of backward compatibility:

  1. Unknown Stat Type: skip 4 + Stat Length octets and parse the next entry, as already specified by [RFC9972].

  2. Unknown Family: if the Stat Type is recognized but the 1-octet Family value is not, ignore that Stat Data payload and continue parsing subsequent entries, consistent with the receive rule in Section 3.1.

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 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:

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.

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. Operational Considerations

The statistics carried in this container are produced per Route Distinguisher, so the number of Stat Data instances in a report grows with the number of monitored RDs. A producer SHOULD be able to rate-limit the reporting interval, and SHOULD allow an operator to select a subset of RDs, families, or Stat Types, so that a high-cardinality deployment does not emit an unbounded volume of statistics. Reporting only counters that have changed since the previous report, for example by layering a triggered or differential mechanism on top of a Stat Type that uses this container, further bounds the volume.

When these statistics are exported from an Adj-RIB-In or Adj-RIB-Out on an intermediate node such as a Route Reflector or Route Server, the reported counts reflect only the routes present in that RIB after any inbound or outbound policy, Route Target Constrain [RFC4684], and best-path or Add-Path selection have been applied. Such a count is therefore a view of the constrained or selected subset seen by that node, not of the entire fabric. A collector SHOULD interpret an RD-scoped count in the context of the RIB and the node it was produced on, and SHOULD NOT assume that counts from two different nodes for the same RD are directly comparable unless those nodes observe the same set of routes.

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

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

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>.
[RFC4364]
Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, , <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, , <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>.
[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, , <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, , <https://www.rfc-editor.org/info/rfc8174>.

11.2. Informative References

[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.ietf-grow-bmp-yang]
Cardona, C., Lucente, P., Graf, T., Claise, B., Patki, D., and N. Prasad, "A YANG Data Model for BMP", Work in Progress, Internet-Draft, draft-ietf-grow-bmp-yang-10, , <https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-yang-10>.
[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.smc-grow-bmp-route-change-stats]
Dikshit, D., Srivastava, M. K., and C. Lin, "BMP Route Change Statistics Based on Routing Policy", Work in Progress, Internet-Draft, draft-smc-grow-bmp-route-change-stats-02, , <https://datatracker.ietf.org/doc/html/draft-smc-grow-bmp-route-change-stats-02>.
[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.zhuang-grow-bmp-enhancement-for-vrf-loc-rib]
Zhuang, S., Geng, N., Dikshit, D., and H. Wang, "Enhancement for Monitoring VRF's Loc-RIB", Work in Progress, Internet-Draft, draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib-02, , <https://datatracker.ietf.org/doc/html/draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib-02>.
[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>.
[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>.
[RFC7432]
Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A., Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, , <https://www.rfc-editor.org/info/rfc7432>.
[RFC9069]
Evens, T., Bayraktar, S., Bhardwaj, M., and P. Lucente, "Support for Local RIB in the BGP Monitoring Protocol (BMP)", RFC 9069, DOI 10.17487/RFC9069, , <https://www.rfc-editor.org/info/rfc9069>.

Appendix A. Changes Between Revisions

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

v03 -> v04

v02 -> v03

v01 -> v02

v00 -> v01

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