Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

[STDS-802-11-TGM] 11me/D2.0 CID 3683 (drop v ignore v discard)



--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---

Here is what I have now for CID 3683, for upload as 22/2069r8.

On further examination, the stuff about dropping on page 5683 seems

to be not about failing to receive, but about abandoning an attempt

to transfer a frame after a number of retries, so I've used "abandon"

rather than "fail (to receive)".

 

Proposed changes:

 

Here are the instances of “drop” excluding those adjacent to { eligib protectedframe dot11 level eaves }.

 

Change “drop”/“dropped” highlighted in yellow to “discard”/“discarded”.

Change “drop”/“dropped” highlighted in green to “ignore”/“ignored”.

Do not change “drop”/“dropped” highlighted in magenta.

 

1860.54: With the information from the DEI subfield, a STA may selectively drop frames with the DEI subfield set to 1

2496.52: The STA may pause Data frame transmission and may drop any received Data frames until the SA query procedure has completed successfully

2526.47: the AP shall delay the actual transmission of a Measurement Pilot frame according to the basic medium access rules specified in Clause 10 (MAC sublayer functional description) for a maximum period of one dot11RMMeasurementPilotPeriod and drop the delayed Measurement Pilot frame at the next TMPTT. In this way, a continuously busy medium causes multiple successive Measurement Pilot frames to be delayed, then dropped.

2601.65: The proxy ARP function shall drop those messages if the target IP address does not correspond to an associated STA.

2623.61: Figure 11-46—Group addressed GAS frame exchange with a response drop

2625.40: X = frame is dropped

