three categories of IEEE Std 802.11 service—the station service (SS), the PCP service (PCPS), and the distribution system service (DSS). These categories of service are used by the IEEE Std 802.11 MAC sublayer. Proposed Resolution: REVISED. Make changes as in 11-16/290r2, for CID 7807. These changes effect the commenter’s intent, with additional editorial clean up. CID 7317: 7317 RISON, 1554.34 11.1.2.1 "A STA contained in the AP or Change to "A STA contained in Mark PCP shall initialize its TSF timer the AP or PCP shall initialize its independently of any TSF timer independently of any simultaneously started APs or simultaneously started APs or PCPs" -- this cannot in general be PCPs it is aware of", or delete acheved, unless the APs/PCPs are coordinated. Needs to be restricted to managed ("enterprise/corporate") contexts, but this is arguably out of scope of the standard anyway Discussion: Context: in concept. But, there is no reason to restrict this to synchronizing with other APs or PCPs “shall” that were initialized at the same time. What we really are trying to achieve is no implementation-caused synchronization of TSFs across the infrastructure BSS (or PBSS) regardless of startup methods or timing. Proposed Resolution: REVISED. Change the sentence, as shown: A STA contained in the AP or PCP shall independently initialize its TSF timer independently of any simultaneously started APs or PCPs, respectively in an effort to minimize the synchronization of the TSF timers of multiple APs or PCPs. CID 7324:
three categories of IEEE Std 802.11 service—the station service (SS), the PCP service (PCPS), and the distribution system service (DSS). These categories of service are used by the IEEE Std 802.11 MAC sublayer. Proposed Resolution: REVISED. Make changes as in 11-16/290r2, for CID 7807. These changes effect the commenter’s intent, with additional editorial clean up. CID 7317: 7317 RISON, Mark 1554.34 11.1.2.1 "A STA contained in the AP or PCP shall initialize its TSF timer independently of any simultaneously started APs or PCPs" -- this cannot in general be acheved, unless the APs/PCPs are coordinated. Needs to be restricted to managed ("enterprise/corporate") contexts, but this is arguably out of scope of the standard anyway Change to "A STA contained in the AP or PCP shall initialize its TSF timer independently of any simultaneously started APs or PCPs it is aware of", or delete Discussion: Context: in concept. But, there is no reason to restrict this “shall” to synchronizing with other APs or PCPs that were initialized at the same time. What we really are trying to achieve is no implementation-caused synchronization of TSFs across the infrastructure BSS (or PBSS) regardless of startup methods or timing. Proposed Resolution: REVISED. Change the sentence, as shown: A STA contained in the AP or PCP shall independently initialize its TSF timer independently of any simultaneously started APs or PCPs, respectively in an effort to minimize the synchronization of the TSF timers of multiple APs or PCPs. CID 7324: