doc.: IEEE 802.11-14/1336r2 · Web viewa) Status of CID 3152 if available - Menzo WENTINK, Sean...

November, 2014 doc.: IEEE 802.11-14/1336r2

IEEE P802.11Wireless LANs

TGmc Telecom Minutes October 2014

Date: 2014-10-03

Author(s):Name Affiliation Address Phone email

Jon Rosdahl CSR Technologies Inc. 10871 N 5750 WHighland, Utah 84003 +1-801-492-4023 [email protected]

Minutes page 1 Jon Rosdahl, CSR Technologies Inc.

AbstractAs approved during the September Interim meeting, TGmc teleconferences are scheduled for October 3, 24 and 31. We will be continuing comment resolution.-----------------R0: October 3 Friday 10am Eastern/7am Pacific – R1: Oct 24, Friday 10am ET.7am PT

a) CID 3019 - 11-14-1345- Adrian STEPHENS b) CID 3119 in 11-14-0923 - Mike MONTEMURROc) CIDs CIDs 3313, 3314, 3493, 3141, 3281, 3282, 3334, 3346, 3353, 3394, in 11-14-1041-04-000 – Dorothy STANLEYd) CIDs in 11-14-1104 - Mark RISON - technical comments (min 1 hour)

R2: October 31: Friday 10am ET.7am PTa) Status of CID 3152 if available - Menzo WENTINK, Sean COFFEYb) Jon ROSDAHL CIDs:

