RFC 5520: Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based Mechanism
In plain English — editorial summary, not part of the RFC
Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering (TE) Label Switched Paths (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. However, in some cases (e.g., when ASes are administered by separate Service Providers), it would break confidentiality rules for a PCE to supply a path segment to a PCE in another domain, thus disclosing AS-internal topology information. This issue may be circumvented by returning a loose hop and by invoking a new path computation from the domain boundary Label Switching Router (LSR) during TE LSP setup as the signaling message enters the second domain, but this technique has several issues including the problem of maintaining path diversity. This document defines a mechanism to hide the contents of a segment of a path, called the Confidential Path Segment (CPS). The CPS may be replaced by a path-key that can be conveyed in the PCE Communication Protocol (PCEP) and signaled within in a Resource Reservation Protocol TE (RSVP-TE) explicit route object. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5520
- Published
- April 2009
- Authors
- R. Bradford; JP. Vasseur; A. Farrel
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6457PCC-PCE Communication and PCE Discovery Requirements for Inter-Layer Traffic EngineeringCurrent
December 2011
- RFC 6484Certificate Policy (CP) for the Resource Public Key Infrastructure (RPKI)Current
February 2012
- RFC 7420Path Computation Element Communication Protocol (PCEP) Management Information Base (MIB) ModuleCurrent
December 2014
- RFC 7896Update to the Include Route Object (IRO) Specification in the Path Computation Element Communication Protocol (PCEP)Current
June 2016
- RFC 7897Domain Subobjects for the Path Computation Element Communication Protocol (PCEP)Current
June 2016
- RFC 8233Extensions to the Path Computation Element Communication Protocol (PCEP) to Compute Service-Aware Label Switched Paths (LSPs)Updated
September 2017
- RFC 8253PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)Updated
October 2017
- RFC 8356Experimental Codepoint Allocation for the Path Computation Element Communication Protocol (PCEP)Current
March 2018
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?