Re: [ippm] [mpls] [Detnet] IOAM, iOAM, and oOAM abbreviations

Adrian Farrel <adrian@olddog.co.uk> Sat, 16 December 2023 10:17 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADEC8C15108B; Sat, 16 Dec 2023 02:17:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.803
X-Spam-Level:
X-Spam-Status: No, score=-2.803 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, HTML_MESSAGE=0.001, 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_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=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 Y2IzndlTXTIF; Sat, 16 Dec 2023 02:17:04 -0800 (PST)
Received: from mta8.iomartmail.com (mta8.iomartmail.com [62.128.193.158]) (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 A5405C151089; Sat, 16 Dec 2023 02:16:55 -0800 (PST)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta8.iomartmail.com (8.14.7/8.14.7) with ESMTP id 3BGAGrv2001483; Sat, 16 Dec 2023 10:16:53 GMT
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 33F854604B; Sat, 16 Dec 2023 10:16:53 +0000 (GMT)
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 2635E4603D; Sat, 16 Dec 2023 10:16:53 +0000 (GMT)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs1.iomartmail.com (Postfix) with ESMTPS; Sat, 16 Dec 2023 10:16:53 +0000 (GMT)
Received: from LAPTOPK7AS653V ([148.252.129.48]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.7/8.14.7) with ESMTP id 3BGAGpXP023647 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 16 Dec 2023 10:16:52 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: xiong.quan@zte.com.cn, gregimirsky@gmail.com
Cc: mpls@ietf.org, ipv6@ietf.org, ippm@ietf.org, pascal.thubert@gmail.com, opsawg@ietf.org, detnet@ietf.org
References: <202312141056289511089@zte.com.cn>
In-Reply-To: <202312141056289511089@zte.com.cn>
Date: Sat, 16 Dec 2023 10:16:50 -0000
Organization: Old Dog Consulting
Message-ID: <017501da3008$fcf69120$f6e3b360$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0176_01DA3008.FCF77B80"
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AQGF59oLLLkz1TAYm/wmQyJY+DIQZbFUQLxw
X-Originating-IP: 148.252.129.48
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:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type; s=20221128; bh=MfjkPJmHi0wL0b0hJcJsI 49JCRygxY9sNhlGs2NlucA=; b=qzOn2Flp5YGY9/Gsbuazjmf7JIUXUVH7rSIVe PpiZpqA5dQVLrKBznD9xnCRyHz0qNHg0WMkfVcC0Qwyxo8a4a4XJCHNF3zFP/VI/ KVwWK/ZfwOfYqyaEnAdeXYaMDgUXTAdsAs+DBWoNeMESjvrpuImwyTh28KPkUOIh nusCKb6M/oq1K7/9njoXpYe/yAfux8CTD9g/GTiCzmd139T4lWd2S27APYHIYSai MIoJwBR2mF8suzVnRqnRoTNtQvB6JcfoRnfMaVBHKL6IZBrAMO22NtVsCGMfqb5i GjdBkdSMb8UDf25VkkZOanAhojPiNhVd0sWROPFJSPoQqafKg==
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1002-28060.006
X-TM-AS-Result: No--27.452-10.0-31-10
X-imss-scan-details: No--27.452-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1002-28060.006
X-TMASE-Result: 10--27.452400-10.000000
X-TMASE-MatchedRID: H0/uSqZo4D7xIbpQ8BhdbDXgRPG8ApuynNnwm+XC73H23CzozEI96Vng o1EZw+I09OAzRg3F2nJF7ORT0nOv5t6WnwRPJcpeDZs/KgmqdksZskwWqoib3LcIt210bWgIVFw FEckQLeOmxfziGDG2mhFc4pZXalFQ9RYy+aTqMwUX6pCkJZNSOedjQ/G9Lk6QEd+K6O5Nt53nw6 LRy+2IbNY8qTWNMLWmdlwnBvQITCzbazPcdv/32wihQ5NZCXsSo8tN19oTXld68VpiQd7QGORZ+ ls/484hp7ylFcbHN30XlxePCzMBLEdb73gUDwkXwbRQ2Bpmlio3l2plwgrtWLmyqTXHGxLI387R OTCkGUPCfvo3UgFFJE/XebjNV+vbYwAv5CupnhPfSQNpZkETVNBO21OxlsoveZ45ULYLKJP/PLZ jYAgg1m+zs7oErZewu4BgFjMvXkdA4VPFYKuhbwI6gMblpHUxo09MP0yScOgtvNfCaL2uAkv+Gv 9gyZL/rCCXG3Lpn8QAFmb/zOv8COVo8AL9lHEQxVQFfLw4zf9KuSsZSVbDc+HfRqDYP2lAPKtz6 HnGDNR4CEzn2zvJrH41niV9KymzHxPMjOKY7A+DGx/OQ1GV8mgVPcrOkeoTq1bO1OIU069SjKiH jrLYn7U+KYi1qWO6ftwZ3X11IV0=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/2-izSnRVjLKMdtztLfEmAaW4PtM>
Subject: Re: [ippm] [mpls] [Detnet] IOAM, iOAM, and oOAM abbreviations
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Dec 2023 10:17:08 -0000

<My hats are off>

 

I suppose that I don’t object to the definition of new abbreviations if people are keen.

 

Personally, I don’t get the value of “inb-OAM” compared with “in-band OAM”. It’s not like it can be said faster (one additional syllable to say it) and it only saves four characters in typing.

“oob-OAM” is also marginal. Same number of syllables to say (I don’t think anyone pronounces “oob” as a single syllable), and a little more saving in typing.

 

Are the abbreviations worth it for the loss of clarity resulting from not using real words?

 

Cheers,

Adrian

 

From: mpls <mpls-bounces@ietf.org> On Behalf Of xiong.quan@zte.com.cn
Sent: 14 December 2023 02:56
To: gregimirsky@gmail.com
Cc: mpls@ietf.org; ipv6@ietf.org; ippm@ietf.org; pascal.thubert@gmail.com; opsawg@ietf.org; detnet@ietf.org
Subject: Re: [mpls] [Detnet] IOAM, iOAM, and oOAM abbreviations

 

 

Hi Greg,

 

Thanks for bringing this problem up!

I support to define the new abbreviations to help with the in-band OAM and out-of-band OAM. 

And I prefer the inb-OAM and oob-OAM to precisely indicate the two original OAM and to distinguish from IOAM.

 

Best Regards,

Quan

  

 

 

<<Dear All,
<<Loa and I have discussed these abbreviations to help us find a solution
<<that avoids the confusion we found when we came across them. Firstly, what
<<they stand for:
 
   - IOAM - In-situ OAM (RFC 9197
   <https://datatracker.ietf.org/doc/rfc9197/>)
   - iOAM - in-band OAM (RAW architecture
   <https://datatracker.ietf.org/doc/html/draft-ietf-raw-architecture-13>)
   - oOAM - out-of-band OAM (RAW architecture
   <https://datatracker.ietf.org/doc/html/draft-ietf-raw-architecture-13>)
 
<<We discussed the issue with Pascal and came to slightly different
<<abbreviations for the last two:
 
   - inb-OAM
   - oob-OAM
 
<<We also discord these abbreviations with the RFC Editor. Resulting from
<<that, RFC Editor agreed to add IOAM to the RFC Editor Abbreviation List
<https://www.rfc-editor.org/materials/abbrev.expansion.txt>. The other two
abbreviations cannot be added at this time. If that is needed, we can ask
the RFC Editor to add them once the respective RFC is published.
We are seeking your feedback on the following:
 
   - Do you see the benefit of introducing two new abbreviations for
   in-band OAM and out-of-band OAM?
   - Which set of abbreviations (iOAM/oOAM vs. inb-OAM/oob-OAM) do you
   prefer for being used in IETF?
   - Or would you propose another set of abbreviations?
 
Regards,
Loa and Greg