draft-ietf-ippm-multimetrics-10.txt   draft-ietf-ippm-multimetrics-11.txt 
Network Working Group E. Stephan Network Working Group E. Stephan
Internet-Draft France Telecom Internet-Draft France Telecom
Intended status: Standards Track L. Liang Intended status: Standards Track L. Liang
Expires: October 24, 2009 University of Surrey Expires: October 30, 2009 University of Surrey
A. Morton A. Morton
AT&T Labs AT&T Labs
April 22, 2009 April 28, 2009
IP Performance Metrics (IPPM) for spatial and multicast IP Performance Metrics (IPPM) for spatial and multicast
draft-ietf-ippm-multimetrics-10 draft-ietf-ippm-multimetrics-11
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. 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 Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 24, 2009. This Internet-Draft will expire on October 30, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 23 skipping to change at page 3, line 7
in multiparty communications (e.g., a multicast tree). in multiparty communications (e.g., a multicast tree).
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].
Table of Contents Table of Contents
1. Introduction and Scope . . . . . . . . . . . . . . . . . . . . 3 1. Introduction and Scope . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Brief Metric Descriptions . . . . . . . . . . . . . . . . . . 7 3. Brief Metric Descriptions . . . . . . . . . . . . . . . . . . 8
4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . 9 4. Motivations . . . . . . . . . . . . . . . . . . . . . . . . . 10
5. Spatial vector metrics definitions . . . . . . . . . . . . . . 11 5. Spatial vector metrics definitions . . . . . . . . . . . . . . 12
6. Spatial Segment Metrics Definitions . . . . . . . . . . . . . 18 6. Spatial Segment Metrics Definitions . . . . . . . . . . . . . 19
7. One-to-group metrics definitions . . . . . . . . . . . . . . . 23 7. One-to-group metrics definitions . . . . . . . . . . . . . . . 24
8. One-to-group Sample Statistics . . . . . . . . . . . . . . . . 26 8. One-to-group Sample Statistics . . . . . . . . . . . . . . . . 27
9. Measurement Methods: Scalability and Reporting . . . . . . . . 36 9. Measurement Methods: Scalability and Reporting . . . . . . . . 37
10. Manageability Considerations . . . . . . . . . . . . . . . . . 39 10. Manageability Considerations . . . . . . . . . . . . . . . . . 40
11. Security Considerations . . . . . . . . . . . . . . . . . . . 44 11. Security Considerations . . . . . . . . . . . . . . . . . . . 45
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 45 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 46
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 45 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 49 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 50
14.1. Normative References . . . . . . . . . . . . . . . . . . 49 14.1. Normative References . . . . . . . . . . . . . . . . . . 50
14.2. Informative References . . . . . . . . . . . . . . . . . 50 14.2. Informative References . . . . . . . . . . . . . . . . . 51
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 50 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 51
1. Introduction and Scope 1. Introduction and Scope
IETF has standardized IP Performance Metrics (IPPM) for measuring IETF has standardized IP Performance Metrics (IPPM) for measuring
end-to-end performance between two points. This memo defines two new end-to-end performance between two points. This memo defines two new
categories of metrics that extend the coverage to multiple categories of metrics that extend the coverage to multiple
measurement points. It defines spatial metrics for measuring the measurement points. It defines spatial metrics for measuring the
performance of segments of a source to destination path, and metrics performance of segments of a source to destination path, and metrics
for measuring the performance between a source and many destinations for measuring the performance between a source and many destinations
in multiparty communications (e.g., a multicast tree). in multiparty communications (e.g., a multicast tree).
 End of changes. 6 change blocks. 
22 lines changed or deleted 32 lines changed or added

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