Lightweight Mesh Point – A confusing term

Slides:



Advertisements
Similar presentations
Beacon Measurement on Pilot Frames
Advertisements

LB84 General AdHoc Group Sept. Closing TGn Motions
[ Interim Meetings 2006] Date: Authors: July 2005
TGn Sync Atlanta Presentation on Confirmation
IEEE White Space Radio Contribution Title
TGu/TGv Joint Session Date: Authors: July 2005 July 2005
Lightweight Mesh Point – A confusing term
London TGu Motions Authors: January 2007 Date: Month Year
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Waveform Generator Source Code
Power Save Mechanism for Unsync MPs
TGp Closing Report Date: Authors: July 2005 Month Year
TGp Closing Report Date: Authors: July 2007 Month Year
Attendance and Documentation for the March 2007 Plenary
3GPP Extended Date: Authors: July 2005 July 2005
[ Policies and Procedure Summary]
[ Policies and Procedure Summary]
3GPP liaison report May 2006 May 2006 Date: Authors:
Motion to accept Draft p 2.0
3GPP liaison report July 2006
[place presentation subject title text here]
Descriptive Language Usage in TGv
Motions Date: Authors: January 2006
TGp Motions Date: Authors: November 2005 Month Year
TGp Closing Report Date: Authors: March 2006 Month Year
On Coexistence Mechanisms
TGu-changes-from-d0-02-to-d0-03
TGp Closing Report Date: Authors: May 2007 Month Year
Call for OLSR Participation
On Coexistence Mechanisms
TGp Closing Report Date: Authors: March 2006 Month Year
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGv Redline D0.06 Insert and Deletion
ADS Study Group Mid-week Report
Selection Procedure Recommendation
TGu-changes-from-d0-01-to-d0-02
LB73 Noise and Location Categories
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D0.10 Insert and Deletion
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
TGp Closing Report Date: Authors: March 2007 Month Year
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
May 2005 CAPWAP AHC Closing Report
TGu Motions Date: Authors: May 2006 May 2006
Liaison Report From Date: Authors: Month Year
Beamforming and Link Adaptation Motions
Lightweight Mesh Point – A confusing term
Draft P802.11s D1.03 WordConversion
Motion to go to Letter Ballot
EC Motions – July 2005 Plenary
TGu-changes-from-d0-04-to-d0-05
Method for geting Link RCPI
Lightweight Mesh Point – A confusing term
Transition Nowhere Date: Authors: Sept 2005 Sept 2005
Use of More Data Field Date: Authors: Nov 2005 Month Year
TGu-changes-from-d0-03-to-d0-04
TGu Motions Date: Authors: May 2006 May 2006
WNG SC Closing Report Date: Authors: November 2005
MAC Address Spoofing in Mesh
Lightweight Mesh Point – A confusing term
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Use of KCK for TGr Management Frame Protection
Use of KCK for TGr Management Frame Protection
TGr Proposed Draft Revision Notice
WNG SC Closing Report Date: Authors: July 2006 July 2006
TGp Motions Date: Authors: January 2006 Month Year
Presentation transcript:

Lightweight Mesh Point – A confusing term July 2006 doc.: IEEE 802.11-06/1036r5 July 2006 Lightweight Mesh Point – A confusing term Date: 2006-07-20 Authors: Notice: This document has been prepared to assist IEEE 802.11. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.11. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair <stuart.kerry@philips.com> as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at <patcom@ieee.org>. Guido R. Hiertz, Philips et al. Guido R. Hiertz, Philips et al.

July 2006 doc.: IEEE 802.11-06/1036r5 July 2006 Abstract The term “Lightweight Mesh Point” is defined in draft 0.02 of IEEE 802.11s. It describes an entity that neither forwards traffic nor participates in the formation of the Mesh WLAN. In the recent months, the term has been confusing to people that are not familiar with the concept. This presentation describes the differences between an 802.11 STA, an 802.11s MP and an 802.11s LW-MP. The presentation concludes with the request to clarify the functionality of the entity “Lightweight Mesh Point.” Guido R. Hiertz, Philips et al. Guido R. Hiertz, Philips et al.

What is the idea of a Lightweight Mesh Point (LW-MP)? July 2006 doc.: IEEE 802.11-06/1036r5 July 2006 What is the idea of a Lightweight Mesh Point (LW-MP)? Without “LW-MP” capability no communication even if in range “LW-MP” capability enables communication to any device in range Convenient for customers Meet expectations No forwarding capabilities at LW-MP needed Traditional WLAN All traffic relayed via AP Both, laptop and printer must be in range of AP Otherwise no communication   Guido R. Hiertz, Philips et al. Guido R. Hiertz, Philips et al.

How is a Lightweight Mesh Point (LW-MP) defined? July 2006 doc.: IEEE 802.11-06/1036r5 July 2006 How is a Lightweight Mesh Point (LW-MP) defined? 5.4.7.2.1 Lightweight mesh point operation These are the minimal functionality mesh points. They do not use or provide distribution system (DS) and congestion control services, [...] Thus, they are able to communicate only with their neighbors [...] This indicates to neighbors that these MPs are unable to provide DS services. The choice of not using the DS service does not require any modification to mesh services specification. 5.4.7.2.2 Support for Power Saving Devices in a WLAN Mesh [...] Lightweight MPs communicate with neighbors without association. [...] 11A.13 Power Management in a Mesh (Optional) [...] 11A.13.1 Basic approach [...] Alternatively, a lightweight MP may associate with a MAP as a simple STA if it intends to enter PS mode. 11A.12.2.1 Beaconing by unsynchronizing MPs [...] Unsynchronizing MAPs shall treat any [...] neighboring LW-MPs operating in PS mode identical to STA [...] 11A.12.2.2 Beaconing by synchronizing MPs [...] A LW-MP [...] may opt not to beacon [...] Guido R. Hiertz, Philips et al. Guido R. Hiertz, Philips et al.

What is a 802.11 Station (STA)? Source or Destination of traffic July 2006 doc.: IEEE 802.11-06/1036r5 July 2006 What is a 802.11 Station (STA)? Source or Destination of traffic Never forwards traffic Never uses 4-address scheme Never uses “112” as “To/From DS” bits Does not send beacon frames in infrastructure mode Sends beacon frames in IBSS mode Does not provide association service Does not authenticate other devices Guido R. Hiertz, Philips et al. Guido R. Hiertz, Philips et al.

What is a 802.11s Mesh Point (MP)? July 2006 doc.: IEEE 802.11-06/1036r5 July 2006 What is a 802.11s Mesh Point (MP)? Forwards traffic Uses 4-address scheme Uses all combinations of “To/From DS” bits MP can be co-located with STA (Then also) MP can be Source or Destination of traffic Sends beacon frames May provide association service when MP and AP co-located Works as 802.11i authenticator for joining MPs Guido R. Hiertz, Philips et al. Guido R. Hiertz, Philips et al.

What is a 802.11s Lightweight Mesh Point (LW-MP)? July 2006 doc.: IEEE 802.11-06/1036r5 July 2006 What is a 802.11s Lightweight Mesh Point (LW-MP)? Source or Destination of traffic Never forwards traffic Never uses 4-address scheme Uses “112” as “To/From DS” bits May choose not to send beacon frames Guido R. Hiertz, Philips et al. Guido R. Hiertz, Philips et al.

LW-MPs do not forward but are MPs? July 2006 doc.: IEEE 802.11-06/1036r5 July 2006 LW-MPs do not forward but are MPs? In its current form, the entity termed as “Lightweight Mesh Point (LW-MP)” is not clearly differentiated from normal “Mesh Point (MP)” capability No Path Selection & Frame Forwarding No Participation in WLAN Mesh formation No Route set-up, maintenance & discovery Thus, the term LW-MP is confusing  Different WLAN Mesh related entities such as MP and LW-MP should be more clearly differentiated with respect to functionality Guido R. Hiertz, Philips et al. Guido R. Hiertz, Philips et al.

July 2006 doc.: IEEE 802.11-06/1036r5 July 2006 Motion Move to instruct the IEEE 802.11s editor to adopt the changes to P802.11s/D0.02 provided in submission “11-06-1103-02-000s-clarification-ieee-802-11s-entity-classes.doc”. Moved by: Second by: Result (Yes/No/Abstain): Guido R. Hiertz, Philips et al. Guido R. Hiertz, Philips et al.

References IEEE 802.11s Draft 0.02 IEEE 802.11 Standard July 2006 doc.: IEEE 802.11-06/1036r5 July 2006 References IEEE 802.11s Draft 0.02 IEEE 802.11 Standard D. Engwer, “"WDS" Clarifications,” IEEE, Submission 802.11-05/0710r0, July 2005 Guido R. Hiertz, Philips et al. Guido R. Hiertz, Philips et al.