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

Benoit Claise <benoit.claise@huawei.com> Thu, 29 February 2024 08:46 UTC

Return-Path: <benoit.claise@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 068E6C1519BB; Thu, 29 Feb 2024 00:46:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.296
X-Spam-Level:
X-Spam-Status: No, score=-4.296 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.091, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=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_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 yOOcqtqVo_iA; Thu, 29 Feb 2024 00:46:40 -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 9364CC14F60A; Thu, 29 Feb 2024 00:46:40 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Tll8K6jxYz6K5Xg; Thu, 29 Feb 2024 16:42:09 +0800 (CST)
Received: from frapeml500001.china.huawei.com (unknown [7.182.85.94]) by mail.maildlp.com (Postfix) with ESMTPS id 78E87140DAF; Thu, 29 Feb 2024 16:46:37 +0800 (CST)
Received: from [10.45.147.123] (10.45.147.123) by frapeml500001.china.huawei.com (7.182.85.94) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Thu, 29 Feb 2024 09:46:34 +0100
Message-ID: <eac4aa68-8d19-e7d3-e9ff-6b9a003dfe87@huawei.com>
Date: Thu, 29 Feb 2024 09:46:29 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1
Content-Language: en-US
To: Henk Birkholz <henk.birkholz@ietf.contact>, opsawg@ietf.org, nmop-chairs@ietf.org
References: <fecb3c52-493c-436e-78fc-7d3cdc13e43c@ietf.contact> <10b295f6-ab36-e244-1745-3a17a3ff78b9@ietf.contact>
From: Benoit Claise <benoit.claise@huawei.com>
In-Reply-To: <10b295f6-ab36-e244-1745-3a17a3ff78b9@ietf.contact>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.45.147.123]
X-ClientProxiedBy: dggems704-chm.china.huawei.com (10.3.19.181) To frapeml500001.china.huawei.com (7.182.85.94)
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/elWMOyK-0p4CxbZL3LkEIuC6Iow>
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: Thu, 29 Feb 2024 08:46:42 -0000

Dear OPSAWG co-chairs,

Thanks for this summary email. Much appreciated.
This draft will be presented in NMOP, in the context of "Anomaly 
detection and incident management" topic from the charter.

Regards, Benoit (NMOP co-chair)

On 2/29/2024 7:44 AM, Henk Birkholz wrote:
> Dear OPSAWG members,
>
> this email concludes the call for Working Group Adoption on 
> https://datatracker.ietf.org/doc/html/draft-feng-opsawg-incident-management-04.
>
> We received a significant amount of positive replies, a few elaborate 
> comments, and most importantly the notion that this work should be 
> considered for adoption in the NMOP WG.
>
> There were also a few concerns about access to some work by other 
> bodies that must be accounted in this I-D. Strong collaboration with 
> other bodies must happen to ensure terminology consistency (avoiding 
> the definition of subtly different or conflicting semantics).
>
> The OPSAWG chairs believe this I-D is ready for adoption. If the NMOP 
> chairs agree they can inherit the result of the WG adoption call or 
> issues a complementary one on the NMOP list, referring to the results 
> of this WG adoption call.
>
>
> For the OPSAWG co-chairs,
>
> Henk
>
> On 08.02.24 16:44, Henk Birkholz 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