Fact-checked by Grok 2 weeks ago

Network address

A network address is an identifier for a computer network or subnetwork within a larger network topology, enabling the routing of data packets to the appropriate segment.^[1] In the Internet Protocol (IP) suite, which forms the foundation of modern internetworking, a network address refers to the network portion of an IP address—a 32-bit (for IPv4) or 128-bit (for IPv6) numerical label that is structured into a network portion, identifying the overall subnet or segment, and a host portion, specifying the individual device within that segment; for example, in IPv4, the network address for a subnet might be represented with all host bits set to zero, such as 192.168.1.0 for a /24 network.^[1]^[2] Network addresses play a critical role in enabling scalable communication across diverse network environments, from local area networks (LANs) to the global internet, by supporting protocols like TCP/IP for reliable data transmission and fragmentation.^[1] They are managed through mechanisms such as subnetting, which divides larger networks into smaller subnetworks for efficient resource allocation and traffic control, and address translation techniques like Network Address Translation (NAT), which allow private internal addresses to map to public ones for internet access.^[3] Evolving standards, including the transition from IPv4's limited address space (approximately 4.3 billion unique addresses) to IPv6's vastly expanded pool (about 3.4 × 10^38 addresses), address the growing demand for connectivity in an era of billions of internet-connected devices. Beyond IP, network addresses can encompass other protocols, such as MAC addresses at the data link layer for local network identification, though these are distinct from routable layer-3 addresses.

Fundamentals

Definition

A network address is a unique or semi-unique identifier assigned to a node, host, or device on a telecommunications network to enable communication and routing of data packets.^[4] In IPv4 networks, a network address serves as a 32-bit number distinguishing sources and destinations among interconnected systems.^[5] These addresses facilitate the identification of endpoints in packet-switched environments, allowing routers and switches to direct traffic efficiently across local or global scopes.^[4] Network addresses exhibit various characteristics depending on their design and purpose. They can be flat, such as Media Access Control (MAC) addresses, which are 48-bit non-hierarchical identifiers assigned by manufacturers for local network communication within a single broadcast domain.^[6] Alternatively, they may be hierarchical, like IP addresses, which are structured into network and host portions to support scalable routing across multiple domains.^[4] Hosts often possess multiple addresses per interface, enabling multi-homing or support for different communication protocols.^[7] Address types include globally unique identifiers for internet-wide reachability, local or private addresses valid only within an enterprise (e.g., the 10.0.0.0/8 block, which requires no global coordination), and special forms like broadcast addresses for all nodes in a subnet or multicast addresses for group delivery to selected recipients.^[8]^[9] The concept of network addressing evolved from early packet-switched systems in the 1970s, beginning with the ARPANET's Network Control Protocol (NCP) for host identification in 1970, to the foundational TCP/IP protocols published in 1974.^[10] The transition to TCP/IP as the ARPANET standard in 1983 marked a shift to hierarchical addressing, with the Internet Engineering Task Force (IETF), established in 1986, subsequently developing and standardizing modern schemes like the Domain Name System (DNS) introduced in 1984 for address resolution.^[10]

Distinction from Host Address

In IP networking, the full address, such as an IPv4 address, is a 32-bit identifier divided into a network portion and a host portion. The network portion specifies the particular network or subnet to which the address belongs, while the host portion identifies the specific device within that network. This division allows for hierarchical addressing, where the network address represents the shared prefix common to all hosts in the subnet, effectively identifying the entire group rather than an individual endpoint.^[4] The primary purpose of the network address is to facilitate inter-network routing, enabling routers to determine the path for packets destined for a specific network without needing to know the individual host details. In contrast, the host address supports intra-network delivery, allowing devices within the same network to communicate directly by resolving the unique identifier of the target host. This functional separation ensures efficient packet forwarding across the internet, as routers can aggregate traffic based on network prefixes while local switches or hosts handle the final delivery using the host identifier.^[4]^[11] For example, consider an IP address of 192.168.1.10 with a subnet mask of /24, which allocates the first 24 bits to the network portion. Here, the network address is 192.168.1.0, shared by all devices in the subnet, while the host address .10 uniquely identifies the particular device. This setup ensures that packets addressed to any host in 192.168.1.0/24 are routed to the correct network, with local resolution handling the specific host.^[4]

IP-Based Network Addresses

IPv4 Network Addresses

