PAR Review - Meeting Agenda and Comment slides - San Antonio 2016 November 2016 doc.: IEEE 802-11-16/1326r2 November 2016 PAR Review - Meeting Agenda and Comment slides - San Antonio 2016 Date: 2016-11-10 Authors: Jon Rosdahl, (Qualcomm) Jon Rosdahl, (Qualcomm)

Abstract-Snapshot Nov 6-11, 2016, San Antonio, TX, USA November 2016 doc.: IEEE 802-11-16/1326r2 November 2016 Abstract-Snapshot Nov 6-11, 2016, San Antonio, TX, USA PARs under consideration: 802c - Amendment: Local Medium Access Control (MAC) Address Usage, PAR Modification 802.1AR:  Standard - Secure Device Identity, PAR and CSD 802.1CS - Standard: Link-local Registration Protocol, PAR and CSD 802.3cg - Amendment: 10 Mb/s Operation over Single Balanced Twisted-pair Cabling and Associated Power Delivery , PAR and CSD 802.11 Amendment: Low-power wake-up radio operation, PAR and CSD 802.19.2 – Standard: Coexistence of Unlicensed Wireless Systems in an Automotive Environment , PAR and CSD Meeting times: Monday PM2, Tuesday AM2, Thursday AM2 Jon Rosdahl, (Qualcomm) Jon Rosdahl, (Qualcomm)

PAR Review SC – November 2016 Chair: Jon Rosdahl doc.: IEEE 802-11-16/1326r2 November 2016 PAR Review SC – November 2016 Chair: Jon Rosdahl Draft Agenda: Monday Agenda: Welcome Approve Previous Minutes Determine order of review Review PARs/CSD posted for review this week. Recess Tuesday Agenda: Complete review of PARs/CSD and post comments to 802 WGs Thursday Agenda: Review Response to Comments Prepare Report for 802.11 WG closing plenary Adjourn Jon Rosdahl, (Qualcomm) Jon Rosdahl, (Qualcomm)

Motion to Approve Previous Minutes November 2016 Motion to Approve Previous Minutes Move to approve doc 11-16/0986r0 <https://mentor.ieee.org/802.11/dcn/16/11-16-0986-00- 0PAR-minutes-july-2016-session.docx> as the minutes for PAR Review SC from July 2016 Plenary in San Diego. Moved: Mike Montemurro 2nd: Stuart Kerry Results: 4-0-1 Jon Rosdahl, (Qualcomm)

November 2016 Par Review Comments Jon Rosdahl, (Qualcomm)

November 2016 802c - Amendment: Local Medium Access Control (MAC) Address Usage, PAR Modification No Comment Jon Rosdahl, (Qualcomm)

802.1AR: Standard - Secure Device Identity, PAR and CSD November 2016 802.1AR:  Standard - Secure Device Identity, PAR and CSD No Comment Jon Rosdahl, (Qualcomm)

802.1CS - Standard: Link-local Registration Protocol, PAR and CSD November 2016 802.1CS - Standard: Link-local Registration Protocol, PAR and CSD PAR: 5.2 “rapidly, accurately, and efficiently” do you have any metric to quantify these adverbs. 5.5 – expansion of first use Acronym Change MRP "802.1Q Multiple Registration Protocol“ to “802.1Q Multiple Registration Protocol (MRP)” 5.5 – Quantify: smaller vs bigger – give numeric range for each. CSD: 1.2.1 – MRP acronym expansion needed. Change “New applications like industrial automation” to “New applications in industrial automation” 1.2.3 LRP and LLDP expansion needed Suggestion – add a use case example to expand the 2nd paragraph 1.2.4 What is IS-IS? Please expand. Jon Rosdahl, (Qualcomm)

November 2016 802.3cg - Amendment: 10 Mb/s Operation over Single Balanced Twisted-pair Cabling and Associated Power Delivery , PAR and CSD Replace 5.2.b. Scope of the project: with “Specify additions to and appropriate modifications of IEEE Std 802.3 to add 10 Mb/s Physical Layer (PHY) specifications and management parameters for operation and associated optional provision of power on single balanced twisted-pair copper cabling.” 5.5 – change “IEEE 802.3” to “IEEE Std 802.3” 5.6 suggestion is to delete “factory, process” as they are redundant 8.1 – add “5.2.b. - IEEE Std 802.3 – <full title of standard.> Jon Rosdahl, (Qualcomm)

