Minutes for 0021: TC must be configured for ETS to specify bandwidth

Standard: 802.1Qaz Clause: D2.9.7 Draft with fix: 802.1Q-cor-2-d2-0 Status: Published
Submitter: Anoop Ghanwani Date: 2012-01-06 Rationale: The current text is as follows: > The table consists of one 8-bit en...
Show Request Show Preformatted Request
Date Meeting Text Status
2012-01-11 Jan 2012 Interim It needs to be possible to configure the TCs, but not necessarily enable them for ETS yet because of timing constraints and can’t be made to work otherwise. The proposed solution doesn’t work, but what to do is still somewhat unclear. If bandwidth is assigned to a non-TC class the left over should be distributed to the other classes. This is described in 37.3.c. We could add a note here to clarify the above. It could read something like 5.4.1.6. Leave this in the received state until we have a vehicle to incorporate the fix. Received
2012-03-14 Mar 2012 Plenary Since the Q-Cor-2 is by necessity having to address items that are amendments to Q-Rev, it is conceivable that we can incorporate a small change to address this item. Anoop has proposed the following text to the end of Clause D.2.9.7 NOTE--While it is intended that only TCs configured for ETS will have a bandwidth value associated with them, it is possible, during configuration changes, to have situations where a TC is not configured for ETS but has a non-zero TCBandwidth percentage. In this case, the sum of all the TCBandwidth percentages must still be 100, but the TC bandwidth percentages of the non-ETS TCs would effectively be unused bandwidth and reallocated to the ETS TCs. Ready for Ballot
2012-07-17 Jul 2012 Plenary Q-Cor-2-d2-0 in sponsor ballot Balloting
2012-09-12 Sep 2012 Interim Q-Cor2 submitted to RevCom Balloting
2012-11-13 Nov 2012 Planery Q-Cor2 approved by SASB Approved
2013-01-15 Jan 2013 Interim Q-Cor2 was published November 2012 Published

Back