CID 3438 - Security TabCID 3372 - Terminology TabCID 3463 - Terminology TabCID 3528 - Definitions TabCID 3561 - Definitions TabCID 3352 - Protection mechanisms (not yet in the file, but hope to next week or so.5 of the 6 CIDs proposed resolutions are now posted in 11-14/975r6:https://mentor.ieee.org/802.11/dcn/14/11-14-0975-06-000m-lb202-gen-adhoc-comments.xlsx

(c) CIDs in 11-14-1104 - Mark RISON, continued - (min 1 hour)

Note that teleconferences are subject to IEEE policies and procedures, see:– IEEE Patent Policy – Patent FAQ – Letter of Assurance Form– Affiliation FAQ – Anti-Trust FAQ – Ethics – 802 LMSC P&P – 802 LMSC OM – 802 WG P&P – IEEE802.11 WG OM


1.0 Minutes for 802.11 TG REVmc on 3 October 2014 10:00-12:001.1 Called to order by Dorothy STANLEY (Aruba) at 10:02am1.2 Review Patent Policy – No issues noted1.3 Review Agenda:

Draft agenda:1. Call to order, patent policy, attendance2. Editor report3. Comment resolution: Available resolutions and presenters from:

11-14-0923 - Mike MONTEMURRO11-14-1173 - Gabor BAJKO - deferred11-14-1041 - Dorothy STANLEY11-14-1104 - Mark RISONRemaining Editorial CIDs

4. AOB5. Adjourn

1.4 Adjustments to Agenda: -1.4.1 Add to Editor Report discussion on Extended Element IDs1.4.2 Agenda approved without objection

1.5 Attendance: Adrian STEPHENS (Intel); Dorothy STANLEY (Aruba); Jon ROSDAHL (CSR); Michael MONTEMURRO (Blackberry); Scott MARIN (Nokia Networks); Carlos Aldana (Qualcomm); Mark RISON (Samsung); Jouni MALINEN (Qualcomm)(no Audio); Sean COFFEY (Realteak)(No Audio);

1.6 Editor Report – Adrian STEPHENS (Intel)1.6.1 Work ongoing, but nothing to report1.6.2 Element IDs – ANA hat

1.6.2.1 Note sent to the reflector with Strawman – need feedback.1.6.2.2 TGai has requested to allocate 14 of the last 201.6.2.3 Request to discuss allocation during face to face in Nov.1.6.2.4 Need escape/expansion of element ID number space.1.6.2.5 Strawman: Option A or Option B – are they independent or alternatives

that can be done together?1.6.2.5.1 Could do both – Option A would go into Beacons, and

Option B would be everything else1.6.2.5.2 An alternate option would allow for mixing 16 and 8 bit

lengths, but that may be over complicated.1.6.2.6 Would like more discussion – Dorothy Schedule time at Face to Face at

November Plenary Session.1.7 Review 11-14-0923 - Mike MONTEMURRO (Blackberry)

1.7.1 11-14/093r6 – will capture today’s comments and be posted after the call.1.7.2 CID 3504 MAC

1.7.2.1 Review comment1.7.2.2 Proposed Resolution: incorporate the changes in 11-14/0923r6 for CID

3504.1.7.2.3 No objection mark ready for motion

1.7.3 CID 3119 MAC



1.7.3.1 Review Comment1.7.3.2 From submission discussion

“Mark Rison’s comment “For 3319, I think that for consistency with the row above it should be"Power save mode or PS". However I've spotted a wrinkle, which is that "active mode" is defined at 24.34 only as a mesh power mode...Note also that the capitalization of "Active mode" is inconsistent”

1.7.3.3 Concern with “Shall” statements in the table. Should this be moved to regular text location or see if these are duplicates of Shall statements elsewhere in the draft. Typically we want to reduce the table text and not cause contradiction elsewhere.

1.7.3.4 Suggestion to change the text in the table to be more descriptive.1.7.3.5 There are lots of PowerSave modes and we need to ensure that we

reference the specific power save clauses rather than trying to restate it here.

1.7.3.6 Action Item: Mike will go rework this CID and look for comment from others to assist.

1.7.4 CID 3120 MAC1.7.4.1 Review Comment1.7.4.2 From discussion

“Mark Rison’s comment “For 3120, there is a difference between bufferable MMPDUs and buffered MMPDUs, I think. The NOTE might be better with "bufferable" changed to "buffered", with the second sentence deleted. But where actually is the normative statement of the use of AC_VO for buffered MMPDUs? Should this not be a NOTE at all (i.e. should it be normative)?”

1.7.4.3 Question on the rational for the proposed reject – 1.7.4.4 Difference from “bufferable” vs “buffered” MMPDUs1.7.4.5 In unicast case there does not seem to be a difference in how the AC is

used.1.7.4.6 More discussion1.7.4.7 The note as stated is not correct – MMPDU may be via 11ae using other

accesses categories. 1.7.4.8 Removing the informative note does not change the draft standard.1.7.4.9 Proposed Resolution: Accept1.7.4.10 No objection – mark ready for motion1.7.4.11 Mark RISON asked to be an Abstain

1.7.5 CID 3018 MAC1.7.5.1 Review comment1.7.5.2 Proposed Resolution: Revised: Change “ Mesh STAs should adopt the

mandatory PHY rates as the default BSSBasicRateSet to reduce the risk that a candidate peer mesh STA utilizes a different BSSBasicRateSet.” To “ The SME of a Mesh STAs should use the mandatory PHY rates as the default BSSBasicRateSet in the MLME-START.request primitive to reduce



the risk that a candidate peer mesh STA utilizes a different BSSBasicRateSet.”

1.7.5.3 No objection - Mark ready for motion1.7.6 CID 3019 MAC

1.7.6.1 Review Comment1.7.6.2 Discussion on CID 2010 got rid of HT version, but we need to revisit for

the VHT set. This CID only removes the BSSBasicMCSSet at this one cited location. Reference to 11-14/207r3 for the HT removal.

1.7.6.3 Action Item: Adrian to check the VHT-MCS changes that may need to be done as well.

1.7.6.4 Proposed Resolution: Accept1.7.6.5 No objection – Mark ready for motion

1.7.7 CID 3042 MAC1.7.7.1 Review comment1.7.7.2 Agree that description of over the air material, but the parameter set is

the question.1.7.7.3 Discussion on how a station would know the peer values in the paring

process1.7.7.4 Discussion on what is actually passed from peer to peer.1.7.7.5 Update the proposed resolution in the submission for two new locations

as well.1.7.7.6 Discussion on needing hyphens in the correct locations.1.7.7.7 Proposed Resolution: Incorporate the changes in 11-14/0923r6 for CID

3042.1.7.7.8 No objection mark ready for motion

1.7.8 CID 3142 MAC1.7.8.1 Review comment1.7.8.2 Question on why table 9-17 is in clause 9 and not in clause 8 –

1.7.8.2.1 Good question, but not subject of this CID.1.7.8.3 Why refer to the sub-clause instead of the table?

1.7.8.3.1 See the clause vs table1.7.8.3.2 Why not just refer to the table?1.7.8.3.3 The table is different, so the description is better to be

referred to.1.7.8.4 The tables are not consistent so the description needs to be referred to.1.7.8.5 Straw poll:

1.7.8.5.1 Section vs Table;1.7.8.5.2 Section : 111 Table: 1 Abstain: 11 DNV: 111.7.8.5.3 Go with Section

1.7.8.6 Proposed resolution: Revised. Change “The content of the address fields is defined in Table 8-34 (Address field contents).” to “The content of the address fields transmitted by non-mesh STAs is defined in Table 8-34 (Address field contents). The content of the address fields transmitted by mesh STAs is defined in 9.35.3 (Frame addressing in an MBSS).”



1.7.8.7 After straw poll - mark ready for motion1.7.9 CID 3143 MAC

1.7.9.1 Review comment1.7.9.2 Proposed resolution. Revised; Replace the text in 611.52-60 with “The

address fields for Multihop action frames are described in 9.35.3 (Frame addressing in an MBSS).”

1.7.9.3 No objection mark ready for motion1.7.10 CID 3351 MAC

1.7.10.1 Review Comment1.7.10.2 Proposed resolution: Rejected. “The cited text refers to HCCA

operation. EDCA TXOPs do not depend on TBTT.”1.7.10.3 Discussion on if a Note is needed or not.1.7.10.4 9.22.3 is HCCA1.7.10.5 This section would be therefore HCCA issues.1.7.10.6 Updated Proposed Resolution: Revised Rename Title of 9.22.3.3

to “HCCA TXOP structure and timing” and the clause title of 9.22.3.4. to “NAV Operation of a TXOP under HCCA.”

1.7.10.7 No objection - mark ready for motion1.7.11 Recap Action items/issues–

1.7.11.1 only one CID 3119 will need to come back1.7.11.2 Adrian to review possible issue related to 3019.1.7.11.3 Question on CID 3355/3374

1.7.11.3.1 They were assigned to Mark RISON during the Athens, Greece meeting.

1.8 Review 11-14-1041 - Dorothy STANLEY (Aruba)1.8.1 11-14/1041r2 was posted – r3 will capture today’s changes made during the

conference call.1.8.2 CID 3496 GEN

1.8.2.1 Review comment1.8.2.2 Suggest that there only be one footnote 1.8.2.3 Proposed resolution: Revised; incorporate the text changes for CID 3496

as detailed in 11-14/1041r3.1.8.2.4 No objection – mark ready for motion

1.8.3 CID 3057 GEN1.8.3.1 Review comment1.8.3.2 Proposed Resolution: Accepted1.8.3.3 No objection – mark ready for motion

1.8.4 CID 3058 GEN1.8.4.1 Review comment1.8.4.2 Proposed Resolution: Revised; Proposed resolution: Incorporate the text

changes for CID 3058 as detailed in 11-14/1041r3.1.8.4.3 No objection – Mark ready for motion



1.8.4.4 Note that we need to look for PLCP removal from the definitions, but that would be separate from this CID. CID 3047 takes care of this, so no worries here.

1.8.5 Will post r3 shortly.1.8.6 There are some additional CIDs that will come later(not addressed today).

1.9 Review 11-14-1104 - Mark RISON (Samsung)1.9.1 11-14/1104r1 is on the server and was the subject of discussion in Athens, r2

was not posted after the Athens meeting.1.9.1.1 It was requested that Mark post the r2 so that it captures the discussion

and gives revisions as boundaries for the discussion times.1.9.2 CID 3321 3325 MAC

[Secretary Note: this was presented as 3321, but really it should have been identified as 3325 (11-14/1104r2 has the wrong number (3321) but it has been corrected in R3]

1.9.2.1 Review comments1.9.2.2 Discussion on the rational for the note

1.9.2.2.1 We have been trying to not mix state and capabilities.1.9.2.2.2 Change the proposed note to “This subfield indicates the

operational state immediately after association.”1.9.2.3 Review other proposed changes1.9.2.4 Concern about restricting the AP from changing the number of spatial

streams. Need to have more discussion on this.1.9.2.5 We also need more discussion on the DLS to see if it is inconsistent with

the power save or not.1.9.2.6 AI: Mark RISON to contact Matthew FISCHER and Menzo WENTINK for

feedback.1.9.2.6.1 [Secretary Note: (Menzo WENTINK) is currently assigned CID

3321 which was originally identified as the CID for this discussion.]

1.9.3 Out of time.1.10 Next call on Oct 24

1.10.1 Will start with 11-14/1104r3 - Mark RISON and do at least an hour. Will focus on the technical CIDs first.

1.11 Adjourned at 12:02 ET.




1. Call to order, patent policy, and attendance.2. Editor report - 3. Comment resolution: Available resolutions and presenters from:

a) CID 3019 – 11-14/1345 Adrian STEPHENSb) CID 3119 in 11-14-0923 - Mike MONTEMURROc) CIDs CIDs 3313, 3314, 3493, 3141, 3281, 3282, 3334, 3346, 3353, 3394, in 11-14-1041-04-000 – Dorothy STANLEYd) CIDs in 11-14-1104 - Mark RISON - technical comments (min 1 hour)e) 11-14-1104 - Mark RISONf) 11-14-1173 - Gabor BAJKO

