| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
| --- This message came from the IEEE 802.11 Task Group M Technical Reflector ---
Graham, I can agree with 0 being legal, and probably even the most used value, on receive. It is a bit harder to understand on transmit. If we allow 0 in (for example) the TXVECTOR, then the very low levels of the stack have determined that actual on-the-air energy should start and bits should start to modulate, but we still have no idea what antenna(s) will be used to do this? If not here (in the TXVECTOR), then where will this information come from, and when? For Table 15-1, in particular, I agree that we should (next ballot?) clean this up, as it is completely unspecified what should happen when diversity _is_ enabled. (By the way, I think that would be 255, not 0. So maybe here it is 1-255, to be correct.) On receive, it seems to indicate that for some reason (perhaps reasonable, perhaps just sloppy implementation) the actual antenna used to receive something is no longer known. OK, I can see that a functioning system could happen this way. Mark From: ***** 802.11 REVm - Revision Maintainance List ***** [mailto:STDS-802-11-TGM@xxxxxxxx] On Behalf Of Graham Smith --- This message came from the IEEE 802.11 Task Group M Technical Reflector --- Hi Jon, I am still not sure about this. To me the Antenna ID is very clear, it can be 0 to 255. 1 to 254 are specific antennas, 0 is unknown and 255 is multiple. Hence 0 and 255 are valid values. Furthermore I would opine that 0 is the most used value. Graham From: ***** 802.11 REVm - Revision Maintainance List ***** [mailto:STDS-802-11-TGM@xxxxxxxx] On Behalf Of Jon Rosdahl --- This message came from the IEEE 802.11 Task Group M Technical Reflector --- Greetings, CID 195 and 196 address a concern where a parameter to hold an antenna ID should have a valid range of 1-254. Antenna ID is defined in 9.4.2.40 (Antenna element). Variables that hold an specific valid Antenna ID include TX_ANTENNA (specific for transmit), RX_ANTENNA (specific ID for receiving antenna), dot11CurrentTXAntenna (specific ID for transmitting), dot11CurrentRxAntenna (specific ID for receiving antenna), dot11AntennaListIndex (specifies a valid antenna ID). These variables do not provide for the value of "0 = unknown" or for "255 = Multiple Antenna". The CIDs and the proposed resolutions are noted below.
Comment: The antenna ID in the Antenna element is only allowed to be from 1 to 254 (0 and 255 have special meanings) Proposed Change: Change 256 to 254 in Table 16-1, 15.2.2.7 and Table 16-2; change 255 to 254 in C.3 for dot11CurrentTxAntenna, dot11CurrentRxAntenna and dot11AntennaListIndex Proposed Resolution: REVISED (GEN: 2018-01-18 08:42:37Z) CID 196 Comment: The antenna ID in the Antenna element is only allowed to be from 1 to 254 (0 (unknown) and 255 (multiple) have special meanings, but maybe they're allowed on receive) Proposed Change: In Table 16-5 change 1-256 to 1-254. In Table 17-2 change 0-255 for ANT_STATE to 1-254 Proposed Resolution: REVISED (GEN: 2018-01-18 07:56:47Z) There are only 3 instances of ANT_STATE which is referenced as the receive antenna information, so the change to RX_ANTENNA is consistent. A Motion will be prepared to accept the proposed resolutions for CID 195 and CID 196 made on Thursday PM1 slot. regards, Jon -----------------------------------------------------------------------------
_______________________________________________________________________________ IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your request to this CLOSED reflector. We use this valuable tool to communicate on the issues at hand. SELF SERVICE OPTION: Point your Browser to - http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM and then amend your subscription on the form provided. If you require removal from the reflector press the LEAVE button. Further information can be found at: http://www.ieee802.org/11/Email_Subscribe.html _______________________________________________________________________________ _______________________________________________________________________________ IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your request to this CLOSED reflector. We use this valuable tool to communicate on the issues at hand. SELF SERVICE OPTION: Point your Browser to - http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM and then amend your subscription on the form provided. If you require removal from the reflector press the LEAVE button. Further information can be found at: http://www.ieee802.org/11/Email_Subscribe.html _______________________________________________________________________________ IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your request to this CLOSED reflector. We use this valuable tool to communicate on the issues at hand. SELF SERVICE OPTION: Point your Browser to - http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM and then amend your subscription on the form provided. If you require removal from the reflector press the LEAVE button. Further information can be found at: http://www.ieee802.org/11/Email_Subscribe.html _______________________________________________________________________________ |