| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Antonio,Ok, that's fine. I just thought that at some point, we mentioned that even a "receive only" device would have to transmit some information, so that the AP knows the broadcast traffic stream is being consumed.I'm happy having a receive only device, I just wanted to check that this is still a valid statement.Kind regardsStephenOn Mon, 9 May 2022 at 11:33, ANTONIO DE LA OLIVA DELGADO <aoliva@xxxxxxxxxx> wrote:Hi Stephen, why do you say this device is not feasible? for example, a device receiving EBCS which does not require negotiation nor request, does not need to tx any .11 frame. Am I wrong?ThanksAntonioEl lun, 9 may 2022 a las 12:22, Stephen McCann (<mccann.stephen@xxxxxxxxx>) escribió:Dear all,I'm working on CID 3148 that questions whether the PICS definition of "CF STARXOnly" is still valid or not.My interpretation of this definition is that it is a STA that is not capable of transmitting any frames (related to the IEEE 802.11 standard). So, it's scope is wider than that of TGbc.My feeling is that following all our discussions in TGbc this sort of device is no longer feasible.Thoughts/comments?Kind regardsStephen
To unsubscribe from the STDS-802-11-TGBC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBC&A=1
--Antonio de la Oliva
Associate Professor
Telematics Department
Universidad Carlos III de Madrid
E-mail: aoliva@xxxxxxxxxx
Phone: +34 91 624 8803
Fax: +34 91 624 8749
To unsubscribe from the STDS-802-11-TGBC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBC&A=1
To unsubscribe from the STDS-802-11-TGBC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBC&A=1