Re: [bess] I-D Action: draft-www-bess-yang-vpn-service-pm-06.txt
Qin Wu <bill.wu@huawei.com> Thu, 30 April 2020 07:00 UTC
Return-Path: <bill.wu@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 436F33A09BB; Thu, 30 Apr 2020 00:00:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.82, SPF_PASS=-0.001, URIBL_BLOCKED=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 Lfm_dBFqbv7S; Thu, 30 Apr 2020 00:00:13 -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 ADB803A09B4; Thu, 30 Apr 2020 00:00:12 -0700 (PDT)
Received: from lhreml730-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 8D428ED95DB5F581EF66; Thu, 30 Apr 2020 08:00:10 +0100 (IST)
Received: from lhreml730-chm.china.huawei.com (10.201.108.81) by lhreml730-chm.china.huawei.com (10.201.108.81) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Thu, 30 Apr 2020 08:00:10 +0100
Received: from DGGEML424-HUB.china.huawei.com (10.1.199.41) by lhreml730-chm.china.huawei.com (10.201.108.81) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Thu, 30 Apr 2020 08:00:10 +0100
Received: from DGGEML531-MBS.china.huawei.com ([169.254.5.240]) by dggeml424-hub.china.huawei.com ([10.1.199.41]) with mapi id 14.03.0487.000; Thu, 30 Apr 2020 15:00:06 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "slitkows.ietf@gmail.com" <slitkows.ietf@gmail.com>, "bess@ietf.org" <bess@ietf.org>
CC: "Mankamana Mishra (mankamis)" <mankamis@cisco.com>, "bess-chairs@ietf.org" <bess-chairs@ietf.org>
Thread-Topic: I-D Action: draft-www-bess-yang-vpn-service-pm-06.txt
Thread-Index: AdYeu/4in/t+P9bRTbO/mHNOyqV+qA==
Date: Thu, 30 Apr 2020 07:00:06 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAAD662019@dggeml531-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.33.123]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/tiwd2jCRciY_gKx2oIWIPiix_v0>
Subject: Re: [bess] I-D Action: draft-www-bess-yang-vpn-service-pm-06.txt
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: Thu, 30 Apr 2020 07:00:16 -0000
Stephane: Thanks for comments in BESS interim meeting, Your comments is more about whether this document defines new metrics or mechanisms for measuring performance? I think the answer is no, but the document doesn’t make that clear. This document make use of metrics and structures defined elsewhere. There are import clauses, but the text could be clearer on this point. Here is the proposed change to abstract and introduction section: Abstract OLD This model is designed as an augmentation to the network topology YANG data model defined in RFC8345. NEW This document does not define metrics for network performance or mechanisms for measuring network performance. The YANG model defined in this document is designed as an augmentation to the network topology YANG model defined in RFC 8345 and draws on relevant YANG types defined in RFC 6991, RFC 8299, RFC 8345, and RFC 8532. END Introduction OLD Three types of VPN service topologies are supported in [RFC8299]: "any to any", "hub and spoke", and "hub and spoke disjoint". These VPN topology types can be used to describe how VPN sites communicate with each other. This document defines a YANG Model for both Network Performance Monitoring and VPN Service Performance Monitoring (see Section 2.2.4 of [RFC4176]) that can be used to monitor and manage network Performance on the topology at higher layer or the service topology between VPN sites. The model is designed as an augmentation to the network topology YANG data model defined in [RFC8345]. NEW [RFC8299] defines a YANG model for L3VPN Service Delivery. Three types of VPN service topologies are supported in [RFC8299]: "any to any", "hub and spoke", and "hub and spoke disjoint". These VPN topology types can be used to describe how VPN sites communicate with each other. [RFC4176] provides a framework for L3VPN operations and management. Section 2.2.4 of that document describes performance management. This document defines a YANG Model for both network performance monitoring and VPN service performance monitoring that can be used to monitor and manage network performance on the topology at higher layer or the service topology between VPN sites. This document does not define metrics for network performance or mechanisms for measuring network performance. The YANG model defined in this document is designed as an augmentation to the network topology YANG model defined in [RFC8345] and draws on relevant YANG types defined in [RFC6991], [RFC8299], [RFC8345], and [RFC8532]. END Let me if these changes address your comments. -Qin -----邮件原件----- 发件人: BESS [mailto:bess-bounces@ietf.org] 代表 Qin Wu 发送时间: 2020年4月22日 16:44 收件人: bess@ietf.org 抄送: Oscar González de Dios <oscar.gonzalezdedios@telefonica.com>; mohamed.boucadair@orange.com 主题: Re: [bess] I-D Action: draft-www-bess-yang-vpn-service-pm-06.txt Hi, folks: Here is the update of draft-www-bess-yang-vpn-service-pm, the version is v-06, https://datatracker.ietf.org/doc/html/draft-www-bess-yang-vpn-service-pm-06 the main changes include: 1. Add vpn-summary-statistis related to vpn route at the network level. 2.Add reference time and measurement interval associated with performance measurement data 3.Replace average-delay-value at the link level with low-delay-percentile, middle-delay-percentile and high-delay-percentile 4.Replace average-jitter-value at the link level with low-jitter-percentile, middle-jitter-percentile and high-jitter-percentile 5.Add low-percentile, middle-percentile, high-percentile at the network level Your comments and suggestions are welcome. -Qin -----邮件原件----- 发件人: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] 代表 internet-drafts@ietf.org 发送时间: 2020年4月22日 16:32 收件人: i-d-announce@ietf.org 主题: I-D Action: draft-www-bess-yang-vpn-service-pm-06.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : A YANG Model for Network and VPN Service Performance Monitoring Authors : Qin Wu Mohamed Boucadair Oscar Gonzalez de Dios Bin Wen Change Liu Honglei Xu Filename : draft-www-bess-yang-vpn-service-pm-06.txt Pages : 29 Date : 2020-04-22 Abstract: The data model defined in RFC8345 introduces vertical layering relationships between networks that can be augmented to cover network/service topologies. This document defines a YANG model for both Network Performance Monitoring and VPN Service Performance Monitoring that can be used to monitor and manage network performance on the topology at higher layer or the service topology between VPN sites. This model is designed as an augmentation to the network topology YANG data model defined in RFC8345. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-www-bess-yang-vpn-service-pm/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-www-bess-yang-vpn-service-pm-06 https://datatracker.ietf.org/doc/html/draft-www-bess-yang-vpn-service-pm-06 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-www-bess-yang-vpn-service-pm-06 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt _______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess