Changwang, Thanks for your patience while I was on PTO.
I noticed that Mukul's reply was suggesting that Loc-RIB was removed from the I-D, but it seems that the rest of the authors want to continue with it. While I still think that section 4 should be more normative about Loc-RIB, I will clear my DISCUSS as it is more palatable and clearer now, but please consider being more normative in section 4. Regards -éric Cisco Confidential From: linchangwang <[email protected]> Date: Friday, 14 November 2025 at 13:44 To: Eric Vyncke (evyncke) <[email protected]>, Srivastava, Mukul <[email protected]>, The IESG <[email protected]> Cc: [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]> Subject: Re: [GROW] Éric Vyncke's Discuss on draft-ietf-grow-bmp-bgp-rib-stats-13: (with DISCUSS and COMMENT) Hi éric, Thank you for your prompt and insightful review and suggestions. Your comments have been addressed in latest version. Link: https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-bgp-rib-stats/14/ Diff: https://author-tools.ietf.org/iddiff?url1=draft-ietf-grow-bmp-bgp-rib-stats-13&url2=draft-ietf-grow-bmp-bgp-rib-stats-14&difftype=--html The main revisions are as follows: 1. Make the changes based on the discussion between Mukul and you below. 2. For DISCUSS (blocking) comments, the updates include: * In the Introduction section， add the following: “The applicability scope of these new gauges (Adj-RIB-In,Adj-RIB-Out, Loc-RIB) is provided in Section 4. * In Section 3, add the following: "Some of these statistics are also applicable to Loc-RIB; refer to Section 4 for more details." * Revise the title of Section 4 from "Summary" to "Application Scope of Statistics." Pls check and let us know if there are any further comments. Thanks, Changwang 发件人: Eric Vyncke (evyncke) <[email protected]> 发送时间: 2025年11月13日 0:11 收件人: Srivastava, Mukul <[email protected]>; The IESG <[email protected]> 抄送: [email protected]; [email protected]; [email protected]; [email protected] 主题: Re: [GROW] Éric Vyncke's Discuss on draft-ietf-grow-bmp-bgp-rib-stats-13: (with DISCUSS and COMMENT) Hi Mukul Thanks for the prompt reply, and indeed to address the blocking DISCUSS a revised I-D must be uploaded for the DISCUSS point Regards -éric Cisco Confidential From: Srivastava, Mukul <[email protected]<mailto:[email protected]>> Date: Wednesday, 12 November 2025 at 16:40 To: Eric Vyncke (evyncke) <[email protected]<mailto:[email protected]>>, The IESG <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>, [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>, [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>, [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Subject: Re: [GROW] Éric Vyncke's Discuss on draft-ietf-grow-bmp-bgp-rib-stats-13: (with DISCUSS and COMMENT) Hello All Pls see my response below with MS: >>> DISCUSS (blocking) comments [MS] - My understanding is that these statistics are only for BMP rib-in and rib-out monitoring. I am not sure how/when some of the stats mentioned in section 4 were marked for local-rib monitoring. I will wait for my co-author response on this. >>> ### Section 1 [MS] I agree and that can be updated by removing sentence 1. >>> ### Section 3.1 [MS] Personally I am fine with the current format for describing the stats like - "name (type = #, format) longer description”. This aligns with the prior BMP RFCs of describing stats. As you pointed this is more like a personal taste. I feel that a router should send both types on wire (ex 7 & 18) if it is able to do so. Let BMP collectors decide what it wants to do when it receives both types. Also, it is likely that there are applications already build using existing type 7 and we don’t want to break that when type 18 is implemented by someone using this draft. In fact, I feel we shouldn’t provide any recommendations in this draft about which type should be streamed out by router and consumed by BMP station. This is more like an implementation detail. >>> ### Section 7 and 10.2 [MS] Sure the document can be updated for this. Let me know if you all agree or have further comments. One clarification - I am assuming, we need to publish a new version with above changes. Kindly confirm. Thanks Mukul From: Éric Vyncke via Datatracker <[email protected]<mailto:[email protected]>> Date: Wednesday, November 12, 2025 at 9:54 AM To: The IESG <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>, [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>, [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>, [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Subject: [GROW] Éric Vyncke's Discuss on draft-ietf-grow-bmp-bgp-rib-stats-13: (with DISCUSS and COMMENT) Éric Vyncke has entered the following ballot position for draft-ietf-grow-bmp-bgp-rib-stats-13: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://urldefense.com/v3/__https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/__;!!NEt6yMaO-gk!GV_tlXr7JEuw_CJX6796BZn5cZCW3M3m4Ptv10kRf3JxiEKAbl-yRBh1skIb7D4sL8sZsQHfg1yz$<https://urldefense.com/v3/__https:/www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/__;!!NEt6yMaO-gk!GV_tlXr7JEuw_CJX6796BZn5cZCW3M3m4Ptv10kRf3JxiEKAbl-yRBh1skIb7D4sL8sZsQHfg1yz$> for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-bgp-rib-stats/__;!!NEt6yMaO-gk!GV_tlXr7JEuw_CJX6796BZn5cZCW3M3m4Ptv10kRf3JxiEKAbl-yRBh1skIb7D4sL8sZsdZl3P-1$<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-ietf-grow-bmp-bgp-rib-stats/__;!!NEt6yMaO-gk!GV_tlXr7JEuw_CJX6796BZn5cZCW3M3m4Ptv10kRf3JxiEKAbl-yRBh1skIb7D4sL8sZsdZl3P-1$> ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- # Éric Vyncke, INT AD, comments for draft-ietf-grow-bmp-bgp-rib-stats-13 CC @evyncke Thank you for the work put into this document. Please find below one blocking DISCUSS points (easy to address), some non-blocking COMMENT points/nits (replies would be appreciated even if only for my own education). Special thanks to Job Snijders for the shepherd's write-up including the WG consensus *and* the justification of the intended status. I hope that this review helps to improve the document, Regards, -éric ## DISCUSS (blocking) As noted in https://urldefense.com/v3/__https://datatracker.ietf.org/doc/statement-iesg-handling-ballot-positions-20220121/__;!!NEt6yMaO-gk!GV_tlXr7JEuw_CJX6796BZn5cZCW3M3m4Ptv10kRf3JxiEKAbl-yRBh1skIb7D4sL8sZsVWfKqjI$<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/statement-iesg-handling-ballot-positions-20220121/__;!!NEt6yMaO-gk!GV_tlXr7JEuw_CJX6796BZn5cZCW3M3m4Ptv10kRf3JxiEKAbl-yRBh1skIb7D4sL8sZsVWfKqjI$> , a DISCUSS ballot is a request to have a discussion on the points below; I really think that the document would be improved with a change here, but can be convinced otherwise. ### Section 3.3 There is no section 3.3 to list the types for Loc-RIB, the reader has to wait until section 4 to see this mentioned in the "summary", which is NOT a summary as it specifies the available value for Loc-RIB. I.e., add a section 3.3 listing the type numbers available for Loc-RIB. ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- ## COMMENTS (non-blocking) ### Section 1 Mostly cosmetic but the 1st sentence of the 2nd paragraph has little value, the 2nd sentence seems to be enough. ### Section 3.1 It is a matter of taste of course, but I would have preferred to have the statistic types presented as "name (type = #, format) longer description" as starting with the type number is cumbersome for the reader. I also failed to understand the logic of sending only one (as opposed to the latest version of this I-D) type when two are available (e.g., for types 7 & 18), should there be some recommendations ? ### Section 7 Please use the exact URI of https://urldefense.com/v3/__https://www.iana.org/assignments/bmp-parameters/bmp-parameters.xhtml*statistics-types__;Iw!!NEt6yMaO-gk!GV_tlXr7JEuw_CJX6796BZn5cZCW3M3m4Ptv10kRf3JxiEKAbl-yRBh1skIb7D4sL8sZsSYHBla9$<https://urldefense.com/v3/__https:/www.iana.org/assignments/bmp-parameters/bmp-parameters.xhtml*statistics-types__;Iw!!NEt6yMaO-gk!GV_tlXr7JEuw_CJX6796BZn5cZCW3M3m4Ptv10kRf3JxiEKAbl-yRBh1skIb7D4sL8sZsSYHBla9$> ### Section 10.2 As indicated by the idnits tool, s/Informational References/*Informative* References/ _______________________________________________ GROW mailing list -- [email protected]<mailto:[email protected]> To unsubscribe send an email to [email protected]<mailto:[email protected]> ------------------------------------------------------------------------------------------------------------------------------------- 本邮件及其附件含有新华三集团的保密信息，仅限于发送给上面地址中列出 的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、 或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本 邮件！ This e-mail and its attachments contain confidential information from New H3C, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
_______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
