<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.feng-opsawg-incident-management" target="https://datatracker.ietf.org/doc/html/draft-feng-opsawg-incident-management-04">
   <front>
      <title>Incident Management for Network Services</title>
      <author initials="C." surname="Feng" fullname="Chong Feng">
         </author>
      <author initials="T." surname="Hu" fullname="Tong Hu">
         <organization>China Mobile (Hangzhou) Information
      Technology Co., Ltd</organization>
      </author>
      <author initials="L. M." surname="Contreras" fullname="Luis M. Contreras">
         <organization>Telefonica I+D</organization>
      </author>
      <author initials="T." surname="Graf" fullname="Thomas Graf">
         <organization>Swisscom</organization>
      </author>
      <author initials="Q." surname="Wu" fullname="Qin Wu">
         <organization>Huawei</organization>
      </author>
      <author initials="C." surname="Yu" fullname="Chaode Yu">
         <organization>Huawei</organization>
      </author>
      <author initials="N." surname="Davis" fullname="Nigel Davis">
         <organization>Ciena</organization>
      </author>
      <date month="January" day="30" year="2024" />
      <abstract>
	 <t>   A network incident refers to an unexpected interruption of a network
   service, degradation of a network service quality, or sub-health of a
   network service.  Different data sources including alarms, metrics
   and other anomaly information can be aggregated into few amount of
   network incidents by data correlation analysis and the service impact
   analysis.

   This document defines YANG Modules for the network incident lifecycle
   management.  The YANG modules are meant to provide a standard way to
   report, diagnose, and resolve network incidents for the sake of
   network service health and root cause analysis.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-feng-opsawg-incident-management-04" />
   
</reference>
