| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
| --- This message came from the IEEE 802.11 Working Group Reflector ---
Dan, I think receivers should process all valid frames (within reason). Of course! But where is the normative requirement that they have to, in order to be compliant with the IEEE 802.11 spec? I don’t see any specific statement anywhere, and apparently neither does Mark H. I’m open to correction; does anyone have a specific
page and line number? Perhaps we should add one in REVme? It’s a bit late for devices that have already deployed, but by all means let’s fix what we can. However, many of the later amendments have much longer maximum frame sizes. Table 9-34 says that HE PSDUs have a maximum size of 6,500,631 octets. Seems like a lot! Is there really an implied requirement that all HE STAs shave to be able
to receive PSDUs of this size? I don’t see any such requirement anywhere (again, open to correction on this). To reiterate on the proposed note that started this discussion, it seems fully reasonable to expect (and require) all STAs to be able to receive 2304 octets. I’m against adding a note that discourages transmitters from sending frames of
this length. Regards, Sean From: Harkins, Daniel <daniel.harkins@xxxxxxx> Hello, On 2/8/22, 9:06 AM, "Sean Coffey" <coffey@xxxxxxxxxxx> wrote: --- This message came from the IEEE 802.11 Working Group Reflector ---
Mike, Mark, all, I agree with Mark that there is no explicit requirement that a STA has to be able to receive all possible legal frames successfully. Minimum receive sensitivity requirements imply that STAs have to be able to receive
certain lengths (1024 octets, 4096 octets, etc.), and perhaps there are implied requirements to be able to receive lengths that are used in some control frames, but where is the requirement that the receiving STA has to be able to process all frame lengths
(or more to the point, all possible frames of all possible lengths) successfully? I’d describe it as an expectation, rather than a requirement, that receivers have to be able to process valid frames. However, I don’t think it’s helpful to add a note here, and especially not the proposed note,
which seems to place the onus on transmitters. Receivers are not required to process valid frames? What kind of standard is this!? The baseline for interoperability (which is the whole point of doing a standard, right?) is that every valid thing that can be constructed and sent can
be received and processed. On top of that we can have requirements to ignore what you don't understand—be conservative in what you send and liberal in what you accept, etc—or drop things that you don't understand or whatever, but if our standard doesn't require
that valid frames have to be able to be processed on reception then we have a bigger problem. Dan. -- "the object of life is not to be on the side of the majority, but to escape finding oneself in the ranks of the insane." – Marcus Aurelius
To unsubscribe from the STDS-802-11 list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11&A=1 |