Transport NBI Design Team Update Italo Busi Daniel King Luis - PowerPoint PPT Presentation

Transport NBI Design Team Update Italo Busi Daniel King Luis Miguel Contreras Murillo Oscar González de Dios Zhangxian Tara Cummings Yan Shi Monali Chakrabarty Rod Lu Carlo Perocchio Gianmarco Bruno Qilei Wang Xing Zhao Yunbin Xu Zheng Haomian Dieter Beller Sergio Belottj Michael Scharf Young Lee Anurag Sharma Karthik Sethuraman IETF 104 (Prague)

Transport NBI DT • Design Team’s Goals and Deliverables: – Develop use cases and gap analysis • Identjfy a set of technologies use cases and providing a gap analysis against existjng models – Identjfy missing models or capability – Coordinate requirements with appropriate WGs • Including TEAS, RTGWG and CCAMP itself – Providing guidelines in terms of how all the related models can be used in a step-wise manner • Using a couple of well identjfjed transport network use cases • Working methods – Mailing lists & Conference calls – GitHub: htups://github.com/danielkinguk/transport-nbi 2 IETF 104 (Prague)

Applicability Statement Updates • Major updates since IETF 103 – Agreed defjnitjon of “Domain” – Further describes the control of access links which support difgerent technology confjguratjon (e.g., STM-64, 10GE or OTU2) depending on the type of service – Completed Ethernet service and topology descriptjon – Updated “Protectjon and Restoratjon Confjguratjon” sectjon – Improved overall readability – drafu-ietg-ccamp-transport-nbi-app-statement-05 3 IETF 104 (Prague)

Reference Network 10GE, STM-64 and OTU2 S1 S2 Network Network domain 1 domain 3 R1 R5 S3 S4 S31 S32 R6 S5 S33 STM-64 and OTU2 10GE S6 R2 S34 S8 S7 R3 STM-64 S11 S12 Network R4 domain 2 S14 S13 S15 R7 S16 S17 S18 R8 R9 S19 S20 S21

Control Hiearchy CMI MDSC Scope of the drafu MPI2 MPI3 MPI1 PNC2 PNC1 Network Domain 2 PNC3 Network Domain 1 Network domain 3

OTN and ETH TE Topology Abstractjon PNC1 black topology (OTN) PNC 3 white topology (OTN) PNC 2 black topology (OTN) S31 S32 S33 AN1 AN2 S34 PNC1 black topology (ETH) PNC 3 white topology (ETH) PNC 2 black topology (ETH) S31 S33 AN1 AN2

TE Tunnel Setup MDSC Internal Topology (OTN&ETH) S31 PNC 3 white topology (OTN&ETH) S33 S32 S34 PNC1 black topology (OTN&ETH) AN1 AN2 PNC 2 black topology (OTN&ETH) PNC 3 white topology (OTN) PNC 2 black topology (OTN) PNC1 black topology (OTN) S31 S32 S33 AN1 AN2 S34

Transparent Client Setup (STM-64 PL) MDSC Internal Topology (OTN&ETH) S31 PNC 3 white topology (OTN&ETH) S33 S32 S34 PNC1 black topology (OTN&ETH) STM-64 STM-64 AN1 AN2 PNC 2 black topology (OTN&ETH) PNC 3 white topology (OTN) PNC 2 black topology (OTN) PNC1 black topology (OTN) S31 S32 S33 AN1 AN2 S34

ETH Client Setup (EPL/EVPL) MDSC Internal Topology (OTN&ETH) S31 PNC 3 white topology (OTN&ETH) S33 S32 S34 PNC1 black topology (OTN&ETH) ETH EPL: port-classifjcatjon ETH AN1 AN2 EVPL: vlan-classifjcatjon PNC 2 black topology (OTN&ETH) PNC 3 white topology (OTN) PNC 2 black topology (OTN) PNC1 black topology (OTN) S31 S32 S33 AN1 AN2 S34

Applicability Statement Updates • JSON code folded using the method described in: htups://tools.ietg.org/html/drafu-ietg-netmod-artwork-folding – Appendix A. Validatjng a JSON fragment against a YANG Model • A.1 Manipulatjon of JSON fragments • A.2 Comments in JSON fragments • A.3 Validatjon of JSON fragments: DSDL-based approach • A.4 Validatjon of JSON fragments: why not using a XSD-based approach – Appendix B. Detailed JSON Examples • B.1 JSON Examples for Topology Abstractjon • B.1.1 JSON Code: mpi1-otn-topology.json • B.2 JSON Examples for Service Confjguratjon • B.2.1 JSON Code: mpi1-odu2-service-confjg.json • B.2.2 JSON Code: mpi1-odu2-tunnel-confjg.json • B.2.3 JSON Code: mpi1-epl-service-confjg.json 10 IETF 104 (Prague)

Next Steps • Document has a number of enhancements queued – htups://github.com/danielkinguk/transport-nbi/issues – Editors, authors and contributors need to agree which are useful, nice to have, unnecessary • Face-to-face DT meetjng planned during IETF 104 – Review open issues and enhancements – Wednesday 13:30-15:00 (Karlin 1/2) • Submit for Last Call in June 11 IETF 104 (Prague)