IETF Logo Mail Archive

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

Italo Busi <Italo.Busi@huawei.com> Mon, 12 February 2024 19:48 UTC

Return-Path: <Italo.Busi@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 386FBC15109A for <opsawg@ietfa.amsl.com>; Mon, 12 Feb 2024 11:48:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.905
X-Spam-Level:
X-Spam-Status: No, score=-6.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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_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 uzgtb3fYCcX4 for <opsawg@ietfa.amsl.com>; Mon, 12 Feb 2024 11:48:05 -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 02260C14F6B5 for <opsawg@ietf.org>; Mon, 12 Feb 2024 11:48:05 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4TYZf04dYJz67ydF; Tue, 13 Feb 2024 03:44:08 +0800 (CST)
Received: from frapeml500006.china.huawei.com (unknown [7.182.85.219]) by mail.maildlp.com (Postfix) with ESMTPS id 574DE140B30; Tue, 13 Feb 2024 03:48:03 +0800 (CST)
Received: from frapeml500007.china.huawei.com (7.182.85.172) by frapeml500006.china.huawei.com (7.182.85.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Mon, 12 Feb 2024 20:48:03 +0100
Received: from frapeml500007.china.huawei.com ([7.182.85.172]) by frapeml500007.china.huawei.com ([7.182.85.172]) with mapi id 15.01.2507.035; Mon, 12 Feb 2024 20:48:03 +0100
From: Italo Busi <Italo.Busi@huawei.com>
To: Henk Birkholz <henk.birkholz@ietf.contact>, OPSAWG <opsawg@ietf.org>
Thread-Topic: [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg-incident-management-04
Thread-Index: AQHaWsmvnod0QZbVs0qX1OMuKBqcA7ECM5IQ
Date: Mon, 12 Feb 2024 19:48:02 +0000
Message-ID: <9bca3f41009e47bba0beade7aafb38bd@huawei.com>
References: <fecb3c52-493c-436e-78fc-7d3cdc13e43c@ietf.contact>
In-Reply-To: <fecb3c52-493c-436e-78fc-7d3cdc13e43c@ietf.contact>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.144.200]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/4RcrvtZTwDHSJAzRm3Eh9c4REsw>
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: Mon, 12 Feb 2024 19:48:06 -0000

I support the adoption of this document

Italo

> -----Original Message-----
> From: Henk Birkholz <henk.birkholz@ietf.contact>
> Sent: giovedì 8 febbraio 2024 16:44
> To: OPSAWG <opsawg@ietf.org>
> Subject: [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
>

v2.28.0 | Report a Bug | By Email | System Status