WRED profile is difficult to be used

[niloda]

Some devices support a WRED profile composed of 1 to 4 sets of thresholds, one for each combination of drop-precedence and traffic types. Of course, thresholds can have the same value for multiple combinations of drop precedence and traffic. Once created, the profile can be connected to any of the queues of an Ethernet port. One and only one profile can be assigned to a queue.

For these devices, the current WRED profile model is difficult to apply. The following figure shows the relationship between a configuration of WRED profiles in the current yang model and the corresponding configuration on the device.

The configuration is just an example and does not need to be realistic. Anyway, the relationship between the two models highlights:

• that the number of profiles does not match, therefore the UUID assigned by the NETCONF interface cannot be maintained easily (there is no one-to-one relationship)
• that the profile can be written to the device only after being assigned to a queue (when the combination of drop-precedence and traffic type is known).

Conceptually, replacing the queue's wred-behavior-list with a simple pointer to the profile, and allowing the WRED profile to contain a list of sets of thresholds indexed with the combination of drop-precedence and traffic type, would help to have a one-to-one mapping between the current TR-532 models and the model on the device (backward compatibility needs to be evaluated).

This issue affects both the wred-profile-1-0.yang model and the ethernet-container-2-0.yang model.

[openBackhaul]

Decision during the LF ONMI x-haul call on 10th of July 2024:

The following read-only attributes to be added to the EthernetContainerCapability class:

• wredProfileIsAvail: Boolean [1] = false with comment "true = The device supports individual WRED Profiles at every interface."
• wredTemplateProfileIsAvail: Boolean [1] = false with comment "true = The device supports WRED Template Profiles."
• wredTemplateProfileConfigurationIsAvail: Boolean [1] = false with comment "true = The WRED Template Profile can be configured individually at every interface."

The following read/write attribute to be added to the QueueBehaviorType datatype:

• _wredTemplateProfile: Profile [0..1] with comment "Only relevant, if EthernetContainerCapability::wredTemplateProfileIsAvail == true. Associates an instance of WredTemplate Profile to the queue. Attribute to point to an instance of Profile with profileName=='PROFILE_NAME_TYPE_WRED_TEMPLATE_PROFILE'."

Further on, a new modelling for WredTemplateProfile to be created and to be put side-by-side to the existing definitions of the WredProfile.