Some open questions Date: 2010-01-21 Authors: January 2010 September 2008 doc.: IEEE 802.11-08/1173r0 January 2010 Some open questions Date: 2010-01-21 Authors: Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

Abstract Some open questions to task group members for clarification September 2008 doc.: IEEE 802.11-08/1173r0 January 2010 Abstract Some open questions to task group members for clarification “Portal” in the base standard and in the TGs draft spec SSID element Join MBSS? Start MBSS? Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

“Portal” in the base standard and in the TGs draft spec September 2008 doc.: IEEE 802.11-08/1173r0 January 2010 “Portal” in the base standard and in the TGs draft spec What is written in the base standard: 3.110 portal: The logical point at which the integration service is provided. 3.72 integration service: The service that enables delivery of medium access control (MAC) service data units (MSDUs) between the distribution system (DS) and a non-IEEE-802.11 local area network (LAN) (via a portal). “Portal” is an interface between DS and non-IEEE-802.11 LAN. 3.40 distribution system (DS): A system used to interconnect a set of basic service sets (BSSs) and integrated local area networks (LANs) to create an extended service set (ESS). Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

“Portal” in the base standard and in theTGs draft spec September 2008 doc.: IEEE 802.11-08/1173r0 January 2010 “Portal” in the base standard and in theTGs draft spec What is implied in TGs draft spec: Portal is an interface between MBSS and external network. The external network may be DS (may not be non-802.11 network) This contradicts with portal definition in the base standard. Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

“Portal” in the base standard and in the TGs draft spec September 2008 doc.: IEEE 802.11-08/1173r0 January 2010 “Portal” in the base standard and in the TGs draft spec How can we solve this problem? We need to reconsider the usage of “portal” in TGs draft spec. We need to come up with a reader friendly self explaining alternative, which does not conflict with existing 802 standard family. Some candidates: “mesh portal” “mesh gate” “MBSS bidge” Anything else? Strawpoll: Which name do you prefer for this alternative. Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

SSID element Strawpoll: January 2010 CID2456: CID2338: CID2219: September 2008 doc.: IEEE 802.11-08/1173r0 January 2010 SSID element CID2456: Use of the wildcard SSID may be confusing to legacy devices. Use a fixed string for the SSID. CID2338: The SSID is absolutely unnecessary for Mesh WLANs. CID2219: Doesn't the wildcard SSID mean, that a STA with any SSID can join? How we should handle SSID element in Beacon or Probe Response frame? Use “IEEE802.11s MESH” or something similar for the SSID ? Delete SSID element from these frames ? Use wildcard SSID ? (as in D4.0) Strawpoll: Which option should be taken? Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

Join MBSS? Start MBSS? CID2779: Which terminology we should use? September 2008 doc.: IEEE 802.11-08/1173r0 January 2010 Join MBSS? Start MBSS? CID2779: "When a mesh STA starts an MBSS" sounds a lot like "When a mesh STA joins an MBSS", except I don't understand what "starting" means. Which terminology we should use? In case a mesh STA tries to establish a new mesh BSS (i.e., there is no preferred neighbor mesh STAs operating) In case a mesh STA tries to be a member of existing neighbor mesh STAs. Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola

Join MBSS? Start MBSS? From the base standard: September 2008 doc.: IEEE 802.11-08/1173r0 January 2010 Join MBSS? Start MBSS? From the base standard: MLME-JOIN.request : requests synchronization with a BSS. START.request : requests that the MAC entity start a new BSS. TGs D4.01 (clause 10 MLME primitive): START.request : requests that the MAC entity to start a new BSS or, start mesh beaconing, or join an MBSS. (will be amended by 11-10/135) Strawpoll: Which terminology shall we use? Kazuyuki Sakoda, Sony Corporation Tony Braskich, Motorola