4. Remaining Editorial CIDs5. AOB6. Adjourn2.3.1 No objection to the agenda

2.4 Attendance: Adrian STEPHENS (Intel); Dorothy STANLEY (Aruba); Jon ROSDAHL (CSR); Michael MONTEMURRO (Blackberry); Mark RISON (Samsung) Mark HAMILTON (Spectralink); Sean COFFEY (Realteak)(No Audio);

2.5 Editor report - 2.5.1 D3.3 is now available2.5.2 Need reviewers

2.6 CID 3019 MAC– 11-14/1345 Adrian STEPHENS2.6.1 Review comment2.6.2 Discussion on 11-14/207r3 consequence of implementation

2.6.2.1 1274.19(d3) change reviewed2.6.3 Review the discussion outlined in 11-14/1345r02.6.4 Proposed Resolution: Revised. Delete the cited sentence, because it has no

normative effect.2.6.5 Question on the primitives that are being changed, and if they can change the

basic rate sets or not.2.6.5.1 There may not be any issue, but we may want to look at descriptions in

the future.2.6.6 This changes the resolution from the previous resolution.(from Oct 3 call).2.6.7 No objection – mark ready for motion

2.7 CID 3119 MAC in 11-14-0923r7 - Mike MONTEMURRO2.7.1 Review Comment2.7.2 Proposed Resolution: Revised. Make the Changes indicated in Doc

