IETF Logo Mail Archive

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

Ziyang Xing <xzynet@gmail.com> Sat, 10 February 2024 08:27 UTC

Return-Path: <xzynet@gmail.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 C1AA7C14F5EC for <opsawg@ietfa.amsl.com>; Sat, 10 Feb 2024 00:27:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Oy46lfIi7PAy for <opsawg@ietfa.amsl.com>; Sat, 10 Feb 2024 00:27:27 -0800 (PST)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 ECA07C14F5EE for <OPSAWG@ietf.org>; Sat, 10 Feb 2024 00:27:27 -0800 (PST)
Received: by mail-ed1-x532.google.com with SMTP id 4fb4d7f45d1cf-55fe4534e9bso2248517a12.0 for <OPSAWG@ietf.org>; Sat, 10 Feb 2024 00:27:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1707553646; x=1708158446; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=4D3kOfBBfEqeTDFHmquV8aLQT3BJHh4vsVSPDAsd/YM=; b=VI8ZQ9nu/S92f6IyLDHtz4VCrF9aMFLV+br+Gkbmh1HrE6xdUooMvKBqDXU/rI9i2Q Ow2ONPCtl6SI1bk8CZWzLHGvFIIBJNGSpkpDV//HwgT+Lg08yxn+oIz4VAnSjS4vT0Sy iYKywvBxIvAK3PO45rdOTsqd9S970IAM6Ohk29hShimB9hlOFlsNngH9qJ+9WCpLwiN6 Qeh71C3cNI2njvAOZv+zKPdC7IoY6mPz0mDBsTbiwTe1egRts+xJIR8Gohsr9xl4jycj 3ZhbS6G13iAmcXJqWzC65gPWtxxR35OQ8D3bsG2iboh7gN8Su54543HyARbkQpDvSzXf SbCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1707553646; x=1708158446; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=4D3kOfBBfEqeTDFHmquV8aLQT3BJHh4vsVSPDAsd/YM=; b=g8K7SgF1sXR5HdsQkt0mxrGui+I/pPX2b6Qz5lMkuRjq8UI4JJOAQG8YyvaIid1zRu OOj7xJ8fKpv2V4Qp+r/OhO6so9c/4nRwPabsjzRnLxb+pvC6kvx0NYgiZcSFdRNxw0FR HE63eINy++ZNEkZwwwQz+KfnrKK2OVd24BVCNXk5Um3S2Wl8aZhZDouZtD1+0tLSXb8j 4qneHILpb7Z9fWvXF+Zk4j1dpus+CS5ktHmlYQf2Qz8bvRcHD/DArC2GAlJIooBbjWWP 6k8Ys9xgbTef/FILjQZypMf1/v8RJGalker5mJ0Dc76jUPXTqKsSdghR1mqByAJ6fHzS /Xng==
X-Gm-Message-State: AOJu0Yxwc/QL4pZbN4i2WIEhz3ETKtKEalqbUwBACdu6cFypuCriGzgw aeTTKqcIYmRh3dskq0KLDuhjIObFSeJzeQ05t3w4c8TbmxR7Fn8AWqsu3gzWBCKNS7ABWaNSaw1 sMiEt2Vzedb8D2Drh0WQBrTzErzKsvexUVKk=
X-Google-Smtp-Source: AGHT+IGAmHtjKlhtJs5OF+2AJThMZfUPLzF9ttHQnfpfPPJcw4fUsmViSaPX00I/0dlhoCN0ZrIsUM8N9byAoW5wvAk=
X-Received: by 2002:aa7:d758:0:b0:560:5f1e:f420 with SMTP id a24-20020aa7d758000000b005605f1ef420mr770438eds.0.1707553645635; Sat, 10 Feb 2024 00:27:25 -0800 (PST)
MIME-Version: 1.0
From: Ziyang Xing <xzynet@gmail.com>
Date: Sat, 10 Feb 2024 16:27:16 +0800
Message-ID: <CAG646tvTAB3qA+s85kkCvuAyG3453mLzb_o+ep5MARseCHNeEg@mail.gmail.com>
To: OPSAWG@ietf.org
Content-Type: multipart/alternative; boundary="0000000000007bad53061102d096"
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/ZbhPfgqZTsiKUM2HY5Ep3TiqhvE>
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: Sat, 10 Feb 2024 08:27:31 -0000

I agree!

I support the adoption of this draft as a WG document.

The draft defines the concepts, requirements, and architecture of incident
management and a YANG data model for incident lifecycle management, which
can improve troubleshooting efficiency, ensures network service quality.


Ziyang Xing
-------------------------------------
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.28.0 | Report a Bug | By Email | System Status