2018-04-20 ODTN(NTT Com)

1 ODTN-Open and Disaggregated Transport Networks -Toru FurusawaNTT CommunicationsAgenda Technology Trends of Disaggregated Transport Networks Introduction of ODTN Project Project Scope Members & Teams Schedule Software Design Current Project Status & Next Steps2 Technology Trends of Disaggregated Transport Networks From All-in-One to Disaggregation Innovations and upgrades from per all-in-one nodes to per each component Integration from in hardware to in software Active Open communities for disaggregated transport networks Open Line Systems OpenConfig & Optical Transport DomainAccess DomainMPLSVLAN/OTNOTN / WDMVNFFromAll-in-One toDisaggregationTransport NW ControllerOrchestratorREST APINETCONF4 Traditional optical line systems are integrated systems with a single vendor s transponder, mux/demux, amp.

2 ROADMOpen Line Systems4 Open Line Systems are disaggregated systems composed of multi-vendor transponders Possible to use preferred vendor s transponder every time of wavelenth expansionOpenConfig5 Google-Driven community to define vendor neutral data models for device configuration and telemetry Covering multiple layers (L1-L3) Out of scope: Data Plane interoperability, controller software & southbound protocolSDN CtrlModel: OpenConfigProtocol: NETCONF/gNMI(out of scope)YANGT ransport API TAPI ONF Driven API used for NBI of Transport Network ControllersONF TAPI6 Towards Full Open Architecture with existing activities7 Open NBISDN ControllerExisting communities are focused on each specific targetNo Integrated Solution in open source community-> Build a reference implementation by using those communities outputsOpen SBIOpen CtrlOpen DeviceOrchestratorOpen Line SystemTransport APIV endor Controller<As-Is> <To-Be>Proprietary NBIP roprietary SBIV endor Proprietary DeviceODTN Project8

3 YANGNETCONFOLS / DisaggregationDataModelLanguageOpenProto colCommonDataModelOpenSourceControllerIn novativeDeviceReference ArchitectureComponentProject members As of We have launched ODTN (Open and Disaggregated Transport Networks) Project with ONF and other companies to build a open reference implementation with open technologiesNBITAPIP roject Members9 Project Purpose and Charter Bring eco-system together to Build reference implementation using open source and open standards Do lab and field trials Consisting of three phases Plan/Retrospective meetings for each phase Kick-off with 3 leading service providers, 8 vendors (as of Jan 2018)10 Project Scope11 Point-to-PointSDN ControllerTransport API(TAPI)YANGYANG(1) NBI Handler(3) SBI Driver(2)

4 Service ApplicationNETCONFRESTCONFC ompileCompileMapping LogicImplement(4) Integration Test(1) NBI HandlerCompile YANG based service modelProvide TAPI based NBI(2) Service ApplicationImplement Java code to map TAPI to OpenConfig(3) SBI DriverCompile YANG based device modelConfigure device with OpenConfigmodel(4) Integration & TestPhase 1: Point-to-Point Open Line System with Open APIsGoal Integrate ONOS and OLS devices with a simple P-to-P topology by using open API (TAPI / OpenConfig) Build and verify the reference implementation for P-to-P use case Identify problems to be solved for the phase 2 Device Components Transponder OLS: mux/demux, in-line amplifierTerm Jan 2018 -Aug 2018 (8 months) Phase (transponder only): Jan 2018 April 2018 Phase (transponder + OLS).

5 May 2018 August 20181212 WSSTRNAPIOpen Line System (OLS)APIAPIMUXWSSAMPMUXTRNP hase 2: Mesh Metro ROADM with Open APIsGoal Integrate ONOS and ROADM devices with a partial mesh topology by using open APIs Build and verify the reference implementation metro ROADM use case Identify problems to be solved for the phase 3 Device Components Transponder ROADMTerm Sep2018 April201913 TRNROADMROADMROADMROADMTRNTRNTRNAPIAPIAP IAPIP hase 3: Full Disaggregated ROADM with Open APIsGoal Integrate ONOS and disaggregated optical components by using open APIs Verify the reference implementation that works certainly for disaggregated ROADM use case Identify problems to be solved toward productionDevice Components Transponder, WSS, AMP, AOS, etc.

