1. TGac January 2011 Agenda Date: 2011-01-13 Authors: January 2011
doc.: IEEE /0011r0
January 2011
TGac January 2011 Agenda
Date:
Authors:
Osama Aboul-Magd (Samsung)
Osama Aboul-Magd (samsung)

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

3. Register Indicate attendance Attendance
January 2011
Attendance
Register
Indicate attendance
See document r0 for more details
Slide 3
Osama Aboul-Magd (Samsung)

4. Attendance, Voting & Document Status
January 2011
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 –
Cell Phones Silent or Off
Slide 4
Osama Aboul-Magd (Samsung)

5. Patent Policy Following 5 slides January 2011 January 2011
doc.: IEEE /0011r0
January 2011
Patent Policy
Following 5 slides
Osama Aboul-Magd (Samsung)
Osama Aboul-Magd (samsung)

6. Instructions for the WG Chair
January 2011
doc.: IEEE /0011r0
January 2011
Instructions for the WG Chair
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 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.
(Optional to be shown)
Osama Aboul-Magd (Samsung)
Osama Aboul-Magd (samsung)

7. Participants, Patents, and Duty to Inform
January 2011
doc.: IEEE /0011r0
January 2011
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
Osama Aboul-Magd (Samsung)
Osama Aboul-Magd (samsung)

8. Patent Related Links Patent Policy is stated in these sources:
January 2011
doc.: IEEE /0011r0
January 2011
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
IEEE-SA Standards Board Operations Manual
Material about the patent policy is available at
If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at or visit
This slide set is available at
Slide #2
Osama Aboul-Magd (Samsung)
Osama Aboul-Magd (samsung)

9. Call for Potentially Essential Patents
January 2011
doc.: IEEE /0011r0
January 2011
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
Osama Aboul-Magd (Samsung)
Osama Aboul-Magd (samsung)

10. Other Guidelines for IEEE WG Meetings
January 2011
doc.: IEEE /0011r0
January 2011
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 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)
Osama Aboul-Magd (samsung)

11. Agenda Items for the Week
January 2011
Agenda Items for the Week
Call for secretary
Review from November2010
Approve minutes from November2010
Ad Hoc group meetings and straw polls
Updating task group documents as needed
Selection of the TGac Technical Editor
Approve TGac Draft D0.1 and start TG review
Technical Submissions
Osama Aboul-Magd (Samsung)

12. Submissions January 2011 PHY MAC January 2011
doc.: IEEE /0011r0
January 2011
Submissions
PHY
11/0029, “256-QAM TX EVM and RX Sensitivity”, Youhaan Kim (Atheors)
11/0030, “Adjacent and Nonadjacent Channel Rejection”, Youhan Kim (Atheors)
11/0032, “STBC with multiple spatial streams”, Sun Bo (ZTE)
11/0033, “RIFS Mode”, Joshua Zhao (Atheros)
11/0039, “Partial AID field”, Simone Merlin (Qualcomm)
11/0047, “VHT Link Adaptation”, Hongyuan Zhang (Marvell)
11/0048, “Interleaver for Nss Greater than 4”, Hongyuan Zhang (Marvell)
11/0049, “VHT NDP Transmission”, Hongyuan Zhang (Marvell)
11/0052, “Max Nss for SU BF” Sameer Vermani (Qualcomm)
11/0063, “80-MHz Non-Contiguous Channel Spectrum”, Tian-Wei Huang (National Taiwan University)
11/0064, “Modulo Precoding for 11ac”, Leonardo Lanante Jr. (Kyushu Inst. of Tech.)
11/0122, “Transmit OOB emission”, Raja (Marvell Semiconductor)
MAC
11/0025, “gcmp restriction”, Matthew Fischer (Broadcom)
11/0026, “VHT Supported MCS Field”, Sameer Vermani (Qualcomm)
11/0034, “max-frame-length-changes”, Yong Liu (Marvell)
11/0036, “vht-nav-assertion”, Yong Liu (Marvell)
11/0037, “BW-indication-in-non-HT-frames”, Yong Liu (Marvell)
11/0040, “VHT control field and link adaptation“Simone Merlin (Qualcomm)
11/0041, “Sounding protocol - segmentation and null feedback”, Simone Merlin (Qualcomm)
11/0045, “sounding-sequence-for-su-only-beamformee”, Yong Liu, Marvel
11/0050, “VHT BF and MU Capabilities”, Hongyuan Zhang (Marvell)
11/0091, “DL TXOP PS protocol”, Patil Sandhya (Samsung)
11/097, “Bandwidth-Specific-TXOP-Limits”, Jarkko Kneckt (Nokia)
11/0098, “Bandwidth-Specific-TXOP-Limits-Text”, Jarkko Kneckt (Nokia)
Osama Aboul-Magd (Samsung)
Osama Aboul-Magd (samsung)

