5560
PROPOSED STANDARD
A One-Way Packet Duplication Metric
Authors: H. Uijterwaal
Date: May 2009
Area: ops
Working Group: ippm
Stream: IETF
Updated by:
RFC 6248
Abstract
When a packet is sent from one host to the other, one normally expects that exactly one copy of the packet that was sent arrives at the destination. It is, however, possible that a packet is either lost or that multiple copies arrive.
In earlier work, a metric for packet loss was defined. This metric quantifies the case where a packet that is sent does not arrive at its destination within a reasonable time. In this memo, a metric for another case is defined: a packet is sent, but multiple copies arrive. The document also discusses streams and methods to summarize the results of streams. [STANDARDS-TRACK]
RFC 5560
PROPOSED STANDARD
Updated by: 6248
Network Working Group H. Uijterwaal
Request for Comments: 5560 RIPE NCC
Category: Standards Track May 2009
<span class="h1">A One-Way Packet Duplication Metric</span>
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract
When a packet is sent from one host to the other, one normally
expects that exactly one copy of the packet that was sent arrives at
the destination. It is, however, possible that a packet is either
lost or that multiple copies arrive.
In earlier work, a metric for packet loss was defined. This metric
quantifies the case where a packet that is sent does not arrive at
its destination within a reasonable time. In this memo, a metric for
another case is defined: a packet is sent, but multiple copies
arrive. The document also discusses streams and methods to summarize
the results of streams.
<span class="grey">Uijterwaal Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc5560">RFC 5560</a> Packet Duplication Metric May 2009</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
<a href="#section-1.1">1.1</a>. Requirements Notation ......................................<a href="#page-3">3</a>
<a href="#section-1.2">1.2</a>. Motivation .................................................<a href="#page-4">4</a>
<a href="#section-2">2</a>. A Singleton Definition for One-Way Packet Arrival Count .........<a href="#page-4">4</a>
<a href="#section-2.1">2.1</a>. Metric Name ................................................<a href="#page-4">4</a>
<a href="#section-2.2">2.2</a>. Metrics Parameters .........................................<a href="#page-4">4</a>
<a href="#section-2.3">2.3</a>. Metric Units ...............................................<a href="#page-4">4</a>
<a href="#section-2.4">2.4</a>. Definition .................................................<a href="#page-4">4</a>
<a href="#section-2.5">2.5</a>. Discussion .................................................<a href="#page-5">5</a>
<a href="#section-2.6">2.6</a>. Methodology ................................................<a href="#page-6">6</a>
<a href="#section-2.7">2.7</a>. Errors and Uncertainties ...................................<a href="#page-6">6</a>
<a href="#section-2.8">2.8</a>. Reporting the Metric .......................................<a href="#page-6">6</a>
<a href="#section-3">3</a>. A Singleton Definition for One-Way Packet Duplication ...........<a href="#page-6">6</a>
<a href="#section-3.1">3.1</a>. Metric Name ................................................<a href="#page-6">6</a>
<a href="#section-3.2">3.2</a>. Metrics Parameters .........................................<a href="#page-7">7</a>
<a href="#section-3.3">3.3</a>. Metric Units ...............................................<a href="#page-7">7</a>
<a href="#section-3.4">3.4</a>. Definition .................................................<a href="#page-7">7</a>
<a href="#section-3.5">3.5</a>. Discussion .................................................<a href="#page-7">7</a>
<a href="#section-4">4</a>. Definition for Samples for One-Way Packet Duplication ...........<a href="#page-7">7</a>
<a href="#section-4.1">4.1</a>. Poisson Streams ............................................<a href="#page-7">7</a>
<a href="#section-4.1.1">4.1.1</a>. Metric Name .........................................<a href="#page-7">7</a>
<a href="#section-4.1.2">4.1.2</a>. Metric Parameters ...................................<a href="#page-8">8</a>
<a href="#section-4.1.3">4.1.3</a>. Metric Units ........................................<a href="#page-8">8</a>
<a href="#section-4.1.4">4.1.4</a>. Definition ..........................................<a href="#page-8">8</a>
<a href="#section-4.1.5">4.1.5</a>. Methodology .........................................<a href="#page-8">8</a>
<a href="#section-4.1.6">4.1.6</a>. Errors and Uncertainties ............................<a href="#page-8">8</a>
<a href="#section-4.1.7">4.1.7</a>. Reporting the Metric ................................<a href="#page-8">8</a>
<a href="#section-4.2">4.2</a>. Periodic Streams ...........................................<a href="#page-9">9</a>
<a href="#section-4.2.1">4.2.1</a>. Metric Name .........................................<a href="#page-9">9</a>
<a href="#section-4.2.2">4.2.2</a>. Metric Parameters ...................................<a href="#page-9">9</a>
<a href="#section-4.2.3">4.2.3</a>. Metric Units ........................................<a href="#page-9">9</a>
<a href="#section-4.2.4">4.2.4</a>. Definition ..........................................<a href="#page-9">9</a>
<a href="#section-4.2.5">4.2.5</a>. Methodology .........................................<a href="#page-9">9</a>
<a href="#section-4.2.6">4.2.6</a>. Errors and uncertainties ............................<a href="#page-9">9</a>
<a href="#section-4.2.7">4.2.7</a>. Reporting the metric ...............................<a href="#page-10">10</a>
<a href="#section-5">5</a>. Some Statistics Definitions for One-Way Duplication ............<a href="#page-10">10</a>
<a href="#section-5.1">5.1</a>. Type-P-one-way-packet-duplication-fraction ................<a href="#page-10">10</a>
<a href="#section-5.2">5.2</a>. Type-P-one-way-replicated-packet-rate .....................<a href="#page-10">10</a>
<a href="#section-5.3">5.3</a>. Examples ..................................................<a href="#page-11">11</a>
<a href="#section-6">6</a>. Security Considerations ........................................<a href="#page-12">12</a>
<a href="#section-7">7</a>. IANA Considerations ............................................<a href="#page-12">12</a>
<a href="#section-8">8</a>. Acknowledgements ...............................................<a href="#page-13">13</a>
<a href="#section-9">9</a>. References .....................................................<a href="#page-13">13</a>
<a href="#section-9.1">9.1</a>. Normative References ......................................<a href="#page-13">13</a>
<a href="#section-9.2">9.2</a>. Informative References ....................................<a href="#page-13">13</a>
<span class="grey">Uijterwaal Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc5560">RFC 5560</a> Packet Duplication Metric May 2009</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document defines a metric for one-way packet duplication across
Internet paths. It builds on the IP Performance Metrics (IPPM)
Framework document [<a href="./rfc2330" title=""Framework for IP Performance Metrics"">RFC2330</a>]; the reader is assumed to be familiar
with that document.
This document follows the same structure as the document for one-way
packet loss [<a href="./rfc2680" title=""A One-way Packet Loss Metric for IPPM"">RFC2680</a>]; the reader is assumed to be familiar with that
document as well.
The structure of this memo is as follows:
o First, a singleton metric, called Type-P-one-way-packet-arrival-
count, is introduced to measure the number of arriving packets for
each packet sent.
o Then, a singleton metric, called Type-P-one-way-packet-
duplication, is defined to describe a single instance of packet
duplication.
o Next, this singleton metric is used to define samples, Type-P-one-
way-Packet-Duplication-Poisson-Stream and Type-P-one-way-Packet-
Duplication-Periodic-Stream. These are introduced to measure
duplication in a series of packets sent with either Poisson-
distributed [<a href="./rfc2680" title=""A One-way Packet Loss Metric for IPPM"">RFC2680</a>] or periodic [<a href="./rfc3432" title=""Network performance measurement with periodic streams"">RFC3432</a>] intervals between the
packets.
o Finally, statistics that summarize the properties of these samples
are introduced.
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Requirements Notation</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
Although <a href="./rfc2119">RFC 2119</a> was written with protocols in mind, the key words
are used in this document for similar reasons. They are used to
ensure the results of measurements from two different implementations
are comparable and to note instances when an implementation could
perturb the network.
<span class="grey">Uijterwaal Standards Track [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc5560">RFC 5560</a> Packet Duplication Metric May 2009</span>
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Motivation</span>
When a packet is sent from one host to the other, one normally
expects that exactly one copy of the packet that was sent arrives at
the destination. It is, however, possible that a packet is either
lost or that multiple copies arrive.
In earlier work, a metric for packet loss was defined [<a href="./rfc2680" title=""A One-way Packet Loss Metric for IPPM"">RFC2680</a>].
This metric distinguishes between cases where the packet arrives and
where the packet does not arrive within a reasonable time. In this
memo, a metric for a third outcome is defined: a single packet is
sent, but multiple copies arrive.
As this document describes a case similar to the one discussed in
[<a href="./rfc2680" title=""A One-way Packet Loss Metric for IPPM"">RFC2680</a>], all considerations from that document on timing and
accuracy apply.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. A Singleton Definition for One-Way Packet Arrival Count</span>
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Metric Name</span>
Type-P-one-way-packet-arrival-count
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Metrics Parameters</span>
o src, the IP address of a host
o dst, the IP address of a host
o T, the wire time of a packet at the source
o T0, the maximum waiting time for a packet to arrive at the
destination.
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Metric Units</span>
An integer number.
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Definition</span>
Two packets are considered identical if and only if:
o Both contain identical information fields (see <a href="#section-2.5">Section 2.5</a>). The
recipient thus could take either packet and use the data in an
application. The other packet does not contain any additional
information.
<span class="grey">Uijterwaal Standards Track [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc5560">RFC 5560</a> Packet Duplication Metric May 2009</span>
o Both packets appear to have been sent by one and the same host, to
one and the same destination. Hosts are identified by their IP
addresses.
The value of a Type-P-one-way-packet-arrival-count is a positive
integer number indicating the number of (uncorrupted and identical)
copies received by dst in the interval [T, T+T0] for a packet sent by
src at time T.
If a packet is sent, but it is lost or does not arrive in the
interval [T, T+T0], then the metric is undefined. Applications MAY
report an "impossible" value (for example, -1) to indicate this
condition instead of undefined.
If a packet is fragmented during transport and if, for whatever
reason, reassembly does not occur, then the packet will be deemed
lost. It is thus not included in the Type-P-one-way-packet-arrival-
count.
<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Discussion</span>
This metric counts the number of packets arriving for each packet
sent. The time-out value T0 SHOULD be set to a value when the
application could potentially still use the packet and would not
discard it automatically.
If this metric is used in parallel with the Packet Loss Metric
[<a href="./rfc2680" title=""A One-way Packet Loss Metric for IPPM"">RFC2680</a>], the value of T0 MUST be the same for both cases in order
to keep the results comparable.
The metric only counts packets that are not corrupted during
transmission and may have been resent automatically by lower layers
or intermediate devices. Packets that were corrupted during
transmission but, nevertheless, still arrived at dst are not counted.
Clocks do have to be synchronized between src and dst such that it is
possible to uniquely and accurately determine the interval [T, T+T0]
at both sides.
If this metric is used in an active measurement system, the system
MUST NOT send multiple packets with identical information fields in
order to avoid that all packets will be declared duplicates. This
metric can be used inside a passive measurement system as well, using
packets generated by another source. However, if the source can send
two identical packets within the interval [T, T+T0], this will be
incorrectly labeled as a duplicate, resulting in a false positive.
It is up to the implementor to estimate if this scenario is likely to
happen and the rate of false positives that is acceptable.
<span class="grey">Uijterwaal Standards Track [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc5560">RFC 5560</a> Packet Duplication Metric May 2009</span>
The definition of identical information fields is such that two
packets are considered to be identical if they are sent from the same
source and contain the same information. This does not necessarily
mean that all bits in the packet are the same. For example, when a
packet is replicated and the copies are transferred along different
paths, the Time to Live (TTL) may be different. The implementation
MUST specify which fields are compared when deciding whether or not
two packets are identical.
In the case of IPv4, these will usually be: version, ihl,
identification, src, dst, protocol, some or all upper-layer protocol
data.
In IPv6, these will usually be: version, next header, source,
destination, some or all upper-layer protocol data
Note that the use of the identification field is not present in non-
fragmented IPv6 packets and may not be sufficient to distinguish
packets from each even in IPv4, particularly at higher transmission
speeds
<span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. Methodology</span>
The basic technique to measure this metric follows the methodology
described in <a href="./rfc2680#section-2.6">Section 2.6 of [RFC2680]</a> with one exception.
[<a id="ref-RFC2680">RFC2680</a>] does not specify that the receiving host should be able to
receive multiple copies of a single packet, as it only needs one copy
to determine the metrics. Implementations for this metric should
obviously be capable of receiving multiple copies.
<span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a>. Errors and Uncertainties</span>
Refer to <a href="./rfc2680#section-2.7">Section 2.7 of [RFC2680]</a>.
<span class="h3"><a class="selflink" id="section-2.8" href="#section-2.8">2.8</a>. Reporting the Metric</span>
Refer to <a href="./rfc2680#section-2.8">Section 2.8 of [RFC2680]</a>.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. A Singleton Definition for One-Way Packet Duplication</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Metric Name</span>
Type-P-one-way-packet-duplication
<span class="grey">Uijterwaal Standards Track [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc5560">RFC 5560</a> Packet Duplication Metric May 2009</span>
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Metrics Parameters</span>
o src, the IP address of a host
o dst, the IP address of a host
o T, the wire time of a packet at the source
o T0, the maximum waiting time for a packet to arrive at the
destination.
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Metric Units</span>
An integer number.
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Definition</span>
The value of a Type-P-one-way-packet-duplication is a positive
integer number indicating the number of (uncorrupted and identical)
additional copies of an individual packet received by dst in the
interval [T, T+T0] as sent by src at time T.
If a packet is sent and only one copy arrives in the interval [T,
T+T0], then the metric is 0. If no copy arrives in this interval,
then the metric is undefined. Applications MAY report an
"impossible" value (for example, -1) to indicate this condition.
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. Discussion</span>
This metric is equal to:
Type-P-one-way-packet-arrival-count - 1
This metric is expected to be used for applications that need to know
duplication for an individual packet. All considerations regarding
methodology, errors, and reporting from the previous section apply.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Definition for Samples for One-Way Packet Duplication</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Poisson Streams</span>
<span class="h4"><a class="selflink" id="section-4.1.1" href="#section-4.1.1">4.1.1</a>. Metric Name</span>
Type-P-one-way-Packet-Duplication-Poisson-Stream
<span class="grey">Uijterwaal Standards Track [Page 7]</span><span id="page-8" ></span>
<span class="grey"><a href="./rfc5560">RFC 5560</a> Packet Duplication Metric May 2009</span>
<span class="h4"><a class="selflink" id="section-4.1.2" href="#section-4.1.2">4.1.2</a>. Metric Parameters</span>
o src, the IP address of a host.
o dst, the IP address of a host.
o Ts, a time.
o Tf, a time. Ts and Tf specify the time interval when packets can
be sent for this stream.
o T0, the maximum waiting time for a packet to arrive at the
destination.
o lambda, a rate in reciprocal seconds.
<span class="h4"><a class="selflink" id="section-4.1.3" href="#section-4.1.3">4.1.3</a>. Metric Units</span>
A sequence of pairs; the elements of each pair are:
o T, a time
o Type-P-one-way-packet-arrival-count for the packet sent at T.
<span class="h4"><a class="selflink" id="section-4.1.4" href="#section-4.1.4">4.1.4</a>. Definition</span>
Given Ts, Tf, and lambda, we compute a pseudo-random Poisson process
beginning at or before Ts, with average-rate lambda, and ending at or
after Tf. Those time values greater than or equal to Ts, and less
than or equal to Tf are then selected. At each of the times in this
process, we obtain the value of Type-P-one-way-packet-arrival-count.
The value of the sample is the sequence made up of the resulting
{time, duplication} pairs. If there are no such pairs, the sequence
is of length zero, and the sample is said to be empty.
<span class="h4"><a class="selflink" id="section-4.1.5" href="#section-4.1.5">4.1.5</a>. Methodology</span>
Refer to <a href="./rfc2680#section-3.6">Section 3.6 of [RFC2680]</a>.
<span class="h4"><a class="selflink" id="section-4.1.6" href="#section-4.1.6">4.1.6</a>. Errors and Uncertainties</span>
Refer to <a href="./rfc2680#section-3.7">Section 3.7 of [RFC2680]</a>.
<span class="h4"><a class="selflink" id="section-4.1.7" href="#section-4.1.7">4.1.7</a>. Reporting the Metric</span>
Refer to <a href="./rfc2680#section-3.8">Section 3.8 of [RFC2680]</a>.
<span class="grey">Uijterwaal Standards Track [Page 8]</span><span id="page-9" ></span>
<span class="grey"><a href="./rfc5560">RFC 5560</a> Packet Duplication Metric May 2009</span>
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Periodic Streams</span>
<span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a>. Metric Name</span>
Type-P-one-way-Packet-Duplication-Periodic-Stream
<span class="h4"><a class="selflink" id="section-4.2.2" href="#section-4.2.2">4.2.2</a>. Metric Parameters</span>
o src, the IP address of a host.
o dst, the IP address of a host.
o Ts, a time.
o Tf, a time. Ts and Tf specify the time interval when packets can
be sent for this stream.
o T0, the maximum waiting time for a packet to arrive at the
destination.
o lambda, a rate in reciprocal seconds.
<span class="h4"><a class="selflink" id="section-4.2.3" href="#section-4.2.3">4.2.3</a>. Metric Units</span>
A sequence of pairs; the elements of each pair are:
o T, a time
o Type-P-one-way-packet-arrival-count for the packet sent at T.
<span class="h4"><a class="selflink" id="section-4.2.4" href="#section-4.2.4">4.2.4</a>. Definition</span>
At time Ts, we start sending packets with a constant-rate lambda,
until time Tf. For each packet sent, we obtain the value of Type-P-
one-way-packet-arrival-count. The value of the sample is the
sequence made up of the resulting {time, duplication} pairs. If
there are no such pairs, the sequence is of length zero and the
sample is said to be empty.
<span class="h4"><a class="selflink" id="section-4.2.5" href="#section-4.2.5">4.2.5</a>. Methodology</span>
Refer to <a href="./rfc3432#section-4.5">Section 4.5 of [RFC3432]</a>.
<span class="h4"><a class="selflink" id="section-4.2.6" href="#section-4.2.6">4.2.6</a>. Errors and uncertainties</span>
Refer to <a href="./rfc3432#section-4.6">Section 4.6 of [RFC3432]</a>.
<span class="grey">Uijterwaal Standards Track [Page 9]</span><span id="page-10" ></span>
<span class="grey"><a href="./rfc5560">RFC 5560</a> Packet Duplication Metric May 2009</span>
<span class="h4"><a class="selflink" id="section-4.2.7" href="#section-4.2.7">4.2.7</a>. Reporting the metric</span>
Refer to <a href="./rfc3432#section-4.7">Section 4.7 of [RFC3432]</a>.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Some Statistics Definitions for One-Way Duplication</span>
Note: the statistics described in this section can be used for both
Type-P-one-way-Packet-Duplication-Poisson-Stream and Type-P-one-way-
Packet-Duplication-Periodic-Stream. The application SHOULD report
which sample was used as input.
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Type-P-one-way-packet-duplication-fraction</span>
This statistic gives the fraction of additional packets that arrived
in a stream.
Given a Type-P-one-way-Packet-Duplication-Poisson-Stream, one first
removes all values of Type-P-one-way-Packet-Duplication that are
undefined. For the remaining pairs in the stream, one calculates:
(Sum Type-P-one-way-packet-arrival-count/Number of pairs left) - 1
(In other words, (number of packets received)/(number of packets sent
and not lost).)
The number can be expressed as a percentage.
Note: this statistic is the equivalent to the Y.1540 IPDR [<a href="#ref-Y1540" title=""Y.1540 ITU-T Recommendation Y.1540 (2007), Internet protocol data communication service IP packet transfer and availability performance parameters."">Y1540</a>].
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Type-P-one-way-replicated-packet-rate</span>
This statistic gives the fraction of packets that was duplicated (one
or more times) in a stream.
Given a Type-P-one-way-Packet-Duplication-Poisson-Stream, one first
removes all values of Type-P-one-way-packet-arrival-count that are
undefined. For the remaining pairs in the stream, one counts the
number of pairs with Type-P-one-way-packet-arrival-count greater than
1. Then, one calculates the fraction of packets that meet this
criterion as a fraction of the total. (In other words: (number of
duplicated packets)/(number of packets sent and not lost).)
The number can be expressed as a percentage.
Note: this statistic is the equivalent of the Y.1540 RIPR [<a href="#ref-Y1540" title=""Y.1540 ITU-T Recommendation Y.1540 (2007), Internet protocol data communication service IP packet transfer and availability performance parameters."">Y1540</a>].
<span class="grey">Uijterwaal Standards Track [Page 10]</span><span id="page-11" ></span>
<span class="grey"><a href="./rfc5560">RFC 5560</a> Packet Duplication Metric May 2009</span>
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Examples</span>
Consider a stream of 4 packets, sent as:
(1, 2, 3, 4)
and arriving as:
o Case 1: (1, 2, 3, 4)
o Case 2: (1, 1, 2, 2, 3, 3, 4, 4)
o Case 3: (1, 1, 1, 2, 2, 2, 3, 3, 3, 4, 4, 4)
o Case 4: (1, 1, 1, 2, 3, 3, 3, 4)
Case 1: No packets are duplicated in a stream, and both the Type-P-
one-way-packet-duplication-fraction and the Type-P-one-way-packet-
replicated-packet-rate are 0.
Case 2: Every packet is duplicated once, and the Type-P-one-way-
packet-duplication-fraction is 100%. The Type-P-one-way-replicated-
packet-rate is 100%, too.
Case 3: Every packet is duplicated twice, so the Type-P-one-way-
packet-duplication-fraction is 200%. The Type-P-one-way-replicated-
packet-rate is still 100%.
Case 4: Half the packets are duplicated twice and the other half are
not duplicated. The Type-P-one-way-packet-duplication-fraction is
again 100%, and this number does not show the difference with case 2.
However, the Type-P-one-way-packet-replicated-packet-rate is 50% in
this case and 100% in case 2.
However, the Type-P-one-way-packet-duplication-rate will not show the
difference between cases 2 and 3. For this, one has to look at the
Type-P-one-way-packet-duplication-fraction.
Finally, note that the order in which the packets arrived does not
affect the results. For example, these variations of case 2:
o Case 2a: (1, 1, 2, 2, 3, 3, 4, 4)
o Case 2b: (1, 2, 3, 4, 1, 2, 3, 4)
o Case 2c: (1, 2, 3, 4, 4, 3, 2, 1)
<span class="grey">Uijterwaal Standards Track [Page 11]</span><span id="page-12" ></span>
<span class="grey"><a href="./rfc5560">RFC 5560</a> Packet Duplication Metric May 2009</span>
(as well as any other permutation) all yield the same results for
Type-P-one-way-packet-duplication-fraction and the Type-P-one-way-
replicated-packet-rate.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
Conducting Internet measurements raises both security and privacy
concerns. This memo does not specify an implementation of the
metrics, so it does not directly affect the security of the Internet
nor of applications that run on the Internet. However,
implementations of these metrics must be mindful of security and
privacy concerns.
There are two types of security concerns: potential harm caused by
the measurements and potential harm to the measurements. The
measurements could cause harm because they are active, and they
inject packets into the network. The measurement parameters MUST be
carefully selected so that the measurements inject trivial amounts of
additional traffic into the networks they measure. If they inject
"too much" traffic, they can skew the results of the measurement, and
in extreme cases, cause congestion and denial of service.
The measurements themselves could be harmed by routers giving
measurement traffic a different priority than "normal" traffic or by
an attacker injecting artificial measurement traffic. If routers can
recognize measurement traffic and treat it separately, the
measurements will not reflect actual user traffic. If an attacker
injects artificial traffic that is accepted as legitimate, the loss
rate will be artificially lowered. Therefore, the measurement
methodologies SHOULD include appropriate techniques to reduce the
probability that measurement traffic can be distinguished from
"normal" traffic. Authentication techniques, such as digital
signatures, may be used where appropriate to guard against injected
traffic attacks.
The privacy concerns of network measurement are limited by the active
measurements described in this memo. Unlike passive measurements,
there can be no release of existing user data.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span>
IANA has registered the metrics defined in this document in the IP
Performance Metrics (IPPM) Metrics Registry, see [<a href="./rfc4148" title=""IP Performance Metrics (IPPM) Metrics Registry"">RFC4148</a>].
<span class="grey">Uijterwaal Standards Track [Page 12]</span><span id="page-13" ></span>
<span class="grey"><a href="./rfc5560">RFC 5560</a> Packet Duplication Metric May 2009</span>
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgements</span>
The idea to write this document came up in a meeting with Al Morton,
Stanislav Shalunov, Emile Stephan, and the author on the IPPM
reporting document.
This document relies heavily on [<a href="./rfc2680" title=""A One-way Packet Loss Metric for IPPM"">RFC2680</a>], and the author would like
to thank the authors of that document for writing it.
Finally, thanks are due to Lars Eggert, Al Morton, Martin Swany, and
Matt Zekauskas for their comments.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span>
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC2680">RFC2680</a>] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way
Packet Loss Metric for IPPM", <a href="./rfc2680">RFC 2680</a>, September 1999.
[<a id="ref-RFC3432">RFC3432</a>] Raisanen, V., Grotefeld, G., and A. Morton, "Network
performance measurement with periodic streams", <a href="./rfc3432">RFC 3432</a>,
November 2002.
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span>
[<a id="ref-RFC2330">RFC2330</a>] Paxson, V., Almes, G., Mahdavi, J., and M. Mathis,
"Framework for IP Performance Metrics", <a href="./rfc2330">RFC 2330</a>,
May 1998.
[<a id="ref-RFC4148">RFC4148</a>] Stephan, E., "IP Performance Metrics (IPPM) Metrics
Registry", <a href="https://www.rfc-editor.org/bcp/bcp108">BCP 108</a>, <a href="./rfc4148">RFC 4148</a>, August 2005.
[<a id="ref-Y1540">Y1540</a>] "Y.1540 ITU-T Recommendation Y.1540 (2007), Internet
protocol data communication service IP packet transfer and
availability performance parameters.", 2007.
<span class="grey">Uijterwaal Standards Track [Page 13]</span><span id="page-14" ></span>
<span class="grey"><a href="./rfc5560">RFC 5560</a> Packet Duplication Metric May 2009</span>
Author's Address
Henk Uijterwaal
RIPE NCC
Singel 258
1016 AB Amsterdam
The Netherlands
Phone: +31 20 535 4444
EMail: [email protected]
Uijterwaal Standards Track [Page 14]
Annotations
Select text to annotate