Monitoring Outgoing Routes Using BMP
draft-mi-grow-monitoring-outgoing-bgp-routes-00

Document Type Expired Internet-Draft (individual)
Last updated 2017-09-14 (latest revision 2017-03-13)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-mi-grow-monitoring-outgoing-bgp-routes-00.txt

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. At present, the BMP only monitors the incoming bgp routes (Adj-RIB-In), does not monitor the outgoing bgp routes (Adj-RIB-Out). This draft extends the applicability of BMP [RFC7854] to monitor the outgoing bgp routes.

Authors

Kevin Mi (kevinmi@tencent.com)
Shunwan Zhuang (zhuangshunwan@huawei.com)
Jie Dong (jie.dong@huawei.com)

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