BGP Route Policy and Attribute Trace Using BMP
draft-xu-grow-bmp-route-policy-attr-trace-05

Document Type Expired Internet-Draft (individual)
Authors Feng Xu  , Thomas Graf  , Yunan Gu  , Shunwan Zhuang  , Zhenbin Li 
Last updated 2021-01-27 (latest revision 2020-07-26)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized 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-xu-grow-bmp-route-policy-attr-trace-05.txt

Abstract

The generation of BGP adj-rib-in, local-rib or adj-rib-out comes from BGP route exchange and route policy processing. BGP Monitoring Protocol (BMP) provides the monitoring of BGP adj-rib-in [RFC7854], BGP local-rib [I-D.ietf-grow-bmp-local-rib] and BGP adj-rib-out [I-D.ietf-grow-bmp-adj-rib-out]. By monitoring these BGP RIB's the full state of the network is visible, but how route-policies affect the route propagation or changes BGP attributes is still not. This document describes a method of using BMP to record the trace data on how BGP routes are (not) changed under the process of route policies.

Authors

Feng Xu (oliverxu@tencent.com)
Thomas Graf (thomas.graf@swisscom.com)
Yunan Gu (guyunan@huawei.com)
Shunwan Zhuang (zhuangshunwan@huawei.com)
Zhenbin Li (lizhenbin@huawei.com)

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