6 (details TBD)Term May2019 -Dec201914 TRNTRNTRNTRNC lient ports(add)To/from packet layerWSSAMPAOSC lient ports(drop)Line portsSingle wavelengthTo/from network controlEMSTo/from remote ROADMAPIAPIAPIAPIAPIP roject Teams15Te a mActive MembersProject SteeringComcast, NTT Com (Project Chair), Telefonica, 1 vendor, ONFUse CaseCiena, Comcast, Coriant, NEC,NTT Com(lead), Nokia, Telefonica, TIMetcSoftware DevelopmentCTTC, NEC (lead), Nokia, Oplink, ZTEetcInfrastructure (not formed yet)TBD -formed for each service provider labTe st i n g ( n o t f o r m e d ye t )

7 TBD -work closely with SW Development TeamSchedulePhase2 Mesh ROADMP hase1 Point-to-PointJanFebMarAprMayJuneJulyAug SepResult & PlanWorkshopOctDev & integrationInitial devices + Dev & interchangeability test+ additional devicesODTN KickoffResult & PlanWorkshopDev & integrationTBDONS talkOFC talkNovDecResult & PlanWorkshopECOCP hase Transponder onlyPhase Transponder + OLSAppNetwork Service RequestInstruction to deviceTAPI over RESTCONFOpenConfigover NETCONFT ransponderTransponderOLS Driver XDriver YDriver ZSolves constrained pathManage resourcesGenerate device control and configurationMap imposed semantics to commands that device understandsProtocol handlingUnderstand semantics of requestSB driver layerControl logicNB API mediation layerHigh Level Design17 Model Definition work by Use Case Team(0.)

8 Scope Clarification and TAPI Model Selection) NBI Parameter Mapping (ConnectivityService/SEP -> Connection/CEP) Parameter Selection (Connection/CEP) mapped to Mapping from TAPI (Connection/CEP) to OpenConfig(different for each vendor) Model Selection(different for each vendor)18 OrchestratorConnnectivityService/SEP Connection/CEPC onnection/CEP OpenConfig/CEPC onnection/CEP OpenConfig/CEPT ransponderTransponderTransponderConnecti on/CEP OpenConfig12354commonNBI(RESTCONF)NETCON F different for each vendorModel Discussion slide in Use Case TeamTransponder1 Transponder2aggregateaggregateLink (200G)Link (40G)DSRDSRDSR Link Conn(40G)DSR Conn(40G)DSR Connectivity Service (40G)x5x5x5x5x5x5 TAPI Model for phase layer(ignored)Must be done in advanceODTN Scope for Phase ParametersTAPIOpenConfigHow to configurestep 0 TopologyTransponder, Fiber, Link ports, Client ports(for )Link, Node, NEP, SIPn/avia API (for Provider)or Auto-generated( using show cmd or LLDP)

9 Step 1 Optical parametersFrequency, Modulation, Power, FEC, etc?OTSi layer (+OTN?)Connection/CEP not used for phase parametersfor line portsvia API (for Provider)step 2 Connection between line port and client portDSR layerConnection/CEPC onnectivityService/SEPPort mapping betweenline and clientvia NBI (for Client)Configurablew/ OrangeBoxNot neededfor pre-configuration ofoptical parametersModel Discussion slide in Use Case TeamCurrent Status & Next Steps TAPI & OpenConfigmodel definitions for phase Software development in progress 2 vendors transpondersto be tested for the phase Nokia Infinera F-2-F Meeting planned in May Agenda Phase summary Phase planning Any other discussions (TBD) Location ONF Office in Menlo Park, California To be announced our Wiki and join us!

10