[802SEC] 802.15 Comments on the 802c PAR
Here are some comments on the 802c PAR from members of 802.15 for your
Scope of the Project: The project scope is vague and confusing,
leaving it unclear what is expected as the outcome of this project.
Suggested changes: Include specifically in the scope that the
project will develop guidelines, techniques and strategies which
may be applied to management of local address spaces, and rules to apply
when the specific guidelines, techniques and strategies recommended are
Need for the Project: The sentence "Such protocols will allow
virtual machines and IoT devices to obtain a local address without local
administration." is self contradictory and technically
invalid: "This project will enable protocols that automatically
configure addresses from a portion of the local address space" would
be a method of local administration. Suggest deleting this sentence.
Also, the opening premise in the "need for the project" appears
based on the assumption virtual machines and IoT devices use EUI-48
addresses and ignores the far deeper EUI-64 address space used by many
(now approaching one billion and growing rapidly) 15.4 based IoT
devices. From explanations given in the ad-hoc discussion, it
appears the intent of the project is to address ONLY locally administered
EUI-48 address space. If this is the intent it should be clearly stated
in the project scope.
Bob Heile, Ph.D
Chairman Emeritus & Chief Technologist, ZigBee Alliance
Chair, IEEE 802.15 Working Group on Wireless Personal Area Networks
Co-Chair IEEE P2030 Task Force 3 on Smartgrid Communications
Chair IEEE 2030.5 Working Group for Smart Energy Profile 2
11 Robert Toner Blvd, Suite 5-301
North Attleboro, MA 02763 USA
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.