Requested revision
| Standard: | 802.1Q-2018 | Clause: | 48 |
| Clause title: | YANG | ||
Rationale for revision
YANG parameters to determine or configure the transmission selection algorithm of traffic classes in bridge ports are missing
(cmp. IEEE Std 802.1Q-2018, table 8-6). As a result, it is not possible to:
a) Identify the transmission selection algorithms assigned to classes:
1) If recommendations of clause 34 in IEEE Std 802.1Q-2018 are implemented (or not)
2) In presence vendor-specific algorithms
b) Compute gate event list schedules and similar based on the identified assignments
c) Change the transmission selection algorithm of a class, if supported via management
Proposed text
a) Insert the following code to ieee802-dot1q-bridge.yang in line 1304
(i.e., as a sibling node of “container traffic-class”):
container transmission-selection-algorithm-table {
description
"The Transmission Selection Algorithm Table for a given Port assigns,
for each traffic class that the Port supports, the transmission
selection algorithm that is to be used to select frames for
transmission from the corresponding queue. Transmission Selection
Algorithm Tables may be managed, and allow the identification of
vendor-specific transmission selection algorithms. The transmission
selection algorithms are identified in the Transmission Selection
Algorithm Table by means of integer identifiers."
reference
"8.6.8 of IEEE Std 802.1Q-2018";
list transmission-selection-algorithm-mapping {
key traffic-class;
leaf traffic-class {
type dot1qtypes:traffic-class-type;
config false;
description
"The traffic class to which a transmission selection algorithm is assigned to.";
reference
"8.6.8 of IEEE Std 802.1Q-2018";
}
leaf transmission-selection-algorithm {
type uint32;
description
"The transmission selection algorithm identifier assigned to the traffic class.";
reference
“Clause 8.6.8 of IEEE Std 802.1Q-2018”;
}
}
}
b) Update the listing of ieee802-dot1q-bridge.yang in the Standard accordingly.
c) Update associated UML Figures in clause 48 accordingly.
d) Update YANG tree listings in clause 48 accordingly.
Impact on existing networks
No hardware changes in implementations expected, management via YANG needs update.
Originator
| Name: | Johannes Specht | Email: | johannes.specht.standards@gmail.com |
| Affiliation: | University of Duisburg-Essen | ||
| Submitted: | 2020-07-07 | ||