openBackhaul / qosProfile

Quality of Service Definitions based on 802.1p, MPLS Exp and IP DSCP
Apache License 2.0
0 stars 0 forks source link

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

Open niloda opened 2 years ago

niloda commented 2 years ago

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 commented 1 year ago

64 entries are needed.

niloda commented 1 year ago

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 commented 1 year ago

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

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

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

openBackhaul commented 10 months ago

UML changed as described.