[ippm] IOAM, iOAM, and oOAM abbreviations
Greg Mirsky <gregimirsky@gmail.com> Wed, 13 December 2023 03:13 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 DCE06C14CF13; Tue, 12 Dec 2023 19:13:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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_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 qzWb1WYCyC5Y; Tue, 12 Dec 2023 19:13:29 -0800 (PST)
Received: from mail-yw1-x1135.google.com (mail-yw1-x1135.google.com [IPv6:2607:f8b0:4864:20::1135]) (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 319A5C14F5E8; Tue, 12 Dec 2023 19:13:29 -0800 (PST)
Received: by mail-yw1-x1135.google.com with SMTP id 00721157ae682-5d3758fdd2eso63409947b3.0; Tue, 12 Dec 2023 19:13:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1702437208; x=1703042008; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=qO/GpieIoptlx56+kUWr1JqDTc+LgJb1q3/0G1imF7Y=; b=SVdOcO4QE/jE7CDk/ORDn3C+hJg3Dw+dptWoG4j//RObbnt+JX6rd0vZnWdAqgdmeA Q9sshP8SztMiyAfaM4Y+fuPESTr70T52AnH/Wo01m7nOqGceeeELojcPrdnQOafQB707 U5gIFvTFlBZH2E19OiEMvL2EpjqF+5QoOAziSCjyCL2BHhZmiWTZGIYYxu0Hqw0hedBr BMdAvMSLqVJ6z+0hFFb/Zosj+/s0YAFsp/DYaQNwjy5M2uIgfpy0DnMZQw9/AGGPCD25 PsJIgVEAtOdZprp/wPKNtkyRWvyTuTb1YUapTkZMwo+CBrsbz7TBmhzw0MlfSgudYSx/ gQig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702437208; x=1703042008; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=qO/GpieIoptlx56+kUWr1JqDTc+LgJb1q3/0G1imF7Y=; b=sRBLCQKBzEhAlOJbYN1PuaTP9y2Kze5STxk7Aalpab8/ZSdS+B9QRrQkCZ6vPGEqi3 8P0k+c2P5jk+TQMtgWGnmA29QwCoVxDtPw3HgvVZkm3FJ7IeXf6UCIepp9VCJ6KiXj5f kq1PAIBEAFggu1GheVdd4RSJzoQrjQtH3EiSl4x8m8L9Aw1ikL3JOIjcLPree4EhvNIz 3tW7955MkxzYjZ2kKzdN3rMjtqLM3mPeDABoA0711T6xJY2gsd8ZfW3b+c/LYwN9zZgC jjjFuv4aInuZ3wQtdiy/8B9+fuM584lr4GNIV9Q94nCK3DvmKmeTulvlieQpmrfuDgD7 cgBw==
X-Gm-Message-State: AOJu0Yx+RSrkwQrOl3HaHKet07V52XLxi7Q3F32+R45NELrJiJipSCQE De/m5XTcvZXmsIFibgCQtXHI6xt4xyc4v21dvwNmfRQswr8Sfg==
X-Google-Smtp-Source: AGHT+IEB7NWnBwF56WWHbRulWGSfDoqblhvnQpeQBG5Hd1j4FLJhh23e+S9ooe59FiWmBIpman7cHFGD4uAMw8ph3AA=
X-Received: by 2002:a81:4ec9:0:b0:5e2:51d9:9eb6 with SMTP id c192-20020a814ec9000000b005e251d99eb6mr1263872ywb.52.1702437207948; Tue, 12 Dec 2023 19:13:27 -0800 (PST)
MIME-Version: 1.0
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Tue, 12 Dec 2023 19:13:17 -0800
Message-ID: <CA+RyBmU=CKb+oieBwqwn=QkprayA_8KWeTL3XTgioNqw8KTZ+g@mail.gmail.com>
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>
Content-Type: multipart/alternative; boundary="0000000000000843ff060c5b8d01"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/IQSUmDuvnUXQLF8qxyBaiOu71SA>
Subject: [ippm] 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 03:13:33 -0000
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
- [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