Two major versions exist: IPv4 and IPv6. IPv4 uses a 32‑bit numeric format written as four decimal octets separated by periods (e.g., 192.0.2.1). Its limited address space prompted the development of IPv6, which expands the addressing space to 128 bits and writes addresses in hexadecimal pairs separated by colons (e.g., 2001:0db8::1). IPv6 also offers simplified host configuration, built‑in packet authentication and privacy via temporary addresses.
IP addresses are categorized as public or private. Public IPs are routable on the global Internet and are typically assigned by ISP or RIRs. Private ranges, defined by RFC 1918 for IPv4 (e.g., 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) and RFC 4193 for IPv6 (fc00::/7), are reserved for use inside organizations and are not forwarded by external routers. Devices on a private network often use Network Address Translation (NAT) to share a single public IP address.
Dynamic Host Configuration Protocol (DHCP) automatically assigns IP addresses to devices in a network, reducing manual configuration. Static addressing is used where persistent identification is necessary, such as servers or network equipment. The Address Resolution Protocol (ARP) translates IP addresses to MAC addresses at the data link layer, enabling delivery within a local segment.
IP addressing governs routing decisions in the Internet Backbone. Routers evaluate the longest prefix match of destination addresses to determine the best forwarding path. Because IP addresses are both network and host identifiers, subnetting and CIDR notation (e.g., 192.168.1.0/24) provide flexibility in dividing address space and optimizing routing tables.
Security considerations arise from the public visibility of IP addresses. Transparent logging, geolocation, and tracing can potentially reveal user activity. Techniques such as VPNs, proxies, or Tor mix networks obscure source and destination addresses, providing anonymity and privacy.
The transition from IPv4 to IPv6 is gradual, driven by address exhaustion, improved fragmentation handling, and built‑in security features. Adoption requires compatibility layers, dual‑stack deployments, and updates to host software, routing protocols, and application logic. Continued research and policy efforts aim to balance efficient resource allocation, technical feasibility, and global Internet stability.
---