]> Log More Routing Events in the BGP Monitoring Protocol (BMP) Huawei
Beijing China gengnan@huawei.com
Huawei
Beijing China zhuangshunwan@huawei.com
Huawei
Beijing China rainsword.wang@huawei.com
OPS GROW Internet-Draft The Route Event Logging (REL) message is defined in 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 and BGP SR Policies .
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 , BGP Loc-RIB , and BGP Adj-RIB-Out . The Route Event Logging (REL) message is defined in 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 and BGP SR Policies .
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 when, and only when, they appear in all capitals, as shown here.
Log some routing events for BGP Flowspec Log Action TLV is defined in , 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 . 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 . 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 . 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 some routing events for BGP SR Policies Log Action TLV is defined in , 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.
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.
Security Considerations The same considerations as in Section 11 of 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.
IANA Considerations TBD
Normative References BGP Monitoring Protocol (BMP) This document defines the BGP Monitoring Protocol (BMP), which can be used to monitor BGP sessions. BMP is intended to provide a convenient interface for obtaining route views. Prior to the introduction of BMP, screen scraping was the most commonly used approach to obtaining such views. The design goals are to keep BMP simple, useful, easily implemented, and minimally service affecting. BMP is not suitable for use as a routing protocol. Support for Adj-RIB-Out in the BGP Monitoring Protocol (BMP) The BGP Monitoring Protocol (BMP) only defines access to the Adj-RIB-In Routing Information Bases (RIBs). This document updates BMP (RFC 7854) by adding access to the Adj-RIB-Out RIBs. It also adds a new flag to the peer header to distinguish between Adj-RIB-In and Adj-RIB-Out. Dissemination of Flow Specification Rules This document defines a Border Gateway Protocol Network Layer Reachability Information (BGP NLRI) encoding format that can be used to distribute (intra-domain and inter-domain) traffic Flow Specifications for IPv4 unicast and IPv4 BGP/MPLS VPN services. This allows the routing system to propagate information regarding more specific components of the traffic aggregate defined by an IP destination prefix. It also specifies BGP Extended Community encoding formats, which can be used to propagate Traffic Filtering Actions along with the Flow Specification NLRI. Those Traffic Filtering Actions encode actions a routing system can take if the packet matches the Flow Specification. This document obsoletes both RFC 5575 and RFC 7674. Dissemination of Flow Specification Rules for IPv6 "Dissemination of Flow Specification Rules" (RFC 8955) provides a Border Gateway Protocol (BGP) extension for the propagation of traffic flow information for the purpose of rate limiting or filtering IPv4 protocol data packets. This document extends RFC 8955 with IPv6 functionality. It also updates RFC 8955 by changing the IANA Flow Spec Component Types registry. Support for Local RIB in the BGP Monitoring Protocol (BMP) The BGP Monitoring Protocol (BMP) defines access to local Routing Information Bases (RIBs). This document updates BMP (RFC 7854) by adding access to the Local Routing Information Base (Loc-RIB), as defined in RFC 4271. The Loc-RIB contains the routes that have been selected by the local BGP speaker's Decision Process. Logging of routing events in BGP Monitoring Protocol (BMP) NTT NTT The BGP Monitoring Protocol (BMP) does provision for BGP session event logging (Peer Up, Peer Down), state synchronization (Route Monitoring), debugging (Route Mirroring) and Statistics messages, among the others. This document defines a new Route Event Logging (REL) message type for BMP with the aim of covering use-cases with affinity to alerting, reporting and on-change analysis. Advertising Segment Routing Policies in BGP Huawei Technologies Cisco Systems Cisco Systems Microsoft Google A Segment Routing (SR) Policy is an ordered list of segments (also referred to as instructions) that define a source-routed policy. An SR Policy consists of one or more candidate paths, each comprising one or more segment lists. A headend can be provisioned with these candidate paths using various mechanisms, such as CLI, NETCONF, PCEP, or BGP. This document specifies how BGP can be used to distribute SR Policy candidate paths. It introduces a BGP SAFI for advertising a candidate path of an SR Policy and defines sub-TLVs for the Tunnel Encapsulation Attribute to signal information related to these candidate paths. Furthermore, this document updates RFC9012 by extending the Color Extended Community to support additional steering modes over SR Policy. BGP Flow-Spec Redirect-to-IP Action HPE Nokia Nokia Flow-spec is an extension to BGP that allows for the dissemination of traffic flow specification rules. This has many possible applications, but the primary one for many network operators is the distribution of traffic filtering actions for distributed denial of service (DDoS) mitigation. The flow-spec standard [RFC8955] defines a redirect-to-VRF action for policy-based forwarding. This mechanism can be difficult to use, particularly in networks without L3 VPN infrastructure. This draft defines a new redirect-to-IP flow-spec action that provides a simpler method of policy-based forwarding. The details of the action, including the IPv4 or IPv6 target address, are encoded in newly defined BGP extended communities. Key words for use in RFCs to Indicate Requirement Levels In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.