ONF is pleased to announce the release of updated Reference Implementation Agreements for TAPI v2.1.3, version 1.1 of TR-547 and TR-548. These 1.1 versions update and enhance the 1.0 version. The Reference Implementation Agreements are the result of joint collaboration between optical network providers and operators within the OTCC Project at ONF. The goal of this effort is to create a standard reference specification for the implementation of TAPI 2.1.3 based optical network management, by leveraging operator experiences with testing and deployment. TAPI 2.1.3 is a production-grade API that has been deployed in real networks and interoperability tested by OIF. The Reference Implementation Agreements present a comprehensive guide for the development and implementation of different use cases ranging from optical network discovery, service provisioning, hardware inventory and simple fault management.
The target audience for this document is both network providers deploying TAPI as a northbound interface for their SDN controller systems, and client layer applications and Operations Support Systems (OSS) consuming TAPI as a southbound API.
TR-547 v1.1 is the result of a thorough, line-by-line review of version 1.0, resulting in better and more detailed explanations, enhanced document structure and overall consistency and readability. It incorporates feedback from Interop testing of TAPI 2.1.3, such as the need to supplement RESTCONF related standards specifications to facilitate interoperability.
Support for new operator uses cases has also been added, e.g.
- Multi-domain OTN interdomain links discovery.
- Asymmetric DSR Service Provisioning, DSR UNI to OTUk E-NNI grey interface.
- Subscription to Notification Service for Alarm and Threshold Crossing Alert (TCA) events.
- Notification of Alarm and Threshold Crossing Alert (TCA) events
The Reference Implementation Agreement has also been supplemented with a spreadsheet specifying over 100 standard Alarms and PM Parameters.
TR-548 v1.1 provides requirements, use cases and guidelines for use of TAPI 2.1.3 Streaming Yang. TAPI Streaming is an alternative to the traditional notification mechanism specified in TR-547 covering all TAPI modelled information including NEPs CEPs, equipment etc. as defined in TR-547 and associated Yang, and provides a specific alarm structure that enables alarm streaming. TAPI Streaming offers various stream strategies. TR-548 v1.1 focuses on a stream strategy (compacted log with whole entity on change) designed to enable a TAPI client to gain and maintain alignment (eventual consistency) with the relevant current state of the network, as presented via the TAPI Context, by simply connecting to the appropriate streams. With this strategy, there is no need to get information for initial alignment as the stream is based upon a compacted log that essentially maintains the current state in the stream. Each stream also provides ongoing reporting of change so as to enable the TAPI client to maintain alignment.
Interest from TIP
TIP MUST (Mandatory Use Case Requirements for SDN for Transport) subgroup, an operator-led subgroup aiming to accelerate and drive the adoption of SDN standards for transport technologies, is referencing TAPI defined use cases in TR-547 and TR-548 as part of the technical requirements defined to evaluate SDN commercial solutions following TIP's Test and Validation framework. In the short term, MUST will release the first Ribbon Eligibility process for Optical SDN Controllers to evaluate their support of the standard Northbound Interface based on TAPI models. The MUST subgroup will also continue collaborating with the ONF at the definition of new versions of the TAPI models and Reference Implementations towards the standardization of the features and use cases of interest of the operators participating in MUST.
Learn more about the Open Transport Configuration and Control Working Group.
Authors: Nigel Davis (Ciena), Lyndon Ong (Ciena), Ramon Casellas (CTTC), Arturo Mayoral (TIP), Andrea Mazzini (Nokia)