On 10/11/18, 2:23 PM, "Jeffrey Haas" <[email protected]> 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.
> 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). 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.
[rest left in for future context]
-- Jeff
> I think we should
> allow the implementation to suppress the inactive or to advertise the
> inactive prefixes. We can use a per-peer flag to indicate that the
> NLRI's in the RM/BGP UPDATE are suppressed due to another routing
> protocol/direct/static having better preference. We'll also need to add a
> new INFO TLV in the PEER UP to indicate the expected conveyance of
> inactive/rib-failure NLRI's.
>
> Unless others have hardship about adding this, I can do an update.
>
>
> Thanks,
> Tim
>
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
