1. PAR Comment Responses Date: 2016-11-09 Authors: November 2016
Month Year
doc.: IEEE yy/xxxxr0
November 2016
PAR Comment Responses
Date:
Authors:
Notice: This document has been prepared to assist IEEE It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
Steve Shellhammer, Qualcomm
John Doe, Some Company

2. November 2016
802.3 Comments
Comment
PAR, General— We suggest the scope be broader and reflected in the title. The term vehicular environment would be better than automotive environment. Need and Stakeholders talk about vehicles. We believe the project should address motor coaches and other non-automobile highway vehicles? The Need (5.5 highlights traffic jams as a potential problem, and therefore, a motor coach could be a coexistence challenge. The Scope need an appropriate terminology change.
Response
Accept. Changed “automotive” to “vehicular”
Added the following to Section 8.1 “The term ‘vehicular’ in this context refers to vehicles that operate on roadways.”
Steve Shellhammer, Qualcomm

3. November 2016
802.3 Comments
Comment
Further the note in 8.1 to 5.2 belongs in the scope.
Response
Reject. It is our understanding that Section 8.1 is the appropriate location for an explanation of terms like “vehicular environment” (originally “automotive environment”)
Steve Shellhammer, Qualcomm

4. November 2016
802.3 Comments
Comment
PAR, 5.4 Purpose — Because Purpose is included in the standard, the statement should not include phrases like “typical scenarios the recommended practice will include:”. Could probably be rewritten “typical scenarios include:”
Response
Accept in principle. Used text provide by
Steve Shellhammer, Qualcomm

5. November 2016
802.3 Comments
Comment
CSD — The CSD document uses both automotive environment and vehicle, and therefore causes the same concerns as expressed in the first general comment. Please use vehicular environment.
Response
Accept. Changed “automotive” to “vehicular”
Steve Shellhammer, Qualcomm

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

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

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

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

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