IETF Logo Mail Archive

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

Justin Iurman <justin.iurman@uliege.be> Wed, 10 April 2024 18:57 UTC

Return-Path: <justin.iurman@uliege.be>
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 C4952C14F6F2 for <opsawg@ietfa.amsl.com>; Wed, 10 Apr 2024 11:57:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.394
X-Spam-Level:
X-Spam-Status: No, score=-4.394 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_MED=-2.3, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=uliege.be
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 WGzFumB7xhI4 for <opsawg@ietfa.amsl.com>; Wed, 10 Apr 2024 11:56:57 -0700 (PDT)
Received: from serv108.segi.ulg.ac.be (serv108.segi.ulg.ac.be [139.165.32.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2261BC14F6F0 for <opsawg@ietf.org>; Wed, 10 Apr 2024 11:56:55 -0700 (PDT)
Received: from [192.168.1.55] (125.179-65-87.adsl-dyn.isp.belgacom.be [87.65.179.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by serv108.segi.ulg.ac.be (Postfix) with ESMTPSA id 6B4D6200BBB7; Wed, 10 Apr 2024 20:56:53 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.11.0 serv108.segi.ulg.ac.be 6B4D6200BBB7
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uliege.be; s=ulg20190529; t=1712775413; bh=yQa4rWPhs7Ogkyd8sVKeXgB5rTvTLqu6IMrFNdFsl50=; h=Date:Subject:To:References:From:In-Reply-To:From; b=XNrs2ITDHTAkpbvLyl32ZHybSaPVeSQJ6Ws2127GQKVSY6Dnfq1VbmTrPxyOw+nHz 2EGk21G8wfY/BfGv+FGQU7QNd+CW6ZyGMOVGBiurDKfLVT0HclbuPRkkp51Hp3DPYH 3gZx0mZ5QqYnqkTEyDRPGW9iKgXfZMXRQCOCZxNz+joqUxzrlC28cXYPfu49hOmIMK ob4ru/6BZX+Kkq5V0MUA+zREjfFAJBqEiC8Y4Q8OMKzyCQoLXR5CPNIflyjtBOu/1f nbqRa0/pZTIVMzy5OFev/VooPfSbQ3Qy8ghBjx0hFhVjUps2CJ2qgvaZVEbPw3ZyKC hQdp/1SwCLzrQ==
Message-ID: <3877f63f-b26d-4998-b4b9-e060f1b9d1b5@uliege.be>
Date: Wed, 10 Apr 2024 20:56:53 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Henk Birkholz <henk.birkholz@ietf.contact>, OPSAWG <opsawg@ietf.org>
References: <d75cddf8-8872-cb2e-fb13-82e2d978c9bb@ietf.contact>
Content-Language: en-US
From: Justin Iurman <justin.iurman@uliege.be>
In-Reply-To: <d75cddf8-8872-cb2e-fb13-82e2d978c9bb@ietf.contact>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/D9oET4CEJDTBsWxw0hDLs2LRGVk>
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: Wed, 10 Apr 2024 18:57:01 -0000

Support adoption. I think this document is *very* useful (speaking as an 
IOAM contributor in ippm).

Cheers,
Justin

On 4/10/24 13:05, Henk Birkholz wrote:
> 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
> 
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg

v2.23.0 | Report a Bug | By Email