CID#89-Directed Multicast Service (DMS) Month Year Month Year doc.: IEEE 802.11-yy/xxxxr0 doc.: IEEE 802.11-yy/xxxxr0 January 2008 CID#89-Directed Multicast Service (DMS) Authors: Date: 2008-1-2 Slide 1 Emily Qi (Intel Corp) et al Page 1 Emily Qi John Doe, Some Company

Month Year Month Year doc.: IEEE 802.11-yy/xxxxr0 doc.: IEEE 802.11-yy/xxxxr0 January 2008 Abstract The proposal provides a directed multicast service to allow AP to transmit group addressed frames as individually addressed frames. The original comment (LB108 CID #89) is to use FBMS frames to facilitate directed multicast delivery. A separate submission was suggested while reviewing CID #89 in the TGv teleconference. Slide 2 Emily Qi (Intel Corp) et al Page 2 Emily Qi John Doe, Some Company

Agenda Problem Statement Proposed Solution and Benefits Month Year doc.: IEEE 802.11-yy/xxxxr0 January 2008 Agenda Problem Statement Proposed Solution and Benefits Proposed Changes Slide 3 Emily Qi (Intel Corp) et al Emily Qi

January 2008 Problem Statement Issue: clients may be compliant with different protection methods, e.g. Open Authentication, WEP, TKIP or AES-CCMP Today’s solution: a single protection method (the lowest common method supported by all devices) for Broadcast/multicast traffic delivery within the BSS. Issue with Today’s solution: some clients may require AES security while other might only use open authentication in hot spot, citywide, and home environment, For example, in hot spot or citywide deployment, most service announcement traffic is transmitted via broadcast, rouge AP can forge these information, generating DOS. Slide 4 Emily Qi (Intel Corp) et al

Solution and Benefits Solution: Benefits: January 2008 Solution and Benefits Solution: Directed Multicast: Transmit multicast as unicast per client’s request Benefits: Enable different security methods for different clients for home, hotspot, and citywide Provide authenticity and integrity protection if lowest common method is open auth. Enable reliable service Unicast is more reliable than multicast Enable aggressive client power scheme Client doesn’t need to wake up at DTIM or any FBMS intervals to receive multicast frames Slide 5 Emily Qi (Intel Corp) et al

Proposed Solution: Directed Multicast January 2008 Proposed Solution: Directed Multicast STA advertise its Directed Multicast Capability Non-AP STA sends a request to specify traffic class for the directed multicast traffic delivery AP may accept or reject the traffic class specified by the non-AP STA If the service is accepted by the AP, AP shall transmit the requested group addressed (broadcast/multicast) traffic as the individual addressed (unicast) traffic to the requesting STA, and AP still transmits the group addressed traffic for other STAs in the BSS as normal Other STAs will process group addressed traffic as normal The requesting STA shall filter out the duplicated group addressed traffic to avoid traffic duplication Slide 6 Emily Qi (Intel Corp) et al

Proposed Changes Define a Capability bit “Directed Multicast” January 2008 Proposed Changes Define a Capability bit “Directed Multicast” Option 1: Use FBMS Request and Response frames Define a new field Directed Multicast. The Directed Multicast field set to 1 for “Enabled” , set to 0 for “Disabled”. No new frames, but will define new procedure. Change is small Option 2: Define new Action frames, Directed Multicast Service (DMS) request and response New frames and will define procedure Change is cleaner Slide 7 Emily Qi (Intel Corp) et al

Option 2: DMS Request and Response frames Month Year doc.: IEEE 802.11-yy/xxxxr0 January 2008 Option 2: DMS Request and Response frames DMS Request frame: Category Action Dialog Token Request Type (“Add” or “Remove”) DMS Descriptor List Octets: 1 variable DMS ID Length (optional) TCLAS Elements (optional) TCLAS Processing Element (optional) Octets: 1 variable 3 DMS Descriptor DMS Response frame: Category Action Dialog Token DMS Status List Octets: 1 DMS Status DMS ID DMS Status Octets: 1 Emily Qi (Intel Corp) et al Slide 8 Emily Qi

Thank You! & Questions? January 2008 Month Year doc.: IEEE 802.11-yy/xxxxr0 January 2008 Thank You! & Questions? Slide 9 Emily Qi (Intel Corp) et al Emily Qi