Skip to main content

TLV support for BMP Route Monitoring and Peer Down Messages

Document Type Expired Internet-Draft (grow WG)
Authors Paolo Lucente , Yunan Gu
Last updated 2022-09-08 (Latest revision 2022-03-07)
Replaces draft-lucente-bmp-tlv
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Expired & archived
Stream WG state WG Consensus: Waiting for Write-Up
Document shepherd Job Snijders
IESG IESG state Expired
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Most of the message types defined by the BGP Monitoring Protocol (BMP) make provision for optional trailing data. However, Route Monitoring messages (which provide a snapshot of the monitored Routing Information Base) and Peer Down messages (which indicate that a peering session was terminated) do not. Supporting optional data in TLV format across all BMP message types allows for a homogeneous and extensible surface that would be useful for the most different use-cases that need to convey additional data to a BMP station. While it is not intended for this document to cover any specific utilization scenario, it defines a simple way to support optional TLV data in all message types.


Paolo Lucente
Yunan Gu

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)