What is this "approximate state"? Why does a sample peer not give you approximate state? Why does loc-rib not give you approximate state?
Thanks, Jakob. > On Jul 13, 2017, at 3:51 AM, Jeffrey Haas <[email protected]> wrote: > > Jakob, > >> On Wed, Jul 12, 2017 at 10:48:28PM +0000, Jakob Heitz (jheitz) wrote: >> Here are some more factors that cause different updates to peers in the same >> peer-group: >> - RT Constraint: This filters different updates from different peers. >> - Refresh requests: Only the peer that sent the request receives the updates. >> - Nexthop SAFI (future). > > You missed simple BGP loop detection such as RRs with cluster list or > originator ID suppression for iBGP or AS_PATH for eBGP. > >> IMO, the point of BMP is to take the guess work out of figuring out what was >> sent. >> Peer-groups will add more guess work. > > Much of my point is that even without complicated features, if you care > about per-peer state, you have to monitor *ALL* of the peers. Otherwise, > you're going to miss things. There's no "monitor one or two sample peers". > > You either care about the approximate state of the peers in the group or you > care about the exact state. The use cases are different. > > -- Jeff _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
