doc.: IEEE 802.11-20/1468r3 · Web view2017/09/14 · Telecon Minutes for REVmd CRC - Sept 14-17 2020 Date: 2020-11-17 Author(s): Name Affiliation Address Phone email Jon Rosdahl

doc.: IEEE 802.11-20/1468r3

September 2020doc.: IEEE 802.11-20/1468r3

IEEE P802.11Wireless LANs

Telecon Minutes for REVmd CRC - Sept 14-17 2020

Date: 2020-11-17

Author(s):

Name

Affiliation

Address

Phone

email

Jon Rosdahl

Qualcomm Technology, Inc.

10871 N. 5750 W.

Highland, UT 84003

+1-801-492-4023

Jrosdahl @ ieee.org

Abstract

This file contains the minutes for the 802.11md REVmd CRC Telecons from September 14 to September 17, 2020.

R0: Sept 14, 2020 Telecon Minutes

R1: Sept 15, 2020 Telecon Minutes added minor corrections made to Sept 14 minutes.

R2: Sept 16, 2020 Telecon Minutes added...

R3: Sept 17, 2020 Telecon Minutes Added.

1.0 IEEE 802.11md REVmd CRC Telecon Monday, September 14, 2020 11:15-13:15 ET

1.1 Called to order at 11:16 am ET by the TG Chair Dorothy STANLEY (HPE)

1.2 Review Patent and Participation Policy

1.2.1 No Issues noted.

1.3 Attendance: -please log with IMAT:

1.3.1 See References for the IMAT report (Attendance Sept 14)

1.3.2 About 80 attendees reported by Webex

1.3.3 Missing from IMAT: None reported

1.4 Review Agenda 11-20/1366r2:

1.4.1 https://mentor.ieee.org/802.11/dcn/20/11-20-1366-02-000m-2020-september-interim-tgmd-agenda.pptx

1.4.2 The draft agenda for the teleconferences is below:

1. Call to order, attendance (https://imat.ieee.org/attendance ), and patent policy

a. Patent Policy: Ways to inform IEEE:

i. Cause an LOA to be submitted to the IEEE-SA ([email protected]); or

ii. Provide the chair of this group with the identity of the holder(s) of any and all such claims as soon as possible; or

iii. Speak up now and respond to this 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, please respond at this time by providing relevant information to the WG Chair

b. Patent, Participation and policy related slides: See slides 4-19 in https://mentor.ieee.org/802.11/dcn/20/11-20-0323-00-0000-2nd-vice-chair-report-july-2020.pptx

2. Editor report – Emily QI/Edward AU – see https://mentor.ieee.org/802.11/dcn/17/11-17-0920-28-000m-802-11revmd-editor-s-report.ppt and https://mentor.ieee.org/802.11/dcn/19/11-19-2156 .

3. Comment resolution and motions for the week.

· Monday AM2

· Chair’s Welcome, Policy & patent reminder, Approve agenda

· Status, Review of Objectives, Editor Report 11-17-0920

· Emily Qi – CIDs 5002

· Jon ROSDAHL: CIDs 5081, 5079, 5022, 5007

· Michael Montemurro – CID 5076

· Mark Hamilton ARC Liaison – 11-20-0177

· Srini KANDALA – CID 5025

· Youhan Kim – CIDs 5009, 5010, 5011

· Tuesday PM2

· Mark RISON –5056 (4602), 5058 & 5061 (4699), 5040 (4205), [5048 (4229, 4226), 5047 & 5046, 5049, 5050, 5051]

· David GOODALL CID 5017 in 11-20-1433, also CIDs 5018, 5016


· C. Ghosh – CID 5008


· Wednesday PM2

· Motions

· M. Montemurro, A. Myles CID 5001

· Youhan Kim – CIDs 5009, 5010, 5011

· Jouni Malinen – CIDs 5071, 5073, 5074, 5075, 5062

· Mark Rison Assigned CIDs 5038, 5042, 5043, 5063, 5066, 5068, 5078

· Thursday PM2

· Comment resolution

· Motions

· Plans for September – December 2020

· Adjourn

4. AOB

5. Adjourn

1.4.3 Emily noted that CID 5033 was completed last Friday.

1.4.4 Update agenda according to availability

1.4.5 Move to approve agenda R3

1.4.5.1 Moved: Jon Rosdahl 2nd: Emily QI

1.4.5.2 No discussion

1.4.5.3 No objection to the displayed Agenda (see 11-20/1366r3)

1.4.5.3.1

1.5 Status and Objectives:

1.5.1 We are in Recirc process for D4.0

1.5.2 Current planned Schedule:

· January 2018 – Initial WGLB

· November 2018 –D2.0 WGLB Recirculation LB

· May 2019 – MEC/MDR done

· September 2019 – D3.0 WGLB Recirculation LB

· September 2019 – Form SB Pool – Closes 2019-10-11

· November 2019 – D3.0 Recirculation (unchanged)

· December 2019 – Initial SB D3.0

· August 2020– Recirculation SB D4.0

· October 2020 – WG/EC approval

· December 2020 – RevCom/SASB approval

1.6 Editor Report Emily QI (Intel)

1.6.1 Report 11-17-0920

1.6.2 Review 11-19/2156r22

1.6.2.1 https://mentor.ieee.org/802.11/dcn/19/11-19-2156-22-000m-revmd-sponsor-ballot-comments.xls

1.6.3 Current status:

1.7 Review doc 11-20/1413r4 – Emily QI (Intel)

1.7.1 https://mentor.ieee.org/802.11/dcn/20/11-20-1413-04-000m-sa2-proposed-resolutions-for-editor-adhoc-and-others.doc

1.7.2 CID 5002 (EDITOR)

1.7.2.1 Review the comment and the history of the proposed changes.

1.7.2.2 Discussion on the proposed change and the Note related to the figure.

1.7.2.3 Corrections of the note from an “and” to an “or”

1.7.2.4 The change in 3239.37 needed to have a change earlier in the text changes. (see R5 for final version). Also an “NF” should be “MF”

1.7.2.5 Discussion on change 3242.10 – There is a reference else where so the deletion is correct and sufficient.

1.7.2.6 A revision will be loaded

1.7.3 Proposed resolution: CID 5002 (EDITOR): Revised. Incorporate the changes in 11-1413r5 for CID 5002.

1.7.3.1 No Objection – Mark Ready for Motion

1.8 GEN CIDS – Jon Rosdahl (Qualcomm)

1.8.1 CID 5079 (GEN):

1.8.1.1 Reviewed what is being changed. Sentence clean-up for clarification.

1.8.1.2 Proposed Resolution: ACCEPTED (GEN: 2020-09-14 15:54:42Z).

1.8.1.3 No objection - Mark Ready for motion.

1.8.2 CID 5081 (GEN):

1.8.2.1 Review comment

1.8.2.2 Proposed Resolution: Rejected. The draft under consideration is D4.0. D7.0 is TGax, and not part of this ballot. The comment fails to identify changes in sufficient detail so that the specific wording of the changes that will satisfy the commenter can be determined.

1.8.2.3 After more discussion, remove the TGax reference.

1.8.2.4 Updated Proposed Resolution: REJECTED (GEN: 2020-09-14 15:48:08Z) The draft under consideration is D4.0. The comment fails to identify changes in sufficient detail so that the specific wording of the changes that will satisfy the commenter can be determined.1.4.Ready for motion.

1.8.2.5 No Objection - Mark Ready for motion.

1.8.3 CID 5022 (GEN):

1.8.3.1 Review Comment

1.8.3.2 Proposed Resolution: REJECTED (GEN: 2020-09-14 15:56:46Z) The comment does not identify a specific technical problem. The comment fails to identify changes in sufficient detail so that the specific wording of the changes that will satisfy the commenter can be determined.


1.8.4 CID 5007 (GEN):


1.8.4.2 Proposed Resolution: REJECTED (GEN: 2020-09-11 16:35:29Z) Commenter withdrew comment.


1.9 PHY CIDs – Michael MONTEMURRO (Self)

1.9.1 CID 5076 (PHY)


1.9.1.2 Made a related change with CID 2391

1.9.1.3 This comment is consistent with those prior changes. (In both locations)

1.9.1.4 Discussion on the proposed change of plural to singular “Antenna Connector”. The power level is properly noted to be measured at the antenna connector.

1.9.1.4.1 antenna connector: The measurement point of reference for radio frequency (RF) measurements in astation (STA).

1.9.1.4.2 In systems using multiple antennas or antenna arrays, the antenna connector is avirtual point representing the aggregate output of (or input to) the multiple antennas. In systems using activeantenna arrays with processing, the antenna connector is the output of the active array, which includes anyprocessing gain of the active antenna subsystem.

1.9.1.5 Proposed resolution: Accepted

1.9.1.6 No objection – Mark Ready for Motion

1.10 Review doc 11-20/0177r2 – Mark HAMILTON (Ruckus/CommScope)

1.10.1 https://mentor.ieee.org/802.11/dcn/20/11-20-0177-02-0arc-liaison-to-revmd-on-ess.docx

1.10.2 Abstract: This is a liaison from 802.11’s ARC SC to 802.11’s REVmd, with proposals for modification of Draft Standard text on the definition and introductory discussion of the concepts “ESS” and “HESS”.

1.10.3 Presentation of the submission.

1.10.4 Discussion on the use of “Location transparency”.

1.10.5 Discussion on if LLC is sublayer or layer. Delete phrase “the same to an LLC layer as an IBSS” to make the sentence clear.

1.10.6 Discussion on getting rid of “homogeneous”, also homogamous.

1.10.7 Discussion on the meaning name for HeSS. – could a better name be found.

1.10.8 No CID covers this issue, so we need to decide if we are going to include now, or wait until 11me.

1.10.9 There may be more issues to resolve in Clause 4.

1.10.10 Concern with the global change instructions and need to have the specific changes included in the proposal

1.10.11 Discussion on if the HESSID is truly globally unique identifier.

1.10.12 Suggestion to push these changes to REVme.

1.10.13 There has been a lot of effort on this already. The ARC SC has spent a lot of time to create this text and should be considered in this round.

1.10.14 A Revision of the submission will be prepared and come back to the group.

1.11 Review doc 11-20/1313r5 Srini KANDALA (Samsung)

1.11.1 https://mentor.ieee.org/802.11/dcn/20/11-20-1313-05-000m-bss-max-idle-period-negotiation-enhancements-for-non-s1g-phys.docx

1.11.2 There is an R6 on Mentor, but the discussion is on R5 and depending on the discussion, may want to use R6

1.11.2.1 https://mentor.ieee.org/802.11/dcn/20/11-20-1313-06-000m-bss-max-idle-period-negotiation-enhancements-for-non-s1g-phys.docx

1.11.3 Review submission R5 as there are more people than usual on the call.

1.11.4 This submission is for CID 5025 (PHY)

1.11.5 Discussion on the value that may be requested. What is the incentive to choose a larger or smaller value?

1.11.6 Discussion on capability indication is not needed (which is in R6).

1.11.7 Discussion on a SAP argument and a MIB variable gives 2 different access points. If we have a MIB variable, why do we need the primitive?

1.11.8 More discussion on wanting to move to R6 (which does not have a capability bit).

1.11.9 Discussion on if the baseline seemed to have the same type description. If the MIB variable is set true, and the SAP parameter is set.

1.11.10 Seems that the current SAP/MIB were put in by 11ah, and may not be correct, but it is in the draft.

1.11.11 If all variables are true, then the “may” should be a “shall” have dot11BSSMaxIdlePeriodIndicationbyNonAPSTA be present.

1.11.12 Plan to proceed with editorial and other changes to R6 and bring back later.

1.11.13 If we do not come to consensus, we will reject the comment.

1.12 Review CIDS 5009, 5010, 5011 – Youhan KIM (Qualcomm)

1.12.1 Essentially the 3 CIDs are on the same topic.

1.12.2 CID 5009, 5010, 5011 (PHY)


1.12.2.2 Review the context of the comment

1.12.2.3 The cited rows have not changed during the 11md process, so we are not obligated to action these CIDs.

1.12.2.4 Need to check if there is a real technical issue, if not, we can reject.

1.12.2.5 Put on the agenda for the first part of Wednesday.

1.13 Review CID assignment

1.13.1 CIDs assigned to DAN CID 5071, 5073, 5074, 5075

1.13.1.1 Reassign to Jouni MALINEN

1.13.1.2 Add to Wednesday Agenda

1.13.2 Review that all assignees are on the Agenda to resolve assigned CIDs.

1.14 Recess 1:16pm

2.0 IEEE 802.11md REVmd CRC Telecon Tuesday, September 15, 2020 16:00-18:00 ET

2.1 Called to order at 4:02 pm ET by the TG Chair Dorothy STANLEY (HPE)

2.

2.1





2.3.2 About 80 attendees reported by Webex




2.4.2 Tuesday PM2

· Mark RISON –5056 (4602), 5058 & 5061 (4699), 5040 (4205), [5048 (4229, 4226), 5047 & 5046, 5049, 5050, 5051]

· David GOODALL CID 5017 in 11-20-1433, also CIDs 5018, 5016


· C. Ghosh – CID 5008


2.4.3 Review agenda plan

2.4.4 Jouni requested that Move CID 5065 to Mark RISON

2.4.5 Request to postpone time of Srini’s submission, but we will still review it today and tomorrow.

2.4.6 No objection to the agenda displayed – see 11-1366r4

2.5 Review doc 11-20/0435r15 – Mark RISON (Samsung)

2.5.1 https://mentor.ieee.org/802.11/dcn/20/11-20-0435-15-000m-resolutions-for-some-comments-on-11md-d3-0-sb1.docx

2.5.2 Mark RISON –5056 (4602), 5058 & 5061 (4699), 5040 (4205), [5048 (4229, 4226), 5047 & 5046, 5049, 5050, 5051]

2.5.3 CID 5056 (GEN) (nee 4602)


2.5.3.2 Review the proposed changes.

2.5.3.3 No objection to changes.

2.5.3.4 Proposed resolution: Incorporate the changes for CID 5056 in 11-10/0435r15, which makes the sessions key name clear.


2.5.4 CID 5040 (PHY) (nee 4205)


2.5.4.2 Review proposed changes.

2.5.4.3 Discussion on the instructions.

2.5.4.4 Concern on having a “NOTE” in the table.

2.5.4.5 May be better to add between NOTE 3 and NOTE 4 at 1109.26

2.5.4.6 Proposed resolution: REVISED (PHY: 2020-09-15 20:22:24Z) - In Table 9-151—AKM suite selectors:

For the 00-0F-AC:11 row:

Change "Authentication negotiated over IEEE Std 802.1X"

to "Authentication negotiated over IEEE Std 802.1X using a Suite B compliant EAP method supporting SHA-256".

At 1109.26 add “NOTE 4—The AKM suite selector value 00-0F-AC:11 is deprecated.” and renumber the subsequent NOTEs.

For the 00-0F-AC:12 row:

Change "Authentication negotiated over IEEE Std 802.1X"

to "Authentication negotiated over IEEE Std 802.1X using a CNSA Suite compliant EAP method"

(For the 00-0F-AC:13 row, no change.)

2.5.4.7 No objection - Mark Ready for Motion

2.5.5 CID 5058 and 5061

2.5.5.1 Not ready to discuss

2.5.6 CID 5048 (4229, 4226), 5047 & 5046, 5049, 5050, 5051 (4229)

2.5.6.1 Not in document

2.5.7 CID 5062 (MAC)


2.5.7.2 Review proposed changes

2.5.7.3 No objection

2.5.7.4 Proposed Resolution: CID 5062 (MAC): REVISED (MAC: 2020-09-15 20:24:40Z): In 9.4.2.246 Rejected Groups element change:

The Rejected Groups field contains a (#4658)list of unsigned 16-bit integers representing finite cyclic groups that have been rejected by a peer in a previous authentication attempt.

to:

The Rejected Groups field contains a (#4658)list of Finite Cyclic Group fields indicating finite cyclic groups that have been rejected by a peer in a previous authentication attempt.

Note to the commenter: the new text is the Proposed Change.

2.5.7.5 No Objection – Mark ready for motion

2.5.8 CID 5048 (GEN) (Follow-up to CID 4229/4266)



2.5.8.3 Discussion on the definition of the Basic Rate Set.

2.5.8.4 Discussion on how the basic rate set is set when the AP first starts up establishing the BSS and it does not change.

2.5.8.5 Discussion on the need for a definition for the “Basic Rate Set”.

2.5.8.6 STRAW POLL S1:

2.5.8.6.1 Resolve 5048 as “Accepted”

2.5.8.6.2 Yes/No/Abstain

2.5.8.6.3 Result: 6/10/10

2.5.8.7 Proposed Resolution: Reject – No consensus to make the change

2.5.8.8 Proposed Resolution: REJECTED (GEN: 2020-09-15 20:48:21Z) The TG considered document https://mentor.ieee.org/802.11/dcn/20/11-20-0435-15-000m-resolutions-for-some-comments-on-11md-d3-0-sb1.docx to address the comment and did not come to a consensus to adopt the proposed changes. A Strawpoll to accept the change had a result of 6 yes - 10 no and 10 abstain.

2.5.9 CID 5049 and 5050 (MAC)

2.5.9.1 The comments are the same, but the proposed change is different.

2.5.9.2 Review of Comments

2.5.9.3 Discussion on the STA Type

2.5.9.4 Discussion on the location of the change

2.5.9.5 Proposed resolution: CID 5049 (MAC): REVISED (MAC: 2020-09-15 20:56:29Z) - At 1716.6 change the NOTE to:

"NOTE—The operational rate or MCS set that a STA advertises does not necessarily contain all the mandatory rates or MCSs, respectively. The basic rate or MCS set that a STA starting a BSS advertises does not necessarily contain all the mandatory rates or MCSs, respectively. However, a STA has to be capable of receiving using a mandatory rate or MCS (when required by the rules in 10.6 (Multirate support)) even if it is not present in the operational rate or MCS set, respectively, that the STA advertises, and similarly has to be capable of transmitting using a mandatory rate or MCS (when required by the rules in 10.6 (Multirate support)) even if it is not present in the basic rate or MCS set, respectively. In this context, “mandatory” describes rates or MCSs that are so described, or described using “shall support”, in reference to the STA type, in the PHY clause applicable to the STA.".

Delete NOTE 1 in 11.1.4.6 Operation of Supported Rates and BSS Membership Selectors element and Extended Supported Rates and BSS Membership Selectors element and renumber the following NOTEs.

2.5.9.6 Proposed Resolution: CID 5050 (MAC): REVISED (MAC: 2020-09-15 20:56:29Z) - At 1716.6 change the NOTE to:

"NOTE—The operational rate or MCS set that a STA advertises does not necessarily contain all the mandatory rates or MCSs, respectively. The basic rate or MCS set that a STA starting a BSS advertises does not necessarily contain all the mandatory rates or MCSs, respectively. However, a STA has to be capable of receiving using a mandatory rate or MCS (when required by the rules in 10.6 (Multirate support)) even if it is not present in the operational rate or MCS set, respectively, that the STA advertises, and similarly has to be capable of transmitting using a mandatory rate or MCS (when required by the rules in 10.6 (Multirate support)) even if it is not present in the basic rate or MCS set, respectively. In this context, “mandatory” describes rates or MCSs that are so described, or described using “shall support”, in reference to the STA type, in the PHY clause applicable to the STA.".

Delete NOTE 1 in 11.1.4.6 Operation of Supported Rates and BSS Membership Selectors element and Extended Supported Rates and BSS Membership Selectors element and renumber the following NOTEs.

2.5.9.7 No objection – Mark Both CIDs Ready for Motion

2.5.10 CID 5051 (MAC)



2.5.10.3 Proposed Resolution: CID 5051 (MAC): ACCEPTED (MAC: 2020-09-15 20:58:46Z)


2.5.11 CID 5047 (GEN)

2.5.11.1 Pending discussion with Sean

2.5.12 CID 5046 (GEN) (follow-up to CID 4229)

2.5.12.1 Review comment.


2.5.12.3 Discussion on support of the changes.

2.5.12.4 Proposed Resolution: ACCEPTED (GEN: 2020-09-15 21:03:10Z)

2.5.12.5 No Objection – Mark Ready for Motion

2.6 Review doc 11-20/1433 – David GOODALL (Morse Micro)

2.6.1 https://mentor.ieee.org/802.11/dcn/20/11-20-1433-03-000m-s1g-mac-resolution-to-cid5017.docx

2.6.2 CID 5017 (MAC)

2.6.2.1 Review comment and history of changes since last presented.

2.6.2.2 Review the proposed changes.

2.6.2.3 No objection to the proposed changes in 11-20/1433r3.

2.6.2.4 Proposed Resolution: CID 5017 (MAC): REVISED (MAC: 2020-09-15 21:07:57Z): Incorporate the changes in 11-20/1433r3 for CID 5017, which corrects the discussion of the duration for these frames.


2.7 Review doc 11-20/1454r1– David GOODALL (Morse Micro)

2.7.1 https://mentor.ieee.org/802.11/dcn/20/11-20-1454-01-000m-s1g-gen-resolution-to-cid5018.docx

2.7.2 CID 5018 (GEN)


2.7.2.2 Background: Table D-4 (Maximum STA transmit power and maximum BW allowed) is out of date due to recent changes in various regulatory domains, including China and Europe. Also, the name of the table should be made specific to sub 1 GHz.

2.7.2.3 Proposed resolution: REVISED (GEN: 2020-09-15 21:12:42Z); Incorporate the changes for CID 5018 in doc 11-20/1454r2 which updates Table D-4 as noted in the comment.

2.7.2.4 No objection – Mark Ready for Motion.

2.8 Review doc 11-20/1471r0 - David GOODALL (Morse Micro)


2.8.2 CID 5016 (GEN)


2.8.2.2 Review proposed change.

2.8.2.3 Request to have a review of the test vectors in the draft.

2.8.2.4 Discussion on the variables are entered in the text.

2.8.2.5 Question on the representation of the vectors. Would be best to find the original author to verify the vectors in the document.

2.8.2.6 ACTION ITEM: Ask for review and present again for resolution of CID on Thursday.

2.9 Review doc 11-20/13113r8 – Srini KANDALA (Samsung)


2.9.2 CID 5025 (PHY)

2.9.2.1 Review changes since last review.

2.9.2.2 Many changes have been requested offline.

2.9.2.3 Would like a straw-poll to determine if we have consensus for the proposed requested changes.

2.9.2.4 Discussion on why the Extended Capability bits needs to be added or not.

2.9.2.5 Will take up the discussion again tomorrow (Wednesday).

2.10 Review doc 11-20/0177r4 – Mark HAMILTON (Ruckus/Commscope)

2.10.1 https://mentor.ieee.org/802.11/dcn/20/11-20-0177-04-0arc-liaison-to-revmd-on-ess.docx

2.10.2 Two revisions were made since presentation yesterday to address requests.

2.10.3 Review contribution changes and the effective proposed changes.

2.10.4 Discussion on the changes proposed could be taken in parts.

2.10.5 Support for the changes in whole was expressed due to the fact that 802.11 ARC spent a lot of time making the proposed changes including the HESS ID.

2.10.6 For those that wanted a little more time, the discussion was stopped and will be on the agenda for Thursday.

2.11 Review doc 11-20/1104r3 Chittabrata Ghosh (Intel Corporation)

2.11.1 https://mentor.ieee.org/802.11/dcn/20/11-20-1104-03-000m-proposed-changes-in-scs-10-23-2-2-and-10-23-2-9.docx

2.11.2 CID 5008 (MAC)

2.11.2.1 Review the changes since last presented.


2.11.2.3 Discussion on which rules need to apply to which cases.

2.11.2.4 Discussion on the rationale for making any changes.

2.11.2.5 Discussion on why we need two separate lists of requirements.

2.11.2.6 Discussion on why the changes were made.

2.11.2.7 More work is needed.

2.11.2.8 Either Tomorrow or Thursday, we will have a motion and if it passes or not we will make a final determination.

2.12 Review Agenda plan:

2.12.1 Review 11-20/1366r4:

2.12.1.1 https://mentor.ieee.org/802.11/dcn/20/11-20-1366-04-000m-2020-september-interim-tgmd-agenda.pptx

2.12.2 Reminder of CID list for Mark RISON:

2.12.2.1 Mark Rison Assigned CIDs 5058 & 5061 (4699), 5047, 5038, 5042, 5043, 5063, 5066, 5068, 5078

2.13 Recessed 6:00pm ET.

3.0 IEEE 802.11md REVmd CRC Telecon Wednesday, September 16, 2020 16:00-18:00 ET


3.

3.1





3.3.2 About 58 attendees reported by Webex/IMAT




3.4.2 Wednesday PM2

· Motions

· M. MONTEMURRO, A. MYLES CID 5001

· Youhan KIM – CIDs 5009, 5010, 5011

· Jouni MALINEN – CIDs 5071, 5073, 5074, 5075

· Mark RISON Assigned CIDs 5058 & 5061 (4699), 5047, 5038, 5042, 5043, 5063, 5066, 5068, 5078


3.4.3 Add Chitta to Thursday’s agenda

3.4.4 No other changes to today’s agenda plan – see 11-20/1366r5.

3.5 Motions:

3.5.1 Motion S1: Approve prior TGmd minutes

3.5.1.1 Approve the minutes of

· Teleconference minutes:

· August 3-7: https://mentor.ieee.org/802.11/dcn/20/11-20-1183-04-000m-telecon-minutes-for-revmd-crc-aug-3-7-2020.docx

· August 19: https://mentor.ieee.org/802.11/dcn/20/11-20-1251-00-000m-telecon-minutes-for-revmd-crc-aug-19-2020.docx

· August 21-26: https://mentor.ieee.org/802.11/dcn/20/11-20-1325-01-000m-telecon-minutes-for-revmd-crc-aug-21-and-aug-26-2020.docx

· September 2-4: https://mentor.ieee.org/802.11/dcn/20/11-20-1390-01-000m-telecon-minutes-for-revmd-crc-sept-2-and-sept-4-2020.docx

· September 8-9-11: https://mentor.ieee.org/802.11/dcn/20/11-20-1432-03-000m-telecon-minutes-for-revmd-crc-sept-8-9-and-10-2020.docx

3.5.1.2 Moved: Jon ROSDAHL

3.5.1.3 Seconded: Emily QI

3.5.1.4 Result S1: Approved by Unanimous Consent – motion Passes.

3.5.2 Motion S2: Re-affirm TGmd officers

3.5.2.1 Reaffirm the following TG officers:

Mark HAMILTON and Michael MONTEMURRO as TGmd Vice Chairs

and Jon ROSDAHL as TGmd secretary.

3.5.2.2 Moved: Edward AU

3.5.2.3 Seconded: Joseph LEVY

3.5.2.4 Result S2: Approved by Unanimous consent (38 on the call (24 voters)

3.5.3 Motion #253 - EDITOR (5+6+1) and EDITOR2 (12) CIDs

3.5.3.1 Approve the comment resolutions in the

“Motion-EDITOR-A”, “Motion-EDITOR-B” and “Motion-EDITOR-C” tabs in https://mentor.ieee.org/802.11/dcn/20/11-20-1412-02-000m-revmd-sa2-comments-for-editor-ad-hoc.xlsx

Motion-EDITOR2-V tab in https://mentor.ieee.org/802.11/dcn/19/11-19-2160-15-000m-revmd-editor2-standards-association-ballot-comments.xlsx

and incorporate the text changes into the TGmd draft.

3.5.3.2 Moved: Stephen PALM

3.5.3.3 Seconded: Edward AU

3.5.3.4 Result Motion #253: Approved with Unanimous Consent – Motion Passes

3.5.4 Motion #254 – GEN (7+4) CIDs


“Motion GEN -Sept A” and “Motion GEN –Sept B” tabs in 11-20/1438r3 < https://mentor.ieee.org/802.11/dcn/20/11-20-1438-03-000m-sa-ballot-recirc-1-revmd-gen-comments.xls >



3.5.4.3 Seconded: Michael MONTEMURRO


3.5.5 Motion #255 – MAC (6) CIDs


“Motion MAC-AU” tabs in https://mentor.ieee.org/802.11/dcn/17/11-17-0927-65-000m-revmd-mac-comments.xls


3.5.5.2 Moved: Michael MONTEMURRO

3.5.5.3 Seconded: Stephen PALM


3.6 Review 11-20/227r4 CID 5001 (PHY) – Andrew MYLES (Cisco)

3.6.1 https://mentor.ieee.org/802.11/dcn/20/11-20-0227-04-000m-pifs-for-beacons.pptx

3.6.2 CID 5001 (PHY):

3.6.2.1 Review history of the comment

3.6.2.2 Rejected in last ballot, new comment to reconsider.

3.6.2.3 Discussion on if the comment in the last ballot was appropriately considered.

3.6.2.4 Discussion on the use of Beacons using AC_V) with AIFSN of 1.

3.6.2.5 From Aug 5th Telecon Minutes – 3.10.2.7:

Proposed Resolution: REVISED (GEN: 2020-08-05 21:43:54Z) – at 1730.30 add

"–A STA transmitting a Beacon frame, as described in 11.1.3.2 (Beacon generation in non-DMG infrastructure networks).

NOTE–An extended period during which the medium is busy after the TBTT can increase the probability for collisions between PIFS transmissions from nearby STAs on the same channel. The use of a random backoff instead of PIFS can reduce the collision probability in this case."

Note to the Commenter:

This change allows beacons to be transmitted at PIFS.

It is possible that clock drift causes TBTTs at two nearby APs to line up within 9 us and that a beacon collision occurs. However, the time this happens would only be 0.009% for a 100 ms beacon period. This fraction may be increased some by CCA busy events occurring around the TBTT, but the odds will still be low.

A medium busy time after the TBTT of for example 1 ms will increase this collision probability to 1%.

Matthew FISCHER suggested: A medium busy time after the TBTT of for example 5 ms will increase this collision probability to 5%.

3.6.2.6 STRAW POLL S2: Modify the Text to explicitly allow Beacon Frames Using PIFS.

3.6.2.6.1 YES/NO/Abstain

3.6.2.6.2 Results: 14-8-4

3.6.2.7 If this were a motion it would not pass.

3.6.2.8 ACTION: Mike to prepare Accept and Reject motions for this CID.

3.6.2.9 Two resolutions to be prepared for Thursday. One will reject and one will be a revised.

3.6.2.10 Proposed Resolutions: CID 5001 (PHY)

3.6.2.10.1 Reject Proposal: Reject;

- the comment was discussed.

1) Makes a major change to the requirements that are already specified.

2) Making the change would introduce unfairness.

3) There was no consensus for making a change.