14/0923r7 under CID 31192.7.3 Discussion on the actual change to the PS summary sentence2.7.4 Proposed new sentence: “STA enters the Awake State to receive or

transmit frames. The STA remains in the Doze state otherwise.”2.7.5 No objection to the change (will be included in R7).2.7.6 Mark ready for motion



2.8 CIDs 3313, 3314, 3493, 3141, 3281, 3282, 3334, 3346, 3353, 3394, in 11-14/1041r05 Dorothy STANLEY

2.8.1 Start on page 19, we looked at the others earlier2.8.2 CID 3313, 3314 – MAC

2.8.2.1 Review comments2.8.2.2 Proposed Resolution CID 3313: Rejected – The cited text is in the

“Dual CTS protection procedure” section. Dual CTS has been deprecated. No Change is required.

2.8.2.3 Proposed Resolution CID 3314: Revised At 1259.42, insert the following text: “NOTE—The following paragraph addresses the Dual CTS protection mechanism. The use of the Dual CTS protection mechanism is deprecated.

2.8.2.4 No objection mark ready for motion2.8.3 CID 3493 GEN

2.8.3.1 Review Comment2.8.3.2 Review proposed changes2.8.3.3 Proposed Resolution: REVISED (GEN: 2014-10-24 14:43:57Z)

Incorporate the changes in 11-14/1041r6 for CID 3493.Line references are relative to D3.0

2.8.3.4 No objection – mark ready for motion2.8.4 CID 3141 MAC

2.8.4.1 Review Comment2.8.4.2 Proposed Resolution: Revised – incorporate changes as noted

under CID 3141 in 11-14/1041r6.2.8.4.3 Question on the “TVHT” in the parameters of the primitives2.8.4.4 Checked and it is ok2.8.4.5 No objection – Mark Ready for Motion

2.8.5 CID 3281 and 3282 GEN2.8.5.1 Review comments2.8.5.2 Proposed Resolution: REJECTED (GEN: 2014-10-24 14:55:38Z)

Rejected The WDS term is listed in 3.1 Definitions that gets integrated into a generic dictionary of terms. This term is still in active use in devices implementing the IEEE 802.11 standard and such use is likely to continue to be the case in the future. As such, it is useful to maintain this definition. Note to commenter: This comment is effectively a duplicate comment to Comment 301 in https://mentor.ieee.org/802.11/dcn/13/11-13-0233-40-000m-revmc-wg-ballot-comments.xls.



The resolution there was to keep the term, with an explanation: “The WDS term is listed in 3.1 Definitions that gets integrated into a generic dictionary of terms. This term is still in active use in devices implementing the IEEE 802.11 standard and such use is likely to continue to be the case in the future. As such, it is useful to maintain this definition.”


2.8.6.1 Review Comment2.8.6.2 Proposed Resolution: Revised- At 992.31 change the section reference

from 10.24.5 to 10.6.2.8.6.3 No objection – Mark Ready for motion

2.8.7 CID 3346 GEN2.8.7.1 Review Comment2.8.7.2 Proposed Resolution: REVISED (GEN: 2014-10-24 14:58:23Z)

Proposed Resolution: Revised – incorporate changes as noted under CID 3346 in 11-14/1041r6.

2.8.7.3 No objection Mark ready for motion2.9 CIDs in 11-14-1104r3 - Mark Rison - technical comments (min 1 hour)

2.9.1 CID 3323 MAC and 3325 GEN2.9.1.1 Where we left off last time – note that CID was corrected in the

minutes from last time (Oct 3)2.9.1.2 Request to reach out was completed by Menzo, but no reply from

Matthew F. Some support from Adrian was also received.2.9.1.3 Review proposed changes (see page 5-8)2.9.1.4 Proposed resolution: REVISED (GEN: 2014-10-24 15:03:40Z)

Revised incorporate the changes as noted under CID 3323/3325 in 11-14/1104r4


2.9.2.1 Review comment2.9.2.2 Proposed resolution: REVISED Add the following at 1829.25:

“NOTE 3—The number of spatial streams might be further restricted if the receiving STA is in SM power save mode (see 10.2.5).” Increment the number of the two following NOTEs.


