IETF Logo Mail Archive

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

Adrian Farrel <adrian@olddog.co.uk> Wed, 17 April 2024 20:14 UTC

Return-Path: <adrian@olddog.co.uk>
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 404C2C14F6B9 for <opsawg@ietfa.amsl.com>; Wed, 17 Apr 2024 13:14:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.797
X-Spam-Level:
X-Spam-Status: No, score=-2.797 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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=olddog.co.uk
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 GyA3fHgA5PoY for <opsawg@ietfa.amsl.com>; Wed, 17 Apr 2024 13:14:04 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40DBAC14F5F7 for <opsawg@ietf.org>; Wed, 17 Apr 2024 13:14:02 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta5.iomartmail.com (8.14.7/8.14.7) with ESMTP id 43HKDx5e018434; Wed, 17 Apr 2024 21:13:59 +0100
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 60FA246050; Wed, 17 Apr 2024 21:13:59 +0100 (BST)
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 556DF4604C; Wed, 17 Apr 2024 21:13:59 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs2.iomartmail.com (Postfix) with ESMTPS; Wed, 17 Apr 2024 21:13:59 +0100 (BST)
Received: from LAPTOPK7AS653V (82-69-109-75.dsl.in-addr.zen.co.uk [82.69.109.75]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.7/8.14.7) with ESMTP id 43HKDuij005559 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 17 Apr 2024 21:13:58 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Henk Birkholz' <henk.birkholz@ietf.contact>, 'OPSAWG' <opsawg@ietf.org>
References: <d75cddf8-8872-cb2e-fb13-82e2d978c9bb@ietf.contact>
In-Reply-To: <d75cddf8-8872-cb2e-fb13-82e2d978c9bb@ietf.contact>
Date: Wed, 17 Apr 2024 21:13:54 +0100
Organization: Old Dog Consulting
Message-ID: <02b301da9103$c7bd1cc0$57375640$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQKjgDBvNKeOvsTZtV4V/D/vw+A5yq/bAZ8Q
Content-Language: en-gb
X-Originating-IP: 82.69.109.75
X-Thinkmail-Auth: adrian@olddog.co.uk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=olddog.co.uk; h=reply-to :from:to:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding; s= 20221128; bh=6GvJLkZF3WJCIhk5AcDQ+LMLB9nuz6xoAVUMYcD22pI=; b=j9t 51Ti7k3LWEP/Znbx0DoHzkqU/gMDcy5W1nynIyoYypk7e5HNE72DapR/RfMEKLA9 JI0+2+CAuPYGg206TavP1jFLZ0TODu2kXRuMcnToHJQoc+AqPp44QWb4c8W/uA/R buBw6siZCCexb0mlHqTQr0XJFv7XFnFirTC1ig1hjEj+u7lCDSPSwQxfoEhGjIlM /eqrf0UEj9ypLcluVe+2NkKRlvo10/fcRxDQyis6+kJk6211+/NXWjFv5ayIUspU yzbQ1NPds6+PQtAqFSRZbEpQwWQXR+ZbdLIKNqSCMd2aaKMoNq7t1ZEE7c/14u31 ViEFr9+tG+I1OgUM+sA==
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1002-28328.002
X-TM-AS-Result: No--17.927-10.0-31-10
X-imss-scan-details: No--17.927-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1002-28328.002
X-TMASE-Result: 10--17.927400-10.000000
X-TMASE-MatchedRID: X4bcv0S75KnxIbpQ8BhdbDCIlN/eSPB9+VJ6lZyB0s9ShcWO/83xosIr JyGzvIdDGLyzmhOFRR2ZTE1KpnMDTc4Cn0fUiJuCGUkpc56lLW2CMN25048Eetx5dDqraCBKHAl sAHftTamC9FpVQ3HWgJUE/Am5Y1o/HEr3EpDncX/6zT5BlgBw37d2noO4P7rA4Ju5UjuFVstUza n9xEPKMYD3m8JnKVIERcPjbVSTZq3Trrk6HnoRbzLRY601LrakkKAa/khZ3iR44yqH65lYDT6yz EmkViqrXrup22nKA3FqNIDF3xjqhnAfiwYMiqEZQQ5+hY6u+45In9CXeywIeYLNFxrEcSlaZROI vB174YikV52mAIXFpZt+1VCW3d+FPQfj0i6w3iueAiCmPx4NwFkMvWAuahr8i2QFaYS1v20qtq5 d3cxkNQP90fJP9eHt
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/LTIJV1F7GlYRIO-GTuzT1j9ADts>
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, 17 Apr 2024 20:14:09 -0000

Hi Henk,

It should come as no surprise that I would be happy to see this adopted.

I want to note that, as is always the case in the IETF, adoption would mean that the working group can change every word of the document and even decide to abandon the document. So Carlos and I are listening to all of the comments being made and trying to work out solutions. Obviously, some of the comments are asking for bigger changes than others so will need more discussion, and we'll need to bring the WG along as we search for consensus.

Cheers,
Adrian

-----Original Message-----
From: OPSAWG <opsawg-bounces@ietf.org> On Behalf Of Henk Birkholz
Sent: 10 April 2024 12:06
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-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