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

"Wubo (lana)" <lana.wubo@huawei.com> Thu, 05 May 2022 12:47 UTC

Return-Path: <lana.wubo@huawei.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 613EAC15E41D; Thu, 5 May 2022 05:47:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 XUidG2h9gciY; Thu, 5 May 2022 05:47:15 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B885AC15E6C4; Thu, 5 May 2022 05:46:46 -0700 (PDT)
Received: from fraeml744-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4KvD0H43Szz6H7K6; Thu, 5 May 2022 20:43:59 +0800 (CST)
Received: from kwepemi100011.china.huawei.com (7.221.188.134) by fraeml744-chm.china.huawei.com (10.206.15.225) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Thu, 5 May 2022 14:46:42 +0200
Received: from kwepemi500014.china.huawei.com (7.221.188.232) by kwepemi100011.china.huawei.com (7.221.188.134) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Thu, 5 May 2022 20:46:40 +0800
Received: from kwepemi500014.china.huawei.com ([7.221.188.232]) by kwepemi500014.china.huawei.com ([7.221.188.232]) with mapi id 15.01.2375.024; Thu, 5 May 2022 20:46:40 +0800
From: "Wubo (lana)" <lana.wubo@huawei.com>
To: Greg Mirsky <gregimirsky@gmail.com>, 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" <draft-ietf-opsawg-yang-vpn-service-pm@ietf.org>
Thread-Topic: [ippm] Heads up on draft-ietf-opsawg-yang-vpn-service-pm
Thread-Index: AQHYXzARZVaO5UEziUqPDjHy7vttFa0QO6yg
Date: Thu, 05 May 2022 12:46:40 +0000
Message-ID: <935f25105da8466883da5a699b0b71f0@huawei.com>
References: <09bc01d85c12$c6906c30$53b14490$@olddog.co.uk> <CA+RyBmVQv-cEPjAsY7_gGhjj9Hdq1RmA2Km8w49k7_Xd5-ajzA@mail.gmail.com>
In-Reply-To: <CA+RyBmVQv-cEPjAsY7_gGhjj9Hdq1RmA2Km8w49k7_Xd5-ajzA@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.98.73]
Content-Type: multipart/alternative; boundary="_000_935f25105da8466883da5a699b0b71f0huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/Ve6ZCIcOcS4SsXq5LCludbEx4kA>
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: Thu, 05 May 2022 12:47:18 -0000

Hi Greg,

Thanks for the comments. STAMP referenced as RFC 8762 has been added as one of PM measurement protocol.
Please be aware this model is a network model and does not specifies the details of STAMP.
Please check whether rev-08 addresses your concerns:
  https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-yang-vpn-service-pm-08

Thanks,
Bo
From: Greg Mirsky [mailto:gregimirsky@gmail.com]
Sent: Wednesday, May 4, 2022 4:54 AM
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
Subject: Re: [ippm] Heads up on draft-ietf-opsawg-yang-vpn-service-pm

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<mailto: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<mailto:ippm@ietf.org>
https://www.ietf.org/mailman/listinfo/ippm