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

赵星 <zhaoxing@caict.ac.cn> Tue, 20 February 2024 08:11 UTC

Return-Path: <zhaoxing@caict.ac.cn>
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 558C1C14F5ED for <opsawg@ietfa.amsl.com>; Tue, 20 Feb 2024 00:11:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.606
X-Spam-Level:
X-Spam-Status: No, score=-2.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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, 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 UZbZq-lCxqsA for <opsawg@ietfa.amsl.com>; Tue, 20 Feb 2024 00:11:01 -0800 (PST)
Received: from azure-sdnproxy.icoremail.net (azure-sdnproxy.icoremail.net [207.46.229.174]) by ietfa.amsl.com (Postfix) with ESMTP id 5B0B0C14CE4D for <opsawg@ietf.org>; Tue, 20 Feb 2024 00:11:00 -0800 (PST)
Received: from LAPTOP-PEJL4BCI (unknown [36.112.177.90]) by app2 (Coremail) with SMTP id IEIICgBnT9KOXtRlFmBkAA--.38708S2; Tue, 20 Feb 2024 16:10:55 +0800 (CST)
Date: Tue, 20 Feb 2024 16:11:05 +0800
From: 赵星 <zhaoxing@caict.ac.cn>
To: opsawg <opsawg@ietf.org>
References: <97e25762a5d54b1f9ff9fd22f741059e@huawei.com>, <397f5adec6c14f0388a7189bbd4463f8@huawei.com>, <403e5967d86747f28b384666b56cf430@huawei.com>
X-Priority: 3
X-GUID: 3EFB2B0E-1F51-441A-866E-E0C9CE4FE7CD
X-Has-Attach: no
X-Mailer: Foxmail 7.2.14.409[cn]
Mime-Version: 1.0
Message-ID: <202402201611042704189@caict.ac.cn>
Content-Type: multipart/related; boundary="----=_001_NextPart143224380177_=----"
X-CM-TRANSID: IEIICgBnT9KOXtRlFmBkAA--.38708S2
X-Coremail-Antispam: 1UD129KBjvJXoWxWw47WrW5Jr4kKw4rJF17Awb_yoWrtryfpF W7K34rGFWkZr1xG3Zaq3WrAr1Y9395XFZrWa4Yyr18Aas8tF1ktr1Fyw1Yv3y7Crn3XFn0 y3y29Fn0qws8ArJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUQqb7Iv0xC_Zr1lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_tr0E3s1l84ACjcxK6xII jxv20xvEc7CjxVAFwI0_Gr1j6F4UJwA2z4x0Y4vEx4A2jsIE14v26rxl6s0DM28EF7xvwV C2z280aVCY1x0267AKxVW0oVCq3wAS0I0E0xvYzxvE52x082IY62kv0487M2AExVA0xI80 1c8C04v7Mc02F40Eb7x2x7xS6r4j6ryUMc02F40E57IF67AEF4xIwI1l5I8CrVAKz4kIr2 xC04v26r1j6r4UMc02F40E42I26xC2a48xMcIj6xIIjxv20xvE14v26r1Y6r17McIj6I8E 87Iv67AKxVWUJVW8JwAm72CE4IkC6x0Yz7v_Jr0_Gr1lF7xvr2IYc2Ij64vIr41lFcxC0V AYjxAxZF0Ew4CEw7xC0wACY4xI67k04243AVC20s07MxkIecxEwVAFwVW8ZwCF04k20xvY 0x0EwIxGrwCFx2IqxVCFs4IE7xkEbVWUJVW8JwC20s026c02F40E14v26r106r1rMI8I3I 0E7480Y4vE14v26r106r1rMI8E67AF67kF1VAFwI0_Jr0_JrylIxkGc2Ij64vIr41lIxAI cVC0I7IYx2IY67AKxVWUJVWUCwCI42IY6xIIjxv20xvEc7CjxVAFwI0_Jr0_Gr1lIxAIcV CF04k26cxKx2IYs7xG6r1j6r1xMIIF0xvEx4A2jsIE14v26r1j6r4UMIIF0xvEx4A2jsIE c7CjxVAFwI0_Jr0_GrUvcSsGvfC2KfnxnUUI43ZEXa7IU8upBDUUUUU==
X-CM-SenderInfo: p2kd05xlqjquhdlf3hldfou0/
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/BhH0w0qm7ua0XWKWxdJKRYlbEU0>
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, 20 Feb 2024 08:11:06 -0000

Dear OPSAWG,

As an contributor of this draft, I support to adopt it as a WG draft.



Regards
Xing
发件人: yuchaode 
发送时间: 2024年2月19日 10:56
收件人: 'Qin Wu' <bill.wu=40huawei.com@dmarc.ietf.org>; OPSAWG <opsawg@ietf.org>; nmop@ietf.org
主题: 答复: [OPSAWG] WG Adoption Call for draft-feng-opsawg-incident-management-04
 
Hi all,
 
I agree with Qin’s idea. As an author of this draft, I support to adopt it as a WG draft.
I also agree that the chair and AD of both working groups should have an alignment at first, discussing which WG this work belongs to and how to make the work forward.
Thanks!
 
B.R.
Chaode
 
发件人: Qin Wu [mailto:bill.wu=40huawei.com@dmarc.ietf.org] 
发送时间: 2024年2月18日 10:18
收件人: Rob Wilton (rwilton) <rwilton@cisco.com>; Alex Huang Feng <alex.huang-feng@insa-lyon.fr>; Henk Birkholz <henk.birkholz@ietf.contact>; draft-feng-opsawg-incident-management.all@ietf.org
抄送: OPSAWG <opsawg@ietf.org>; nmop@ietf.org
主题: RE: [OPSAWG] WG Adoption Call for draft-feng-opsawg-incident-management-04
 
Hi, NMOP Chairs:
Since this document has been discussed in OPSAWG for a long time, and because it was ready for adoption there, and considering that it is now 'suddenly' in scope for NMOP, could we please consider moving the existing adoption poll to NMOP (perhaps extending it to make up for time when NMOP was not aware of the poll).
 
-Qin (on behalf of authors)
发件人: Rob Wilton (rwilton) [mailto:rwilton@cisco.com] 
发送时间: 2024年2月13日 18:06
收件人: Alex Huang Feng <alex.huang-feng@insa-lyon.fr>; Henk Birkholz <henk.birkholz@ietf.contact>; draft-feng-opsawg-incident-management.all@ietf.org
抄送: OPSAWG <opsawg@ietf.org>; nmop@ietf.org
主题: Re: [OPSAWG] WG Adoption Call for draft-feng-opsawg-incident-management-04
 
Hi authors, OPSAWG, WG chairs,

I appreciate that the timing isn’t ideal, but given that NMOP has just been successfully chartered, and Incident Management is one of the current topics of focus for that WG, then I think that it would be better for this document to be discussed, and potentially adopted, within that WG.  I.e., so that all the incident management related drafts and discussions are kept to one place.

I appreciate that this will potentially slow the adoption a bit, since I think that NMOP should meet first, and this draft should then be presented in NMOP, but hopefully it would only slow the adoption call by a few months.

Note – this doesn’t stop interested parties showing their interest in this work, reviewing the draft and providing comments now.  And of course, that discussion can also happen on the NMOP list.

Regards,
Rob
 
 
From: OPSAWG <opsawg-bounces@ietf.org> on behalf of Alex Huang Feng <alex.huang-feng@insa-lyon.fr>
Date: Tuesday, 13 February 2024 at 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