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

Henk Birkholz <henk.birkholz@ietf.contact> Wed, 10 April 2024 11:05 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 35FF3C14CEFD for <opsawg@ietfa.amsl.com>; Wed, 10 Apr 2024 04:05:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.796
X-Spam-Level:
X-Spam-Status: No, score=-2.796 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-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 IS6cQlZh4cqr for <opsawg@ietfa.amsl.com>; Wed, 10 Apr 2024 04:05:39 -0700 (PDT)
Received: from smtp01-ext2.udag.de (smtp01-ext2.udag.de [62.146.106.18]) (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 E53F3C14F6EE for <opsawg@ietf.org>; Wed, 10 Apr 2024 04:05:38 -0700 (PDT)
Received: from [192.168.16.50] (p4fce9f0e.dip0.t-ipconnect.de [79.206.159.14]) by smtp01-ext2.udag.de (Postfix) with ESMTPA id CDF9AE0186 for <opsawg@ietf.org>; Wed, 10 Apr 2024 13:05:36 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf.contact; s=uddkim-202310; t=1712747137; 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; bh=2Whq7C9mIs8GiItGEi7800qLQe4CW57xsUEbYrOhVkc=; b=eAIzsZ8TL/UC2/Y8cFqUo7F8P9rSunip+K719JYx4eVbXwq1wa9CZE5+0ttaIy4WP10GqT r/NoRDON7y0/gI9x3xsydHz8FYl75hlnTXBlcVN+lSWeQS2UCTbOHzSH4SW8waPGFxTvnM RAypGO/OwMDyI6xSG4gK86m8qIqOE9W91SmZUzoSOyQzhCyvqXhPoXZS5a9w9zXNnX+Seb a1OL+YdmMGOVREAX9Vl8mf5ic6xN0omK2LWMaMD+bXoEWu0faP/qSK5X4MKkjViNUU3vuD xJ3JXU0TZGuNeJmWtxW1u/O57dGSFvWAJOYZE2JcBFx/pZ7CSHdaMarvxRXhaw==
Message-ID: <d75cddf8-8872-cb2e-fb13-82e2d978c9bb@ietf.contact>
Date: Wed, 10 Apr 2024 13:05:36 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0
From: Henk Birkholz <henk.birkholz@ietf.contact>
To: OPSAWG <opsawg@ietf.org>
Content-Language: en-US
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Authentication-Results: smtp01-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/K19W7eSSt_XuRDTgH5xyims8wkE>
Subject: [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: Wed, 10 Apr 2024 11:05:43 -0000

Dear OPSAWG members,

this email starts a call for Working Group Adoption of

> https://www.ietf.org/archive/id/draft-pignataro-opsawg-oam-whaaat-question-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