1. Mar. 2018
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: [Draft PAR & CSD Comment Responses]
Date Submitted: [8 March, 2018]
Source: [Joerg ROBERT] Company [Friedrich-Alexander University Erlangen-Nuernberg]
Address [Am Wolfsmantel 33, Erlangen, Germany]
Voice:[ ], FAX: [ ],
Re: []
Abstract: [Comment resolution to comments on w PAR & CSD]
Purpose: [Information to 802 EC]
Notice: This document has been prepared to assist the IEEE P 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.
Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P
Joerg ROBERT, FAU Erlangen-Nuernberg

2. Draft 802.15.4w PAR & CSD Comment Responses
Mar. 2018
Draft w PAR & CSD Comment Responses
Joerg ROBERT (FAU Erlangen-Nuernberg), chair SG
Joerg Robert, FAU Erlangen-Nuernberg

3. In response to the comments from James Gilb
Mar. 2018
In response to the comments from James Gilb
Joerg Robert, FAU Erlangen-Nuernberg

4. Mar. 2018
PAR 5.2b
Comment: Add the anticipated range that this new PHY will provide. Delete "as needed“
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

5. Mar. 2018
PAR 5.5
Comment:
The text says that high link margin is required for interferers, but doesn't put a value on "high". What is high and why don't current PHYs in meet it?
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

6. Mar. 2018
PAR 5.5 cont’d
Comment:
140 dBm sensitivity implies -174 dBm/Hz + 10 dB SNR and NF gives -164 dBm/Hz, leaving only 24 dB for BW, or 251 Hz. That would likely give < 1 kb/s, which doesn't work for IoT. From where does this -140 dBm come?
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

7. Mar. 2018
PAR 5.5 cont’d
Comment: The end result is the inability to guarantee the required transmission reliability in such scenarios." Wireless networks can never "guarantee the required transmission reliability" and this project won't change that fact.
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

8. Mar. 2018
PAR 5.5 cont’d
Comment: "receiver sensitivities of -140dBm while delivering multiyear battery life." already provides multi-year battery life with the existing PHYs. There does not appear to be anything proposed with the amendment that would improve battery life. In fact, by spreading the information over a longer period of time, the receiver would be on longer, using more power, not less.
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

9. CSD 1.3 Comment: Quantify "high immunity to interference".
Mar. 2018
CSD 1.3
Comment: Quantify "high immunity to interference".
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

10. Mar. 2018
CSD 1.2.5
Comment: None of the reasons given address why this specific, new addition will be similar in cost to existing devices (which vary widely in cost, depending on which version of you implement). Are there LECIM devices fielded?
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

11. Mar. 2018
CSD cont’d
Comment:
The answer for c) does not address item c), which has to do with installation costs, no manufacturing methods.
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

12. In response to the comments from IEEE 802.3
Mar. 2018
In response to the comments from IEEE 802.3
Joerg Robert, FAU Erlangen-Nuernberg

13. PAR 5.3 Comment: Question is not answered, please do so.
Mar. 2018
PAR 5.3
Comment: Question is not answered, please do so.
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

14. Mar. 2018
PAR 6.1b
Comment: Not sure who recommended review but if so, the RAC Chair is unaware of a recommendation from the RAC or from editorial staff (typically occurring because of content found in MEC review). RAC review can also be requested by the WG/TG later without a PAR modification if "not anticipated" registry related content appears in the draft. Please refer to the PAR form instructions (copied at end of slide deck) for when a Yes answer is appropriate and consider if the answer should be changed to No. (The RAC has reviewed IEEE Std )
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

15. Mar. 2018
CSD 1.2.5c
Comment: The answer about manufacturing costs is non-responsive to the question about installation costs. Please provide a responsive answer.
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

16. Mar. 2018
CSD 1.2.5d
Comment:
Change IEEE Std to IEEE Std (remove the dot after Std).
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

17. In response to the comments from IEEE 802.11
Mar. 2018
In response to the comments from IEEE
Joerg Robert, FAU Erlangen-Nuernberg

18. PAR 2.1 Comment: Use of “Low Power” should include a range or limit.
Mar. 2018
PAR 2.1
Comment: Use of “Low Power” should include a range or limit.
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

19. PAR 2.1 cont’d Comment: expand “LEICM” Text in PAR/CSD:
Mar. 2018
PAR 2.1 cont’d
Comment: expand “LEICM”
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

20. PAR 5.2b Comment: editorial remove extra period “Std.” should be “Std”
Mar. 2018
PAR 5.2b
Comment: editorial remove extra period “Std.” should be “Std”
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

21. PAR 5.2b cont’d Comment: correct “<30kBit/s” should “< 30 kb/s”
Mar. 2018
PAR 5.2b cont’d
Comment: correct “<30kBit/s” should “< 30 kb/s”
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

22. PAR 5.2b cont’d Comment: expand “FSK” Text in PAR/CSD:
Mar. 2018
PAR 5.2b cont’d
Comment: expand “FSK”
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

23. Mar. 2018
PAR 5.2b cont’d
Comment:
delete “Furthermore, it defines lower code rates of the FEC in addition to the K=7 R=1/2 convolutional code. Modifications to the Medium Access Control (MAC) layer, needed to support this PHY extension, are defined as needed.” or at least reword to be definitive and define “lower code rates” and the reword to make meaning of “K=7 R=1/2 convolutional code” clear.
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

24. Mar. 2018
PAR 5.2b
Comment: define the expected range of “Wide Area Network”. i.e. what are you expecting to reach.
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

25. Mar. 2018
PAR 5.5
Comment: What is “very high link margin” vs “high link margin”? rewording is expected.
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

26. Mar. 2018
PAR 5.5 cont’d
Comment: Please include definition of the expected range and power that is being included in the specification.
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

27. Mar. 2018
PAR 5.5 cont’d
Comment:
“guarantee” reword this sentence as you will not be able to “guarantee” in general.
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

28. Mar. 2018
PAR 5.6
Comment: delete “and similar organtizations” – not necessary (and misspelled).
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg

29. PAR 8.1 Comment: Add full name of the cited “IEEE Std 802.11h.
Mar. 2018
PAR 8.1
Comment: Add full name of the cited “IEEE Std h.
Text in PAR/CSD:
Remarks / Answers to the Comments:
Joerg Robert, FAU Erlangen-Nuernberg