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

2. Abstract-Snapshot Nov 6-11, 2016, San Antonio, TX, USA
November 2016
doc.: IEEE /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
Amendment: Low-power wake-up radio operation, PAR and CSD
– 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)

3. PAR Review SC – November 2016 Chair: Jon Rosdahl
doc.: IEEE /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 WG closing plenary
Adjourn
Jon Rosdahl, (Qualcomm)
Jon Rosdahl, (Qualcomm)

4. Motion to Approve Previous Minutes
November 2016
Motion to Approve Previous Minutes
Move to approve doc 11-16/0986r0 < 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)

5. November 2016
Par Review Comments
Jon Rosdahl, (Qualcomm)

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

7. 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)

8. 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 What is IS-IS? Please expand.
Jon Rosdahl, (Qualcomm)

9. 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 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 – <full title of standard.>
Jon Rosdahl, (Qualcomm)

10. November 2016
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)

11. November 2016
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 devices in the 2.4 GHz band.
Interference between IEEE devices and non IEEE devices in the 2.4 GHz band.
Non-IEEE 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)

12. November 2016
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)

13. 802.11 Amendment: Low-power wake-up radio operation, PAR and CSD
November 2016
doc.: IEEE /1326r2
November 2016
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)

14. 802.11 Amendment: Low-power wake-up radio operation, PAR and CSD
November 2016
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 standard periodically wake up from a sleep… “
To “Devices based on the IEEE power save modes periodically wake up from a sleep…”
Change “Therefore, for the standard to be competitive, the IEEE 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)

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

16. IEEE 802.19.2 response November 2016
   IEEE would like to thank and for their time reviewing and commenting on the PAR and CSD.
               Here is a link to the responses to the comments we received on the PAR and CSD,
              
               The CSD has been updated to implement the changes as per the above document,
              
               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 response
Jon Rosdahl, (Qualcomm)

17. November 2016
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

18. November 2016
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

19. 802.11 Comments Comment 5.4 change “for example” to “such as”
November 2016
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

20. November 2016
Comments
Comment
5.4 change “The typical scenarios the recommended practice will include: Interference among IEEE devices in the 2.4 GHz band. Interference between IEEE devices and non IEEE devices in the 2.4 GHz band. Non-IEEE 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

21. 802.11 Comments Comment 5.5 replace the Need for Project with
November 2016
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

22. November 2016
In response to comments received on the wake-up radio (WUR) PAR and 5C,  these documents have been revised. The comment responses are in document . The updated PAR is The updated CSD is
WUR Response
Jon Rosdahl, (Qualcomm)

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

24. Comments from 802.11 PAR SC on PAR
November 2016
doc.: IEEE /1326r2
November 2016
Comments from 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)

25. Comments from 802.11 PAR SC on PAR
November 2016
doc.: IEEE /1326r2
November 2016
Comments from 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 r9
Minyoung Park (Intel Corporation)
Osama Aboul-Magd (Huawei Technologies)

26. Comments from 802.11 PAR SC on PAR
November 2016
Comments from PAR SC on PAR
Comment:
5.5 suggested changes:
Change “Devices based on the power save modes of the IEEE standard periodically wake up from a sleep… “
To “Devices based on the IEEE power save modes periodically wake up from a sleep…”
Change “Therefore, for the standard to be competitive, the IEEE 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)

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

28. November 2016
IEEE 802.3cg
Jon Rosdahl, (Qualcomm)

29. November 2016
Response from 802.3cg
IEEE would like to thank IEEE 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 < 00EC-ieee-p802-3cg-draft-par.pdf >.
Jon Rosdahl, (Qualcomm)

30. 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 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 Mb/s single-pair interfaces. 5.5 Change IEEE to IEEE Std
Jon Rosdahl, (Qualcomm)

31. November 2016
IEEE 802.3cg
• 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 – IEEE Standard for Ethernet”.
Jon Rosdahl, (Qualcomm)

32. IEEE 802.1CS Response November 2016
The responses to the comment are here:
The PAR has been updated:
The updated CSD:
IEEE 802.1CS Response
Jon Rosdahl, (Qualcomm)

33. November 2016
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)

34. Change MRP "802.1Q Multiple Registration
November 2016
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)

35. 5.5 – Quantify: smaller vs bigger – give numeric range for each.
November 2016
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)

36. 1.2.1 –MRP acronym expansion needed. Response:
November 2016
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)

37. 1.2.3 LRP and LLDP expansion needed Response:
November 2016
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)

38. Suggestion – add a use case example to expand the 2nd paragraph 1.2.4.
November 2016
Comment #6 on CSD:
Suggestion – add a use case example to expand the 2nd paragraph
Response:
The text in 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)

39. November 2016
Final Report to
Jon Rosdahl, (Qualcomm)

40. November 2016
Report to
IEEE PAR Review SC report to WG. The Standing Committee reviewed 6 PARs. Feedback for 802.1CS (slide 8), 802.3cg (slide 9), (slides 10-12) and WUR (slides 13-14) was provided by the Tuesday 6:30pm deadline. Responses were received from (slides 17-21), 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)

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

42. References IEEE 802 PARs Under consideration Webpage: Minutes:
November 2016
doc.: IEEE /1326r2
November 2016
References
IEEE 802 PARs Under consideration Webpage:
Minutes:
Previous Plenary: 11-16/986r0:
< july-2016-session.docx>
Current Meeting: 11-16/1486r0
< PAR-minutes-november-2016-session.docx >
Jon Rosdahl, (Qualcomm)
Jon Rosdahl, (Qualcomm)