transponders and system software • Allows system software to operate with any TAI-compliant transponders • Allows transponders to operate in any system which supports TAI • By decoupling the transponders from the rest of the system, it allows each to innovate independently • Available here: ◦ https://github.com/Telecominfraproject/oopt-tai ◦ https://github.com/Telecominfraproject/oopt-tai-implementations HW Independent Application X TAI libtai.so (for vendor A) Transponder A HW Independent Application X TAI libtai.so (for vendor B) Transponder B Same codebase HW Independent Application Y TAI libtai.so (for vendor B) Transponder B Multiple NOS choices Disaggregated Same codebase Multiple transponder choices from TIP summit 2018
for operators like YANG models • TAI is not trying to become a de jure standard or standardization body Application TAI libtai.so (for vendor A) Transponder A Application TAI libtai.so (for vendor B) Transponder B Application Transponder C Application Transponder D YANG model YANG model YANG model YANG model Operation Support Systems / SDN Controller / Orchestrator Operator Software Transport Component Transponders with TAI Transponders without TAI from TIP summit 2018
Infusion provides OpenConfig NBI interface to us with OcNOS (Thanks!) Application TAI libtai.so (for vendor A) Transponder A Application TAI libtai.so (for vendor B) Transponder B YANG model YANG model SDN Controller / Orchestrator Operator Software Transport Component OcNOS TAI libtai.so (for vendor A) Transponder A TAI libtai.so (for vendor B) Transponder B OpenConfig ODTN TAPI
Mapping between OpenAPIs: TAPI => OpenConfig => TAI • Got confidence that Cassini/OcNOS/TAI are promising devices/NOS/API as whitebox transponder • Still work in progress • Some features of TAI are not implemented as of now • Exposed configurations are limited as well • Will be able to have a full capability of TAI in a year • Some critical issues are found in DCS • Should be addressed from its design • Good requirement for next DCS