1 / 66

TGac November 2010 Agenda

TGac November 2010 Agenda. Authors:. Date: 2010-11-07. Meeting Protocol. Please announce your affiliation when you first address the group during a meeting slot. Slide 2. Attendance. https://murphy.events.ieee.org/imat/attendance/index Register Indicate attendance

brynne-drake
Download Presentation

TGac November 2010 Agenda

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TGac November 2010 Agenda Authors: Date: 2010-11-07 Osama Aboul-Magd (Samsung)

  2. Meeting Protocol Please announce your affiliation when you first address the group during a meeting slot Slide 2 Osama Aboul-Magd (Samsung)

  3. Attendance https://murphy.events.ieee.org/imat/attendance/index Register Indicate attendance See document 11-09-0517r0 for more details Slide 3 Osama Aboul-Magd (Samsung)

  4. Attendance, Voting & Document Status Make sure your badges are correct If you plan to make a submission be sure it does not contain company logos or advertising Questions on Voting status, Ballot pool, Access to Reflector, Documentation, member’s area see Adrian Stephens – adrian.p.stephens@intel.com Cell Phones Silent or Off Slide 4 Osama Aboul-Magd (Samsung)

  5. Patent Policy • Following 5 slides Osama Aboul-Magd (Samsung)

  6. The IEEE-SA strongly recommends that at each WG meeting the chair or a designee: Show slides #1 through #4 of this presentation Advise the WG attendees that: The IEEE’s patent policy is consistent with the ANSI patent policy and is described in Clause 6 of the IEEE-SA Standards Board Bylaws; Early identification of patent claims which may be essential for the use of standards under development is strongly encouraged; There may be Essential Patent Claims of which the IEEE is not aware. Additionally, neither the IEEE, the WG, nor the WG chair can ensure the accuracy or completeness of any assurance or whether any such assurance is, in fact, of a Patent Claim that is essential for the use of the standard under development. Instruct the WG Secretary to record in the minutes of the relevant WG meeting: That the foregoing information was provided and that slides 1 through 4 (and this slide 0, if applicable) were shown; That the chair or designee provided an opportunity for participants to identify patent claim(s)/patent application claim(s) and/or the holder of patent claim(s)/patent application claim(s) of which the participant is personally aware and that may be essential for the use of that standard Any responses that were given, specifically the patent claim(s)/patent application claim(s) and/or the holder of the patent claim(s)/patent application claim(s) that were identified (if any) and by whom. The WG Chair shall ensure that a request is made to any identified holders of potential essential patent claim(s) to complete and submit a Letter of Assurance. It is recommended that the WG chair review the guidance in IEEE-SA Standards Board Operations Manual 6.3.5 and in FAQs 12 and 12a on inclusion of potential Essential Patent Claims by incorporation or by reference. Note: WG includes Working Groups, Task Groups, and other standards-developing committees with a PAR approved by the IEEE-SA Standards Board. Instructions for the WG Chair (Optional to be shown) Osama Aboul-Magd (Samsung)

  7. 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 orpatent 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 patentclaim 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 Osama Aboul-Magd (Samsung)

  8. 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 Patent Related Links 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 Osama Aboul-Magd (Samsung)

  9. 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 Call for Potentially Essential Patents Slide #3 Osama Aboul-Magd (Samsung)

  10. 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 Osama Aboul-Magd (Samsung)

  11. Agenda Items for the Week • Call for secretary • Review from September2010 • Approve minutes from September 2010 • Ad Hoc group meetings and straw polls • Updating task group documents as needed • Channel models • Functional Requirements and Evaluation methodology • Selection Procedure • Specification Framework • Timeline Discussion • Technical Submissions Osama Aboul-Magd (Samsung)

  12. Submissions • PHY • 10/1227, “11ac Explicit Feedback “, Joonsuk Kim (Broadcom) • 10/1242, “120MHz Channelization Solution”, Kaiying Lv (ZTE) • 10/1243, “120MHz Preamble for 120 MHz”, Bo Sun(ZTE) • 10/1244, “Transmission Mechanism in MU-MIMO”, Bo Sun (ZTE) • 10/1245, “Pilot Pattern for 120MHz”, Bo Sun (ZTE) • 10/1247, “Data-Subcarrier and Interleaving for 120MHz”, Bo Sun (ZTE) • 10/1248, “Bandwidth Indication Design for 120MHz”, Peng Liang • 10/1255, “TX Mask for Noncontiguous 160 MHz”, Youhan Kim (Atheors) • 10/1256, “Rotation Modulation Application to 802.11ac system”, Zhanji • 10/1257, “Phase Rotation for 120 MHz 802.11ac Mixed Mode Packet”, Hui Zhao (BUPT) • 10/1259, “Channelization for China's spectrum”, Zhendong (CATR) • 10/1264, “160MHz Stream Parser”, Hongyuan Zhang (Marvell) • 10/1275, “Complexity reduction for time domain H matrix feedback”, Laurent CARIOU (France Telecom) • 10/1279, “Segment Parser for 160MHz”, Minho Cheong (ETRI) • 10/1282, “plcp rx procedure”, Eldad Perahia (Intel) • 10/1290, “VHT-SIG-B in NDPs”, Allert van Zelst (Qualcomm) • 10/1300, “LDPC for 11AC”, Jun Zheng (Broadcom Corp.) • 10/1301, “Legacy CSD Table for 11AC”, Jun Zheng (Broadcom Corp.) Osama Aboul-Magd (Samsung)

  13. Submission (Cntd) • Coexistence • 10/1294, “System Capacity Evaluation in OBSS Environment at 5 GHz band”, Tomoki Murakami (NTT) • 10/1280, “CCA for RTS/CTS Operation in Wider Channels”, Simone Merlin • 10/1281, “BW-and-static-dynamic-indication-within-legacy, “Brian Hart (Cisco Systems) • 10/1289, “RTS CTS Operation for Wider Bandwidth”, Michelle Gong (Intel) • 10/1233, “Overlapping BSS Co-Existence”, Jarkko Kneckt (Nokia) • 10/1271, “Protection of IEEE 802.11ac Downlink with Single-RTS-Multiple-CTS”, Haiguang Wang, Jaya Shankar, Zhongding Lei • 10/1274, “Non contiguous 40+40Mhz for Europe/Japan/Global”, Philippe CHRISTIN (France Telecom) • MU-MIMO • 10/1277, “MU-MIMO support for Heterogeneous Devices”, Daewon Lee (LG Electronics) • 10/1288, “Frame Format for GroupID Management”, Sameer Vermani (Qualcomm) • 10/1258, “Efficient Frame format for MU transmission”, Yunzhou Li (Tsinghua) • 10/1265, “explicit feedback dimension reduction procedures”, Nir Shapira (Celeno) • 10/1266, “mcs control over explicit sounding feedback”, Nir Shapira (Celeno) • 10/1293, “Performance evaluation of MU-RTS under OBSS environment”, B. A. Hirantha Sithira Abeysekera (NTT) • MAC • 10/1267, “vht-capabilities-and-operation-elements-and-vhtc-field”, Yong Liu (Marvell) • 10/1254, “Notification on Change of BW and Rx Nss”, Joshua, Zhao Atheros • 10/1302, “DL MU TXOP Power Save”, Patil Sandhya (Samsung) • 10/1278, “BSS load balancing for MU-MIMO”, Daewon Lee (LG Electronics) Osama Aboul-Magd (Samsung)

  14. TGac Schedule in a Glance Osama Aboul-Magd (Samsung)

  15. Monday November 8th, 9:00 – 11:00 Ad Hoc Group Meetings PHY and MAC Ad Hocs Presentations and Straw Polls Monday November 8th, 16:00 – 18:00 Call for Secretary IEEE IPR and Patent Policy Approve of September minutes Review from September meeting TG Motions Tuesday November 9th, 08:00 – 10:00 Ad Hoc Group Meetings PHY and MU-MIMO Ad Hocs (joint Session) Presentations and Straw Polls Tuesday November 9th 10:30 – 12:30 Ad Hoc Group Meetings PHY and COEXAd Hocs Presentations and Straw Polls Wednesday November 10th, 08:00 – 10:00 Ad Hoc Group reports TG Motions Wednesday November 10th, 16:00 – 18:00 Ad Hoc Group Meetings PHY and MAC Ad Hocs Presentations and Straw Polls Thursday November 11th, 10:30 – 12:30 Ad Hoc Group Meetings COEX and MU-MIMO Ad Hocs Presentations and Straw Polls Thursday November 11th, 13:30 – 15:30 TG Meeting Call for secretary Ad Hoc group reports and straw polls TG Motions Timeline Discussion Presentations Goals for January 2011 Conference calls Tentative TGac Agenda for the Week Osama Aboul-Magd (Samsung)

  16. Agenda for Monday, November 8th, 9:00 – 11:00 • AD Hoc Group Meetings • PHY (Landmark C) • MAC (Cumberland G) Osama Aboul-Magd (Samsung)

  17. Agenda for Monday, November 8th, 16:00 – 18:00 (Landmark C) • TG Meeting • Call for secretary • Patent policy, etc. • Set agenda • Call for submissions • Review from September 2010 • Approve minutes from September 2010 • TG documents and presentations • TG motions, if any • Recess Osama Aboul-Magd (Samsung)

  18. Review from September 2010 • Continued with the Ad Hoc group meetings. Ad Hoc group reports are available at: • PHY Ad Hoc report  11-10-1097r3 • MU-MIMO Ad Hoc report  11-10-1102r5 • Coexistence Ad Hoc report  11-10-1122r3 • MAC Ad Hoc Ad Hoc report . 11-10-1100r3 • Motions passed to update the TG Specification Framework in areas related to: • MAC: AID Selection, DL MU-MIMO TXOP Sharing, A-MPDU Delimiter, Max MPDU/A-MPDU Sizes • PHY: Explicit Sounding, Phase rotation, Spectral mask, BCC coding rates, NDP sounding, 160 MHz transmission flow, support for channelization in China • Coexistence: Medium access for wider BW, 160 MHz channelization. • MU-MIMO: Sounding frame exchange protocol and formats, backoff procedure for MU-MIMO • The current approved revision of the specification Framework is 09/0992r15 Osama Aboul-Magd (Samsung)

  19. Approval of September 2010 Minutes • Motion to approve May 2010 TGac minutes as contained in 11-10-1170r0 • Move: Joonsuk Kim • Second: Menzo Wentink • Approved with no objections Osama Aboul-Magd (Samsung)

  20. Motion #1 (MAC 10/1267r0) • Move to update the Spec Framework document to include a VHT Capabilities element as defined in slide 8 of 11-10-1267r0 • Move: Yong • Second: Menzo • Yes: • No: • Abstain: • Motion accepted with no objection Osama Aboul-Magd (Samsung)

  21. Motion #2 (MAC 10/1267r0) • Move to update the Spec Framework doc to include a VHT Operation element as defined in slide 13 of 11-10-1267r0 • Move: Yong • Second: Menzo • Yes: • No: • Abstain: • Motion accepted with no objection Osama Aboul-Magd (Samsung)

  22. Motion #3 (MAC 10/1267r0) • Move to update the Spec Framework doc to define HT/VHT control field as in slide 18 of 11-10-1267r0 • Move: Yong • Second: Menzo • Yes: • No: • Abstain: • Motion accepted with no objection Osama Aboul-Magd (Samsung)

  23. Motion #4 (MAC 10/1254r1) • Move to update TGac spec framework doc to define a new VHT action frame for operating mode change as defined in Slide 5 of 11-10-1254r1 • Move: Joshua • Second: Menzo • Yes: • No: • Abstain: • Accepted with no objection Osama Aboul-Magd (Samsung)

  24. Motion #5 (MAC 1254r1) • Move to update TGac spec framework to add the concept of optionally using Power Save mode in the “operating mode notification” frame exchange sequence as described in slide 4 of 11-10-1254r1 • Move: Joshua • Second: Menzo • Yes: • No: • Abstain: • Accepted with no objection Osama Aboul-Magd (Samsung)

  25. Motion #6 (MAC 10/1302r0) • Move to update the Spec Framework to include the operation of MU TXOP power save capable STA during downlink MU TXOP for power save as follows: • STA saves power till the end of DL MU TXOP after it finds that it is not a member of Group ID received in VHT-SIG-A. • STA saves power till the end of DL MU TXOP after receiving VHT-SIG-A with corresponding NSTS = 0 for its position in Group ID. • STA saves power till the end of DL MU TXOP after sending BA in response to frame with “More Data” bit =0. • Note that support for DL MU TXOP power save is optional at both STA and AP • Move: Sandhya Second: Menzo • Yes: No: Abstain • Accepted with no objection Osama Aboul-Magd (Samsung)

  26. Motion #7 (MAC 10/1302r0) • Move to update the Spec Framework to include, if AP chooses to allow MU TXOP power saving as described in motion #6 for certain downlink MU TXOP, then AP shall include NAV-set sequence at the beginning of that TXOP • Move: Sandhya Second: Menzo • Yes: No: Abstain • Motion accepted with no objection Osama Aboul-Magd (Samsung)

  27. Motion #8 (MAC 10/1302r0) • Move to update the Spec Framework doc to include TXOP PM modes at STA that is used as mentioned in slide #5 of 11-10-1302r0 • Move: Sandhya Second: Menzo • Yes: No: Abstain • Motion accepted with no objection Osama Aboul-Magd (Samsung)

  28. Motion #9 (MAC 10/1302r0) • Move to update the Spec Framework doc to add a bit that indicates whether or not AP allows STAs in TXOP PS mode to do power save during a downlink MU TXOP as mentioned in motion #6. The exact bit to be used is TBD. • Move: Sandhya Second: Menzo • Yes: No: Abstain • Accepted with no objection Osama Aboul-Magd (Samsung)

  29. Motion #10 (MAC 10/1278r0) • Move to update the Spec Framework to include an additional load information element target for MU-MIMO capable devices as shown in slide 12 of 11-10-1278r0. • BSS load element for MU-MIMO contains 1 octet element ID field, 1 octet length field, and N octet TBD field, in which N is TBD • Move: Daewon Second: Menzo • Yes: No: Abstain • Accepted with no objection Osama Aboul-Magd (Samsung)

  30. Motion # 11 (PHY 10/1290r0) • Move to accept the bit patterns as listed on slide 5 of 11-10-1290r0 as the fixed bit patterns for VHT-SIG-B in VHT NDPs • Move: Joonsuk • Second: Menzo • Yes: • No: • Abstain: • Accepted with no objection Osama Aboul-Magd (Samsung)

  31. Motion #12 (PHY 10/1255r0) • Move to accept the transmit spectral mask for noncontiguous 160 MHz transmissions as described on slide 4 of 11-10-1255r1, and to edit the specification framework document (11-09/0992r15) accordingly • Move: Youhan Kim • Second: Menzo • Yes: • No: • Abstain: • Accepted with no objection Osama Aboul-Magd (Samsung)

  32. Motion #13 (PHY 10/1264r0) • Move to include the following text into 3.2.4.3.1 (Stream Parser) of the spec framework • “For 160MHz MCSs, if each BCC encoder does not generate integer blocks of S coded bits in each OFDM symbol, then apply the same stream parsing method until the last integer block (floor(NCBPS/NES/S)) of S bits at each encoder. Assuming that at this point in each OFDM symbol each BCC has M.s (M<NSS) residue bits, take the last M.s bits in the current OFDM symbol from the first encoder and allocate them to the first M spatial streams (s bits to each stream); then take the last M.s bits in the current OFDM symbol from the second encoder and distribute these among M spatial streams, starting from the (M + 1)-th spatial stream, and so on. Note that upon reaching the NSS’th spatialstream, we cycle back to the 1st spatial stream. Repeat till all bits are distributed in the current OFDM symbol.” • Move: Joonsuk Second: Menzo • Yes: No: Abstain: • Accepted with no objection Osama Aboul-Magd (Samsung)

  33. Motion #14 (PHY 10/1279r0) • Move to accept the supplementation of 160MHz segment parser (as described in slides 10-12 of 11-10-1279r0) and modify the IEEE Specification Framework for TGac as shown on slide 20 of 11-10-1279r0. • Move: Minho • Second: Menzo • Yes: • No: • Abstain: • Accepted with no objection Osama Aboul-Magd (Samsung)

  34. Motion #15 (PHY 10/1300r0) • Move to accept to use the same MCS table for both BCC and LDPC and update the Spec Framework accordingly • Move: Jun • Second: Menzo • Yes: • No: • Abstain: • Accepted with no objection Osama Aboul-Magd (Samsung)

  35. Motion #16 (PHY 10/1300r0) • Move to accept the use of the same LDPC PPDU encoding process from 802.11n (described in Section 20.3.11.6.5) for 11ac, regarding codeword length, shortening, puncturing and repetition. • Move: Jun • Second: Menzo • Yes: • No: • Abstain: • Accepted with no objections Osama Aboul-Magd (Samsung)

  36. Motion #17 (PHY 10/1300r0) • Move to accept the use of the proposed solution in slide 9-12 of 11-10-1300r0 for LDPC encoding/decoding process and modify the IEEE Specification Framework for TGac as suggested by Appendix A of 11-10-1300r0 • Move: Jun • Second: Menzo • Yes: • No: • Abstain: • Accepted with no objection Osama Aboul-Magd (Samsung)

  37. Motion #18 (PHY 10/1300r0) • Move to adopt the concept of LDPC tone mapping, as described in slide 15-18 of 11-10-1300r0, for LDPC-coded streams with DTM=4/6/9/9 for 20/40/80/160 MHz (Tone interleaving for 160 is done as 2 separate 80). • Move: Jun • Second: Menzo • Yes: • No: • Abstain: • Accepted with no objection Osama Aboul-Magd (Samsung)

  38. Motion #19 (PHY 10/1301r0) 802.11n Legacy CSD table • Move to accept the use the following CSD table for legacy preamble and add the language provided in the Appendix of 11-10-1301r0 to Clause 3.2.3.1.1 of the TGac Specification Framework. • Move: Jun • Second: Menzo • Yes: • No: • Abstain: • Accepted with no objection Osama Aboul-Magd (Samsung)

  39. Agenda for Tuesday, November 9th, 08:00 – 10:00 • Ad Hoc Group Meetings • Joint Meeting (Landmark C) • PHY • MU-MIMO Osama Aboul-Magd (Samsung)

  40. Agenda for Tuesday, November 9th, 10:30 – 12:30 • Ad Hoc Group Meetings • PHY (Landmark C) • COEX (Cumberland G) Osama Aboul-Magd (Samsung)

  41. Agenda for Wednesday, November 10th, 08:00 – 10:00 (Landmark C) • TG Meeting • Agenda Discussion • TG motions Osama Aboul-Magd (Samsung)

  42. Motion #20 (PHY 10/1105r1) • Move to adopt compressed V matrix feedback (based on 20.3.12.2.5 and 7.3.1.29 in 11n spec) as the only feedback format for SU beamforming and MU-MIMO, and add the same statement into the spec framework • Move: Hongyuan • Second: Menzo • Yes: 46 • No: 4 • Abstain:10 • Motion passes Osama Aboul-Magd (Samsung)

  43. Motion #21 (PHY 10/1265r1) • Move to accept enabling the beamformer to control the explicit feedback dimension for each user in MU-MIMO operation, and to update the specification framework document accordingly • Move: Nir • Second: Menzo • Yes: 24 • No: 3 • Abstain: 36 • Motion passes Osama Aboul-Magd (Samsung)

  44. Motion #22 (PHY 10/1265r1) • Move to add TBD dimension reduction information per user in MU-MIMO operation to the NDPA frame, and update the Specifications Framework document accordingly • Move: Nir • Second: Menzo • Yes: 9 • No: 3 • Abstain: 60 • Motion Passes Osama Aboul-Magd (Samsung)

  45. Motion #23 (PHY 10/1277r0) • Move to redefine the VHT-SIG-A2 bit B2, B4, B5, and B6 in the specification framework document r15 to be described as following • For SU: • B2: Set to 0 for BCC, 1 for LDPC • For MU: • B2: Set to 0 for BCC, 1 for LDPC for the 1st user • B4: Set to 0 for BCC, 1 for LDPC for the 2nd user • B5: Set to 0 for BCC, 1 for LDPC for the 3rd user • B6: Set to 0 for BCC, 1 for LDPC for the 4th user • Note: if user 1, 2, 3, and/or 4 has 0 Nsts value, then corresponding bit is reserved and set to 1 • Move: Byeongwoo Second: Menzo • Yes: No: Abstain • Motion accepted with no objection Osama Aboul-Magd (Samsung)

  46. Motion #24 (PHY 10/1227r0) • Move to accept the VHT MIMO Control Field in the beamforming report frame as described in slide 5 of 11-10-1227r0 and to update the VHT MIMO Control Field in the spec framework document accordingly • Move: Joonsuk • Second: Menzo • Yes: • No: • Abstain: • Accepted with no objection Osama Aboul-Magd (Samsung)

  47. Motion #25 (PHY 10/1227r0) • Move to accept feedback tone mapping as shown on slide 14 of 11-10-1227r0 and to define it in the spec framework document accordingly • Move: Joonsuk • Second: Menzo • Yes: • No: • Abstain: • Accepted with no objection Osama Aboul-Magd (Samsung)

  48. Motion #26 (PHY 10/1227r0) • Move to accept the Sub-Channel Feedback Tone Interpretation as in slide 15 of 11-10-1227r0 and add the text in the spec framework document • Move: Joonsuk • Second: Menzo • Yes: • No: • Abstain: • Motion accepted with no objection Osama Aboul-Magd (Samsung)

  49. Motion #27 (PHY 10/1227r0) • Move to include per-tone-SNR field in the MU-MIMO exclusive beamforming report as described in slide 19 and 20 of 10-11-1227r0, and to add the proposed field in the spec framework document • Move: Jonnsuk • Second: Menzo • Yes: • No: • Abstain: • Motion accepted with no objection Osama Aboul-Magd (Samsung)

  50. Motion # 28 (PHY 10/1227r0) • Move to define SNR per tone for PT-SNR subfield as described in slide 18 of 11-10-1227r0 and to add the proposed text in the second bullet in the spec framework document • Move: Joonsuk • Second: Menzo • Yes: • No: • Abstain: • Motion accepted with no objection Osama Aboul-Magd (Samsung)

More Related