Re: [OPSAWG] 🔔 WG Adoption Call for draft-pignataro-opsawg-oam-whaaat-question-mark-03

Giuseppe Fioccola <giuseppe.fioccola@huawei.com> Thu, 11 April 2024 08:21 UTC

Return-Path: <giuseppe.fioccola@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 D0457C14F6B2 for <opsawg@ietfa.amsl.com>; Thu, 11 Apr 2024 01:21:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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 PBWjRS7GRXHF for <opsawg@ietfa.amsl.com>; Thu, 11 Apr 2024 01:21:34 -0700 (PDT)
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 CAA41C14F602 for <opsawg@ietf.org>; Thu, 11 Apr 2024 01:21:33 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4VFXgB0FVfz6K74S; Thu, 11 Apr 2024 16:19:50 +0800 (CST)
Received: from frapeml100008.china.huawei.com (unknown [7.182.85.131]) by mail.maildlp.com (Postfix) with ESMTPS id 5A3691404F4; Thu, 11 Apr 2024 16:21:30 +0800 (CST)
Received: from frapeml500006.china.huawei.com (7.182.85.219) by frapeml100008.china.huawei.com (7.182.85.131) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Thu, 11 Apr 2024 10:21:30 +0200
Received: from frapeml500006.china.huawei.com ([7.182.85.219]) by frapeml500006.china.huawei.com ([7.182.85.219]) with mapi id 15.01.2507.035; Thu, 11 Apr 2024 10:21:29 +0200
From: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
To: Henk Birkholz <henk.birkholz@ietf.contact>, OPSAWG <opsawg@ietf.org>
Thread-Topic: [OPSAWG] 🔔 WG Adoption Call for draft-pignataro-opsawg-oam-whaaat-question-mark-03
Thread-Index: AQHaizctOjb/vqkAok6EozIt2rMntrFiuJ+Q
Date: Thu, 11 Apr 2024 08:21:29 +0000
Message-ID: <9dce286d4a3540a8baeb5c9accf66bcd@huawei.com>
References: <d75cddf8-8872-cb2e-fb13-82e2d978c9bb@ietf.contact>
In-Reply-To: <d75cddf8-8872-cb2e-fb13-82e2d978c9bb@ietf.contact>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.81.202.252]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/iFAm0K3U01UDNbr-QsrGqj7Iubk>
Subject: Re: [OPSAWG] 🔔 WG Adoption Call for draft-pignataro-opsawg-oam-whaaat-question-mark-03
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, 11 Apr 2024 08:21:37 -0000

Dear All,
I support the adoption of this draft since it aims to provide guidelines for OAM terminology, and I think this is quite useful. I’m interested in contributing and I would also suggest to involve IPPM WG for further review, considering the correlation with RFC 7799 .

Regards,

Giuseppe

-----Original Message-----
From: OPSAWG <opsawg-bounces@ietf.org> On Behalf Of Henk Birkholz
Sent: Wednesday, April 10, 2024 1:06 PM
To: OPSAWG <opsawg@ietf.org>
Subject: [OPSAWG] 🔔 WG Adoption Call for draft-pignataro-opsawg-oam-whaaat-question-mark-03

Dear OPSAWG members,

this email starts a call for Working Group Adoption of

> https://www.ietf.org/archive/id/draft-pignataro-opsawg-oam-whaaat-ques
> tion-mark-03.html

ending on Thursday, May 2nd.

As a reminder, this I-D summarizes how the term "Operations, Administration, and Maintenance" (OAM) is used currently & historically in the IETF and intends to consolidate unambiguous and protocol agnostic terminology for OAM. The summary includes descriptions of narrower semantics introduced by added qualifications the term OAM and a list of common capabilities that can be found in nodes processing OAM packets.

The chairs acknowledge a positive poll result at IETF119, but there has not been much discussion on the list yet. We would like to gather feedback from the WG if there is interest to further contribute and review. As a potential enabler for discussions, this call will last three weeks.

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