All,
At the side meeting in Prague, Nigel and I committed to putting together a
first stab at a terminology set for network incidents. We have now posted a
-00 draft.
The intentions here are:
* To provide a starting point for discussions of the terminology
* To give something that can be edited and made correct
* To end up with a set of terms that we can agree upon and use in all
of our work
We would be shocked if we have got this right on our first pass. We are sure
that there will be many opinions, and we welcome suggestions for edits and
proposals for changes.
Although this email is circulated quite widely (including OPSAWG, NMRG, and
NMOP (still masquerading as NETMO)), we believe that this work will end up
in NMOP (if the WG is ever formed) and so we suggest that all responses and
discussions be directed exclusively to the NETMO mailing list.
Looking forward to a fruitful debate,
Nigel and Adrian
===
Internet-Draft draft-davis-nmop-incident-terminology-00.txt is now
available.
Title: Some Key Terms for Incident Management
Authors: Nigel Davis
Adrian Farrel
Name: draft-davis-nmop-incident-terminology-00.txt
Pages: 5
Dates: 2024-01-18
Abstract:
This document sets out some key terms that are fundamental to a
common understanding of Incident Management.
The purpose of this document is to bring clarity to discussions and
other work related to Incident Management in particular YANG models
and management protocols that report, make visible, or manage
incidents.
The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-davis-nmop-incident-terminology/
There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-davis-nmop-incident-terminology-00.htm
l
_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
