[ippm] A question about the interpretation of "performance monitoring" in draft-ietf-teas-actn-pm-telemetry-autonomics

Greg Mirsky <gregimirsky@gmail.com> Mon, 21 March 2022 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 05CD63A08D6; Mon, 21 Mar 2022 13:15:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id skAAPJIexzTm; Mon, 21 Mar 2022 13:15:49 -0700 (PDT)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F25D63A1B02; Mon, 21 Mar 2022 13:15:41 -0700 (PDT)
Received: by mail-lf1-x136.google.com with SMTP id d5so7257705lfj.9; Mon, 21 Mar 2022 13:15:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=9MU4EgMEQeF0pNEoHwLYPanOhest4TUdMTSbPrx+zzY=; b=AI9MQoRJVPf7o//DZzkpnp++BkSxcNvLnw+cEfRlTKphr/Ev5kCXXy030RT2l+0lVt FMNJvYupbD9akeIXV9V/K1r4lbYwxRI/hGR3tA4Hys6gyAl+1NZQFPxqPLAp6hFdHidp v4JSRLerloFeWvd9oKIjSK0+m3YQDuXWi0n4BMkmkCTkN51SdnhH00e6IyL+0Qx2iGzf ev+4AbhLdCa3pP66NUvF2lVWAyVF+h69Svji3PEIRAp4eLuh9LcSxY6iuaHtckrDW4RX FY1asykHMy13S7RCXxbXD5Vz5Pu8UyTepCtn4KGBqI1oq0Qv+ZOibWcILQFbxO1AgLFI F2Sg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=9MU4EgMEQeF0pNEoHwLYPanOhest4TUdMTSbPrx+zzY=; b=t3EHzE36JxC5mN+X2nhQiGjiTd+19+1N0+/VO4n8RnEXzNi56s2lt0ri3cXUsRe1uP v66x51Wgb7ESRwuCVQvPBnKol9L9FNzidzYBYM7CaOGtqthbeJheN1f9c449yU4hiCH0 Ws+BItdq2iGmHBRXCyULipZSfIzb3gljkyqaYmGsGafXL+LB+PVYxY9ZI1uGVhySEqJR zeS3DuEpXIEym8K9WdZ5wWksnZ1IOF3pNu2GDdPpJLxhVIOAe+GI1MFPzuDvUFie7F3J HQeDtKwbFpFXUWPhTZeXZTvV1hOE84/X0wzbEILszh27+Xb2Gj8TW5NpCMrO4A9Y/i6I jblg==
X-Gm-Message-State: AOAM533K4o7xh6SjmF18FMM5N/fLj+BMCs2PNTPyn9cFul3r3TcP1pxC BVdNgQf0bvjD0XiE3CvqdUQhlFFBmu495pvBFGr8BxG00OI=
X-Google-Smtp-Source: ABdhPJxVgsGAmFCzdeAU8bvPTVVFAgwfRhmT13B+v5eqCJ8CzRP58E8qdbvHj4vm7LvDnWhXt2MppZrNwpRFDg/b7C8=
X-Received: by 2002:a05:6512:321c:b0:44a:2109:201f with SMTP id d28-20020a056512321c00b0044a2109201fmr7713051lfe.26.1647893738985; Mon, 21 Mar 2022 13:15:38 -0700 (PDT)
MIME-Version: 1.0
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 21 Mar 2022 13:15:26 -0700
Message-ID: <CA+RyBmXHj=2G+v9Hk9AG0FMG0yVqo53d=8qqg8SL7fnSxBYh+A@mail.gmail.com>
To: draft-ietf-teas-actn-pm-telemetry-autonomics@ietf.org, TEAS WG <teas@ietf.org>, IETF IPPM WG <ippm@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f09f5305dac02891"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/-3r3dd4gIyONRu31WUDXsxIA4X8>
Subject: [ippm] A question about the interpretation of "performance monitoring" in draft-ietf-teas-actn-pm-telemetry-autonomics
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 21 Mar 2022 20:15:53 -0000

Dear Authors,
thank you for all your work on the document. As you can see from the
subject line, I am interested in how performance monitoring is
interpreted in your draft. You've noted in the Introduction that:
   The term performance monitoring is used in this document in a
   different from how the term has been used in TE networks for many
   years.  Performance monitoring in this document refers to
   subscription and publication of streaming telemetry data.
I think that it would be helpful to add a reference to the document that,
in your opinion, provides a different, "traditional" interpretation of
performance monitoring in TE networks. Personally, I don't see any
significant differences as I consider publication/subscription as a *method
*of performance monitoring. In my understanding, collecting information
using YANG notifications can be classified, according to RFC 7799, as a
passive measurement method (similar to SNMP queries). Another example of
the PM OAM method is an active measurement, e.g., using TWAMP or STAMP.
Lately, we've seen the development of a new type of PM - hybrid methods
that combine characteristics of passive and active methods.
I greatly appreciate your opinions on this and whether you think the draft
can use RFC 7799-style classification of performance measurement methods.

Regards,
Greg