Dear GROW,

As suggested in the working group meeting in Bangkok,
draft-ietf-grow-bmp-local-rib may ready for last call. The last call
will be 2 weeks, ending November 26th, 2018.

Abstract:

    The BGP Monitoring Protocol (BMP) defines access to the Adj-RIB-In
    and locally originated routes (e.g. routes distributed into BGP from
    protocols such as static) but not access to the BGP instance
    Loc-RIB. This document updates the BGP Monitoring Protocol (BMP)
    RFC 7854 by adding access to the BGP instance Local-RIB, as defined
    in RFC 4271 the routes that have been selected by the local BGP
    speaker's Decision Process. These are the routes over all peers,
    locally originated, and after best-path selection.

The document is at 
https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-local-rib

Please review the document and provide feedback.

The internet-draft authors should note that Jeff Haas contributed a
comment to the IETF 103 GROW jabber room that unfortunatly wasn't read
out loud. This comment should be considered input into the last call
process:

    jhaas> "For loc-rib draft, list discussion was over whether we should
    advertise active route vs. best bgp route. Best bgp route means
    that you still need an active bgp session to monitor actual bgp and
    doesn't simplify use case."
    https://www.ietf.org/jabber/logs/grow/2018-11-05.html

Kind regards,

Job & Chris

_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow

Reply via email to