1 / 5

GMPLS-based Hierarchy LSP Creation in MRN/MLN

This draft, presented at the IETF 80th meeting in Prague, outlines the GMPLS-based hierarchical LSP creation for Multi-Protocol Label Switching (MLN) and Multi-Radio Network (MRN). It addresses the need for specifying server layer switching capabilities, granularities, and adaptation functions at the source node. Updates from the previous version include the incorporation of new co-author Cyril Margaria and enhancements to the selection of adaptation functions. This work aims to refine LSP creation processes and support function negotiations for effective client signal adaptation in complex network environments.

bing
Télécharger la présentation

GMPLS-based Hierarchy LSP Creation in MRN/MLN

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GMPLS-based Hierarchy LSP Creation in MRN/MLN CCAMP WG, IETF 80th, Prague, Czech Republic draft-zhang-ccamp-gmpls-h-lsp-mln-03.txt Fatai Zhang <zhangfatai@huawei.com> Dan Li <huawei.danli@huawei.com> Francisco Javier Jimenez Chico <fjjc@tid.es> Oscar Gonzalez de Dios <ogondio@tid.es> Cyril Margaria <cyril.margaria@nsn.com>

  2. Overview of this Draft (Version 03) • Overview of the draft: • In MLN/MRN, there may be multiple switching capabilities and/or multiple switching granularities and/or adaptation functions in the server layer network • The source node of the client layer connection needs to specify which server layer switching capability and/or switching granularityand/or adaptation functions is selected • Changes from version 02: • We welcome Cyril Margaria to be the co-author • Support selection of adaptation functions of the server layer

  3. Client Layer LSP Selection of Adaptation Functions • There may be multiple adaptation functions for the edge nodes to adapt the client signal into the server layer FA-LSP • CALL mechanism may be used for adaptation function negotiation if the edge nodes support CALL mechanism • But in case that the source node (i.e., node A) or PCE performs a full path computation including the server layer path, the adaptation functions will also be selected by node A or PCE • When creating the client layer LSP, the source node should tell the edge node of the selected adaptation function Path: Adaptation function = A Node A Node B Node C Node D FA PSC PSC PSC PSC FA-LSP Node E B A A TDM TDM TDM TDM TDM

  4. Selection of Adaptation Functions • G-PID can be used to indicate the payload type of the server layer (i.e., the client signal) as well as the adaptation function for adapting the client signal into the server layer FA-LSP • The G-PID is added into the suggested SERVER_LAYER_INFO sub-object in ERO • The edge node of the server layer network will use the selected G-PID (i.e., adaptation function) to create the FA-LSP Server layer switching capability Adaptation function • +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |L| Type | Length |M| Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | LSP Enc. Type |Switching Type | G-PID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Traffic Parameters | ~ ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Server layer granularity

  5. Next Steps • Adopt it as WG document • Comments are always appreciated • Refine it based on the feedback from the meeting or mailing list

More Related