2.9.3.1 Review Comment2.9.3.2 Proposed Resolution: Revised incorporate the changes as noted

under CID 3355 in 11-14/1104r42.9.3.3 Discussion on “necessarily”



2.9.3.4 Page 38 change return(ed) to include(d)2.9.3.5 More changes and noodling required.

2.9.4 CID 3440 Editor2.9.4.1 This seemed fairly straight forward, so would ask people to take a

look at it, but don’t want to take time on this one today.2.9.5 CID 3478 MAC

2.9.5.1 Review comment2.9.5.2 Distinction between EOF PAD vs EOF padding2.9.5.3 Also discuss pre-EOF padding2.9.5.4 Propose Change “This Padding” to EOF padding in the definition. –

cannot do this as we don’t use the term being defined in the definition.

2.9.5.5 No change was made.2.9.5.6 Proposed Resolution: REVISED (MAC: 2014-10-24 16:06:29Z):

Make the changes described in 11-14/1104r4 under "Proposed changes:" for CID 3478. This addresses the comment in a different way to the way proposed by the commenter.

2.9.5.7 No objection – Mark ready for motion2.9.6 CID 3137 GEN

2.9.6.1 Review comment2.9.6.2 Proposed resolution: REJECTED (GEN: 2014-10-24 15:57:46Z) The

TVHT PHY does not require support for HT PPDUs (See 23.2.4 at 2575.62) The 11af CRC erred..

2.9.7 CID 3136 GEN2.9.7.1 Review comment2.9.7.2 Proposed Resolution: ACCEPTED (GEN: 2014-10-24 15:58:31Z)2.9.7.3 No objection – Mark ready for motion

2.9.8 CID 30512.9.8.1 Review Comment

2.9.9 Out of Time2.9.10 Start with Mark on Oct 31 – PICs comments

2.10 Review Proposed Agenda for next weeka) Status of CID 3152 if available - Menzo WENTINK, Sean COFFEYb) Jon ROSDAHL CIDs:

CID 3438 - Security TabCID 3372 - Terminology TabCID 3463 - Terminology TabCID 3528 - Definitions TabCID 3561 - Definitions TabCID 3352 - Protection mechanisms (not yet in the file, but hope to next week.



5 of the 6 CIDs proposed resolutions are now posted in 11-14/975r6:https://mentor.ieee.org/802.11/dcn/14/11-14-0975-06-000m-lb202-gen-adhoc-comments.xlsx

(c) CIDs in 11-14-1104 - Mark RISON, continued - (min 1 hour)d) One hour for Mark RISON, and one hour for others

2.11 Adjourned 12:01pm ET




a) Status of CID 3152 if available - Menzo WENTINK, Sean COFFEYb) Gen AdHoc CIDs: Jon ROSDAHL

CID 3438 - Security TabCID 3372 - Terminology TabCID 3463 - Terminology TabCID 3528 - Definitions TabCID 3561 - Definitions TabCIDs proposed resolutions are now posted in 11-14/975r7:https://mentor.ieee.org/802.11/dcn/14/11-14-0975-06-000m-lb202-gen-adhoc-comments.xlsx

(c) CIDs in 11-14-1104 - Mark RISON, continued - (min 1 hour)3.3.1 Adjustments to the agenda will be made if presenters are not present at

time of presentation3.3.2 Assaf and Mark Rison are not going to be in San Antonio, so we will try to

give them priority today.3.4 Attendance: Adrian STEPHENS (Intel); Dorothy STANLEY (Aruba); Jon ROSDAHL

(CSR); Assaf KASHER (Intel), Scott Marin (Nokia Networks), Mark HAMILTON (Spectralink); Sean COFFEY (Realteak); Viewer 5 – did not identify self., Menzo WENTINK (Qualcomm), Dan Harkins, Carlos Cordeiro (Intel); Mark RISON (Samsung);

3.5 Editor Report:3.5.1 D3.3 has been on server for week, and has been going through a review.

1st authors and volunteers are to review and respond by Nov 7th.3.6 Gen Adhoc CIDS – 11-14/975r7 - Jon ROSDAHL

3.6.1 CID 3463 GEN3.6.1.1 Reviewed and agreed with proposed changes in Ad hoc notes

column in 11-14/975r73.6.1.2 Proposed resolution: REVISED (GEN: 2014-10-31 14:17:25Z): (D3.2

line numbers) Change "Burst Timeout" with "Burst Duration" at 1057.52 (Note Figure 8-567 is split across page needs anchor to be on one page) 1058.62, 1058.64, 1059.1 (name of table), 1746.26

3.6.1.3 No objection, mark as ready for motion3.6.2 CID 3438 GEN

3.6.2.1 Reviewed proposed changes in in Ad hoc notes column in 11-14/975r7

