openBackhaul
commented
5 months ago Decision during the LF ONMI x-haul call on 24th of April 2024: It is not reasonable to define a temperature for an expected equipment. If the definition of the ExpectedEquipment :: operationalState would be changed as proposed in the latest proposal in issue#38, §32 of chapter 9 of the TransmitterEquipment Spec. shall be complemented with the following statement 'The temperature shall always represent "".'
No default value defined in the ONF CoreIM.
Currently, §32 of chapter 9 of the TransmitterEquipment Spec. says that ExpectedEquipment :: temperature shall not be represented. The YANG module generated from the ONF CoreIM is structured in such a way that ExpectedEquipment and ActualEquipment share the same set of attributes.
If the definition of the ExpectedEquipment :: operationalState would be defined in such a way that a smaller number of attributes would be compared and representing all attributes would no longer be excluded in §32, and if we would agree that it is not reasonable to define a temperature at an expected equipment, we should define a value to be permanently represented.
Potential Proposal: If the mentioned changes would be made, §32 of chapter 9 of the TransmitterEquipment Spec shall be complemented with the following statement "Whenever the ExpectedEquipment :: temperature is represented it should have "" (empty Sting) as a read-only value."