4) AP's should not use PIFS for transmitting beacons. In the industry, it’s a valid mechanism for transmitting beacons.

5) In the commenter's opinion, AP's that use PIFS are not compliant with the specification. There is no clear statement that AP's shall not transmit beacons on PIFS.

3.6.2.10.2 Proposed change under discussion in 11-20/1183r4:

At 1730.30 add

"–A STA transmitting a Beacon frame, as described in 11.1.3.2 (Beacon generation in non-DMG infrastructure networks).


3.7 Review doc 11-20/1475r0 - CID 5009, 5010, 5011 (PHY) - Youhan KIM: (QUALCOMM)

3.7.1 https://mentor.ieee.org/802.11/dcn/20/11-20-1475-00-000m-sa2-cids-5009-5010-5011.docx

3.7.2 CID 5009, 5010, 5011 (PHY)

3.7.2.1 Review Comments


3.7.2.3 Discussion on the changes.

3.7.2.4 Discussion on the coverage of the clause 19 and 20 Mhz.

3.7.2.5 Proposed Resolution: Revised; REVISED (PHY: 2020-09-16 20:47:30Z)

Implement the proposed text changes under "Proposed Text Updates for CIDs 5009, 5010, 5011" in https://mentor.ieee.org/802.11/dcn/20/11-20-1475-00-000m-sa2-cids-5009-5010-5011.docx, so that the text states directly that start of PPDUs needed to be detected regardless of the PPDU bandwidth if the power measured within the primary 20 MHz is at or above -82 dBm.

