Greetings, All approvals have been received, and we will continue with the publication process at this time.
Thank you. Alice Russo RFC Production Center On Thu, Mar 12, 2026 at 4:51 AM Davis, Nigel <[email protected]> wrote: > > Apologies for the delay, I also approve. > > Kind regards, > > Nigel > > -----Original Message----- > From: Qin Wu <[email protected]> > Sent: 09 March 2026 23:51 > To: Alice Russo <[email protected]>; Davis, Nigel <[email protected]> > Cc: Adrian Farrel <[email protected]>; Thomas.Graf > <[email protected]>; yuchaode <[email protected]>; > [email protected]; [email protected]; Mahesh Jethanandani > <[email protected]>; [email protected]; auth48archive > <[email protected]>; RFC Editor <[email protected]> > Subject: [**EXTERNAL**] RE: AUTH48: RFC-to-be 9940 > <draft-ietf-nmop-terminology-23> for your review > > Hi, Alice: > The latest version looks good, I approve publication of this document. Thanks. > > -Qin > -----邮件原件----- > 发件人: Alice Russo [mailto:[email protected]] > 发送时间: 2026年3月10日 4:16 > 收件人: [email protected]; Qin Wu <[email protected]> > 抄送: Adrian Farrel <[email protected]>; [email protected]; yuchaode > <[email protected]>; [email protected]; [email protected]; Mahesh > Jethanandani <[email protected]>; [email protected]; > auth48archive <[email protected]>; RFC Editor > <[email protected]> > 主题: Re: AUTH48: RFC-to-be 9940 <draft-ietf-nmop-terminology-23> for your > review > > Nigel, Qin, > > This is a reminder that we await word from you regarding this document's > readiness for publication as an RFC. The files are here: > > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9940.html__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-tpF4sm6kYrdjMQi1yIH7H_5VP8mTnEiym$ > [rfc-editor[.]org] > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9940.pdf__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-tpF4sm6kYrdjMQi1yIH7H_5VP8nXKKWOg$ > [rfc-editor[.]org] > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9940.txt__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-tpF4sm6kYrdjMQi1yIH7H_5VP8pKqaSNc$ > [rfc-editor[.]org] > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9940.xml__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-tpF4sm6kYrdjMQi1yIH7H_5VP8tGlb1u7$ > [rfc-editor[.]org] (source) > > Diff files of all changes from the approved Internet-Draft: > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9940-diff.html__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-tpF4sm6kYrdjMQi1yIH7H_5VP8nA9Zok7$ > [rfc-editor[.]org] > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9940-rfcdiff.html__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-tpF4sm6kYrdjMQi1yIH7H_5VP8iQAmzbb$ > [rfc-editor[.]org] (side by side) > > Diff file of AUTH48 changes only: > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9940-auth48diff.html__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-tpF4sm6kYrdjMQi1yIH7H_5VP8v9OyfMb$ > [rfc-editor[.]org] > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9940-auth48rfcdiff.html__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-tpF4sm6kYrdjMQi1yIH7H_5VP8iOO9hqN$ > [rfc-editor[.]org] (side by side) > > This page shows the AUTH48 status of your document: > > https://urldefense.com/v3/__https://www.rfc-editor.org/auth48/rfc9940__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-tpF4sm6kYrdjMQi1yIH7H_5VP8oWHob4K$ > [rfc-editor[.]org] > > Thank you. > > Alice Russo > RFC Production Center > > > On Feb 23, 2026, at 6:27 PM, [email protected] wrote: > > > > *****IMPORTANT***** > > > > Updated 2026/02/23 > > > > 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://urldefense.com/v3/__https://www.rfc-editor.org/faq/__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-tpF4sm6kYrdjMQi1yIH7H_5VP8hqsCLRr$ > > [rfc-editor[.]org]). > > > > 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: > > > > <!-- [rfced] ... --> > > > > 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://urldefense.com/v3/__https://trustee.ietf.org/license-info__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-tpF4sm6kYrdjMQi1yIH7H_5VP8u-mAiZ9$ > > [trustee[.]ietf[.]org]). > > > > * Semantic markup > > > > Please review the markup in the XML file to ensure that elements of > > content are correctly tagged. For example, ensure that <sourcecode> > > and <artwork> are set correctly. See details at > > > > <https://urldefense.com/v3/__https://authors.ietf.org/rfcxml-vocabulary__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-tpF4sm6kYrdjMQi1yIH7H_5VP8g-n48CK$ > > [authors[.]ietf[.]org]>. > > > > * 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://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/ietf > > -announce/yb6lpIGh-4Q9l2USxI__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQ > > whil5JoVi6zP-tpF4sm6kYrdjMQi1yIH7H_5VP8l7jdHxB$ > > [mailarchive[.]ietf[.]org] Ae6P8O4Zc > > > > * The archive itself: > > > > https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/browse/a > > uth48archive/__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-tp > > F4sm6kYrdjMQi1yIH7H_5VP8pC8tSCd$ [mailarchive[.]ietf[.]org] > > > > * 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://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9940.xml__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-tpF4sm6kYrdjMQi1yIH7H_5VP8tGlb1u7$ > > [rfc-editor[.]org] > > > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9940.html__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-tpF4sm6kYrdjMQi1yIH7H_5VP8mTnEiym$ > > [rfc-editor[.]org] > > > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9940.pdf__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-tpF4sm6kYrdjMQi1yIH7H_5VP8nXKKWOg$ > > [rfc-editor[.]org] > > > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9940 > > .txt__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-tpF4sm6kYrd > > jMQi1yIH7H_5VP8pKqaSNc$ [rfc-editor[.]org] > > > > Diff file of the text: > > > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9940-diff.html__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-tpF4sm6kYrdjMQi1yIH7H_5VP8nA9Zok7$ > > [rfc-editor[.]org] > > > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9940 > > -rfcdiff.html__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-tp > > F4sm6kYrdjMQi1yIH7H_5VP8iQAmzbb$ [rfc-editor[.]org] (side by > > side) > > > > Diff of the XML: > > > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9940 > > -xmldiff1.html__;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-t > > pF4sm6kYrdjMQi1yIH7H_5VP8iMurvDW$ [rfc-editor[.]org] > > > > > > Tracking progress > > ----------------- > > > > The details of the AUTH48 status of your document are here: > > > > https://urldefense.com/v3/__https://www.rfc-editor.org/auth48/rfc9940_ > > _;!!OSsGDw!NnGU8r5ue2JLD63kGhi1bgwF_cQtOQwhil5JoVi6zP-tpF4sm6kYrdjMQi1 > > yIH7H_5VP8oWHob4K$ [rfc-editor[.]org] > > > > Please let us know if you have any questions. > > > > Thank you for your cooperation, > > > > RFC Editor > > > > -------------------------------------- > > RFC9940 (draft-ietf-nmop-terminology-23) > > > > Title : Some Key Terms for Network Fault and Problem Management > > Author(s) : N. Davis, Ed., A. Farrel, Ed., T. Graf, Q. Wu, C. Yu > > WG Chair(s) : Benoît Claise, Reshad Rahman > > Area Director(s) : Mohamed Boucadair, Mahesh Jethanandani > > > -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
