Open rservadio opened 1 year ago
Proposal: Option #2
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:
UML changed as described.
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:
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