Internet DRAFT - draft-liu-grow-bmp-stats-reports
draft-liu-grow-bmp-stats-reports
Global Routing Operations Y. Liu
Internet Draft China Mobile
Intended status: Standards Track C. Lin
Expires: August 26, 2024 New H3C Technologies
J. Li
China Mobile
February 26, 2024
Addition of New BMP Stat Types
draft-liu-grow-bmp-stats-reports-00
Abstract
BMP statistics messages are used by the monitoring station to
observe interesting events that occur on the router. Several BMP
statistics types are defined in RFC 7854, this document lists some
new statistics types to update RFC 7854 for growing BGP features.
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 August 26, 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
(http://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 Simplified BSD License text as described in
Liu, et al. Expire August 26, 2024 [Page 1]
Internet-Draft New BMP Route Monitoring Message February 2024
Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License.
Table of Contents
1. Introduction...................................................3
2. Requirements Language..........................................3
3. Statistics Types...............................................3
3.1. RIB-IN Statistics Types...................................3
3.1.1. RIB-IN Statistics Types for Route Threshold..........3
3.1.2. RIB-IN Statistics Types for AS-Path Length Threshold.4
3.1.3. RIB-IN Statistics Types for Route Origin Validation..4
3.2. RIB-OUT Statistics Types..................................5
3.2.1. RIB-OUT Statistics Types for AS-Path Length Threshold5
3.2.2. RIB-OUT Statistics Types for Route Origin Validation.5
4. IANA Considerations............................................6
5. Security Considerations........................................6
6. Normative References...........................................6
Authors' Addresses................................................7
Liu, et al. Expires August 26, 2024 [Page 2]
Internet-Draft New BMP Route Monitoring Message February 2024
1. Introduction
[RFC7854] defines BMP statistics messages to observe interesting
events that occur on the router. Several different BMP statistics
types are defined in [RFC7854] to indicate the activity going on in
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.
As the BGP protocol continues to expand, more and more functional
features are implemented through the BGP protocol, which adds more
event information to monitor these functional features. This
document defines new gauges for BMP statistics message to enrich
events of interest to routers. The format of the BMP statistics
message remains same as defined in [RFC7854].
2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
3. Statistics Types
This section lists multiple new statistics types for RIB-IN and RIB-
OUT monitoring stat type, which enhances the monitoring station's
attention to events on the router.
3.1. RIB-IN Statistics Types
3.1.1. RIB-IN Statistics Types for Route Threshold
* Stat Type = TBD1: (64-bit Gauge) Current Number of routes rejected
by reaching the received route threshold. This value can increase or
decrease base on ongoing configuration changes of the peer's
received route threshold.
* Stat Type = TBD2: (64-bit Gauge) Current Number of routes in per-
AFI/SAFI rejected by reaching the received route threshold. This
value can increase or decrease base on ongoing configuration changes
of the peer's received route threshold. The value is structured as:
2-byte Address Family Identifier (AFI), 1-byte Subsequent Address
Family Identifier (SAFI), followed by a 64-bit Gauge.
Liu, et al. Expires August 26, 2024 [Page 3]
Internet-Draft New BMP Route Monitoring Message February 2024
* Stat Type = TBD3: (64-bit Gauge) Current Number of routes rejected
by reaching the license-customized route threshold. This value is
affected by whether a customized license exists for the relevant
address family, and when the customized license is installed. This
value can increase or decrease based on current customized
information of license.
* Stat Type = TBD4: (64-bit Gauge) Current Number of routes in per-
AFI/SAFI rejected by reaching the license-customized route
threshold. This value is affected by whether a customized license
exists for the relevant address family, and when the customized
license is installed. This value can increase or decrease based on
current customized information of license. The value is structured
as: 2-byte Address Family Identifier (AFI), 1-byte Subsequent
Address Family Identifier (SAFI), followed by a 64-bit Gauge.
3.1.2. RIB-IN Statistics Types for AS-Path Length Threshold
* Stat Type = TBD5: (64-bit Gauge) Current Number of routes rejected
by exceeding the length threshold of as-path. This value can
increase or decrease base on ongoing configuration changes of the
length threshold of as-path [RFC4271].
* Stat Type = TBD6: (64-bit Gauge) Current Number of routes in per-
AFI/SAFI rejected by exceeding the length threshold of as-path. This
value can increase or decrease base on ongoing configuration changes
of the length threshold of as-path [RFC4271]. The value is
structured as: 2-byte Address Family Identifier (AFI), 1-byte
Subsequent Address Family Identifier (SAFI), followed by a 64-bit
Gauge.
3.1.3. RIB-IN Statistics Types for Route Origin Validation
* Stat Type = TBD7: (64-bit Gauge) Current Number of routes in per-
AFI/SAFI Adj-RIBs-In-Post-Policy invalidated by verifying route
origin Autonomous System (AS) number through the Route Origin
Authorization (ROA) of Resource Public Key Infrastructure (RPKI)
[RFC6811]. This value can increase or decrease base on ongoing ROA
changes of RPKI. The value is structured as: 2-byte Address Family
Identifier (AFI), 1-byte Subsequent Address Family Identifier
(SAFI), followed by a 64-bit Gauge.
* Stat Type = TBD8: (64-bit Gauge) Current Number of routes in per-
AFI/SAFI Adj-RIBs-In-Post-Policy validated by verifying route origin
Autonomous System (AS) number through the Route Origin Authorization
(ROA) of Resource Public Key Infrastructure (RPKI) [RFC6811]. This
value can increase or decrease base on ongoing ROA changes of RPKI.
The value is structured as: 2-byte Address Family Identifier (AFI),
Liu, et al. Expires August 26, 2024 [Page 4]
Internet-Draft New BMP Route Monitoring Message February 2024
1-byte Subsequent Address Family Identifier (SAFI), followed by a
64-bit Gauge.
* Stat Type = TBD9: (64-bit Gauge) Current Number of routes in per-
AFI/SAFI Adj-RIBs-In-Post-Policy not found by verifying route origin
Autonomous System (AS) number through the Route Origin Authorization
(ROA) of Resource Public Key Infrastructure (RPKI) [RFC6811]. This
value can increase or decrease base on ongoing ROA changes of RPKI.
The value is structured as: 2-byte Address Family Identifier (AFI),
1-byte Subsequent Address Family Identifier (SAFI), followed by a
64-bit Gauge.
3.2. RIB-OUT Statistics Types
3.2.1. RIB-OUT Statistics Types for AS-Path Length Threshold
* Stat Type = TBD10: (64-bit Gauge) Current Number of routes refused
to be sent by exceeding the length threshold of as-path. This value
can increase or decrease base on ongoing configuration changes of
the length threshold of as-path [RFC4271].
* Stat Type = TBD11: (64-bit Gauge) Current Number of routes in per-
AFI/SAFI refused to be sent by exceeding the length threshold of as-
path. This value can increase or decrease base on ongoing
configuration changes of the length threshold of as-path [RFC4271].
The value is structured as: 2-byte Address Family Identifier (AFI),
1-byte Subsequent Address Family Identifier (SAFI), followed by a
64-bit Gauge.
3.2.2. RIB-OUT Statistics Types for Route Origin Validation
* Stat Type = TBD12: (64-bit Gauge) Current Number of routes in per-
AFI/SAFI Adj-RIBs-Out-Post-Policy invalidated by verifying route
origin Autonomous System (AS) number through the Route Origin
Authorization (ROA) of Resource Public Key Infrastructure (RPKI)
[RFC6811]. This value can increase or decrease base on ongoing ROA
changes of RPKI. The value is structured as: 2-byte Address Family
Identifier (AFI), 1-byte Subsequent Address Family Identifier
(SAFI), followed by a 64-bit Gauge.
* Stat Type = TBD13: (64-bit Gauge) Current Number of routes in per-
AFI/SAFI Adj-RIBs-Out-Post-Policy validated by verifying route
origin Autonomous System (AS) number through the Route Origin
Authorization (ROA) of Resource Public Key Infrastructure (RPKI)
[RFC6811]. This value can increase or decrease base on ongoing ROA
changes of RPKI. The value is structured as: 2-byte Address Family
Identifier (AFI), 1-byte Subsequent Address Family Identifier
(SAFI), followed by a 64-bit Gauge.
Liu, et al. Expires August 26, 2024 [Page 5]
Internet-Draft New BMP Route Monitoring Message February 2024
* Stat Type = TBD14: (64-bit Gauge) Current Number of routes in per-
AFI/SAFI Adj-RIBs-Out-Post-Policy not found by verifying route
origin Autonomous System (AS) number through the Route Origin
Authorization (ROA) of Resource Public Key Infrastructure (RPKI)
[RFC6811]. This value can increase or decrease base on ongoing ROA
changes of RPKI. The value is structured as: 2-byte Address Family
Identifier (AFI), 1-byte Subsequent Address Family Identifier
(SAFI), followed by a 64-bit Gauge.
4. 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).
5. 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.
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/rfc/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, January 2006, <https://www.rfc-
editor.org/info/rfc4271>.
[RFC6811] Mohapatra, P., Scudder, J., Ward, D., Bush, R., and
R.Austein, "BGP Prefix Origin Validation", RFC 6811, DOI
10.17487/RFC6811, January 2013, <https://www.rfc-
editor.org/info/rfc6811>.
[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>.
Liu, et al. Expires August 26, 2024 [Page 6]
Internet-Draft New BMP Route Monitoring Message February 2024
Authors' Addresses
Yisong Liu
China Mobile
Beijing
China
Email: liuyisong@chinamobile.com
Changwang Lin
New H3C Technologies
Beijing
China
Email: linchangwang.04414@h3c.com
Jinming Li
China Mobile
Beijing
China
Email: lijinming@chinamobile.com
Liu, et al. Expires August 26, 2024 [Page 7]