November 2016 802.19.2 - Standard: Coexistence of Unlicensed Wireless Systems in an Automotive Environment , PAR and CSD Change scope 5.2 to “This recommended practice recommends dynamic parameter values for IEEE 802 and Bluetooth devices operating in the 2.4 GHz band to enhance their performance in the automotive environment.” 5.4 request to quantify “improvements in throughput, latency, reliability, PESQ (Perceptual Evaluation Speech Quality) score etc” 5.4 change “for example” to “such as” 5.4 delete “the” prior to physical layer and medium access…(two instances) Jon Rosdahl, (Qualcomm)

November 2016 802.19.2 - Standard: Coexistence of Unlicensed Wireless Systems in an Automotive Environment , PAR and CSD 5.4 change “The typical scenarios the recommended practice will include: Interference among IEEE 802.11 devices in the 2.4 GHz band. Interference between IEEE 802.11 devices and non IEEE 802.11 devices in the 2.4 GHz band. Non-IEEE 802.11 devices in the 2.4 GHz band include but are not limited to Bluetooth devices.” To “The recommended practice addresses interference scenarios among and between 2.4 GHz IEEE 802 and non-IEEE 802 devices (e.g. Bluetooth).” Jon Rosdahl, (Qualcomm)

November 2016 802.19.2 - Standard: Coexistence of Unlicensed Wireless Systems in an Automotive Environment , PAR and CSD 5.5 replace the Need for Project with “The automotive environment is one of the 2.4 GHz wireless environments with rapidly increasing deployment. This environment differs from the enterprise or residential environments. Automotive environments are characterized by high density of access points and stations (e.g. in traffic jams) with inter-AP distance of 2m-3m and dynamically changing interference conditions. There is extensive use of non IEEE 802 technologies in the 2.4 GHz band, which require consideration of coexistence issues. This recommended practice aims to improve coexistence and performance in 2.4 GHz. Jon Rosdahl, (Qualcomm)

802.11 Amendment: Low-power wake-up radio operation, PAR and CSD November 2016 doc.: IEEE 802-11-16/1326r2 November 2016 802.11 Amendment: Low-power wake-up radio operation, PAR and CSD 1.1 Project Number – change to “P802.11ba” 2.1 Title – need to quantify “Low-power” suggest “Low-power (less than 1mill-watt)” 5.2.b. The scope uses “normal” which should be removed. Is it really a new PHY layer that uses both 2.4 GHz and 5 GHz bands? Use of “packets” seems odd to use rather than “frame”? Can this work in the 3 GHz, 60Ghz or Whitespace bands as well? The current scope statement seems to be a listing of market points for the amendment. Proposed Scope replacement text 5.2.b Scope of the Project: This amendment defines physical (PHY) layer and medium access control (MAC) layer specifications that enables operation of a wake-up radio (WUR). The WUR defines an active receiver with expected power consumption of less than one milliwatt. Jon Rosdahl, (Qualcomm) Jon Rosdahl, (Qualcomm)

802.11 Amendment: Low-power wake-up radio operation, PAR and CSD November 2016 802.11 Amendment: Low-power wake-up radio operation, PAR and CSD 5.5 suggested changes: Change “Devices based on the power save modes of the IEEE 802.11 standard periodically wake up from a sleep… “ To “Devices based on the IEEE 802.11 power save modes periodically wake up from a sleep…” Change “Therefore, for the 802.11 standard to be competitive, the IEEE 802.11 WG needs to develop power efficient mechanisms “ To “Power efficient mechanisms need …” Delete “This project addresses this need. This project is also expected to benefit traditional devices with WLAN interfaces such as smartphones.” 8.1 delete the 5.2.b. note (all the text). Jon Rosdahl, (Qualcomm)

November 2016 Responses From 802 WGs Jon Rosdahl, (Qualcomm)

IEEE 802.19.2 response November 2016    IEEE 802.19 would like to thank 802.3 and 802.11 for their time reviewing and commenting on the 802.19.2 PAR and CSD.                  Here is a link to the 802.19 responses to the comments we received on the 802.19.2 PAR and CSD,                https://mentor.ieee.org/802.19/dcn/16/19-16-0184-01-Auto-par-comment-responses.pptx                The CSD has been updated to implement the changes as per the above document,                https://mentor.ieee.org/802.19/dcn/16/19-16-0130-05-Auto-csd-document.docx                Since the PAR has been pre-submitted to NesCom I will provide a redlined PAR (as suggested by Jon Rosdahl), since now that the PAR has been pre-submitted I cannot make PAR changes directly on the NesCom web site. IEEE 802.19.2 response Jon Rosdahl, (Qualcomm)

