Presentation is loading. Please wait.

Presentation is loading. Please wait.

Doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Avoiding Interactions with Lazy-WDS Equipment Date: 2008-03-15.

Published byEaster Martin Modified over 9 years ago

Similar presentations

Presentation on theme: "Doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Avoiding Interactions with Lazy-WDS Equipment Date: 2008-03-15."— Presentation transcript:

1 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Avoiding Interactions with Lazy-WDS Equipment Date: 2008-03-15

2 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 2 Abstract Mesh multicast traffic will trigger unwanted responses on Access Points that implement Lazy- WDS. A frame format change is proposed that will avoid these interactions and make a more efficient use of the 802.11 header address fields.

3 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 3 Background The origin of this problem is summarized in IEEE Std 802.11TM-2007: 3.170 wireless distribution system (WDS): (...) This standard describes such a frame format, but does not describe how such a mechanism or frame format would be used. The Wi-Fi Alliance is also silent about the use of the WDS frame format.

4 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 4 Background So vendors had to get creative. There are two ways APs use WDS frames: Static WDS configuration –Network managers manually enter a list of WDS-peers Dynamic WDS configuration (most commonly known as Lazy-WDS)‏ –Access Points automatically "discover" WDS peers.

5 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 5 What triggers automatic peer discovery? We've empirically established that some Lazy-WDS Access Points will assign WDS-peer status to any STA that transmits a multicast WDS frame (i.e if bit8, 1st octet of the Receiver Address is set). Ah, and this is regardless of the value of the protected bit in the frame control header.

6 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 6 The birth of a WDS-peer link

7 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 7 How does that affect 802.11s? Resolution 11-07/799r6 established that mesh will use WDS frame format. This means that each MP that forwards a broadcast/multicast frame in the vicinity of a Lazy-WDS AP will be treated as a WDS-peer. There is a large deployed population of Lazy-WDS Access Points... being in the vicinity of one is not hard.

8 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 8 So? Mesh Points in range of Lazy-WDS APs will cause two serious problems: spurious traffic and DDoS attack on the AP.

9 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 9 Spurious Traffic Lazy-APs will retransmit all multicast traffic in the BSS to each and every MP in range. The AP does not consider the Mesh Sequence number to limit broadcast flooding. N MPs in range -> Each multicast frame is retransmitted N times by the AP.

10 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 10 Spurious Traffic

11 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 11 Spurious Traffic

12 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 12 Distributed Denial of Service Attack Apparently Lazy-WDS APs were designed to support only a small number of WDS peer links. A large number of MPs near a Lazy-WDS AP will carry out a DDoS attack on the Access Point. Service to the BSS will be disrupted.

13 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 13 Distributed Denial of Service Attack

14 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 14 Because of these problems we propose...

15 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 15 Broadcast and Multicast Packet Transmission According to Draft 1.09 Broadcast mesh packets are transmitted using 4 address frame formats with Address 1 as either unicast or broadcast/multicast. If Address 1 is unicast there is no issue. However if Address 1 is broadcast then…

16 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 16 Broadcast and Multicast Packet Transmission According to Draft 1.09 11A.5.5.3.1 At Source MPs For non Proxied entries Address 1 = Broadcast or Multicast Address 2 = Source MP MAC address Address 3 = Broadcast or Multicast Address 4 = Source MP MAC Address From Proxied entities Address 1 = Broadcast or Multicast Address 2 = Source MP MAC address Address 3 = Broadcast or Multicast Address 4 = Source MP MAC Address AE: Add 5 = Broadcast or Multicast AE:Addr 6 = Address of Proxied entity 11A.5.5.3.2 At Intermediate and destination MPs For non Proxied entries Address 1 = Broadcast or Multicast Address 2 = Intermediate MP MAC address Address 3 = Broadcast or Multicast Address 4 = Source MP MAC Address From Proxied entities Address 1 = Broadcast or Multicast Address 2 = Intermediate MP MAC address Address 3 = Broadcast or Multicast Address 4 = Source MP MAC Address AE:Addr 5 = Broadcast or Multicast AE:Addr 6 = Address of Proxied entity Observations A lot of redundant fields Broadcast/multicast address repeated 2 times in non-proxied case Broadcast/multicast address repeated 3 times in proxied case

