2002
DOI: 10.17487/rfc3393
|View full text |Cite
|
Sign up to set email alerts
|

IP Packet Delay Variation Metric for IP Performance Metrics (IPPM)

Abstract: This document refers to a metric for variation in delay of packets across Internet paths. The metric is based on the difference in the One-Way-Delay of selected packets. This difference in delay is called "IP Packet Delay Variation (ipdv)".

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
151
0
7

Year Published

2002
2002
2016
2016

Publication Types

Select...
5
2
2

Relationship

0
9

Authors

Journals

citations
Cited by 263 publications
(159 citation statements)
references
References 4 publications
(13 reference statements)
1
151
0
7
Order By: Relevance
“…-Performance metrics (throughput, delay, loss, jitter) such as defined in [RFC3148], [RFC2679], [RFC2680], and [RFC3393].…”
Section: Nve Location Trade-offsmentioning
confidence: 99%
“…-Performance metrics (throughput, delay, loss, jitter) such as defined in [RFC3148], [RFC2679], [RFC2680], and [RFC3393].…”
Section: Nve Location Trade-offsmentioning
confidence: 99%
“…Indeed, the CPP interface aims at exposing and characterizing, in a technology-agnostic manner, the IP transfer requirements to be met when invoking IP transfer capabilities of a network operated by a Network Provider between a set of Customer Nodes (e.g., Multimedia Gateway (Section 11.2.7 of [RFC2805]), Session Border Controller [RFC5853], etc.). These requirements include: reachability scope (e.g., limited scope, Internet-wide), direction, bandwidth requirements, QoS parameters (e.g., one-way delay [RFC2679], loss [RFC2680], or one-way delay variation [RFC3393]), protection, and high-availability guidelines (e.g., restoration in less than 50 ms, 100 ms, or 1 second).…”
Section: Rationalementioning
confidence: 99%
“…o One-way delay [RFC2679] o One-way delay variation [RFC3393] These parameters may be specific to a given path or a given scope (e.g., between two Customer Nodes). IP performance metric values indicated in a CPP should reflect the measurement between a set of Customer Nodes or between a Customer Node and a set of Provider Nodes.…”
Section: Qos Guaranteesmentioning
confidence: 99%
“…CPN is a QoS-driven routing protocol based on a smart network where users (applications) can declare their desired QoS requirements, while CPN adaptively routes their traffic by means of online sensing and measurement so as to provide the best possible QoS requested by the users [22,23], as a means to support and enhance the users' QoS needs. To address the needs of real-time traffic, this paper introduces a variant of CPN with a "goal" function that addresses real-time needs with regard to "Jitter" according to RFC3393 [24], and implements new functions in CPN to support multiple QoS classes for multiple traffic flows [25]. Furthermore, since adaptive routing takes place when CPN is used in order to meet some of the requirements of this QoS goal, path switching can occur and we evaluate the correlation of end-to-end packet loss with path switching and with the delay that occurs at the end-user's re-sequencing buffer that is needed to insure that packets are received in time-stamp order.…”
Section: Introductionmentioning
confidence: 99%