November 2016 802.11 Comments Comment Change scope 5.2 to “This recommended practice recommends dynamic parameter values for IEEE 802 and Bluetooth devices operating in the 2.4 GHz band to enhance their performance in the automotive environment.” Response Accept in principle. Used this text except replaced “automotive” with “vehicular” Steve Shellhammer, Qualcomm

November 2016 802.11 Comments Comment 5.4 request to quantify “improvements in throughput, latency, reliability, PESQ (Perceptual Evaluation Speech Quality) score etc.” Response Reject. Since this is a Recommended Practice, the document cannot quantify the performance improvement. Steve Shellhammer, Qualcomm

802.11 Comments Comment 5.4 change “for example” to “such as” November 2016 802.11 Comments Comment 5.4 change “for example” to “such as” 5.4 delete “the” prior to physical layer and medium access…(two instances) Response Accept Steve Shellhammer, Qualcomm

November 2016 802.11 Comments Comment 5.4 change “The typical scenarios the recommended practice will include: Interference among IEEE 802.11 devices in the 2.4 GHz band. Interference between IEEE 802.11 devices and non IEEE 802.11 devices in the 2.4 GHz band. Non-IEEE 802.11 devices in the 2.4 GHz band include but are not limited to Bluetooth devices.” To “The recommended practice addresses interference scenarios among and between 2.4 GHz IEEE 802 and non-IEEE 802 devices (e.g. Bluetooth).” Response Accept in Principle. Changed to “The recommended practice addresses interference scenarios among 2.4 GHz IEEE 802 devices. It also addresses interference between 2.4 GHz IEEE 802 and non- IEEE 802 devices (e.g. Bluetooth).” Steve Shellhammer, Qualcomm

802.11 Comments Comment 5.5 replace the Need for Project with November 2016 802.11 Comments Comment 5.5 replace the Need for Project with “The automotive environment is one of the 2.4 GHz wireless environments with rapidly increasing deployment. This environment differs from the enterprise or residential environments. Automotive environments are characterized by high density of access points and stations (e.g. in traffic jams) with inter-AP distance of 2m-3m and dynamically changing interference conditions. There is extensive use of non IEEE 802 technologies in the 2.4 GHz band, which require consideration of coexistence issues. This recommended practice aims to improve coexistence and performance in 2.4 GHz. Response Accept in principle. Used this text except replaced “automotive” with “vehicular” Steve Shellhammer, Qualcomm

November 2016 In response to comments received on the 802.11 wake-up radio (WUR) PAR and 5C,  these documents have been revised. The comment responses are in document https://mentor.ieee.org/802.11/dcn/16/11-16-1528-00-0wur-comments-on-wur-sg-par-and-csd.ppt . The updated PAR is https://mentor.ieee.org/802.11/dcn/16/11-16-1045-09-0wur-a-par-proposal-wur-sg.docx The updated CSD is https://mentor.ieee.org/802.11/dcn/16/11-16-0936-04-0wur-a-csd-proposal-for-wake-up-radio-wur.docx 802.11 WUR Response Jon Rosdahl, (Qualcomm)

Comments from 802.11 PAR SC on PAR November 2016 doc.: IEEE 802-11-16/1326r2 November 2016 Comments from 802.11 PAR SC on PAR Comments: Project Number – change to “P802.11ba” Resolution: Agreed. Minyoung Park (Intel Corporation) Osama Aboul-Magd (Huawei Technologies)

Comments from 802.11 PAR SC on PAR November 2016 doc.: IEEE 802-11-16/1326r2 November 2016 Comments from 802.11 PAR SC on PAR Comments: 2.1 Title – need to quantify “Low-power”. suggest “Low-power (less than 1mill-watt)” Resolution: Revised. The title is changed to “wake-up radio operation”. Minyoung Park (Intel Corporation) Osama Aboul-Magd (Huawei Technologies)

