| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Roger,
1.
If you find the 2nd sentence of paragraph 11 unintelligible then please propose new wording.
2.
You may not be aware of the issues that have been occurring with regards to the EC reflector. Therefor it seemed that there was no other way to guarantee
that this email would ever reach the intended audience other than to use the private list. I’m adding the reflector to this response. Let’s see if it will work this week. My last several attempts to use it ended up with messages not being delivered. At Paul’s
request I was in contact with the SA and they were not able to resolve the matter. In that case last week the use of the private list was agreed to by Paul and with the tight timeline that this ballot is on it seemed best to use it to better guaranty being
received by the EC..
3.
Paul did very clearly authorize me to conduct this ballot. Do you feel that there was another reference other than 8.2 that should have been used or,
that under 8.2, he is not authorized to delegate to someone else the role of conducting a ballot? The reference to 8.2 was also used on the very recent comments on the FCC’s 3.5 GHz NPRM without objection by anyone. In reviewing 8.2 I see nothing that prevents
the Sponsor Chair from delegating the function of communicating with governmental bodies. On the other hand if the Sponsor Chair is the only one who can communicate with governmental organizations then indeed he should be the sole point of contact for all
communications to and from the FCC, Ofcom, ITU, etc. Maybe the OM needs to be revised (again) to make it clear that this role can be delegated? Best regards, Mike From: Roger Marks [mailto:r.b.marks@ieee.org]
Mike, I have a few editorial and procedural comments. (1) The second sentence of paragraph 11 is unintelligible. (2) Conducting a ballot by circulation to a closed email list does not meet the requirement of OM 4.1.2: "Provision shall be made for the IEEE 802 LMSC membership to observe and comment on Sponsor electronic ballots. All comments from those
who are not members of the Sponsor shall be considered." (3) Since the language indicates OM Subclause 8.2, then the elements of 8.2.1(b) apply. In particular: "All IEEE 802 LMSC communications to government bodies shall be issued by the Sponsor Chair…" Roger On 2013/03/02, at 12:10 PM, Michael Lynch wrote:
Dear EC, During the January wireless interim meeting in Vancouver 802.18 began work on a response to the FCC’s 3.5 GHz NPRM proceeding. It was not possible to complete
the response at that meeting so a series of conference calls were announced to complete the work. Two calls, one on January 24th and the second on January 31st, were used to complete the document Doc. 18-12-0109-06. The document was approved by 802.18 by a
vote of 5 yes, 0 no and 1 abstention, submitted to and approved by the EC and filed with the FCC. During the discussion of any other business the group decided to continue to have the Thursday evening calls during the period of February 7th to March 14th.
The positive result of that action was the approval on February 28th of proposed reply comments to the FCC’s “Incentive Auction” proposal (Docket No. 12-268). This takes advantage of the FCC having extended the reply comment date to March 12th. I have asked Paul to allow me to conduct a ten day EC email ballot to approve submitting the reply comments (Doc. 18-13-0016-06-0000) to the FCC. Paul’s response to my request is: “I will authorize a 10 day EC email ballot, to be conducted by Mike Lynch, for the following motion.” Motion: “To approve, under OM Subclause 8.2, document 18-13-0016-06-0000 subject to the early close provision of OM Subclause 4.1.2.." Moved: Mike Lynch Seconded: Apurva Mody Link to the document: Reply comments are to be submitted to the FCC by March 12, 2013. The ballot will start March 2nd and end on March 11th, 2013. I am using the “private list” since once again there seems to be an issue with either delay or non-delivery when using the EC reflector. This has also impacted
the 802.18 reflector. Best regards, Mike +1.972.814.4901 |