Tim, On Thu, Oct 11, 2018 at 09:33:16PM +0000, Tim Evens (tievens) wrote: > > On 10/11/18, 2:23 PM, "Jeffrey Haas" <jh...@pfrc.org> wrote: > > > > [Trimming original thread to re-ask my core question.] > > > > On Thu, Oct 11, 2018 at 09:18:17PM +0000, Tim Evens (tievens) wrote: > > > The local RIB in BMP should only contain what is/would be > > used/installed. > > > > From where? BGP's best route? The routing table's active route? > > It's the BGP best/selected route.
Ok, that at least gives us something concrete to discuss. > > > In other words, the local rib sent via BMP should not contain the > > > suppressed prefixes that were not installed due to another routing > > > protocol/direct/static having a better preference. > > > > Which ties into the RFC question about where other protocols are > > injected > > into the Decision Process. > > > > If you read the RFC as literally saying it's injecting it into the > > Decision > > Process (section 9.4), the LocRib should be the best route and thus the > > active route regardless of whether it was learned from BGP or not. > > RIB failures due to another routing protocol preference is limited in > scope to specific AFI/SAFI's (e.g. mainly IPv4/IPv6 unicast/multicast). I don't recognize the term "RIB failure". > For this use-case of installation/rib-failures where the prefix would be > used but cannot be installed seems to justify a flag/info_tlv to indicate > that. If you're saying "when the active route in the Routing Table (used for forwarding) is not the best BGP route, and we're sending the best BGP route in BMP as the loc-rib entry, we should flag that", then I at least understand what you're saying. So, I think we're back to my original points with better context: The biggest motivation to have a "loc-rib" feed in BMP is to avoid the need for a parallel BGP feed from a given router for correlation purposes. BGP will advertise its active route in the majority of cases. In the case where we're not putting the route that we're advertising into this feed, we're basically bypassing the use case. While I agree that the best bgp route is a useful thing, it's a somewhat different use case. --- I'll answer the followup mail once "rib failure" is explained. I suspect we're hitting implementation details, which are obscuring the discussion from a vendor-neutral standards point. -- Jeff _______________________________________________ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
