From cmpignat@ncsu.edu Sun Mar 24 11:46:13 2024 Return-Path: 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 DF153C14F5FD for ; Sun, 24 Mar 2024 11:46:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.103 X-Spam-Level: X-Spam-Status: No, score=-2.103 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=ncsu.edu 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 jteezveIYV-l for ; Sun, 24 Mar 2024 11:46:10 -0700 (PDT) Received: from mail-oi1-x22d.google.com (mail-oi1-x22d.google.com [IPv6:2607:f8b0:4864:20::22d]) (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 23971C14EB19 for ; Sun, 24 Mar 2024 11:46:09 -0700 (PDT) Received: by mail-oi1-x22d.google.com with SMTP id 5614622812f47-3c3915a7afaso2463305b6e.2 for ; Sun, 24 Mar 2024 11:46:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ncsu.edu; s=google; t=1711305968; x=1711910768; 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=RRglU0GGxijHscgVPm/uMC4DvkUrKxS2o2n2U6Xunco=; b=M/JUDP8aFKIl3fGLW7EEWvSIpB6M94NRbp6NySYC+JmjzOcXlFRzC1NlAD3/0H8wqG Mt8mK2t/mF1ffsvddU7vgOxfQU4EbqYgmyKz/OZqhevo8SYNUcHFNTOnAkUehrEHCoam yPGJVVTc2nc7dIB2s2giCvqzoDa5QKK/79BCZYH8nBCxM8QWUewRmftpMUmPn75UAeEH /xiDmfr4b3aKwAwr0QO/l7/7lhpSgKVGE/++i1RVXnQPyIYT8YIovg/nUtQHj6CUfB1O u+1ybGHOTHh2Fe47imqm/6lQxmExoRVIHTpmpRvBkRltomX1WxJDYbET2mCJ7dT7cJ+x C8Fg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711305968; x=1711910768; 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=RRglU0GGxijHscgVPm/uMC4DvkUrKxS2o2n2U6Xunco=; b=Ia7P5ugF0VmD4Bh8C6Z273Nw7O2guYTudzOMRZV6O6TJSFO4RO3+XA/rCgI+eMWCzT KSy2XQAEW7kXgr/0YS7P0X+tJv3Vb7KM71zlVD2610G2TTClEmdTUIz0veo7g/5d7WGG GGaW+JUGfsLIS+hU3er2lr2VYSmlSd49xczKIJB5k/nExISvHybO9Diq65QnwBjHl4Kc U/pVHbivq6Faya6MnfCW640nsUaflCmOJbByBpgfAjAf1N1QPEK4S1HMD2UW8aFY5nO+ E/nnkjNHTcYOLGMhYUx4p8hBEZzrkmWwqVOwaV+81vHmpyI3ois4sEKaC6TouWSjtawF TzdQ== X-Forwarded-Encrypted: i=1; AJvYcCUVEdqgZ2CsnoWa3XyD8IPhrRJuUA6JlQY3xM3vj4pdmhvCRIOfrMCSs2dYJOB30FQ3CTYCZVfIG93zXnshhU8= X-Gm-Message-State: AOJu0YwXR1HVVSYw6mEYs1l/FrHA391iwgRBZScNFykPcZ4FXOIjxe+R NKncfJmpnBE5WtHZHshj+b5MewId0BAIJsAQ/O1afS0QMPbu4xYHlG6RF38RWK73bHqIvK4f3uY pww== X-Google-Smtp-Source: AGHT+IFu4J/5NF+Yqj9O6bWeFHACfkgqq6Mi2ZsVufy5pefijDfqh7+KNUlx7Mrzv8x67kmWehbiyQ== X-Received: by 2002:a05:6808:257:b0:3c1:e8d4:e16f with SMTP id m23-20020a056808025700b003c1e8d4e16fmr5928620oie.24.1711305968415; Sun, 24 Mar 2024 11:46:08 -0700 (PDT) Received: from smtpclient.apple (2603-6080-1201-7e2f-b90c-4b19-f7f1-4cdd.res6.spectrum.com. [2603:6080:1201:7e2f:b90c:4b19:f7f1:4cdd]) by smtp.gmail.com with ESMTPSA id ca9-20020a05622a1f0900b00430ea220b32sm1840381qtb.71.2024.03.24.11.46.07 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 24 Mar 2024 11:46:08 -0700 (PDT) From: Carlos Pignataro Message-Id: <8A8BDCB0-1C27-4577-BC04-49278ACD202C@ncsu.edu> Content-Type: multipart/alternative; boundary="Apple-Mail=_25F7A3F1-E972-4C51-8841-76BC0AB6011B" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\)) Date: Sun, 24 Mar 2024 14:45:57 -0400 In-Reply-To: Cc: "Thomas.Graf" , Adrian Farrel , Ops Area WG To: Alex Huang Feng References: <61057ae96b744ef19ded9a6e84883325@swisscom.com> X-Mailer: Apple Mail (2.3774.500.171.1.1) Archived-At: X-Mailman-Approved-At: Sun, 31 Mar 2024 06:46:31 -0700 Subject: Re: [OPSAWG] draft-pignataro-opsawg-oam-whaaat-question-mark X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Mar 2024 18:48:27 -0000 --Apple-Mail=_25F7A3F1-E972-4C51-8841-76BC0AB6011B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Many thanks Thomas and Alex, both for the support, as well as for the = useful suggestions. Alex, =E2=80=9Con-path=E2=80=9D is much more descriptive than = =E2=80=9Cin-band=E2=80=9D for sure! Thomas, Alex, will send an iteration of the draft incorporating the Node = Type suggestion. Thanks! Carlos. > On Mar 18, 2024, at 2:55=E2=80=AFAM, Alex Huang Feng = wrote: >=20 > Dear Carlos and Adrian, >=20 > As I said in the chat during the OPSAWG meeting, I also support this = document. > I don=E2=80=99t have a lot of specific examples of how the terminology = are confusing, but I am co-authoring = draft-ietf-opsawg-ipfix-on-path-telemetry where it started as an inband = telemetry protocol and then we were asked to change this terminology to = =E2=80=9Con-path telemetry protocol=E2=80=9D.=20 > Also I haven=E2=80=99t been able to find a clear formal definition of = =E2=80=9Con-path telemetry protocol=E2=80=9D. >=20 > Thanks for the document, > Alex >=20 >> On 18 Mar 2024, at 15:32, Thomas.Graf@swisscom.com wrote: >>=20 >> Dear Carlos and Adrian, >> =20 >> As the author of draft-ietf-opsawg-ipfix-on-path-telemetry, I care = and value that you are defining OAM terminology. This is much needed. = Count me on the list of people who misused the term inband previously. >> =20 >> I would appreciate of you could add also OAM node type. As an example = in RFC 9398 for IOAM the following types are defined >> =20 >> IOAM encapsulation node >> IOAM transit node >> IOAM decapsulation node >> =20 >> It would be very useful to have an OAM protocol agnostic terminology. >> =20 >> Best wishes >> Thomas >> =20 >> _______________________________________________ >> OPSAWG mailing list >> OPSAWG@ietf.org >> https://www.ietf.org/mailman/listinfo/opsawg >=20 --Apple-Mail=_25F7A3F1-E972-4C51-8841-76BC0AB6011B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Many thanks = Thomas and Alex, both for the support, as well as for the useful = suggestions.

