draft-ietf-ippm-spatial-composition-10.txt   draft-ietf-ippm-spatial-composition-11.txt 
Network Working Group A. Morton Network Working Group A. Morton
Internet-Draft AT&T Labs Internet-Draft AT&T Labs
Intended status: Standards Track E. Stephan Intended status: Standards Track E. Stephan
Expires: April 21, 2010 France Telecom Division R&D Expires: October 16, 2010 France Telecom Division R&D
October 18, 2009 April 14, 2010
Spatial Composition of Metrics Spatial Composition of Metrics
draft-ietf-ippm-spatial-composition-10 draft-ietf-ippm-spatial-composition-11
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 21, 2010.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract Abstract
This memo utilizes IPPM metrics that are applicable to both complete This memo utilizes IPPM metrics that are applicable to both complete
paths and sub-paths, and defines relationships to compose a complete paths and sub-paths, and defines relationships to compose a complete
path metric from the sub-path metrics with some accuracy w.r.t. the path metric from the sub-path metrics with some accuracy w.r.t. the
actual metrics. This is called Spatial Composition in RFC 2330. The actual metrics. This is called Spatial Composition in RFC 2330. The
memo refers to the Framework for Metric Composition, and provides memo refers to the Framework for Metric Composition, and provides
background and motivation for combining metrics to derive others. background and motivation for combining metrics to derive others.
The descriptions of several composed metrics and statistics follow. The descriptions of several composed metrics and statistics follow.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
In this memo, the characters "<=" should be read as "less than or In this memo, the characters "<=" should be read as "less than or
equal to" and ">=" as "greater than or equal to". equal to" and ">=" as "greater than or equal to".
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 16, 2010.
Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. Motivation . . . . . . . . . . . . . . . . . . . . . . . . 6 2.1. Motivation . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Scope and Application . . . . . . . . . . . . . . . . . . . . 6 3. Scope and Application . . . . . . . . . . . . . . . . . . . . 6
3.1. Scope of work . . . . . . . . . . . . . . . . . . . . . . 7 3.1. Scope of work . . . . . . . . . . . . . . . . . . . . . . 7
3.2. Application . . . . . . . . . . . . . . . . . . . . . . . 7 3.2. Application . . . . . . . . . . . . . . . . . . . . . . . 7
3.3. Incomplete Information . . . . . . . . . . . . . . . . . . 8 3.3. Incomplete Information . . . . . . . . . . . . . . . . . . 8
4. Common Specifications for Composed Metrics . . . . . . . . . . 8 4. Common Specifications for Composed Metrics . . . . . . . . . . 8
skipping to change at page 5, line 27 skipping to change at page 5, line 27
- Maurizio Molina <maurizio.molina@dante.org.uk> - Maurizio Molina <maurizio.molina@dante.org.uk>
- Lei Liang <L.Liang@surrey.ac.uk> - Lei Liang <L.Liang@surrey.ac.uk>
- Dave Hoeflin <dhoeflin@att.com> - Dave Hoeflin <dhoeflin@att.com>
2. Introduction 2. Introduction
The IPPM framework [RFC2330] describes two forms of metric The IPPM framework [RFC2330] describes two forms of metric
composition, spatial and temporal. The new composition framework composition, spatial and temporal. The new composition framework
[I-D.ietf-ippm-framework-compagg] expands and further qualifies these [RFC5835] expands and further qualifies these original forms into
original forms into three categories. This memo describes Spatial three categories. This memo describes Spatial Composition, one of
Composition, one of the categories of metrics under the umbrella of the categories of metrics under the umbrella of the composition
the composition framework. framework.
Spatial composition encompasses the definition of performance metrics Spatial composition encompasses the definition of performance metrics
that are applicable to a complete path, based on metrics collected on that are applicable to a complete path, based on metrics collected on
various sub-paths. various sub-paths.
The main purpose of this memo is to define the deterministic The main purpose of this memo is to define the deterministic
functions that yield the complete path metrics using metrics of the functions that yield the complete path metrics using metrics of the
sub-paths. The effectiveness of such metrics is dependent on their sub-paths. The effectiveness of such metrics is dependent on their
usefulness in analysis and applicability with practical measurement usefulness in analysis and applicability with practical measurement
methods. methods.
skipping to change at page 7, line 31 skipping to change at page 7, line 31
packets to support measurement). packets to support measurement).
We note a possibility: Using a complete path metric and all but one We note a possibility: Using a complete path metric and all but one
sub-path metric to infer the performance of the missing sub-path, sub-path metric to infer the performance of the missing sub-path,
especially when the "last" sub-path metric is missing. However, such especially when the "last" sub-path metric is missing. However, such
de-composition calculations, and the corresponding set of issues they de-composition calculations, and the corresponding set of issues they
raise, are beyond the scope of this memo. raise, are beyond the scope of this memo.
3.2. Application 3.2. Application
The new composition framework [I-D.ietf-ippm-framework-compagg] The new composition framework [RFC5835] requires the specification of
requires the specification of the applicable circumstances for each the applicable circumstances for each metric. In particular, each
metric. In particular, each section addresses whether the metric: section addresses whether the metric:
Requires the same test packets to traverse all sub-paths, or may use Requires the same test packets to traverse all sub-paths, or may use
similar packets sent and collected separately in each sub-path. similar packets sent and collected separately in each sub-path.
Requires homogeneity of measurement methodologies, or can allow a Requires homogeneity of measurement methodologies, or can allow a
degree of flexibility (e.g., active or passive methods produce the degree of flexibility (e.g., active or passive methods produce the
"same" metric). Also, the applicable sending streams will be "same" metric). Also, the applicable sending streams will be
specified, such as Poisson, Periodic, or both. specified, such as Poisson, Periodic, or both.
Needs information or access that will only be available within an Needs information or access that will only be available within an
skipping to change at page 26, line 15 skipping to change at page 26, line 15
Unicast concepts are stable (or maybe appear in a separate draft)? Unicast concepts are stable (or maybe appear in a separate draft)?
>>>>>>>>>>>>>>>>RESOLUTION: No and Yes. >>>>>>>>>>>>>>>>RESOLUTION: No and Yes.
12. Acknowledgements 12. Acknowledgements
13. References 13. References
13.1. Normative References 13.1. Normative References
[I-D.ietf-ippm-framework-compagg]
Morton, A., "Framework for Metric Composition",
draft-ietf-ippm-framework-compagg-08 (work in progress),
June 2009.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2330] Paxson, V., Almes, G., Mahdavi, J., and M. Mathis, [RFC2330] Paxson, V., Almes, G., Mahdavi, J., and M. Mathis,
"Framework for IP Performance Metrics", RFC 2330, "Framework for IP Performance Metrics", RFC 2330,
May 1998. May 1998.
[RFC2679] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way [RFC2679] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way
Delay Metric for IPPM", RFC 2679, September 1999. Delay Metric for IPPM", RFC 2679, September 1999.
[RFC2680] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way [RFC2680] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way
Packet Loss Metric for IPPM", RFC 2680, September 1999. Packet Loss Metric for IPPM", RFC 2680, September 1999.
[RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation [RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation
Metric for IP Performance Metrics (IPPM)", RFC 3393, Metric for IP Performance Metrics (IPPM)", RFC 3393,
November 2002. November 2002.
[RFC4148] Stephan, E., "IP Performance Metrics (IPPM) Metrics [RFC4148] Stephan, E., "IP Performance Metrics (IPPM) Metrics
Registry", BCP 108, RFC 4148, August 2005. Registry", BCP 108, RFC 4148, August 2005.
[RFC5835] Morton, A. and S. Van den Berghe, "Framework for Metric
Composition", RFC 5835, April 2010.
13.2. Informative References 13.2. Informative References
[I-D.ietf-ippm-multimetrics] [RFC5644] Stephan, E., Liang, L., and A. Morton, "IP Performance
Stephan, E., Liang, L., and A. Morton, "IP Performance Metrics (IPPM): Spatial and Multicast", RFC 5644,
Metrics (IPPM) for spatial and multicast", October 2009.
draft-ietf-ippm-multimetrics-12 (work in progress),
September 2009.
[Stats] McGraw-Hill NY NY, "Introduction to the Theory of [Stats] McGraw-Hill NY NY, "Introduction to the Theory of
Statistics, 3rd Edition,", 1974. Statistics, 3rd Edition,", 1974.
[Y.1540] ITU-T Recommendation Y.1540, "Internet protocol data [Y.1540] ITU-T Recommendation Y.1540, "Internet protocol data
communication service - IP packet transfer and communication service - IP packet transfer and
availability performance parameters", December 2002. availability performance parameters", November 2007.
[Y.1541] ITU-T Recommendation Y.1541, "Network Performance [Y.1541] ITU-T Recommendation Y.1541, "Network Performance
Objectives for IP-based Services", February 2006. Objectives for IP-based Services", February 2006.
Index Index
? ?
??? 14 ??? 14
Authors' Addresses Authors' Addresses
 End of changes. 9 change blocks. 
65 lines changed or deleted 60 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/