Introduction
In Data Networking, there are two kinds of addresses; physical addresses (like MAC) and logical addresses (like IP). IP addresses and MAC addresses were developed around the same time but each was responding to a different problem. Consider the case of an Ethernet cable/segment over which several devices could be physically connected, and all have visibility to the signals transmitted onto the cable. In other words; all devices can hear all other devices, but each device has a unique identifier (MAC Address) with which they could address their data. This address would not prevent everyone else on the cable from seeing the data, but it would provide an indicator as to which, specific device was the intended recipient of that data. But because in the real-world nodes will not always be on the same segment, as the case of the public Internet, every data network node (host, router, or even a network printer)is assigned a logical global address (like IP) that is used to locate and identify the node in communications with other nodes.
In the IP world, if a device has several network interfaces, then each interface must have at least one distinct IP address assigned to it. For example, a laptop might have a wireless network interface and a wired network interface using a network cable, and this would require a total of two IP addresses, one per interface. Another example is a mobile phone with cellular data network and Wi-Fi. Routers, by nature, have several network interfaces and typically have several IP addresses associated with them. It is also possible that an interface can be assigned more than one IP address for various reasons(secondary addresses).The IPv4 addressing structure provides an insufficient number of publicly routable addresses to provide a distinct address to every Internet device or service. This problem has been mitigated for some time by changes in the address allocation and routing infrastructure of the Internet. This started by the transition from classful network addressing to Classless Inter-Domain Routing (CIDR), that delayed the exhaustion of addresses substantially. In addition, Network Address Translation (NAT) permits Internet service providers and enterprises to masquerade private network address space with only one publicly routable IPv4 address on the Internet interface of a customer premises router (CPE), instead of allocating a public address to each network device.
PROBLEMS
Address exhaustion is the depletion of the pool of unallocatedIPv4 addresses. Because there are fewer than 4.3 billion addresses available, depletion has been anticipated since the late 1980s, when the Internet started to experience dramatic growth. This depletion is one of the reasons for the development and deployment other alternatives solutions, likeIPv6.The main market forces that accelerated IPv4 address depletion included the rapidly growing number of Internet users, always-on devices, mobile devices and recently the Internet of Things (IoT). The Internet Engineering Task Force (IETF) created the Routing and Addressing Group (ROAD) in November 1991 to respond to the scalability problem caused by the classful network allocation system in place at the time. The anticipated shortage has been the driving factor in creating and adopting several new technologies, including NAT, CIDR in 1993, and IPv6 in 1998. IPv6, the successor technology to IPv4 which was designed to address this problem, supports approximately 3.4×1038 network addresses. Although as of 2008the predicted depletion was already approaching its final stages, most providers of Internet services and software vendors were just beginning IPv6 deployment at that time. The top-level exhaustion occurred on 31 January 2011. Four of the five RIRs have exhausted allocation of all the blocks they have not reserved forIPv6 transition; this occurred on 15 April 2011 for the APNIC, Asia-Pacific, on 14 September 2012 for RIPE NCC, Europe, Middle East and Central Asia, on 10 June 2014 for LACNIC, Latin America and the Caribbean, and on 24 September 2015 for ARIN North America. Individual ISPs still had unassigned pools of IP addresses, and could recycle addresses no longer needed by their subscribers. Each exhausted its pool of available addresses at different times.
The current centralized system to manage the global pool of IP addresses is centralized in five transnational organizations, the Regional Internet Registries (RIRs). Each of these RIRs manage the address pool for a large number of countries. Because the RIRs are private organizations, they are subject to the legal framework of the country where they are based. This configuration results in a jurisdictional overflow from the legal framework of the countries where the RIR is based to all the countries that the RIRs are serving (the countries served by the RIRs de facto become subjects of the legal system of the country where the RIR is hosted).Beside the centralized nature of address allocation, there is always the burden of recurring maintenance or renewal fees as well as the relatively hard re-allocation of resources among the different RIRs.
SOLUTION ATTEMPTS
Efforts to delay address space exhaustion started with the recognition of the problem in the early 1990s and the introduction of a number of stop-gap refinements to make the existing structure operate more efficiently, such as CIDR, NAT as well as strict usage-based allocation policies.
Other technologies include:
Use of NAT which allows a private network to use one public IP address and permitting private addresses in the private network
Use of private network addressing
Name-based virtual hosting of web sites
Tighter control by regional Internet registries on the allocation of addresses to local Internet registries.
Network renumbering and subnetting to reclaim large blocks of address space allocated in the early days of the Internet, when the Internet used inefficient classful network addressing.
###JACS AND BLOCKCHAIN
As previously explained, JACS utilizes blockchain to create a communications stack. Here the blockchain plays a vital role as the protocol that will support JACS. The blockchain will perform many functions such as Address allocation, Address registry, Route Origin verification, and validation, Incentivizing the community, etc. In this case, JACS will use the Ethereum blockchain as a protocol that will support the operation of the platform. But in the future JACS will launch its own native blockchain, namely “JACS native blockchain”, which runs on the native public blockchain instead of the Ethereum blockchain.
JACS
If we had the luxury of starting over from scratch, most likely we would have based the Internet on a new datagram internet protocol with much larger multi-level address structure. In principle, there are many choices available for a new datagram internet protocol. For example, the current IP could be augmented by addition of larger addresses, or a new protocol could be developed. However, the development, standardization, implementation, testing, debugging and deployment of a new protocol (as well as associated routing and host-to-router protocols) would take a very large amount of time and energy, and is not guaranteed to lead to success.
There is already such a protocol available. In particular, CLNP, that is very similar to IP, and offers the required datagram service and address flexibility, but that came with some differences as well.
CLNP addresses are assigned to nodes, not interfaces. This is the host-based addressing. All interfaces (even multi-access interfaces like LAN) are unnumbered and each node has a “loopback” interface with a single address (similar to the host /32 prefix in IPv4). While the concept was highly interesting and marginally more useful than subnet-based IP architecture, it also imposed additional burden on hosts and routers:
Hosts and routers had to run a host-to-router protocol among themselves that enables routers to find adjacent hosts and helps hosts to find the nearest router, this is the ES-IS protocol that basically does a similar job to what Router Advertisement(RA) does in IPv6.
ES-IS provides great failover, redundancy (in terms of first-hop routers) and hosts mobility.
Routers then have to propagate all hosts reachability information throughout the area so that each router in the area has to know the location of all hosts within the same area.
CLNP intra-area forwarding has some elements that could be similar to bridging (packets are forwarded based on host ID) but works as true routing (layer-2 encapsulation is changed and TTL is decreased whenever a packet is forwarded by a CLNP router). The number of hosts within an area is obviously limited by the routers’ capabilities (and can be quite limited in some actual CLNP implementations); to scale, CLNP introduced a concept of areas, which are almost identical to IP summary routes. Per-node addresses nicely solve intra-area multihoming. A host is always reachable through a single address, even if it has more than one interface. When an interface fails, the existing sessions are not disrupted (as they originate from an address that belongs to the node itself, not the failed interface). In the IP world there are some solutions that could provide the same result for multi-homing, like: NIC bonding, multi-chassis port channel and others.
ROADMAP
IN CONCLUSION
In line with technological developments such as IoT and the presence of the 5G network, there will be many devices in the world connected to the internet network. The TCP / IP technology we use today has many limitations and problems — JACK’s “Just Another Communications Stack” is a platform that utilizes blockchain and Connection-Less Network Services (CLNS) with its 160-bits ISO NSAP addresses. JACK aims to change the way data networks work and overcome various problems in internet protocols such as IPv4 address depletion, high recurring maintenance and renewal fees, etc.
Below is a link with accurate information about the JACS project:
Website : https://www.jacs.tech/
Whitepaper : https://www.jacs.tech/white-paper
Telegram : https://t.me/jacstech
Twitter : https://www.twitter.com/Moustafaamin77
Youtube : https://www.youtube.com/channel/UCICHtYggmdDTRJsPdOBs-GQ
Facebook : https://www.facebook.com/viaBlockLTD
Reddit : https://www.reddit.com/r/JACSTECH/
Linkedin : https://www.linkedin.com/company/viablock
Ann Thread : https://bitcointalk.org/index.php?topic=5279310.0
Name:Bayanganhitam
Profile:https://bitcointalk.org/index.php?action=profile;u=2851798;sa=summary
Eth:0xA95A2De787CA11c530978f0eFfcE7fB1bBbc664C