1.3 Network Types and Characteristics in Focus ---------------------------------------------- (a) "Mobile Adhoc networks (MANET) are self-configuring _infrastructureless_ networks of mobile devices connected by wireless technologies." --> Why is a differentiation being made between MANETs and other types of wireless networks? Couldn't moblie phones technically fit into the IoT as well? Is the differentiation only made based on the _infrastructureless_ part of it? If so, does it make sense to have categories of infrastructure and infrastructureless, rather than MANET and non-MANET networks? (b) "Wireline non-constrained networks are mainly used for specific applications like Building Automation or Infrastructure Monitoring. However, wireline and wireless networks with multi-hop or point-to- multipoint connectivity are especially in the interest of the analysis on the management of constrained devices in this document." --> This paragraph is unclear. What is it trying to convey? Is it saying that only wireline multi-hop and point-to-multipoint are within the scope of this document? Why not regular wireline networks that may have constrained devices as part of a non-constrained network? --> There is talk about bandwidth, but not frame size, which is likely to have a bigger impact than the overall bandwidth available in a channel. Maybe this should be mentioned? 1.6. Managing the Constrainedness of a Device or Network --------------------------------------------------------- (a) "might only be able to support one simple communication protocol, i.e. the management protocol needs to be possible to downscale from constrained (C2) to very constrained (C0) devices" --> Is it important that the same management protocol be applicable to the entire range of constrained devices? Why not allow the capabilities of the management protocol to scale up and down with the type/capabilities of the device at hand? SOLUTION: A new bullet point stating that different management protocols work on different class of devices. (b) "might only be able to support limited or no user and/or transport security" AND "might only be able to support very simple encryption" --> Simple encryption doesn't make sense, maybe it should be efficient encryption instead? (c) "might also need energy-efficient key management algorithms for security." --> Not just energy-efficient, but also memory, processing and etc. efficient. No? SOLUTION: Change text to only efficient key management.