> Suggested approach to handle non-transmitting BSS entries is simplified in the > following sense. If new entries have been already created after channel switch, > only transmitting bss will be updated using IEs of new entry for the same > transmitting bss. Non-transmitting bss entries will be updated as soon as > new mgmt frames are received. Updating non-transmitting bss entries seems > too expensive: nested nontrans_list traversing is needed since we can not > rely on the same order of old and new non-transmitting entries. That sounds like a reasonable trade-off. I do wonder though what happens if we're connected to a non-transmitting BSS? johannes
