[OPSAWG] New I-D -> Guidelines for Charactering "OAM"

Carlos Pignataro <cpignata@gmail.com> Fri, 05 January 2024 20:38 UTC

Return-Path: <cpignata@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 43D83C1930BF for <opsawg@ietfa.amsl.com>; Fri, 5 Jan 2024 12:38:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 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_HI=-5, 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 Gxu4hvAM0_Iy for <opsawg@ietfa.amsl.com>; Fri, 5 Jan 2024 12:38:47 -0800 (PST)
Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 717D5C18DBA7 for <opsawg@ietf.org>; Fri, 5 Jan 2024 12:38:47 -0800 (PST)
Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-a28cc85e6b5so232052066b.1 for <opsawg@ietf.org>; Fri, 05 Jan 2024 12:38:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1704487125; x=1705091925; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=sBoQ80jZWhuEp/MTRLfpAf/5G7B7Pi+0ldHd0KkoNBE=; b=B2J6patiZu9zsXicJmRm1LrmuEqh76zm2dwRkDMFcU977zdY+oQSHwhOxfYz+qmcID tf+SfzMl96ByZqOAuNoxxhYpBjgho1I2EvDV/XilJSmmFZigN89HC14AQxwcDWHABzyn g5N+zS747b5RZ5RwXpQO5drsbnYgQhEBo2mbIiwOwPbJHVo10Q9oGThulHEp5iX+SzEr L6PjNE5fsyMFFbIw7UCcE7JtIPoXs6c3YaCDu56srMD7Dnpa0lSoDGmV7DpOYO1WGNXl gR+rBTHr0LLgQjR/LeAFSCf4c+9Q3gCNTwGFgvtRWdwlBFpwDaP4X/Rij5Y5JudLjX7L uK3Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704487125; x=1705091925; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=sBoQ80jZWhuEp/MTRLfpAf/5G7B7Pi+0ldHd0KkoNBE=; b=gRTdAsEZgwFVZGnhlWD8/+lF9E9CSPEsCRBS4nJo4eoYXqs1+/VvjdKct4DEsht+v3 xZ1y/04mln6Q9iqjh03G/seS/OU2lDteFjcXZ+bdVdKRaqq66D8y/MVROFFFr9VI+6Z9 uLOdEcmXPERx3ORIXEjUuXtE5xZjp7ZFifdlo9faRvIi8ByLqi6KKpc/l5nBzOpv4Ona olbgNUJVDDL1WrYK7m8p3/FE4rS+YnWJdGoCgydSm7LQJg4EzxVmbl8J4GWIUMq8zrX8 9IHtgjkArRr5sG4RVCcDr+wekvTu1vYytTNBNJ2dcB3Wg3jA45YXlWGsj03UyFkR1MGH VOxg==
X-Gm-Message-State: AOJu0YzzDJDQ2ItOIYfHcNpabhebuchmFyNCw7wgcQ/fHRO2vpf9UxSN N5f3ZQvUj9RyQ3Kn4PQhbo/VPcmEmFAcjSOKTVwkp2RlIFtb1g==
X-Google-Smtp-Source: AGHT+IHMxHt0bZxjXEPUXHm67HArsiT4eHOTijRuksNLYdNsBGndZmqhDBuLzqDqGnY3B7JJDpJRiujlidbSUOxgiIc=
X-Received: by 2002:a17:906:4a09:b0:a1f:ad99:a8d8 with SMTP id w9-20020a1709064a0900b00a1fad99a8d8mr1035611eju.113.1704487124797; Fri, 05 Jan 2024 12:38:44 -0800 (PST)
MIME-Version: 1.0
From: Carlos Pignataro <cpignata@gmail.com>
Date: Fri, 05 Jan 2024 15:38:33 -0500
Message-ID: <CACe62MncZZOzad8Z25+6rx3LwKFUuL073A_G4yVTqT9z8XntcA@mail.gmail.com>
To: Ops Area WG <opsawg@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary="000000000000990c13060e38d5e8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/eiMa4yqWSZp-e5nxPgAPBbatwdU>
Subject: [OPSAWG] New I-D -> Guidelines for Charactering "OAM"
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: Fri, 05 Jan 2024 20:38:51 -0000

Hi, Ops Area WG,

Every now and again, there are discussions on how to best characterize or
qualify a particular kind of "OAM", as well as misunderstandings due to
having different definitions and contexts for a given term. A case in point
is "in-band" or "out-of-band" OAM, as recently surfaced at
https://mailarchive.ietf.org/arch/msg/opsawg/jREEH1sFOZ-uxZNky-RTggpxkuk/.

To alleviate this issue, Adrian and I wrote a short I-D to provide
forward-looking guidance on "foobar OAM".

We would appreciate feedback and input on this position, which aims at
updating the guidelines for the "OAM" acronym, with unambiguous guidelines
for their modifiers.

Guidelines for Charactering "OAM":
https://datatracker.ietf.org/doc/draft-pignataro-opsawg-oam-whaaat-question-mark/

Look forward to input and comments to make this more clear and effective!

Adrian & Carlos.