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 ---
Hello Mark: I recall having a similar discussion in REVmc in the context of resolving MLME related comments for Fine Timing Measurement. We added a set of “and not present otherwise” because of the discussion. This make it clear on when to expect/not
expect something to be included. We also raised potential inconsistencies as a result of adding ‘and not present otherwise’ which we felt is required in other (non-FTM related) occurrences but did not pursue it precisely for the reason you state below:
Cheers -- ganesh “It is amazing what you can accomplish if you don’t care who gets the credit.” – Harry Truman From: Mark Hamilton <mark.hamilton2152@xxxxxxxxx> --- This message came from the IEEE 802.11 Working Group Reflector ---
All, REVme is looking for feedback on current implementation behavior/assumptions on a wide-ranging technical point: REVme is discussing a comment on D1.0 (CID 1622) that requests, in effect, to add a statement to clause 9 that wherever we currently have a requirement such as “the xxx element is present if condition yyy is true”, then there is an implicit
_requirement_ (to be made explicit by this comment) that if “condition yyy” is not true then “xxx” is _not_ present. Specifically, the added sentence(s) would be: “If an element is indicated as present when certain conditions are met, this is to be understood as meaning that the element is not included if these conditions are not met.” Some considerations, and where we would like feedback:
Feedback to this reflector, or to the REVme reflector, is appreciated. Thanks! Mark 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 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 |