| Internet-Draft | BMP New Statistics | April 2024 |
| Srivastava | Expires 1 November 2024 | [Page] |
RFC 7854 defined different BMP statistics messages types to observe interesting events that occur on the router. This document updates RFC 7854 by adding new statistics type.¶
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 1 November 2024.¶
Copyright (c) 2024 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.¶
[RFC7854] defines a number of different BMP statistics types to observe interesting events that occur on the router. Stats are either counters or gauges. A 32-bit Counter is a non-negative integer that monotonically increases until it reaches a maximum value, when it wraps around and starts increasing again from 0. A 64-bit Gauge is a non-negative integer that may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum one.¶
This document defines new gauges for BMP statistics message. The format of the BMP statistics message remains same as defined in [RFC7854]¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
This section defines different statistics type for RIB-IN and RIB-OUT monitoring type.¶
Type = TBD1: (64-bit Gauge) Current number of routes in Adj-RIBs-In-Pre-Policy. The value can increase or decrease based upon ongoing configuration change. Note that this counter updates stats type 7 defined in [RFC7854] and makes it a explicit for Adj-RIBs-In-Pre-Policy.¶
Type = TBD2: (64-bit Gauge) Current number of routes in per-AFI/SAFI Adj-RIBs-In-Pre-Policy. The value can increase or decrease based upon ongoing configuration change. Note that this counter is similar from stats type 9 defined in [RFC7854] and makes it a explicit for Adj-RIBs-In-Pre-Policy. The value is structured as: 2-byte Address Family Identifier (AFI), 1-byte Subsequent Address Family Identifier (SAFI), followed by a 64-bit Gauge.¶
Type = TBD3: (64-bit Gauge) Current number of routes in Adj-RIBs-In-Post-Policy. The value can increase or decrease based upon ongoing configuration change.¶
Type = TBD4: (64-bit Gauge) Current number of routes in per-AFI/SAFI Adj-RIBs-In-Post-Policy. The value can increase or decrease based upon ongoing configuration change. The value is structured as: 2-byte Address Family Identifier (AFI), 1-byte Subsequent Address Family Identifier (SAFI), followed by a 64-bit Gauge.¶
Type = TBD5: (64-bit Gauge) Current number of routes in per-AFI/SAFI rejected by inbound policy. The value can increase or decrease based upon ongoing configuration change. Note that this counter is different from stats type 0 defined in [RFC7854]. The stats type 0 in [RFC7854] is the a 32 counter which is monotonically increasing number and doesn't represents the current number of routes rejected by inbound policy due to ongoing configuration changes. The value is structured as: 2-byte Address Family Identifier (AFI), 1-byte Subsequent Address Family Identifier (SAFI), followed by a 64-bit Gauge.¶
Type = TBD6: (64-bit Gauge) Number of routes in per-AFI/SAFI accepted by inbound policy. The value can increase or decrease based upon ongoing configuration change or network events. The value is structured as: 2-byte Address Family Identifier (AFI), 1-byte Subsequent Address Family Identifier (SAFI), followed by a 64-bit Gauge. Some implementations, or configurations in implementations, may discard routes that do not match policy and thus the accepted count and the rib-in counts will be identical in such cases.¶
Type = TBD7: (64-bit Gauge) Number of routes in per-AFI/SAFI selected as primary route. The value can increase or decrease based upon ongoing configuration change or network events. The value is structured as: 2-byte Address Family Identifier (AFI), 1-byte Subsequent Address Family Identifier (SAFI), followed by a 64-bit Gauge. A primary path is a recursive or non-recursive path whose nexthop resolution ends with an adjacency draft-ietf-rtgwg-bgp-pic [I-D.ietf-rtgwg-bgp-pic]. A prefix can have more than one primary path if multipath is configured draft-lapukhov-bgp-ecmp-considerations [I-D.lapukhov-bgp-ecmp-considerations]. A best-path is also considered as a primary path.¶
Type = TBD8: (64-bit Gauge) Number of routes in per-AFI/SAFI selected as backup route. The value can increase or decrease based upon ongoing configuration change or network events. The value is structured as: 2-byte Address Family Identifier (AFI), 1-byte Subsequent Address Family Identifier (SAFI), followed by a 64-bit Gauge. A backup path is also installed in the RIB, but it is not used until some or all primary paths become unreachable. Backup paths are used for fast convergence in the event of failures.¶
Type = TBD9: (64-bit Gauge) Number of routes in per-AFI/SAFI suppressed by configured route damping policy. The value can increase or decrease based upon configuration change or network events. The value is structured as: 2-byte Address Family Identifier (AFI), 1-byte Subsequent Address Family Identifier (SAFI), followed by a 64-bit Gauge. Suppressed refers to a path which has been declared suppressed by the BGP Route Flap Damping mechanism as described in Section 2.2 of [RFC2439].¶
Type = TBD10: (64-bit Gauge) Number of routes in per-AFI/SAFI marked as stale by any configuration. The value is structured as: 2-byte Address Family Identifier (AFI), 1-byte Subsequent Address Family Identifier (SAFI), followed by a 64-bit Gauge. Stale refers to a path which has been declared stale by the BGP Graceful Restart mechanism as described in Section 4.1 of [RFC4724].¶
Type = TBD11: (64-bit Gauge) Number of routes in per-AFI/SAFI marked as stale by LLGR. The value is structured as: 2-byte Address Family Identifier (AFI), 1-byte Subsequent Address Family Identifier (SAFI), followed by a 64-bit Gauge. Stale refers to a path which has been declared stale by the BGP Long-Lived Graceful Restart mechanism as described in Section 4.3 of [RFC9494]. This is the route that are marked stale as part of LLGR process.¶
Type = TBD12: (64-bit Gauge) Current number of routes in per-AFI/SAFI rejected by outbound policy. These routes are active routes which should otherwise would have been advertised in absense of outbound policy which rejected them. The value can increase or decrease based upon ongoing configuration change. The value is structured as: 2-byte Address Family Identifier (AFI), 1-byte Subsequent Address Family Identifier (SAFI), followed by a 64-bit Gauge. This counter only considers routes distributed from loc-rib into the adj-ribs-out and does not include cases like BGP add-paths [RFC7911].¶
This document requests that IANA assign the following new parameters to the BMP parameters name space.¶
The considerations in Section 11 of [RFC7854] apply to this document. It is also believed that this document does not add any additional security considerations.¶
The author would like to thank Jeff Haas for his valuable input.¶