Description
Hello!
Does goBMP support the following capabilities that are required to successfully ingest BMP LOC-RIB Route monitoring messages?
1) VRF Name TLV (RFC9069 §5.2.1)
Support parsing of VRF name TLV in BMP Peer Up messages. While RD+BGP-ID can be used for VRF mapping, the VRF Name TLV simplifies collector operation and enables human-friendly VRF association.
2) Multi-VRF Route Handling
Ensure that routes received from different VRFs (default, VRF1, etc.) are maintained distinctly and exported as such to downstream systems. We’d like to avoid cross-VRF deduplication. For example: When prefix 1 is received from default VRF and VRF1, two instances of prefix1 must be maintained (one per VRF) and exported as such to a downstream consumer.
3) ECMP Awareness via add-path (RFC7911)
Support for collecting multiple paths for a single prefix via add-path. This is required to fully reflect LOC-RIB ECMP information on platforms that support it.
- Support for Peer-type 3 to ingest LOC-RIB messages.