Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based Mechanism
RFC 5520, “Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based Mechanism”, is a Proposed Standard document published in April 2009 by R. Bradford, JP. Vasseur, A. Farrel. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5520 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5519 Multicast Group Membership Discovery MIB
- RFC 5521 Extensions to the Path Computation Element Communication Protocol for Route Exclusions
- RFC 5518 Vouch By Reference
- RFC 5522 Network Mobility Route Optimization Requirements for Operational Use in Aeronautics and Space Exploration Mobile Networks
- RFC 5523 OSPFv3-Based Layer 1 VPN Auto-Discovery
- RFC 5516 Diameter Command Code Registration for the Third Generation Partnership Project Evolved Packet System
- RFC 5524 Extended URLFETCH for Binary and Converted Parts
- RFC 5515 Layer 2 Tunneling Protocol Access Line Information Attribute Value Pair Extensions