You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In general, it is expected that a valid entry in this field is supporting identifying the right components in the live network.
If some component would not have a version, or the device not provide such information a default value should be provided.
Potential Proposal:
The two entries for the version in the two tables in §31 of chapter 9 of the TransmitterEquipment Spec. shall be complemented with the following statement "If some vendor, respectively hardware would not apply the concept of versions, an empty string shall be provided. If the device would apply versions, but not be able to provide the version information, "Version not yet provided." shall be represented as a default."
The text was updated successfully, but these errors were encountered:
Proposal to the LF ONMI x-haul call on 24th of April 2024:
The default value of the EquipmentType :: version attribute (both ActualEquipment and ExpectedEquipment) has already been covered in Equipment issue#38.
If decided as proposed, this issue would be a duplicate and shall just be closed.
No default value defined in the ONF CoreIM.
In general, it is expected that a valid entry in this field is supporting identifying the right components in the live network.
If some component would not have a version, or the device not provide such information a default value should be provided.
Potential Proposal:
The two entries for the version in the two tables in §31 of chapter 9 of the TransmitterEquipment Spec. shall be complemented with the following statement "If some vendor, respectively hardware would not apply the concept of versions, an empty string shall be provided. If the device would apply versions, but not be able to provide the version information, "Version not yet provided." shall be represented as a default."
The text was updated successfully, but these errors were encountered: