IEEE P802.11 Wireless LANs 802.11 TGad Proposed SB1 Resolutions for CID 6501, 6516 Date: 2012-03-01 Author(s): Name Company Address Phone email Mark 1765 West 121st Avenue Polycom mark.hamilton@polycom.com Hamilton Westminster, CO 80234 Abstract This document presents proposed resolutions to CIDs 6501 and 6516 on the 1st sponsor ballot of REVad. Comments 6501 4.9.3 50.13 The architectural model of Pull out the multiple MAC entities architectural concept sharing one PHY (one of multiple MAC example of MM-SME entities sharing one usage) seems to be a PHY, and put into its general enhancement to own subclause of 802.11 (well beyond 11ad), clause 4, ahead of for some specific usage 4.9.3. Specifically, scenarios (like desiring to create a diagram like have parallel associations Figure 4-16a (but with different security without the MM-SME), modes/levels). This is pull out the last really quite independent of sentence of the first FST or even MM-SME paragraph of 4.9.3, concepts. The and the paragraph at architectural change of lines 21-23 in 4.9.3, multiple MAC entities and make a new sharing a single PHY (and subclause with this the PHY-SAP changes to source material. Also, support this) should be modify the reference pulled out into its own to 4.9.3 in the NOTE subclause of clause 4, at p51.23 to reference introduced before the the new subclause, subclause that adds and modify the as an additional changes in 9.19.2.5 to feature for multiple MAC not be specific to entity scenarios. but rather to be general to a multiple MAC entities sharing one PHY architecture
IEEE P802.11 Wireless LANs 802.11 TGad Proposed SB1 Resolutions for CID 6501, 6516 Date: 2012-03-01 Author(s): Name Company Address Phone email Mark Hamilton Polycom 1765 West 121st Avenue Westminster, CO 80234 mark.hamilton@polycom.com Abstract This document presents proposed resolutions to CIDs 6501 and 6516 on the 1st sponsor ballot of REVad. Comments 6501 4.9.3 50.13 The architectural model of multiple MAC entities sharing one PHY (one example of MM-SME usage) seems to be a general enhancement to 802.11 (well beyond 11ad), for some specific usage scenarios (like desiring to have parallel associations with different security modes/levels). This is really quite independent of FST or even MM-SME concepts. The architectural change of multiple MAC entities sharing a single PHY (and the PHY-SAP changes to support this) should be pulled out into its own subclause of clause 4, introduced before the subclause that adds as an additional feature for multiple MAC entity scenarios. Pull out the architectural concept of multiple MAC entities sharing one PHY, and put into its own subclause of clause 4, ahead of 4.9.3. Specifically, create a diagram like Figure 4-16a (but without the MM-SME), pull out the last sentence of the first paragraph of 4.9.3, and the paragraph at lines 21-23 in 4.9.3, and make a new subclause with this source material. Also, modify the reference to 4.9.3 in the NOTE at p51.23 to reference the new subclause, and modify the changes in 9.19.2.5 to not be specific to but rather to be general to a multiple MAC entities sharing one PHY architecture
11-12-0242-00-00ad-proposed-resolution-to-sb1-cids-6501-6516.docx