1 / 5

GMPLS-based Hierarchy LSP creation in MRN/MLN

GMPLS-based Hierarchy LSP creation in MRN/MLN. CCAMP WG, IETF 79th, Beijing, China draft-zhang-ccamp-gmpls-h-lsp-mln-02.txt. Fatai Zhang <zhangfatai@huawei.com> Dan Li < danli@huawei.com >

shirin
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 79th, Beijing, China draft-zhang-ccamp-gmpls-h-lsp-mln-02.txt Fatai Zhang <zhangfatai@huawei.com> Dan Li <danli@huawei.com> Francisco Javier Jimenez Chico <fjjc@tid.es> Oscar Gonzalez de Dios <ogondio@tid.es>

  2. Overview of this Draft (Version 02) • Overview of the draft: • In MLN/MRN, for the hybrid node, there may be multiple switching capabilities and/or multiple switching granularities • At the source node of the connection, it may be desirable to specify which server layer switching capability and/or switching granularity to be used for the FA-LSP. • Signaling extension is described to meet the requirment • Changes from version 01: • We welcome “Francisco Javier Jimenez Chico” and “Oscar Gonzalez de Dios” to be the co-authors • No significant change for the contents is made in this version

  3. Path: Server layer = TDM, Granularity = ODU3 Client Layer LSP FA FA-LSP Open Discussion: Single-carrier • Source node or PCE may have the policy to select server layer SC & granularity • If Node A or PCE can perform full path computation, it may need to explicitly specify server layer SC & granularity to be used • If Node A or PCE can perform loose path computation, and it may also need to specify which server layer SC & granularity to be used • In the both cases above, the head node (e.g. Node A) should be capable of indicating this information (SC& granularity) in the signaling. • Multi-layer for one carrier is more typical for MLN control Node A Node B Node C Node D PSC PSC PSC PSC Node E TDM TDM TDM TDM & WDM TDM & WDM WDM WDM WDM

  4. Client Layer LSP H-LSP Open Discussion: Multi-carrier • H-LSP is usually pre-provisioned based on planning and is usually not allowed to be dynamically created triggered by client layer (policy stuff) • So, it may be not necessary to specify server layer SC & granularity in this case. • However, it does not prevent to do that (e.g., we can get the policy from MP, and then carry this information (SC & granularity) in the signaling). Path: Server layer = TDM, Granularity = ODU3 Node A Node B Node C Node D PSC PSC PSC PSC Node E TDM TDM TDM TDM & WDM TDM & WDM WDM WDM WDM Carrier 1: A D Carrier 2: B E C

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

More Related