Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Pat: Good catch. I missed it. Editorial privileges will fix it. Thanks. Rich Kennedy Manager, New Technology Development MediaTek Inc. rich.kennedy@mediatek.com (832) 298-1114 Wi-Fi Alliance Spectrum & Regulatory TG Chair Wi-Fi Alliance White Spaces TTG Chair Wi-Fi Alliance White Spaces MTG Vice-chair IEEE802.11 TGaf (WLAN in White Spaces) Chair IEEE802.11/15 Regulatory SC Chair IEEE 802.11/18 Liaison Sent from my awesome BlackBerry Passport
Dear Adrian, I think this is a good course to follow. One additional edit is needed. III Conclusion begins â??IEEE 802 appreciatesâ?? which should be changed to â??IEEE 802.11
appreciatesâ?? Regards, Pat From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org]
On Behalf Of Stephens, Adrian P Dear EC members, I am responding as described in this email to the failure of the EC motion on the question, â??Move
that EC approves transmission of document 11-15/683r2 (https://mentor.ieee.org/802.11/dcn/15/11-15-0683-02-0reg-comments-in-fcc-15-47.docx) to the FCC as a letter
in response to FCC docket 15-47, granting the LMSC Chair editorial license.â?? I hereby request a â??Sponsor memberâ?? review of document
https://mentor.ieee.org/802.11/dcn/15/11-15-0683-05-0reg-comments-in-fcc-15-47.docx as an IEEE 802.11 WG communication to the FCC under the procedure in 8.2.2 the IEEE LMSC OM: â??8.2.2 Sponsor subgroup communications with government bodies a) Sponsor subgroup communications with government bodies shall not be released without prior approval by 75% of the Sponsor subgroup. Such
communications may proceed unless blocked by a Sponsor vote. For statements not presented for review in a sponsor meeting, Sponsor members shall have a review period of at least five days; if, during that time, a motion to block it is made, release of the
statement will be withheld until a letter ballot of the Sponsor is held to determine if it is approved. b) Sponsor subgroup communications shall be identified in the first paragraph as the view of only the Sponsor subgroup and shall be issued by
the Sponsor subgroup(s) Chair(s) and shall include the Sponsor Chair in the distribution. Such statements shall not bear the IEEE, the IEEE-SA, or IEEE 802 LMSC logos.â?? The cited procedure states that the review period should be at least 5 days. As there is a long weekend coming up for many, I am indicating
a review period of 7 days, ending midnight UTC-12 on 2015-07-08. The submission deadline to the FCC is Wednesday July 15th, so any EC actions related to this need to take place during the Monday EC
plenary (July 13th) (I have requested an agenda slot as a contingency). No action of the EC will be necessary if no motion to block is made. This modified communication has not yet been approved by 802.11. I am anticipating a motion to approve the document as reviewed by the EC at
the 802.11 WG Monday plenary. The 802.11 WG motion will be essentially identical to: â??Approve transmission of document 11-15/683r5 to the FCC as a letter in response to FCC
docket 15-47, granting the 802.11 WG chair editorial licenseâ??. I would be astonished if such a motion was not approved in the WG, hence my presumption in asking for the EC to review this updated document now.
Compared to the document that has already been reviewed, the following changes have been made: 1.
The initial paragraph makes it clear this is a communication from the 802.11 Working Group 2.
A new final sentence has been added: â??IEEE 802.11 will continue to monitor progress towards resolving the exclusion zone and FSS protection limitations, and
will re-evaluate our position as conditions dictate.â?? A redline is attached for your convenience. This shows as tracked changes the changes between R2 (approved by the WG and motioned originally in
the WG) and R5, which is the subject of the current review. The submission responds to comments received during the EC ballot as follows: Apurva wrote: â??I feel that this Document should be the position of the 802.11 / 802.15 Working Groups. So I am okay if this is sent out as a Liaison
from IEEE 802.11 / 802.15 Regulatory Standing Committee or the Working Groups but not as an IEEE 802 LMSC Position.â?? (excerpt) The updated document represents only an 802.11 WG position. (I should add that Apurva also had disagreements with technical content. You can see his full argument here:
http://www.ieee802.org/secmail/msg18886.html) Subir wrote: â??Subir: "Towards that I liked Richâ??s suggestion on adding
â??IEEE 802 will continue to monitor progress towards resolving the exclusion zone and FSS protection limitations, and will re-evaluate our position
as conditions dictateâ??. It would be good if we return this to 802.11/15 REG group and allow them for another round of discussions. OTH, if it delays a timely response,
WG can communicate to FCC directly since it does not require an EC approval motion as pointed out by Roger."â?? 1)
The text cited above has been added to the updated document 2)
The updated document represents only an 802.11 WG position Pat wrote: â??Pat: "My vote is Approve if the â??continue to monitor progressâ?? text is added. Disapprove otherwise"â?? That text has been added. Roger wrote: â??Roger: "The statement under discussion is very narrowly drawn toward an 802.11 position. If it were reformatted as an 802.11 communication
in accordance with 8.2.2 and presented for five-day review, I would not move to block it."â?? (excerpt) (The rest of his response is here:
http://www.ieee802.org/secmail/msg18897.html) We are presenting this as an 802.11 position for 5-day review. I believe these comments have been addressed in the draft sent to review in a manner that is consistent with at least one of the alternatives (where
present) requested in the comment. Best Regards, Adrian P STEPHENS Tel: +44 (1793) 404825 (office) ---------------------------------------------- ---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
|