openBackhaul / ethernetContainer

Technology specific interface definition for an Ethernet Container
Apache License 2.0
1 stars 0 forks source link

supportedAlarmList to get DefaultValue and * #42

Closed openBackhaul closed 2 years ago

openBackhaul commented 4 years ago

The current concept of supportedAlarmList:

This concept doesn't work, because it is not assured that devices support the mandatory alarms. As a consequence they could not be listed in the Capability attribute. In worst case (happened at least for HybridMwStructure and PureEthernetStructure) the device does not support any alarm at all at this interface.

Because it is a list attribute, but does not have a default value, the attribute doesn't show up in the implementation in this case.

Proposal: All supportedAlarmList attributes shall have multiplicity and default value "Supported Alarms Not Yet Defined." supportedAlarmList : String [] = "Supported Alarms Not Yet Defined."

openBackhaul commented 3 years ago

Decision on the 5G-xhaul call on 16th of June The EthernetContainerCapability::supportedAlarmList attribute shall be changed from [2..] to [] multiplicity, the default value "Supported Alarms Not Yet Defined." shall be added and the formulation "Mandatory:'framingIsFaulty' and 'containerIsDown'. " shall be removed from the comment.

supportedAlarmList : String [*] = "Supported Alarms Not Yet Defined."

openBackhaul commented 2 years ago

obsoleted by issue #47