Hi Franck, all, 

Thank you for initiating this work. Please find some comments, fwiw: 

(1) The document overstates what it achieves. I would soften many of these 
statements. For example, It would be helpful to discuss whether the approach 
eases the identification of root causes and their mitigation.
(2) Rather than opposing the alarm model with what is specified in this 
document, I would instead better articulate and highlight how they complement 
each other.
(3) The network service aspect is not highlighted as I was expecting from the 
title/abstract. For example, I was expecting to see a discussion how 
service-specific incidents are tagged/characterized and then reported. The 
current discussion is mostly device-centric.
(4) Consider positioning this work in the context of the automation framework 
in RFC8969. Likewise, call out potential interactions with the TMF incident API.
(5) You may also position this work vs. the service assurance work led by 
Benoît. I don’t see conflict between both, but it is better to discuss that in 
the draft.

Hope this helps. 

Cheers,
Med

> -----Message d'origine-----
> De : OPSAWG <[email protected]> De la part de Fengchong
> (frank)
> Envoyé : lundi 13 mars 2023 14:19
> À : [email protected]
> Objet : [OPSAWG] 转发: New Version Notification for draft-feng-
> opsawg-incident-management-00.txt
> 
> Hi all,
>   I submit a new draft about incident management for network
> service. Includes:
>     1. The concept and architecture of Incident management.
>     2. The incident lifecycle management.
>     3. The YANG model for incident management.
> 
>   Please give your comments. Thanks.
> 
>   Best Regards,
>   Frank
> 
> -----邮件原件-----
> 发件人: [email protected] <[email protected]>
> 发送时间: 2023年3月13日 21:06
> 收件人: yuchaode <[email protected]>; Fengchong (frank)
> <[email protected]>; Luis Contreras
> <[email protected]>; Luis Miguel
> Contreras Murillo <[email protected]>;
> Qin Wu <[email protected]>; Qin Wu <[email protected]>; Tong Hu
> <[email protected]>
> 主题: New Version Notification for draft-feng-opsawg-incident-
> management-00.txt
> 
> 
> A new version of I-D, draft-feng-opsawg-incident-management-00.txt
> has been successfully submitted by Chong Feng and posted to the
> IETF repository.
> 
> Name:         draft-feng-opsawg-incident-management
> Revision:     00
> Title:                Incident Management for Network Services
> Document date:        2023-03-13
> Group:                Individual Submission
> Pages:                35
> URL:            https://www.ietf.org/archive/id/draft-feng-opsawg-
> incident-management-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-feng-
> opsawg-incident-management/
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-feng-
> opsawg-incident-management
> 
> 
> Abstract:
>    This document provides an architecture for the incident
> management
>    system and related function interface requirements.
> 
>    This document also defines a YANG module to support the
> incident
>    lifecycle management.  This YANG module is meant to provide a
>    standard way to report, diagnose, and resolve incidents for the
> sake
>    of enhanced network services.
> 
> 
> 
> 
> The IETF Secretariat
> 
> 
> 
> _______________________________________________
> OPSAWG mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/opsawg

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg

Reply via email to