Dear GROW members,
We have just submitted a new draft that extends BMP to collect the correlated
BGP route policy and route attributes for route policy validation.
Comments are very welcome!
Oliver.
On [DATE], "[NAME]" <[ADDRESS]> wrote:
A new version of I-D, draft-xu-grow-bmp-route-policy-attr-trace-00.txt
has been successfully submitted by Yunan Gu and posted to the
IETF repository.
Name: draft-xu-grow-bmp-route-policy-attr-trace
Revision: 00
Title: BGP Route Policy and Attribute Trace Using BMP
Document date: 2019-03-09
Group: Individual Submission
Pages: 12
URL:
https://www.ietf.org/internet-drafts/draft-xu-grow-bmp-route-policy-attr-trace-00.txt
Status:
https://datatracker.ietf.org/doc/draft-xu-grow-bmp-route-policy-attr-trace/
Htmlized:
https://tools.ietf.org/html/draft-xu-grow-bmp-route-policy-attr-trace-00
Htmlized:
https://datatracker.ietf.org/doc/html/draft-xu-grow-bmp-route-policy-attr-trace
Abstract:
The generation of BGP adj-rib-in, local-rib or adj-rib-out comes from
BGP protocol communication, 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]. However, there lacks
monitoring of how BGP routes are transformed from adj-rib-in into
local-rib and then adj-rib-out (i.e., the BGP route policy processing
procedures). This document describes a method of using BMP to trace
the change of BGP routes in correlation with responsible route
policies.
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
The IETF Secretariat
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
