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

QOS profile configuration: ingress list key parameter #13

Open rservadio opened 1 year ago

rservadio commented 1 year ago

The following ingress list:

have the "queue-name" as key parameter but from the description it appears that the order in the list is important and meaningful: "... First entry in the list [0] relates to p-bit value '0'. Last entry in the list [7] relates to p-bit value '7' "

Two considerations:

  1. it should be better to avid an association between p-bit value and the position of the parameters in the list
  2. the egress lists, with similar parameters, have a different organization with "mapping-number" as key parameter.

With reference to ingress-8021p-to-per-hop-behavior-mapping-list the proposal is to change the modelling in one of the two proposed options:

CURRENT VERSION: ingress-8021p-to-per-hop-behavior-mapping-list

PROPOSED CHANGE option-1: ingress-8021p-to-per-hop-behavior-mapping-list

PROPOSED CHANGE option-2 (to be aligned with egress list management): ingress-8021p-to-per-hop-behavior-mapping-list

Same changes could be applied to ingress-exp-to-per-hop-behavior-mapping-list and ingress-ip-dscp-to-per-hop-behavior-mapping-list

demx8as6 commented 1 year ago

Proposal: Option #2

openBackhaul commented 1 year ago

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

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

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

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

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

Egress: 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 8 months ago

UML changed as described.