Transport NBI Design Team Update Italo Busi Daniel

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 Belotti 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 • Identify a set of technologies use cases and providing a gap analysis against existing models – Identify 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 identified transport network use cases • Working methods – Mailing lists & Conference calls – Git. Hub: https: //github. com/danielkinguk/transport-nbi IETF 104 (Prague) 2

Applicability Statement Updates • Major updates since IETF 103 – Agreed definition of “Domain” – Further describes the control of access links which support different technology configuration (e. g. , STM-64, 10 GE or OTU 2) depending on the type of service – Completed Ethernet service and topology description – Updated “Protection and Restoration Configuration” section – Improved overall readability – draft-ietf-ccamp-transport-nbi-app-statement-05 IETF 104 (Prague) 3

10 GE, STM-64 and OTU 2 Reference Network domain. S 1 1 R 1 S 2 Network domain 3 R 5 S 4 S 31 S 32 STM-64 and OTU 2 S 5 R 2 R 6 S 33 10 GE S 6 S 34 S 8 S 7 R 3 STM-64 R 4 Network domain 2 S 11 S 12 S 14 S 13 S 15 S 18 S 17 S 16 R 7 R 8 R 9 S 19 S 20 S 21

Control Hiearchy CMI MDSC MPI 1 MPI 2 MPI 3 PNC 2 PNC 1 Network Domain 2 PNC 3 Network domain 3 Scope of the draft

OTN and ETH TE Topology Abstraction PNC 1 black topology (OTN) PNC 3 white topology (OTN) PNC 2 black topology (OTN) S 31 S 32 S 33 AN 1 AN 2 S 34 PNC 1 black topology (ETH) PNC 3 white topology (ETH) PNC 2 black topology (ETH) S 31 S 33 AN 1 AN 2

TE Tunnel Setup MDSC Internal Topology (OTN&ETH) S 31 PNC 3 white topology (OTN&ETH) S 33 S 32 S 34 PNC 1 black topology (OTN&ETH) AN 1 PNC 1 black topology (OTN) AN 2 PNC 3 white topology (OTN) PNC 2 black topology (OTN&ETH) PNC 2 black topology (OTN) S 31 S 32 S 33 AN 1 AN 2 S 34

Transparent Client Setup (STM-64 PL) MDSC Internal Topology (OTN&ETH) S 31 PNC 3 white topology (OTN&ETH) S 33 S 32 S 34 PNC 1 black topology (OTN&ETH) STM-64 AN 1 AN 2 STM-64 PNC 2 black topology (OTN&ETH) PNC 1 black topology (OTN) PNC 3 white topology (OTN) PNC 2 black topology (OTN) S 31 S 32 S 33 AN 1 AN 2 S 34

ETH Client Setup (EPL/EVPL) MDSC Internal Topology (OTN&ETH) S 31 PNC 3 white topology (OTN&ETH) S 33 S 32 S 34 PNC 1 black topology (OTN&ETH) ETH EPL: port-classification EVPL: vlan-classification AN 1 AN 2 ETH PNC 2 black topology (OTN&ETH) PNC 1 black topology (OTN) PNC 3 white topology (OTN) PNC 2 black topology (OTN) S 31 S 32 S 33 AN 1 AN 2 S 34

Applicability Statement Updates • JSON code folded using the method described in: https: //tools. ietf. org/html/draft-ietf-netmod-artwork-folding – Appendix A. Validating a JSON fragment against a YANG Model • • A. 1 A. 2 A. 3 A. 4 Manipulation of JSON fragments Comments in JSON fragments Validation of JSON fragments: DSDL-based approach Validation of JSON fragments: why not using a XSD-based approach – Appendix B. Detailed JSON Examples • • • B. 1 JSON Examples for Topology Abstraction B. 1. 1 JSON Code: mpi 1 -otn-topology. json B. 2 JSON Examples for Service Configuration B. 2. 1 JSON Code: mpi 1 -odu 2 -service-config. json B. 2. 2 JSON Code: mpi 1 -odu 2 -tunnel-config. json B. 2. 3 JSON Code: mpi 1 -epl-service-config. json IETF 104 (Prague) 10

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