1 / 7

GMPLS Signaling Extensions for the Evolving G.709 OTN Control

GMPLS Signaling Extensions for the Evolving G.709 OTN Control. CCAMP WG, IETF 79th, Beijing, China draft-zhang-ccamp-gmpls-evolving-g709-06.txt. Fatai Zhang <zhangfatai@huawei.com> Guoying Zhang < zhangguoying@mail.ritt.com.cn > Sergio Belotti < sergio.belotti@alcatel-lucent.it >

deirdre-holman
Download Presentation

GMPLS Signaling Extensions for the Evolving G.709 OTN Control

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 Signaling Extensions for the Evolving G.709 OTN Control CCAMP WG, IETF 79th, Beijing, China draft-zhang-ccamp-gmpls-evolving-g709-06.txt Fatai Zhang <zhangfatai@huawei.com> Guoying Zhang <zhangguoying@mail.ritt.com.cn> Sergio Belotti <sergio.belotti@alcatel-lucent.it> Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>

  2. Authors/Contributors • Fatai zhang (@Huawei) • Guoying Zhang (@CATR) • Sergio Belotti (@Alcatel-Lucent) • Daniele Ceccarelli (@Ericsson) • Yi Lin (@Huawei) • Yunbin Xu (@CATR) • Pietro Grandi (@Alcatel-Lucent) • Diego Caviglia(@Ericsson)

  3. Changes from Version 05 • Alignment with [OTN-FWK] and [OTN-INFO] drafts • Some information is moved to [OTN-FWK] and [OTN-INFO] to avoid reduplicate description • No significant change is made in this version

  4. Removing of Reduplicate Text • The overview of mapping & multiplexing structure is removed since it has been described in [OTN-FWK] • The information model of ODU label and TPN is moved to [OTN-INFO] • The data plane backward compatibility is moved to [OTN-FWK] • Explained in the [OTN-FWK] presentation

  5. Open Discussion: Relationship between Label and TPN • Put TPN into ODU label object or use a separate TPN object? Label: indicate the selected TSs TPN: a port number for the selected TSs Label (TS) = 1,2,5,6 TPN = 2 …… A B ODU3 link Decoupling label and TPN Combining label and TPN • More flexible for variant cases: • TPN is allocates by DP (e.g. AutoMSI (deprecated in 2009) was used for the legacy equipments) • TPN is allocated by MP • TPN is allocated by CP • Saving bits and make the message more compact • Logically reasonable if TPN is allocated by CP OR

  6. Open Discussion: Multi-stage Multiplexing ODU0 Connection ODU2 Connection ODU3 Link ODU3 Link A B C D E 2-stage multiplexing ODU2 Cross-connect ODU0 is NOT visible 2-stage demultiplexing • ODU2 cross-connects between B and D in the Data Plane (i.e. ODU2 trail) MUST be created because node C doesn’t support ODU0 • The path of ODU0 is A-B-D-E, and node C only performs ODU2 cross-connection and is not aware of the ODU0 • ODU2 connection (B-C-D) should be treated as Tunnel for the ODU0 • The creation of ODU0 and ODU2 Tunnel by CP is MLN stuff [RFC4206] and [RFC4206bis]. How to create ODU2 trail for ODU0 by CP (RSVP-TE)? • We can not use ODU0 TP or label info to request ODU2 trail. • It should comply with the principle of H-LSP (MLN stuff).

  7. Next Steps • Adopt it as a WG document • Significant agreement have been achieved and quite stable for quite long time • Put TPN into the label object if the meeting agrees • Refine it based on the feedback from the meeting or mailing list

More Related