Log More Routing Events in the BGP Monitoring Protocol (BMP)
draft-geng-grow-bmp-rel-enhancement-00
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
| Document | Type | Active Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Nan Geng , Shunwan Zhuang , Haibo Wang | ||
| Last updated | 2025-10-17 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-geng-grow-bmp-rel-enhancement-00
GROW N. Geng
Internet-Draft S. Zhuang
Intended status: Standards Track H. Wang
Expires: 20 April 2026 Huawei
17 October 2025
Log More Routing Events in the BGP Monitoring Protocol (BMP)
draft-geng-grow-bmp-rel-enhancement-00
Abstract
The Route Event Logging (REL) message is defined in
[I-D.ietf-grow-bmp-rel] and is used to report event-driven data to
the BMP Server from the monitored routers.
This document defines more event-driven data for BGP FlowSpec RFC8955
[RFC8956] and BGP SR Policies [I-D.ietf-idr-sr-policy-safi].
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 20 April 2026.
Copyright Notice
Copyright (c) 2025 IETF Trust and the persons identified as the
document authors. All rights reserved.
Geng, et al. Expires 20 April 2026 [Page 1]
Internet-Draft bmp-rel-enhancement October 2025
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
2. Log some routing events for BGP Flowspec . . . . . . . . . . 2
3. Log some routing events for BGP SR Policies . . . . . . . . . 3
4. Operations . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 4
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
7. Normative References . . . . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
The generation of BGP Adj-RIB-In, Loc-RIB and Adj-RIB-Out comes from
BGP route exchange and route policy processing. BGP Monitoring
Protocol (BMP) provides the monitoring of BGP Adj-RIB-In [RFC7854],
BGP Loc-RIB [RFC9069], and BGP Adj-RIB-Out [RFC8671]. The Route
Event Logging (REL) message is defined in [I-D.ietf-grow-bmp-rel] and
is used to report event-driven data to the BMP Server from the
monitored routers.
This document defines more event-driven data for BGP FlowSpec RFC8955
[RFC8956] and BGP SR Policies [I-D.ietf-idr-sr-policy-safi].
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. Log some routing events for BGP Flowspec
Log Action TLV is defined in [I-D.ietf-grow-bmp-rel], the first byte
defines the nature of the logging, depending on the code point
additional data may follow. the following code points are defined for
BGP Flowspec in this document:
Geng, et al. Expires 20 April 2026 [Page 2]
Internet-Draft bmp-rel-enhancement October 2025
* TBD1 = Redirect-to-VRF-Fail. The BGP flowspec redirect to VRF
action is defined in [RFC8955]. It is used to redirect the
specified traffic into a Virtual Routing and Forwarding (VRF)
instance that matched the flow specification's Network Layer
Reachability Information (NLRI). The VRF instance may fail due to
various reasons. As a result, the BGP FlowSpec will fails to
redirect the matched traffic to the specific VRF instance. Data
contains a UTF-8 string whose value can be organized freely by an
implementation and is meant to give additional information about
why the log was made.
* TBD2 = Redirect-to-Nexthop-Fail. The BGP flowspec redirect to IP
action is defined in [I-D.ietf-idr-flowspec-redirect-ip]. It is
used to redirect the specified traffic to a target IPv4 address or
a target IPv6 address that matched the flow specification's
Network Layer Reachability Information (NLRI). The destination
IPv4 address or destination IPv6 address may fail for a variety of
reasons. Data contains a UTF-8 string whose value can be
organized freely by an implementation and is meant to give
additional information about why the log was made.
* TBD3 = Redirect-to-SR-Policy-Fail. Data contains a UTF-8 string
whose value can be organized freely by an implementation and is
meant to give additional information about why the log was made.
* TBD4 = Flowspec Validation Fail. The BGP Flowspec Validation
Procedure is defined in [RFC8955]. Data contains a UTF-8 string
whose value can be organized freely by an implementation and is
meant to give additional information about why the log was made.
3. Log some routing events for BGP SR Policies
Log Action TLV is defined in [I-D.ietf-grow-bmp-rel], the first byte
defines the nature of the logging, depending on the code point
additional data may follow. the following code points are defined for
BGP SR Policies in this document:
* TBD5 = Invalid Candidate Path. Data contains a UTF-8 string whose
value can be organized freely by an implementation and is meant to
give dditional information about why the log was made.
Geng, et al. Expires 20 April 2026 [Page 3]
Internet-Draft bmp-rel-enhancement October 2025
4. Operations
Network devices from other devices (can be a network controller,
Flowspec server, router, switch, etc.) When receiving the Flowspec
route that carries the Flowspec Redirect-to-vrf Action, it is
detected that the target VRF instance is in the faulty state, and the
network device reports the fault information to the BMP Server via
BMP REL message.
5. Security Considerations
The same considerations as in Section 11 of [RFC7854] apply to this
document. Implementations of this protocol SHOULD require that
sessions only be established with authorized and trusted monitoring
devices. It is also believed that this document does not introduce
any additional security considerations.
6. IANA Considerations
TBD
7. Normative References
[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>.
[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>.
[RFC8955] Loibl, C., Hares, S., Raszuk, R., McPherson, D., and M.
Bacher, "Dissemination of Flow Specification Rules",
RFC 8955, DOI 10.17487/RFC8955, December 2020,
<https://www.rfc-editor.org/info/rfc8955>.
[RFC8956] Loibl, C., Ed., Raszuk, R., Ed., and S. Hares, Ed.,
"Dissemination of Flow Specification Rules for IPv6",
RFC 8956, DOI 10.17487/RFC8956, December 2020,
<https://www.rfc-editor.org/info/rfc8956>.
[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>.
Geng, et al. Expires 20 April 2026 [Page 4]
Internet-Draft bmp-rel-enhancement October 2025
[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-04, 3 September
2025, <https://datatracker.ietf.org/doc/html/draft-ietf-
grow-bmp-rel-04>.
[I-D.ietf-idr-sr-policy-safi]
Previdi, S., Filsfils, C., Talaulikar, K., Mattes, P., and
D. Jain, "Advertising Segment Routing Policies in BGP",
Work in Progress, Internet-Draft, draft-ietf-idr-sr-
policy-safi-13, 6 February 2025,
<https://datatracker.ietf.org/doc/html/draft-ietf-idr-sr-
policy-safi-13>.
[I-D.ietf-idr-flowspec-redirect-ip]
Haas, J., Henderickx, W., and A. Simpson, "BGP Flow-Spec
Redirect-to-IP Action", Work in Progress, Internet-Draft,
draft-ietf-idr-flowspec-redirect-ip-04, 2 September 2025,
<https://datatracker.ietf.org/doc/html/draft-ietf-idr-
flowspec-redirect-ip-04>.
[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>.
[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>.
Authors' Addresses
Nan Geng
Huawei
Beijing
China
Email: gengnan@huawei.com
Shunwan Zhuang
Huawei
Beijing
China
Email: zhuangshunwan@huawei.com
Geng, et al. Expires 20 April 2026 [Page 5]
Internet-Draft bmp-rel-enhancement October 2025
Haibo Wang
Huawei
Beijing
China
Email: rainsword.wang@huawei.com
Geng, et al. Expires 20 April 2026 [Page 6]