RFC 5553: Resource Reservation Protocol (RSVP) Extensions for Path Key Support
In plain English — editorial summary, not part of the RFC
The paths taken by 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. To preserve confidentiality of topology within each AS, the PCEs support a mechanism to hide the contents of a segment of a path (such as the segment of the path that traverses an AS), called the Confidential Path Segment (CPS), by encoding the contents as a Path Key Subobject (PKS) and embedding this subobject within the result of its path computation. This document describes how to carry Path Key Subobjects in the Resource Reservation Protocol (RSVP) Explicit Route Objects (EROs) and Record Route Objects (RROs) so as to facilitate confidentiality in the signaling of inter-domain TE LSPs. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5553
- Published
- May 2009
- Authors
- A. Farrel; R. Bradford; JP. Vasseur
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5556Transparent Interconnection of Lots of Links (TRILL): Problem and Applicability StatementCurrent
May 2009
- RFC 5557Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions in Support of Global Concurrent OptimizationCurrent
July 2009
- RFC 5548Routing Requirements for Urban Low-Power and Lossy NetworksCurrent
May 2009
- RFC 5561LDP CapabilitiesCurrent
July 2009
- RFC 5542Definitions of Textual Conventions for Pseudowire (PW) ManagementCurrent
May 2009
- RFC 5541Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)Current
June 2009
- RFC 5575Dissemination of Flow Specification RulesObsoleted
August 2009
- RFC 5523OSPFv3-Based Layer 1 VPN Auto-DiscoveryCurrent
April 2009
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?