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

"Xu honglei" <xuhl.bri@chinatelecom.cn> Mon, 17 June 2019 08:27 UTC

Return-Path: <xuhl.bri@chinatelecom.cn>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 30DC5120111 for <bess@ietfa.amsl.com>; Mon, 17 Jun 2019 01:27:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id qbHgpW8M1RXZ for <bess@ietfa.amsl.com>; Mon, 17 Jun 2019 01:27:37 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn []) by ietfa.amsl.com (Postfix) with ESMTP id 35D961200F1 for <bess@ietf.org>; Mon, 17 Jun 2019 01:27:37 -0700 (PDT)
Received: from clientip- (unknown []) by chinatelecom.cn (HERMES) with SMTP id 7424B2800C5; Mon, 17 Jun 2019 16:27:31 +0800 (CST)
X-189-SAVE-TO-SEND: xuhl.bri@chinatelecom.cn
Received: from EHLO ip<> ([]) by App0025 with ESMTP id 35b8dc41-e51d-4799-9bd9-cfa93e67dcab for bess@ietf.org; Mon Jun 17 16:27:33 2019
X-filter-score: filter<0>
X-Real-From: xuhl.bri@chinatelecom.cn
X-MEDUSA-Status: 0
From: Xu honglei <xuhl.bri@chinatelecom.cn>
To: bess@ietf.org
Date: Mon, 17 Jun 2019 16:27:29 +0800
Message-ID: <000401d524e6$829a5c90$87cf15b0$@chinatelecom.cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01D52529.90BED510"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AdUk5lGqgJO+rEdkRRaMEjw7vh8GxA==
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/RzclffQoGeXQsFIPYbAkwIDLv1M>
Subject: [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 08:27:40 -0000

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.

  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.

  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. Please make this clear in the text.






 <mailto:xuhl.bri@chinatelecom.cn> xuhl.bri@chinatelecom.cn


China Telecom Corporation Limited Beijing Research Institute

Southern Zone of Future Science City, 

Beiqijia Town, Changping District, 

Beijing, China