Hi Changwang, Authors,

Went thru the latest revision 16

1. Addition of a RIB-view scope table is the newer version is helpful. We seem 
to have picked only Adj-RIB-In, Adj-RIB-Out and LRIB only, but instead can we 
please include all 5 variants of RIB-views (In-Pre/Post, LRIB, Out-pre/post) 
and clarify in table and stats type of which of the RIB-views do the stats 
apply to. 

2. Looking at the stats defined as applicable across Adj-RIB-In and LRIB, if 
the answer to 'point C' below is 'Adj-RIB-In' only, then it seems to me like, 
we don't have a need for muxing of stats in this draft.

 |  24   |     Y    |     N     |   Y   |
 |  25   |     Y    |     N     |   Y   |
 |  26   |     Y    |     N     |   Y   |
 |  27   |     Y    |     N     |   Y   |
 |  28   |     Y    |     N     |   Y   |
 |  31   |     Y    |     N     |   Y   |
 |  32   |     Y    |     N     |   Y   |

A. These stats would only be applicable after bgp best-path is run only in the 
LRIB view, but it is marked as multiplexed across In-pre and lrib  
- Type = 24: (64-bit Gauge) Current Number of routes in per-AFI/SAFI selected 
as primary route.
- Type = 25: (64-bit Gauge) Current Number of routes in per-AFI/SAFI selected 
as a backup route.

B. Following stats are Adj-RIB-In only (not LRIB)
// In-Pre would have routes suppressed, not showing up in In-Post
- Type = 26: (64-bit Gauge) Current Number of routes in per-AFI/SAFI suppressed 
by configured route damping policy. 

// In-post, GR event marks them stale (do we want In-pre also here ?)
- Type = 27: (64-bit Gauge) Current Number of routes in per-AFI/SAFI marked as 
stale by Graceful Restart (GR) events. 
- Type = 28: (64-bit Gauge) Current Number of routes in per-AFI/SAFI marked as 
stale by Long-Lived Graceful Restart (LLGR). 

C. Stats 29/30 are defined as Adj-RIB-In only, but Stats 31/32 their license 
counterparts are defined to be across LRIB and Adj-RIB-In. Do you see the 
license thresholds being defined for both Adj-RIB-In/LRIB ? Dhananjay has asked 
for more clarity on license thresholds in the other thread, u could clarify 
these points together 
- Type = 31: (64-bit Gauge) Current Number of routes left before exceeding a 
license-customized route threshold. 
- Type = 32: (64-bit Gauge) Current Number of routes in per-AFI/SAFI left 
before exceeding a license-customized route threshold. 

3. Given the recent discussion on the WG mailer about routes/paths, multi-path 
scenario, primary/backup + the latest version updates clarifies a few things to 
avoid different interpretations, but also makes some areas more confusing to 
me, mentioning a few below

- it may be helpful to add a section on multi-path consideration and provide 
more clarity on the definitions around this. We can polish this a bit more in 
the draft across stats types (Eg: For stats 24, for ECMP case, we can have 
multiple paths eligible to be downloaded to system RIB - say if this count is 4 
for a given prefix, do we expect this count to be 1 or 4)

- The term route, path seem to be used interchangeably, sometimes route refers 
to path as well - for example in Type 26, Type 27, Type 28, we start the defn 
with routes but talk about paths later. The definition of Primary and Backup 
route also uses route/path interchangeably whilst stats type refers to routes. 

- Add-path as in RFC7911 is towards BGP peers, this would be independent of 
multi-path towards RIB. We could have one of these enabled without the other 
(Eg: best-path in HW + add-path towards peers)

Thanks
/snnp
(Prasad)


-----Original Message-----
From: [email protected] <[email protected]> 
Sent: 25 November 2025 08:52
To: [email protected]
Cc: [email protected]
Subject: [GROW] I-D Action: draft-ietf-grow-bmp-bgp-rib-stats-16.txt

Internet-Draft draft-ietf-grow-bmp-bgp-rib-stats-16.txt is now available. It is 
a work item of the Global Routing Operations (GROW) WG of the IETF.

   Title:   Advanced BGP Monitoring Protocol (BMP) Statistics Types
   Authors: Mukul Srivastava
            Yisong Liu
            Changwang Lin
            Jinming Li
   Name:    draft-ietf-grow-bmp-bgp-rib-stats-16.txt
   Pages:   18
   Dates:   2025-11-24

Abstract:

   RFC 7854 defines different BGP Monitoring Protocol (BMP) statistics
   message types to observe events that occur on a monitored router.
   This document defines new statistics type to monitor BMP Adj-RIB-In
   and Adj-RIB-Out Routing Information Bases (RIBs).

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-bgp-rib-stats/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-bgp-rib-stats-16

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-grow-bmp-bgp-rib-stats-16

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
GROW mailing list -- [email protected]
To unsubscribe send an email to [email protected]

_______________________________________________
GROW mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to