IPv4 network addresses are part of the 32-bit addressing scheme defined in the Internet Protocol version 4 (IPv4), where each address consists of four 8-bit octets typically represented in dotted decimal notation, such as 192.168.1.0.^[4] The address space is divided into a network portion, which identifies the overall network, and a host portion, which specifies individual devices within that network, though the exact division was historically determined by classful addressing. In the original classful system, addresses were categorized into classes A, B, and C for unicast communication, based on the leading bits of the first octet: Class A addresses (first octet 1-126) allocate the first 8 bits to the network portion and the remaining 24 bits to hosts, supporting up to 16,777,214 hosts per network; Class B addresses (first octet 128-191) use the first 16 bits for the network and 16 for hosts, accommodating up to 65,534 hosts; and Class C addresses (first octet 192-223) dedicate the first 24 bits to the network and 8 to hosts, allowing up to 254 hosts.^[12] Class D (first octet 224-239) and Class E (first octet 240-255) were reserved for multicast and experimental use, respectively, without a traditional network-host split.^[12] The allocation of IPv4 addresses is managed by the Internet Assigned Numbers Authority (IANA), which delegates blocks to regional internet registries for further distribution to organizations.^[13] Public IPv4 addresses, routable on the global internet, comprise the majority of the 4.3 billion possible addresses but have been subject to conservation measures due to rapid exhaustion; by the early 1990s, projections indicated the address space would deplete within years, prompting the adoption of Classless Inter-Domain Routing (CIDR) in 1993 to enable more flexible prefix lengths beyond class boundaries.^[14] Private IPv4 address ranges, not routable on the public internet, were designated to alleviate scarcity for internal networks: these include 10.0.0.0/8 (over 16 million addresses), 172.16.0.0/12 (over 1 million addresses), and 192.168.0.0/16 (65,536 addresses).^[8] Examples of IPv4 network addresses illustrate their practical use; for instance, 192.168.0.0/16 serves as a private network address for local area networks, where the /16 prefix denotes the network portion covering all addresses from 192.168.0.0 to 192.168.255.255.^[8] Within a specific subnet like 192.168.1.0/24, the network address is 192.168.1.0 (all host bits set to 0), while the broadcast address—used to send data to all hosts on the network—is derived by setting all host bits to 1, resulting in 192.168.1.255.^[12] These conventions, rooted in the classful model, persist in modern configurations despite the shift to classless addressing.

IPv6 Network Addresses

IPv6 addresses are 128-bit identifiers that form the foundation of network addressing in the Internet Protocol version 6, providing a hierarchical structure to support scalable global routing.^[15] Unlike IPv4, IPv6 employs no fixed classes for address allocation; instead, it uses variable-length prefixes to denote network portions, allowing flexible subnetting and aggregation.^[15] The typical structure divides the 128-bit address into a 64-bit network prefix, which identifies the subnet for routing purposes, and a 64-bit interface identifier, which uniquely identifies a host within that subnet.^[15] This design yields a total address space of $2^{128}, or approximately $3.4 \times 10^{38} unique addresses, enabling the protocol to accommodate the growth of internet-connected devices without the limitations faced by IPv4.^[16] Standardized in RFC 4291 in February 2006, IPv6 was developed to address the impending exhaustion of IPv4 addresses, which had reached critical depletion by the early 2010s.^[17]^[18] Key address types include global unicast addresses, allocated from the 2000::/3 prefix for routable communication across the internet; unique local addresses, using the fc00::/7 prefix for site-internal communications without global routability; and link-local addresses, starting with fe80::/10 for automatic configuration and communication on a single network segment.^[15]^[19] For documentation and testing purposes, the prefix 2001:db8::/32 is reserved, ensuring examples do not conflict with production networks.^[15] These features emphasize IPv6's focus on simplicity, security, and end-to-end connectivity in modern networks.

Calculation and Representation

Subnet Masks

