search

openBackhaul / equipment

Equipment for an Ethernet PHY interface according to IEEE 802.3
Apache License 2.0
1 stars 0 forks source link

DeviceType attribute required #53

Open openBackhaul opened 1 month ago

openBackhaul commented 1 month ago

Problem: The name of the device type (e.g. “MINI-LINK Traffic Node”, “OptiXRTN950”, “AGS-20 IDU” or “ALCplus2e”) is required for proper display in the user interface.

Background: The original CoreIM does not contain a deviceType attribute. During some ONF PoC in past, adding an additional instance (“value-name”: “neType”) in a name-and-value list attribute (ControlConstruct :: extension) has been informally agreed. It contains the required string values. All officially harmonized appliances of name-and-value attributes have been replaced by explicit attributes in the meantime.

Potential Proposal: Adding a deviceType: String [1] = “Device type not yet defined.” attribute with comment “Name of the device type according to its official documentation” in ControlConstruct :: ControlConstructPac.

openBackhaul commented 1 month ago

Decision during the LF ONMI x-haul call on 19th of June 2024: Adding a read-only deviceModelName: String [1] = “Device model not yet defined.” attribute with comment “Name of the device model according to its official documentation.” in ControlConstruct :: ControlConstructPac.