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

Alex Huang Feng <alex.huang-feng@insa-lyon.fr> Tue, 13 February 2024 05:24 UTC

Return-Path: <alex.huang-feng@insa-lyon.fr>
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 22EB1C15109A for <opsawg@ietfa.amsl.com>; Mon, 12 Feb 2024 21:24:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.463
X-Spam-Level:
X-Spam-Status: No, score=0.463 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_HELO_IP_MISMATCH=2.368, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-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=no 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 Ez4YHQQUH1gV for <opsawg@ietfa.amsl.com>; Mon, 12 Feb 2024 21:24:52 -0800 (PST)
Received: from smtpout01-ext2.partage.renater.fr (smtpout01-ext2.partage.renater.fr [194.254.240.33]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B164C14F6F0 for <opsawg@ietf.org>; Mon, 12 Feb 2024 21:24:51 -0800 (PST)
Received: from zmtaauth03.partage.renater.fr (zmtaauth03.partage.renater.fr [194.254.240.26]) by smtpout10.partage.renater.fr (Postfix) with ESMTP id 202216488B; Tue, 13 Feb 2024 06:24:48 +0100 (CET)
Received: from zmtaauth03.partage.renater.fr (localhost [127.0.0.1]) by zmtaauth03.partage.renater.fr (Postfix) with ESMTPS id 19AAD80017; Tue, 13 Feb 2024 06:24:48 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by zmtaauth03.partage.renater.fr (Postfix) with ESMTP id 14C8B80139; Tue, 13 Feb 2024 06:24:48 +0100 (CET)
Received: from zmtaauth03.partage.renater.fr ([127.0.0.1]) by localhost (zmtaauth03.partage.renater.fr [127.0.0.1]) (amavis, port 10026) with ESMTP id B9ov0oLfxbgL; Tue, 13 Feb 2024 06:24:48 +0100 (CET)
Received: from 150.100.50.67 (unknown [194.254.241.251]) by zmtaauth03.partage.renater.fr (Postfix) with ESMTPA id 1870980017; Tue, 13 Feb 2024 06:24:46 +0100 (CET)
From: Alex Huang Feng <alex.huang-feng@insa-lyon.fr>
Message-Id: <8C56A5ED-909F-4DE4-BFEA-91954035D56C@insa-lyon.fr>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D4ABD378-227A-4B8F-943C-5340BB4B7BCA"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
Date: Tue, 13 Feb 2024 14:24:34 +0900
In-Reply-To: <fecb3c52-493c-436e-78fc-7d3cdc13e43c@ietf.contact>
Cc: OPSAWG <opsawg@ietf.org>
To: Henk Birkholz <henk.birkholz@ietf.contact>
References: <fecb3c52-493c-436e-78fc-7d3cdc13e43c@ietf.contact>
X-Mailer: Apple Mail (2.3731.700.6)
X-Virus-Scanned: clamav-milter 0.103.8 at clamav02
X-Virus-Status: Clean
X-Renater-Ptge-SpamState: clean
X-Renater-Ptge-SpamScore: -100
X-Renater-Ptge-SpamCause: gggruggvucftvghtrhhoucdtuddrgedvledrudeggdekhecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucftgffptefvgfftnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefhkfgtggfuffgjvefvfhfosegrtdhmrehhtdejnecuhfhrohhmpeetlhgvgicujfhurghnghcuhfgvnhhguceorghlvgigrdhhuhgrnhhgqdhfvghnghesihhnshgrqdhlhihonhdrfhhrqeenucggtffrrghtthgvrhhnpeekgeegveetffeitdeuueekudeivdevheefledthfeiteektefghfekgedthfehfeenucffohhmrghinhepihgvthhfrdhorhhgnecukfhppeduleegrddvheegrddvgedurddvhedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepudelgedrvdehgedrvdeguddrvdehuddphhgvlhhopeduhedtrddutddtrdehtddrieejpdhmrghilhhfrhhomheptehlvgigucfjuhgrnhhgucfhvghnghcuoegrlhgvgidrhhhurghnghdqfhgvnhhgsehinhhsrgdqlhihohhnrdhfrheqpdhnsggprhgtphhtthhopedvpdhrtghpthhtohephhgvnhhkrdgsihhrkhhhohhliiesihgvthhfrdgtohhnthgrtghtpdhrtghpthhtohepohhpshgrfihgsehivghtfhdrohhrgh
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/9_I1rZXAPPh-cyTWpjHOh4OumA8>
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: Tue, 13 Feb 2024 05:24:55 -0000

Dear OPSAWG,

I support the progress of this document.

I only have a comment. Since the creation of the new NMOP WG, I wonder if this draft should be discussed in that WG too. There is “incident management” in the charter.
Some of the related work such as https://datatracker.ietf.org/doc/draft-davis-nmop-incident-terminology/ is planned to be discussed there.
Just wondering.

Regards,
Alex

> On 9 Feb 2024, at 00:44, Henk Birkholz <henk.birkholz@ietf.contact> wrote:
> 
> 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