17 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 17 Broadcast and Multicast Packet Transmission According to Draft 1.09 MPs MP1 MP2 MP3 Address 1 = Broadcast or Multicast Address 2 = MPs MAC Addr Address 3 = Broadcast or Multicast Address 4 = MPs MAC Address SQ1 Address 1 = Broadcast or Multicast Address 2 = MPs MAC Addr Address 3 = Broadcast or Multicast Address 4 = MPs MAC Address SQ1 Address 1 = Broadcast or Multicast Address 2 = MP1 MAC Addr Address 3 = Broadcast or Multicast Address 4 = MPs MAC Address SQ1 Address 1 = Broadcast or Multicast Address 2 = MP2 MAC Addr Address 3 = Broadcast or Multicast Address 4 = MPs MAC Address SQ1 Determines duplicate Packet based on

18 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 18 Broadcast and Multicast Packet Transmission According to Draft 1.09 MPs1 MPi1 MPi2 MP3 Address 1 = Broadcast or Multicast Address 2 = MPs1 MAC Addr Address 3 = Broadcast or Multicast Address 4 = MPs1 MAC Address AE:Addr 5 =Broadcast or Multicast AE:Addr 6= S SQ1 Address 1 = Broadcast or Multicast Address 2 = MPi1 MAC Addr Address 3 = Broadcast or Multicast Address 4 = MPs1 MAC Address AE:Addr 5 =Broadcast or Multicast AE:Addr 6 = S SQ1 Address 1 = Broadcast or Multicast Address 2 = MPi2 MAC Addr Address 3 = Broadcast or Multicast Address 4 = MPs2 MAC Address AE:Addr 5 =Broadcast or Multicast AE:Addr 6 = S SQ1 S

19 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 19 Broadcast and Multicast Packet Transmission Proposed Solution 11A.5.5.3.1 At Source MPs For non Proxied entries Address 1 = Broadcast or Multicast Address 2 = Source MP MAC address Address 3 = Source MP MAC Address From Proxied entities Address 1 = Broadcast or Multicast Address 2 = Source MP MAC address Address 3 = Source MP MAC address AE:Addr 4 = Address of Proxied entity 11A.5.5.3.2 At Intermediate MPs For non Proxied entries Address 1 = Broadcast or Multicast Address 2 = Intermediate MP MAC address Address 3 = Source MP MAC Address From Proxied entities Address 1 = Broadcast or Multicast Address 2 = Intermediate MP MAC address Address 3 = Source MP MAC Address AE:Add 4 = Address of Proxied entity Use 3 address formats for all non-proxied broadcast/multicast data frames Use AE=01 to carry proxied entity in proxied broadcast/multicast frame Addr1, Addr2, Addr3 are TA, RA and SA respectively From DS = 1, To DS = 0 Addr4 is proxied entity when AE=01

20 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 20 Broadcast and Multicast Packet Transmission Proposed Solution MPs MP1 MP2 MP3 Address 1 = Broadcast or Multicast Address 2 = MPs MAC Addr Address 3 = MPs MAC Address SQ1 Address 1 = Broadcast or Multicast Address 2 = MPs MAC Addr Address 3 = MPs MAC Address SQ1 Address 1 = Broadcast or Multicast Address 2 = MP1 MAC Addr Address 3 = MPs MAC Address SQ1 Address 1 = Broadcast or Multicast Address 2 = MP2 MAC Addr Address 3 = MPs MAC Address SQ1 Determines duplicate Packet based on

21 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 21 Broadcast and Multicast Packet Transmission Proposed Solution MPs1 MPi1 MPi2 MP3 Addr4 is proxied entity when AE=01 Address 1 = Broadcast or Multicast Address 2 = MPs1 MAC Addr Address 3 = MPs1 MAC Addr AE:Addr 4 = S SQ1 Addr4 is proxied entity when AE=01 Address 1 = Broadcast or Multicast Address 2 = MPi1 MAC Addr Address 3 = MPs1 MAC Address AE:Addr 4 = S SQ1 Addr4 is proxied entity when AE=01 Address 1 = Broadcast or Multicast Address 2 = MPi2 MAC Addr Address 3 = MPs2 MAC Address AE:Addr 4 = S SQ1 Use to determine duplicate packets. MPs2 S

22 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 22 Changes Required 1.Modify 11.A.5.5.3.1 and 11.A.5.5.3.2 to describe transmission of 3 address broadcast and multicast data frames 2.Modify Table s2 to allow AE=01 for broadcast/multicast data frames as well

23 doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Slide 23 Straw Poll Would you support the proposed modifications to mesh broadcast frames as presented in this submission? 1) Yes2) No 3) DK/DC

Download ppt "Doc.: IEEE 802.11-08/0278r5 Submission March 2008 Javier Cardona et al. Avoiding Interactions with Lazy-WDS Equipment Date: 2008-03-15."

Similar presentations

Short MAC Header Date: Authors: John Doe, Some Company

Short MAC Header Date: Authors: John Doe, Some Company
Submission doc.: IEEE 802.11-12/1357r3 Nov. 2012 Slide 1 Dynamic TIM and Page Segmentation Date: 2012-11-08 Authors: Weiping Sun, Seoul National University.

Submission doc.: IEEE /1357r3 Nov Slide 1 Dynamic TIM and Page Segmentation Date: Authors: Weiping Sun, Seoul National University.
Doc.: IEEE 802.11-11/0065r2 Submission January 2011 Ivan Pustogarov, IITP RASSlide 1 GCR for mesh Date: January 2011 Authors:

Doc.: IEEE /0065r2 Submission January 2011 Ivan Pustogarov, IITP RASSlide 1 GCR for mesh Date: January 2011 Authors:
Submission doc.: IEEE 802.11-14/1015r1 September 2015 Guido R. Hiertz et al., EricssonSlide 1 Proxy ARP in 802.11ax Date: 2015-08-25 Authors:

Submission doc.: IEEE /1015r1 September 2015 Guido R. Hiertz et al., EricssonSlide 1 Proxy ARP in ax Date: Authors:
Doc.: IEEE 802.11-08/1468r0 Submission Dec 2008 Ashish Shukla, Marvell SemiconductorSlide 1 ERP Protection in IEEE 802.11s Mesh Network Date: 2008-12-12.

Doc.: IEEE /1468r0 Submission Dec 2008 Ashish Shukla, Marvell SemiconductorSlide 1 ERP Protection in IEEE s Mesh Network Date:
Submission doc.: IEEE 11-13/0406-03-00ak May 2013 Norman Finn, Cisco SystemsSlide 1 P802.1Qbz + P802.11ak Proposed Division of Work Date: 2013-05-09 Authors:

Submission doc.: IEEE 11-13/ ak May 2013 Norman Finn, Cisco SystemsSlide 1 P802.1Qbz + P802.11ak Proposed Division of Work Date: Authors:
Submission doc.: IEEE 11-12/0246r2 NameAffiliationsAddressPhoneemail Jing-Rong HsiehHTC Corp. 1F, 6-3 Baoqiang Road, Xindian district, New Taipei City,

Submission doc.: IEEE 11-12/0246r2 NameAffiliationsAddressPhone Jing-Rong HsiehHTC Corp. 1F, 6-3 Baoqiang Road, Xindian district, New Taipei City,
Doc.: 11-04-0500-00-0mes Submission 7 May 2004 Tricci SoSlide 1 Need Clarification on The Definition of ESS Mesh Prepared by Tricci So.

Doc.: mes Submission 7 May 2004 Tricci SoSlide 1 Need Clarification on The Definition of ESS Mesh Prepared by Tricci So.
Doc.: IEEE 802.11-08/0103r0 Submission January 2008 Jarkko Kneckt, NokiaSlide 1 Peer Service Period Date: 2008-1-14 Authors:

Doc.: IEEE /0103r0 Submission January 2008 Jarkko Kneckt, NokiaSlide 1 Peer Service Period Date: Authors:
Doc.: IEEE 11-04/0319r0 Submission March 2004 W. Steven Conner, Intel Corporation Slide 1 Architectural Considerations and Requirements for 802.11 ESS.

