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

[danielkinguk]

Some early text for discussion.

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.
<<

[danielkinguk]

Action: Explain that "well-defined, also includes procedure and usage, and need to include that YANG is used to model capability.

[ggrammel]

What is a little confusing is that the current definition does not define "from where" the T-NBI is exposed. Furthermore, there current definition proposal does not refer to topology while the Scope of the document speaks about it:

The analysis provided in this document confirms that the IETF YANG models defined in [RFC8453], [RFC8795], [OTN-TOPO], [CLIENT-TOPO], [TE-TUNNEL], [PATH-COMPUTE], [OTN-TUNNEL], and [CLIENT-SIGNAL] can be used together

A suitable modification addressing those issues would be:

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 topology, capability and infrastructure assets by (sub-)network controllers 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) APIs are well-defined, open interfaces exposed by (sub-)network controllers and vital for operating the network. 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.

[danielkinguk]

Need to be clear in where "T" (Transport) in T-NBI for CCAMP applies.