IP Performance Metrics (ippm) ----------------------------- Charter Last Modified: 2007-12-17 Current Status: Active Working Group Chair(s): Matthew Zekauskas Henk Uijterwaal Transport Area Director(s): Magnus Westerlund Lars Eggert Transport Area Advisor: Lars Eggert Technical Advisor(s): Andy Bierman Mailing Lists: General Discussion:ippm@ietf.org To Subscribe: https://www1.ietf.org/mailman/listinfo/ippm In Body: subscribe Archive: http://www.ietf.org/mail-archive/web/ippm/index.html Description of Working Group: Note: Andy Bierman serves as MIB advisor. The IPPM WG will develop a set of standard metrics that can be applied to the quality, performance, and reliability of Internet data delivery services. These metrics will be designed such that they can be performed by network operators, end users, or independent testing groups. It is important that the metrics not represent a value judgment (i.e. define "good" and "bad"), but rather provide unbiased quantitative measures of performance. Functions peripheral to Internet data delivery services, such as NOC/NIC services, are beyond the scope of this working group. The IPPM WG will produce documents that define specific metrics and procedures for accurately measuring and documenting these metrics. The metrics are: - connectivity - one-way delay and loss - round-trip delay and loss - delay variation - loss patterns - packet reordering - bulk transport capacity - link bandwidth capacity This is the cumulative set, including the metricsalready completed and published. The working group will closely review and then be guided by an IESG document on how metrics advance along the standards track within the IETF. This document will also be relevant to the work of the benchmarking working group (BMWG). The first draft of this document was discussed at IETF 51. Additionally, the WG will produce Proposed Standard AS documents, comparable to applicability statements in RFC 2026, that will focus on procedures for measuring the individual metrics and how these metrics characterize features that are important to different service classes, such as bulk transport, periodic streams, or multimedia streams. It is specifically out of scope for this working group to actually characterize traffic, for example to characterize a voice-over-IP stream. Each AS document will discuss the performance characteristics that are pertinent to a specified service class; clearly identify the set of metrics that aid in the description of those characteristics; specify the methodologies required to collect said metrics; and lastly, present the requirements for the common, unambiguous reporting of testing results. Specific topics of these AS documents must be approved by the Area Directors as charter additions. The WG will produce a protocol to enable communication among test equipment that implements the one-way metrics. The intent is to create a protocol that provides a base level of functionality that will allow different manufacturer's equipment that implements the metrics according to a standard to interoperate. A protocol requirements document will guide the protocol design. The WG will also produce a MIB to retrieve the results of IPPM metrics, such as one-way delay and loss, to facilitate the communication of metrics to existing network management systems. Thus, the group will create a MIB that contains predominantly read only variables. If, after the protocol requirements document is finished, the group decides that it is appropriate to add variables that control the underlying measurements that the metrics report, such a control structure may be added as a separate document, subject to review by the IESG. The intent of the WG is to cooperate with other appropriate standards bodies and forums (such as T1A1.3, ITU-T SG 12 and SG 13) to promote consistent approaches and metrics. Within the IETF process, IPPM metrics definitions will be subject to as rigorous a scrutiny for usefulness, clarity, and accuracy as other protocol standards. The IPPM WG will interact with other areas of IETF activity whose scope intersect with the requirement of these specific metrics. These include working groups such as BMWG, RMONMIB, and TEWG. Goals and Milestones: Done Submit drafts of standard metrics for connectivity and treno-bulk-throughput. Done Submit a framework document describing terms and notions used in the IPPM effort, and the creation of metrics by the working group to IESG for publication as an Informational RFC. Done Submit documents on delay and loss to IESG for publication as Informational RFCs. Done Submit a document on connectivity to IESG for publication as an Informational RFC. Done Submit a document on bulk-throughput to IESG for publication as an Informational RFC. Done Submit draft on loss pattern sample metrics to the IESG for publication as an Informational RFC. Done Submit draft on metrics for periodic streams to the IESG for publication as a Proposed Standard RFC. Done Submit draft on IP delay variation to the IESG for publication as a Proposed Standard RFC. Done First draft for AS on one-way delay and loss. Done Submit draft on One-Way Active Measurement Protocol Requirements to the IESG for consideration as an Informational RFC. Done Create initial draft on a MIB for reporting IPPM metrics. Done Create initial draft on a packet reordering metric. Done Create draft on a One-Way Active Measurement Protocol that satisfies the requirements document. Done Submit draft on the One-Way Active Measurement Protocol to the IESG for consideration as a PS. Done Submit draft on implementation reports for RFCs 2678-2681 to the IESG Done Submit initial draft on framework for Composition and Aggregation Metrics Done Submit draft on the One-Way Active Measurement Protocol to the IESG for consideration as a PS Done Submit draft on a packet reordering metric to the IESG for Proposed Standard Done Submit initial applicability statement for the IPPM and ITU Jitter Measurements to the WG Done Submit link bandwidth capacity definitions draft to the IESG, for consideration as an Informational RFC Aug 2006 Submit draft on spatial composition of metrics to the IESG Aug 2006 Submit draft on Temporal Aggregation of Metrics to the IESG Aug 2006 Submit draft on spatial decomposition and multicast metrics to the IESG Done Submit draft on storing results of traceroute measurements to the IESG May 2007 Submit draft on Two-way active measurements protocol (TWAMP) to the IESG for consideration as proposed standard Dec 2007 Develop new charter text Jul 2008 Delay Variation Applicability Statement (Informational) to IESG Review Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- Jun 2005 May 2007 Defining Network Capacity Nov 2005 Dec 2007 A Two-way Active Measurement Protocol (TWAMP) Jan 2006 Feb 2008 IP Performance Metrics (IPPM) for spatial and multicast Feb 2006 Nov 2007 Spatial Composition of Metrics Feb 2006 Feb 2008 Framework for Metric Composition Jun 2006 Dec 2007 Information Model and XML Data Model for Traceroute Measurements Apr 2007 Feb 2008 A One-Way Packet Duplication Metric for IPPM Request For Comments: RFC Stat Published Title ------- -- ----------- ------------------------------------ RFC2330 I May 1998 Framework for IP Performance Metrics RFC2678 E Feb 1999 IPPM Metrics for Measuring Connectivity RFC2679 PS Sep 1999 A One-way Delay Metric for IPPM RFC2680 PS Sep 1999 A One-way Packet Loss Metric for IPPM RFC2681 PS Sep 1999 A Round-trip Delay Metric for IPPM RFC3148 I Aug 2001 A Framework for Defining Empirical Bulk Transfer Capacity Metrics RFC3357 I Aug 2002 One-way Loss Pattern Sample Metrics RFC3393 PS Nov 2002 IP Packet Delay Variation Metric for IPPM RFC3432 PS Dec 2002 Network performance measurement for periodic streams RFC3763 I May 2004 A One-way Active Measurement Protocol Requirements RFC4148BCP Aug 2005 IP Performance Metrics (IPPM) metrics registry RFC4656 PS Sep 2006 A One-way Active Measurement Protocol (OWAMP) RFC4737 PS Nov 2006 Packet Reordering Metrics