Skip to main content

Monitoring Service KPIs using TWAMP
draft-sp-ippm-monitor-services-kpi-00

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Srivathsa Sarangapani , Peyush Gupta
Last updated 2015-10-07 (Latest revision 2015-06-29)
Replaced by draft-spv-ippm-monitor-methodology-services-kpi, draft-spv-ippm-monitor-implementation-services-kpi
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-spv-ippm-monitor-methodology-services-kpi, draft-spv-ippm-monitor-implementation-services-kpi
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

We are introducing a new method to calculate services KPIs and metrics in the network using TWAMP protocol. The services here ranging from subscriber aware services to security application, Traffic load balancing, content delivery, real time streaming and like.The KPIs discussed in this draft include Service Latency, Serviced Packets Count, Serviced Subscriber Count, Application Liveliness and Session load per Service. KPIs monitoring of these services therefore, play a vital role in optimum usage of network resources such as capacity and throughput. Once we have the attributes like service latency, the network topology can be chosen to provide better quality of experience to the end user. For different services, the attributes may vary and our design takes care of supporting different KPIs for different services model. Additionally, liveliness of application and servers can be monitored using this proposed solution.

Authors

Srivathsa Sarangapani
Peyush Gupta

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)