Internet DRAFT - draft-ietf-grow-bmp-bgp-rib-stats
draft-ietf-grow-bmp-bgp-rib-stats
GROW M. Srivastava
Internet-Draft Juniper Networks
Updates: 7854 (if approved) 22 January 2024
Intended status: Standards Track
Expires: 25 July 2024
Definition For New BMP Statistics Type
draft-ietf-grow-bmp-bgp-rib-stats-01
Abstract
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.
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 July 2024.
Copyright Notice
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.
Srivastava Expires 25 July 2024 [Page 1]
Internet-Draft BMP New Statistics January 2024
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
2. Statistics Definition . . . . . . . . . . . . . . . . . . . . 2
2.1. RIB-IN Statistics Definition . . . . . . . . . . . . . . 2
2.2. RIB-OUT Statistics Definition . . . . . . . . . . . . . . 4
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
6. Normative References . . . . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
[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]
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. Statistics Definition
This section defines different statistics type for RIB-IN and RIB-OUT
monitoring type.
2.1. RIB-IN Statistics Definition
* Type = TBD1: (64-bit Gauge) Current number of routes in Adj-RIBs-
In-Pre-Policy. The value can increase or decrease base on 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.
Srivastava Expires 25 July 2024 [Page 2]
Internet-Draft BMP New Statistics January 2024
* Type = TBD2: (64-bit Gauge) Current number of routes in per-AFI/
SAFI Adj-RIBs-In-Pre-Policy. The value can increase or decrease
base on 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 base on
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
base on 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 base on 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
base on 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 active route. The value can increase or decrease base
on 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.
Srivastava Expires 25 July 2024 [Page 3]
Internet-Draft BMP New Statistics January 2024
* Type = TBD8: (64-bit Gauge) Number of routes in per-AFI/SAFI
damped by configured route damping policy. The value can increase
or decrease base on 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.
* Type = TBD9: (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. This is the
route that are marked stale as part of GR [RFC4784] process.
* Type = TBD10: (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. This is the route
that are marked stale as part of LLGR process.
2.2. RIB-OUT Statistics Definition
* Type = TBD11: (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 base on 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].
3. IANA Considerations
This document requests that IANA assign the following new parameters
to the BMP parameters name space (https://www.iana.org/assignments/
bmp-parameters/bmp-parameters.xhtml).
4. Security Considerations
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.
5. Acknowledgements
The author would like to thank Jeff Haas for his valuable input.
Srivastava Expires 25 July 2024 [Page 4]
Internet-Draft BMP New Statistics January 2024
6. 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>.
[RFC4784] Carroll, C. and F. Quick, "Verizon Wireless Dynamic Mobile
IP Key Update for cdma2000(R) Networks", RFC 4784,
DOI 10.17487/RFC4784, June 2007,
<https://www.rfc-editor.org/info/rfc4784>.
[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>.
[RFC7911] Walton, D., Retana, A., Chen, E., and J. Scudder,
"Advertisement of Multiple Paths in BGP", RFC 7911,
DOI 10.17487/RFC7911, July 2016,
<https://www.rfc-editor.org/info/rfc7911>.
[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>.
[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, November
2019, <https://www.rfc-editor.org/info/rfc8671>.
[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, February 2022,
<https://www.rfc-editor.org/info/rfc9069>.
Author's Address
Mukul Srivastava
Juniper Networks
10 Technology Park Dr
Westford, MA 01886
United States of America
Email: msri@juniper.net
Srivastava Expires 25 July 2024 [Page 5]