2628.17: If the GAMode associated with the Query Request is true and the advertisement server(#571) has no response to the Query Request, the advertisement server(#571) may drop the request.

2628.41: If the responding STA does not receive a GAS Comeback Request frame whose source MAC address and dialog token match the source MAC address and value of the Dialog Token field respectively of the corresponding GAS Initial Response frame within this time, it may drop the query response.

2629.49: If the query response is subsequently received from the advertisement server(#571), it shall be dropped by the responding STA.

2629.57: NOTE—If there is no response to the Query Request, the advertisement server(#571) may drop the request.

If the Query Response received from the advertisement server(#571) is larger than dot11GASQueryResponseLengthLimit or requires more than 128 fragments for transmission to the requesting STA, it shall be dropped by the responding STA.

2630.24: If the query response is subsequently received from the advertisement server(#571), it shall be dropped by the STA.

2) If the Query Response received from the advertisement server(#571) is larger than dot11GASQueryResponseLengthLimit, it shall be dropped by the responding STA.

2686.32: The AP or PCP should stop the spatial sharing of two or more SPs if it determines that the link quality of any of the links involved in the spatial sharing has dropped below acceptable levels.

2795.22: The receiver drops MPDUs received out of order, i.e., not received with increasing sequence numbers.

2809.6: NOTE—This works because if an attacker modifies the TSC, then the encryption key is modified and hence both the ICV and MIC decrypt incorrectly, causing the received MPDU to be dropped.

2830.57: If it is identical, the frame shall be dropped.

2831.10: If there are no protocol instances indexed by that peer MAC address, the frame shall be dropped.

2832.57: The mesh STA with the numerically greater of the two MAC addresses shall drop the received SAE Commit message

2946.15: An AP that has both dot11ProtectedTXOPNegotiationActivated is false and dot11ProtectedQLoadReportActivated is false shall drop all received Public Key frames.

3022.57: — If the Peer Nonce field is present in the received frame, and the localNonce in the mesh peering instance is different from the Peer Nonce field of the received frame, the frame shall be dropped.

— If the peerNonce in the mesh peering instance exists and is different from the Local Nonce field of the received frame, the frame shall be dropped.

4437.1: The PHY entity shall switch to the IDLE state immediately after the energy drops below the specified threshold.

4571.27: If no such WIGTK exists, the WUR non-AP STA shall silently drop the frame and terminate BIP processing for this reception.

4614.32: Did receive signal strength drop significantly?

4615.3: the PHY shall keep decoding until receive signal strength drops significantly.

5383.34: For EDCA operation, this counter shall be incremented for each MSDU dropped by the AP on the voice access category."

5384.1/30/59: ditto “MSDU dropped by the AP”

5385.25: For EDCA operation, this counter shall be incremented for each MSDU dropped by the AP on the best effort access category and for each MSDU dropped by the AP on either user priority 0 or 3. For DCF operation, this counter shall be incremented for each MSDU dropped by the AP."

5385.59/60/62, 5386.26/57, 5387.21/50, 5388.15/44: ditto “MSDU dropped by the AP”

5411.5/19/34/48: When the RSSI drops below this threshold, a report is issued.

5682.6: If a stream is dropped, the scheduler might use the time available to resume contention. The scheduler might also choose to move the TXOPs for the STAs following the STA dropped to use the unused time.

5682.18: Figure K-3—Reallocation of TXOPs when a stream is dropped

5682.60: For example, UP-based ACU is possible by examining the UP field in TSPEC to decide whether to admit, retain, or drop a stream. If the UP is not specified, a default value of 0 is used. If a higher UP stream needs to be serviced, an ACU might drop lower UP streams.

 

Change “ignore”/“ignored” to “discard”/“discarded” in:

 

10.23.5.7 RAW Operation with Resource Allocation frame

The AP transmits the RA frame to non-AP STAs belonging to the RAW group allocated to access the RAW as specified in the previously transmitted RPS element. A non-AP STA that does not belong to the RAW group may ignore the RA frame.

 

10.36.5.2 Rules for VHT sounding protocol sequences

A STA ignores received VHT NDP Announcement, VHT NDP, and Beamforming Report Poll frames if dot11VHTSUBeamformeeOptionImplemented is false.

 

10.42.10.2.3.4 MIMO phase–nonreciprocal

A responder whose corresponding bit in the Group User Mask field of the MIMO Setup Control element included in the received MIMO BF Setup frame is equal to 0 can ignore frames transmitted in the following MU-MIMO BF training subphase and MU-MIMO BF feedback subphase.

 

10.53.3 Group sectorization operation

A non-AP STA that is not group sectorized capable may ignore the sectorized Beacon frame and is not subject to the rules described in this subclause.

 

11.3.3 Frame filtering based on STA state

If an IBSS STA receives a Class 2 or Class 3 frame, it shall ignore the frame.

 

11.3.5.3 AP or PCP association receipt procedures

11.3.5.5 AP or PCP reassociation receipt procedures

This MLME-DISASSOCIATE.request primitive generates a protected Disassociation frame. If the association request was genuine, the STA has deleted the PTKSA by this point and so the protected Disassociation frame is ignored.

 

11.21.2.8 BSS color in use event

An AP shall not transmit frames to a non-AP HE STA during a TXOP, if it has received a BSS color in use event report from that non-AP HE STA with a nonzero BSS color in the Event Report field and the AP ignores an inter-BSS PPDU with the same BSS color value as the one carried in the Event Report field to obtain a TXOP by following the procedure in 26.10.2.2 (General operation with non-SRG OBSS PD level) and 26.10.2.3 (General operation with SRG OBSS PD level).

 

11.31.3.1 General

A STA that does not support the FST protocol shall ignore a received FST Setup Request frame.

 

11.31.5 On-channel Tunneling (OCT) operation

A receiving TR-MLME shall ignore the received On-channel Tunnel Request frame if that frame is not targeting an NT-MLME in the same multi-band capable device as the TR-MLME.

 

11.40 Notification of operating mode changes

A VHT STA associated with a VHT AP shall ignore Notify Channel Width frames received from the VHT AP.

 

26.6.3.4 Ack-enabled multi-TID A-MPDU operation

A STA that transmits an ack-enabled multi-TID A-MPDU that contains at least two tagged MPDUs shall ignore the immediate response if it is an Ack frame.

 

26.10.2.2 General operation with non-SRG OBSS PD level

The received PPDU is an inter-BSS PPDU (see 26.2.2 (Intra-BSS and inter-BSS PPDU classification)), and the received PPDU is not a non-HT PPDU carrying a response frame (Ack, BlockAck, or CTS frame); or the received PPDU contains a CTS, a PHY-CCA.indication transition from BUSY to IDLE occurred within the PIFS time immediately preceding the received CTS, and that transition corresponded to the end of an inter-BSS PPDU that contained an RTS that was ignored following this procedure.

 

26.10.3.2 PSR-based spatial reuse initiation

may issue a PHY-CCARESET.request to ignore the associated HE TB PPDU(s) that are triggered by the Trigger frame

 

29.9.2 WUR Short Wake-up frame operation

Otherwise, a WUR AP shall not transmit WUR Short Wake-up frames to a WUR non-AP STA and the WUR non-AP STA shall ignore received WUR Short Wake-up frames with a matching WUR ID and FCS.

 

The WUR non-AP STA shall ignore received WUR Short Wake-up frames with a matching WUR ID and FCS after the WUR non-AP STA received a WUR Short Wake-up frame with a matching WUR ID and FCS, until a new WUR ID has been configured at the WUR non-AP STA by the WUR AP.

 

Change as follows:

 

11.2.3.6 AP operation

Until the transmission of this BU either has succeeded or is presumed failed (when maximum retries are exceeded), the AP shall acknowledge but ignore then discard all PS-Poll frames from the same STA.

 

11.31.3.2 Transitioning between states

Upon receipt of an FST Setup Request frame, the responder shall respond with an FST Setup Response frame unless it has a pending FST Setup Request frame addressed to the initiator and the responder has a numerically larger MAC address (see 12.7.1.1 (General) for comparison of MAC addresses) than the initiator’s MAC address, (#274)in which case the responder shall ignorediscard the received FST Setup Request frame.

 

Change at 2942.17 as follows:

 

Any (#1836)EAPOL-Key PDUs with an invalid MIC are dropped and ignoreddiscarded.

 

Change at 5683.52 as follows:

 

With p as the probability of droppingabandoning transmission of the frame, and pe as the probability of the frame not being transmitted successfully in a given frame exchange (i.e., either the Data frame or the Ack frame associated with it is in error), let Np be the number of retries required to maintain the probability of droppingabandoning transmission of the frame to be p.

The probability of any given packet being droppedabandoned in such a channel after Np retries is given by

pdropabandon = (pe)Np + 1

For example, in such a channel, if pe = 0.1 and pdropabandon = 10–8, then up to seven retries within the delay bound are required, and the scheduler should consider these retransmissions in the cumulative TXOP allocations.

The Surplus Bandwidth Allowance (SBA) parameter causes the requesting STA to be allocated a minimum amount of excess time by the scheduler so that the application droppedabandoned packet rates are bounded.

 

Thanks,

 

Mark

 

--

Mark RISON, Standards Architect, WLAN   English/Esperanto/Français

Samsung Cambridge Solution Centre       Tel: +44 1223  434600

Innovation Park, Cambridge CB4 0DS      Fax: +44 1223  434601

ROYAUME UNI                             WWW: http://www.samsung.com/uk

 


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