Skip to main content

Support for Local RIB in the BGP Monitoring Protocol (BMP)

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc: Job Snijders <>, The IESG <>,,,,,,
Subject: Protocol Action: 'Support for Local RIB in BGP Monitoring Protocol (BMP)' to Proposed Standard (draft-ietf-grow-bmp-local-rib-12.txt)

The IESG has approved the following document:
- 'Support for Local RIB in BGP Monitoring Protocol (BMP)'
  (draft-ietf-grow-bmp-local-rib-12.txt) as Proposed Standard

This document is the product of the Global Routing Operations Working Group.

The IESG contact persons are Warren Kumari and Robert Wilton.

A URL of this Internet Draft is:

Ballot Text

Technical Summary

   The BGP Monitoring Protocol (BMP) defines access to various 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.

Working Group Summary

   There was some discussion on what exactly constitutes the Loc-RIB, various vendors have slightly different interpretations of this abstract concept. This has been resolved in Section 3 (“definitions”) which clarifies the contents of the Loc-RIB as received via the BMP protocol potentially are different from what is stored on a BGP node in its local interpretation of Loc-RIB. 

Document Quality

   BMP Local RIB has been implemented on the receiver side in Pmacct and OpenBMP, both are widely deployed collectors. On the BMP export side Cisco, Huawei, and Juniper implemented support for Loc-RIB. This indicates broad support and a need for standardization.


   Warren Kumari is RAD!
   Job Snijders is the document shepherd.

RFC Editor Note