{"draft":"draft-ietf-ccamp-lsp-stitching-06","doc_id":"RFC5150","title":"Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE)","authors":["A. Ayyangar","K. Kompella","JP. Vasseur","A. Farrel"],"format":["ASCII","HTML"],"page_count":"19","pub_status":"PROPOSED STANDARD","status":"PROPOSED STANDARD","source":"Common Control and Measurement Plane","abstract":"In certain scenarios, there may be a need to combine several\r\nGeneralized Multiprotocol Label Switching (GMPLS) Label Switched\r\nPaths (LSPs) such that a single end-to-end (e2e) LSP is realized and\r\nall traffic from one constituent LSP is switched onto the next LSP.\r\nWe will refer to this as \"LSP stitching\", the key requirement being\r\nthat a constituent LSP not be allocated to more than one e2e LSP.\r\nThe constituent LSPs will be referred to as \"LSP segments\" (S-LSPs).\r\n\r\nThis document describes extensions to the existing GMPLS signaling\r\nprotocol (Resource Reservation Protocol-Traffic Engineering\r\n(RSVP-TE)) to establish e2e LSPs created from S-LSPs, and\r\ndescribes how the LSPs can be managed using the GMPLS signaling and\r\nrouting protocols.\r\n\r\nIt may be possible to configure a GMPLS node to switch the traffic\r\nfrom an LSP for which it is the egress, to another LSP for which it is\r\nthe ingress, without requiring any signaling or routing extensions\r\nwhatsoever and such that the operation is completely transparent to\r\nother nodes.  This will also result in LSP stitching in the data\r\nplane.  However, this document does not cover this scenario of LSP\r\nstitching.  [STANDARDS-TRACK]","pub_date":"February 2008","keywords":["[--------]","lsp","label switched paths","e2e lsp","lsp stitching","lsp segments","s-lsp"],"obsoletes":[],"obsoleted_by":[],"updates":[],"updated_by":[],"see_also":[],"doi":"10.17487\/RFC5150","errata_url":"https:\/\/www.rfc-editor.org\/errata\/rfc5150"}