3.6.2.2 Thanks for those that commented on proposal.3.6.2.3 Proposed resolution: REVISED (GEN: 2014-10-31 14:23:39Z):



104.19 - Change "PMK caching" to "PMKSA caching "; 104.42 - Change "If pairwise master key (PMK) caching is not enabled, deauthentication also destroys the pairwise master key security association (PMKSA) from which the deleted PTKSA was derived." to "If pairwise master key security association (PMKSA) caching is not enabled, deauthentication also destroys the PMKSA from which the deleted PTKSA was derived."; 1934.24 - No Change - Generic use of the word cache. 2915.16 - Change "maximum lifetime of a PMK in the PMK cache." to "maximum lifetime of a PMK in the PMKSA cache." 3305.61 - "…for managing PMKSA caching functionality in the STA."



3.6.3.2 Proposed resolution: REJECTED (GEN: 2014-10-31 14:25:08Z) "network" in this context is descriptive and does not cause harm to the text and is not detrimental to the standard.Examples: 16.15 -"or two STAs in an independent basic service set (IBSS) network."67.43 -"The key concept is that the ESS network appears the same to an LLC layer as an IBSS network." 68.14 -"Some examples are when an IBSS network is operating in a location that also has an ESS network,"99.43 - "The differences among the ESS, the PBSS, and the IBSS network environments are discussed separately in 4.7 (Differences among ESS, PBSS, and IBSS LANs).List of uses: "wireless network"; "access network"; "IBSS network"; "ESS network"; "PBSS network"; "MBSS network";" non-IBSS network"; "public network"; "private network";



3.6.4.2 Proposed resolution: REVISED (GEN: 2014-10-31 14:26:38Z): "A matrix determined using knowledge of the channel between a transmitter and an intended receiver that maps from space-time streams to transmit antennas with the goal of improving the



signal power or signal-to-noise ratio (SNR) at the intended receiver."



3.6.5.2 Proposed Resolution: REVISED (GEN: 2014-10-31 14:30:05Z): Replace the definition of nontransmitted BSSID with:"nontransmitted basic service set (BSS) identifier (BSSID): A BSSID that is not transmitted explicitly, but that can be derived from the information encoded in a Beacon frame."There are 4 instances of "non-transmitted" in D3.2, which need to lose their hyphen: 3551.50, 3552.11, 3552.43, and 3553.7

3.6.5.3 No objection, mark as ready for motion3.7 Review 11-14/1412r0 -- Status of CID 3152 if available - Menzo WENTINK, Sean

COFFEY3.7.1 CID 3321 MAC

3.7.1.1 Review comment3.7.1.2 Review 11-14/1412r0 for the proposed changes3.7.1.3 Proposed Resolution: REVISED (MAC: 2014-10-31 14:38:11Z):

Incorporate the text changes in 11-14/1412r1 for CID 33213.7.1.3.1 No objection mark ready for motion

3.7.1.4 CID 3457 and CID 3458 MAC3.7.1.4.1 Review comment3.7.1.4.2 Review context of changes proposed3.7.1.4.3 Proposed Resolution: CIDs 3457, 3458: REVISED (MAC:

2014-10-31 14:41:12Z): Incorporate changes shown in 11-14/1412r1 for CIDs 3457 and 3458.

3.7.1.4.4 No objection mark ready for motion3.7.2 CID 3776 MAC

3.7.2.1 Review Comment3.7.2.2 Review context of the changes proposed – 11-14/1412r13.7.2.3 Should we check another table – OCB (11p table).3.7.2.4 In R1 Menzo will make the same changes to the OCB table to

match this set of changes – 3.7.2.4.1 This should be handled separately, and will not be in

the R1 afterall.3.7.2.5 Proposed Resolution: CID 3776: REVISED (MAC: 2014-10-31

14:43:46Z): Modify Table 8-144 (Default EDCA Parameter Set element parameter values if dot11OCBActivated is false) as shown in 11-14-1412-01-000m-revmc-lb202-assorted-cids.docx, changing the TXOP limit for AC_BK and AC_BE to 2.528 ms, from 2.080 ms.

3.7.2.6 No objection Mark ready for motion3.7.3 CID 3777 MAC



3.7.3.1 Review Comment3.7.3.2 Proposed Resolution: CID 3777: REJECTED (MAC: 2014-10-31

14:49:33Z): The identified issue is not likely to occur in practice3.7.4 CID 3778 MAC

3.7.4.1 Review Comment3.7.4.2 Propose Resolution: CID 3778: REJECTED (MAC: 2014-10-31

14:50:33Z): This comment does include sufficient details to determine the changes required.

3.7.4.3 No objection mark ready for motion3.7.5 CID 3779

3.7.5.1 Review Comment3.7.5.2 Proposed resolution: CID 3779: REJECTED (MAC: 2014-10-31

14:51:56Z): This comment does include sufficient details to determine the changes required.

3.7.5.3 No objection mark ready for motion3.7.6 CID 3152

3.7.6.1 Review Comment3.7.6.2 Review discussion3.7.6.3 Changes to the proposal discussed3.7.6.4 Proposed Resolution: CID 3152: REJECTED (MAC: 2014-10-31

14:57:53Z): While an option is to change the identified "shall" to "should" and add a recommendation that the Use_Protection bit is set to 1 when remote STAs are suspected, such a recommendation is hard to quantify, so it is unknown how it will affect practical implementations.

3.8 Review 11-14/1274r1 – Assaf KASHER3.8.1 CID 3242 GEN

3.8.1.1 Review Comment3.8.1.2 Proposed Resolution: CID 3242 REVISED (GEN: 2014-10-31

15:02:47Z) Make changes as shown in 11-14/1274r2 for CID 32423.8.1.3 No objection mark ready for motion

3.8.2 CID 3245 GEN3.8.2.1 Review Comment3.8.2.2 Reviewed discussion and proposed changes.3.8.2.3 Discussion on Field/subfield/unit usage.3.8.2.4 Request for a change – the figure so that TRN-Unit be defined the

same or if there are differences it should be labeled different.3.8.2.5 Page 4 – the TRN subfields should be “units”3.8.2.6 The entire document will need to be checked to ensure it is

consistent. This will be taken offline and fixed up in R2.3.8.2.7 We will look for an R2 before we take more of this.

3.8.3 CID 3246 is similar to 3245, so we will skip that and go to 3247,3.8.4 CID 3247 GEN

3.8.4.1 Review Comment3.8.4.2 Proposed Resolution: REJECTED (GEN: 2014-10-31) N_CBPS is

defined in table 21-5 as Number of coded bits per symbol.



Nothing in the definition makes it specific to OFDM. It is assumed that the reader knows what a single carrier symbols is. The term is also used in table 21-18. It is not necessary to define this for low-power single carrier PHY as it is not used in 21.7.

3.8.4.3 No objection mark ready for motion3.8.5 Assaf will not be in San Antonio, so Carlos will present the rest of the

document in Texas next week as well as 11-14/1275..3.9 CIDs in 11-14-1104r5 - Mark RISON, continued

3.9.1 Mark joined late, so we do not have 60mins left for his requested time.3.9.2 Start with 11-14/1104r4 – CID 3355 then PICS CIDs. – r4 is currently on

mentor, and r5 will capture today’s discussion3.9.3 CID 3355 MAC

3.9.3.1 Review comment3.9.3.2 Review proposed changes from what was presented last week.3.9.3.3 There was a stray comment that questioned a bullet, but did not

make a change – it was noted that we are expecting to go out of next week for recirculation.

3.9.3.4 Proposed resolution: CID 3355: REVISED (MAC: 2014-10-31 15:35:40Z): Incorporate changes as shown in 11-14/1104r4 for CID 3355.

3.9.3.5 No objection – mark ready for motion3.9.4 CID 3051 GEN

3.9.4.1 Review comment3.9.4.2 Identify fixes that need to be done in the PICs along with the

specific change – add VHT to the list of PHYs to be supported.3.9.4.2.1 The change is not necessary, so more thought on how

to define the dependency will need to be reviewed.3.9.4.3 Wait on the proposed resolution on this CID

3.9.5 CID 3049 GEN3.9.5.1 Review Comment3.9.5.2 Proposed Resolution: ACCEPTED (GEN: 2014-10-31 15:42:46Z)3.9.5.3 No objection mark ready for motion

3.9.6 CID 3050 GEN3.9.6.1 Review comment3.9.6.2 Proposed Resolution: REVISED (GEN: 2014-10-31 15:43:59Z) Insert

“FR10:M” in the Status column at 2651.12.3.9.6.3 No objection mark ready for motion

3.9.7 CID 30523.9.7.1 Review comment3.9.7.2 Question on the Initiator vs Responder

3.9.7.2.1 Is the initiator the transmitter?3.9.7.2.2 Need to check with Brian for specific wording to be

sure.3.9.7.3 Hold for review of the language3.9.7.4 AI: Mark to e-mail Brian and cc Dorothy – Dorothy will follow-up

on the specific wording.



3.9.8 Security CIDS – 3426 (GEN), 3427, 3429 (EDITOR) – 12 minutes left.3.9.8.1 There is a proposal in 11-14-1104r4

3.9.8.1.1 Discussion on if the ‘-‘ is to be included or not3.9.8.1.2 HMAC convention from IETF RFC 2104

3.9.8.1.2.1 HMAC-SHAn[-len]] to avoid confusion3.9.8.1.3 One proposal to consider HMAC-SHA1-64 a proper

noun rather than an adjective.3.9.8.2 Alternate approach from Dan HARKINS

