Wrong index in ingress-ip-dscp-to-per-hop-behavior-mapping-list

[niloda]

The queue-name index of ingress-ip-dscp-to-per-hop-behavior-mapping-list provides 8 values, so is not possible to fulfill the min-elements (64) constraint.

[demx8as6]

64 entries are needed.

[niloda]

According to the description of ingress-ip-dscp-to-per-hop-behavior-mapping-list:

"... associates the value of the 8 dscp bits of the IP header with a per hop behavior at the physical interface. First entry in the list [0] relates to dscp value '0'. Last entry in the list [63] relates to dscp value '63'."

if the purpose of this object is basically to choose the output queue for packets whose priority is defined by DHCP bits, than the key of the list should be the DSCP value and the queue-name attribute should be the destination queue for any incoming packet having the DSCP priority specified by the key. The drop-precedence-inside-queue attribute should define the drop precedence (NONE, LOW, MEDIUM, HIGH) of any incoming packet having the DSCP priority specified by the key.

[openBackhaul]

Decision made at the 5G-xhaul-call on 26th of April 2023:

The following artifacts shall be created in the UML of the QosProfile:

• A DscpPerHopBehaviorType datatype
• DscpPerHopBehaviorType::dscpPriority[1] : UINT8 as a read-only key attribute with comment "Value of the dscp bits of the IP header."
• DscpPerHopBehaviorType::queueName read/write attribute with comment "Name of the queue."
• DscpPerHopBehaviorType::dropPrecedenceInsideQueue read/write attribute with comment "(if dropPrecedenceAt*QueueIsAvail for the referenced queue == false) default value shall be kept and configuration attempts shall be ignored."

The following changes shall be made on the UML of the QosProfile:

• The QosProfileConfiguration::ingressIpDscpToPerHopBehaviorMappingList shall no longer be of PerHopBehaviorType datatype, but of DscpPerHopBehaviorType datatype instead.

[openBackhaul]

UML changed as described.