Expedited forwarding end‐to‐end delay and jitter in DiffServ

The scheduling disciplines and active buffer management represent the main components employed in the differentiated services (DiffServ) data plane, which provide qualitative per‐hop behaviors corresponding to the QoS required by supported traffic classes. In the first part of this paper, we compute the per‐hop delay bound that should be guaranteed by the different multiservice scheduling disciplines, so that the end‐to‐end (e2e) delay required by expedited forwarding (EF) traffic can be guaranteed. Consequently, we derive the e2e delay bound of EF traffic served by priority queuing–weighted fair queuing (PQ–WFQ) at every hop along its routing path. Although real‐time flows are principally offered EF service class, some simulations on DiffServ‐enabled network show that these flows suffer from delay jitter and they are negatively impacted by lower priority traffic. In the second part of this paper, we clarify the passive impact of delay jitter on EF traffic, where EF flows are represented by renewal periodic ON–OFF flows, and the background (BG) flows are characterized by the Poisson process. We analyze through different scenarios the jitter effects of these BG flows on EF flow patterns when they are served by a single class scheduling discipline, such as first‐input first‐output, and a multiclass or multiservice scheduling discipline, such as static priority service discipline. As a result, we have found out that the EF per‐hop behaviors (PHBs) configuration according to RFCs 2598 and 3246 (IETF RFC 2598, June 1999; RFC 3246, IETF, March 2002) cannot stand alone in guaranteeing the delay jitter required by EF flows. Therefore, playout buffers must be added to DiffServ‐enabled networks for handling delay jitter problem that suffers from EF flows. Copyright © 2008 John Wiley & Sons, Ltd.