IETF Logo Mail Archive

Re: [ippm] Heads up on draft-ietf-opsawg-yang-vpn-service-pm

Greg Mirsky <gregimirsky@gmail.com> Tue, 03 May 2022 20:54 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 8B230C14F73D; Tue, 3 May 2022 13:54:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 BeOiSzFPJa_Y; Tue, 3 May 2022 13:54:42 -0700 (PDT)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (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 7D91AC14F72A; Tue, 3 May 2022 13:54:42 -0700 (PDT)
Received: by mail-lf1-x12e.google.com with SMTP id j4so32297110lfh.8; Tue, 03 May 2022 13:54:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kzDefs6ApZEXw6fl8bcgt1VIvoN5eYvaBvuyGinQFrw=; b=IWNWQWL0hD6f1tMQwHNE1XlUUaVxAy8rQfrCjZmd/Cde9p9Bk1KPPxY7P0OuyPlARN l6UdTKDFJ97GfaOxEbgQ02E1yxDv3XfWIh/F1KsDaz90vd7JZsizuKwxRcuxyD/dwIhV sUR0qtR7X82gDLLyDhoazBRTG8wj9yKz7KAMR9u73kgtnrE5n8l+eJrwKynBzJlWhrRh uItVbVj0lOXFQu11DZozd1FCaRkY8zVT8n+74ajfHAi8FyYmoN8PisVci2zPkUBOLCKP kpYUJtFXLFHZoy3CWnwfHE8fhGGCV62tch78hniyF8piiXe2i44AA4m7pohTKlq9i6XR pSJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kzDefs6ApZEXw6fl8bcgt1VIvoN5eYvaBvuyGinQFrw=; b=xiM9JgRjdX2YJI2TLlRSCasUoYJODN58jpRXmuR0tiNdQNgIZP5DwV2Ua8W1y4C49w NSnjpVTIlBiqwQfdaIg1hx2RqpQvu9CdVfv9OpgsvHh3zq0XpSv1j5ZHVNQt5L+TWiaU L6SpB0bkwFPPr+ZqPcBjzKSNpJ0XQiz7g+dTv0mf6LI2RAUFEaRwEeK/7CvP1MX2lgOl K8bjlkrwhTdmdBz7gNwHnqumt+NfwVTNM4HV4Td8UVna9Sc/7xKNavLJiQnjYF0gPWeJ FsoY7y4eoilLXtmpp+HEQOSOyb3ewocCAOatZh7zIXj0J9ec1Wuz38rC8mEm8m1zWpKL oyIQ==
X-Gm-Message-State: AOAM532yWwpCBR9SMwDdAPDsZ+EmYHvIBjRRd+7gJu6vsMl0Yd2gz94Z zxi1HhjINGGe59INvHevdKUzW92CPWNpnC852lSrRaFb
X-Google-Smtp-Source: ABdhPJyCJQ+8QcxPPEZeUwbXGV9pupbmCgSsjUyAvJqKITzi+8rNl7RK1ilS/qaBRv3svFUODRcF/erHgLjxFvxaoRM=
X-Received: by 2002:a05:6512:31d3:b0:473:a680:2616 with SMTP id j19-20020a05651231d300b00473a6802616mr3946676lfe.570.1651611280065; Tue, 03 May 2022 13:54:40 -0700 (PDT)
MIME-Version: 1.0
References: <09bc01d85c12$c6906c30$53b14490$@olddog.co.uk>
In-Reply-To: <09bc01d85c12$c6906c30$53b14490$@olddog.co.uk>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Tue, 03 May 2022 13:54:28 -0700
Message-ID: <CA+RyBmVQv-cEPjAsY7_gGhjj9Hdq1RmA2Km8w49k7_Xd5-ajzA@mail.gmail.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Cc: IETF IPPM WG <ippm@ietf.org>, opsawg <opsawg@ietf.org>, draft-ietf-opsawg-yang-vpn-service-pm@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a7c86405de21b789"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/Vuv2rqr521uDsGvB7kdBZZKi5Sg>
Subject: Re: [ippm] Heads up on draft-ietf-opsawg-yang-vpn-service-pm
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.34
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: Tue, 03 May 2022 20:54:43 -0000

Hi Adrian,
thank you for bringing this work to my attention. I've read and shared my
comments earlier. The authors responded promptly and we've worked together
to address my comments. After reading the current version I have a question
about the importance of identifying the particular active measurement
protocol used to measure the reported performance metrics. If reporting the
protocol used for the performance measurement is deemed essential to
characterize the accuracy of the measurement method, then I would propose
to consider several additions to the model:

   - adding STAMP described in RFCs 8762 and 8972 to the list of active
   measurement methods
   - adding Error Estimate for Session-Sender and
   Session-Reciever/Session-Reflector for OWAMP, TWAMP, and STAMP

Thank you for your kind consideration.

Regards,
Greg

On Fri, Apr 29, 2022 at 2:48 PM Adrian Farrel <adrian@olddog.co.uk> wrote:

> Hi,
>
> I'm the document shepherd for draft-ietf-opsawg-yang-vpn-service-pm. It has
> completed WG last call in the OPSAWG.
>
> The work may be of interest to IPPM and you might want to watch out for the
> IETF last call which will be along in due course.
>
> But I'm sure that the authors would welcome any comments you have at any
> time.
>
> Best,
> Adrian
>
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm
>

v2.23.0 | Report a Bug | By Email