Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg-incident-management-04

["Joe Clarke (jclarke)" <[e-mail]>]

=== As a contributor ===

I struggle to see why the IETF should be working on this.  Clearly there are other SDOs that work in the area of incident management.  This draft refers to a [IMHO tenuous] reference to a TM Forum API spec (which I cannot read as I am not a member), but ITIL has similar definitions of incidents and problems.  There does not seem to be any liaison or indication of a close relationship with these other SDOs to help drive consistent use of terminology and help their members achieve desired goals.

Even in this first pass, I see what I feel is a mix of terminology.  You have an enumeration on leaf type where “fault” reads as the type of incident being a fault.  To me, this is the type of problem (i.e., the cause of the incident).  The incident type might be an SLA violation.

I do not feel this work should be adopted by the IETF in its current form.

Joe

From: OPSAWG <[e-mail]> on behalf of Henk Birkholz <[e-mail]>
Date: Thursday, February 8, 2024 at 10:44
To: OPSAWG <[e-mail]>
Subject: [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg-incident-management-04
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
[e-mail]
https://www.ietf.org/mailman/listinfo/opsawg