Comments from 802.11 PAR SC on PAR November 2016 doc.: IEEE 802-11-16/1326r2 November 2016 Comments from 802.11 PAR SC on PAR Comments: 5.2.b. The scope uses “normal” which should be removed. Is it really a new PHY layer that uses both 2.4 GHz and 5 GHz bands? Use of “packets” seems odd to use rather than “frame”? Can this work in the 3 GHz, 60Ghz or Whitespace bands as well? The current scope statement seems to be a listing of market points for the amendment. Proposed Scope replacement text 5.2.b Scope of the Project: This amendment defines physical (PHY) layer and medium access control (MAC) layer specifications that enables operation of a wake-up radio (WUR). The WUR defines an active receiver with expected power consumption of less than one milliwatt. Response: Revised. Project scope was updated in 11-16-1045r9 https://mentor.ieee.org/802.11/dcn/16/11-16-1045-09-0wur-a-par-proposal-wur-sg.docx Minyoung Park (Intel Corporation) Osama Aboul-Magd (Huawei Technologies)

Comments from 802.11 PAR SC on PAR November 2016 Comments from 802.11 PAR SC on PAR Comment: 5.5 suggested changes: Change “Devices based on the power save modes of the IEEE 802.11 standard periodically wake up from a sleep… “ To “Devices based on the IEEE 802.11 power save modes periodically wake up from a sleep…” Change “Therefore, for the 802.11 standard to be competitive, the IEEE 802.11 WG needs to develop power efficient mechanisms “ To “Power efficient mechanisms need …” Delete “This project addresses this need. This project is also expected to benefit traditional devices with WLAN interfaces such as smartphones.” Response: Accepted. Minyoung Park (Intel Corporation)

Comments from 802.11 PAR SC on PAR November 2016 Comments from 802.11 PAR SC on PAR Comment: 8.1 delete the 5.2.b. note (all the text). Response: Accepted. Minyoung Park (Intel Corporation)

November 2016 IEEE 802.3cg Jon Rosdahl, (Qualcomm)

November 2016 Email Response from 802.3cg IEEE 802.3 would like to thank IEEE 802.11 for their time reviewing and commenting on the IEEE P802.3cg PAR. In responses to these comments the following changes were made: An updated draft IEEE P802.3cg PAR is available at < https://mentor.ieee.org/802-ec/dcn/16/ec-16-0152-02- 00EC-ieee-p802-3cg-draft-par.pdf >. Jon Rosdahl, (Qualcomm)

November 2016 Change to 802.3CG - Scope • Change 5.2.b. as shown: 5.2.b. Scope of the project: Specify additions to and appropriate modifications of IEEE Std 802.3 to add 10 Mb/s Physical Layer (PHY) specifications and management parameters for operation, and associated optional provision of power, on single balanced twisted-pair copper cabling. Define methodology for the optional provision of power to connected Data Terminal Equipment (DTE) for use with IEEE 802.3 10 Mb/s single-pair interfaces. 5.5 Change IEEE 802.3 to IEEE Std. 802.3 Jon Rosdahl, (Qualcomm)

November 2016 IEEE 802.3cg - 5.6 • Change 5.6 as shown: • 5.6 Stakeholders for the Standard: End-users, vendors, system integrators, and providers of systems and components (e.g., sensors, actuators, instruments, controllers, network infrastructure, user interfaces, and servers) for automotive, other transportation, industrial, factory, process, and building automation. • 8.1 – add “5.2b – IEEE Std 802.3 – IEEE Standard for Ethernet”. Jon Rosdahl, (Qualcomm)

IEEE 802.1CS Response November 2016 The responses to the comment are here: http://ieee802.org/1/files/public/docs2016/cs-PAR-CSD-comments-and-resolution-1116-v02.pdf   The PAR has been updated: http://ieee802.org/1/files/public/docs2016/cs-LRP-PAR-1116-v01.pdf The updated CSD: http://ieee802.org/1/files/public/docs2016/cs-LRP-CSD-1116-v01.pdf IEEE 802.1CS Response Jon Rosdahl, (Qualcomm)

November 2016 802.11 Comment #1 on PAR: 5.2 “rapidly, accurately, and efficiently” – do you have any metric to quantify these adverbs. Response: It is impractical to assign numerical values for rapidity, accuracy, and efficiency for a software protocol, as opposed to a physical link. As indicated in 5.5 Need for Project, these words can be read as, “more rapidly, accurately, and efficiently than MRP.” We have removed those words, see modified 5.2 scope. Jon Rosdahl, (Qualcomm)