13. Submission (Cntd) January 2011 Coexistence MU-MIMO
11/0059, “RTS CTS rule amendment”, Liwen Chu (STMicroelectronics)
11/0061, “CCA Threshold Levels”, Ron Porat (Broadcom)
11/0081, “Transmission rules for wider bandwidth TXOP”, Michelle Gong (Intel)
11/0108, “Impact evaluation of considering complex environment in the dense cases”, Philippe Chambelin (Technicolor)
11/0127, “Reserving STA”, Jarkko Kneckt(Nokia)
MU-MIMO
11/0053, “Dimension Reduction for MU-MIMO”, Sameer Vermani (Qualcomm)
11/0082, “Errory recovery TXOP sharing”, Michelle Gong (Intel)
11/0095, “Indication of Group Address Text”, Jarkko kneckt (Nokia)
11/0096, “Indication of Group Address”, Jarkko Kneckt (Nokia)
11/0102, “Maximum dimension per stream SNR feedback”, Nir Shapira (Celeno)
11/0111, “No MCS recommendation in MFB for MU MIMO”, Nir Shapira
Osama Aboul-Magd (Samsung)

14. TGac Schedule in a Glance
January 2011
TGac Schedule in a Glance
Monday
Tuesday
Wednesday
Thursday
AM1
PHY
COEX
(joint meeting)
TGac
MU-MIMO
AM2
MAC
PM1
PM2
TGac (1 hr)
PHY (1 hr)
PM3
Osama Aboul-Magd (Samsung)

15. Tentative TGac Agenda for the Week
January 2011
doc.: IEEE /0011r0
January 2011
Tentative TGac Agenda for the Week
Monday January 17th, 16:00 – 18:00
Call for Secretary
IEEE IPR and Patent Policy
Approve of January minutes
Review from November meeting
Presentations
Recess for PHY Ad Hoc
Monday January 17th, 19:30 – 21:30
Ad Hoc Group Meetings
PHY and MAC Ad Hocs
Presentations, straw polls, and pre-motions
Tuesday January 18th, 08:00 – 10:00
PHY and COEXAd Hocs (joint meeting)
Tuesday January 18th 10:30 – 12:30
MAC and MU-MIMO Ad Hocs
Wednesday January 19th, 08:00 – 10:00
TGac meeting
Ad Hoc Group reports
TG Motions
Recess for MU-MIMO
Wednesday January 19th, 13:30 – 15:30
Ad Hoc Group Meetings
PHY and COEX Ad Hocs
Presentations and Straw Polls
Thursday January 20th, 10:30 – 12:30
PHY and MAC Ad Hocs
Thursday January 20th, 16:00 – 18:00
TG Meeting
Call for secretary
Ad Hoc group reports and straw polls
Approve TGac Draft D0.1
Technical Editor election
Presentations
Goals for March 2011
Conference calls
Osama Aboul-Magd (Samsung)
Osama Aboul-Magd (samsung)

16. Agenda for Monday, January 17th, 16:00 – 18:00 (Constellation 1/2)
TG Meeting
Call for secretary
Patent policy, etc.
Set agenda
Call for submissions
Review from November 2010
Approve minutes from November 2010
NUHT Discussion
TG documents and presentations
TG motions, if any
Recess
Osama Aboul-Magd (Samsung)

17. Approval of November 2010 Minutes
January 2011
Approval of November 2010 Minutes
Motion to approve November 2010 TGac minutes as in document r0
Move: Menzo
Second: Robert
Motion accepted with no objections
Osama Aboul-Magd (Samsung)

18. January 2011
Review from November 2010
Approved a new revision of the TGac Specification Framework document ( r18)
Submission r1 includes a proposed TGac Draft Amendment
r0 is the related presentation
For a complete set of motions, please refer to 10/1214r7
Minutes are available in doc r0
Osama Aboul-Magd (Samsung)

19. Agenda for Monday, January 17th, 19:30 – 21:30
doc.: IEEE /0011r0
January 2011
Agenda for Monday, January 17th, 19:30 – 21:30
Ad Hoc Group Meetings
PHY (Constellation 1)
MAC (Constellation 2)
Osama Aboul-Magd (Samsung)
Osama Aboul-Magd (samsung)

20. Agenda for Tuesday, January 18th, 08:00 – 10:00
doc.: IEEE /0011r0
January 2011
Agenda for Tuesday, January 18th, 08:00 – 10:00
Ad Hoc Group Meetings
PHY and COEX joint meeting (Constellation 1)
Osama Aboul-Magd (Samsung)
Osama Aboul-Magd (samsung)

21. Agenda for Tuesday, January 18th, 10:30 – 12:30
doc.: IEEE /0011r0
January 2011
Agenda for Tuesday, January 18th, 10:30 – 12:30
Ad Hoc Group Meetings
MAC (Constellation 1)
MU-MIMO (Constellation 2)
Osama Aboul-Magd (Samsung)
Osama Aboul-Magd (samsung)

22. Agenda for Wednesday, January 19th, 08:00 – 10:00
doc.: IEEE /0011r0
January 2011
Agenda for Wednesday, January 19th, 08:00 – 10:00
TG Meeting
TG motions
Presentation on FR-EM – Minho Cheong
11/0127, “Reserving STA”, Jarkko Kneckt(Nokia)
Agenda Discussion
Recess for MU-MIMO (if time allows)
Osama Aboul-Magd (Samsung)
Osama Aboul-Magd (samsung)

23. January 2011
Motion #1: (PHY 11/0029)
Move to support -30 dB and -32 dB as the TX EVM requirements for 256-QAM 3/4 and 5/6, respectively, and to edit the specification framework document (11-09/0992) accordingly
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

24. January 2011
Motion #2: (PHY 11/0029)
Move to support support receiver minimum sensitivity for 256-QAM ¾ and 5/6 as shown on slide 7 0f 11-11/0029 and to edit the specification framework document (11-09/0992) accordingly
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

25. January 2011
Motion #3: (PHY 11/0030)
Move to support adjacent/nonadjacent channel rejection for 11ac as shown on slides 6 and 7 ( ac-adjacent-and-nonadjacent-channel-rejection), and editing the specification framework document (11-09/0992) accordingly
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

26. January 2011
Motion #4: (PHY 11/0030)
Move to support adjacent/nonadjacent channel rejection for 11ac as shown on slides 6 and 7 ( ac-adjacent-and-nonadjacent-channel-rejection), and editing the specification framework document (11-09/0992) accordingly
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

27. January 2011
Motion #5 (PHY 11/0033r1)
Move to support that VHT STAs shall not transmit any HT or VHT frames separated by RIFS
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

28. January 2011
Motion #6 (PHY 11/0033r1)
Move to support that VHT AP shall set the RIFS mode bit to 0 in the HT operation element
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

29. January 2011
Motion #7 (PHY 11/0032)
Move to add a new section “ Space-time block coding” into spec framework 0992/r18 and add the table as listed in slide 6 under above new section with following explaining text
=================Proposed text start===========================
Section Space-time block coding
When all streams use STBC, an odd number of space time streams per user shall not be used, and NSTS=2*NSS. For NSTS=2,4, the constellation mapper output to the spatial mapper input for STBC table shall reuse mapping as defined in Clause For NSTS=6,8, the constellation mapper output to the spatial mapper input shall follow the mapping as defined in table X, similarly to mapping defined for NSTS=2,4.
Table X Constellation mapper Output to spatial mapper input for STBC
---insert the table listed in slide 6 here---
==================Proposed text end==========================
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

30. Motion #8 (PHY 11/0039) Move: Second Yes: No: Abstain: January 2011
 Move to modify the spec framework document with the following definition for the partial AID and Group ID field in SIG-A of a SU PPDU
In a VHT PPDU that carries MPDUs addressed to a single non-AP STA, the Partial AID is set as described in slide 5 of IEEE /0039r0
In a VHT PPDU that carries MPDUs addressed to an AP STA, the Partial AID parameter is set to the lower 9 bits of the BSSID
In a VHT PPDU that carries group addressed MPDUs, the Partial AID is set to 0
In a VHT PPDU addressed to an IBSS peer STA, the Partial AID parameter is set to 0
In a SU VHT PPDU,  if the PPDU carries MPDUs addressed to an AP STA, the GROUP ID field is set to all zeros, otherwise it is set to all ones
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

31. Motion #9 (PHY 11/0052) Move: Second Yes: No: Abstain:
January 2011
Motion #9 (PHY 11/0052)
Move to add the following two sub-fields and modify the spec framework document accordingly
‘Max Nss for SU BF’ (applicable only when using an MU type feedback) as an STA operating mode
‘Number of sounding dimensions’ as a transmit side capability
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

32. January 2011
Motion #10 (PHY 11/0052)
Move to accept the use of operating mode field as shown on slide 5 of this document (0052/r0) to convey the ‘Max Nss for SU BF’ and modify the spec framework document accordingly.
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

33. January 2011
Motion #11 (PHY 11/0047)
Move to add the following sentence to the spec framework
6.x VHT Link Adaptation
MRQ in VHT Control Field could be sent with any frame (i.e. not only with NDPA).
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

34. January 2011
Motion #12 (PHY 11/0047)
Move to add the following sentence in spec frame work
6.x VHT Link Adaptation
An SNR Feedback field is included in VHT Control Field, which is defined as 8bit 2’s complement number, averaged over all the tones and all the space-time streams.
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

35. January 2011
Motion #13 (PHY 11/0047)
Move to add the following sentence in spec framework
6.x VHT Link Adaptation
If the MFB requester sends MRQ in an VHT NDP announcement frame requesting only SU-BF Feedbacks, then the MFB responder shall include the corresponding MFB and SNR feedback in the VHT Compressed Beamforming frame that is the response of the same NDP-A and NDP sequence.
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

36. January 2011
Motion #15 (PHY 11/0048)
Move to insert the following text in Frequency interleaver of the spec framework
“For BCC encoding, when Nss>4, the third permutation of the interleaver uses the following parameters:
Permutation as the first Nss values of [ ]*Nrot *NBPSCS.
NROT =28, 13 and 6 for 80MHz, 40MHz and 20MHz, respectively.”
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

37. January 2011
Motion #16 (PHY 11/00122)
Move to insert the following requirements for maximum transmit OOB emission to the spec framework
Add to Table 6--Transmit spectral mask for various BW PPDUs, “Maximum transmit OOB emission” with the following values
20 MHz -53 dBm/MHz, if transmit power is below 0dBm
40 MHz -56 dBm/MHz, if transmit power is below 0dBm
80 MHz dBm/MHz, if transmit power is below 0dBm
80+80 and 160 MHz -59dBm/MHz, if transmit power is below 3dBm
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

38. January 2011
Motion #17: (COEX 11/0061)
Move to accept the following CCA levels on the secondary channels:
20MHz: dBm
40MHz: dBm
80MHz : dBm
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

39. January 2011
Motion #18 (COEX 11/0059)
Move to accept the RTS/CTS rule amendment in slide 4 of (11/0059r0):
“If a VHT STA initiates a TXOP by transmitting a RTS with the Multicast/Unicast bit being set to Multicast in TA, the VHT STA shall not send a RTS to a legacy STA in the TXOP”.
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

40. January 2011
Motion #19 (COEX 11/0081r1)
Move to update the TGac spec framework to include the following protocol rule
If there is no non-HT duplicate frame exchange in a TXOP to set the NAV:
A TXOP holder shall not transmit frames using more bandwidth than the bandwidth occupied by the preceding frame in the same TXOP
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

41. January 2011
Motion #20 (COEX 11/0081r1)
Move to update the TGac spec framework to include the following protocol rule?
If there is at least one non-HT duplicate frame exchange (not a RTS/CTS exchange) in a TXOP:
A TXOP holder shall not transmit frames using more bandwidth than the bandwidth occupied by the first non-HT duplicate frame exchange in the same TXOP
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

42. Motion #21: (MAC 11/0025r2) January 2011
Move to make the following changes in the TGac draft specification:
Editor: add the following text to the end of the 3rd paragraph of REVmb D RSNA policy selection in an ESS
Within an ESS, A VHT STA shall eliminate TKIP and GCMP as choices for the pairwise cipher suite if CCMP is advertised by the AP or if the AP included either an HT Capabilities element or a VHT Capabilities element in its Beacon and Probe Response frames. The elimination of TKIP and GCMP as choices for the pairwise cipher suite may result in a lack of overlap of the remaining pairwise cipher suite choices, in which case the VHT STA shall decline to create an RSN association with that AP.
Editor: add the following text after the 3rd paragraph of REVmb D RSNA policy selection in an IBSS and for DLS:
A VHT STA that is in an IBSS or that is transmitting frames through a direct link shall eliminate TKIP and GCMP as choices for the pairwise cipher suite if CCMP is advertised by the other STA or if the other STA included either an HT Capabilities element or a VHT Capabilities element in any of its Beacon, Probe Response, DLS Request, or DLS Response messages.
NOTE—The elimination of TKIP and GCMP as choices for the pairwise cipher suite might result in a lack of overlap of the remaining pairwise cipher suites choices, in which case the STAs will not exchange encrypted frames.
Move: Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

43. January 2011
Motion #22: (MAC 11/0026)
Move to add the VHT Supported MCS Set Field proposed in this presentation (11/0026r0) to the spec framework document.
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

44. January 2011
Motion #33: ( MAC 11/0034)
Move to update the spec framework document to define the Max VHT Management Frame Length as following
If a management MPDU is sent using a VHT PPDU, the length of the MPDU is constrained by the maximum MPDU length supported by the recipient
The Max VHT Management Frame Body Length can be up to:
11422 octets = – 28 (MAC header) – 4 (FCS) octets
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

45. January 2011
Motion #34: (MAC 11/0034)
Move to update the spec framework document to replace the Maximum A-MSDU Length subfield in the VHT Capabilities element with the max MPDU length subfield
Set to 0 for 3895 octets (Maximum A-MSDU Lenth in HT Capabilities set to 3839 octets)
Set to 1 for 7991 octets (Maximum A-MSDU Length in HT Capabilities set to 7935 octets)
Set to 2 for octets (Maximum A-MSDU Length in HT Capabilities set to 7935 octets)
The value 3 is reserved
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

46. January 2011
Motion #35 (MAC 11/0034)
Move to update the spec framework document to include the following rule:
In case of null padding with EOF, the transmitter shall not count the padding delimiters for the A-MPDU length limit
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

47. January 2011
Motion #36: (MAC 11/0036)
Move to update the spec framework document to define VHT NAV assertion as following
A VHT STA shall update its NAV using the Duration/ID field value in any frame received in a 20 MHz PPDU in the primary 20 MHz channel or received in a 40 MHz PPDU in the primary 40 MHz channel or received in a 80MHz PPDU in the primary 80 MHz channel or received in a 160 MHz or MHz PPDU and that does not have an RA matching the STA’s MAC address.
NOTE—A STA need not set its NAV in response to 20/40/80 MHz frames received on any channel that is not or does not include the primary channel, even if it is capable of receiving those frames.
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

48. January 2011
Motion #37: (MAC 11/0037)
Move to update the spec framework document with the following BW indication rule
A VHT STA that transmits a control frame carried in non-HT or non-HT duplicate format and addressed to a VHT STA and eliciting a control frame transmission or a sounding feedback management frame transmission shall set the INDICATED_CH_BANDWIDTH TXVECTOR parameter of the control frame to the same value as the CH_BANDWIDTH TXVECTOR parameter and shall set the Individual/Group bit in the TA field to 1.
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

49. January 2011
Motion #38: (MAC 11/0040)
Move to update the spec framework document with
The bit B0 in HT Control field is defined as ‘HT/VHT’ field and indicates:
B0 = 0: field is HT Control
B0 = 1: field is VHT Control
If B0 = 1, B1-B31 are TBD
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

50. January 2011
Motion #39: (MAC 11/0040)
Move to update the spec framework document with the VHTC frame and Link Adaptation design as described in slides 5 to 11 of document IEEE /0040r0 (excluding the Notes).
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

51. January 2011
Motion #40: (MAC 11/0041)
Move to update the spec framework document with the following rules for the segmentation of sounding feedback
If it would otherwise result in an MMPDU that exceeds the maximum MPDU size, the VHT Compressed Beamforming Report field may be split into up to TBD segments. The length of each segment shall be equal number of octets for all segments except the last, which may be smaller.
All segments shall be sent within the same A-MPDU
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

52. January 2011
Motion #41: (MAC 11/0041)
Move to update the spec framework document with the introduction of a Null Sounding Feedback response frame, defined as a Compressed Beamforming Report frame without the Compressed Beamforming Report and the MU Exclusive Beamforming Report fields; Presence/absence of the above fields is indicated in the VHT MIMO Control field, with a TBD signaling.
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

53. January 2011
Motion #42: (MAC 11/0041)
Move to support that a STA shall reply to a NDPA or Poll frame with a Null feedback frame in case the STA has no feedback to send
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

54. January 2011
Motion #43: (MAC 11/0045)
Move to update the spec framework document to include the following rule for sounding SU-only beamformee
A beamformer shall sound a SU-only beamformee using a unicast NDPA with a single STA Info field as following
NDP-A => RA = Beamformee’s MAC address
NDP-A => STA Info => sounding control => STA AID = Beamformee’s AID
NDP-A => STA Info => sounding control => SU/MU = SU
NDP-A => STA Info => sounding control => Recommended Dimension = Invalid
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

55. January 2011
Motion #44: (MAC 11/0045)
Move to update the Spec Framework to include the following rule for sounding SU-only beamformee
A beamformer shall only poll a SU-only beamformee for sounding feedback if it received at least one segment of the feedback from the beamformee.
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

56. January 2011
Motion #45: (MAC 11/0050)
Move to add the VHT BF capabilites fields as in slide 4 of 11/0050r0 into a new section 6.x of the spec framework
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

57. January 2011
Motion #46: (MAC 11/0091)
Move to indicate the MU TXOP power Management Capability by AP and the MU TXOP Power Save Mode by STA as described in slide #3 of 11/0091r0, and update the Spec Framework accordingly.
The exact bit on slide #3 in VHT capabilities info field is TBD.
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

58. January 2011
Motion #47: (MAC 11/0091)
Move to indicate the TXOP power save by AP during downlink MU TXOP as described in slide #4 of (11/0091r0) and update the Spec Framework accordingly.
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

59. January 2011
Motion # 48: (MAC 11/0091)
Move to extend the MU TXOP power save for SU TXOP as mentioned in slide #5 of 11/0091r0, and update the Spec Framework accordingly.
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

60. January 2011
Motion # 49 (MU-MIMO 11/0053)
Move to accept the following rule for sounding feedback:
STA shall send a feedback frame with the “MU type” bit in the VHT MIMO control field set to the same value as the MU/SU bit in the corresponding STA’s Info field in NDPA
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

61. January 2011
Motion # 50 (MU-MIMO 11/0053)
Move to accept the following rule for dimension reduction in MU-MIMO
When the Feedback Type field is set to MU, the STA shall send a feedback with the Nc field value in the VHT MIMO Control field equal to the Nc field value in the corresponding STA Info field in the NDPA provided the Nc requested is not larger than the number of currently active receive antennas
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

62. January 2011
Motion #51 (MU-MIMO 11/0082)
Move to update the TGac spec framework to include the following protocol rule
For MU MIMO TXOP sharing:
If a valid response to the initial frame of a TXOP is not received, the AP shall initiate an exponential backoff for the primary AC.
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

63. Motion # 52 (MU-MIMO 11/0049) January 2011
Move to insert the following new section in the spec framework?
6.3.xx Transmission of a VHT NDP
A STA shall transmits a VHT format NDP using the following TXVECTOR parameters:
—        LENGTH shall be set to 0.
—        NUM_USERS shall be set to 1.
—        GROUP ID shall be set to 63 (all ones).
—        NUM_STS shall indicate two or more space-time streams.
The number of space time streams sounded and as indicated by the NUM_STS parameter shall not exceed the value indicated in the Compressed Steering Number of Beamformer Antennas Supported field in the VHT Capability element of the STA that is the intended recipient of the VHT NDP. The NUM_STS parameter may be set to any value, subject to the constraint of the previous sentence, regardless of the value of the Supported MCS Set field of the VHT Capabilities field at either the transmitter or recipient of the NDP.
A STA shall not transmit an NDPA addressed to a STA or broadcast and including a STA’s AID in one of the STA Info fields in the frame unless it has received from that STA a VHT Capability element where the last VHT Capability element received has the SU Beamformee Capability field set to 1 or the MU Rx Capability field is set to 1 or both fields set to 1.
Move:
Second
Yes: No: Abstain:
Osama Aboul-Magd (Samsung)

64. Agenda for Wednesday, January 10th, 13:30 – 15:30
Ad Hoc Group Meetings
PHY
COEX
Osama Aboul-Magd (Samsung)

65. Agenda for Thursday, January 11th, 10:30 – 12:30
Ad Hoc Group Meetings
PHY
MAC
Osama Aboul-Magd (Samsung)

66. Agenda for Thursday, January 10th, 16:00 – 18:00
doc.: IEEE /0011r0
January 2011
Agenda for Thursday, January 10th, 16:00 – 18:00
TG Meeting
Call for secretary
Ad Hoc group reports and straw polls
TG Motions
Specification Framework Motion
Approve of TGac draft D0.1
Technical Editor Selection
Presentations
Goals for March 2011
Conference calls
Osama Aboul-Magd (Samsung)
Osama Aboul-Magd (samsung)

67. Conference call times Not to overlap with TGad Thursday March xx, 2011
January 2011
doc.: IEEE /0011r0
January 2011
Conference call times
Not to overlap with TGad
Thursday March xx, 2011
Osama Aboul-Magd (Samsung)
Osama Aboul-Magd (samsung)