1. CCAMP WG, IETF 79th, Beijing, China draft-ietf-ccamp-gmpls-g709-framework-03.txt Framework for GMPLS and PCE Control of G.709 Optical Transport Networks Fatai Zhang(zhangfatai@huawei.com) Dan Li(danli@huawei.com) Han Li(lihan@chinamobile.com) Sergio Belotti(sergio.belotti@alcatel-lucent.it) Daniele Ceccarelli(daniele.ceccarelli@ericsson.com)

2. Contents of this Draft  Informative overview of the OTN technology  Connection management in OTN network  GMPLS and PCE requirements Hierarchy LSP in OTN GMPLS Signaling requirements GMPLS Routing requirements GMPLS LMP requirements PCEP requirements

3. Changes from Version 02  We welcome Daniele Ceccarelli to be a co-author for his much contribution on this draft  Updated on signaling requirements Refined the descriptions to make it much clearer (e.g., TPN allocation of Tributary Port Number)  New added Requirements: Control of Hitless Adjustment of ODUflex(GFP) (HAO)  Added “Data Plane Backward Compatibility” (The text is taken from draft-zhang-ccamp-gmpls-evolving-g709)

4. Requirement of TPN Allocation TPN is transported in the MSI bytes of the OPUk overhead, the Received TPN should be equal to the Expected TPN TPN is the same for all the TSs assigned to the transport of the same ODUj instance on each ODUk link TPN needs to be configured on each hop of the path. So GMPLS signaling can be responsible for allocating TPN on each link …… TPN = 2TPN = 3 …… OTU3 link B A TPN = 2 MSI [i]LO ODUTPN #1ODU22 #2ODU22 #3ODU1x #4ODU1y #5ODU22 #6ODU22 #7 ~ #16Others MSI bytes in OPUk OH C TPN = 3 Received TPN = Expected TPN

5. Requirement of Control of HAO G.HAO is being developed to specify hitless adjustment of ODUflex (GFP) HAO requires configuration(e.g.TS allocation) on every node along the path. Therefore, control plane is recommended to be involved in HAO operation Added some placeholder to address HAO requirements for CP, since G.HAO is at pre-mature stage currently ABC Add TS#1 Add TS#1 Add TS#4 Add TS#4

6. Data Plane Backward Compatibility In data plane, the node supporting 1.25Gbps TS can interwork with the other nodes that only supporting 2.5Gbps TS by combining Specific TSs together (i.e., work in 2.5Gbps mode) The section is taken from [OTN-Signaling] draft, because it is more appropriate to describe the data plane stuff in framework document TS1 TS2 TS3 TS4 TS1 TS2 TS3 TS4 TS5 TS6 TS7 TS8 Node A (TS=2.5G) Node B (TS=1.25G) Resv: TS type = 2.5G, TS#2 Actually allocate TS#2 & TS#6 in its data plane

7. Next Steps Refine the document according to the progress of OTN data plane tech (e.g., G.HAO) Refine the draft based on the feedback from the meeting or mailing list