Skip to end of metadata
Go to start of metadata

Updated  

Outline colors reflect backward compatibility, dotted ones are planned items

Fill colors: red = do not use, green = candidate for production


GitHub Links:

RIA Links:

See here the Archived Deliveries

See here the Candidate Features for Future Releases of TAPI SDK and RIA

See here the Feature priority for TAPI "2.5"

TAPI Reference Implementation Agreements under development

  • TR-547 2.1 - February 2023
    • Reference Model version is 2.4.1
    • See TR-547 V2.1 under development for more details
    • Consolidate Optical Protection
    • Optical power minor clarification
    • Progress on 3R
    • Progress on Path Computation
  • TR-548 2.1 - February 2023
    • Security
    • Delta streaming
  • TR-547 2.2
    • RESTCONF Response codes for use cases
    • Security: identity, authentication, authorization, confidentiality
      • TLS, SSH
      • NACM

TAPI SDK


  • 2.4.0-RC1 delivered November 2022, 2.4.0 delivered December 2022. This includes RIA 2.0
    • See 2.4.0-RC1, 2.4.0
      • Delivery includes TR-547, TR-548, normalized alarms and notification/streaming scenarios
    • Not backward compatible with Version 2.1.3
    • Candidate for adoption
    • New Use Cases
      • OAM Provisioning
      • Optical Impairments (CCAMP/GNPy)
        • Including introduction of profiles/templates.
      • Physical Route
        • based on Access Ports and/or connector/pin statements
    • Consolidate/Adapt existing Use Cases to model 2.4
      • OTU layer management (as opposed to OTSi)
      • OTS_MEDIA and OMS layer qualifiers
      • Detected Condition (aligning streaming and notification approaches)
      • Clarified the navigation across layers
      • Clarification and improvement of asymmetric scenarios
      • Clarification on Notifications considering the different object relationships
      • Link between OTSi and MC/OTSiMC (transponder line ports - ROADM add/drop ports)
        • Solution is based on deprecation of OTSi qualifier and adoption of OTSiMC qualifier on both ROADM and transponder
      • Addition of Strand joint
        • Provides a more fine grained opportunity to specific fiber impairments
    • UNI and ENNI interfaces modelling
      • Options specified
    • 3R Scenarios (not fully covered at this stage)
      • In relationship with Asymmetric Service model
      • In relationship to Resiliency
      • See IETF related works
    • Begin to remove all RPCs - leaving the specification of required operations to RIA (through Restconf API spec).
    • Update the Alarm dictionary and formalize it in the model
    • Updates to streaming model
      • Improvements to the specification of stream type parameters
      • optional (preferred) use of common alarm definition
      • softening of attribute use to Conditional with clear condition statements
    • Several improvements to the equipment model


  • 2.4.1 - likely to be adopted by RIA 2.1 - February 2023
    • TR-547 RIA and other documents are under ongoing development: ONF TAPI RIA
    • Slide set which will be included in the RIA: otcc2022.AM.001_TAPI_RIASlides.pptx
    • Optical protection will be updated.
    • Profiles YANG had an issue with the augmentation with mandatory properties. This was fixed in 2.4.0 using presence.
    • Optical power minor clarification
    • Minor general issues to be fixed
    • Some common fixes to other use cases.
    • Path Computation Use Cases may be addressed, although this is not a primary priority. This should be covered in 2.5.0.
  • > 2.4.1 
    • DSR over OTSi (skip OTN) 
    • Multiband management extensions
    • OTSiG on multiple line ports
    • Replace all ENUM with IDENTITY, to allow the correct distribution of identities across the proper modules, to maintain the modularity.
    • Quality, e.g. add descriptions to UML - Technology specific modules.
    • Consider introduction of Administrative State for physical context objects.
      • Consider also more general subject of state propagation behavior.
    • Further development of Optical Impairments UCs - which lead to model changes
    • Further development of Connectivity UCs including 3R - which lead to model changes
    • Development of Path Computation UCs - which lead to model changes
      • Explore reuse of Connectivity model
      • Explore two distinct use cases:
        • Planning, i.e. create a quasi static set of paths which can used to guide future connectivity services
        • Connectivity Route Selection, i.e. at connectivity service creation, provide a set of alternative paths from which to select the preferred one
      • Consider potential improvements to diversity-policy of connectivity-service. The current enumeration does no appear to allow necessary flexibility/coverage
      • Review other work such as https://github.com/rvilalta/ietf-te-path-computation