Glenn,
Looking at 802.1Q, I certainly don’t understand from the “copy and paste” response to 5.5 Need why a revision is required to a recently published revision (2022) with possibly only one amendment rolled up into the next revision. Were I on the EC, you would need to answer the Need better to get my vote. Are the changes from the one Amendment so significant that the user base for the standard would significantly benefit from the merge? Was the last revision rushed resulting in so many maintenance requests that an immediate new revision is needed? Or is the Need for an immediate revision something else not really addressed by the generic response to rollup amendments and maintenance changes?
—Bob
On Mar 14, 2023, at 2:59 PM, Glenn Parsons <00000f6f9e80d40c-dmarc-request@listserv.ieee.org> wrote:
Folks, Two proposed PARs for maintenance rollups of both 802.1Q and 802.1AS are posted here: These are maintenance PARs to rollup the approved and published amendments of 802.1Q and 802.1AS into new base standards with no new functionality added -- i.e., no CSD requirement and pre-circulate up to 48 hours before the closing EC. Paul has confirmed this as an ordinary item, so this is for consideration at the Friday EC. FYI, a timeline of these standards was presented to the 802.1 opening plenary: Cheers, Glenn. -- Glenn Parsons Chair, IEEE 802.1 WG +1-514-379-9037
To unsubscribe from the STDS-802-SEC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-SEC&A=1
To unsubscribe from the STDS-802-SEC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-SEC&A=1
|