Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg-incident-management-04
Benoit Claise <benoit.claise@huawei.com> Tue, 13 February 2024 09:31 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 7579CC14F609; Tue, 13 Feb 2024 01:31:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.993
X-Spam-Level:
X-Spam-Status: No, score=-1.993 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.091, RCVD_IN_DNSWL_BLOCKED=0.001, 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 CPbR2-84G3dV; Tue, 13 Feb 2024 01:31:09 -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 D26B5C14F5EC; Tue, 13 Feb 2024 01:31:08 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4TYwvf5MyRz6J9qZ; Tue, 13 Feb 2024 17:27:10 +0800 (CST)
Received: from frapeml500001.china.huawei.com (unknown [7.182.85.94]) by mail.maildlp.com (Postfix) with ESMTPS id 07285141F49; Tue, 13 Feb 2024 17:31:07 +0800 (CST)
Received: from [10.81.209.171] (10.81.209.171) by frapeml500001.china.huawei.com (7.182.85.94) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Tue, 13 Feb 2024 10:31:03 +0100
Content-Type: multipart/alternative; boundary="------------36SXNikyMzWKE6Yb2AkeCkLr"
Message-ID: <3c469751-802f-44a8-ad26-57d4681f1046@huawei.com>
Date: Tue, 13 Feb 2024 10:30:58 +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: adrian@olddog.co.uk, 'Alex Huang Feng' <alex.huang-feng@insa-lyon.fr>, nmop-chairs@ietf.org, opsawg-chairs@ietf.org, ops-ads@ietf.org
CC: 'OPSAWG' <opsawg@ietf.org>, nmop@ietf.org
References: <fecb3c52-493c-436e-78fc-7d3cdc13e43c@ietf.contact> <8C56A5ED-909F-4DE4-BFEA-91954035D56C@insa-lyon.fr> <091d01da5e5d$f35eb290$da1c17b0$@olddog.co.uk>
From: Benoit Claise <benoit.claise@huawei.com>
In-Reply-To: <091d01da5e5d$f35eb290$da1c17b0$@olddog.co.uk>
X-Originating-IP: [10.81.209.171]
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/dlxExAdMdIDmD5EFB11k3vNBUBg>
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 09:31:10 -0000
Hi Alex, Adrian, Let's check with Rob (I am on it) Regards, Benoit On 2/13/2024 10:20 AM, Adrian Farrel wrote: > > I am also as confused as Alex :-) > > The OPSAWG charter says: > > The Operations and Management Area receives occasional proposals for > the development and publication of RFCs dealing with operational and > management topics that are not in scope of an existing working group > > The NMOP charter is very clear that > > The current topics of focus for the working group are: > > * NETCONF/YANG Push integration with Apache Kafka & time series > databases > * Anomaly detection and incident management > > It also says: > > * Standardize YANG data models to solve operational issues identified in > the scope items above. YANG data models potentially within the scope > of other WGs will only be progressed here with agreement from the > relevant ADs. > > So, while I strongly support the IETF working on this draft, I am > confused about why it is being polled for adoption in OPSAWG rather > than NMOP. I appreciate that a lot of initial work has been done in > OPSAWG, but now that NMOP has been chartered we should attempt to keep > the lines clean. > > I’d ask that the chairs of both WGs and the ADs talk to each other and > give us direction on this as a matter of some urgency. > > Thanks, > > Adrian > > PS. Unlike Alex, I don’t think the solution is to discuss the document > in two WGs: that usually leads to interesting challenges > > *From:*OPSAWG <opsawg-bounces@ietf.org> *On Behalf Of *Alex Huang Feng > *Sent:* 13 February 2024 05:25 > *To:* Henk Birkholz <henk.birkholz@ietf.contact> > *Cc:* OPSAWG <opsawg@ietf.org> > *Subject:* Re: [OPSAWG] 🔔WG Adoption Call for > draft-feng-opsawg-incident-management-04 > > 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 >
- [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg… Henk Birkholz
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… chong feng
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Wei Wang
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Ziyang Xing
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… LUIS MIGUEL CONTRERAS MURILLO
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Qin Wu
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Aihua Guo
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Andrew L
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Italo Busi
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Alex Huang Feng
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Adrian Farrel
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Benoit Claise
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Henk Birkholz
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Rob Wilton (rwilton)
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… kaigao
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Jensen Zhang
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Joe Clarke (jclarke)
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Qin Wu
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Qin Wu
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Italo Busi
- [OPSAWG] 答复: 🔔 WG Adoption Call for draft-feng-op… yuchaode
- Re: [OPSAWG] WG Adoption Call for draft-feng-op… 赵星
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… hutong
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Davis, Nigel
- Re: [OPSAWG] WG Adoption Call for draft-feng-op… li_zhenqiang@hotmail.com
- Re: [OPSAWG] WG Adoption Call for draft-feng-op… duzongpeng@foxmail.com
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Michael Richardson
- Re: [OPSAWG] WG Adoption Call for draft-feng-op… Meiling Chen
- Re: [OPSAWG] WG Adoption Call for draft-feng-op… liupengyjy@outlook.com
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Joe Clarke (jclarke)
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Henk Birkholz
- Re: [OPSAWG] [警惕!外部邮件]转发:WG Adoption Call fordra… 郑滟雷(联通集团本部)
- Re: [OPSAWG] 转发: WG Adoption Call for draft-fen… xuyunbin@caict.ac.cn
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Roland.Schott
- Re: [OPSAWG] WG Adoption Call for draft-feng-op… Qin Wu
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Qin Wu
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Qin Wu
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Henk Birkholz
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Benoit Claise
- Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-op… Fernando Camacho