Note to Commenter:

The main point the commenter is making is that a STA in a X1 MHz operating mode needs to be able to detect the start of PPDUs with X2 MHz bandwidth, including cases where X2 > X1. For example, a STA in 80 MHz operating mode needs to be able to detect the start of a 160 MHz PPDU and defer appropriately, even though the 80 MHz operating STA will not be able to demodulate the data portion of the 160 MHz PPDU. And Table 21-27 does not capture this point.

Furthermore, Table 21-27 as currently written is not easy to understand. For example, does the row “The start of a 160 MHz or 80+80 MHz non-HT duplicate or VHT PPDU at or above –73 dBm.” mean that a VHT receiver must measure the preamble power over 160 MHz, and run the preamble detector over 160 MHz? The intention of that row was that even for 160 MHz PPDUs, if you see energy in the primary 20 MHz greater than or equal to -82 dBm (the requirement for 20 MHz VHT PPDU detection), then you need to detect those 160 MHz PPDUs as well. And assuming flat power spectral density, -82 dBm in primary 20 MHz translates to -73 dBm over 160 MHz – hence the limit of -73 dBm in the last row of Table 21-27.


3.8 Review doc 11-1493r0 – CID 5071, 5073, 5074, and 5075- Jouni MALINEN (Qualcomm)

3.8.1 https://mentor.ieee.org/802.11/dcn/20/11-20-1493-00-000m-some-sa2-sae-comments.docx

3.8.2 CID 5071 (PHY) (nee 4671)



3.8.2.3 Question if there was similar Comment? Not overlapping.

3.8.2.4 No objection to the change.

3.8.2.5 Proposed Resolution: ACCEPTED (PHY: 2020-09-16 20:50:29Z)


3.8.3 CID 5073 (PHY)



3.8.3.3 Review discussion in the submission.

3.8.3.4 Proposed resolution: REJECTED. Modular multiplication and division are operations in the SSWU algorithm and as such, are already covered by practically identical requirement on line 63.

3.8.3.5 Discussion on the need to indicate “constant time operation” and if it is sufficiently defined or not.

3.8.3.6 STRAW POLL S3: Reject CID 5073 with the reason proposed in 11-20/1493r0:

3.8.3.6.1 YES/NO/Abstain

3.8.3.6.2 Results: 14-2-8

3.8.3.7 Proceed with the reject resolution.

3.8.3.8 Updated Resolution: REJECTED (PHY: 2020-09-16 21:01:54Z) - Modular multiplication and division are operations in the SSWU algorithm and as such, are already covered by practically identical requirement on line 63.

3.8.3.9 Mark Ready for Motion.

3.8.4 CID 5074 (PHY)




3.8.4.4 Discussion on the need for constant time operations and if it is defined sufficiently or not...

3.8.4.5 Proposed resolution: REJECTED (PHY: 2020-09-16 21:10:20Z). Determination of quadratic residue on page 2561 line 58 is one of the operations in the SSWU algorithm and as such, is already covered by practically identical requirement on line 63.

3.8.4.6 The next CID is similar

3.8.5 CID 5075 (PHY)




3.8.5.4 Proposed Resolution: REJECTED (PHY: 2020-09-16 21:10:04Z) -. sqrt(x) is one of the operations in the SSWU algorithm and as such, is already covered by practically identical requirement on line 63. The NOTE following this algorithm description indicates how sqrt(x) is implemented. The condition in that note applies to all the applicable curves. As such, there is no need to define sqrt(x) in the SSWU algorithm itself as it is a common operation in modular arithmetic which the reader of this algorithm is expected to be familiar with and is implemented in the manner described immediately following this text.

3.8.5.5 Discussion on the sqrt(x) cannot be defined in the NOTE. It was pointed out that line 63 covers sqrt(x) also.

3.8.5.6 ACTION ITEM: Michael MONTEMURRO to prepare a separate Motion will be prepared for CID 5074 and 5075 with an option for reject and Accept.

3.8.5.7 Secretary Note – response on Action item:

3.8.5.7.1 With respect to tomorrow. The motion for Rejection will be Approve resolutions on the "SAE Constant Time" tab of 11-20/1425r2. The motion for approve will simply be "Resolve CID 5074 and CID 5075 as ACCEPTED".

3.9 Mark Rison Assigned CIDs 5058 & 5061 (4699), 5047, 5038, 5042, 5043, 5063, 5066, 5068, 5078


3.9.2 CID 5058 and 5061 (MAC) (nee 4699)


3.9.2.2 From Webex Chat Window:

3.9.2.2.1 The STA shall not initiate transmission of a frame unless the transmission and any acknowledgment orother immediate response expected from the peer MAC entity are able to complete prior to the end of thethe HCCA TXOP. All transmissions, including response frames, within the polled TXOP are considered to be the part of the TXOP

3.9.2.2.2 NOTE-The remaining TXOP duration is indicated in the NAV.

3.9.2.3 Discussion on completing prior to the TXOP. No Need to change the text.

3.9.2.4 The use of NAV would also need the TX NAV included in the resolution.

3.9.2.5 Discussion on the value of leaving the existing text.

3.9.2.6 There was insufficient support for a change.

3.9.2.7 ACTION ITEM: Mark HAMILTON to prepare CID 5058 and 5061 (MAC) rejection resolution for tomorrow.

3.9.3 CID 5038 (MAC)


3.9.3.2 Review discussion in submission.

3.9.3.3 Proposed resolution: CID 5038 (MAC): REVISED (MAC: 2020-09-16 21:25:20Z): Incorporate the text changes in 11-20/0435r16 for CID 5038, which clarifies when security is required.

3.9.3.4 Mark Ready for Motion

3.9.4 CID 5042 (MAC) (nee 4679)



3.9.4.3 Proposed change reviewed: Change “For example, receiver address matching is always performed on the contents of the Address 1 field in received frames, and the receiver address of CTS and Ack frames is always obtained from the Address 2 field in the corresponding RTS frame, or from the frame being acknowledged.” in 9.2.4.3.1 to “Specifically, the Address 1 field always identifies the intended receiver(s) of the frame, and the Address 2 field, where present, always identifies the transmitter of the frame.NOTE—The Address 2 field is not equal to the MAC address of the transmitter, in the case of a bandwidth signalling TA.”



3.9.5 CID 5043 (MAC) (nee 4689)



3.9.5.3 Proposed resolution: CID 5043 (MAC): ACCEPTED (MAC: 2020-09-16 21:34:45Z)


3.9.6 CID 5063 (MAC) (ne 4137)


3.9.6.2 Review context on page 784.

3.9.6.3 Discussion on the reserved fields being treated differently in MAC and PHY sections.

3.9.6.4 The Note would be added to Clause 9.

3.9.6.5 Discussion what the scope of the statement “Reserved Fields and subfields are set to 0 on transmission and ignored on reception.

3.9.6.6 Proposed resolution: At the end of the penultimate para in the referenced subclause add a "NOTE---Reserved fields and subfields in PHY headers might be set to different values upon transmission and might not be ignored upon reception."Change the penultimate para from "Reserved fields and subfields are set to 0 upon transmission and are ignored upon reception." to "Reserved fields and subfields defined in this clause are set to 0 upon transmission and are ignored upon reception."

3.9.6.7 Discussion on the wording caused a change.

3.9.6.8 Updated proposed resolution: CID 5063 (MAC): REVISED (MAC: 2020-09-16 21:39:28Z): At the end of the penultimate para in the referenced subclause add a "NOTE---Reserved fields and subfields in PHY headers might be set to a nonzero value upon transmission and might not be ignored upon reception."Change the penultimate para from "Reserved fields and subfields are set to 0 upon transmission and are ignored upon reception." to "Reserved fields and subfields defined in this clause are set to 0 upon transmission and are ignored upon reception."

3.9.6.9 No objection - Mark ready for motion

3.9.7 CID 5066 (MAC) (nee 4717)





3.9.8 CID 5078 (MAC): (nee 4444)


3.9.8.2 Review proposed resolution.

3.9.8.3 Proposed Resolution: CID 5078 (MAC): REVISED (MAC: 2020-09-16 21:47:43Z): Change to "To start an HCCA TXOP, the HC gains control of the WM by waiting a shorter time before initiating the first transmission of the TXOP than STAs using the EDCA procedures."


3.9.9 CID 5047 (GEN)

3.9.9.1 Already done yesterday.

3.9.10 CID 5068 left to do.

3.10 Review doc 11-20/1313r8 Srini KANDALA (Samsung)


3.10.2 CID 5025 (PHY)

3.10.2.1 Discussion on the concerns of having a capability bit or not.

3.10.2.2 Discussion on why a capability bit is being requested.

3.10.2.3

3.10.2.4 STRAW POLL S4: Include a capability bit in the 11-20-1313 proposal:

3.10.2.4.1 YES/NO/ABSTAIN

3.10.2.4.2 Results: 6/5/

3.10.2.5 Will have a motion on the version without the capability bit.

3.11 Add Sean Coffey who was not able to mark attendance.

3.12 For tomorrow, we will have many motions.

