Re: [ippm] [Detnet] IOAM, iOAM, and oOAM abbreviations
Greg Mirsky <gregimirsky@gmail.com> Wed, 13 December 2023 20:15 UTC
Return-Path: <gregimirsky@gmail.com>
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 B7123C14F5ED; Wed, 13 Dec 2023 12:15:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.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_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=unavailable 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 zv0zqUCt5DBB; Wed, 13 Dec 2023 12:15:05 -0800 (PST)
Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) (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 E9534C14F5FC; Wed, 13 Dec 2023 12:14:59 -0800 (PST)
Received: by mail-yb1-xb33.google.com with SMTP id 3f1490d57ef6-db3a09e96daso7597499276.3; Wed, 13 Dec 2023 12:14:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1702498499; x=1703103299; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=2wor1N05EJMieeh7DCrW9c2K6/cqDIfGdxGeh/VEtA0=; b=jQ8k6smDDejlJHau2IJZUvG8PiHzlROf6t1w529Cu9qPbjWa4l3F/1pAq9iGCT8OeD 4UT8r1VBE4P9gR8S4O4A7oNKUJqf/FT9r3N5pTKKzBUkgrbM3GqqieFlhn8M3V8VwuAO o95zRV5veVA7tr1VsCvcs/WeZ+Kif5eT+RxOaSDbOCrsUKE01bxR6XyZ2YUmPaPRSBm3 95hGp/NBLv7/AmBLajz8CuM5OCkhlLoFLj1PHZQ2Mm8ulv+1CLd1ZvWtpdbrpTVKgCc5 DF7QtztXde0fyj97oSCsgwD/QrxKaxGCzFqHk9clb1rMUgkCCirUSaTuvCZWc3FzUA/U KxSw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702498499; x=1703103299; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=2wor1N05EJMieeh7DCrW9c2K6/cqDIfGdxGeh/VEtA0=; b=g6zw68hPhsNwjvSXUAi1oFEd1LvoHHGP3FbM8t94uJOtm/h3Oy+dB+KokmHeLi/KDy 5tp6LRIXW+uHKqknGuSLiaOllWm3fRi6UiUL92vdHeP/TwoXCBtuL5rRFBnUZw1MkY+d +Ey4G6F27Jy1Ybno8g1uuxEj2+dSwHDPw7Gp7d/5calUBLfuGV62li22RQ6uQrIje75r +R/KkwTPCDQXQFDUIUBkJoOJar96SPi5V5aI8dB47Ooethqyga+xy4mgTYHgwK0IZjeW nSEhhOMrhwJxLXsQHuwprWsvPz7klqCviSLQ88MT5Vbhsbjkel/U0ZTtVwbfnQgg6onU lGdQ==
X-Gm-Message-State: AOJu0YyR8D5sJOsOzeg2T//PFvIenBXTQaTn1gGLeKQclxbta3S/SYmx KkxRV+hbPaj6WJoob+i4NNzcxj+rkFbUuUHQee0=
X-Google-Smtp-Source: AGHT+IGIIEs7MBG5Ff5FmIwXg4kjVB8NzoCHWLGl1SklnlySs/EZELurchLwG5ASeCI9Ur2iRsnfIZevSZfrzk5c5Kc=
X-Received: by 2002:a25:f209:0:b0:dbc:7c50:284a with SMTP id i9-20020a25f209000000b00dbc7c50284amr4711330ybe.111.1702498498753; Wed, 13 Dec 2023 12:14:58 -0800 (PST)
MIME-Version: 1.0
References: <CA+RyBmU=CKb+oieBwqwn=QkprayA_8KWeTL3XTgioNqw8KTZ+g@mail.gmail.com> <PH7PR11MB8478C2D6660F7C9166FD8E6EDA8DA@PH7PR11MB8478.namprd11.prod.outlook.com> <ddbad7a2-9f8d-48ef-812c-5a71611a0d69@linutronix.de>
In-Reply-To: <ddbad7a2-9f8d-48ef-812c-5a71611a0d69@linutronix.de>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Wed, 13 Dec 2023 12:14:47 -0800
Message-ID: <CA+RyBmVpZozu_ghmB5800KBKY-4JOyRrOPG7Mtnh-U508rw18A@mail.gmail.com>
To: Florian Kauer <florian.kauer@linutronix.de>
Cc: "Frank Brockners (fbrockne)" <fbrockne=40cisco.com@dmarc.ietf.org>, DetNet WG <detnet@ietf.org>, mpls <mpls@ietf.org>, 6man WG <ipv6@ietf.org>, IETF IPPM WG <ippm@ietf.org>, opsawg <opsawg@ietf.org>, Pascal Thubert <pascal.thubert@gmail.com>, Loa Andersson <loa@pi.nu>
Content-Type: multipart/alternative; boundary="0000000000003fc0f0060c69d2ba"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/mxOv6gk5rXAUh8mcOXabZOyC3ZQ>
Subject: Re: [ippm] [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: Wed, 13 Dec 2023 20:15:09 -0000
Hi Florian, thank you for your questions. I added my notes below under the GIM>> tag. Regards, Greg On Wed, Dec 13, 2023 at 3:06 AM Florian Kauer <florian.kauer@linutronix.de> wrote: > Hi, > so does in-band OAM (RAW architecture) actually mean exactly the same as > In-situ OAM (RFC 9197)? > If yes, both should be named and abbreviated exactly the same way and > since RFC 9197 is already published, it should probably be In-situ OAM > (IOAM). (But the question then is what is out-of-band OAM? Out-situ OAM? > ;-) ) > GIM>> The intention of introducing "in-band OAM" and "out-of-band OAM" terms is to stress that some performance measurements can be performed without traversing the same set of links and nodes as the monitored flow. For example, direct loss measurement, which is collecting counters of in-profile frames/packets, can be out-of-band. These measurement methods are classified as passive per RFC 7799. Examples of in-band OAM, in our view, can be found among active and hybrid (per RFC 7799) measurement methods. > > If no, PLEASE don't use the same abbreviation for slightly different > things, even in slightly different contexts. I acknowledge the preference > of those working on a very specific topic to keep their daily used > terminology as concise as possible, but as someone who tries to get into > all those topics to understand the bigger picture or to actually implement > something, specific abbreviations are always a hurdle, especially when they > have different meanings in slightly different contexts. > > So I really like inb-OAM and oob-OAM, because you can really "see" the > origin in it without repeatedly asking yourself if "i" stands for in-situ, > in-band, internet, industrial, intelligent... > GIM>> Thank you. > > If you need a whole new section in an RFC just to explain the different > uses of I in an abbreviation, you will likely spend more key strokes on > that section, than on the additional "nb-"s ;-) > > Just my two cents. > > Greetings, > Florian > > > On 13.12.23 11:54, Frank Brockners (fbrockne) wrote: > > > > > > When IPPM started working on IOAM, there was a long discussion on naming > – and the conclusion was that “in-band” as not appropriate for OAM > information being piggybacked on top of user traffic. This is why the IPPM > WG concluded to use “In-situ OAM” – or “IOAM” for short, which is what is > used in RFC9197 and all related documents. > > > > Frank > > > > > > > > *From:*ippm <ippm-bounces@ietf.org> *On Behalf Of *Greg Mirsky > > *Sent:* Wednesday, 13 December 2023 04:13 > > *To:* DetNet WG <detnet@ietf.org>; mpls <mpls@ietf.org>; 6man WG < > ipv6@ietf.org>; IETF IPPM WG <ippm@ietf.org>; opsawg <opsawg@ietf.org>; > Pascal Thubert <pascal.thubert@gmail.com>; Loa Andersson <loa@pi.nu> > > *Subject:* [ippm] IOAM, iOAM, and oOAM abbreviations > > > > > > > > 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 > > > > > > > > > > _______________________________________________ > > detnet mailing list > > detnet@ietf.org > > https://www.ietf.org/mailman/listinfo/detnet >
- [ippm] IOAM, iOAM, and oOAM abbreviations Greg Mirsky
- Re: [ippm] [IPv6] IOAM, iOAM, and oOAM abbreviati… Vasilenko Eduard
- Re: [ippm] [IPv6] IOAM, iOAM, and oOAM abbreviati… mohamed.boucadair
- Re: [ippm] IOAM, iOAM, and oOAM abbreviations Frank Brockners (fbrockne)
- Re: [ippm] [Detnet] IOAM, iOAM, and oOAM abbrevia… Florian Kauer
- Re: [ippm] [Detnet] IOAM, iOAM, and oOAM abbrevia… Frank Brockners (fbrockne)
- Re: [ippm] [Detnet] IOAM, iOAM, and oOAM abbrevia… Greg Mirsky
- Re: [ippm] [Detnet] IOAM, iOAM, and oOAM abbrevia… Florian Kauer
- Re: [ippm] [Detnet] IOAM, iOAM, and oOAM abbrevia… Greg Mirsky
- Re: [ippm] [Detnet] IOAM, iOAM, and oOAM abbrevia… Florian Kauer
- Re: [ippm] [IPv6] IOAM, iOAM, and oOAM abbreviati… Michael Richardson
- Re: [ippm] [IPv6] IOAM, iOAM, and oOAM abbreviati… Bob Hinden
- Re: [ippm] [Detnet] IOAM, iOAM, and oOAM abbrevia… xiong.quan
- Re: [ippm] [mpls] [Detnet] IOAM, iOAM, and oOAM a… Adrian Farrel
- [ippm] Is out-of-band OAM relevant? (Was: IOAM, i… Alexander Vainshtein
- Re: [ippm] Is out-of-band OAM relevant? (Was: IOA… Alexander Vainshtein
- Re: [ippm] [OPSAWG] Is out-of-band OAM relevant? … Italo Busi
- Re: [ippm] [mpls] [Detnet] IOAM, iOAM, and oOAM a… tom petch
- Re: [ippm] [IPv6] [mpls] [Detnet] IOAM, iOAM, and… Stewart Bryant
- Re: [ippm] [mpls] [IPv6] [Detnet] IOAM, iOAM, and… Loa Andersson
- Re: [ippm] [IPv6] [mpls] [Detnet] IOAM, iOAM, and… xiao.min2
- Re: [ippm] [mpls] IOAM, iOAM, and oOAM abbreviati… Italo Busi
- Re: [ippm] [mpls] IOAM, iOAM, and oOAM abbreviati… Loa Andersson