TCP/IP

 
    TCP/IP, or Transmission Control Protocol/Internet Protocol, was developed to establish a standard for communication, ensuring that a universal method is adopted regardless of the vendor or equipment used. This standardization allows for seamless communication within a network, whether it includes equipment from Nokia, Fortinet, Palo Alto, or Cisco.

 Before the TCP/IP was developed, vendors pretty much ran their own protocols and thus communicating was an issue. This was one of the issues faced by the US Department of Defense.  The first solution was NCP (network control protocol) with ARPAnet. They quickly realized that NCP had limitations. It could only go as far as next hops. Which is usually within the same network. So technically the network has to keep growing for devices to reach each other. Since I prefer a different network for my privacy, just like you, it won't be feasible to have one massive network worldwide. The TCP/IP was put together to deal with assigning IP addresses to hosts and unifying how they talk to each other. The Ip portion handles the addressing rules and the TCP portion handles the communication rules.  We will dive into both partitions in details. 

   One of the rules about the IP portion is, no two devices or Hosts across the world should have the same internet IP. Indeed, you may have noticed devices with the same IP addresses in different locations; this is due to the use of private IPs that do not connect to the internet. I will delve into this topic in a subsequent chapter. On the internet, each device is assigned a unique address. To enforce this rule we have organizations tasked for these enforcement and management. The Picture for IANA's and the regional authorities coverage.