Hi,
I approve the change. Best Regards Jinming ----邮件原文---- 发件人：Megan Ferguson <[email protected]> 收件人："linchangwang (RD)" <[email protected]>,"[email protected]" <[email protected]>,"[email protected]" <[email protected]> 抄 送: "[email protected]" <[email protected]>,"[email protected]" <[email protected]>,"[email protected]" <[email protected]>,"[email protected]" <[email protected]>,"[email protected]" <[email protected]>,"[email protected]" <[email protected]>,"Srivastava, Mukul" <[email protected]> 发送时间：2026-05-08 00:44:54 主题：Re: [AD] AUTH48: RFC-to-be 9972<draft-ietf-grow-bmp-bgp-rib-stats-17> for your review All,*AD - please review and approve the removal of a BCP 14 keyword as follows:>> >> 7) >> >> 【Changwang] I agree with the above modifications.Changwang - Thank you for your reply and guidance. We have updated the files as requested and reposted them. We believe all of our initial queries have been resolved and have marked them as such on the this document’s AUTH48 status page (see link below).Please review the files carefully as we do not make changes once published as an RFC.We will await approvals of the document in its current form from each of the parties listed at the AUTH48 status page prior to moving the document forward in the publication process. The files have been posted here (please refresh): https://www.rfc-editor.org/authors/rfc9972.txt https://www.rfc-editor.org/authors/rfc9972.pdf https://www.rfc-editor.org/authors/rfc9972.html https://www.rfc-editor.org/authors/rfc9972.xml The diff files have been posted here (please refresh): https://www.rfc-editor.org/authors/rfc9972-diff.html (Comprehensive) https://www.rfc-editor.org/authors/rfc9972-rfcdiff.html (same as above but side by side) https://www.rfc-editor.org/authors/rfc9972-auth48diff.html (AUTH48 changes only) https://www.rfc-editor.org/authors/rfc9972-auth48rfcdiff.html (side by side) The AUTH48 status page for this document is available here: https://www.rfc-editor.org/auth48/rfc9972Thank you.Megan FergusonRFC Production Center> On May 7, 2026, at 9:48AM, Srivastava, Mukul wrote:> > I just want to support the feedback provided by Changing.> I am in sync with the changes suggest.> > Thanks> Mukul> > From: linchangwang (RD) > Date: Thursday, May 7, 2026 at 11:32AM> To: [email protected] Srivastava, Mukul [email protected] [email protected] > Cc: [email protected] [email protected] [email protected] [email protected] [email protected] > Subject: Re: AUTH48: RFC-to-be 9972 for your review> > Hi,> > Thank you for your valuable feedback.> For a detailed response, please see the reply below.> > Thanks,> Changwang> > -----邮件原件-----> 发件人: [email protected] > 发送时间: 2026年5月6日 20:15> 收件人: [email protected] [email protected] linchangwang (RD) [email protected]> 抄送: [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]> 主题: Re: AUTH48: RFC-to-be 9972 for your review> > > > Authors,> > While reviewing this document during AUTH48, please resolve (as necessary) the following questions, which are also in the source file.> > 1) > [Changwang] Here it simply means that Collector is equivalent to Monitoring Station, without the need for a Monitoring Station to appear. No modifications are required.> > > 2) > 【Changwang] If directly abbreviated, it is recommended to change it to the following:> NEW:> ...Global Statistics and Per-AFI/SAFI [see RFC4760] Statistics.> > > 3) > > 【Changwang] Please modify as follows:> OLD:> The Per-AFI/SAFI Statistics apply only to the AFI/SAFIs that a BGP speaker supports and negotiates with its peer.> > NEW:> The Per-AFI/SAFI Statistics apply only to the AFI/SAFI that a BGP speaker supports and negotiates with its peer.> > > 4) > > 【Changwang] I agree with the above modifications.> > > 5) > 【Changwang] I agree with the above modifications.> > 6) > 【Changwang] Change it to be consistent with the definition of Section 8.> > > 7) > > 【Changwang] I agree with the above modifications.> > 8) > 【Changwang] I agree with the above modifications.> > 9) > [Changwang] "sample..., buffer..., or temporarily suspend..."> NEW:> To avoid adversely impacting the restart process, a BMP statistics producer MAY choose to sample this value at a lower frequency, buffer the updates, or temporarily suspend reporting for this type during the most critical phases of a switchover.> > > 10) > [Changwang] Agreed.> > > 11) > [Changwang] alphabetized.> > > 12) > [Changwang] statistics types.> > > 13) > [Changwang] Agreed, please make the changes uniformly.> > 14) > [Changwang] Reviewed, no modifications needed.> > > Thank you.> > Megan Ferguson> RFC Production Center> > *****IMPORTANT*****> > Updated 2026/05/06> > RFC Author(s):> --------------> > Instructions for Completing AUTH48> > Your document has now entered AUTH48. Once it has been reviewed and approved by you and all coauthors, it will be published as an RFC.> If an author is no longer available, there are several remedies available as listed in the FAQ (https://www.rfc-editor.org/faq/).> > You and you coauthors are responsible for engaging other parties (e.g., Contributors or Working Group) as necessary before providing your approval.> > Planning your review> ---------------------> > Please review the following aspects of your document:> > * RFC Editor questions> > Please review and resolve any questions raised by the RFC Editor> that have been included in the XML file as comments marked as> follows:> > > > These questions will also be sent in a subsequent email.> > * Changes submitted by coauthors> > Please ensure that you review any changes submitted by your> coauthors. We assume that if you do not speak up that you> agree to changes submitted by your coauthors.> > * Content> > Please review the full content of the document, as this cannot> change once the RFC is published. Please pay particular attention to:> - IANA considerations updates (if applicable)> - contact information> - references> > * Copyright notices and legends> > Please review the copyright notice and legends as defined in> RFC 5378 and the Trust Legal Provisions> (TLP – https://trustee.ietf.org/license-info).> > * Semantic markup> > Please review the markup in the XML file to ensure that elements of> content are correctly tagged. For example, ensure that > and are set correctly. See details at> .> > * Formatted output> > Please review the PDF, HTML, and TXT files to ensure that the> formatted output, as generated from the markup in the XML file, is> reasonable. Please note that the TXT will have formatting> limitations compared to the PDF and HTML.> > > Submitting changes> ------------------> > To submit changes, please reply to this email using ‘REPLY ALL’ as all the parties CCed on this message need to see your changes. The parties> include:> > * your coauthors> > * [email protected] (the RPC team)> > * other document participants, depending on the stream (e.g.,> IETF Stream participants are your working group chairs, the> responsible ADs, and the document shepherd).> > * [email protected], which is a new archival mailing list> to preserve AUTH48 conversations it is not an active discussion> list:> > * More info:> https://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc> > * The archive itself:> https://mailarchive.ietf.org/arch/browse/auth48archive/> > * Note: If only absolutely necessary, you may temporarily opt out> of the archiving of messages (e.g., to discuss a sensitive matter).> If needed, please add a note at the top of the message that you> have dropped the address. When the discussion is concluded,> [email protected] will be re-added to the CC list and> its addition will be noted at the top of the message.> > You may submit your changes in one of two ways:> > An update to the provided XML file> — OR —> An explicit list of changes in this format> > Section # (or indicate Global)> > OLD:> old text> > NEW:> new text> > You do not need to reply with both an updated XML file and an explicit list of changes, as either form is sufficient.> > We will ask a stream manager to review and approve any changes that seem beyond editorial in nature, e.g., addition of new text, deletion of text, and technical changes. Information about stream managers can be found in the FAQ. Editorial changes do not require approval from a stream manager.> > > Approving for publication> --------------------------> > To approve your RFC for publication, please reply to this email stating that you approve this RFC for publication. Please use ‘REPLY ALL’, as all the parties CCed on this message need to see your approval.> > > Files> -----> > The files are available here:> https://www.rfc-editor.org/authors/rfc9972.xml> https://www.rfc-editor.org/authors/rfc9972.html> https://www.rfc-editor.org/authors/rfc9972.pdf> https://www.rfc-editor.org/authors/rfc9972.txt> > Diff file of the text:> https://www.rfc-editor.org/authors/rfc9972-diff.html> https://www.rfc-editor.org/authors/rfc9972-rfcdiff.html (side by side)> > Diff of the XML:> https://www.rfc-editor.org/authors/rfc9972-xmldiff1.html> > > Tracking progress> -----------------> > The details of the AUTH48 status of your document are here:> https://www.rfc-editor.org/auth48/rfc9972> > Please let us know if you have any questions.> > Thank you for your cooperation,> > RFC Editor> > --------------------------------------> RFC9972 (draft-ietf-grow-bmp-bgp-rib-stats-17)> > Title : Advanced BGP Monitoring Protocol (BMP) Statistics Types> Author(s) : M. Srivastava, Ed., Y. Liu, C. Lin, Ed., J. Li> WG Chair(s) : Paolo Lucente, Job Snijders> > Area Director(s) : Mohamed Boucadair, Mahesh Jethanandani> > > -------------------------------------------------------------------------------------------------------------------------------------> 本邮件及其附件含有新华三集团的保密信息，仅限于发送给上面地址中列出的个人或群组。> 禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。> 如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！> 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!
-- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