3.9.8.2.1 11-14/1357r0 – shows another alternative3.9.8.2.2 [HMAC-]SHA-<name>[-n] – for <name> being either 1,

256, or 3843.9.8.2.3 FIPS and IETF have different “standards”3.9.8.2.4 Review a set of proposed resolutions for the CIDs3.9.8.2.5 Question on the specific resolution: as the text as

shown gives the rationale, but does not give the changes in the box.

3.9.8.3 Due to time, debate on how to write the resolution stopped to discuss the specific changes being proposed by the two proposals..3.9.8.3.1 There was concern that the latter proposal did not give

reference to terms that are cited in the references already used.

3.9.8.3.2 The Normative reference for Hash algorithm has to be referenced in the proper format for the algorithm being called out.

3.9.9 Time was called3.10 Review proposal3.11 Next week

3.11.1 We have 7 slot times3.11.2 There is a lot of work to do next week.

3.12 Adjourned at 12:01 ET.



References:

3 Oct 2014:https://mentor.ieee.org/802.11/dcn/14/11-14-0923-05-000m-tgmc-selected-mac-comment-resolutions.docx

https://mentor.ieee.org/802.11/dcn/14/11-14-1041-02-000m-lb202-assigned-comments.docxhttps://mentor.ieee.org/802.11/dcn/14/11-14-1041-03-000m-lb202-assigned-comments.docx

https://mentor.ieee.org/802.11/dcn/14/11-14-1104-02-000m-resolutions-for-some-mac-pics-and-security-comments-on-11mc-d3-0-lb202.docx

24 Oct 2014:https://mentor.ieee.org/802.11/dcn/14/11-14-1345-00-000m-lb202-stephens-resolutions-part-deux.dochttps://mentor.ieee.org/802.11/dcn/14/11-14-0207-08-000m-lb199-stephens-comments.dochttps://mentor.ieee.org/802.11/dcn/14/11-14-0923-07-000m-tgmc-selected-mac-comment-resolutions.docxhttps://mentor.ieee.org/802.11/dcn/14/11-14-1041-05-000m-lb202-assigned-comments.docxhttps://mentor.ieee.org/802.11/dcn/14/11-14-1041-06-000m-lb202-assigned-comments.docxhttps://mentor.ieee.org/802.11/dcn/14/11-14-1104-03-000m-resolutions-for-some-mac-pics-and-security-comments-on-11mc-d3-0-lb202.docx

31 Oct 2014https://mentor.ieee.org/802.11/dcn/14/11-14-0975-07-000m-lb202-gen-adhoc-comments.xlsxhttps://mentor.ieee.org/802.11/dcn/14/11-14-1412-01-000m-revmc-lb202-assorted-cids.docxhttps://mentor.ieee.org/802.11/dcn/14/11-14-1412-00-000m-revmc-lb202-assorted-cids.docxhttps://mentor.ieee.org/802.11/dcn/14/11-14-1274-01-000m-11ad-phy-comment-resolution.docxhttps://mentor.ieee.org/802.11/dcn/14/11-14-1274-01-000m-11ad-phy-comment-resolution.docxhttps://mentor.ieee.org/802.11/dcn/14/11-14-1104-04-000m-resolutions-for-some-mac-pics-and-security-comments-on-11mc-d3-0-lb202.docx




https://mentor.ieee.org/802.11/dcn/14/11-14-1274-01-000m-11ad-phy-comment-resolution.docx

https://mentor.ieee.org/802.11/dcn/14/11-14-1274-01-000m-11ad-phy-comment-resolution.docx

https://mentor.ieee.org/802.11/dcn/14/11-14-1412-00-000m-revmc-lb202-assorted-cids.docx

https://mentor.ieee.org/802.11/dcn/14/11-14-1412-01-000m-revmc-lb202-assorted-cids.docx

https://mentor.ieee.org/802.11/dcn/14/11-14-0975-07-000m-lb202-gen-adhoc-comments.xlsx



https://mentor.ieee.org/802.11/dcn/14/11-14-1041-06-000m-lb202-assigned-comments.docx


https://mentor.ieee.org/802.11/dcn/14/11-14-0923-07-000m-tgmc-selected-mac-comment-resolutions.docx


https://mentor.ieee.org/802.11/dcn/14/11-14-0207-08-000m-lb199-stephens-comments.doc

https://mentor.ieee.org/802.11/dcn/14/11-14-1345-00-000m-lb202-stephens-resolutions-part-deux.doc

https://mentor.ieee.org/802.11/dcn/14/11-14-1345-00-000m-lb202-stephens-resolutions-part-deux.doc







doc.: IEEE 802.11-14/1336r2 · Web viewa) Status of CID 3152 if available - Menzo WENTINK, Sean...

Documents

Transcript of doc.: IEEE 802.11-14/1336r2 · Web viewa) Status of CID 3152 if available - Menzo WENTINK, Sean...