TGax MU Ad-hoc Agenda September 2016 December 2015 doc.: IEEE 802.11-11/1588r0 September 2016 TGax MU Ad-hoc Agenda September 2016 Date: 2016-09-13 TGax MU ad-hoc group Dorothy Stanley, Aruba Networks

IEEE 802.11 TGax High Efficiency WLAN MU Ad Hoc September 2016 IEEE 802.11 TGax High Efficiency WLAN MU Ad Hoc Co-Chairs: Kaushik Josiam (Samsung) Sigurd Schelstraete (Quantenna) Kiseon Ryu (LG Electronics) TGax MU ad-hoc group Brian Hart (Cisco Systems)

September 2016 Meeting Protocol Please announce your affiliation when you first address the group during a meeting slot Slide 3 TGax MU ad-hoc group

Register Indicate attendance Attendance December 2015 doc.: IEEE 802.11-11/1588r0 September 2016 Attendance https://murphy.events.ieee.org/imat/attendance/index Register Indicate attendance See document 11-09-0517r0 for more details Slide 4 TGax MU ad-hoc group Dorothy Stanley, Aruba Networks

MU sessions this week MU September 2016 TGax Tuesday AM2 10:30 AM – 12:30 AM Wednesday PM2 4:00 PM – 6:00 PM Monday Tuesday Wednesday Thursday AM1 TGax AM2 MU MAC PM1 PHY PM2 EVE SR Osama Aboul-Magd (Huawei Technologies)

Agenda Items Call meeting to order September 2016 Agenda Items Call meeting to order Patent policy, etc. (Call for Potentially Essential Patents) Ad-hoc rules Set and approve agenda Technical Presentations approved by 802.11ax chair for presentation this week, and related straw polls Any other technical presentations TGax MU ad-hoc group Brian Hart (Cisco Systems)

Participants, Patents, and Duty to Inform July 2014 doc.: IEEE 802.11-12/xxxxr0 September 2016 Participants, Patents, and Duty to Inform All participants in this meeting have certain obligations under the IEEE-SA Patent Policy. Participants: “Shall inform the IEEE (or cause the IEEE to be informed)” of the identity of each “holder of any potential Essential Patent Claims of which they are personally aware” if the claims are owned or controlled by the participant or the entity the participant is from, employed by, or otherwise represents “Personal awareness” means that the participant “is personally aware that the holder may have a potential Essential Patent Claim,” even if the participant is not personally aware of the specific patents or patent claims “Should inform the IEEE (or cause the IEEE to be informed)” of the identity of “any other holders of such potential Essential Patent Claims” (that is, third parties that are not affiliated with the participant, with the participant’s employer, or with anyone else that the participant is from or otherwise represents) The above does not apply if the patent claim is already the subject of an Accepted Letter of Assurance that applies to the proposed standard(s) under consideration by this group Quoted text excerpted from IEEE-SA Standards Board Bylaws subclause 6.2 Early identification of holders of potential Essential Patent Claims is strongly encouraged No duty to perform a patent search Slide #1 TGax MU ad-hoc group Osama Aboul-Magd (Huawei Technologies)

Patent Related Links Patent Policy is stated in these sources: July 2014 doc.: IEEE 802.11-12/xxxxr0 September 2016 Patent Related Links All participants should be familiar with their obligations under the IEEE-SA Policies & Procedures for standards development. Patent Policy is stated in these sources: IEEE-SA Standards Boards Bylaws http://standards.ieee.org/guides/bylaws/sect6-7.html#6 IEEE-SA Standards Board Operations Manual http://standards.ieee.org/guides/opman/sect6.html#6.3 Material about the patent policy is available at http://standards.ieee.org/board/pat/pat-material.html If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at patcom@ieee.org or visit http://standards.ieee.org/board/pat/index.html This slide set is available at http://standards.ieee.org/board/pat/pat-slideset.ppt Slide #2 TGax MU ad-hoc group Osama Aboul-Magd (Huawei Technologies)

Call for Potentially Essential Patents July 2014 doc.: IEEE 802.11-12/xxxxr0 September 2016 Call for Potentially Essential Patents If anyone in this meeting is personally aware of the holder of any patent claims that are potentially essential to implementation of the proposed standard(s) under consideration by this group and that are not already the subject of an Accepted Letter of Assurance: Either speak up now or Provide the chair of this group with the identity of the holder(s) of any and all such claims as soon as possible or Cause an LOA to be submitted Slide #3 TGax MU ad-hoc group Osama Aboul-Magd (Huawei Technologies)

Other Guidelines for IEEE WG Meetings July 2014 doc.: IEEE 802.11-12/xxxxr0 September 2016 Other Guidelines for IEEE WG Meetings All IEEE-SA standards meetings shall be conducted in compliance with all applicable laws, including antitrust and competition laws. Don’t discuss the interpretation, validity, or essentiality of patents/patent claims. Don’t discuss specific license rates, terms, or conditions. Relative costs, including licensing costs of essential patent claims, of different technical approaches may be discussed in standards development meetings. Technical considerations remain primary focus Don’t discuss or engage in the fixing of product prices, allocation of customers, or division of sales markets. Don’t discuss the status or substance of ongoing or threatened litigation. Don’t be silent if inappropriate topics are discussed … do formally object. --------------------------------------------------------------- See IEEE-SA Standards Board Operations Manual, clause 5.3.10 and “Promoting Competition and Innovation: What You Need to Know about the IEEE Standards Association's Antitrust and Competition Policy” for more details. Slide #4 TGax MU ad-hoc group Osama Aboul-Magd (Huawei Technologies)

