Re: [ippm] TWAMP Service Monitoring Extension
Qin Wu <bill.wu@huawei.com> Tue, 28 June 2016 07:22 UTC
Return-Path: <bill.wu@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 5C55112B048 for <ippm@ietfa.amsl.com>; Tue, 28 Jun 2016 00:22:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.646
X-Spam-Level:
X-Spam-Status: No, score=-5.646 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=unavailable 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 F3P5ZOer4vr9 for <ippm@ietfa.amsl.com>; Tue, 28 Jun 2016 00:22:45 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54CE912DAFD for <ippm@ietf.org>; Tue, 28 Jun 2016 00:15:52 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml702-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CRR30240; Tue, 28 Jun 2016 07:15:47 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml702-cah.china.huawei.com (10.201.5.99) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 28 Jun 2016 08:15:36 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.81]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Tue, 28 Jun 2016 15:15:33 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Srivathsa Sarangapani <srivathsas@juniper.net>, IETF IPPM WG <ippm@ietf.org>
Thread-Topic: TWAMP Service Monitoring Extension
Thread-Index: AQHR0OF00ei/it556k2N2qn8plu0YJ/+ZpxA
Date: Tue, 28 Jun 2016 07:15:32 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA85363642@nkgeml513-mbx.china.huawei.com>
References: <356EC78D-6A1E-42F0-A37A-230E4734B17C@juniper.net>
In-Reply-To: <356EC78D-6A1E-42F0-A37A-230E4734B17C@juniper.net>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.79.112]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA85363642nkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090202.57722424.00BB, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.81, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 6520e79ce60e5ea6d3405b912fc3ea07
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/dU3CoIGsalU5sPhqIn-HaDQH8fk>
Cc: Peyush Gupta <peyushg@juniper.net>
Subject: Re: [ippm] TWAMP Service Monitoring Extension
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.17
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, 28 Jun 2016 07:22:47 -0000
Hi,Sri: Thanks for your update to these two drafts, I have read these two drafts and feel the mechanisms proposed in this draft and the metrics defined in this draft are very useful in Network optimization and can also help us provide better network planning and dimension. The most important is this draft provide value added service Performance monitoring which complementary to network performance monitoring and can help us measure end to end network performance and provide better network visibility. Here are few comments/suggestion to first document: draft-spv-ippm-monitor-methodology-services-kpi-01 1.If I read correctly, these two drafts below, one is about TWAMP extension for Service KPIs Monitoring, the other is about Metric Definition for Service KPIs Monitoring. In the first draft, a new framework is proposed for service KPIs monitoring, which adopts the similar logical model for TWAMP. I would suggest the title of draft-spv-ippm-monitor-methodology-services-kpi-01 can be rephrased a little bit to reflect the difference as I mentioned above. 2.I think this draft more focuses on TWAMP protocol extension for service KPIs monitoring while draft-spv-ippm-monitor-implementation-services-kpi-01 focus on metric definition, the methodology should be part of the draft-spv-ippm-monitor-implementation-services-kpi-01, here is the proposed change to the abstract “ Monitoring of Service KPIs in the service plane with in a network play a vital role in network optimization and Network planning and dimension. In this document, we are introducing a new method to calculate services KPIs and Performance metrics in the network using TWAMP protocol. Services here is ranging from Layer 4 to Layer 7 services. Some of the examples are HTTP based services, Traffic load balancer, DPI, Video caching, real time streaming and IPSec. The KPIs MAY be service latency, liveliness of an application, number of flows and sessions per service, load balancer statistics. This draft proposes a TWAMP protocol extension for service level parameters monitoring in the real network. These service level parameters can be used to calculate service KPIs using Metric proposed in draft-spv-ippm-monitor-implementation-services-kpi. Some of the existing fields in the TWAMP protocol is extended to support new modes in the TWAMP protocol for calculating these KPIs. A set of new messages are added in the control protocol between TWAMP client (session sender) and the TWAMP server (session reflector). ” 3.Introduction section, paragraph 3: Do you require DPI, SFW, CGNAT support TWAMP protocol or TWAMP test message exchange? What role DPI play in the logical model? TWAMP server or session reflector? 4.Section 2, last paragraph: OLD TEXT “ The actual method to calculate the KPIs is discussed in a separate draft on implementation ” NEW TEXT: “ The actual method to calculate the KPIs is discussed in a separate Draft [I.D-spv-ippm-monitor-implementation-services-kpi] ” 5.Section 3, 3rd paragraph: I believe the service messages KPI-Monitor-IND and KPI-Monitor-ACK are exchanged between Session Sender and Session Reflector instead of between Control-Client and Session reflector unless you require Control-Client is collocated with Session Sender and TWAMP Server is collocated with Session Reflector? 6.Section, 3 rd paragraph, last sentence It is not clear which two sets of messages you are referred to, suggest the following change OLD TEXT “ These two sets of messages will be repeated for each of the services that Server can monitor. ” NEW TEXT “ This pair of two messages will be repeated for each of the services that Server can monitor. ” 7. section 7 s/ anthenticated/ authenticated Here are a few comments on the second draft-spv-ippm-monitor-implementation-services-kpi 1.Suggest a few change to the 1st paragraph of the abstract OLD TEXT: “ We are using a new method to calculate services KPIs and metrics in the network using TWAMP protocol. This draft outlines the implementation of the service KPIs and there use cases in the service plane in the network. The KPIs discussed in this draft include Service Latency and Application Liveliness detection. ” NEW TEXT: “ We are using a new method to calculate services KPIs and performance metrics in the network using TWAMP protocol. This draft Defines the service KPIs Metrics and outlines use cases in the service plane for these metrics in the network. The KPIs discussed in this draft include Service Latency and Application Liveliness detection. ” 2.Section 1, 1st paragraph Does this draft require update RFC5357 since it update existing TWAMP-TEST packet format? 3.Section 2.2 OLD TEXT: “ Metric Description: This indicates the total latency introduced by the service for a data packet which is undergoing that service. Please note that the latency calculation in service agnostic. ” NEW TEXT: “ Metric Description: This indicates the total latency introduced by the service for a data packet which is undergoing specific treatment offered by that service node in the path. Please note that the latency calculation in service agnostic. ” 4.Section 5. s/ anthenticated/authenticated -Qin 发件人: ippm [mailto:ippm-bounces@ietf.org] 代表 Srivathsa Sarangapani 发送时间: 2016年6月28日 10:05 收件人: IETF IPPM WG 抄送: Peyush Gupta 主题: [ippm] TWAMP Service Monitoring Extension Hi All, New versions of the TWAMP Service Monitoring extension drafts are being posted after addressing the comments given by Al, Greg, Nalini, Qin and others in the last IETF meeting. We request you all to please go through the documents and reply back with your comments/suggestions. The documents are in the below path: Name: draft-spv-ippm-monitor-methodology-services-kpi Revision: 01 Title: Monitoring Service KPIs using TWAMP - Methodology URL: https://www.ietf.org/internet-drafts/draft-spv-ippm-monitor-methodology-services-kpi-01.txt Status: https://datatracker.ietf.org/doc/draft-spv-ippm-monitor-methodology-services-kpi/ Htmlized: https://tools.ietf.org/html/draft-spv-ippm-monitor-methodology-services-kpi-01 Diff: https://www.ietf.org/rfcdiff?url2=draft-spv-ippm-monitor-methodology-services-kpi-01 Name: draft-spv-ippm-monitor-implementation-services-kpi Revision: 01 Title: Monitoring Service KPIs using TWAMP - Implementation URL: https://www.ietf.org/internet-drafts/draft-spv-ippm-monitor-implementation-services-kpi-01.txt Status: https://datatracker.ietf.org/doc/draft-spv-ippm-monitor-implementation-services-kpi/ Htmlized: https://tools.ietf.org/html/draft-spv-ippm-monitor-implementation-services-kpi-01 Diff: https://www.ietf.org/rfcdiff?url2=draft-spv-ippm-monitor-implementation-services-kpi-01 — Regards, Vathsa
- Re: [ippm] TWAMP Service Monitoring Extension Qin Wu
- Re: [ippm] TWAMP Service Monitoring Extension Srivathsa Sarangapani
- Re: [ippm] TWAMP Service Monitoring Extension Qin Wu
- Re: [ippm] TWAMP Service Monitoring Extension Srivathsa Sarangapani
- Re: [ippm] TWAMP Service Monitoring Extension Qin Wu
- [ippm] TWAMP Service Monitoring Extension Srivathsa Sarangapani