Subject: [GROW] Re: Review of draft-ietf-grow-bmp-bgp-rib-stats-05
From: linchangwang <[email-masked]>
To: "[email-masked]" <[email-masked]>, "Mukul Srivastava" <[email-masked]>, Mukul Srivastava <msri=[email-masked]>, "[email-masked]" <[email-masked]>
Cc: "[email-masked]" <[email-masked]>
Date: Thu, 24 Apr 2025 12:47:09 +0000
List-Id: Grow Working Group Mailing List <grow.ietf.org>

Hi Med,

Thank you for your prompt response and thorough  review.
We will request a WGLC and then address this comment in the next version.

Thanks,
Changwang

发件人: [email-masked] <[email-masked]>
发送时间: 2025年4月24日 20:31
收件人: linchangwang (RD) <[email-masked]>; Mukul Srivastava <[email-masked]>; Mukul Srivastava <msri=[email-masked]>; [email-masked]
抄送: [email-masked]
主题: RE: Review of draft-ietf-grow-bmp-bgp-rib-stats-05

Hi Changwang,

Thank you for taking care of this. The two issues are resolved in this version.

I see that you also made this change s/may discard/MAY discard. I think the OLD was correct. You can fix this in your local copy; no need to release a new version for this. This can wait for other comments you may get in the WGLC. Thanks.

Cheers,
Med

De : linchangwang <[email-masked]<mailto:[email-masked]>>
Envoyé : jeudi 24 avril 2025 14:18
À : BOUCADAIR Mohamed INNOV/NET <[email-masked]<mailto:[email-masked]>>; Mukul Srivastava <[email-masked]<mailto:[email-masked]>>; Mukul Srivastava <msri=[email-masked]<mailto:msri=[email-masked]>>; [email-masked]<mailto:[email-masked]>
Cc : [email-masked]<mailto:[email-masked]>
Objet : Re: Review of draft-ietf-grow-bmp-bgp-rib-stats-05

Hi Med,

Thank you for your review.

We've submitted version-08 addressing these comments.

Link: https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-bgp-rib-stats/08/

Pls check and let us know if there are any further comments.

Thanks,
Changwang

发件人: [email-masked]<mailto:[email-masked]> <[email-masked]<mailto:[email-masked]>>
发送时间: 2025年4月23日 15:38
收件人: Mukul Srivastava <[email-masked]<mailto:[email-masked]>>; Mukul Srivastava <msri=[email-masked]<mailto:msri=[email-masked]>>; [email-masked]<mailto:[email-masked]>
抄送: [email-masked]<mailto:[email-masked]>
主题: RE: Review of draft-ietf-grow-bmp-bgp-rib-stats-05

Hi Mukul,

Any update about this one? Thank you.

Cheers,
Med

De : Mukul Srivastava <[email-masked]<mailto:[email-masked]>>
Envoyé : jeudi 27 février 2025 21:51
À : BOUCADAIR Mohamed INNOV/NET <[email-masked]<mailto:[email-masked]>>; Mukul Srivastava <msri=[email-masked]<mailto:msri=[email-masked]>>; [email-masked]<mailto:[email-masked]>
Cc : [email-masked]<mailto:[email-masked]>
Objet : Re: Review of draft-ietf-grow-bmp-bgp-rib-stats-05

Thanks, Med, for the review.

We will soon update doc on this.

Thanks
Mukul

Juniper Business Use Only
From: [email-masked]<mailto:[email-masked]> <[email-masked]<mailto:[email-masked]>>
Date: Monday, February 24, 2025 at 5:43 AM
To: Mukul Srivastava <[email-masked]<mailto:[email-masked]>>, Mukul Srivastava <msri=[email-masked]<mailto:msri=[email-masked]>>, [email-masked]<mailto:[email-masked]> <[email-masked]<mailto:[email-masked]>>
Cc: [email-masked]<mailto:[email-masked]> <[email-masked]<mailto:[email-masked]>>
Subject: RE: Review of draft-ietf-grow-bmp-bgp-rib-stats-05
[External Email. Be cautious of content]

Hi Mukul,

Thank you for taking care of the comments. I appreciate the new section on the implementation status.

When reviewing the 05-07 diff, I have the following comments:

* Does it really make sense to include text that mandates a vendor-specific behavior? Why using type 31 isn’t sufficient here?

CURRENT:
      If the license-customized route threshold is vendor specific, this
      type value (31) SHOULD use enterprise-specific TLV encoding as
      described in Section 3.3 of [I-D.ietf-grow-bmp-tlv-ebit].

I tend to suggest deleting that part.

* The descriptions in the IANA section should be consistent with BMP practice (that is, delete “(64-bit Gauge)”). See that inconsistency at https://www.iana.org/assignments/bmp-parameters/bmp-parameters.xhtml#statistics-types<https://urldefense.com/v3/__https:/www.iana.org/assignments/bmp-parameters/bmp-parameters.xhtml*statistics-types__;Iw!!NEt6yMaO-gk!BbvLvZxPfWUkZcmq6Ppo3rVTWyzD9fzgWlyxtczLOgJQyoWQvO2PDpwo2nRcebJBauJ6yitUFn_Fwmpj57dnW3im$>. Having a column to clearly indicate the type would be useful, though.

Cheers,
Med

Juniper Business Use Only
De : Mukul Srivastava <[email-masked]<mailto:[email-masked]>>
Envoyé : vendredi 21 février 2025 17:31
À : Mukul Srivastava <msri=[email-masked]<mailto:msri=[email-masked]>>; BOUCADAIR Mohamed INNOV/NET <[email-masked]<mailto:[email-masked]>>; [email-masked]<mailto:[email-masked]>
Cc : [email-masked]<mailto:[email-masked]>
Objet : Re: Review of draft-ietf-grow-bmp-bgp-rib-stats-05

Hello Med

All your comments have been addressed in latest version.
https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-bgp-rib-stats/07/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-ietf-grow-bmp-bgp-rib-stats/07/__;!!NEt6yMaO-gk!BbvLvZxPfWUkZcmq6Ppo3rVTWyzD9fzgWlyxtczLOgJQyoWQvO2PDpwo2nRcebJBauJ6yitUFn_Fwmpj55sUUtIX$>

Pls check and let us know if there are any further comments.

Thanks
Mukul

Juniper Business Use Only
From: Mukul Srivastava <msri=[email-masked]<mailto:msri=[email-masked]>>
Date: Tuesday, February 18, 2025 at 8:32 AM
To: [email-masked]<mailto:[email-masked]> <[email-masked]<mailto:[email-masked]>>, [email-masked]<mailto:[email-masked]> <[email-masked]<mailto:[email-masked]>>
Cc: [email-masked]<mailto:[email-masked]> <[email-masked]<mailto:[email-masked]>>
Subject: [GROW] Re: Review of draft-ietf-grow-bmp-bgp-rib-stats-05
[External Email. Be cautious of content]

Thanks, Med, for your comments. I would go over them and get back to you.

Thanks
Mukul

Juniper Business Use Only

Juniper Business Use Only
From: [email-masked]<mailto:[email-masked]> <[email-masked]<mailto:[email-masked]>>
Date: Friday, February 7, 2025 at 10:12 AM
To: [email-masked]<mailto:[email-masked]> <[email-masked]<mailto:[email-masked]>>
Cc: [email-masked]<mailto:[email-masked]> <[email-masked]<mailto:[email-masked]>>
Subject: Review of draft-ietf-grow-bmp-bgp-rib-stats-05
[External Email. Be cautious of content]

Hi  Mukul, Yisong, Changwang, and Jinming,

Thank you for the effort put into this document. FWIW, you may find a review at:

  *   pdf: https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/2025/draft-ietf-grow-bmp-bgp-rib-stats-05-rev%20Med.pdf<https://urldefense.com/v3/__https:/github.com/boucadair/IETF-Drafts-Reviews/blob/master/2025/draft-ietf-grow-bmp-bgp-rib-stats-05-rev*20Med.pdf__;JQ!!NEt6yMaO-gk!Cl2I5P4e4ExpPUJdtm8UN8u8IFgFDRtP2U9y1PKh-ffpAgmwG35ar4QMQ0rKODbIGPOLCzOgaZRrj2nMaHga8NNo$>
  *   doc: https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/2025/draft-ietf-grow-bmp-bgp-rib-stats-05-rev%20Med.doc<https://urldefense.com/v3/__https:/github.com/boucadair/IETF-Drafts-Reviews/blob/master/2025/draft-ietf-grow-bmp-bgp-rib-stats-05-rev*20Med.doc__;JQ!!NEt6yMaO-gk!Cl2I5P4e4ExpPUJdtm8UN8u8IFgFDRtP2U9y1PKh-ffpAgmwG35ar4QMQ0rKODbIGPOLCzOgaZRrj2nMaODB7c5B$>

The document includes a comprehensive list of stat types. I wonder whether we have a public record about available implems of these stats.

The document claims that it updates 7854, but I don’t think it does.

Also, I recommend the authors to fix the normative dependency on an individual draft. You can easily get ride of that citation by having self-contained description. I guess you can do the same even with draft-ietf-rtgwg-bgp-pic (which is expired).

One side comment, unlike the approach followed by 7854, the new entries at https://www.iana.org/assignments/bmp-parameters/bmp-parameters.xhtml<https://urldefense.com/v3/__https:/www.iana.org/assignments/bmp-parameters/bmp-parameters.xhtml__;!!NEt6yMaO-gk!Cl2I5P4e4ExpPUJdtm8UN8u8IFgFDRtP2U9y1PKh-ffpAgmwG35ar4QMQ0rKODbIGPOLCzOgaZRrj2nMaDQQxB1G$> includes the type as part of the description. If that information is important, it is cleaner to consider adding a new column to the registry (called type) to record that.

Cheers,
Med

____________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

____________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

____________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.
-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有新华三集团的保密信息，仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、
或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本
邮件！
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!

____________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.