IETF Logo Mail Archive

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

Henk Birkholz <henk.birkholz@ietf.contact> Thu, 29 February 2024 06:45 UTC

Return-Path: <henk.birkholz@ietf.contact>
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 A6657C151075; Wed, 28 Feb 2024 22:45:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.196
X-Spam-Level:
X-Spam-Status: No, score=-7.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.091, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ietf.contact
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 AGLtD09CeQhY; Wed, 28 Feb 2024 22:45:06 -0800 (PST)
Received: from smtp03-ext2.udag.de (smtp03-ext2.udag.de [62.146.106.30]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62B3BC151071; Wed, 28 Feb 2024 22:45:06 -0800 (PST)
Received: from [192.168.144.212] (115x125x248x126.ap115.ftth.ucom.ne.jp [115.125.248.126]) by smtp03-ext2.udag.de (Postfix) with ESMTPA id 30213E124F; Thu, 29 Feb 2024 07:45:02 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf.contact; s=uddkim-202310; t=1709189104; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=2bSMjUY6JxpAxzMKsIUcoxfnjMWdL+No041ZQHttGXg=; b=HcJi5hswkxDEiHW7aEUJuFsmuXyqNt24AbQuIgnPgATYhFp4n+jYBDnLL3ALb0NyvZuJ+G md3byFIh/EVAwToQtTJZZ514mLF5kb1qdQoF5Uyd5/x/bBLzi3h9LKe+Fidbsw/L8OHxgj foYnEx2oWtw3bB8V8ekcLdNf6ph2mUOyJfffj35ue8DOxrq2zTH5JPhrdzQNguVHEXJkw9 oNz+NlAJSng3gvwY8AC43U+9Sm4LENZtdb6BxUAPk5GyuzV7yv/L3JJBI77/MV0XnXAL8T kS4JFuH9pT+SvEmWsMxayRVvKh6X7tzkmP4gndXDjxWSt9JZ1gxzWwZeLLI+cA==
Message-ID: <10b295f6-ab36-e244-1745-3a17a3ff78b9@ietf.contact>
Date: Thu, 29 Feb 2024 07:44:59 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0
Content-Language: en-US
To: opsawg@ietf.org, nmop-chairs@ietf.org
References: <fecb3c52-493c-436e-78fc-7d3cdc13e43c@ietf.contact>
From: Henk Birkholz <henk.birkholz@ietf.contact>
In-Reply-To: <fecb3c52-493c-436e-78fc-7d3cdc13e43c@ietf.contact>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Authentication-Results: smtp03-ext2.udag.de; auth=pass smtp.auth=henk.birkholz@ietf.contact smtp.mailfrom=henk.birkholz@ietf.contact
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/ry16O_YkT3VlLHpoFoX2_LLUoEs>
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 06:45:10 -0000

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

v2.23.0 | Report a Bug | By Email