RFC 7854: BGP Monitoring Protocol (BMP)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7854
- Published
- June 2016
- Authors
- J. Scudder; R. Fernando; S. Stuart
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 27
- Also known as
- —
Topics
Referenced by
4 later RFCs formally update or obsolete part of this document.
- RFC 8671Support for Adj-RIB-Out in the BGP Monitoring Protocol (BMP)Updated
November 2019
- RFC 9069Support for Local RIB in the BGP Monitoring Protocol (BMP)Updated
February 2022
- RFC 9515Revision to Registration Procedures for Multiple BMP RegistriesCurrent
December 2023
- RFC 9736The BGP Monitoring Protocol (BMP) Peer Up Message NamespaceCurrent
March 2025
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9972Advanced BGP Monitoring Protocol (BMP) Statistics TypesCurrent
May 2026
- RFC 7705Autonomous System Migration Mechanisms and Their Effects on the BGP AS_PATH AttributeCurrent
November 2015
- RFC 8538Notification Message Support for BGP Graceful RestartCurrent
March 2019
- RFC 9072Extended Optional Parameters Length for BGP OPEN MessageCurrent
July 2021
- RFC 5575Dissemination of Flow Specification RulesObsoleted
August 2009
- RFC 5492Capabilities Advertisement with BGP-4Updated
February 2009
- RFC 7908Problem Definition and Classification of BGP Route LeaksCurrent
June 2016
- RFC 7948Internet Exchange BGP Route Server OperationsCurrent
September 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?