rfc-6777

Label Switched Path (LSP) Data Path Delay Metrics in Generalized MPLS and MPLS Traffic Engineering (MPLS-TE) Networks

W. Sun (Editor), G. Zhang (Editor), J. Gao, G. Xie, R. Papneja
date2012-11 streamIETF areartg wgccamp statusPROPOSED STANDARD pages29 canonicalhttps://www.rfc-editor.org/rfc/rfc6777 doi10.17487/RFC6777
When setting up a Label Switched Path (LSP) in Generalized MPLS (GMPLS) and MPLS Traffic Engineering (MPLS-TE) networks, the completion of the signaling process does not necessarily mean that the cross-connection along the LSP has been programmed accordingly and in a timely manner. Meanwhile, the completion of the signaling process may be used by LSP users or applications that control their use as an indication that the data path has become usable. The existence of the inconsistency between the signaling messages and cross-connection programming, and the possible failure of cross- connection programming, if not properly treated, will result in data loss or even application failure. Characterization of this performance can thus help designers to improve the way in which LSPs are used and to make applications or tools that depend on and use LSPs more robust. This document defines a series of performance metrics to evaluate the connectivity of the data path in the signaling process. [STANDARDS-TRACK]

Extracted elements (24)

design-rationale §3

Five distinct metrics (RRFD, RSRD, PRFD, PSFD, PSRD) are defined rather than a single metric to capture the relationship between different signaling events (PATH sent/received, Resv sent/received) and data path readiness, enabling identification of specific implementation behaviors.

mpls, measurement

design-rationale §5.6

RRFD can be a negative value when a node programs cross-connections before forwarding the PATH message downstream, meaning the data path is ready before the Resv reaches the ingress. PRFD is recommended to further characterize this case.

mpls, measurement

design-rationale §10

The metrics use Poisson sampling (from the IPPM framework in RFC 2330) to select measurement instances, following the established methodology of related LSP provisioning performance metrics in RFC 5814.

mpls, measurement

design-rationale §1

Vendors may program cross-connections in a pipelined manner to reduce overall LSP provisioning delay, causing the data path to not be ready instantly after signaling completes. This gap between signaling completion and data path readiness motivates the metrics defined in this document.

mpls, measurement

interoperability-note §5.6

Clock synchronization between ingress and egress nodes is required for RRFD, RSRD, and PSFD measurements, but is NOT required for PRFD and PSRD since both timestamps are taken on the same node.

mpls, measurement, ntp

normative-requirement §5.6 MUST

For rate-based data path connectivity verification (e.g., Ethernet), it is RECOMMENDED that the injecting node use small intervals between successive frames, and the interval value MUST be reported.

mpls, measurement

normative-requirement §5.6 MUST

If an error-free signal is received by the egress node before a PATH message is sent on the ingress node, an error MUST be reported and the measurement SHOULD terminate.

mpls, measurement

normative-requirement §5.6 MUST

If the corresponding Resv message is received but no error-free signal is received by the egress node within a threshold period, RRFD MUST be treated as undefined, and the threshold value MUST be reported.

mpls, measurement

normative-requirement §6.6 MUST

If the corresponding Resv message is sent but no error-free signal is received by the ingress node within a threshold period, RSRD MUST be treated as undefined, and the threshold value MUST be reported.

mpls, measurement

normative-requirement §5.6 MUST NOT

If the LSP setup fails, metric values (RRFD, RSRD, PRFD, PSFD, PSRD) MUST NOT be counted.

mpls, measurement

normative-requirement §9.6 MUST

If the PATH message is sent but no error-free signal is received by the ingress node within a threshold, PSRD MUST be treated as undefined, and the threshold value MUST be reported.

mpls, measurement

normative-requirement §11.2 MUST NOT

In computing the median of a metric, undefined values MUST NOT be included; the median SHOULD be set to undefined if all dT values are undefined or if the sample is empty.

mpls, measurement

normative-requirement §11.3 MUST NOT

In computing the percentile of a metric, undefined values MUST NOT be included.

mpls, measurement

normative-requirement §7.6 SHOULD

PRFD SHOULD be used together with RRFD; a PRFD measurement is RECOMMENDED to be carried out after a negative RRFD value has been observed.

mpls, measurement

normative-requirement §10.5 MUST

The parameter Ts (maximum waiting time for an error-free signal) MUST be reported along with the LSP forward/reverse data path delay sample.

mpls, measurement

protocol-element §11.4.2

Failure Ratio is defined as the percentage of undefined metric values (signaling completed successfully but no error-free signal observed) to the total number of requests: Failure Ratio = Number of undefined values / (valid + undefined) * 100%.

mpls, measurement

protocol-element §7

PRFD (PATH Received, Forward Data path) measures the delay between when the egress node receives the last bit of the PATH message and when it receives an error-free signal, useful for identifying implementations that program cross-connections before forwarding the PATH message downstream.

mpls, measurement

protocol-element §8

PSFD (PATH Sent, Forward Data path) measures the delay from when the ingress node sends the first bit of the PATH message to when the egress node receives an error-free signal on the forward data path, providing an end-to-end view of forward data path setup time.

mpls, measurement

protocol-element §9

PSRD (PATH Sent, Reverse Data path) measures the delay from when the ingress node sends the first bit of the PATH message to when the ingress node receives an error-free signal on the reverse data path, complementing PSFD for bidirectional LSP characterization.

mpls, measurement

protocol-element §5

RRFD (Resv Received, Forward Data path) is a metric measuring the delay between when the last bit of a Resv message is received by the ingress node and when an error-free signal is received by the egress node, indicating the forward data path is ready.

mpls, measurement

protocol-element §6

RSRD (Resv Sent, Reverse Data path) measures the delay between when the egress node sends the last bit of the Resv message and when the ingress node receives an error-free signal on the reverse data path of a bidirectional LSP.

mpls, measurement

protocol-element §10.2

The data path delay sample is parameterized by ID0 (ingress LSR ID), ID1 (egress LSR ID), T0/Tf (time window), Lambda (Poisson rate), Th (LSP holding time), Td (maximum wait for LSP setup), and Ts (maximum wait for error-free signal).

mpls, measurement

protocol-element §4

The 'error-free signal' is a data-plane-specific indication of data path connectivity: for packet switching, reception of the first error-free packet; for SDH/SONET cross-connects, disappearance of alarms. Implementations must choose a signal appropriate to the technology being tested.

mpls, measurement

security-consideration §12 MUST NOT

Measurement parameters must be carefully selected to inject only trivial amounts of additional traffic; excessive traffic can skew results and in extreme cases cause congestion and denial of service. In the data plane, injected traffic MUST NOT exceed the rate specified in the LSP setup request, and wavelength-switched measurements MUST use the specified or negotiated lambda with appropriate power.

mpls, security, measurement