Jul 12, 2010 07/12/10 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Response to PAR and 5C Comments Date Submitted: July 2013 Source: Clint Powell, Powell Wireless Commsulting, LLC Contact: Clint Powell, Powell Wireless Commsulting, LLC Voice: +1 480-586-8457, E-Mail: cpowell@ieee.org Re: Response to 802 Comments Abstract: Purpose: Layer 2 (Mesh Under) Routing Notice: This document has been prepared to assist the IEEE P802.15. 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 P802.15. Page 1

Comments Received from 802.11 doc.: IEEE 802.11-13/0789r1 July 2013 Comments Received from 802.11 PAR 1.2 Type of Document Is this really a Recommended Practice or a Standard? Yes, it is a recommended practice. A recommended practice is more appropriate to verify that this appropriately meets the market demands of 802.15.4 5.2 Scope Change to “This standard defines a protocol that routes packets in a dynamically changing network (changes on the order of a minute time frame), with minimal impact to route handling. Changed to “This recommended practice defines a protocol that routes packets in a dynamically changing network (changes on the order of a minute time frame), with minimal impact to route handling. 5.4 Purpose What L3 mechanisms are to be considered? The L3 mechanisms are described in IETF RFC4903 “Multilink Subnet Issues” Jon Rosdahl, CSR Technology Inc.

Comments Received from 802.11 (cont’d.) doc.: IEEE 802.11-13/0789r1 July 2013 Comments Received from 802.11 (cont’d.) PAR 8.1 Additional Explanatory Notes Clarify the relationship between 15.4e and 15.10. 802.15.4e (MAC enhancements) is anticipated to facilitate 802.15.10 Are there any new functions being added by 15.10? No functions are being added to IEEE 802.15.4 15.10 will have define IEEE 802.15.4 behaviors for routing Does 15.10 use only features previously defined by 15.4e? Yes Is 15.10 for use only with 15.4 based networks? Should the project be called 802.15.4.1 because this is a recommended practice (standard) for 15.4? While 15.10 is a recommended practice for IEEE 802.15.4, it keeps a clear distinction between the standard and the recommended practice This also provides a capability to extend the recommended practice to other IEEE 802.15 networks Jon Rosdahl, CSR Technology Inc.

Comments Received from Chair 802.19 doc.: IEEE 802.11-13/0789r1 July 2013 Comments Received from Chair 802.19 PAR 2.1 Title Change “dynamically changing wireless networks” to “dynamically changing wireless personal area networks” Change to “dynamically changing IEEE 802.15.4 networks” 5.2 Scope The scope says that this recommended practice “extends wireless networks.” It is not clear what is meant by “extend” in this phrase. Is the distance extended? Would the word “enhance” be a better word than “extend” in this scope? Change to ”extends the area of coverage of IEEE 802.15.4 networks” When you say that the network is “dynamically changing” are you saying that the network connections are changing due to mobility? Yes, among other s (see below). Please explain what is meant by “dynamically changing networks” in Section 8.1, Additional Explanatory Notes. Add to 8.1: “Dynamically changing networks refer to network connections changing due to mobility, signal impairments, and the transient nature of networks” Jon Rosdahl, CSR Technology Inc.

Comments Received from Chair 802.19 (cont’d.) doc.: IEEE 802.11-13/0789r1 July 2013 Comments Received from Chair 802.19 (cont’d.) PAR 5.2 Scope We suggest changing “This recommended practice will facilitate the routing of packets …” to “This recommended practice will provide recommendations on the routing of packets …” Agree 5.5 Need for the Project Please add an explanation in Section 8.1 on what is a “Field Area Network” Add to 8.1: The Field Area Network (FAN) may provide a connectivity path from field Distribution Automation (DA) devices to the substation upstream, or connectivity that bypasses the Substations and links the field DA devices into a centralized management and control system. Jon Rosdahl, CSR Technology Inc.

Comments Received from Chair Reg. Auth. Comm. doc.: IEEE 802.11-13/0789r1 July 2013 Comments Received from Chair Reg. Auth. Comm. PAR 6.1b Intellectual Property (registration activity) The practice of reducing EUI-64 addresses to effectively be EUI-48 addresses has been of concern to the Registration Authority Committee for some time. Because this proposed PAR is involved with bridging (L2 routing) of 802.15 frames, presumably would increase bridging of 802.15, is silent on any positive or negative impact on that practice of concern, and the practice of concern is mentioned in the 5C document, I am requesting that the answer to 6.1.b be changed to Yes. No, this recommended practice is not changing the MAC addressing used in IEEE Std. 802.15.4, therefore no changes to registration activity are required. Jon Rosdahl, CSR Technology Inc.

Comments Received from Chair 802 doc.: IEEE 802.11-13/0789r1 July 2013 Comments Received from Chair 802 PAR 5.5 Need for the Project "new route handling capabilities" is mentioned. It might be helpful to mention the current route handling capabilities this project is intended to enhance or replace. IEEE 802.15.4 does not define route handling, this recommended practice addresses routing practices needed for IEEE 802.15.4 networks such as those implementing IEEE 802.15.4g 8.1 Additional Explanatory Notes There is an implication that there are other standards with a similar scope. If true, please consider listing those standards. The practice of reducing EUI-64 addresses to effectively be EUI-48 addresses has been of concern to the Registration Authority Committee for some time. We are not addressing bridging across 48 and 64 bit networks. There are no standards or projects with a similar scope. Delete the following text in 8.1: (7.1) None that make use of the features provided by IEEE Std.802.15.4e-2012 Jon Rosdahl, CSR Technology Inc.

Comments Received from Chair 802.1 doc.: IEEE 802.11-13/0789r1 July 2013 Comments Received from Chair 802.1 Replace answer to 2. Compliance in 5C to: The PAR does not mandate compliance with IEEE Std. 802, IEEE Std. 802.1D or IEEE Std. 802.1Q. 802.15.10 will schedule joint meetings with 802.1 to facilitate review of the draft. For responses to additional questions see doc. # 15-13-0452-00. Jon Rosdahl, CSR Technology Inc.