Hi Benoît, all, Thanks for starting this. Please find below some comments:
(1) I think that we need to have text to formally endorse the dispatch function for the ops area. (2) I would simplify this part as the message seems to be redundant: "The OPSAWG will serve as the forum for developing such work items in the IETF. The OPSAWG mailing list is an open discussion forum for such work items when they arise." (3) Please remove OPS from this sentence "...don't otherwise belong to another OPS Working Group" as there are ops-related topics in non-ops area (e.g. transport matters in tsvwg). (4) Don't know what is meant by "small-scale extensions". May be we want to say "minor extensions"? (5) I would also cite service models, not only "network-level YANG modules" (6) please clear the current two milestones Cheers, Med > -----Message d'origine----- > De : Benoit Claise <benoit.claise=40huawei....@dmarc.ietf.org> > Envoyé : jeudi 20 mars 2025 11:33 > À : opsawg <opsawg@ietf.org> > Objet : [OPSAWG]OPSAWG recharrting > > > Dear all, > > Even if the OPSAWG has been running smoothy for years and producing > useful RFCs along the way, it's the obvious fact that the charter text > needed an update. For example, stressing MIB developments and showing > 2012/2013 milestones might be misleading to the newcomers. > Note: providing a newcomer training this Sunday, I heard myself saying > "the first thing you have to do to evaluate whether your work applies > is to read the charter" while a second internal voice was telling me > "be consistent here and update the OPSAWG you xxx" ;-) > > Discussing with our AD, we came up with a new proposed OPSAWG charter > text. > Interestingly, it resulted in much text simplification. > > Please review > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdata > tracker.ietf.org%2Fdoc%2Fcharter-ietf-opsawg%2F04- > 02%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Ceff099a17c73417d > a0c708dd676868db%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C63878042 > 0340712713%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjA > uMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C > &sdata=b6k4dRGt29rxAhrX5rnl5SUBcEgghzI77FRDsp%2FkRpg%3D&reserved=0 > Your feedback is welcome. > > Regards, Mahesh, Joe, and Benoit > > _______________________________________________ > OPSAWG mailing list -- opsawg@ietf.org > To unsubscribe send an email to opsawg-le...@ietf.org ____________________________________________________________________________________________________________ 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. _______________________________________________ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org
