Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updated by:

RFC 9756

Authors:

D. Dhody
Q. Wu
V. Manral
Z. Ali
K. Kumaki

Stream:

IETF

Source:

pce (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8233

Discuss this RFC: Send questions or comments to the mailing listpce@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8233

Abstract

In certain networks, such as, but not limited to, financialinformation networks (e.g., stock market data providers), networkperformance criteria (e.g., latency) are becoming as critical to datapath selection as other metrics and constraints. These metrics areassociated with the Service Level Agreement (SLA) between customersand service providers. The link bandwidth utilization (the totalbandwidth of a link in actual use for the forwarding) is anotherimportant factor to consider during path computation.

IGP Traffic Engineering (TE) Metric Extensions describe mechanismswith which network performance information is distributed via OSPF andIS-IS, respectively. The Path Computation Element CommunicationProtocol (PCEP) provides mechanisms for Path Computation Elements(PCEs) to perform path computations in response to Path ComputationClient (PCC) requests. This document describes the extension to PCEPto carry latency, delay variation, packet loss, and link bandwidthutilization as constraints for end-to-end path computation.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.