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

Qin Wu <bill.wu@huawei.com> Sat, 24 February 2024 08:36 UTC

Return-Path: <bill.wu@huawei.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 00290C180B58; Sat, 24 Feb 2024 00:36:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 ATk3-xTNS7Qv; Sat, 24 Feb 2024 00:36:23 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0005DC180B57; Sat, 24 Feb 2024 00:36:22 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Thg941pnqz6K651; Sat, 24 Feb 2024 16:32:08 +0800 (CST)
Received: from lhrpeml100006.china.huawei.com (unknown [7.191.160.224]) by mail.maildlp.com (Postfix) with ESMTPS id E9DD3141069; Sat, 24 Feb 2024 16:36:19 +0800 (CST)
Received: from canpemm500007.china.huawei.com (7.192.104.62) by lhrpeml100006.china.huawei.com (7.191.160.224) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Sat, 24 Feb 2024 08:36:19 +0000
Received: from canpemm500005.china.huawei.com (7.192.104.229) by canpemm500007.china.huawei.com (7.192.104.62) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Sat, 24 Feb 2024 16:36:17 +0800
Received: from canpemm500005.china.huawei.com ([7.192.104.229]) by canpemm500005.china.huawei.com ([7.192.104.229]) with mapi id 15.01.2507.035; Sat, 24 Feb 2024 16:36:17 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Roland.Schott@telekom.de" <Roland.Schott@telekom.de>, "opsawg@ietf.org" <opsawg@ietf.org>, "nmop@ietf.org" <nmop@ietf.org>
Thread-Topic: [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg-incident-management-04
Thread-Index: Adpm+uY00As8MAOlS8S3fThwyaXS+Q==
Date: Sat, 24 Feb 2024 08:36:17 +0000
Message-ID: <99622cf3c5f04aa59c63951fe5a2a711@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.118.68]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/qYaeUvU8QMaACPL8sB1JJCJ_53k>
Subject: Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg-incident-management-04
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: Sat, 24 Feb 2024 08:36:27 -0000

Thanks Roland for your support.
I have noted down your comment in the github issue tracker
https://github.com/billwuqin/network-incident/issues/6
I can see two key differences:
1. draft feng-opsawg- focus on "network as a service" interface while draft-netana-opsawg-nmrg-network-anomaly-semantics is more related to telemetry interface
2. draft feng-opsawg focus on abstraction of network anomaly and performance data, other various data such log data, why draft--netana-opsawg-nmrg-network focus on correlating symptom data with incident data,
  Note that draft--netana-opsawg-nmrg-network references feng-opsawg for the term "incident".
Therefore my first impression they are complementary. Yes we will discuss align between two drafts, thanks for bringing this up earlier.

-Qin
-----邮件原件-----
发件人: OPSAWG [mailto:opsawg-bounces@ietf.org] 代表 Roland.Schott@telekom.de
发送时间: 2024年2月22日 2:54
收件人: opsawg@ietf.org
主题: Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg-incident-management-04

Hi,

regarding the adoption of the draft as WG item, I think this is a good idea to work on.

I have in mind that there has been the aim align the ietf-incident-semantic-metadata.yang with draft-feng-opsawg-incident-management.
In case this has not been done so far, I suggest having a look into this. 
This could be done after the adoption of the draft. 

Best Regards

Roland



-----Ursprüngliche Nachricht-----
Von: Henk Birkholz <henk.birkholz@ietf.contact> 
Gesendet: Donnerstag, 8. Februar 2024 16:44
An: OPSAWG <opsawg@ietf.org>
Betreff: [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
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg