September 2016 Meeting Agenda Date 20160912 Authors Reza Hedayat Newracom IEEE 80211 TGax High Efficiency WLAN MAC Ad Hoc CoChairs Brian Hart Cisco Systems Reza Hedayat Newracom ID: 788786
Download The PPT/PDF document "September 2016 Slide 1 TGax MAC Ad Hoc" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
September 2016
Slide 1
TGax MAC Ad Hoc September 2016 Meeting Agenda
Date: 2016-09-12
Authors:
Reza Hedayat (Newracom)
Slide2IEEE 802.11 TGaxHigh Efficiency WLANMAC Ad HocCo-Chairs: Brian Hart (Cisco Systems)Reza Hedayat (Newracom)Eric Wong (Apple)
Slide 2Reza Hedayat (Newracom)
September 2016
Slide3Slide 3
Agenda ItemsCall meeting to order Patent policy, etc. (Call for Potentially Essential Patents)Call for submissionsSet and approve agendaNote ad hoc rules // Slides 13-14Note MAC ad hoc sessions this week Mon: PM2Tue: AM2, PM2 Wed:PM1, PM2Technical Presentations approved by 802.11ax chair for presentation this week, and related straw pollsAny other technical presentations Reza Hedayat (Newracom)
September 2016
Slide4Slide 4
Slide
4Meeting Protocol, Attendance, Voting & Document Status
Please announce your affiliation when you first address the group during a meeting slotCell Phones to be silent or OffRegister your attendance via https://imat.ieee.org while on a meeting SSID (e.g.
Verilan-secure)Make sure your badges are correct If you plan to make a submission, be sure it does not contain company logos or advertisingQuestions on Voting status, Ballot pool, Access to Reflector, Documentation, Member’s AreaContact Jon Rosdahl –
jrosdahl@ieee.orgReza Hedayat (Newracom)
September 2016
Slide5Slide 5
Patent Policy and Other GuidelinesSee the following 5 slidesReza Hedayat (Newracom)
September 2016
Slide6Slide 6
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 presentationAdvise 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.
(Optional to be shown)
Reza Hedayat (Newracom)
September 2016
Slide7Slide 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 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
Reza Hedayat (Newracom)
September 2016
Slide8Slide 8
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
Slide #2
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
Reza Hedayat (Newracom)
September 2016
Slide9Slide 9
Call for Potentially Essential PatentsIf 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 orProvide the chair of this group with the identity of the holder(s) of any and all such claims as soon as possible orCause an LOA to be submitted
Slide #3
Reza Hedayat (Newracom)
September 2016
Slide10Slide 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 focusDon’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
Reza Hedayat (Newracom)
September 2016
Slide11September MAC SubmissionsIncluding leftover submissions since July 2016
Slide 11Reza Hedayat (Newracom)
September 2016
DCN
Title
Author
Notes11-16/0864d0.1 comment resolution on clause 6Yasuhiko InoueMON/PM1
11-16/0869
Comment resolution section 9.3 TWT
Zhou Lan
MON/PM1
11-16/0881
Comment resolution on ROMI
Jayh Park
MON/PM1
11-16/0882
Comment resolution on TOMI
Alfred Asterjadhi
MON/PM1.
Not
SPed
yet
11-16/0883
Comment resolution for CID152
Jayh Park
MON/PM1
11-16/0884
Spec. Text for HE Operation element and AID Assign Rule
Jianhan Liu
TUE/AM2
11-16/0913
SU Multi-TID Rules
Jarkko Kneckt
11-16/0917
Text for TID value of ALL ACK signaling
Woojin Ahn
Withdrawn
11-16/0918
Discussions on Partial BSS Color
Geonjung Ko
Withdrawn
11-16/0924
NAV resetting with RTS/MU-RTS
Weimin
Xing
TUE/AM2
11-16/0925
Spex
text on NAV resetting with RTS/MU-RTS
Weimin
Xing
TUE/AM2
11-16/0941
CR HE Fragmentation - part 2
Ming Gan
TUE/AM2
11-16/0942
CR Service Field
Ming
Gan
SP deferred to PHY ad hoc
11-16/0960
AP access procedure for UL MU operation
Jinsoo
Ahn
Presented in telecon. No SP
11-16/0961
Consideration on Multi-STA
BlockAck
Optimization
Hanseul
Hong
TUE/AM2
11-16/0962
EDCA rules-follow up 1
Jing Ma
Presented in telecon.
SPed
in TUE/AM2
Slide12September MAC SubmissionsIncluding leftover submissions since July 2016
Slide 12Reza Hedayat (Newracom)
September 2016
DCN
Title
Author
Notes11-16/0998Rules for 2 EDCA parameterslaurent cariou TUE/AM2
11-16/1110
comment resolution on
subclause
10.22.2 and 10.22.4
Yongho Seok
TUE/PM2
11-16/1131
comment resolution on mu
ack
policy
Yongho Seok
TUE/PM2
11-16/1154
MAC CR for CID 966
Weimin Xing
Withdrawn
11-16/1157
Comment resolution on SU_MU ACK procedures
Jeongki
Kim
TUE/PM2
11-16/1173
Comment Resolution on Two NAVs - Part II
Po-Kai Huang
11-16/1180
Proposed text changes for MU EDCA parameters
laurent
cariou
TUE/AM2
11-16/1181
CW value after UL MU procedure
Woojin
Ahn
TUE/PM2
11-16/1182
HE Sounding Feedback Segmentation
Liwen Chu
Withdrawn
11-16/1183
MU RTS CTS data rate comment
Liwen Chu
MU CIDs. Transferred
11-16/1184
A-MPDU 25.10 25.10.2 comment
resolution
Liwen Chu
TUE/PM2
11-16/1185
A-MPDU 25.10.3 comment resolution
Liwen Chu
11-16/1186
A-MPDU Content Comment Resolution
Liwen Chu
11-16/1188
MAC Capabilities in HE Capabilities IE
Alfred Asterjadhi
TUE/PM2
11-16/1189
CC0-TWT operation
Alfred Asterjadhi
11-16/1195
MAC Clarifications
Alfred Asterjadhi
11-16/1204
Intra-PPDU Power Save for a Multiple BSSID Set Case
Geonjung Ko
11-16/1205
Text for Intra-PPDU Power Save for a Multiple BSSID Set Case
Geonjung Ko
11-16/1210
Comment Resolution on MU acknowledgement procedure
Junichi Iwatani
11-16/1211
CR_CID_122_576_972_2598
Huizhao Wang
11-16/1213
CR TWT and HE element related
Matthew Fischer
11-16/1220
MU mode EDCA control
Jinsoo Ahn
11-16/1234
Spec Text for TWT Protectioin field
Hanseul Hong
11-16/1236
Text for Partial BSS Color and AID Assignment Rule
Geonjung
Ko
Withdrawn
11-16/1237
setting-quiet-time-period
Chao-Chun Wang
11-16/1238
Setting Quiet time period - text
Chao-Chun Wang
Slide13Straw-poll MAC-CR1 Do you agree to add to the 11ax specification D0.4 the comment resolutions in document 16/864r5 for CIDs: 83, 1227, 1228, 1229, 1238, 1239, 1240, 2292, 2293, 2294, 2304, 2305, 2306, 1125, 1230, 1241, 1596,1869, 2420, 1123 Results:Strawpoll passed with no objection
Slide 13Reza Hedayat (Newracom)
September 2016
Slide14Straw-poll MAC-CR2 Do you agree to add to the 11ax specification D0.1 the comment resolutions in document 16/869r2 for CIDs: 1315, 2424, 2589, 2590, 2591 Results:Strawpoll passed with no objection
Slide 14Reza Hedayat (Newracom)
September 2016
Slide15Straw-poll MAC-CR3 Do you agree to add to the 11ax specification D0.1 the comment resolutions in document 16/881r1 for CIDs: 2, 60, 61, 184, 185, 207, 445, 446, 655, 685, 775, 856, 1223, 1224, 1562, 1565, 1568, 1569, 1572, 1573, 1574, 2200, 2236, 2238, 2239, 2328, 2330, 2657 Results:Strawpoll passed with no objection
Slide 15Reza Hedayat (Newracom)
September 2016
Slide16Straw-poll MAC-CR4 Do you agree to add to the 11ax specification D0.1 the comment resolutions in document 16/883r1 for CID: 152 Results:Strawpoll passed with no objection
Slide 16Reza Hedayat (Newracom)
September 2016
Slide17Straw-poll MAC-1 Do you agree to add to the 11ax specification D0.4 the proposed text in document 16/884r3. Results:Strawpoll passed with no objection
Slide 17Reza Hedayat (Newracom)
September 2016
Slide18Straw-poll MAC-2 Do you agree to add to the 11ax specification D0.4 the proposed text in document 16/925r1. Results:Strawpoll passed with no objection
Slide 18Reza Hedayat (Newracom)
September 2016
Slide19Straw-poll MAC-CR5 Do you agree to add to the 11ax specification D0.1 the comment resolutions in document 16/941r0 for CIDs: 1477, 675, 423, 166, 1823, 2270, 2268, 2254, 2198, 1824, 1818, 1800, 1796, 1663, 1491, 1489, 1488, 2630 Results:Strawpoll passed with no objection
Slide 19Reza Hedayat (Newracom)
September 2016
Slide20Straw-poll MAC-3 Do you agree to accept the spec changes proposed in document 16/1180r1. Results:Strawpoll passed with no objection
Slide 20Reza Hedayat (Newracom)
September 2016
Slide21Straw-poll MAC-CR6 Do you agree to add to the 11ax specification D0.1 the comment resolutions in document 16/881r2 for CIDs: 2, 60, 61, 184, 185, 207, 445, 446, 655, 685, 775, 856, 1223, 1224, 1562, 1565, 1568, 1569, 1572, 1573, 1574, 2200, 2236, 2238, 2239, 2328, 2330, 2657 Results:Strawpoll passed with no objection
Slide 21Reza Hedayat (Newracom)
September 2016
Slide22Straw-poll MAC-CR-7 Do you agree to add to the 11ax specification D0.1 the comment resolutions in document 16/1110r0 for CIDs: 2468, 2470, 2448, 2450, 2451, 809 Results:Strawpoll passed with no objection
Slide 22Reza Hedayat (Newracom)
September 2016
Slide23Straw-poll MAC-CR8 Do you agree to add to the 11ax specification D0.1 the comment resolutions in document 16/1131r2 for CIDs: 2445, 2457, 2494, 2395 Results: Strawpoll passed with no objection
Slide 23Reza Hedayat (Newracom)
September 2016
Slide24Straw-poll MAC-CR9 Do you agree to add to the 11ax specification D0.4 the comment resolutions in document 16/1157r0 for CIDs: 129, 130, 131, 132, 405, 406, 407, 408, 672 Results:Strawpoll passed with no objection
Slide 24Reza Hedayat (Newracom)
September 2016
Slide25Straw-poll MAC-CR10 Do you agree to add to the 11ax specification D0.1 the comment resolutions in document 16/1184r1 for CIDs: 2258, 2446, 1588, 1645 Results: Y/N/AStrawpoll passed with no objection
Slide 25Reza Hedayat (Newracom)
September 2016
Slide26Straw-poll MAC-CR-X Do you agree to add to the 11ax specification D0.1 the comment resolutions in document 16/XXXr1 for CIDs: … Results: Y/N/A
Slide 26Reza Hedayat (Newracom)
September 2016
Slide27Straw-poll MAC-X Do you agree to add to the 11ax specification D0.4 the comment resolutions in document 16/xyzr2 for CIDs: … Results:YNA
Slide 27Reza Hedayat (Newracom)
September 2016
Slide28Ad Hoc Groups Operation (1/2)Governing document is 15/075r0Proposed changes to the specification framework shall be discussed in the ad hoc groups first, which are then brought to the Taskgroup for an approval vote.A straw poll (doesn’t require voting rights) result of >=75% is required within an Ad Hoc to approve the resolution of all or part of an issue and forward that resolved item to the Taskgroup where it becomes a motion that requires >=75% approval to modify the specification framework or the draft specification. The straw poll affection the TG specification framework shall include Do you agree to add to the TG Specification Framework:x.y.z. [brief description of the feature]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 Taskgroup if an Ad Hoc straw poll vote to move the subject to the Taskgroup achieves >50% approval.
Slide 28Reza Hedayat (Newracom)
September 2016
Slide29Ad Hoc Groups Operation (2/2)Governing document is 15/075r0A motion passing with >50% in the Taskgroup shall be sufficient to move an issue previously assigned to an Ad Hoc group to any Ad Hoc group. A straw poll vote of >50% is required in an Ad Hoc group to refuse an issue from the Taskgroup.An issue may be sent from one Ad Hoc to another if both the sending Ad Hoc and the receiving Ad Hoc approve straw polls for taking the respective actions with >50% approval. A notice should be sent to the reflector indicating the approval of a straw poll to move an issue.During Taskgroup face to face Plenary and Interim sessions, Chairs for each of the Functional Block Ad Hocs shall report on Progress and Content to the Entire Taskgroup. These Update sessions provide the opportunity for peer review to ensure the creation of a coherent Specification.
Slide 29Reza Hedayat (Newracom)
September 2016
Slide30Slide 30
Backup SlidesReza Hedayat (Newracom)
September 2016
Slide31Slide 31
Strawpoll MAC 1-1: Premotioncontribution-file-nameDo you agree to add the TGax SFD: ABCY: N: Abstain: Reza Hedayat (Newracom)
September 2016
Slide32Slide 32
Approval of MAC Ad Hoc MinutesApprove TGax MAC ad hoc minutes of meetings and teleconferences from the July 2015 meeting until today: <Doc reference>Mover: Seconder:Y: N: Abstain: Reza Hedayat (Newracom)
September 2016
Slide33Slide 33
Strawpoll xxxx (“Testing the temperature of the room”)Do you … xxxxY: N: Abstain: Reza Hedayat (Newracom)
September 2016
Slide34Slide 34
Strawpoll xxxx (“Premotion”)Do you agree to add to the TG Specification Frame work document?x.y.z. <feature description>Y: N: Abstain: Reza Hedayat (Newracom)
September 2016