3.12.1 Mark RISON CIDs remain – 5068

3.12.2 Mark HAMILTON -will have a motion on 11-20/0177 and any discussion will be with the motion.

3.13 Call for any negative voters to identify any CIDs that are still associated with the disapprove vote. You can change your vote in the myProject as well.

3.14 Recess 6:02pm ET.

4.0 IEEE 802.11md REVmd CRC Telecon Thursday, September 17, 2020 16:00-18:00 ET


4.

4.1





4.3.2 About 58 attendees reported by Webex/IMAT




4.4.2 Agenda for Thursday PM2

a) Mark RISON - CID 5068

b) C. GHOSH – CID 5008

c) David GOODALL – CID 11-20-1471, CID 5016

d) Motions

e) Plans for September – December 2020

f) Adjourn

4.4.3 Review versions of the documents for review today.

4.4.4 The plan for today is resolve all the CIDs from the SA Recirc ballot.

4.4.5 Request for time to review doc 11-20/1470 – Matthew FISCHER

4.4.5.1 There may or may not be time to review the submission.

4.4.6 Proceed with the plan as displayed – see 11-20/1366r6.

4.5 Review doc 11-20/0435r16 - CID 5068 - Mark RISON (Samsung)


4.5.2 CID 5068 (MAC)



4.5.2.3 Review Alternatives to resolve the CID.

4.5.2.4 Discussion on the changes proposed and preference for the different alternative.

4.5.2.5 Proposed resolution: CID 5068 (MAC): REVISED (MAC: 2020-09-17 20:14:36Z): Make the changes shown under “Proposed changes” “Alternative 3” for CID 5068 in 11-20/0435r16 (https://mentor.ieee.org/802.11/dcn/20/11-20-0435-16-000m-resolutions-for-some-comments-on-11md-d3-0-sb1.docx), which remove the normative requirements from the NOTEs in the table, and put them into the body.


4.6 Review doc 11-20/1104r4 – CID 5008 - C. GHOSH (Intel)

4.6.1 https://mentor.ieee.org/802.11/dcn/20/11-20-1104-04-000m-proposed-changes-in-scs-10-23-2-2-and-10-23-2-9.docx

4.6.2 CID 5008 (MAC)

4.6.2.1 Review history of submission

4.6.2.2 Discussion on the changes and if the changes increases the clarity of the standard or not.

4.6.2.3 Review the effects of the proposed changes. It may have 4 cases where the “don’t exceed TXOP Limit” repeated.

4.6.2.4 Discussion of the rational on the changes was explained.

4.6.2.5 A Motion will be considered later in the call – either Reject or Revised.

4.7 Review doc 11-20-1471r1 - CID 5016 - David GOODALL (Micro Morse)


4.7.2 CID 5016 (GEN)

4.7.2.1 Review comment and the history of the comment proposed resolution.

4.7.2.2 There may be some more effort in 11me, but the test vectors seem to be ok at this point in r1.

4.7.2.3 The Test vectors where prepared and verified by two separate companies.

4.7.2.4 A Motion to resolve this CID will be made later in the call.

4.8 Review doc 11-20/1470r0 – Matthew FISCHER (Broadcom)

4.8.1 https://mentor.ieee.org/802.11/dcn/20/11-20-1470-00-000m-ba-ta-bw-oops.docx

4.8.2 Abstract: Proposed language to update a change which first appeared in D4.0 due to the resolution of SA1 CID 4439. See 11-20-0650r4

4.8.3 Review Discussion in submission for CID 4439 (from SA ballot).

4.8.4 Discussion on change the fact that the condition cannot happen and support of proposed change. Which removes part of the sentence that may be should have been removed in the last edits.

4.8.5 No Objection to make the change, and a Motion will be made later in today’s telecon.

4.9 Motions:

4.9.1 Motion #256 – GEN CIDs (5)


“Motion GEN -Sept C” tab in 11-20/1438r4




4.9.1.4 Result Motion #256: 28-0-8 Motion Passes

4.9.2 Motion #257 – GEN CID 5016 – PV1 Nonce

4.9.2.1 Resolve CID 5016 as “Revised” with a resolution of

“Incorporate the text changes in https://mentor.ieee.org/802.11/dcn/20/11-20-1471-01-000m-s1g-gen-resolution-to-cid5016.docx. These changes resolve the comment in the direction suggested by the commenter.”


4.9.2.2 Moved: David GOODALL

4.9.2.3 Seconded: Jouni MALINEN

4.9.2.4 Result Motion #257: Approved by Unanimous Consent – Motion passes.

4.9.3 Motion #258 – PHY CIDs (9+6)


“PHY Motion A” and “PHY Motion B” tabs in 11-20/1427r2


4.9.3.2 Moved: Michael MONTEMURRO

4.9.3.3 Seconded: Mark HAMILTON

4.9.3.4 Result Motion #258: Approved by Unanimous Consent – Motion passes.

4.9.4 Motion #259 – PHY CIDs (3)

4.9.4.1 Approve the comment resolutions (rejections) for CIDS 5073, 5074 and 5075 in the “SAE Constant Time” tab in 11-20/1427r2

4.9.4.2 Moved: Jouni MALINEN

4.9.4.3 Seconded: Dan HARKINS

4.9.4.4 Result Motion #259: 25-2-8 Motion Passes

4.9.5 Motion #260 – CID 5001 – Reject - Beacon at PIFS without backoff?

4.9.5.1 Resolve CID 5001 as “Rejected” with a resolution of

“The CRC discussed the comment and associated issues, in some detail during multiple teleconferences. Additional discussions occurred on the TGmd e-mail reflector. These discussions highlighted that there was not consensus on two key associated questions:

· Does the current standard allow a STA to transmit a Beacon at PIFS without any backoff?

o Some experts believe it is clear that Beacons must use AC-VO with EDCA backoff (ie not at PIFS), whereas other experts suggest that the current standard could be interpreted to allow an AP to transmit a Beacon at PIFS. This ambiguity might suggest a clarification is needed to clarify the meaning of the existing standard. However, no proposal was offered to clarify that Beacons must use AC-VO with EDCA backoff. The alternative clarification of the potential ambiguity by explicitly allowing Beacons to be transmitted at PIFS is addressed by the second key question.

· Should the current standard be changed to allow a STA to transmit a Beacon at PIFS without any backoff?

o The commenter suggested such a change could be made on the basis that many implementations transmit Beacons at PIFS today, with no apparent adverse effect, and that, in the interests of equity, the standard should make best/current practice mechanisms available to all vendors and not just those vendors who decide to violate the standard. Some experts agreed that the standard should be changed to allow Beacons to be transmitted at PIFS (a straw poll on 16 Sept 2020 on the question “Modify the text to explicitly allow Beacon frames using PIFS" voted 14 - Yes; 8 - No; 4 - Abstain). However, other experts expressed the view that the transmission of Beacons at PIFS represents “bad behaviour” and should not be rewarded. It was also suggested that the proposed change to the standard to allow the transmission of Beacons at PIFS is inadequate.

4.9.5.2 Moved: Graham SMITH

4.9.5.3 Seconded: Mike MONTEMURRO

4.9.5.4 Discussion:

4.9.5.4.1 Discussion on reasons to oppose the motion to reject.

4.9.5.4.2 Discussion on moving to another motion if this motion fails.

4.9.5.5 Result Motion #260: 19-15-7 – Motion fails.

4.9.6 Motion #261 – CID 5001 - Revised- Beacon at PIFS without backoff?

4.9.6.1 Resolve CID 5001 as Revised with a resolution of

At 1720.65, add the following text::

"–An AP transmitting a Beacon frame, as described in 11.1.3.2 (Beacon generation in non-DMG infrastructure networks).


4.9.6.2 Moved: Menzo WENTINK


4.9.6.4 Discussion:

4.9.6.4.1 There have been many emails on these various cases of changes, and the change may not be enough.

4.9.6.5 Result Motion #261: 21-15-9 Motion Fails

4.9.6.6 We will need to have a motion prepared to find a consensus to reject (of no consensus) to resolve this CID.

4.9.7 Motion #262 – CID 5001 – Reject - Beacon at PIFS without backoff?

4.9.7.1 Resolve CID 5001 as Rejected with a resolution of “The CRC discussed the comment and did not come to consensus. Proposed text changes were discussed and motions to approve them failed.

4.9.7.2 Moved: Jouni MALINEN

4.9.7.3 Second: Michael MONTEMURRO

4.9.7.4 Results Motion #262: Passed by Unanimous Consent – Motion passes.

4.9.7.5 The database resolution has the following resolution: REJECTED (PHY: 2020-09-17 21:05:10Z) - The CRC discussed the comment and did not come to consensus. Proposed text changes were discussed and motions to approve them failed." See the minutes for CID 5001 on September 17 in document https://mentor.ieee.org/802.11/dcn/20/11-20-1468-03-000m-telecon-minutes-for-revmd-crc-sept-14-17-2020.docx.

4.9.8 Motion #263 – CID 5025 – Srini

4.9.8.1 Resolve CID 5025 as Revised with a resolution of “Incorporate the changes described in11-20/1313r8 , excluding those in the APPENDIX” which address the comment in the direction proposed by the commenter.

4.9.8.2 Moved: Srini Kandala

4.9.8.3 Seconded: Mark HAMILTON

4.9.8.4 Result Motion #263: 36-4-5 Motion passes

4.9.9 Motion #264 – MAC CIDs (11)


“Motion MAC-AV” tab in 11-17/0927r66 with the addition of the full URL to the resolution of CID 5038.


4.9.9.2 Moved: Mark HAMILTON


4.9.9.4 Result Motion #264: Approved by Unanimous Consent – Motion Passes

4.9.10 Motion #265 – MAC CID 5008 - Resolve – Chitto

4.9.10.1 Resolve CID 5008 as

“Revised” with a resolution of

“Incorporate the text changes in 11-20/1104r4 . These changes resolve the comment in the direction suggested by the commenter.”

4.9.10.2 Moved: Chitto GHOSH

4.9.10.3 Seconded: Gaurav PATWARDHAN

4.9.10.4 Result Motion #265: 23-19-6 Motion fails

4.9.11 Motion #265 – MAC CID 5008 – Rejected – Chitto

4.9.11.1 Resolve CID 5008 as

“Rejected” with a resolution of

“The CRC discussed the proposed changes and did not come to consensus to make the change.

This topic, and document 11-20/1104 (https://mentor.ieee.org/802.11/dcn/20/11-20-1104-04-000m-proposed-changes-in-scs-10-23-2-2-and-10-23-2-9.docx, and previous revisions) were discussed by the CRC on Sept 11, 15 and 17, and no consensus could be reached on the changes. Concerns raised included technical gaps left by the "double negatives", and by changing what was "may" language guidance into a list of strict "shall" and "shall not" statements. There was also some opinion that the current text is not ambiguous or confusing.

4.9.11.2 Moved: Menzo WENTINK

4.9.11.3 Seconded: Jouni MALINEN

4.9.11.4 Result Motion #266: Approved by Unanimous Consent – Motion passes

4.9.11.5 Resolution in the database: CID 5008 (MAC): REJECTED (MAC: 2020-09-17 21:11:31Z) - This topic, and document 11-20/1104 (https://mentor.ieee.org/802.11/dcn/20/11-20-1104-04-000m-proposed-changes-in-scs-10-23-2-2-and-10-23-2-9.docx, and previous revisions) were discussed by the CRC on Sept 11, 15 and 17, and no consensus could be reached on the changes. Concerns raised included technical gaps left by the "double negatives", and by changing what was "may" language guidance into a list of strict "shall" and "shall not" statements. There was also some opinion that the current text is not ambiguous or confusing.

4.9.12 Motion #267 – MAC CIDs 5058 & 5061

4.9.12.1 Resolve CIDs 5058 and 5061 as

“Rejected” with the resolution reason of

“This comment was discussed on CRC teleconferences on Sept 9 and 16, and no consensus could be reached. Some concerns included that changing the reference point to the TXNAV should be the NAV instead, or perhaps both; perhaps referencing the end of the TXOP limit was more clear, although this raised concerns the sentence and the following sentence became circular with each other; and that the current text was already clear and should not be modified.”

4.9.12.2 Moved: Emily QI

4.9.12.3 Seconded: Menzo WENTINK

4.9.12.4 Results Motion #267: 32-1-5 Motion Passes.

4.9.13 Motion #268 – MAC CID 5068

4.9.13.1 Resolve CID 5068 as “REVISED; Make the changes shown under “Proposed changes” “Alternative 3” for CID 5068 in 11-20/0435r16 (https://mentor.ieee.org/802.11/dcn/20/11-20-0435-16-000m-resolutions-for-some-comments-on-11md-d3-0-sb1.docx), which remove the normative requirements from the NOTEs in the table, and put them into the body.”

4.9.13.2 Moved: Mark RISON

4.9.13.3 2nd: Menzo WENTINK

4.9.13.4 Result Motion #268: Approved by Unanimous consent

4.9.14 Motion #269 – Fix BA/TA/BW error

4.9.14.1 Incorporate the text changes in 11-20/1470r0 into the draft.

4.9.14.2 Moved Matthew FISCHER

4.9.14.3 Second Menzo WENTINK

4.9.14.4 Result Motion #269: Approved by Unanimous Consent – Motion Passes

4.9.15 Motion #270 – ARC changes – HESS/ESS changes

4.9.15.1 Incorporate the text changes in https://mentor.ieee.org/802.11/dcn/20/11-20-0177-04-0arc-liaison-to-revmd-on-ess.docx into the TGmd draft.


4.9.15.3 Seconded: Joseph LEVY

4.9.15.4 Discussion:

4.9.15.4.1 Rationale for support for the motion was expressed.

4.9.15.5 Result Motion #270: 22-9-7 Motion fails.

4.9.16 Motion #271 – CID 5025 – Srini – Corrects error found in the r8

4.9.16.1 Review Doc11-20/1313r9 - SRINI

4.9.16.1.1 Discussion on a potential error found at the last minute in 11-20/1313r8.

4.9.16.1.2 Thanks to Gabor for finding the error

4.9.16.1.3 We need to make change to restore a deleted “may” and delete the following “select”. So, the resultant text should be “may choose”

4.9.16.1.4 This change was made on screen and saved to 11-20/1313r9.

4.9.16.2 Motion text: Resolve CID 5025 as Revised with a resolution of “Incorporate the changes described in11-20/1313r9 , excluding those in the APPENDIX” which address the comment in the direction proposed by the commenter.

4.9.16.3 Moved Srini KANDALA

4.9.16.4 Second: Mark HAMILTON

4.9.16.5 Result Motion #271: Approved by Unanimous Consent – Motion passes

4.9.17 Motion #272 – Report for Conditional approval to RevCom

4.9.17.1 Review of doc 1500r1

4.9.17.2 https://mentor.ieee.org/802.11/dcn/20/11-20-1500-01-000m-p802-11revmd-report-to-ec-on-approval-to-forward-to-revcom.pptx

4.9.17.3 Identify the changes to voting record.

4.9.17.4 Feedback from all but 5 Voters received.

4.9.17.5 Need to have response from outstanding Disapprove voters on disposition of the outstanding comments.

4.9.17.6 Timeline in the report to recirc on D5.0 Sept 25-Oct 5

4.9.17.7 Discuss the need to have a date added for a 3rd recirc if required.

4.9.17.8 Post to REVcom by Oct 13.

4.9.17.9 Motion text: Approve the report in 11-20-1500r2 as the report to the IEEE 802 EC on the requirements for conditional approval to forward P802.11REVmd D5.0 to RevCom, granting the WG chair editorial license.



4.9.17.12 Result Motion #272: Passed by Unanimous Consent

4.9.18 Motion #273: CRC Approval of SA Ballot comment resolutions and recirculation ballot

4.9.18.1 Having approved comment resolutions for all of the comments received from the initial SA recirculation ballot on P802.11REVmd as contained in document 11-19/2156r24 and 11-20/1366r6 ,

Instruct the editor to prepare Draft 5.0 incorporating these resolutions and

Approve a 10-day SA Recirculation Ballot asking the question “Should P802.11REVmd D5.0 be forwarded to RevCom?”


4.9.18.3 Seconded: Stephen PALM

4.9.18.4 Result Motion #273: 26-0-1 Motion passes

4.10 Next Steps

4.10.1 Emily and Edward prepare D5.0

4.10.2 Open Ballot next week.

4.10.3 Volunteers to have 2 days to review changes –

4.10.4 Record attendance reminder

4.11 Cancel the TGmd Telecons for next week and re-announce new telecons after the ballot.

4.12 Adjourned 6:00pm

References:

Files reviewed:

1. September 14:

a) https://mentor.ieee.org/802.11/dcn/20/11-20-1366-02-000m-2020-september-interim-tgmd-agenda.pptx

b) https://mentor.ieee.org/802.11/dcn/20/11-20-0323-00-0000-2nd-vice-chair-report-july-2020.pptx

c) https://mentor.ieee.org/802.11/dcn/20/11-20-1366-03-000m-2020-september-interim-tgmd-agenda.pptx

d) https://mentor.ieee.org/802.11/dcn/19/11-19-2156-22-000m-revmd-sponsor-ballot-comments.xls

e) https://mentor.ieee.org/802.11/dcn/20/11-20-1413-04-000m-sa2-proposed-resolutions-for-editor-adhoc-and-others.doc

