Nigel Davis will set up an additional separate call for clarification regarding TR-548 scope, involving Jack Pugaczewski (MEF and TMF).
Arturo Mayoral, now Program Manager for TIP OOPT, restarts to follow - maybe not continuosly - the TAPI calls.
Nigel Davis mentions O-RAN where the issues regarding Performance Monitoring big amount of data are under study.
Ramon Casellas recalls that TIP OOPT CANDI is integrating GNPy in the disaggregated scenario.
Ramon Casellas recalls the issue of connection-ref and path-ref, which cannot be used because the connection and path yang nodes are read-only hence cannot be referred by a read-write list.
TAPI Call: 2 hours
Andrea Mazzini presents the latest commits to #510.
Delivering RIA 1.1 (TR-547-TAPI Reference Implementation Agreement_v1.1_RCAS.docx)
Ramon Casellas points out that UC 1h (Unconstrained asymmetric DSR Service Provisioning, UNI DSR E-NNI OTUk grey interface) needs some clarifications.
After some discussion there is a preliminary agreement on this picture (access scenario):
Nigel Davis edited the above picture to show the possible "symmetric transit scenario with client monitoring":
Preliminary agreements on the following rules in case of access and transit scenarios:
Ramon Casellas recalls a note mentioned in a previous call: “TR-547 shall include the description of the "DIGITAL_OTN ENNI", reusable for all asymmetric connectivity use cases. MEF 64 Operator Layer 1 Services could be the reference standard.”