| Internet-Draft | bmp-rel-enhancement | October 2025 |
| Geng, et al. | Expires 20 April 2026 | [Page] |
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].¶
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 (c) 2025 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.¶
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].¶
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.¶
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:¶
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.¶
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.¶
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.¶
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.¶