Doc.: IEEE 11-04/0319r0 Submission March 2004 W. Steven Conner, Intel Corporation Slide 1 Architectural Considerations and Requirements for ESS.
Submission doc.: IEEE 11-12/0553r4 May 2012 Jarkko Kneckt, NokiaSlide 1 Response Criteria of Probe Request Date: 2012-05-15 Authors:

Submission doc.: IEEE 11-12/0553r4 May 2012 Jarkko Kneckt, NokiaSlide 1 Response Criteria of Probe Request Date: Authors:
Submission doc.: IEEE 11-13/0406-04-00ak May 2013 Finn and Hart, Cisco SystemsSlide 1 P802.1Qbz + P802.11ak Proposed Division of Work Date: 2013-05-09.

Submission doc.: IEEE 11-13/ ak May 2013 Finn and Hart, Cisco SystemsSlide 1 P802.1Qbz + P802.11ak Proposed Division of Work Date:
Doc.: IEEE 802.11-08/1378r0 Submission November 2008 Darwin Engwer, Nortel NetworksSlide 1 Improving Multicast Reliability Date: 2008-11-11 Authors:

Doc.: IEEE /1378r0 Submission November 2008 Darwin Engwer, Nortel NetworksSlide 1 Improving Multicast Reliability Date: Authors:
Submission doc.: IEEE 11-13/0693-00ak-r1 July 2013 Norman Finn, Cisco SystemsSlide 1 Comparison of Receiver Subset Techniques Date: 2013-07-14 Authors:

Submission doc.: IEEE 11-13/ ak-r1 July 2013 Norman Finn, Cisco SystemsSlide 1 Comparison of Receiver Subset Techniques Date: Authors:
Doc.: IEEE 802.11-08/0357r0 Submission March 2008 Michelle Gong, Intel, et alSlide 1 Enhancement to Mesh Discovery Date: 2008-03-17 Authors:

Doc.: IEEE /0357r0 Submission March 2008 Michelle Gong, Intel, et alSlide 1 Enhancement to Mesh Discovery Date: Authors:
Doc.: IEEE 802.11-12/0263r1 SubmissionJae Seung Lee, ETRI Spec Framework Proposal: Selection of the AP for Scanning Date: 2012-03-02 Slide 1 March 2012.

Doc.: IEEE /0263r1 SubmissionJae Seung Lee, ETRI Spec Framework Proposal: Selection of the AP for Scanning Date: Slide 1 March 2012.
Doc.: IEEE 802.11-05/0174r1 Submission Hang Liu, et al. March 2005 Slide 1 A Routing Protocol for WLAN Mesh Hang Liu, Jun Li, Saurabh Mathur {hang.liu,

Doc.: IEEE /0174r1 Submission Hang Liu, et al. March 2005 Slide 1 A Routing Protocol for WLAN Mesh Hang Liu, Jun Li, Saurabh Mathur {hang.liu,
Doc.: IEEE 802.11-08/1468r1 Submission Jan 09 Ashish Shukla, Marvell SemiconductorSlide 1 ERP Protection in IEEE 802.11s Mesh Network Date: 2009-01-14.

Doc.: IEEE /1468r1 Submission Jan 09 Ashish Shukla, Marvell SemiconductorSlide 1 ERP Protection in IEEE s Mesh Network Date:
Doc.: IEEE 802.11-07/2901r05 Submission November 2007 Doug Kavner, RaytheonSlide 1 Use of BSSID in WAVE Date: 2007-11-15 Authors:

Doc.: IEEE /2901r05 Submission November 2007 Doug Kavner, RaytheonSlide 1 Use of BSSID in WAVE Date: Authors:
Submission doc.: IEEE 11-15/1060r0 September 2015 Eric Wong (Apple)Slide 1 Receive Operating Mode Indication for Power Save Date: 2015-09-14 Authors:

Submission doc.: IEEE 11-15/1060r0 September 2015 Eric Wong (Apple)Slide 1 Receive Operating Mode Indication for Power Save Date: Authors:

Similar presentations

Ads by Google