This is the landing page of the TAPI working group of LF ONMI Project.

TAPI Main Facts:

• TAPI standardizes a single core technology agnostic specification that abstracts common transport network functions.

  • Decoupling from technology specific functions.

• TAPI model decouples service and resource oriented constructs.

  • This allows recursive application along management architecture, in a multi-carrier environment.

• TAPI model decouples functional/logical and physical oriented constructs.

  • This minimizes impacts due to technology optimization and evolution, without losing power of description.

• TAPI is defined in open-source environment.

The Ecosystem:

• TAPI and TMF

  • Leveraging 20 years of experience in developing standard management interfaces, mainly in TMF for MTNM/MTOSI (aka TMF 814)

• TAPI and ONF Core IM

  • TAPI model is a formal pruning/refactoring of the generic ONF Core IM to customize for transfer over specific interface and make the terminology more familiar to users with experience in transport network modeling.

• TAPI and ITU-T

  • TAPI Technology Specific Models are derived from ITU-T (Ethernet, Digital OTN, Photonic)

• TAPI and MEF

  • TAPI has been extended by all MEF Network Resource Models
  • TAPI has been enhanced by MEF feedbacks

• TAPI and OIF

  • TAPI has been successfully adopted by 2016, 2018 and 2020 OIF Interops

The Federation of Standard Models in Open-Source Environment:

The Transport API abstracts a common set of control plane functions such as Network, Topology, Connectivity Requests, Path Computation, OAM, and Network Virtualization to a set of Service interfaces. It also includes support for the following technology-specific interface profiles for Carrier Ethernet (L2), Optical Transport Network (OTN) framework (L1-ODU) and Photonic Media (L0-WDM).

The TAPI releases:

The TAPI Repositories

The code

• The TAPI code is composed by:
  • UML modules, managed through Eclipse/Papyrus
  • YANG modules, the schema semi-automatically generated from UML modules
  • OAS/Swagger modules, the API semi-automatically generated from YANG modules
• Latest release: TAPI v2.5.0
• Main release in production: TAPI v2.1.3
• Release in progress: TAPI develop

The documentation

• The TAPI documentation is composed by:
  • TR-547 and TR-548 Reference Implementation Agreements (RIAs)
  • From TR-547 intro: This document provides a set of requirements, guidelines and recommendations for a standard use of the TAPI models in combination with the RESTCONF protocol for the implementation of the interface between network systems in charge of the control/management of networks based on WDM/OTN technologies. This document can be used in conjunction with TR-548 which is the Reference Implementation Agreement for TAPI Streaming.
  • TAPI RIAs Ancillary Documents
    • TAPI Alarm TCA List
    • TAPI Notification and Streaming Sequences
  • TAPI Delta Document, to document the differences wrt previous release
  • TAPI Gendoc Templates, to generate MS-Word docs from UML modules
  • TAPI Tooling Guidelines, to describe the process to generate YANG and OAS modules
• TAPI 2.5.0 / 2.5.1 Documentation
• TAPI 2.1.3 Documentation
• TAPI Documentation in progress

The current activities

• Contributions for Discussions
• Meeting minutes and items under discussion
• Plan

Participate!

To get involved in the project please join the mailing list and attend meetings:

• Mailing list: [email protected]
• Meetings: Tuesday 9:00 AM US Eastern (Daylight) Time. Duration two hours.
  • Zoom
• Co-leaders: Andrea Mazzini, Nigel Davis