Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [802SEC] Comments and reply comments to Public Trial of Google TVWS Database



All:

 

It took a long time to get Wi-Fi Alliance to recognize that regulatory and standards development are two very different things, and need different rules to operate efficiently.

 

Standards development starts with the interested parties agreeing on a schedule, usually a long-term schedule, and maintaining control of that schedule. Hence, meeting times can also be agreed upon by the interested parties.

 

Regulatory work is totally reactionary. Our schedules are imposed on us, usually with very little warning and no flexibility.

 

It is like applying the same rules to your daily schedule and avoiding an incoming comet.

 

I don’t expect the EC to change these rules quickly, but if this work is to be done properly, it must have the flexibility to react as necessary.

 

Rich Kennedy

MediaTek Inc. 

rich.kennedy@mediatek.com

(832) 298-1114

 

Wi-Fi Alliance Spectrum & Regulatory TG Chair

Wi-Fi Alliance White Spaces MTG Vice-chair

IEEE802.11 TGaf (WLAN in White Spaces) Chair

IEEE802.11/15 Regulatory SC Chair

IEEE802.18 Vice-chair

IEEE 802.11/18 Liaison

 

 

 

 

From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of Nancy Bravin
Sent: Wednesday, July 30, 2014 7:59 AM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] Comments and reply comments to Public Trial of Google TVWS Database

 

All,

 

Respectfully, all WG chairs are voting members of 802.18, along with those with earned voting rights in 802.18, and many are on the EC.

When the response time is 15 days, as it is with the Google trial, and other regulatory bodies often have short reply comments, less than the rules allow,

is it possible for the Sponsor to allow a vote this time by 10 day email ballot, while a response is worked on, and then address the rules

in general to adapt the 30 day rule for this type of exception. Even if it is just a positive reinforcement, 802’s voice should be heard.

 

My personal opinion only. Sincerely, Nancy

 

On Jul 30, 2014, at 5:35 AM, Jon Rosdahl <jrosdahl@ieee.org> wrote:



One way around this snafu or rather the next one would be to schedule weekly calls for 802.18...similar to what 802.11 has for its Regulatory SC.

The calls are often cancelled for lack of an agenda, but that way they can meet when an urgent matter pops up.

IT also gives the participants a tentative place holder on their calendar to make "finding" that time quicker.

Just a thought,
Jon

 

On Wed, Jul 30, 2014 at 6:05 AM, Rich Kennedy <rkennedy1000@gmail.com> wrote:

James:

 

Sixty minus 40 is 20 days; the Reply Comment period for this proceeding. We have also had 15 days from Japanese regulators, which needed bidirectional translations.

 

The government may not work fast, but they do expect us to.

 

Rich Kennedy

 

 

-----Original Message-----
From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of James P. K. Gilb
Sent: Wednesday, July 30, 2014 1:51 AM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] Comments and reply comments to Public Trial of Google TVWS Database

 

Mike

 

These are not new rules.  They are the rules under which we have been operating for at least 4 years.

 

We may have been ignoring these rules, but it is not correct to say that they are new.

 

BTW: Since when does the government only allow 20 day responses to any proposed rule change?  I am not as familiar with the processes as you are, but I thought that they needed to give adequate notification.

 

Thanks

 

James Gilb

 

On 07/29/2014 12:40 PM, Michael Lynch wrote:

> John,

> Correct, another item that the new rules prevent us, as 802, from commenting on. The member's sponsors will be the ones having to do these filings.

> Best regards,

> Mike

> From: ***** IEEE 802 Executive Committee List *****

> [mailto:STDS-802-SEC@ieee.org] On Behalf Of John H Notor

> Sent: Tuesday, July 29, 2014 09:28

> To: STDS-802-SEC@LISTSERV.IEEE.ORG

> Subject: [802SEC] Comments and reply comments to Public Trial of

> Google TVWS Database

> FYI,

> Released:  07/29/2014.  OFFICE OF ENGINEERING AND TECHNOLOGY REQUESTS

> COMMENT ON THE PUBLIC TRIAL OF GOOGLE, INC.'S TV BAND DATABASE SYSTEM

> REGISTRATION PROCEDURES. (DA No.  14-1079). (Dkt No 04-186 ). Comments

> Due:  08/13/2014. Reply Comments Due:  08/19/2014.  OET . Contact: 

> Alan Stillwell at (202) 418-2925 or Hugh Van Tuyl  (202) 418-7506

> https://apps.fcc.gov/edocs_public/attachmatch/DA-14-1079A1.docx

> https://apps.fcc.gov/edocs_public/attachmatch/DA-14-1079A1.pdf

> https://apps.fcc.gov/edocs_public/attachmatch/DA-14-1079A1.txt

> Comments Date:  August 13, 2014

> Reply comments Date:  August 19, 2014

> Unfortunately, 802.18 won't be able to comment on this, since our first teleconference meeting is scheduled on August 20, due to the 802 P&P 30 day notice requirement for meetings.

> John

> John Notor

> President/Chief Technologist

> Notor Research

> Mobile: 1.408.316.8312

> Mobile: 1.408.799.2738

> Web: www.notor.com<http://www.notor.com>

> ---------- 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.




--

-------------------------------------------------------------------------------
Jon Rosdahl                         Senior Standards Architect
hm:801-756-1496                  CSR Technologies Inc.
cell:801-376-6435                 10871 North 5750 West 
office: 801-492-4023             Highland, UT 84003

A Job is only necessary to eat!
A Family is necessary to be happy!!

---------- 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.