Dear OPSAWG, I support the progress of this document.
I only have a comment. Since the creation of the new NMOP WG, I wonder if this draft should be discussed in that WG too. There is βincident managementβ in the charter. Some of the related work such as https://datatracker.ietf.org/doc/draft-davis-nmop-incident-terminology/ is planned to be discussed there. Just wondering. Regards, Alex > On 9 Feb 2024, at 00:44, Henk Birkholz <henk.birkholz@ietf.contact> wrote: > > Dear OPSAWG members, > > this email starts a call for Working Group Adoption of > >> https://www.ietf.org/archive/id/draft-feng-opsawg-incident-management-04.html > > ending on Thursday, February 22nd. > > As a reminder, this I-D specifies a YANG Module for Incident Management. > Incidents in this context are scoped to unexpected yet quantifiable adverse > effects detected in a network service. The majority of the document provides > background and motivation for the structure of the YANG Module that is in > support of reporting, diagnosing, and mitigating the detected adverse effects. > > The chairs acknowledge some positive feedback on the list and a positive poll > result at IETF118. We would like to gather feedback from the WG if there is > interest to further contribute and review. > > Please reply with your support and especially any substantive comments you > may have. > > > For the OPSAWG co-chairs, > > Henk > > _______________________________________________ > OPSAWG mailing list > OPSAWG@ietf.org > https://www.ietf.org/mailman/listinfo/opsawg
_______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
