Andrea Mazzini informs that in MEF Resource Model Project the usage of these statements has been agreed to define some macro features, e.g. "full topology management".
Karthik Sethuraman we may explore the introduction of "connectivity" and "oam" features. For further analysis.
Arturo asks whether there are news on yang2oas tool.
"I can see that OAS folder is still present in future r2.3 release for TAPI. Again, if we are publishing something that we know is wrong to our own specifications, sounds like a very bad idea."
Agreed to update the release disclaimer as follows:
TAPI OpenAPI Specification - TAPI OAS (OpenAPI Specifications) included in this TAPI release (v2.3.1) are an informative part of the TAPI SDK and intended to support TR-547 Use Cases, where a subset of mandatory API is specified.
Huy Tran points out that new parameters have been defined related to Raman fiber impairments (co-effects) for a more accurate estimation.
Explore the model solution, e.g. a new class which augments OTS/OMS links with Raman amplification.
The defined data structure is an array of 96 coefficients, each one applicable to one frequency/spectrum value.
Recalled that all the proposed "GNPy classes" can be considered as profiles, i.e. common for more instances of links, transceivers, amplifiers, etc.
10 mins
Loopback feature
Ronald
Ronald asks whether the loopback is a generic OAM job type or shall be defined in technology specific modules, e.g. Ethernet loopback, DSR loopback, ODU loopback, etc.