A subnet mask is a 32-bit value used in IPv4 to divide an IP address into network and host portions, consisting of contiguous 1 bits from the left to indicate the network bits followed by 0 bits for the host bits.^[20] This mask functions by performing a bitwise AND operation with the IP address, which isolates the network address by preserving only the bits that align with the 1s in the mask while setting host bits to zero.^[20] For IPv6, the equivalent is a 128-bit prefix that similarly delineates the network portion through a specified number of leading bits, though it is not typically represented as a dotted-decimal mask but operates on the same bitwise principle.^[21] Subnet masks are commonly notated in dotted-decimal form for IPv4, such as 255.255.255.0, which corresponds to the binary pattern 11111111.11111111.11111111.00000000 and masks the first 24 bits as network.^[20] An alternative notation is the prefix length in CIDR format, like /24, indicating the number of network bits.^[21] In classful IPv4 addressing, default masks align with address classes: Class A uses /8 (255.0.0.0) for an 8-bit network field, Class B uses /16 (255.255.0.0) for a 16-bit network field, and Class C uses /24 (255.255.255.0) for a 24-bit network field.^[4] To derive the network address, apply the formula: Network Address = IP Address bitwise AND Subnet Mask. For example, with IP address 192.168.1.10 (binary: 11000000.10101000.00000001.00001010) and subnet mask 255.255.255.0 (binary: 11111111.11111111.11111111.00000000), the bitwise AND yields 192.168.1.0 (binary: 11000000.10101000.00000001.00000000), identifying the network portion.^[20] This operation ensures that all hosts within the same subnet share the same network address, facilitating efficient routing and address management.^[20]

Classless Inter-Domain Routing (CIDR)

Classless Inter-Domain Routing (CIDR) is a method for allocating IP addresses and aggregating routes in IPv4 networks, allowing variable-length subnet masks that extend beyond traditional class boundaries to improve address efficiency.^[22] Standardized in RFC 1519 in September 1993, CIDR was developed to address the rapid exhaustion of IPv4 address space, particularly the overuse of Class B networks which provided far more addresses than most organizations needed, while Class C networks were too small for larger entities.^[22] It enables flexible prefix lengths, denoted in slash notation as an IP address followed by a forward slash and the number of significant bits in the prefix (e.g., 192.168.0.0/23 specifies a 23-bit prefix, encompassing 512 total addresses).^[23] One of the primary benefits of CIDR is route aggregation, which summarizes multiple smaller networks into a single routing entry, significantly reducing the size of routing tables in Internet backbone routers and slowing their growth from an unsustainable rate.^[22] For instance, supernetting allows the combination of adjacent networks, such as merging two /24 networks into a /23 supernet, enabling a single advertisement for what would otherwise require multiple entries.^[23] This aggregation not only conserves global routing resources but also supports scalable hierarchical address assignment by Internet service providers.^[22] A practical example of CIDR aggregation is the prefix 10.0.0.0/9, which combines multiple subnets within the 10.0.0.0/8 range (originally a Class A network) into a larger block suitable for regional allocation.^[23] The total number of addresses in a CIDR block is calculated as $2^{(32 - \text{prefix length})}, including the network and broadcast addresses; for /9, this yields $2^{23} = 8,388,608 addresses, with usable host addresses being two fewer to reserve those special ones.^[23] Similarly, 192.168.0.0/23 aggregates two /24 networks, providing 512 addresses in total (usable: 510).^[23]

Advanced Concepts and Applications

Network Address Translation (NAT)

Network Address Translation (NAT) is a method for remapping one IP address space into another by modifying network address information in the headers of IP packets while they are in transit across a traffic routing device, such as a router or firewall. This technique enables transparent routing to hosts in an isolated address realm, typically by translating private internal IP addresses to a public external IP address, thereby conserving the scarce pool of globally routable IPv4 addresses. NAT is particularly vital in scenarios where the number of devices exceeds available public IPs, allowing an entire private network to connect to the internet via a single public address.^[24] The core functionality of NAT involves rewriting the source or destination IP addresses (and often transport-layer identifiers like TCP/UDP ports) in packet headers as they pass through the translating device. For outbound traffic from private devices, the internal source address is replaced with the public IP of the router, and return traffic is demultiplexed back to the correct internal host using port mappings or other session tracking mechanisms. This process supports multiple private devices sharing one public IP, addressing IPv4 address exhaustion without requiring changes to end-user applications in most cases. Private networks commonly utilize address ranges reserved for internal use, such as 192.168.0.0/16, to avoid conflicts with public addressing.^[24]^[8] NAT operates in several variants, as defined in the terminology and considerations outlined in RFC 2663. Static NAT establishes a one-to-one mapping between a private IP and a specific public IP, providing a fixed translation that persists for the duration of the NAT device's operation and is often used for servers requiring consistent external access. Dynamic NAT extends this by drawing from a pool of available public IPs, assigning them temporarily to private hosts on a first-come, first-served basis and releasing them when sessions end, which optimizes public address utilization for varying traffic loads. Port Address Translation (PAT), also known as NAT overload or Network Address Port Translation (NAPT), enhances efficiency further by multiplexing multiple private hosts onto a single public IP through port number translations, enabling thousands of internal devices to share one external address via unique port combinations.^[24] A practical example illustrates NAT's operation: a device with private IP 192.168.1.10 sending outbound traffic might have its source address translated to the router's public IP 203.0.113.5, with an ephemeral port (e.g., 50000) mapped to distinguish the session. Incoming responses are then routed back using the reverse mapping, ensuring seamless connectivity. Beyond address conservation, NAT provides a security benefit by obscuring the internal network topology from external observers, as the private structure remains invisible to the public internet and only explicitly permitted connections can traverse the boundary.^[24]^[25]

