General discovery comment resolution overview September 2008 doc.: IEEE 802.11-08/1173r0 February 2010 General discovery comment resolution overview Date: 2010-03-02 Authors: Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

Abstract Summary of the suggested resolution text (11-10/236r0) September 2008 doc.: IEEE 802.11-08/1173r0 February 2010 Abstract Summary of the suggested resolution text (11-10/236r0) Clean up the clause 11C.1 Mesh discovery. Amend the definition of BSS. Clarify what is Mesh Profile. Use START primitive to become a member of a mesh BSS. Use “become a member of a mesh BSS” consistently, instead of “join a mesh BSS”. Add the missing MIB variables. Add the missing PICS table entries. Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

Clean up the clause 11C.1 Mesh discovery September 2008 doc.: IEEE 802.11-08/1173r0 February 2010 Clean up the clause 11C.1 Mesh discovery Clause 11C.1 has been modified significantly Original 11C.1 does not provide appropriate procedures for discovery. The new subclause structure is as follows: 11C.1 Mesh discovery 11C.1.1 General 11C.1.2 Mesh identifier 11C.1.3 Mesh profile 11C.1.4 Supplemental information for mesh discovery 11C.1.5 Scanning mesh BSS 11C.1.6 Determination of the candidate peer mesh STA 11C.1.7 Establishing or becoming a member of a mesh BSS Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

Definition of BSS and mesh profile September 2008 doc.: IEEE 802.11-08/1173r0 February 2010 Definition of BSS and mesh profile Amend the definition of BSS as follows: 3.25 basic service set (BSS): A set of stations (STAs) that have successfully synchronized using the JOIN service primitives and one STA that has used the START primitive. Alternatively, a set of STAs that have used the START primitive specifying the same mesh profile as neighbor STA or a STA that has used the START primitive without having a neighbor STA that specifies the same mesh profile. Membership in a BSS does not imply that wireless communication with all other members of the BSS is possible. Add the definition of mesh profile as follows: 3.s13 mesh profile: A set of parameters that identifies the attribute of the mesh BSS and are commonly used in a single mesh BSS. The mesh profile consists of mesh ID, active path selection protocol, actie path selection metric, congestion control mode, synchronization protocol, and authentication protocol. Explicitly position “mesh profile” as the MBSS attribute identifiers. Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

September 2008 doc.: IEEE 802.11-08/1173r0 February 2010 Use START primitive Traditionally, STA uses START primitive to start (establish) a new BSS, and use JOIN primitive to join the existing BSS. START primitive kicks beaconing. JOIN primitive kicks sync assuming a single TSF value is shared in a BSS.  This is not applicable for mesh STAs. Mesh STAs use START primitive regardless of the establishment or becoming a member of a BSS. Aligned with 11-10/135r1 (START primitive proposal) Use START to establish a mesh BSS (the same procedure as legacy BSS) Use START to become a member of a mesh BSS (start beaconing) Use “become a member of a mesh BSS” consistently, instead of “join a mesh BSS”, as join implies starting synchronization. Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

MIB and PICS updates February 2010 September 2008 doc.: IEEE 802.11-08/1173r0 February 2010 MIB and PICS updates Many MIB variables are missing to control the discovery related parameters. dot11MeshNumberOfPeerings dot11MeshAcceptingAdditionalPeerings dot11MeshConnectedToPortal dot11MeshActiveAuthenticationProtocol dot11MeshActivePathSelectionMetric dot11MeshActiveCongestionControlMode dot11MeshActiveSynchronizationProtocol Further, specify how these MIB variables to be used. Add the missing PICS table entries regarding: Discovery related information Mesh peering management Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

September 2008 doc.: IEEE 802.11-08/1173r0 February 2010 Summary All G-discovery category comments are examined and resolution text is available to close most of the comments 11-10/236 provides the resolution text 11-10/237 provides the resolution notes to each comments The remaining comment (CID2389) requires discussion with security experts Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

Comments? Questions? February 2010 September 2008 doc.: IEEE 802.11-08/1173r0 February 2010 Comments? Questions? Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola