GMPLS Signaling Extensions for the Evolving G 709

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

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)

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

Removing of Reduplicate Text • The overview of mapping & multiplexing structure is removed since it has been described in [OTNFWK] • 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

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 ODU 3 link Decoupling label and TPN • More flexible for variant cases: • TPN is allocates by DP (e. g. Auto. MSI (deprecated in 2009) was used for the legacy equipments) • TPN is allocated by MP • TPN is allocated by CP Combining label and TPN OR • Saving bits and make the message more compact • Logically reasonable if TPN is allocated by CP

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

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