Hierarchical Addressing and Routing

Hierarchical addressing in IP networks organizes addresses into multiple levels of granularity, enabling scalable routing from global internet-scale paths to local subnet delivery. At the highest level, the Border Gateway Protocol (BGP) uses Autonomous System (AS) numbers to define large routing domains, where each AS represents a collection of networks under a single administrative control, facilitating inter-domain routing decisions.^[26] Within an AS, interior gateway protocols like Open Shortest Path First (OSPF) divide the network into areas, with the backbone area (Area 0) interconnecting subordinate areas to manage intra-domain hierarchy.^[27] This structure progresses to progressively finer levels, such as routing domains, subnets, and individual hosts, allowing routers to aggregate and summarize routes efficiently across scales.^[28] Routers leverage network addresses for packet forwarding by consulting their forwarding information bases (FIBs), which store routes as prefixes associated with next-hop information. The core mechanism is the longest prefix match algorithm, where the router selects the route with the most specific prefix length that matches the destination IP address, ensuring packets follow the optimal path without ambiguity.^[12] For instance, a destination address of 10.144.2.5 would prefer a /24 prefix like 10.144.2.0/24 over a broader /16 prefix like 10.144.0.0/16.^[12] In hierarchical routing, OSPF propagates inter-area route summaries via Area Border Routers (ABRs) using Type 3 Link State Advertisements (LSAs), which aggregate intra-area networks into concise summaries flooded only within the receiving area to minimize update overhead.^[27] Similarly, BGP advertises aggregated prefixes between ASes, employing the AS_PATH attribute to track traversed AS numbers and prevent loops while enabling policy-based path selection at the global level.^[26] Address aggregation, primarily through Classless Inter-Domain Routing (CIDR), addresses challenges in maintaining compact routing tables amid growing address fragmentation, by combining contiguous prefixes into supernets for advertisement. However, aggregation can lead to suboptimal routing if prefixes do not align perfectly, potentially increasing convergence times or blackholing traffic during failures. IPv6 addresses these issues by providing a vastly larger address space (128 bits versus IPv4's 32 bits), supporting longer prefixes like /48 for sites and /64 for subnets, which simplifies hierarchical allocation and reduces the need for frequent aggregation while maintaining routing table efficiency. For example, a route to the prefix 2001:db8:1::/48 might be advertised by a provider's edge router, directing traffic to an enterprise site without exposing internal subnet details.

References

[1]
None
### Summary of IP Addresses, Network Addresses, and Their Use in Internet Protocol (RFC 791)
[2]
TCP/IP addressing and subnetting - Windows Client - Microsoft Learn
Jan 15, 2025 · IP--The network protocol used for sending network packets over a TCP ... Network address--An IP address with a host portion that is all zeros.Summary · IP addresses: Networks and...
[3]
https://www.cisco.com/en/US/docs/security/vpn5000/manager/reference/guide/appA.html
[4]
RFC 791 - Internet Protocol - IETF Datatracker
The internet protocol is designed for use in interconnected systems of packet-switched computer communication networks. Such a system has been called a catenet.<|separator|>
[5]
https://datatracker.ietf.org/doc/html/rfc1208
[6]
[PDF] mac-address format - IEEE 802
IEEE Std 802-2014 and IEEE Std 802c-2017 provide the IEEE definition of MAC addresses (Clause 8) l. Hyphen: Hexadecimal representation is a sequence of octet ...Missing: flat hierarchical
[7]
RFC 6419 - Current Practices for Multiple-Interface Hosts
... address corresponding to the preferred network interface. Per-interface IP stacks also allow to manage overlapping address spaces. When multiple network ...
[8]
RFC 1918 - Address Allocation for Private Internets - IETF Datatracker
This document describes address allocation for private internets. The allocation permits full network layer connectivity among all hosts inside an enterprise.Missing: telecommunications | Show results with:telecommunications
[9]
RFC 5771 - IANA Guidelines for IPv4 Multicast Address Assignments
This document provides guidance for the Internet Assigned Numbers Authority (IANA) in assigning IPv4 multicast addresses.Missing: characteristics | Show results with:characteristics
[10]
https://datatracker.ietf.org/doc/html/rfc2235
[11]
Understand Host and Subnet Quantities - Cisco
The network address is used to identify the network and is common to all the devices attached to the network. The host (or node) address is used to identify a ...
[12]
RFC 1812 - Requirements for IP Version 4 Routers - IETF Datatracker
The simplest classical network prefix is the Class A, B, C, D, or E network prefix. These address ranges are discriminated by observing the values of the ...
[13]
IPv4 Address Space - Internet Assigned Numbers Authority
Oct 10, 2025 · Originally, all the IPv4 address spaces was managed directly by the IANA. Later parts of the address space were allocated to various other ...Ipv4-address-space.txt
[14]
RFC 1519 - Classless Inter-Domain Routing (CIDR) - IETF Datatracker
RFC 1519 CIDR Address Strategy September 1993 5.1 Address allocation ... Eventual exhaustion of the 32-bit IP address space. It has become clear that ...
[15]
RFC 4291: IP Version 6 Addressing Architecture
This specification defines the addressing architecture of the IP Version 6 protocol. It includes the basic formats for the various types of IPv6 addresses.
[16]
IPv4 vs IPv6 - Difference Between Internet Protocol Versions - AWS
The full address space of IPv4 is 2³², or 4,294,967,296 IP addresses. IPv6 has a significantly higher address space of 2¹²⁸, or 3.403×10³⁸, or 340,282,366,920, ...Key differences: IPv4... · How does IPv6 improve on IPv4?
[17]
Information on RFC 4291 - » RFC Editor
This specification defines the addressing architecture of the IP Version 6 (IPv6) protocol. The document includes the IPv6 addressing model.
[18]
IPv4 exhaustion and address transfers, and their impact on IPv6 ...
IPv6 is designed to invisibly replace IPv4, making no immediate difference to Internet users; therefore Internet Service Providers do not experience demand ...
[19]
RFC 4193 - Unique Local IPv6 Unicast Addresses - IETF Datatracker
This document defines an IPv6 unicast address format that is globally unique and is intended for local communications, usually inside of a site.
[20]
RFC 950 - Internet Standard Subnetting Procedure - IETF Datatracker
This memo discusses the utility of "subnets" of Internet networks, which are logically visible sub-sections of a single Internet network.
[21]
RFC 4291 - IP Version 6 Addressing Architecture - IETF Datatracker
This specification defines the addressing architecture of the IP Version 6 protocol. It includes the basic formats for the various types of IPv6 addresses.
[22]
RFC 1519: Classless Inter-Domain Routing (CIDR)
CIDR is a strategy for address assignment and aggregation, topologically allocating IP space to routing domains, to conserve address space and slow routing ...
[23]
RFC 4632 - Classless Inter-domain Routing (CIDR) - IETF Datatracker
This memo discusses the strategy for address assignment of the existing 32-bit IPv4 address space with a view toward conserving the address space.
[24]
RFC 2663 - IP Network Address Translator (NAT) Terminology and ...
Network Address Translation is a method by which IP addresses are mapped from one realm to another, in an attempt to provide transparent routing to hosts.Missing: telecommunications | Show results with:telecommunications
[25]
What Is Network Address Translation (NAT)? - Fortinet
Improved security: NAT can provide a measure of security by hiding the internal network from the outside world. This can be useful for preventing attacks ...How Does Nat (network... · Why Is Nat Important? · Types Of Network Address...Missing: topology | Show results with:topology
[26]
RFC 4271: A Border Gateway Protocol 4 (BGP-4)
Summary of each segment:
[27]
RFC 2328: OSPF Version 2
Below is a merged summary of the OSPF Propagation of Route Summaries in Hierarchical Addressing based on RFC 2328. To retain all information in a dense and organized manner, I’ve used a combination of narrative text and a table in CSV format where applicable. The response consolidates all key details, concepts, and references from the provided segments while avoiding redundancy and ensuring clarity.
[28]
RFC 1518 - An Architecture for IP Address Allocation with CIDR
The objective behind the use of hierarchical routing is to achieve some level of routing ... routing domain which would currently require 4 different IP networks.