| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Apurva, I approve. Steve -----Original Message----- Hi Apurva, I vote approve on this amended motion. Best regards, David ----- From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of Steve
Shellhammer Sent: 17 January 2018 19:17 To:
STDS-802-SEC@LISTSERV.IEEE.ORG Subject: Re: [802SEC] +++ ECM (Early Close) +++ 802.22b ISO/IEC/JTC1 Response I will still Second. Steve From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of Mody,
Apurva (US) Sent: Wednesday, January 17, 2018 10:55 AM To:
STDS-802-SEC@LISTSERV.IEEE.ORG Subject: Re: [802SEC] +++ ECM (Early Close) +++ 802.22b ISO/IEC/JTC1 Response Thanks Subir and All, I have been having some background coordination with others who have already voted on the motion.
I agree with the comment made by Pat and Geoff where the original sentence
"However, the provision of additional ciphers may enhance 802.22's ability to address special use cases and will provide alternatives as the default cipher is compromised in the future." should be changed to "However, the provision of additional ciphers may enhance 802.22's ability to address special use cases or specific national or future market needs." Rich, Clint, Jon, Adrian, Bob, Pat and James who voted on the motion have suggested that they will re-approve the motion or change their vote from Dis-approve to Approve if this change is made.
So if Steve Shellhammer agrees to seconding the amended motion, I would like to change the motion words to the ones below: Amended Motion: ----------------------------------------------------------------------------------------------- EC Approves the IEEE Std. 802.22b-2015 Comment Resolutions Responses for the FDIS Ballots as contained in Document: https://mentor.ieee.org/802.22/dcn/17/22-17-0090-01-0000-802-22b-iso-iec-jtc1-comment-resolutions.doc
with editorial change, where the current sentence However, the provision of additional ciphers may enhance 802.22's ability to address special use cases and will provide alternatives as the default cipher is compromised in the future. is changed to "However, the provision of additional ciphers may enhance 802.22's ability to address special use cases or specific national or future market needs." Move: Apurva Mody Second: Steve Shellhammer For: Against: Abstain: Start of ballot: Tuesday 16th January 2018 Close of ballot: Thursday 25th January, 11:59PM AOE ---------------------------------------------------------------------------------------------- Thanks Apurva From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of Das,
Subir Sent: Wednesday, January 17, 2018 1:39 PM To:
STDS-802-SEC@LISTSERV.IEEE.ORG Subject: Re: +++ ECM (Early Close) +++ 802.22b ISO/IEC/JTC1 Response *** WARNING *** EXTERNAL EMAIL -- This message originates from outside our organization. Apurva, I also agree with Pat's suggested change. One should not include the cipher as default if there is a knowledge/proof that it will be compromised in future. I assume this is not the case here. The current
language however indicates that. In addition, it does not mention a time line when this default cipher may be obsolete.
So my approve vote is conditional.
Regards, _Subir From:
owner-stds-802-sec@ieee.org [mailto:owner-stds-802-sec@ieee.org] On Behalf Of Mody, Apurva
(US) Sent: Monday, January 15, 2018 12:36 PM To:
STDS-802-SEC@LISTSERV.IEEE.ORG Cc: 'Apurva Mody' <apurva.mody@whitespacealliance.org> Subject: [802SEC] +++ ECM (Early Close) +++ 802.22b ISO/IEC/JTC1 Response Dear All, During the IEEE 802 November 2017 Plenary meeting, we had tabled this motion to send the IEEE 802.22b response to the ISO/IEC/JTC1 due to lack of appropriate words for the response.
The EC did not like the words as were discussed and suggested in the ISO/JTC1 Standing committee.
After discussions with Andrew Myles, we have agreed to a slight change in the response to the comment made by the China NB.
Note - The 802.22b-2015 Draft has been approved to be an ISO Standard. So this response is being sent to them as a courtesy.
I am attaching the original EC motions package, and the Draft Response document with marked up text that highlights what changed.
Paul approves starting an EC e-mail ballot and Steve has re-agreed to second the motion. Motion: ----------------------------------------------------------------------------------------------- EC Approves the IEEE Std. 802.22b-2015 Comment Resolutions Responses for the FDIS Ballots as contained in Document: Move: Apurva Mody Second: Steve Shellhammer For: Against: Abstain: Start of ballot: Tuesday 16th January 2018 Close of ballot: Thursday 125th January, 11:59PM AOE Early close: As required in subclause 4.1.2 'Voting rules' of the IEEE 802 LAN/MAN Standards Committee (LMSC) Operations Manual, this is notice that, to ensure the release is provided in a timely manner,
this ballot may close early once sufficient responses are received to clearly decide a matter. Sufficient responses to clearly decide this matter will be based on the required majority for a motion under subclause 7.1.1 'Actions requiring approval by a majority
vote' item (h), 'Other motions brought to the floor by members (when deemed in order by the Sponsor Chair)' of the IEEE 802 LAN/MAN Standards Committee (LMSC) Policies and Procedures. Dr. Apurva N. Mody Chair, IEEE 802.22 Working Group Chairman, WhiteSpace Alliance Acting Chair, National Spectrum Consortium T: +1 603 885 2621 | M: +1 404 819 0314 | E:
apurva.mody@baesystems.com,
apurva.mody@ieee.org
www.baesystems.com Connect with BAE Systems: ---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv. |