IETF Logo Mail Archive

Re: [ippm] [IPv6] IOAM, iOAM, and oOAM abbreviations

Bob Hinden <bob.hinden@gmail.com> Wed, 13 December 2023 22:59 UTC

Return-Path: <bob.hinden@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 13645C14F5E5; Wed, 13 Dec 2023 14:59:52 -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=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 EUMxwWYaVcki; Wed, 13 Dec 2023 14:59:48 -0800 (PST)
Received: from mail-yb1-xb29.google.com (mail-yb1-xb29.google.com [IPv6:2607:f8b0:4864:20::b29]) (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 44FD6C14F615; Wed, 13 Dec 2023 14:59:48 -0800 (PST)
Received: by mail-yb1-xb29.google.com with SMTP id 3f1490d57ef6-db5e5647c24so30479276.1; Wed, 13 Dec 2023 14:59:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1702508387; x=1703113187; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=YaMjKTk1mE/1Q3Al2MbFs6s8+VUf0xfnpJgVJfC3W+E=; b=A5aQh5441pGqOzcD80L/AyPxXBqZsvz7A42tea+q50aTcnnP+oGIpjBuAgC5WdAALh XtGmXvuYDJfrNS4zblynyd3okfe2vTxmo45lSZ9kGtwsu/ayGMRcW7KF84GL0VQuRyIj aIoKkOZpZf8mZhuDq1tWHUDomf7oJyeimbcnj/995wRpf1slqzTx3/789LdhVQGkwKLh G99jlH66oVJoc8QrK8TTXiZhe1hbsX4l2JZI7/vgYJEXUYBPi9oLrNCJq21jImuhe9Wo qaWk55hJKMKJ4iDZjMdeBcLTHb0WGOgCRBSZunlN3UutswMEYBiQaQapWRHw9TTMwhcX tzZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702508387; x=1703113187; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=YaMjKTk1mE/1Q3Al2MbFs6s8+VUf0xfnpJgVJfC3W+E=; b=HLuzDPv49nhLFD9UVKICrwL+npFIG0bltlKb+yhFYW4RtPjJbQDAs4Ee7AbU1ZLPYB 03oW9fFrC8falnJIDef0qQCLiaRZ+PHpVUJgiSIoIK5hsRqxcMsZFUZ6quMEltzAcjVZ Ine8W4mLgRzvmY7aGtM0XwlLEmcYO/g1nmGDF4c+Gqw/WHaZ9yKtFJRXw04tjtN2aN4M 1oAoGDrU1EN5zyENgFvT1P/kLscrINh7LB2xb5oJaeYvid2GaHWRDX2UZBwmQylZ6bSq 2nA7ssn8TzUSfLG2gv+RTVhqe30N6dYWRyR0/fxNFUEIyLvsHlTP2E/tdqo4GsTj2BJ6 LmWQ==
X-Gm-Message-State: AOJu0YyHxL0ADKHq+3CK+k8FISyPT3uCD3IVppxOkx9bQvVJOqZQ+qVi x3S5VQU7LW84WNpYeXcGJq8=
X-Google-Smtp-Source: AGHT+IHzaImRlhS2A6p/aEgz7vam/zgYax9iHjQCZSzob0aBl+IArID6E/ksSOl3431kYDX0//tJQg==
X-Received: by 2002:a81:6905:0:b0:5e2:ee29:80ae with SMTP id e5-20020a816905000000b005e2ee2980aemr1092723ywc.26.1702508387140; Wed, 13 Dec 2023 14:59:47 -0800 (PST)
Received: from smtpclient.apple (99-31-208-116.lightspeed.sntcca.sbcglobal.net. [99.31.208.116]) by smtp.gmail.com with ESMTPSA id c128-20020a0df386000000b005d395bf0ad5sm4979632ywf.64.2023.12.13.14.59.45 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Dec 2023 14:59:46 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <49B1F153-8C80-47EC-994C-53AE1EA7DC27@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_B63C6561-1425-4053-BD1A-529B8D1CFB05"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
Date: Wed, 13 Dec 2023 14:59:33 -0800
In-Reply-To: <CA+RyBmU=CKb+oieBwqwn=QkprayA_8KWeTL3XTgioNqw8KTZ+g@mail.gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, DetNet WG <detnet@ietf.org>, mpls <mpls@ietf.org>, IPv6 List <ipv6@ietf.org>, IETF IPPM WG <ippm@ietf.org>, opsawg <opsawg@ietf.org>, Pascal Thubert <pascal.thubert@gmail.com>, Loa Andersson <loa@pi.nu>
To: Greg Mirsky <gregimirsky@gmail.com>
References: <CA+RyBmU=CKb+oieBwqwn=QkprayA_8KWeTL3XTgioNqw8KTZ+g@mail.gmail.com>
X-Mailer: Apple Mail (2.3731.700.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/W_yUCSjt_QtkQ2r5XZ0AUrEJ-9M>
Subject: Re: [ippm] [IPv6] 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 22:59:52 -0000

Greg,

With my 6MAN hat on very loosely, I don’t think this discussion needs to be on the IPV6 list.

Bob


> On Dec 12, 2023, at 7:13 PM, Greg Mirsky <gregimirsky@gmail.com> wrote:
> 
> 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
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

v2.46.0 | Report a Bug | By Email | System Status