dropping-behavior-kind on device/switch level

[openBackhaul]

Some implementations allow defining the dropping-behavior-kind not per interface, but per switch/device (incl. all attached interface) only.

Proposal: The dropping-behavior-kind shall become part of a Profile,

• which can be instantiated multiple times, in case the device allows independently adjusting the dropping-behavior-kind per interface,
• or just a single time, in case the device allows adjusting the dropping-behavior-kind just on device/switch level.

[openBackhaul]

Decision on 5Gxhaul call on 3rd of June: Capability attributes are to be added for expressing, whether the device is supporting configuring

• queue depth
• dropping behavior
• wred profile
• scheduler kind on an interface base.

Further on, an EthernetContainerFd shall be defined for holding the same attributes plus some similar Capability attributes for facilitating the configuring queue depth, dropping behavior, wred profile and scheduler kind on an switch base.

Next steps: Defining the Capability attributes, which are to be added to the EthernetContainer

[openBackhaul]

According to proposal in issue #28 availability of configuring queue depth would be expressed by having entries in supported-queue-depth-list, which are different from -1

[openBackhaul]

Decision on 5Gxhaul call on 3rd of June: Capability attributes are to be added for expressing, whether the device is supporting configuring

• queue depth (got obsoleted by decision on issue#28 made in May 2021)
• dropping behavior
• wred profile
• scheduler kind

on an interface base. Further on, an EthernetContainerFd shall be defined for holding the same attributes plus some similar Capability attributes for facilitating the configuring queue depth, dropping behavior, wred profile and scheduler kind on an switch base.

Next steps: Defining the Capability attributes, which are to be added to the EthernetContainer

[openBackhaul]

Concrete advice has been documented into the issue list of the EthernetContainerFd (#1).