Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based Mechanism
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 19
- 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]
- Publication Date
- 2009-04-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC5520- Link
- https://doi.org/10.17487/RFC5520
- Author(s)
- Richard BradfordJP VasseurAdrian Farrel
- Keyword(s)
- Confidential Path Segment, PCEP
Latest version of IETF RFC 5520
Document Versions — IETF RFC 5520
-
▶ IETF RFC 5520 (2009-04-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 5440 [Active*]
Bibliographic Reference(s)
- Bradford, R., Vasseur, JP., and A. Farrel, "RSVP Extensions for Path Key Support", Work in Progress, February 2008. EXTERNAL
- Farrel, A., "Reduced Backus-Naur Form (RBNF) A Syntax Used in Various Protocol Specifications", Work in Progress, November 2008. EXTERNAL
- Koushik, K., and E. Stephan, "PCE Communication Protocol (PCEP) Management Information Base", Work in Progress, November 2008. EXTERNAL
- IETF RFC 3209 [Active*]
- IETF RFC 4105 [Active*]
- IETF RFC 4216 [Active*]
- IETF RFC 4655 [Active*]
- IETF RFC 5152 [Active*]
- IETF RFC 5298 [Active*]
- IETF RFC 5441 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5520.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5520, Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based Mechanism. Available at https://doi.org/10.17487/RFC5520
Snippet:
IETF RFC 5520, Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based Mechanism. Available at https://doi.org/10.17487/RFC5520
HTML (ISO 690 compliant)
Preview:
IETF RFC 5520, Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based Mechanism. Available at https://doi.org/10.17487/RFC5520
Snippet:
<span class="citation"><cite>IETF RFC 5520</cite>, Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based Mechanism. Available at <a href="https://doi.org/10.17487/RFC5520" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5520</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5520, Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based Mechanism
doi: 10.17487/RFC5520
url: https://doi.org/10.17487/RFC5520
doi: 10.17487/RFC5520
url: https://doi.org/10.17487/RFC5520
Snippet:
<li> <cite id="bib-rfc5520">IETF RFC 5520</cite>, Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based Mechanism <span class="doi">10.17487/RFC5520</span> </li>
Referenced By
- IETF RFC 5521 [Active*]
- IETF RFC 5553 [Active*]
- IETF RFC 5623 [Active*]
- IETF RFC 6805 [Active*]
- IETF RFC 7439 [Active*]
- IETF RFC 7491 [Active*]
- IETF RFC 8390 [Active*]