Re: [bess] review of draft-www-bess-yang-vpn-service-pm

wangzitao <wangzitao@huawei.com> Mon, 17 June 2019 09:40 UTC

Return-Path: <wangzitao@huawei.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 858F81200E0 for <bess@ietfa.amsl.com>; Mon, 17 Jun 2019 02:40:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.19
X-Spam-Level:
X-Spam-Status: No, score=-4.19 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] 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 PI89e4zrSyjN for <bess@ietfa.amsl.com>; Mon, 17 Jun 2019 02:40:08 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C8C912009E for <bess@ietf.org>; Mon, 17 Jun 2019 02:40:08 -0700 (PDT)
Received: from lhreml703-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 07720D502EFFC87C9317 for <bess@ietf.org>; Mon, 17 Jun 2019 10:40:06 +0100 (IST)
Received: from DGGEMM422-HUB.china.huawei.com (10.1.198.39) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 17 Jun 2019 10:40:05 +0100
Received: from DGGEMM527-MBX.china.huawei.com ([169.254.6.167]) by dggemm422-hub.china.huawei.com ([10.1.198.39]) with mapi id 14.03.0439.000; Mon, 17 Jun 2019 17:37:46 +0800
From: wangzitao <wangzitao@huawei.com>
To: Xu honglei <xuhl.bri@chinatelecom.cn>, "bess@ietf.org" <bess@ietf.org>
Thread-Topic: [bess] review of draft-www-bess-yang-vpn-service-pm
Thread-Index: AdUk74m2nZ4aHoRRR8ehueMmU2liIw==
Date: Mon, 17 Jun 2019 09:37:46 +0000
Message-ID: <E6BC9BBCBCACC246846FC685F9FF41EA2DA00D74@DGGEMM527-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.134.142.117]
Content-Type: multipart/alternative; boundary="_000_E6BC9BBCBCACC246846FC685F9FF41EA2DA00D74DGGEMM527MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/QJO2bho8kVgDLhwkgcFaV76Y-N0>
Subject: Re: [bess] review of draft-www-bess-yang-vpn-service-pm
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jun 2019 09:40:12 -0000

Hi Honglei,

Thanks for the review comments. Please find my reply at [MW].

Best Regards!
-Michael

发件人: BESS [mailto:bess-bounces@ietf.org] 代表 Xu honglei
发送时间: 2019年6月17日 16:27
收件人: bess@ietf.org
主题: [bess] review of draft-www-bess-yang-vpn-service-pm

As abstract said:
“
This document defines a YANG model for
   Network and VPN Service Performance Monitoring that can be used to
   monitor and manage network performance on the topology at different
   layer or the overlay topology between VPN sites.
“
I believe YANG model described in this draft can be used to monitor network performance or can be used to monitor VPN performance.
  This two performance monitoring are two separate functionalities.
[MW]: Agree.

  Section 4 provide two layered topology which can be used to monitor network performance in the overlay topology and monitor in the service topology Separately which is good.
[MW]: Thanks.

  Section 6.1 describe network level parameter such as vpn topology, svc topo type, I think these network level parameters are not needed when monitoring network performance.
[MW]: The section 6.1 introduce how to augment the ietf-network model to support VPN performance monitoring.
For monitoring network performance, IMHO,  the section 6.1 can be ignored since the network-type and l3-topology-attributes have been defined in RFC8345 and RFC8346.

Please make this clear in the text.
[MW]: I’d like to add some text to introduce how to support network performance monitoring.


H.Xu
+86-010-5090-2313
+86-133-0116-8970
xuhl.bri@chinatelecom.cn<mailto:xuhl.bri@chinatelecom.cn>
----------------------------------------------------------------------------------------------------------------------
China Telecom Corporation Limited Beijing Research Institute
Southern Zone of Future Science City,
Beiqijia Town, Changping District,
Beijing, China
102209