[ippm] Extending TWAMP for Monitoring Service KPIs
Srivathsa Sarangapani <srivathsas@juniper.net> Mon, 18 July 2016 05:57 UTC
Return-Path: <srivathsas@juniper.net>
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 83DDA12B02A for <ippm@ietfa.amsl.com>; Sun, 17 Jul 2016 22:57:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level:
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.onmicrosoft.com
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 PxqYiZ6xYUZj for <ippm@ietfa.amsl.com>; Sun, 17 Jul 2016 22:57:42 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0121.outbound.protection.outlook.com [104.47.33.121]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE45012B011 for <ippm@ietf.org>; Sun, 17 Jul 2016 22:57:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=EUJQAxLIPowRwL8SBYhVgt9eV/99yp0OZE7vXisXb4Q=; b=fDGBlUlRiXRoiIhoMxMLqXWMNguIr9FuP4ITXk8oRAx/iVR/WO5fgScoeo7/Whc9vXqW+o5hkK54QFTLMopvKRx9ta/92l4hYlh/KdywWrEpnktg7UGQ5NewRo6/iNWRCD9PTbElw4xYZo8dHiqmN5hp50h644QLzvnAhN3No8I=
Received: from BY2PR0501MB2133.namprd05.prod.outlook.com (10.163.198.19) by BLUPR05MB933.namprd05.prod.outlook.com (10.255.190.11) with Microsoft SMTP Server (TLS) id 15.1.539.6; Mon, 18 Jul 2016 05:57:39 +0000
Received: from BY2PR0501MB2133.namprd05.prod.outlook.com ([10.163.198.19]) by BY2PR0501MB2133.namprd05.prod.outlook.com ([10.163.198.19]) with mapi id 15.01.0539.019; Mon, 18 Jul 2016 05:57:38 +0000
From: Srivathsa Sarangapani <srivathsas@juniper.net>
To: IETF IPPM WG <ippm@ietf.org>
Thread-Topic: Extending TWAMP for Monitoring Service KPIs
Thread-Index: AQHR4LlJs7ZNvrtoBUGJaILAXRFapg==
Date: Mon, 18 Jul 2016 05:57:38 +0000
Message-ID: <0BEE6422-CA88-457A-B651-66C2DE417D16@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.18.0.160709
authentication-results: spf=none (sender IP is ) smtp.mailfrom=srivathsas@juniper.net;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [116.197.184.13]
x-ms-office365-filtering-correlation-id: 3ce866ed-4cad-4820-69c2-08d3aed06c8e
x-microsoft-exchange-diagnostics: 1; BLUPR05MB933; 6:6AKYwUoy0V0pFR97WYosMPAHoN3B9aQdGgQtbYGk2dAq61awBrMx77uc0ux2Wn1xTfP4ID2T3AKBEGbPqO1hotSlLqoEz69ueUJAzloktvL9zkXbn5dfEiCL5BGitf1nYr5h4JI/8olt7F1dfJVPsgpykK2PcOYt638joAA7Hq9JA+iSgvZ05MdLiyOWGKrCSaK9oKJrvbmwzKUGn7p34n4W9DmY116R/UOCVI7vl5cG8dGUXZoLF/ssL0uKvnySHd/yL2+qcwpTlA5rKMZ37L7dPGXj5UyczDePv2r/NRmq5wELNnJ2RX62WCGsxjKNr3wzwWdh53MvvVm0mQOdMg==; 5:hgTcKbxFVO4uUOrIq/UbvccyHrXLkovtD/rlgfRWALxh/KU9BtsdfLjpWQJf7T3IotxjQZYRoVtBQ8ZuzXEtrFTFIRWlUh2YFYDy/X8EtSK+BijMQ0zmoAkbK2kPHQpS0qOwfDX8SbzBQUY7p499jg==; 24:YMeoGEq2ESaiiu6ZEcBVRds7KnqgFufmeRJbOG7oezWf9BdYjbkFBNGfKQMD3zJ7myY2QZUBy4GtddXQYKh4SHl9a8uB2qcVCqAplYmbBSE=; 7:/S23+isvjqeLpgWSX07XenUILOUQbnwsfFDxKO+My3crqPPv4wyu0q4XOxES7uF3BYKja9EImE6wai76iy+7zx2dSax9/RjXER6KTstB9KUN2R3g6b/xwo1B39k6qBeYhtcccG4+myF6LrM7THyJp8Jw8MfxmJJscnoJWOz/CXlpLequIOfaSbRhJyHlqRYLflpNdVBlecxoEqF2M18rfi7m8wEJ3FzaQcxi9mrqfRNmlW7zUN1mXPyD0a0vYZzq
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR05MB933;
x-microsoft-antispam-prvs: <BLUPR05MB933C7326B0CE35C707D5F49D6360@BLUPR05MB933.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(72170088055959)(120809045254105)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026); SRVR:BLUPR05MB933; BCL:0; PCL:0; RULEID:; SRVR:BLUPR05MB933;
x-forefront-prvs: 00073DB75F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(189002)(199003)(377424004)(53754006)(81156014)(189998001)(33656002)(83716003)(19580395003)(2906002)(82746002)(7906003)(4326007)(16236675004)(7736002)(19625215002)(19300405004)(110136002)(87936001)(81166006)(83506001)(2900100001)(54356999)(50986999)(86362001)(68736007)(97736004)(15975445007)(4001350100001)(106356001)(3660700001)(105586002)(101416001)(7846002)(3280700002)(10400500002)(122556002)(9326002)(92566002)(77096005)(106116001)(8676002)(8936002)(6116002)(19617315012)(229853001)(36756003)(66066001)(3846002)(99286002)(586003)(5002640100001)(102836003)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR05MB933; H:BY2PR0501MB2133.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_0BEE6422CA88457AB65166C2DE417D16junipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Jul 2016 05:57:38.5493 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR05MB933
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/b6wf1LUkCy7i3_tjsVY9WE35ybg>
Cc: Peyush Gupta <peyushg@juniper.net>
Subject: [ippm] Extending TWAMP for Monitoring Service KPIs
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: Mon, 18 Jul 2016 05:57:44 -0000
Hi All, New versions of the TWAMP Service Monitoring extension drafts are being posted after addressing the comments given by Greg, Qin and others in the mailing list. 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: 02 Title: Monitoring Service KPIs using TWAMP - Methodology Document date: 2016-07-17 Group: Individual Submission Pages: 20 URL: https://www.ietf.org/internet-drafts/draft-spv-ippm-monitor-methodology-services-kpi-02.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-02 Diff: https://www.ietf.org/rfcdiff?url2=draft-spv-ippm-monitor-methodology-services-kpi-02 Abstract: The TWAMP protocol provides a common architecture for two way measurements in the IP network. However IP network performance are also affected by a set of L4-L7 service deployed in the network. Monitoring of these service performance in the IP network also plays a vital role in network optimization and application layer traffic optimization. This capability is not supported by the existing TWAMP protocol. In this document, we extend TWAMP protocol to support service performance monitoring and service KPIs calculation. Some of the existing fields in the TWAMP protocol are extended to support new modes 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). Services here ranging from Layer 4 to Layer 7 services,such as 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. There is a separate Draft[I.D-spv-ippm-monitor-implementation- services-kpi] that talks about implementation of monitoring these KPIs in the network using TWAMP. Monitoring of these KPIs in the service plane with in a network play a vital role in optimum usage of network resources and improving the overall performance and capacity. Name: draft-spv-ippm-monitor-implementation-services-kpi Revision: 02 Title: KPI Metrics for Service Monitoring using TWAMP Document date: 2016-07-17 Group: Individual Submission Pages: 9 URL: https://www.ietf.org/internet-drafts/draft-spv-ippm-monitor-implementation-services-kpi-02.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-02 Diff: https://www.ietf.org/rfcdiff?url2=draft-spv-ippm-monitor-implementation-services-kpi-02 Abstract: 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. Service latency is defined as the time spent by the packet when it is injected in the service module or service card till the time, serviced packet is received back by the TWAMP server. TWAMP server records the timestamp of the packet when it is injected into the service module and then again record the timestamp when it receives the packet afer service is applied in the data plane. Application Liveliness detection means whether the application is up and running in the network. In case you want to monitor the http application or the dns server and verify if they are up and running, this method is applicable. The implementation can be used for liveliness detection of any service in the network. — Regards, Vathsa
- Re: [ippm] Extending TWAMP for Monitoring Service… P Muthu Arul Mozhi
- Re: [ippm] Extending TWAMP for Monitoring Service… Gregory Mirsky
- Re: [ippm] Extending TWAMP for Monitoring Service… Srivathsa Sarangapani
- Re: [ippm] Extending TWAMP for Monitoring Service… P Muthu Arul Mozhi
- Re: [ippm] Extending TWAMP for Monitoring Service… Srivathsa Sarangapani
- Re: [ippm] Extending TWAMP for Monitoring Service… P Muthu Arul Mozhi
- Re: [ippm] Extending TWAMP for Monitoring Service… Srivathsa Sarangapani
- Re: [ippm] Extending TWAMP for Monitoring Service… P Muthu Arul Mozhi
- Re: [ippm] Extending TWAMP for Monitoring Service… Srivathsa Sarangapani
- Re: [ippm] Extending TWAMP for Monitoring Service… P Muthu Arul Mozhi
- [ippm] Extending TWAMP for Monitoring Service KPIs Srivathsa Sarangapani
- Re: [ippm] Extending TWAMP for Monitoring Service… P Muthu Arul Mozhi
- Re: [ippm] Extending TWAMP for Monitoring Service… Srivathsa Sarangapani
- Re: [ippm] Extending TWAMP for Monitoring Service… Srivathsa Sarangapani