Monitoring BGP Parameters Using BMP
draft-zhuang-grow-monitoring-bgp-parameters-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Shunwan Zhuang , Yunan Gu , Haibo Wang | ||
| Last updated | 2020-05-07 (Latest revision 2019-11-04) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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) [RFC7854] is designed to monitor BGP [RFC4271] running status, such as BGP peer relationship establishment and termination and route updates. Without BMP, manual query is required if you want to know about BGP running status. This document provides the use cases that the BMP station can get the optional parameters that are supported by the monitored network device and default configure parameters of the monitored network device via BMP.
Authors
Shunwan Zhuang
Yunan Gu
Haibo Wang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)