| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
G’day
Bob, It is not actually too late to reconsider the “recent IEEE 802.x withdrawals”. Some missing information meant that I did not execute this action
from Nov 2017. It is on the agenda for the IEEE 802 JTC1 SC, and I intend to execute the action after the Chicago meeting, unless told otherwise by the EC. The standards I am referring to are: ·
ISO/IEC TR 8802-1:2001 ·
ISO/IEC 15802-1:1995 ·
ISO/IEC 15802-3:1998 ·
ISO/IEC 8802-5 and anything related (such as corrigenda) Refer to slides 86-89 of the
IEEE 802 JTC1 SC agenda Andrew From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org]
On Behalf Of Robert Grow John, EC Colleagues The new text reads better, but still doesn’t answer my concern regarding 8802-2. We withdrew 802.2 years ago, but wanted 8802-2 to stick around. I hope the request wasn’t a blanket request to withdraw all international versions of all
withdrawn 802.x standards! IMHO, the EC should specifically identify by motion a request for staff to withdraw the international version when the IEEE standard is withdrawn. We probably also should consider indicating on a withdrawal ballot if the intent is to recommend
withdrawal of a corresponding international standard if the IEEE version is withdrawn. (It is too late for this on recent IEEE 802.x withdrawals, but explicit listing of the 802.x standards would be better than a general request because we still use 8802-2
capabilities in active 802 standards. —Bob
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 |