Alex, =E2=80=9Con-path=E2=80=9D is much = more descriptive than =E2=80=9Cin-band=E2=80=9D for = sure!

Thomas, Alex, will send an iteration of = the draft incorporating the Node Type = suggestion.

Thanks!

Carl= os.

On Mar 18, 2024, at 2:55=E2=80=AFAM, Alex Huang Feng = <alex.huang-feng@insa-lyon.fr> wrote:

Dear Carlos and Adrian,

As I said = in the chat during the OPSAWG meeting, I also support this = document.
I don=E2=80=99t have a lot of specific examples of = how the terminology are confusing, but I am co-authoring = draft-ietf-opsawg-ipfix-on-path-telemetry where it started as an inband = telemetry protocol and then we were asked to change this terminology to = =E2=80=9Con-path telemetry protocol=E2=80=9D. 
Also I = haven=E2=80=99t been able to find a clear formal definition of = =E2=80=9Con-path telemetry protocol=E2=80=9D.

Tha= nks for the document,
Alex

On 18 Mar 2024, at 15:32, Thomas.Graf@swisscom.com = wrote:

Dear Carlos and = Adrian,
 
As the author of draft-ietf-opsawg-ipfix-on-path-telemetry, = I care and value that you are defining OAM terminology. This is much = needed. Count me on the list of people who misused the term inband = previously.
 
I would appreciate of you could add also OAM node type. As = an example in RFC 9398 for IOAM the following types are = defined
 
IOAM encapsulation node
IOAM transit = node
IOAM decapsulation node
 
It would be very useful to have an OAM protocol agnostic = terminology.
 
Best wishes
Thomas
 
_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
<= /div>

= --Apple-Mail=_25F7A3F1-E972-4C51-8841-76BC0AB6011B--