would only consume 1/32 of the operator's IPv6 address block (and operator would get more if the /32 proved to be too little). While IPv4 is seriously problematic for numbering IoT, IPv6 will have no issues. The need to deploy IPv6 for IoT is obvious. Signaling Will Increase It has been observed that already existing UEs, especially smartphones, can cause 3GPP networks to overload due to too much signaling traffic. The reasons can be, for example, the ones identified by 3GPP specification 23.843 [95]: Special mobility events causing registration floods: these can be caused by network attaches or location updating, for example when an airplane lands and people turn on their phones. 2. Radio Access Technology (RAT)-reselections caused by scattered 2G, 3G and 4th Generation (4G) network coverage causing (very) frequent intersystem handovers. 3. Restarting network nodes, such as Base Station Controller (BSC), Radio Network Controller (RNC), Serving Gateway Support Node (SGSN), or MME can trigger large numbers of registration attempts. 4. UEs causing a flood of events, such as bearer activations, Short Message Service (SMS) sending/receiving, or content polling/pushing by/to large numbers of nodes in the same area. Now, with the plans to add numerous smart objects into the 3GPP networks, the risks of signaling overload situations on the network grows even larger. The smart objects might be configured to transmit measurements at the same time, or there could just be a very large number of smart objects in the same network segments and hence problems caused by network element restarts or intersystem handovers due to bad coverage can exacerbate the signaling overload scenarios. Furthermore, signaling overload risks increase if IoT command and control node decides to poll information from large numbers of smart objects at the same time. To avoid signaling overloading, the IoT architecture itself, design of individual smart objects, deployment of IoT, and controllers of large smart object networks have to take mitigating a