50 likes | 168 Views
This document outlines a proposal for enhancing Generalized MPLS (GMPLS) signaling to support Layer-2 Switching Capabilities (L2SC) Label Switched Paths (LSPs). The goal is to enable end-to-end LSP setup while leveraging existing GMPLS frameworks. It discusses various architectures including nested and stitched LSPs while avoiding overlay complexities. Key objectives include agreeing on Generalized Port Identifier (GPID) standards, label semantics, and bandwidth encoding enhancements, to refine procedures for managing L2SC LSPs efficiently.
E N D
Generalized MPLS Signaling for Layer-2 LSPs draft-papadimitriou-ccamp-gmpls-l2sc-lsp-00.txt D.Papadimitriou (dpapadimitriou@psg.com) D.Brungard (dbrungard@att.com) M.Vigoureux (martin.vigoureux@alcatel.fr)
Why ? • Goal: RFC 3473 support of L2SC LSPs • L2 switching architecture: [X,L2SC],…, [L2SC,L2SC],…,[L2SC,X] where X = Any (in particular, PSC) • Layered switching architectures (FA LSP’s): [L2SC,Y],…,[Y,L2SC] where Y = Any (in particular, TDM or LSC) • Non-Goal: PW architecture (~ provisioned overlays over PSN)
L2SC LSP and Setup Methods • L2SC LSP => “tunnel” for Ethernet payload transport w/o necessarily using MPLS PW’s and other extended p2p LDP signaling • Methods for e2e LSP Setup • direct e2e LSP setup • LSP nesting (FA-LSP in network) • LSP stitching (LSP Segment in network) • LSP shuffling (~ GMPLS VPN)
LSP Nesting & Stitching/Shuffling I/f Ethernet 6 9 3 1 7 4 8 2 5 1 3 6 9 [X,L2SC] [L2SC,Y] [Y,Y] [Y,L2SC] [L2SC,X] Nesting (FA) FA-LSP (ex: TDM LSP) Ethernet LSP 2 4 7 8 Ethernet LSP Ethernet LSP Ethernet LSP Stitching Ethernet LSP Shuffling
What do we need ? • Not that much … since max re-use of existing GMPLS RFC’s • Get agreement on GPID’s e.g. GFP, X.86 • Get agreement on label semantic(s) e.g. Port, Flow, VLAN • Get agreement on bandwidth encoding (any enhancement from current TSPEC ?) => Support from the working group to refine GMPLS procedures for L2SC LSPs ?