BMP Extension for Path Information TLV
draft-cppy-grow-bmp-path-info-tlv-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Camilo Cardona , Paolo Lucente , Pierre Francois , Yunan Gu , Thomas Graf | ||
| Last updated | 2021-01-13 (Latest revision 2020-07-12) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The BGP Monitoring Protocol (BMP) provides an interface for obtaining BGP path information. BGP Path Information is conveyed within BMP Route Monitoring (RM) messages. This document proposes an extension to BMP to convey additional path information that is not already encapsulated in the BGP Update PDU, e.g., BPG path status. This extension makes use of the TLV mechanims described in draft-grow-bmp- tlv [I-D.grow-bmp-tlv].
Authors
Camilo Cardona
Paolo Lucente
Pierre Francois
Yunan Gu
Thomas Graf
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)