Refactoring InterfaceStatusType

[openBackhaul]

Decision on the 5G-xhaul call on 23rd of March 2022:

• The 'ADMIN_DOWN' and the 'LOWER_LAYER_DOWN' value shall be deleted from the list.

• The comments of the remaining values shall be complemented by the following statements:

  • UP: 'It is expected that the LogicalTerminationPoint::operationalState attribute is expressing this logical layer being available for use (means: ENABLED), while this value occurs.'

  • DOWN: 'It is expected that the LogicalTerminationPoint::operationalState attribute is expressing this logical layer being NOT available for use (means: DISABLED), while this value occurs.'

  • TESTING: 'It is expected that the LogicalTerminationPoint::operationalState attribute is expressing this logical layer being NOT available for use (means: DISABLED), while this value occurs.'

  • UNKNOWN: 'While this value occurs, the LogicalTerminationPoint::operationalState attribute, which is expressing the availability of the logical layer for being used, might have either ENABLED or DISABLED as value.'

  • DORMANT: 'It is expected that the LogicalTerminationPoint::operationalState attribute is expressing this logical layer being available for use (means: ENABLED), while this value occurs.'

  • NOT_PRESENT: 'It is expected that the LogicalTerminationPoint::operationalState attribute is expressing this logical layer being NOT available for use (means: DISABLED), while this value occurs.'

  • NOT_YET_DEFINED: 'While this value occurs, the LogicalTerminationPoint::operationalState attribute, which is expressing the availability of the logical layer for being used, might have either ENABLED or DISABLED as value.'

[openBackhaul]

Solved with WireInterface_2.0.0-tsp.220324.1100+yang.1