f) https://mentor.ieee.org/802.11/dcn/20/11-20-0177-02-0arc-liaison-to-revmd-on-ess.docx

g) https://mentor.ieee.org/802.11/dcn/20/11-20-1313-05-000m-bss-max-idle-period-negotiation-enhancements-for-non-s1g-phys.docx

h) https://mentor.ieee.org/802.11/dcn/20/11-20-1313-06-000m-bss-max-idle-period-negotiation-enhancements-for-non-s1g-phys.docx

2. September 15:


b) https://mentor.ieee.org/802.11/dcn/20/11-20-0435-15-000m-resolutions-for-some-comments-on-11md-d3-0-sb1.docx

c) https://mentor.ieee.org/802.11/dcn/20/11-20-1433-03-000m-s1g-mac-resolution-to-cid5017.docx

d) https://mentor.ieee.org/802.11/dcn/20/11-20-1454-01-000m-s1g-gen-resolution-to-cid5018.docx

e) https://mentor.ieee.org/802.11/dcn/20/11-20-1454-02-000m-s1g-gen-resolution-to-cid5018.docx

f) https://mentor.ieee.org/802.11/dcn/20/11-20-1471-00-000m-s1g-gen-resolution-to-cid5016.docx

g) https://mentor.ieee.org/802.11/dcn/20/11-20-1313-08-000m-bss-max-idle-period-negotiation-enhancements-for-non-s1g-phys.docx

h) https://mentor.ieee.org/802.11/dcn/20/11-20-0177-04-0arc-liaison-to-revmd-on-ess.docx

i) https://mentor.ieee.org/802.11/dcn/20/11-20-1104-03-000m-proposed-changes-in-scs-10-23-2-2-and-10-23-2-9.docx

j) https://mentor.ieee.org/802.11/dcn/20/11-20-1366-04-000m-2020-september-interim-tgmd-agenda.pptx

3. September 16:


b) Teleconference minutes:

1) August 3-7: https://mentor.ieee.org/802.11/dcn/20/11-20-1183-04-000m-telecon-minutes-for-revmd-crc-aug-3-7-2020.docx

2) August 19: https://mentor.ieee.org/802.11/dcn/20/11-20-1251-00-000m-telecon-minutes-for-revmd-crc-aug-19-2020.docx

3) August 21-26: https://mentor.ieee.org/802.11/dcn/20/11-20-1325-01-000m-telecon-minutes-for-revmd-crc-aug-21-and-aug-26-2020.docx

4) September 2-4: https://mentor.ieee.org/802.11/dcn/20/11-20-1390-01-000m-telecon-minutes-for-revmd-crc-sept-2-and-sept-4-2020.docx

5) September 8-9-11: https://mentor.ieee.org/802.11/dcn/20/11-20-1432-03-000m-telecon-minutes-for-revmd-crc-sept-8-9-and-10-2020.docx

c) https://mentor.ieee.org/802.11/dcn/20/11-20-1412-02-000m-revmd-sa2-comments-for-editor-ad-hoc.xlsx

d) https://mentor.ieee.org/802.11/dcn/19/11-19-2160-15-000m-revmd-editor2-standards-association-ballot-comments.xlsx

e) https://mentor.ieee.org/802.11/dcn/20/11-20-1438-03-000m-sa-ballot-recirc-1-revmd-gen-comments.xls

