Making BMP fruible offline

Correctly parsing BGP Update PDUs included in BMP messages (ie. Route Monitoring) does require a stateful approach by keeping track of capabilities exchanged at BGP Open time as reported by BMP Peer Up messages. The role of Peer Up messages is solely BGP session event logging and the long-lived nature of sessions does pose the problem that a BGP Open message may have been received long time before parsing a BGP Update making challenging a stateful approach based on receipt of Peer Up. TLV support for BMP Route Monitoring and Peer Down Messages defines a Stateless Parsing TLV aimed at including relevant capabilities that have an impact in BGP Update message parsing as part of optional informational TLV in Route Monitoring messages. While the method is valid, in fact it does allow with minor effort to encapsulate BMP in MRT format for offline consumption as documented by Storing BMP messages in MRT Format, it comes with some drawbacks like extra verbosity and increased correlation effort at a BMP exporter. This document defines a new optional BMP message type named Peer Summary that carries a list of the established BGP sessions, along with their capabilities. The general idea is that a Peer Summary message is composed by a sequence of one or multiple Peer TLVs with the goal of allowing a consumer to re-build the list of established BGP sessions like if the sequence of Peer Up messages was just being received live by a BMP exporter.

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 RFC 2119 RFC 8174 when, and only when, they appear in all capitals, as shown here.

The Peer Summary message starts with a BMP Common Header as defined in Section 4.1 of then followed by one or multiple Peer TLVs with code-point &IANA_PS_CODE_PEER_TLV;. Each Peer TLV is structured as a plain TLV as defined in Section 3 of. The value part contains the BMP Common Header and Peer Up Notification body as defined in Section 4.10 of. The Peer Summary message is generated at a BMP station, it MUST encapsulate only actually received Peer Up data from BMP exporters.

While this document does define a way to facilitate replay and more in general consumption of raw BMP data offline, similar benefits may be harnessed by third party off-wire formats, in which BMP can be encapsulated into, for example MRT (Multi-Threaded Routing Toolkit) as defined by RFC 6396. As a result of that, this document does not recommend a preferred way to store BMP data offline.

The Peer Summary message injection in a BMP feed is done by an online BMP station for consumption by an offline BMP station. The advantage of creating summaries at the online BMP station (for example, as opposed to creating them at a BMP exporter) is that it has awareness of how offline data is being organized, for example if a new file is created every five minutes it may make sense to include the summary at the beginning of each file. A BMP station receiving multiple Peer Up for the same peer should perform state compression and include in the Peer Summary the last one received, based on timestamp, at the time the summary is being generated. In other words, the summary is not meant, for example if a BGP session is flapping, as event reporting and this is left to BMP Route Event Logging.

It is not believed that this document adds any additional security considerations.

IANA is asked to allocate a new Peer Summary message type in the BMP Message Types registry with value &IANA_PS_MSG_TYPE;. IANA is also asked to to create a registry within the BMP group, named "BMP Peer Summary Message TLVs". Registration procedures for this registry are: Range Registration Procedures 0-32767 Standards Action 32768-65530 First Come, First Served 65531-65534 Experimental 65535 Reserved Initial values for this registry are: Type Description Reference &IANA_PS_CODE_PEER_TLV; Peer this document