Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Authors:

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

Stream:

IETF

Source:

ccamp (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

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

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

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

Abstract

The paths taken by Multiprotocol Label Switching (MPLS) andGeneralized MPLS (GMPLS) Traffic Engineering (TE) Label SwitchedPaths (LSPs) may be computed by Path Computation Elements (PCEs).Where the TE LSP crosses multiple domains, such as Autonomous Systems(ASes), the path may be computed by multiple PCEs that cooperate,with each responsible for computing a segment of the path.

To preserve confidentiality of topology within each AS, the PCEssupport a mechanism to hide the contents of a segment of a path (suchas the segment of the path that traverses an AS), called theConfidential Path Segment (CPS), by encoding the contents as a PathKey Subobject (PKS) and embedding this subobject within the result ofits path computation.

This document describes how to carry Path Key Subobjects in theResource Reservation Protocol (RSVP) Explicit Route Objects (EROs)and Record Route Objects (RROs) so as to facilitate confidentiality inthe signaling of inter-domain TE LSPs. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.