| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
The ANA accepts requests for allocation of numbers from the 802.11 Regulatory (REG) SC, subject to approval by the WG. The purpose of this support is to allow the WG to track rapidly changing regulatory requirements in a controlled way.
The process is as follows:
1. A request to the ANA from the REG SC shall be approved by motion in a meeting of the REG SC. The intent to hold a motion and the supporting documentation shall be announced to the WG on the WG reflector 4 weeks in advance of the motion being considered. Any motion in the REG SC shall be brought to the WG for confirmation.
2. The request shall be accompanied by a submission that can be referenced from the Description field of any allocation (i.e., entry in the ANA database) explaining how that value is used, and providing any additional information that cannot be recorded in the ANA database.
a. For example, a request for a new operating class would be accompanied by all the information that would go in a draft amendment or standard associated with the value – i.e., the full table row contents.
3. The ANA shall circulate the requests and tentative assignments to the 802.11 editor's reflector and ask TG editors to check for any conflict. Typically the requests are generated following a session. The ANA should respond to the request within 1 week. The ANA shall reject any request that is not properly formed, i.e., does not supply all information required by the ANA form, or does not provide a reference document that fully describes the use of the requested value. The last item of any resource will never be assigned and will always automatically be designated as “escape bit/number”.
4. After a period of 1 week has elapsed and no conflict has been reported, the assignments are confirmed and the ANA shall upload an updated database document and notify the WG reflector.
5. The REG SC can, at its option, update the cited reference document to show the allocated value(s).
6. The ANA will bring any such allocations as a proposed change to TGm when a revision project is active.
----------------------
Dorothy Stanley
IEEE 802.11 WG Chair, dstanley@xxxxxxxx
Hewlett Packard Enterprise
dorothy.stanley@xxxxxxx
dstanley1389@xxxxxxxxx
+1 630-363-1389
Dorothy,
This contribution (11-20/0568) and its discussion, and the discussion on March 8 (REVmd telecon) on 11-19/1778 have reminded me of my request for status on a process for maintaining the regulatory tables in Annex E (and Annex D?) outside the REVision process. I know we have had some discussion in the past of an alternate process for maintaining these tables (probably something more like the IEEE’s maintenance process) – I just don’t recall the outcome or if any decisions were made. I think we need to address this, and settle on a process that can more adequately keep up with the changing regulatory environment, and will involve the appropriate experts in the review and discussions.
Thanks. Mark
From: ***** 802.11 REVm - Revision Maintainance List ***** <STDS-802-11-TGM@xxxxxxxxxxxxxxxxx> On Behalf Of M Montemurro
Sent: Thursday, April 9, 2020 3:18 PM
To: STDS-802-11-TGM@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGM] Updated submission on Japan regulatory updates (was Remove channel 14)
--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---
Hi all,
Thanks for the feedback. I posted an updated submission that updates Annex E with regulatory updates for Japan.
Cheers,
Mike
To unsubscribe from the STDS-802-11-TGM list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM&A=1
To unsubscribe from the STDS-802-11-TGM list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM&A=1