draft-ietf-ippm-rt-loss-01.txt   draft-ietf-ippm-rt-loss-02.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 July 8, 2011 Intended status: Standards Track January 6, 2012
Expires: January 9, 2012 Expires: July 9, 2012
Round-trip Loss Metrics Round-trip Loss Metrics
draft-ietf-ippm-rt-loss-01 draft-ietf-ippm-rt-loss-02
Abstract Abstract
Many user applications (and the transport protocols that make them Many user applications (and the transport protocols that make them
possible) require two-way communications. To assess this capability, possible) require two-way communications. To assess this capability,
and to achieve test system simplicity, round-trip loss measurements and to achieve test system simplicity, round-trip loss measurements
are frequently conducted in practice. The Two-Way Active Measurement are frequently conducted in practice. The Two-Way Active Measurement
Protocol specified in RFC 5357 establishes a round-trip loss Protocol specified in RFC 5357 establishes a round-trip loss
measurement capability for the Internet. However, there is currently measurement capability for the Internet. However, there is currently
no metric specified according to the RFC 2330 framework. no metric specified according to the RFC 2330 framework.
skipping to change at page 1, line 45 skipping to change at page 1, line 45
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on January 9, 2012. This Internet-Draft will expire on July 9, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 50 skipping to change at page 2, line 50
8. Measurement Considerations and Calibration . . . . . . . . . . 10 8. Measurement Considerations and Calibration . . . . . . . . . . 10
9. Security Considerations . . . . . . . . . . . . . . . . . . . 10 9. Security Considerations . . . . . . . . . . . . . . . . . . . 10
9.1. Denial of Service Attacks . . . . . . . . . . . . . . . . 10 9.1. Denial of Service Attacks . . . . . . . . . . . . . . . . 10
9.2. User Data Confidentiality . . . . . . . . . . . . . . . . 10 9.2. User Data Confidentiality . . . . . . . . . . . . . . . . 10
9.3. Interference with the metrics . . . . . . . . . . . . . . 11 9.3. Interference with the metrics . . . . . . . . . . . . . . 11
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
12.1. Normative References . . . . . . . . . . . . . . . . . . . 11 12.1. Normative References . . . . . . . . . . . . . . . . . . . 11
12.2. Informative References . . . . . . . . . . . . . . . . . . 12 12.2. Informative References . . . . . . . . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 13 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
This memo defines a metric for round-trip loss on Internet paths. It This memo defines a metric for round-trip loss on Internet paths. It
builds on the notions and conventions introduced in the IP builds on the notions and conventions introduced in the IP
Performance Metrics (IPPM) framework [RFC2330]. Also, the Performance Metrics (IPPM) framework [RFC2330]. Also, the
specifications of the One-way Loss metric [RFC2680] and the Round- specifications of the One-way Loss metric [RFC2680] and the Round-
trip Delay metric [RFC2681] are frequently referenced and modified to trip Delay metric [RFC2681] are frequently referenced and modified to
match the round-trip circumstances addressed here. However, this match the round-trip circumstances addressed here. However, this
memo assumes that the reader is familiar with the references, and memo assumes that the reader is familiar with the references, and
skipping to change at page 11, line 25 skipping to change at page 11, line 25
may distort the measured performance. It may also be possible to may distort the measured performance. It may also be possible to
generate additional packets that appear to be part of the sample generate additional packets that appear to be part of the sample
metric. These additional packets are likely to perturb the results metric. These additional packets are likely to perturb the results
of the sample measurement. of the sample measurement.
To discourage the kind of interference mentioned above, packet To discourage the kind of interference mentioned above, packet
interference checks, such as cryptographic hash, may be used. interference checks, such as cryptographic hash, may be used.
10. IANA Considerations 10. IANA Considerations
Metrics defined in IETF are typically registered in the IANA IPPM Metrics previously defined in IETF were registered in the IANA IPPM
METRICS REGISTRY as described in initial version of the registry METRICS REGISTRY, however this process was discontinued when the
[RFC4148]. However, areas for improvement of this registry have been registry structure was found to be inadequate, and the registry was
identified, and the registry structure has to be revisited when there declared Obsolete [RFC6248].
is consensus to do so.
Therefore, the metrics in this draft may be considered for Although the metrics in this draft may be considered for some form of
registration in the future, and no IANA Action is requested at this registration in the future, no IANA Action is requested at this time.
time.
11. Acknowledgements 11. Acknowledgements
The author thanks Tiziano Ionta for his careful review of this memo, The author thanks Tiziano Ionta for his careful review of this memo,
primarily resulting in the development of measurement considerations primarily resulting in the development of measurement considerations
using TWAMP [RFC5357] as an example method. using TWAMP [RFC5357] as an example method.
12. References 12. References
12.1. Normative References 12.1. Normative References
skipping to change at page 12, line 24 skipping to change at page 12, line 22
Delay Metric for IPPM", RFC 2681, September 1999. Delay Metric for IPPM", RFC 2681, 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.
[RFC3432] Raisanen, V., Grotefeld, G., and A. Morton, "Network [RFC3432] Raisanen, V., Grotefeld, G., and A. Morton, "Network
performance measurement with periodic streams", RFC 3432, performance measurement with periodic streams", RFC 3432,
November 2002. November 2002.
[RFC4148] Stephan, E., "IP Performance Metrics (IPPM) Metrics
Registry", BCP 108, RFC 4148, August 2005.
[RFC4737] Morton, A., Ciavattone, L., Ramachandran, G., Shalunov, [RFC4737] Morton, A., Ciavattone, L., Ramachandran, G., Shalunov,
S., and J. Perser, "Packet Reordering Metrics", RFC 4737, S., and J. Perser, "Packet Reordering Metrics", RFC 4737,
November 2006. November 2006.
[RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J. [RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J.
Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)", Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)",
RFC 5357, October 2008. RFC 5357, October 2008.
[RFC5835] Morton, A. and S. Van den Berghe, "Framework for Metric
Composition", RFC 5835, April 2010.
12.2. Informative References 12.2. Informative References
[RFC5474] Duffield, N., Chiou, D., Claise, B., Greenberg, A.,
Grossglauser, M., and J. Rexford, "A Framework for Packet
Selection and Reporting", RFC 5474, March 2009.
[RFC5481] Morton, A. and B. Claise, "Packet Delay Variation [RFC5481] Morton, A. and B. Claise, "Packet Delay Variation
Applicability Statement", RFC 5481, March 2009. Applicability Statement", RFC 5481, March 2009.
[Stats] McGraw-Hill NY NY, "Introduction to the Theory of [RFC6248] Morton, A., "RFC 4148 and the IP Performance Metrics
Statistics, 3rd Edition,", 1974. (IPPM) Registry of Metrics Are Obsolete", RFC 6248,
April 2011.
Author's Address Author's Address
Al Morton Al Morton
AT&T Labs AT&T Labs
200 Laurel Avenue South 200 Laurel Avenue South
Middletown,, NJ 07748 Middletown,, NJ 07748
USA USA
Phone: +1 732 420 1571 Phone: +1 732 420 1571
 End of changes. 11 change blocks. 
26 lines changed or deleted 15 lines changed or added

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