Ad-hoc Group Straw poll rules Document: 15/0075r0 September 2016 Ad-hoc Group Straw poll rules Document: 15/0075r0 A straw poll needs to achieves at least 75% at the ad-hoc level to be converted to a motion at the TG level. In the case a consensus can not be reached within an Ad Hoc group (a stalemate that prohibits further progress), the subject is moved to the Task group, if an Ad Hoc straw poll vote to move the subject to the Taskgroup achieves >50% approval. A straw poll affecting the Spec Framework has to start with, Do you agree to add to the TG Specification Frame work document? x.y.z. <feature description> For further details, please see the operating rules for Tgax Ad-hoc groups https://mentor.ieee.org/802.11/dcn/15/11-15-0075-00-00ax-operating-rules-for-tgax-ad-hoc-groups.docx TGax MU ad-hoc group

Submissions (MU) September 2016 Presented Deferred Not presented DCN Title Author Ad Hoc Notes 11-16/773 Comment Resolution Section 25.6 HE Sounding Raja Banerjea MU presented before July meeting. New revision 11-16/0929 CR - UL MU Operation Simone Merlin presented during a telecon. 11-16/1152 DL OFDMA Ack rule for uplink trigger based PPDU Ming Gan 11-16/1158 Comment resolution on OFDMA random access procedure Jeongki Kim 11-16/1162 Comment Resolution on Retransmission of OFDMA Random Access Yunbo Li 11-16/1163 Concluding OFDMA M-BA transmission Zhou Lan 11-16/1177 comment-resolution-TXOP-truncation Young-Hoon Kown 11-16/1239 Trigger Frame_MUBAR_part1 11-16/1241 Trigger Frame_MUBAR_part2 MAC 11-16/1199 Proposed text changes for DL OFDMA Acknowledge rule for trigger based PPDU 11-16/1222 Comment Resolution on UL OFDMA Random Access Chittabrata Ghosh 11-16/1224 Random Access Parameter Set (RAPS) element 11-16/1183 MU RTS CTS data rate comment Liwen Chu 11-16/1173 Comment Resolution on Two NAVs - Part II Po-Kai Huang Presented Deferred Not presented TGax MU ad-hoc group

September 2016 SP#1 Do you agree to approve resolution of CIDs 55, 1000, 1221, 1915, 2234, 802, 1695, 1222, 182, 971, 2713, 702, 1916, 2233, 223 as proposed in doc 11-16/773r4? Accepted without objection 11-16/773r4 TGax MU ad-hoc group

September 2016 SP#2 Do you agree to add the following text after the end of the first paragraph of section 10.3.2.11.3 of the draft spec: Specifically, when an AP transmits an immediate acknowledgement in HE MU PPDU in response to (A-)MPDU sent in HE trigger-based PPDU, the AP should send it within the 20 MHz channel(s) where the pre-HE modulated fields of the HE trigger-based PPDU sent by the STA are located. The immediate acknowledgement is either Block Ack frame (or Ack frame) or Multi-STA Block Ack frame. Accepted without objection 11-16/1199r3 TGax MU ad-hoc group

September 2016 SP#3 Do you agree to approve resolution of CIDs 787 and 2471 as proposed in doc 11-16/1158r2? Accepted without objection 11-16/1158r2 TGax MU ad-hoc group

September 2016 SP#4 Do you agree to approve resolution of CIDs 49, 601, 442, 2385, 51, 602, 1198, 2684, 181, 440 and 2291 as proposed in doc 11-16/1162r1? Accepted without objection 11-16/1162r1 TGax MU ad-hoc group

SP#5 Do you support adding the following paragraph after the first paragraph of section 25.4.1 A HE AP should only transmit group addressed M-BA in the DL MU PPDU to HE non AP STA n on the (broadcast RU) RU (26/52/106/242/484/996) that includes the RU used for receiving the immediate preceding HE Trigger Based PPDU from STA n. There shall be no more than one M-BA that is addressed to multiple recipients carried in a broadcast RU of the DL MU PPDU. Accepted without objection 11-16/1163 TGax MU ad-hoc group

September 2016 SP#6 Do you agree to approve resolution of CIDs 18, 204, 626, 673, 737, 738, 810, 1440, 1660, 2193, 2283, 2447, 2613, 2614 and 992 as proposed in doc 11-16/1177r2? Accepted without objection 11-16/1177r2 TGax MU ad-hoc group

September 2016 SP#7 Do you agree to approve resolution of CIDs 5, 108, 512, 566, 567, 615, 665, 973, 1308, 1815, 2220, 2252, 2423, 2585 and 2586 as proposed in doc 11-16/1239r1? Accepted without objection 11-16/1239r1 TGax MU ad-hoc group

September 2016 SP#8 Do you agree to approve resolution of CIDs 863, 219, 411, 2380, 2609, 671, 2115, 986 and 734 as proposed in doc 11-16/1183r3? Accepted without objection 11-16/1183r3 TGax MU ad-hoc group

September 2016 SP#9 Do you agree to approve resolution of CIDs 47, 48, 179, 180, 450, 600, 701, 801, 820, 988, 1084, 1199, 1201, 1913, 1914 and 2384 as proposed in doc 11-16/1222r1? Accepted without objection 11-16/1222r1 TGax MU ad-hoc group

September 2016 SP#10 Do you agree to approve resolution of CIDs 2316, 631, 811, 2905, 2257, 632, 205 and 966 as proposed in doc 11-16/1173r2? Accepted without objection 11-16/1173r2 TGax MU ad-hoc group