[CCAMP] Do we need a definition for the term "T-NBI"..?

[Italo Busi <[e-mail]>]

As discussed during the CCAMP WG session today, we are looking for some feedbacks from the WG about this open issue we are discussing in the context of the TNBI DT:

https://github.com/ietf-ccamp-wg/transport-nbi/issues/115

The initial definition (to be improved) we are considering is the following:

      The optical transport domain is designed to support various connectivity services, such as Wave Division Multiplexing (WDM) and the Optical Transport Network (OTN). A primary objective for network operators is to automate the establishment of these services in single-layer and complex hierarchical, multi-domain optical transport networks. Exposing capability and infrastructure assets are crucial to providing access to network resources and offering advanced control and manageability features. Optical transport Application Programming Interface (API) becomes essential to achieve this.
      The "Transport Northbound Interface" (T-NBI) API are well-defined, open interfaces vital for network operators. They provide the capability to view optical transport resources and effectively operate multi-vendor and multi-domain networks. Furthermore, the T-NBI API is instrumental in facilitating the coordination and automation of service provisioning, thereby enhancing efficiency and operational flexibility when managing optical network resources.
Do you have any comments or suggestions on how to improve this definition?

Thanks, Italo