amazzini
amazzini
By design it is intended to be always present, regardless existence of children. It is unclear which are the consequences on implementations, could you kindly provide more information?
In TAPI we agreed that for elementary exchange the context instance must be present. The key requirement is that the context instance must be created by the TAPI server, not...
The TAPI team agreed to remove the "presence" statement. So far a patch version of 2.1.3 is not planned, hence the modification will be available on next 2.3 major delivery.
The apparently missing delay counter is defined in G.798: 14.2.1.2 **ODUP trail termination sink function (ODUP_TT_Sk)** 14.5.1.1.2 **ODUT trail termination sink function (ODUT_TT_Sk)** pN_delay
ODU FM & PM enhancements #454 introduces the pN_delay counter. Still to be agreed the removal of dmSource and dmValue.
MEF 10.3: "Bundling Enabled is compatible with Service Multiplexing". Hence I would recommend to model one connection. May G.8052 represent a G.8021 ETHG as single CTP?
@italobusi Because the subject is a network management model - hence for management perspective, there is no rationale to model a "bundle" of connections.
The project is https://github.com/bartoszm/yang2swagger
Regarding alarm entity, we need to check if the item is clarified in TR-547 - and if not, maybe reuse TR-548 statements.
Regarding option 2, also the target-object-name (local class, child of global class identified by target-object-identifier). There is a 5th contender, similar to 2 but based on event-notification plus detected-condition, e.g....