f) https://mentor.ieee.org/802.11/dcn/17/11-17-0927-65-000m-revmd-mac-comments.xls

g) https://mentor.ieee.org/802.11/dcn/20/11-20-0227-04-000m-pifs-for-beacons.pptx

h) https://mentor.ieee.org/802.11/dcn/20/11-20-1475-00-000m-sa2-cids-5009-5010-5011.docx

i) https://mentor.ieee.org/802.11/dcn/20/11-20-1493-00-000m-some-sa2-sae-comments.docx

j) https://mentor.ieee.org/802.11/dcn/20/11-20-0435-15-000m-resolutions-for-some-comments-on-11md-d3-0-sb1.docx

k) https://mentor.ieee.org/802.11/dcn/20/11-20-1313-08-000m-bss-max-idle-period-negotiation-enhancements-for-non-s1g-phys.docx

4. September 17:


b) https://mentor.ieee.org/802.11/dcn/20/11-20-0435-16-000m-resolutions-for-some-comments-on-11md-d3-0-sb1.docx

c) https://mentor.ieee.org/802.11/dcn/20/11-20-1104-04-000m-proposed-changes-in-scs-10-23-2-2-and-10-23-2-9.docx

d) https://mentor.ieee.org/802.11/dcn/20/11-20-1471-01-000m-s1g-gen-resolution-to-cid5016.docx

e) https://mentor.ieee.org/802.11/dcn/20/11-20-1470-00-000m-ba-ta-bw-oops.docx

f) https://mentor.ieee.org/802.11/dcn/20/11-20-1438-04-000m-sa-ballot-recirc-1-revmd-gen-comments.xls

g) https://mentor.ieee.org/802.11/dcn/20/11-20-1427-02-000m-sa2-recirc-phy-sec-comments.xlsx

h) https://mentor.ieee.org/802.11/dcn/20/11-20-1468-03-000m-telecon-minutes-for-revmd-crc-sept-14-17-2020.docx

i) https://mentor.ieee.org/802.11/dcn/20/11-20-1313-08-000m-bss-max-idle-period-negotiation-enhancements-for-non-s1g-phys.docx

j) https://mentor.ieee.org/802.11/dcn/17/11-17-0927-66-000m-revmd-mac-comments.xls

k) mentor.ieee.org/802.11/dcn/20/11-20-1104-04-000m-proposed-changes-in-scs-10-23-2-2-and-10-23-2-9.docx

l) https://mentor.ieee.org/802.11/dcn/20/11-20-0435-16-000m-resolutions-for-some-comments-on-11md-d3-0-sb1.docx

m) mentor.ieee.org/802.11/dcn/20/11-20-0177-04-0arc-liaison-to-revmd-on-ess.docx

n) mentor.ieee.org/802.11/dcn/20/11-20-1313-08-000m-bss-max-idle-period-negotiation-enhancements-for-non-s1g-phys.docx

o) https://mentor.ieee.org/802.11/dcn/20/11-20-1500-01-000m-p802-11revmd-report-to-ec-on-approval-to-forward-to-revcom.pptx

p) https://mentor.ieee.org/802.11/dcn/20/11-20-1500-02-000m-p802-11revmd-report-to-ec-on-approval-to-forward-to-revcom.pptx

q) https://mentor.ieee.org/802.11/dcn/19/11-19-2156-24-000m-revmd-sponsor-ballot-comments.xls

r) https://mentor.ieee.org/802.11/dcn/20/11-20-1366-06-000m-2020-september-interim-tgmd-agenda.pptx

IMAT Attendance Reports:

Attendance Sept 14

About 80 attendees reported by WebEx for Monday Sept 14

1.

TGmd

9/14

An, Song-Haur

INDEPENDENT

2.

TGmd

9/14

Asterjadhi, Alfred

Qualcomm Incorporated

3.

TGmd

9/14

Au, Kwok Shum

Huawei Technologies Co., Ltd

4.

TGmd

9/14

Baik, Eugene


5.

TGmd

9/14

Batra, Anuj

Apple, Inc.

6.

TGmd

9/14

Berner, Stephan

pureLiFi

7.

TGmd

9/14

Bredewoud, Albert

Broadcom Corporation

8.

TGmd

9/14

Cariou, Laurent

Intel Corporation

9.

TGmd

9/14

Chayat, Naftali

Vayyar Imaging

10.

TGmd

9/14

Cheng, Paul

MediaTek Inc.

11.

TGmd

9/14

Coffey, John

Realtek Semiconductor Corp.

12.

TGmd

9/14

Dash, Debashis

Apple, Inc.

13.

TGmd

9/14

Derham, Thomas


14.

TGmd

9/14

Eitan, Alecsander


15.

TGmd

9/14

ElSherif, Ahmed


16.

TGmd

9/14

Gan, Ming

Huawei Technologies Co. Ltd

17.

TGmd

9/14

Hamilton, Mark

Ruckus Wireless

18.

TGmd

9/14

HAN, CHONG

pureLiFi

19.

TGmd

9/14

Hansen, Christopher

Covariant Corporation

20.

TGmd

9/14

Ikegami, Tetsushi

Meiji University

21.

TGmd

9/14

Jiang, Jeng-Shiann

Vertexcom Technologies

22.

TGmd

9/14

JONES, JEFFRUM

Qorvo

23.

TGmd

9/14

Jones, Vincent Knowles IV


24.

TGmd

9/14

Kakani, Naveen


25.

TGmd

9/14

Kamel, Mahmoud

InterDigital, Inc.

26.

TGmd

9/14

Kandala, Srinivas

SAMSUNG

27.

TGmd

9/14

Kasher, Assaf


28.

TGmd

9/14

Kedem, Oren

Intel Corporation

29.

TGmd

9/14

Kim, Jeongki

LG ELECTRONICS

30.

TGmd

9/14

Kim, Sang Gook

LG ELECTRONICS

31.

TGmd

9/14

Kim, Youhan


32.

TGmd

9/14

Lalam, Massinissa

SAGEMCOM SAS

33.

TGmd

9/14

Lansford, James


34.

TGmd

9/14

Levy, Joseph

InterDigital, Inc.

35.

TGmd

9/14

Liu, Der-Zheng


36.

TGmd

9/14

Liu, Jianhan

MediaTek Inc.

37.

TGmd

9/14

Liu, Yong

Apple, Inc.

38.

TGmd

9/14

Lopez, Miguel

Ericsson AB

39.

TGmd

9/14

Lou, Hanqing

InterDigital, Inc.

40.

TGmd

9/14

Malinen, Jouni


41.

TGmd

9/14

Mirfakhraei, Khashayar

Cisco Systems, Inc.

42.

TGmd

9/14

Montemurro, Michael

Self

43.

TGmd

9/14

Nam, Junyoung


44.

TGmd

9/14

NANDAGOPALAN, SAI SHANKAR

Cypress Semiconductor Corporation

45.

TGmd

9/14

Naribole, Sharan

SAMSUNG

46.

TGmd

9/14

Nguyen, An

DHS/CISA/ECD

47.

TGmd

9/14

Oyama, Satoshi

Association of Radio Industries and Businesses (ARIB)

48.

TGmd

9/14

Pare, Thomas

MediaTek Inc.

49.

TGmd

9/14

Petrick, Albert

Jones-Petrick and Associates, LLC.

50.

TGmd

9/14

Pirhonen, Riku

NXP Semiconductors

51.

TGmd

9/14

Qi, Emily

Intel Corporation

52.

TGmd

9/14

Rai, Kapil


53.

TGmd

9/14

RISON, Mark

Samsung Cambridge Solution Centre

54.

TGmd

9/14

Rosdahl, Jon

Qualcomm Technologies, Inc.

55.

TGmd

9/14

Sand, Stephan

German Aerospace Center (DLR)

56.

TGmd

9/14

Sandhu, Shivraj


57.

TGmd

9/14

Segev, Jonathan

Intel Corporation

58.

TGmd

9/14

Serafimovski, Nikola

pureLiFi

59.

TGmd

9/14

Sherlock, Ian

Texas Instruments Incorporated

60.

TGmd

9/14

Smely, Di Dieter

Kapsch TrafficCom AG

61.

TGmd

9/14

Smith, Graham

SR Technologies

62.

TGmd

9/14

Srinivasan, Shree Raman


63.

TGmd

9/14

Stanley, Dorothy

Hewlett Packard Enterprise

64.

TGmd

9/14

Stavridis, Athanasios

Ericsson AB

65.

TGmd

9/14

Stephens, Adrian

Self

66.

TGmd

9/14

Sun, Bo

ZTE Corporation

67.

TGmd

9/14

Sun, Yanjun


68.

TGmd

9/14

Tian, Bin


69.

TGmd

9/14

Tian, Tao

Unisoc Comm.

70.

TGmd

9/14

Turkmen, Halise

IMU; Vestel

71.

TGmd

9/14

Vermani, Sameer


72.

TGmd

9/14

Wang, Chao Chun

MediaTek Inc.

73.

TGmd

9/14

Wang, Huizhao

Quantenna Communications, Inc.

74.

TGmd

9/14

Ward, Lisa

Rohde & Schwarz

75.

TGmd

9/14

Wentink, Menzo


76.

TGmd

9/14

Xue, Ruifeng

Cisco Systems, Inc.

77.

TGmd

9/14

Yang, Mao

Northwestern Polytechnical University

78.

TGmd

9/14

YANG, RUI

InterDigital, Inc.

79.

TGmd

9/14

yi, yongjiang

Futurewei Technologies

80.

TGmd

9/14

Zhang, Yan

NXP Semiconductors

Attendance Sept 15

About 46 attendees reported by WebEx for Tuesday Sept 15

1.

TGmd

9/15

Asterjadhi, Alfred


2.

TGmd

9/15

Au, Kwok Shum


3.

TGmd

9/15

CHERIAN, GEORGE


4.

TGmd

9/15

Derham, Thomas


5.

TGmd

9/15

DOAN, DUNG


6.

TGmd

9/15

Dogukan, Ali

Vestel

7.

TGmd

9/15

ElSherif, Ahmed


8.

TGmd

9/15

Ghosh, Chittabrata

Intel Corporation

9.

TGmd

9/15

Haider, Muhammad Kumail

Facebook

10.

TGmd

9/15

Hamilton, Mark

Ruckus Wireless

11.

TGmd

9/15

Hart, Brian

Cisco Systems, Inc.

12.

TGmd

9/15

