[Adding the NMOP list - which is currently called NETMO]
It's a month later. Nigel and I have been working on the first version of key terminology. We've actually made some progress (perhaps slower than our initial enthusiasm might have suggested). We're just putting the last polish on our first version that we intent to share "soon." Cheers, Adrian From: OPSAWG <[email protected]> On Behalf Of Qin Wu Sent: 10 November 2023 07:46 To: [email protected] Cc: [email protected]; [email protected]; [email protected] Subject: [OPSAWG] Network Incident Management Side Meeting Summary Hi, All: Thanks all folks who participated in network incident management discussion on Tuesday afternoon. The side meeting was spent one hour exploring network incident concepts and use cases; three related drafts were discussed. We received a lot of great contributions for the following drafts being discussed: https://datatracker.ietf.org/doc/draft-feng-opsawg-incident-management/ (Service Level Incident) https://datatracker.ietf.org/doc/draft-opsawg-evans-discardmodel/ (Anomaly Detection, Correlation and Mitigation for Packet Discard) https://datatracker.ietf.org/doc/draft-netana-opsawg-nmrg-network-anomaly-se mantics/ (Network anomaly semantics) It was identified that multi-layer Fault Demarcation is related to POI, however the network incident model can be defined as generic model used for many other use cases. A few issues were raised in the meeting: 1. Network Incident definitions needs more clarity even though it origins from TMF specification, e.g., how it is related to symptom, anomaly, etc. 2. Besides SLO violation, how network incident is generated based on other factors, more usage examples are needed for these. 3. Incident terminology is well-defined and should be consistent across the drafts and, where possible, synced with other SDO meanings (although the language may vary) Follow up actions include: 1. Nigel and Adrian volunteered to help define key terminology uses and define terms; 2. Dan to check with MEF and TMF documentation to check for SLO handling, including incident and problem coordination and definitions; 3. Open the network incident draft GitHub to the public and use it for draft development and tracking issues. -Qin (on behalf of Team)
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
