Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 19
- Abstract
- In certain scenarios, there may be a need to combine several Generalized Multiprotocol Label Switching (GMPLS) Label Switched Paths (LSPs) such that a single end-to-end (e2e) LSP is realized and all traffic from one constituent LSP is switched onto the next LSP. We will refer to this as "LSP stitching", the key requirement being that a constituent LSP not be allocated to more than one e2e LSP. The constituent LSPs will be referred to as "LSP segments" (S-LSPs). This document describes extensions to the existing GMPLS signaling protocol (Resource Reservation Protocol-Traffic Engineering (RSVP-TE)) to establish e2e LSPs created from S-LSPs, and describes how the LSPs can be managed using the GMPLS signaling and routing protocols. It may be possible to configure a GMPLS node to switch the traffic from an LSP for which it is the egress, to another LSP for which it is the ingress, without requiring any signaling or routing extensions whatsoever and such that the operation is completely transparent to other nodes. This will also result in LSP stitching in the data plane. However, this document does not cover this scenario of LSP stitching. [STANDARDS-TRACK]
- Publication Date
- 2008-02-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC5150- Link
- https://doi.org/10.17487/RFC5150
- Author(s)
- Arthi AyyangarKireeti KompellaJP VasseurAdrian Farrel
- Keyword(s)
- LSP, E2e Lsp, Lsp Stitching, Lsp Segments
Latest version of IETF RFC 5150
Document Versions — IETF RFC 5150
-
▶ IETF RFC 5150 (2008-02-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 2747 [Active*]
- IETF RFC 3209 [Active*]
- IETF RFC 3473 [Active*]
- IETF RFC 4206 [Active*]
- IETF RFC 4420 [Superseded*]
Bibliographic Reference(s)
- Fang, L., Ed., Behringer, M., Callon, R., Le Roux, J. L., Zhang, R., Knight, P., Stein, Y., Bitar, N., and R. Graveman., "Security Framework for MPLS and GMPLS Networks", Work in Progress, July 2007. EXTERNAL
- IETF RFC 3032 [Active*]
- IETF RFC 3477 [Active*]
- IETF RFC 4201 [Active*]
- IETF RFC 4203 [Active*]
- IETF RFC 4205 [Superseded*]
- IETF RFC 4655 [Active*]
- IETF RFC 4726 [Active*]
- IETF RFC 4875 [Active*]
- IETF RFC 5151 [Active*]
- IETF RFC 5152 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5150.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 5150, Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE). Available at https://doi.org/10.17487/RFC5150
Snippet:
IETF RFC 5150, Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE). Available at https://doi.org/10.17487/RFC5150
HTML (ISO 690 compliant)
Preview:
IETF RFC 5150, Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE). Available at https://doi.org/10.17487/RFC5150
Snippet:
<span class="citation"><cite>IETF RFC 5150</cite>, Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE). Available at <a href="https://doi.org/10.17487/RFC5150" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5150</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5150, Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE)
doi: 10.17487/RFC5150
url: https://doi.org/10.17487/RFC5150
doi: 10.17487/RFC5150
url: https://doi.org/10.17487/RFC5150
Snippet:
<li> <cite id="bib-rfc5150">IETF RFC 5150</cite>, Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE) <span class="doi">10.17487/RFC5150</span> </li>
Referenced By
- IETF RFC 5145 [Active*]
- IETF RFC 5146 [Active*]
- IETF RFC 5151 [Active*]
- IETF RFC 5152 [Active*]
- IETF RFC 5251 [Active*]
- IETF RFC 5298 [Active*]
- IETF RFC 5376 [Active*]
- IETF RFC 5921 [Active*]
- IETF RFC 6107 [Active*]
- IETF RFC 6424 [Superseded*]
- IETF RFC 7491 [Active*]