Minutes for 0211: AdminCycleTime and Interval max values

Standard: 802.1Qbv-2016 Clause: 12.29.1; 17.2.22; 17.7.22 Draft with fix: 802.1Qcw/D0.3 Status: Approved
Submitter: Marina Gutiérrez Date: 2018-09-18 Rationale: The parameter AdminCycleTime as well as the interval encapsulated in the...
Show Request Show Preformatted Request
Date Meeting Text Status
2018-09-26 6 Nov 2018 Concall Received Received
2018-11-06 6 Nov 2018 Concall There was a question if this is a bug fix or an enhancement request. Marina wasn't sure, but feels the current inconsistency and acceptable range is problematic for deployment. The author of Qbv had reviewed the proposal and was comfortable with it. Not all participants had fully reviewed the item and were not prepared to comment It was decided to re-visit this item in detail at the Plenary and allow others time to review Technical experts review
2018-11-13 Nov 2018 Plenary The item was presented by the submitter. It was felt that having additional objects that clarify the maximum supported values, as indicated in the submission, would be a good idea. It was felt that this could be considered a bug because base text and information model is not is not specifying a range, but many other objects may have a similar issue. While it is possible for a management station to build a schedule, deploy it and then determine that a device can not support the provided cycle time, it was felt this was too onerous of a process and having the provided max value objects would be helpful. It was discussed that making such a change is in scope of 802.1Qcw and that this would be the appropriate vehicle to make the change. So, the submitter's proposal is accepted and the change will be made in 802.1Qcw. Complete then Ballot
2019-07-16 Jul 2019 Plenary resolution in Qcw/D.03 Balloting
2023-10-17 17 Oct 2023 Concall P802.1Qcw/D2.2 is in pre-publication. Approved

Back