Because using any of the various tools used in this technology (IoT) to use an IP for identification, the number of IPs used will increase dramatically.
Is it necessary to transfer to a new Internet Protocol on the Internet of Things (IoT)?
Since, the main goal in IoT is to provide a platform wherein all identifiable heterogeneous objects such as smart phones or sensors can connect to the Internet, so it seems, introducing a flexible protocol is inevitable. In recent years the Internet Engineering Task Force (IETF) group has specified the IPv6 over Low power Wireless Personal Area Networks (6LoWPAN) standard for realizing the IoT idea.
Since, the main goal in IoT is to provide a platform wherein all identifiable heterogeneous objects such as smart phones or sensors can connect to the Internet, so it seems, introducing a flexible protocol is inevitable. In recent years the Internet Engineering Task Force (IETF) group has specified the IPv6 over Low power Wireless Personal Area Networks (6LoWPAN) standard for realizing the IoT idea.
Many communication technologies are well known such as WiFi, Bluetooth, ZigBee and 2G/3G/4G cellular, but there are also several new emerging networking options such as Thread as an alternative for home automation applications, and Whitespace TV technologies being implemented in major cities for wider area IoT-based use cases. Depending on the application, factors such as range, data requirements, security and power demands and battery life will dictate the choice of one or some form of combination of technologies. These are some of the major communication technologies on offer to developers.
Using a host-to-host communication paradigm to achieve the IoT vision has proven to be challenging. Several recent researches explore how Named Data Networking (NDN), a content-centered proposed future Internet architecture can help achieve the IoT vision in a more secure, straightforward, and innovation-friendly manner.
if I understood your question correctly, the answer is : eventually, yes we will need a new scheme or version of the current IPv4(which is IPv6 By the way) to be implemented through out the world. but for now the NAT protocol is helping a lot in reducing the number of required IP addresses for the now a days used devices. and if your question is how to transfer different data of different protocols used in IoT devices and sensors will the answer by using secure box's along with CBTA devices which will act as a media gateway to converge all used protocols to one of the Standard IP protocols.
The huge number if IP addresses usable with IPV6 is helpful to systems using IoT device communications. For communicating with IoT type devices that with network connectivity with high bandwidth, IPV4 and 6 are practical to use. When an IoT device is connected to the network using low bandwidth connections such as serial ports or long-range wireless, using a flexible and data efficient protocol can be used in the local network connection. These types of systems will use gateways that translate their efficient protocol over to IPV4/6. And having a flexible LAN protocol can easily enable thousands to millions of devices to connect to their LAN gateway, and the LAN gateway connects to the internet. It will appear to all devices and servers accessing these IoT devices on the LAN they they are IPV4/6 compatible even though they a different efficient and flexible protocol.
the IoT is an extension of the classic Internet, by connecting WSNs with different things. As a result, the IoT must also be an IP network. Therefore, the Internet Protocol (IP) must be used in the IoT (in fact in WSNs). Due to the large address space, only IPv6 can be used in the IoT. However, IPv6 needs to be adapted to the specifics of WSNs. This adaptation of IPv6 for use in IoT is called 6LoWPAN. This is shown in Figures 008202, 008204 and 008205 in [1] and Figure 2 in [2].
6LoWPAN is not a new protocol but just a compressed form of IPv6. In the IoT, more precisely in the WPANs according to the IEEE 802.15.4 standard, the entire IPv6 packet (IP header + UDP header + data) must not exceed 102 bytes in length. This is illustrated by the figures 008206 in [1]. For this reason, the two headers IPv6 and UDP must be compressed very much.
The IPv6 header can be compressed so much that only the "Hop Limit" field remains from the entire IPv6 header. The IoT uses the so-called Link Local IPv6 Addresses and these IPv6 Addresses are also used as MAC / Link Addresses and entered in the MAC header. This is illustrated by Figures 008207, 008208, 008209 and 008211 in [1] and Figures 3 and 4 in [2].
Conclusion: In the IoT a new Internet Protocol is not necessary, but the header of the old, well-known IPv6 protocol must be compromised.