Kakani, Naveen


13.

TGmd

9/15

Kang, Sugbong

Apple, Inc.

14.

TGmd

9/15

Kim, Youhan


15.

TGmd

9/15

Kwon, Young Hoon

NXP Semiconductors

16.

TGmd

9/15

Levy, Joseph

InterDigital, Inc.

17.

TGmd

9/15

Li, Qinghua

Intel Corporation

18.

TGmd

9/15

Lindskog, Erik

SAMSUNG

19.

TGmd

9/15

Malinen, Jouni


20.

TGmd

9/15

Montemurro, Michael

Self

21.

TGmd

9/15

Nam, Junyoung


22.

TGmd

9/15

Naribole, Sharan

SAMSUNG

23.

TGmd

9/15

Palm, Stephen


24.

TGmd

9/15

Pare, Thomas

MediaTek Inc.

25.

TGmd

9/15

Patwardhan, Gaurav


26.

TGmd

9/15

Petrick, Albert


27.

TGmd

9/15

Qi, Emily

Intel Corporation

28.

TGmd

9/15

Rai, Kapil


29.

TGmd

9/15

Rezk, Meriam


30.

TGmd

9/15

RISON, Mark


31.

TGmd

9/15

Rosdahl, Jon


32.

TGmd

9/15

Sandhu, Shivraj


33.

TGmd

9/15

Segev, Jonathan

Intel Corporation

34.

TGmd

9/15

Sherlock, Ian


35.

TGmd

9/15

Smith, Graham

SR Technologies

36.

TGmd

9/15



37.

TGmd

9/15

Stanley, Dorothy


38.

TGmd

9/15

Tian, Tao

Unisoc Comm.

39.

TGmd

9/15

Torab Jahromi, Payam

Facebook

40.

TGmd

9/15

Wang, Pu

Mitsubishi Electric Research Labs (MERL)

41.

TGmd

9/15

Want, Roy

Google

42.

TGmd

9/15

Wentink, Menzo


43.

TGmd

9/15

Wu, Kanke


44.

TGmd

9/15

Xue, Qi


45.

TGmd

9/15

yi, yongjiang


46.

TGmd

9/15

Yona, Yair


Attendance Sept 16


1.

TGmd

9/16

Andersdotter, Amelia

None - Self-funded

2.

TGmd

9/16

Asterjadhi, Alfred


3.

TGmd

9/16

Au, Kwok Shum


4.

TGmd

9/16

Au, Oscar

Origin Wireless

5.

TGmd

9/16

Berkema, Alan

HP Inc.

6.

TGmd

9/16

Bims, Harry

Bims Laboratories, Inc.

7.

TGmd

9/16

Coffey, John


8.

TGmd

9/16

Davies, Robert

Signify

9.

TGmd

9/16

Derham, Thomas


10.

TGmd

9/16

DOAN, DUNG


11.

TGmd

9/16

Dogukan, Ali

Vestel

12.

TGmd

9/16

ElSherif, Ahmed


13.

TGmd

9/16

Ghosh, Chittabrata

Intel Corporation

14.

TGmd

9/16

Goodall, David

Morse Micro

15.

TGmd

9/16

Haider, Muhammad Kumail

Facebook

16.

TGmd

9/16

Hamilton, Mark

Ruckus Wireless

17.

TGmd

9/16

Kakani, Naveen


18.

TGmd

9/16

Kandala, Srinivas

SAMSUNG

19.

TGmd

9/16

Kim, Youhan


20.

TGmd

9/16

Lee, Il-Gu

Sungshin University

21.

TGmd

9/16

Levy, Joseph

InterDigital, Inc.

22.

TGmd

9/16

Li, Qinghua

Intel Corporation

23.

TGmd

9/16

Lindskog, Erik

SAMSUNG

24.

TGmd

9/16

Lou, Hanqing

InterDigital, Inc.

25.

TGmd

9/16

Malinen, Jouni


26.

TGmd

9/16

McGuire, Colin

The MathWorks, Inc.

27.

TGmd

9/16

Montemurro, Michael

Self

28.

TGmd

9/16

Myles, Andrew

Cisco Systems, Inc.

29.

TGmd

9/16

Nam, Junyoung


30.

TGmd

9/16



31.

TGmd

9/16

Nguyen, An

DHS/CISA/ECD

32.

TGmd

9/16

Palm, Stephen


33.

TGmd

9/16

Patwardhan, Gaurav


34.

TGmd

9/16

Perkins, Richard

Qorvo

35.

TGmd

9/16

Petrick, Albert


36.

TGmd

9/16

Purwita, Ardimas

University of Edinburgh

37.

TGmd

9/16

Qi, Emily

Intel Corporation

38.

TGmd

9/16

Rai, Kapil


39.

TGmd

9/16

Rezk, Meriam


40.

TGmd

9/16

RISON, Mark


41.

TGmd

9/16

Rosdahl, Jon


42.

TGmd

9/16

Sarris, Ioannis

u-blox

43.

TGmd

9/16

Segev, Jonathan

Intel Corporation

44.

TGmd

9/16

Seok, Yongho

MediaTek Inc.

45.

TGmd

9/16

Sherlock, Ian


46.

TGmd

9/16

Smely, Di Dieter


47.

TGmd

9/16

Smith, Graham

SR Technologies

48.

TGmd

9/16



49.

TGmd

9/16

Stacey, Robert

Intel Corporation

50.

TGmd

9/16

Stanley, Dorothy


51.

TGmd

9/16

Tian, Tao

Unisoc Comm.

52.

TGmd

9/16


Facebook

53.

TGmd

9/16

Want, Roy

Google

54.

TGmd

9/16

Wentink, Menzo


55.

TGmd

9/16

Wu, Kanke


56.

TGmd

9/16

Yang, Jay

Nokia

57.

TGmd

9/16

Yee, Peter

NSA-CSD

58.

TGmd

9/16

yi, yongjiang


Attendance Sept 17


1.

TGmd

9/17

Akhmetov, Dmitry

Intel Corporation

2.

TGmd

9/17

Andersdotter, Amelia

None - Self-funded

3.

TGmd

9/17

Au, Kwok Shum


4.

TGmd

9/17

Au, Oscar

Origin Wireless

5.

TGmd

9/17

Baik, Eugene


6.

TGmd

9/17

Bei, Jianwei

NXP Semiconductors

7.

TGmd

9/17

Berkema, Alan

HP Inc.

8.

TGmd

9/17

Chen, Cheng

Intel Corporation

9.

TGmd

9/17

CHERIAN, GEORGE


10.

TGmd

9/17

Coffey, John


11.

TGmd

9/17

Das, Dibakar

Intel Corporation

12.

TGmd

9/17

Das, Subir

Perspecta Labs Inc

13.

TGmd

9/17

Derham, Thomas


14.

TGmd

9/17

de Vegt, Rolf


15.

TGmd

9/17

Fischer, Matthew


16.

TGmd

9/17

Ghosh, Chittabrata

Intel Corporation

17.

TGmd

9/17

Goodall, David

Morse Micro

18.

TGmd

9/17

Hamilton, Mark

Ruckus Wireless

19.

TGmd

9/17

Harkins, Daniel

Aruba Networks, Inc.

20.

TGmd

9/17

Hart, Brian

Cisco Systems, Inc.

21.

TGmd

9/17

Huang, Po-Kai

Intel Corporation

22.

TGmd

9/17

Ikegami, Tetsushi

Meiji University

23.

TGmd

9/17

Jones, Vincent Knowles IV


24.

TGmd

9/17

Kakani, Naveen


25.

TGmd

9/17

Kang, Sugbong

Apple, Inc.

26.

TGmd

9/17

Kim, Youhan


27.

TGmd

9/17

Kumar, Manish

Marvell Semiconductor, Inc.

28.

TGmd

9/17

Kwon, Young Hoon

NXP Semiconductors

29.

TGmd

9/17

Levy, Joseph

InterDigital, Inc.

30.

TGmd

9/17

Li, Qinghua

Intel Corporation

31.

TGmd

9/17

Lindskog, Erik

SAMSUNG

32.

TGmd

9/17

Lou, Hanqing

InterDigital, Inc.

33.

TGmd

9/17

Malinen, Jouni


34.

TGmd

9/17

Merlin, Simone


35.

TGmd

9/17

Montemurro, Michael

Self

36.

TGmd

9/17

Nam, Junyoung


37.

TGmd

9/17



38.

TGmd

9/17

Naribole, Sharan

SAMSUNG

39.

TGmd

9/17

Palm, Stephen


40.

TGmd

9/17

Park, Minyoung

Intel

41.

TGmd

9/17

Patwardhan, Gaurav


42.

TGmd

9/17

Qi, Emily

Intel Corporation

43.

TGmd

9/17

Raissinia, Alireza


44.

TGmd

9/17

Rezk, Meriam


45.

TGmd

9/17

RISON, Mark


46.

TGmd

9/17

Rosdahl, Jon


47.

TGmd

9/17

Sandhu, Shivraj


48.

TGmd

9/17

Segev, Jonathan

Intel Corporation

49.

TGmd

9/17

Sherlock, Ian


50.

TGmd

9/17

Smely, Di Dieter


51.

TGmd

9/17

Smith, Graham

SR Technologies

52.

TGmd

9/17



53.

TGmd

9/17

Stacey, Robert

Intel Corporation

54.

TGmd

9/17

Stanley, Dorothy


55.

TGmd

9/17

Tian, Bin


56.

TGmd

9/17

Tian, Tao

Unisoc Comm.

57.

TGmd

9/17


Facebook

58.

TGmd

9/17

Venkatesan, Ganesh

Intel Corporation

59.

TGmd

9/17

Want, Roy

Google

60.

TGmd

9/17

Wentink, Menzo


61.

TGmd

9/17

Yee, Peter

NSA-CSD

62.

TGmd

9/17

yi, yongjiang


63.

TGmd

9/17

Yona, Yair


Minutespage 2Jon Rosdahl, Qualcomm

Owning Ad-hocAssignedReviewResolution DraftedReady for MotionGrand Total

EDITOR11112

GEN91717

MAC15621

EDITOR21212

PHY11920

Grand Total35114582

Documents

doc.: IEEE 802.11-20/1468r3 · Web view2017/09/14 · Telecon Minutes for REVmd CRC - Sept 14-17 2020 Date: 2020-11-17 Author(s): Name Affiliation Address Phone email Jon Rosdahl