{"id":82596,"date":"2026-09-23T14:02:24","date_gmt":"2026-09-23T17:02:24","guid":{"rendered":"https:\/\/a3aengenharia.com\/?post_type=articles&p=82596"},"modified":"2026-09-23T14:02:24","modified_gmt":"2026-09-23T17:02:24","slug":"ip-addressing-routing-structures-fundamentals-protocols-engineering-practices","status":"publish","type":"articles","link":"https:\/\/a3aengenharia.com\/en-us\/content\/technical-articles\/ip-addressing-routing-structures-fundamentals-protocols-engineering-practices\/","title":{"rendered":"IP Addressing and Routing Structures: Fundamentals, Protocols, and Engineering Practices"},"content":{"rendered":"\n

Addressing and routing structures define how an IP network identifies its segments and selects the paths used by packets<\/strong>. A consistent design needs to coordinate the IPv4\/IPv6 plan, prefixes, subnets, gateways, summarization, routing tables, dynamic protocols, redundancy, policies, observability, and documentation.<\/p>\n\n\n\n

Addressing should not be treated as simple distribution of IP numbers, nor routing as a later device-configuration task. The two disciplines form a single architecture: the way address blocks are reserved affects summarization, convergence, segmentation, troubleshooting, multi-site expansion, and integration with the internet, cloud, OT, IP video surveillance, and other systems.<\/p>\n\n\n\n

In corporate and mission-critical networks, the objective is to achieve a structure that is predictable, scalable, documentable, and verifiable<\/strong>, capable of growing without prefix overlap, maintaining coherent paths during failures, and allowing operations teams to understand why particular traffic follows a given path.<\/p>\n\n\n\n\n

IP Addressing: Structure, Function, and Engineering Objectives<\/h2>\n\n\n\n

An IP address identifies an interface in an Internet Protocol architecture and allows hosts and routers to determine whether a destination is on the local network or whether the packet should be forwarded to a gateway. The effectiveness of the addressing plan directly affects subnet organization, summarization capability, and the clarity of routing policies.<\/p>\n\n\n\n

IPv4<\/h3>\n\n\n\n

IPv4 uses 32-bit addresses, normally represented as four decimal octets, such as 192.168.10.25<\/code>. The separation between the network portion and the host portion is determined by prefix length, for example \/24<\/code>.<\/p>\n\n\n\n

The historical Class A, B, and C model helped shape IP-network terminology, but modern designs use CIDR \u2014 Classless Inter-Domain Routing<\/strong>. Therefore, the historical class of an address should not determine current network sizing.<\/p>\n\n\n\n

The private blocks defined by RFC 1918 remain widely used in internal networks:<\/p>\n\n\n\n

Private IPv4 block<\/td>Aggregate prefix<\/td>Typical use<\/td><\/tr>
10.0.0.0 to 10.255.255.255<\/td>10.0.0.0\/8<\/td>organizations requiring large internal address space<\/td><\/tr>
172.16.0.0 to 172.31.255.255<\/td>172.16.0.0\/12<\/td>corporate networks and segmented environments<\/td><\/tr>
192.168.0.0 to 192.168.255.255<\/td>192.168.0.0\/16<\/td>smaller networks and local segments<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Selection of the internal block should consider not only address quantity but also coexistence with VPNs, partners, acquisitions, temporary networks, cloud services, and possible future overlaps.<\/p>\n\n\n\n

IPv6<\/h3>\n\n\n\n

IPv6 uses 128-bit addresses represented in hexadecimal and was developed primarily to expand address space and modernize IP operation. An address such as 2001:db8:10:20::1\/64<\/code> may represent an interface on an IPv6 subnet.<\/p>\n\n\n\n

IPv6 changes several design elements: autoconfiguration, Neighbor Discovery, routing, DNS, multicast, filtering, logging, and dual-stack operation. It should not automatically be considered more secure<\/strong> than IPv4. Security still depends on policies, hardening, access control, monitoring, and correct configuration.<\/p>\n\n\n\n

In projects that still operate predominantly on IPv4, it is advisable to avoid decisions that would prevent future IPv6 adoption, especially in naming, IPAM, equipment, firewalls, monitoring, and operational processes.<\/p>\n\n\n\n

Public, Private, and Special-Purpose Addresses<\/h3>\n\n\n\n

In addition to private blocks, the plan needs to distinguish public, loopback, link-local, multicast, documentation, and other reserved address spaces. This classification prevents special-purpose ranges from being misused as ordinary corporate networks.<\/p>\n\n\n\n

Global authority over address spaces is coordinated by IANA, with regional distribution through the Regional Internet Registries. In private networks, the organization becomes responsible for its own internal governance.<\/p>\n\n\n\n\n

CIDR, Prefixes, and Subnetting<\/h2>\n\n\n\n

CIDR replaced fixed-class logic with variable-length prefixes. A prefix \/24<\/code>, \/27<\/code> or \/30<\/code> expresses how many bits represent the network, allowing subnet size to be adapted to the actual requirement.<\/p>\n\n\n\n

Detailed planning of masks, host counts, and block subdivision is discussed in greater depth in the article on IPv4 Subnetting and Subnet Sizing<\/a>.<\/p>\n\n\n\n

Subnets Should Be Created from a Hierarchy<\/h3>\n\n\n\n

Instead of creating the next available range at every expansion, the design should reserve blocks using stable criteria, for example:<\/p>\n\n\n\n

  • site or region;<\/li>
  • segment function;<\/li>
  • corporate, OT, or security environment;<\/li>
  • criticality;<\/li>
  • administrative domain;<\/li>
  • growth capacity;<\/li>
  • summarization requirements.<\/li><\/ul>\n\n\n\n

    A multi-site structure may, for example, reserve an aggregate per site and subdivide it internally among users, servers, Wi-Fi, video surveillance, access control, voice, and management.<\/p>\n\n\n\n

    Example of an IP Addressing Hierarchy by Organization, Site, and Function<\/title>