Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi all, I am trying to resolve the issue raised in CIDs 11433 and 12806 – these CIDs identify that AP removal and AP addition should be considered as critical update events which increment BPCC along with setting the CUF field. Current draft spec
only sets the CUF for these events, treating these differently than other critical update events – this is not desirable since this can lead to STA missing these critical updates if it misses the Beacons where the CUF was set. CR doc
22/1838r1 captures relevant issues under Discussion for these CIDs. I have been discussing this offline with some of the members and we have aligned on text proposal in attached 22/1838r1. In summary, the proposed text adds a subclause 35.3.10.2 (Multi-link critical update events) which captures AP removal
and AP addition as ML critical update events in addition to events captured in 11.2.3.15 (TIM Broadcast). Text in relevant places have been revised to refer to this new subclause instead of 11.2.3.15 (TIM Broadcast) for BSS parameter critical update.
Please review and provide any feedback on this proposal. This is scheduled to be presented in tomorrow’s TGbe call. Thanks, Binita To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 |
Attachment:
11-22-1838-01-00be-LB266 CR for ML Reconfiguration clause 35.3.6 part 2.docx
Description: 11-22-1838-01-00be-LB266 CR for ML Reconfiguration clause 35.3.6 part 2.docx