Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Authors:

R. Bradford, Ed.
JP. Vasseur
A. Farrel

Stream:

IETF

Source:

pce (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

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

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 5520

Abstract

Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS)Traffic Engineering (TE) Label Switched Paths (LSPs) may becomputed by Path Computation Elements (PCEs). Where the TE LSPcrosses multiple domains, such as Autonomous Systems (ASes), thepath may be computed by multiple PCEs that cooperate, with eachresponsible for computing a segment of the path. However, in somecases (e.g., when ASes are administered by separate ServiceProviders), it would break confidentiality rules for a PCE tosupply a path segment to a PCE in another domain, thus disclosingAS-internal topology information. This issue may be circumventedby returning a loose hop and by invoking a new path computationfrom the domain boundary Label Switching Router (LSR) during TELSP setup as the signaling message enters the second domain, butthis technique has several issues including the problem ofmaintaining path diversity.

This document defines a mechanism to hide the contents of asegment of a path, called the Confidential Path Segment (CPS). TheCPS may be replaced by a path-key that can be conveyed in the PCECommunication Protocol (PCEP) and signaled within in a ResourceReservation Protocol TE (RSVP-TE) explicit route object. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.