Minutes for 0023: Priority and Drop_eligible parameters from BSI MEP/MIP

Standard: 802.1Q-2011 Clause: 6.11.2 Draft with fix: Status: Rejected
Submitter: Maarten Vissers Date: 2012-01-16 Rationale: The specification in c6.11.2 specifies: ?The priority and drop_eligible...
Show Request Show Preformatted Request
Date Meeting Text Status
2012-03-14 Mar 2012 Plenary The general belief is that the scope of changes required to address this item are beyond the current scope vehicles that are open. Any changes here would be effectively undoing previous agreements and thus this item will be left in the ‘received’ state for consideration in a future revision. This item is related to 0026 as well with similar resolution. Subclause 6.11 is specifically states that it replaces subclause 6.9 in a CBP. This means that the setting of the priority and drop_eligible parameters in 6.11.2 occurs in request primitives after the queues, and therefore has no effect on the queueing. The proposed resolutions do not change this. Any change that would result in using the PCP from the I-tag to determine the priority for queuing in the B-component would require significant restructuring of the document and significant technical changes to the standard. All B-components in the backbone network forward the frames based on the PCP from the B-tag, and it is not obvious that the final B-component the frame traverses should behave any differently. Received
2012-07-17 Jul 2012 Plenary The general belief is that the scope of changes required is too large to address this proposal as a maintenance item. This would be a feature change rather than a bug fix and thus this item will be ‘rejected’ ‐‐ the commenter may pursue this in a future Q revision (PAR approved at July plenary). This item is related to 0026 as well with similar resolution. Rejected

Back