Change MRP "802.1Q Multiple Registration November 2016 802.11 Comment #2 on PAR: 5.5 expansion of first use Acronym Change MRP "802.1Q Multiple Registration Protocol“ to “802.1Q Multiple Registration Protocol (MRP)” Response: Suggested change applied. Jon Rosdahl, (Qualcomm)

5.5 – Quantify: smaller vs bigger – give numeric range for each. November 2016 802.11 Comment #3 on PAR: 5.5 – Quantify: smaller vs bigger – give numeric range for each. Response: “designed for much smaller database and inefficient for applications with bigger database” has been changed to “optimized for databases up to 1500 bytes, and slows significantly when used for larger databases”. Jon Rosdahl, (Qualcomm)

1.2.1 –MRP acronym expansion needed. Response: November 2016 802.11 Comment #4 on CSD: 1.2.1 –MRP acronym expansion needed. Response: Replace the first “MRP” with “802.1Q Multiple Registration Protocol (MRP)” Change “New applications like industrial automation” to “New applications in industrial automation” Response: “New applications like industrial automation require” has been changed to “New applications, including industrial automation or audio/video for large venues, require”. Jon Rosdahl, (Qualcomm)

1.2.3 LRP and LLDP expansion needed Response: November 2016 802.11 Comment #5 on CSD: 1.2.3 LRP and LLDP expansion needed Response: The first “LRP” has been replaced with “Link-local Registration Protocol (LRP)” and the first “LLDP (802.1AB)” has been replaced with “Link Layer Discovery Protocol (LLDP, IEEE 802.1AB)”. Jon Rosdahl, (Qualcomm)

Suggestion – add a use case example to expand the 2nd paragraph 1.2.4. November 2016 802.11 Comment #6 on CSD: Suggestion – add a use case example to expand the 2nd paragraph 1.2.4. Response: The text in 1.2.4 has been updated to make it clear that the IS-IS routing protocol is a use-case example. What is IS-IS? Please expand. “IS-IS” has been replaced with “the Intermediate System to Intermediate System (IS-IS, ISO/IEC 10589:2002) routing protocol” Jon Rosdahl, (Qualcomm)

November 2016 Final Report to 802.11 Jon Rosdahl, (Qualcomm)

November 2016 Report to 802.11 IEEE 802.11 PAR Review SC report to 802.11 WG. The Standing Committee reviewed 6 PARs. Feedback for 802.1CS (slide 8), 802.3cg (slide 9), 802.19.2 (slides 10-12) and 802.11 WUR (slides 13-14) was provided by the Tuesday 6:30pm deadline. Responses were received from 802.19.2 (slides 17-21), 802.11 WUR (slides 23-27), 802.3cg (slides 29-31); 802.1CS (slides 32-38). We had no comments for 802C or 802.1AR. Jon Rosdahl, (Qualcomm)

Motion To Approve Report November 2016 doc.: IEEE 802-11-16/1326r2 November 2016 Motion To Approve Report Move to accept 11-16/1326r2 as the report from PAR Review SC for the November 2016 plenary. Moved: Adrian Stephens 2nd: Michael Montemurro Results: 5-0-0 This Document Jon Rosdahl, (Qualcomm) Jon Rosdahl, (Qualcomm)

References IEEE 802 PARs Under consideration Webpage: Minutes: http://ieee802.org/1/files/public/docs2016/cs-PAR-CSD-comments-and-resolution-1116-v02.pdf http://ieee802.org/1/files/public/docs2016/cs-PAR-CSD-comments-and-resolution-1116-v02.pdf November 2016 doc.: IEEE 802-11-16/1326r2 November 2016 References IEEE 802 PARs Under consideration Webpage: http://grouper.ieee.org/groups/802/PARs.shtml Minutes: Previous Plenary: 11-16/986r0: <https://mentor.ieee.org/802.11/dcn/16/11-16-0986-00-0PAR-minutes- july-2016-session.docx> Current Meeting: 11-16/1486r0 < https://mentor.ieee.org/802.11/dcn/16/11-16- 1486-00-0PAR-minutes-november-2016-session.docx > Jon Rosdahl, (Qualcomm) Jon Rosdahl, (Qualcomm)