One-way delay is intended according to
RFC 2679:
for a real number dT, >>the *Type-P-One-way-Delay* from Src to Dst at
T is dT<< means that Src sent the first bit of a Type-P packet to Dst
at wire-time* T and that Dst received the last bit of that packet at
wire-time T+dT.
Test parameters:
The SmartBits 200 was deployed as EF traffic source and sink.
The SmartMetrics test available from the SmartWindows v. 6.51
application was deployed for both one-way delay and ipdv measurement.
(Note: traffic has to be sinked to the same SmartBits in
order to deploy the SmartWindows application.)
One-way delay is based on the cut-through latency measures
collected by the SmartBits. This metric is measured according to
RFC 1242, where cut-through latency is defined as:
the time interval starting when the end of the first bit of the
input frame reaches the input port and ending when the start of the
first bit of the output frame is seen on the output port.
So, one-way delay can be computed from cut-through latency by adding the transmission time of the packet, which is constant for a given packet size (see figure 2).
The timestamp deployed by the SmartBits represents the clock tick at the time of transmission (an absolute number) and the timestamp is added in hardware. The timestamp resolution is of 100 nsec.
The instantanous packet delay variation is computed by taking the abolute number of the ipdv metric defined by the IPPM working-group at IETF.
One-way delay over time is plotted by taking a given test and by plotting the one-way delay of each sample in packet sequence number order. Similarly, for ipdv over time the ipdv metric is computed and plotted according to the packet sequence number order.
Average one-way delay and average ippm for a given packet size are
computed from the sample means over a set of repetitions of the same
test.
Each test consists of approximately 250 samples.