[ippm] About the draft-mhmcsfh-ippm-pam-00

liu.aihua@zte.com.cn Tue, 22 March 2022 00:36 UTC

Return-Path: <liu.aihua@zte.com.cn>
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 E14423A1C37 for <ippm@ietfa.amsl.com>; Mon, 21 Mar 2022 17:36:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
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 AaVxg8Tc3_sP for <ippm@ietfa.amsl.com>; Mon, 21 Mar 2022 17:36:03 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE8053A1C3B for <ippm@ietf.org>; Mon, 21 Mar 2022 17:36:01 -0700 (PDT)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4KMswb2PP0zBGB8T; Tue, 22 Mar 2022 08:35:59 +0800 (CST)
Received: from szxlzmapp02.zte.com.cn ([10.5.231.79]) by mse-fl2.zte.com.cn with SMTP id 22M0ZrwJ079023; Tue, 22 Mar 2022 08:35:53 +0800 (GMT-8) (envelope-from liu.aihua@zte.com.cn)
Received: from mapi (szxlzmapp04[null]) by mapi (Zmail) with MAPI id mid13; Tue, 22 Mar 2022 08:35:53 +0800 (CST)
Date: Tue, 22 Mar 2022 08:35:53 +0800
X-Zmail-TransId: 2b06623919e9ffffffffbe7-087f2
X-Mailer: Zmail v1.0
Message-ID: <202203220835530613991@zte.com.cn>
Mime-Version: 1.0
From: liu.aihua@zte.com.cn
To: gregimirsky@gmail.com, ippm@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 22M0ZrwJ079023
X-Fangmail-Gw-Spam-Type: 0
X-FangMail-Miltered: at cgslv5.04-192.168.250.137.novalocal with ID 623919EF.001 by FangMail milter!
X-FangMail-Envelope: 1647909359/4KMswb2PP0zBGB8T/623919EF.001/10.30.14.239/[10.30.14.239]/mse-fl2.zte.com.cn/<liu.aihua@zte.com.cn>
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 623919EF.001/4KMswb2PP0zBGB8T
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/DEVMyVTpQb1QM420Ew30jGRqss8>
Subject: [ippm] About the draft-mhmcsfh-ippm-pam-00
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: Tue, 22 Mar 2022 00:36:09 -0000

Hi Greg,


About the draft-mhmcsfh-ippm-pam-00, I have read it and have some comments as below:


I agree this draft is valuabe to evaluating the service quality of IP network, even there are many OAM tools but none provides the services "Precisicion Availablity Metrics" measurement


I think the service metrics usally are made for e2e than IP network only, so it needs an apprepiate method to split the e2e metrics into different domains, including IP network. But I don't sure this work whether if should be done in this draft


If the metrics are many SLOs combined, each SLO has its own measurement tools, we should evaluate them all with a comprehensive system? And the SLOs system catering the different services might be a little complicated, do you have some thoughts?


As we know, G.8261 mainly uses to TDM mechanism connection, but the Packet mechanism connection errors are burst normally, I sugguest the SEI interval and SEI packet counts also need to be configurable for different service types, such as CBR services and packet services.





Best regards,


Aihua