Re: [OPSAWG] New Version Notification for draft-feng-opsawg-incident-management-00.txt

mohamed.boucadair@orange.com Tue, 21 March 2023 08:02 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B766DC19E11B for <opsawg@ietfa.amsl.com>; Tue, 21 Mar 2023 01:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.796
X-Spam-Level:
X-Spam-Status: No, score=-2.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mXQysRxwTmtN for <opsawg@ietfa.amsl.com>; Tue, 21 Mar 2023 01:02:14 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AF4FC14F747 for <opsawg@ietf.org>; Tue, 21 Mar 2023 01:02:14 -0700 (PDT)
Received: from opfedar07.francetelecom.fr (unknown [xx.xx.xx.9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar21.francetelecom.fr (ESMTP service) with ESMTPS id 4PgkbS3L39z7tXZ; Tue, 21 Mar 2023 09:02:12 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1679385732; bh=doKgP85zuE3zDCQcgx9QxyahcnSYzhoSmPu47Iv+sOY=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=px6DIlsoGcCW/IU3QlRXiMtAPVntsP3x+6apBnMRYFb78IHOuKs0t5U9CwmyNpU95 2hiR1ZqOE73dfspGB0naCZHghLYkBplHq8jVv1Kv+6H6GKH0Je/EWGGDhcQc1ahItZ setJ2sFzrQejBk+mvsaUL9SFN+GAHNsQ/UHT2Q0y+7VCi/sPdUsWDq/DNL2NqxVGQ6 raOIE6OEZHmkuC2kseUkKhDThBUQgBBpSLpKWeQPpKLRP2Da3fDNT9nkhV8vVnRooL wVQq2+nBvH5YSj09mY3TkhtQrqJ/nl1Zjsci+N93FWtiySJH97BaHEZQg4SryS7UUt hgWodELeoP1Tw==
From: mohamed.boucadair@orange.com
To: "Fengchong (frank)" <frank.fengchong=40huawei.com@dmarc.ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: New Version Notification for draft-feng-opsawg-incident-management-00.txt
Thread-Index: AQHZVay995Qn/SVoJEegMbqmk5ZuNK74rpuggAw5nOA=
Content-Class:
Date: Tue, 21 Mar 2023 08:02:11 +0000
Message-ID: <1962_1679385732_64196484_1962_91_1_5143d85004f643ebbc914100876bdf14@orange.com>
References: <167871278004.23750.7420104506801536650@ietfa.amsl.com> <1fc9900b185a432a968e5e8ac61ea34d@huawei.com>
In-Reply-To: <1fc9900b185a432a968e5e8ac61ea34d@huawei.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2023-03-21T07:50:25Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=5b1012c0-7d2d-4d80-9e3c-db2936aade4c; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.115.27.51]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/wP0W_E4uzjXAZ-MVxGWta25vg9o>
Subject: Re: [OPSAWG] New Version Notification for draft-feng-opsawg-incident-management-00.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Mar 2023 08:02:18 -0000

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 <opsawg-bounces@ietf.org> De la part de Fengchong
> (frank)
> Envoyé : lundi 13 mars 2023 14:19
> À : opsawg@ietf.org
> 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
> 
> -----邮件原件-----
> 发件人: internet-drafts@ietf.org <internet-drafts@ietf.org>
> 发送时间: 2023年3月13日 21:06
> 收件人: yuchaode <yuchaode@huawei.com>; Fengchong (frank)
> <frank.fengchong@huawei.com>; Luis Contreras
> <luismiguel.contrerasmurillo@telefonica.com>; Luis Miguel
> Contreras Murillo <luismiguel.contrerasmurillo@telefonica.com>;
> Qin Wu <bill.wu@huawei.com>; Qin Wu <bill.wu@huawei.com>; Tong Hu
> <hutong@cmhi.chinamobile.com>
> 主题: 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
> OPSAWG@ietf.org
> 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.