Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.

Welcome to the ONF Transport API project !

The ONF Transport API (TAPI) project charted under the ONF Open Transport Configuration & Control (OTCC) is responsible for the development of this SDK as an Open Source project. The TAPI SDK supports interfaces to the following functional modules:

  • Topology Service
  • Connectivity Service
  • OAM Service
  • Equipment Inventory
  • Virtual Network Service
  • Path Computation Service
  • Streaming Service
  • Notification Service

For further information, please read the TAPI Overview.

If you would like to dive a bit deeper, TAPI v2.1.3 Reference Implementation Agreement (TR-547) - July 2020 is a good start.

The SDK is hosted on ONF Github repository at https://github.com/OpenNetworkingFoundation/tapi.

Latest Release: https://github.com/OpenNetworkingFoundation/TAPI/releases/tag/v2.1.3

The SDK is released under the Apache 2.0 license and consists of following components:

  • TAPI UML Information Model - which is pruned/refactored from the ONF Core Information Model 1.2
  • TAPI YANG Schema - which is generated using the EAGLE UML-to-YANG mapping tool
  • TAPI SWAGGER definitions - which is generated using the EAGLE YANG-to-JSON tool
  • TAPI Reference Implementation - the code stubs for which are generated using the swagger-code for python
  • TAPI Development Guide - a PDF document providing an overview of the SDK.
The project uses the following mailing/discussion list: https://groups.google.com/a/opennetworking.org/forum/#!forum/transport-api
  • No labels