08 January 2018
Time | Item | Who | Notes |
---|---|---|---|
TAPI 2.0 SDK | SDK now approved and published - many thanks, especially to Karthik, Rod, Italo (note Italo contributed numerous comments, and also expressed concerns with the SDK status in the TST), and other TST members that contributed their views during the approval process over the holidays (esp. Thorsten, Weiqiang, Victor, Andrea and Kam) Follow up issues - posted in github Need to work on the FRD to define examples for common use of the model | ||
OIF Demo | Demo timetable Participants need to submit contract and NDA this Friday
Closed meetings to start next week | ||
ONF
| New project now starting on "disaggregated transport network" Controller NBI is planned to be TAPI ONF work starting under Toru Furusawa of NTT We are in contact and will be working with Toru Q: goals - not protocol/API development but open source implementation using ONOS | ||
MEF SOF-TE Service Orchestration Function - Topology Engine | Topology Engine - TAPI/NRP-based not fully open source, access to MEF members One PoC done, more in future but timeframe tbd | ||
ONF CORD/ONOS | UML-to-Protobufs work - ongoing discussion between OIMT and CORD folks development of mapping guidelines - current status in OIMT minutes | ||
ONAP WT | 4.1 PoC using WT to tie to ONAP Inventory Follow up tbd, possibly March timeframe | ||
ODL UNI Manager | TAPI/NRP implementation - part of ODL Nitrogen release | ||
TIP Open OLS work | Need to keep in touch with TIP work that is incorporating TAPI
| ||
Planning for 2018 | 2017 results:
2018 objectives:
| ||
f2f meetings |
| ||
License and copyright statements issue | Note question of what we put in the YANG files - issue for TST discussion - will be further discussed in UML mapping call | ||
Next OTCC TST call | Jan. 22nd |