Equipment category is listed as “[RACK, SUBRACK, CIRCUIT_PACK, SMALL_FORMFACTOR_PLUGGABLE, STAND_ALONE_UNIT]” while the complete values are “[EQUIPMENT_CATEGORY_RACK, EQUIPMENT_CATEGORY_SUBRACK, EQUIPMENT_CATEGORY_CIRCUIT_PACK, EQUIPMENT_CATEGORY_SMALL_FORMFACTOR_PLUGGABLE, EQUIPMENT_CATEGORY_ STAND_ALONE_UNIT]”.
Andrea Mazzini could be useful to distinguish between "handshake/discovery" phase, where the received far end SAPI is accepted by default and "control/connectivity monitoring" phase, where the received far end SAPI is checked against accepted SAPI, and e.g. TIM alarm is raised if different.
Nigel Davis and Ramon Casellas agree that an orchestrator can manage the SAPI/DAPI combinations at the two ENNI terminations:
East ENNI-N it is SAPI-East/DAPI-West
West ENNI-N is it SAPI-West/DAPI-East
Cristian Rosero provides a demo of the related code, showing how the algorithm eventually combines the two East/West identifiers into a unique value.
Ramon Casellas suggests to split the "inter-domain-plug-id" attribute of ENNI-N NEP into e.g.
delegating to the orchestrator the appropriate recombination.
Cristian Rosero will come back with additional considerations on the OTN interdomain links discovery procedure.
When the provisioning of a ConnectivityService implies not only the creation of supporting Connections but also the creation of other supporting ConnectivityServices then the association (composition) between CSEPs, CSEP has Server CSEP may not be appropriate. One issue is the possible overlap between CSEPs belonging to different CSs, another issue the explicit provisioning of UUID of the "supporting" ConnectivityServices, which are actually created by the Server.
Summary of the agreements:
Given the YANG tree constraints, we may need to introduce the "Order" concept, where the ConnectivityServices (and their CSEPs) instances can be organized to provide complex provisioning directives. The "Order" instance will be the root of a new tree. This would allow the independent creation of distinct ConnectivityService instances, a sort of nuance of intent result:
Order is provisioned by the Client.
ConnectivityServices and Connections are created be the Server.
The ConnectivityServices (and CSEPs) belonging to the Order are distinct instances wrt the ConnectivityServices (and CSEPs) created by the Server.
With respect to UC 1g (and analogous 2b: Unconstrained service provisioning with ODU selection), two possible solutions: