Hi Med, Thank you for your reply and additional feedback! We have updated the document accordingly. Please see comments inline.
1) For (2), > (2) There are actually no messages shown in that figure > > CURRENT: > Syslog consists of originators and collectors. The following diagram > shows syslog messages flowing from originators to collectors where > filtering can take place. Would the solution be to remove this sentence entirely? Or should it be replaced with new text (i.e., replace "syslog messages" with "syslog processing flow" per the title of Figure 1)? Perhaps: Syslog consists of originators and collectors. The following diagram shows the syslog processing flow from originators to collectors where filtering can take place. 2) For (3), > (3) Stale/Redundant text: > > CURRENT: > A syslog message is processed if: > > A syslog message is processed if there is an element > of facility-list (F, S) where > the message facility matches F, > the message severity matches S, > and/or the message text matches the regex pattern (if it > is present) > > I guess one of "A syslog message is processed if" mentions should be deleted. We have removed the first instance of "A syslog message is processed if" (outside of the sourcecode element). 3) Regarding the following: > (5) Normative references > > I see that RFC9000 is added as a normative reference, while this should. > Please refer to RFC8407bis which has the guidance to follow here: > > Note: [RFC8341] (or a future RFC that replaces it) MUST be listed as > normative references. > > By default, [RFC4252], [RFC6241], [RFC8040], [RFC8446], [RFC9000], > and RFC AAAA (or future RFCs that replace any of them) are listed > as informative references unless normatively cited in other > sections of the document that specifies the YANG module. > > Please update the references accordingly. Thank you for pointing this out. We have removed RFC 8407 as a normative reference and replaced it with rfc8407bis as an informative reference. Let us know if this was your intention. Please review the updates and let us know if you approve as AD. Updated files (please refresh): https://www.rfc-editor.org/authors/rfc9742.txt https://www.rfc-editor.org/authors/rfc9742.pdf https://www.rfc-editor.org/authors/rfc9742.html https://www.rfc-editor.org/authors/rfc9742.xml Updated diffs: https://www.rfc-editor.org/authors/rfc9742-diff.html https://www.rfc-editor.org/authors/rfc9742-rfcdiff.html (side by side) https://www.rfc-editor.org/authors/rfc9742-auth48diff.html https://www.rfc-editor.org/authors/rfc9742-auth48rfcdiff.html (side by side) AUTH48 status page: https://www.rfc-editor.org/auth48/rfc9742 Thank you! RFC Editor/mc > Thank you. > > Cheers, > Med > >> -----Message d'origine----- >> De : Warren Kumari <war...@kumari.net> >> Envoyé : mercredi 16 avril 2025 23:11 >> À : Madison Church <mchu...@staff.rfc-editor.org>; BOUCADAIR >> Mohamed INNOV/NET <mohamed.boucad...@orange.com> >> Cc : Clyde Wildes <cl...@clydewildes.com>; Joe Clarke >> <jcla...@cisco.com>; Mahesh Jethanandani <mjethanand...@gmail.com>; >> kirankoushik.agraharasreeniv...@verizonwireless.com; RFC Editor >> <rfc-edi...@rfc-editor.org>; netmod-...@ietf.org; netmod- >> cha...@ietf.org; kwat...@juniper.net; auth48archive@rfc-editor.org >> Objet : Re: [AD] Re: AUTH48: RFC-to-be 9742 <draft-ietf-netmod- >> syslog-model-33> for your review >> >> >> [ + Med ] >> I believe that this is fine (and good!), but I'm adding Med as the >> current OpsAD for formal approval. >> >> W >> >> >> >> On Mon, Apr 14, 2025 at 11:22 AM, Madison Church < >> mchu...@staff.rfc-editor.org> wrote: >> >>> Hi Authors, *Warren, >>> >>> Authors - Thank you for your replies! We have noted your >> approvals on >>> the >>> AUTH48 status page (see >> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw >> ww.rfc- >> editor.org%2Fauth48%2Frfc9742&data=05%7C02%7Cmohamed.boucadair%40or >> ange.com%7Cc4750c63c69b4233fa7308dd7d2b2e13%7C90c7a20af34b40bfbc48b >> 9253b6f5d20%7C0%7C0%7C638804346604693219%7CUnknown%7CTWFpbGZsb3d8ey >> JFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiT >> WFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=iRZmIw5I9I0eRbpibi31LQ4v >> ntlD8CuvurIISw6c%2Bmc%3D&reserved=0). >>> >>> *Warren - As Responsible AD for this document, please review and >>> approve the following addition to the Normative References as per >>> https:// datatracker.ietf.org/doc/ >>> statement-iesg-guidelines-for-the-use-of-formal-languages-in- >> ietf-specifications-20011001/. >>> >>> >>> [W3C.REC-xml-20081126] >>> Bray, T., Paoli, J., Sperberg-McQueen, C.M., Maler, E., and F. >>> Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth Edition)", >> World >>> Wide Web Consortium Recommendation REC-xml-20081126, November >> 2008, >>> >> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.w3.org%2FTR%2F2008%2FREC-xml- >> 20081126%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Cc4750c6 >> 3c69b4233fa7308dd7d2b2e13%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C >> 0%7C638804346604708447%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRy >> dWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ% >> 3D%3D%7C0%7C%7C%7C&sdata=Hc2wzZ4k%2F8d4MsQFCKpn7Xri9NWLvM%2FRSlty3G >> qUTDM%3D&reserved=0>. >>> >>> Thank you, >>> RFC Editor/mc >>> >>> On Apr 13, 2025, at 2:00 PM, Clyde Wildes <cl...@clydewildes.com> >> wrote: >>> >>> Madison, >>> >>> Approved from me! >>> >>> Thanks, >>> >>> Clyde >>> >>> On Mar 19, 2025, at 8:56 AM, Madison Church >>> <mchu...@staff.rfc-editor.org> >>> wrote: >>> >>> Hi Authors, >>> >>> Joe - Thank you for your reply! We have updated the document as >>> requested > ____________________________________________________________________________________________________________ > 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. -- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
