Skip to content

Network Layer

The transport-facing service level that identifies destinations and directs data across underlying links or subnetworks in a layered communication architecture.

Version
v1 · 2026-10-07 · History
Domain-specific #
13959
Domain group
Applied Sciences & Engineering
Origin domain
Computer Science & Software Engineering
Subdomain
Computer Networking → Computer Science & Software Engineering

Core Idea

The Network Layer in the OSI Basic Reference Model is the service level between Transport and Data Link that delivers data between transport entities, identifies destinations, uses routes and relays when needed, and hides some lower-network details. X.200 permits connection and connectionless modes, so connectionlessness does not define every network service.[^ref-946a209c4cbd]

The Internet architecture has a partly analogous Internet Layer. IP carries addressed datagrams toward destination hosts using local-network interfaces and gateways. RFC 1812 places the Internet Layer between Transport and Link. The comparison with OSI is an inference from these specifications, not a claim that their names, numbers or guarantees are exactly equivalent.[ref-946a209c4cbd][ref-a5238144d468][^ref-507ad2d1ccbf]

Scope of Application

X.200 defines the exact OSI Network Layer service role: transfer between transport entities, network addressing, route/relay functions, and lower data-link or subnetwork support. It is a conceptual reference model rather than proof of a particular deployed network.[^ref-946a209c4cbd]

RFC 791 describes an IPv4 Internet Layer with source and destination addresses, gateway forwarding when required, and local-network interfaces below. IP is connectionless and does not promise end-to-end reliability; those are IP-specific properties. RFC 1812 also warns that some older Internet documents called the Link Layer “Network Layer,” a different usage from OSI.[ref-a5238144d468][ref-507ad2d1ccbf]

Clarity

Name the architecture first. Then identify the upper transport user, network destination, route or relay capability, and lower link or subnetwork carriage. A router, one packet format or a whole protocol stack does not itself establish this single service level. A local Link Layer with only directly attached transfer is also a near miss, even when older terminology calls it “Network Layer.”[ref-946a209c4cbd][ref-507ad2d1ccbf]

State the particular service mode and guarantees separately. A direct route need not pass through an intermediate router. Connection-mode network service can use packet switching; connection mode alone does not distinguish a layer from a switching method.[ref-946a209c4cbd][ref-a5238144d468]

Manages Complexity

The boundary lets transport users request destination-directed transfer without specifying each data-link segment or subnetwork on the path. X.200 describes this masking of lower differences, while RFC 791 separates host-to-host protocols above IP from local-network interfaces below it. The simplification does not erase each architecture's mode and quality limits.[ref-946a209c4cbd][ref-a5238144d468]

Abstract Reasoning

Suppose a level accepts transport data, identifies a destination, and can direct it using lower links. It meets the mapped network-service role. Remove the upper/lower service boundary and destination forwarding may still exist, but there is no layer as such. Remove the destination/path role and the case becomes local link transfer rather than the mapped Network Layer service.[ref-946a209c4cbd][ref-a5238144d468]

Changing OSI's service from connectionless to connection-mode keeps it within X.200's Network Layer. IP remains a connectionless Internet Layer case. Thus the shared role concerns placement and delivery function, not one universal packet or reliability profile.[ref-946a209c4cbd][ref-a5238144d468]

Knowledge Transfer

Transfer the service-role questions between OSI and Internet documents, but keep their terminology and guarantees distinct. The broad structural relation belongs to the live Layering Prime: an upper service depends on a lower one through a boundary. The network-addressed transport-facing transfer role is the narrower domain-specific child. A generic organizational “middle layer” lacks its communication-service identity.[ref-946a209c4cbd][ref-507ad2d1ccbf]

Example

OSI model. Transport entities use X.200's Network Layer for transparent transfer. Network addresses, route/relay functions and lower data-link or subnetwork facilities fill the destination, path and carriage roles. Connection and connectionless modes are both within the model.[^ref-946a209c4cbd]

IPv4 Internet Layer. Host-to-host protocols pass data and destination parameters to IP. IP uses a destination address and local-network interface to reach a gateway or final host; RFC 1812 places it between Transport and Link. Its connectionless datagram profile is local to this example.[ref-a5238144d468][ref-507ad2d1ccbf]

Relationships to Other Abstractions

Local relationship map for Network LayerParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Network LayerDOMAINPrime abstraction: Layering — presupposesLayeringPRIME

Current abstraction Network Layer Domain-specific

Parents (1) — more general patterns this builds on

  • Network Layer presupposes Layering Prime

    A network service layer presupposes a layered architecture with upper transport and lower link or subnetwork service boundaries.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

Network Layer sits in a sparse region of the domain-specific corpus (91st percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Network Architecture & Transport Protocols (25 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-08

Not to Be Confused With

A Link Layer, router, routing algorithm, packet-switching method or whole protocol stack is not the entire transport-facing network service level. Older Internet “Network Layer” terminology sometimes meant Link Layer. Nor does this entry require every architecture to be OSI layer three, every path to have intermediate routers, or every network service to be connectionless and unacknowledged. Its sole strict graph edge is composition/presupposes → Layering.[ref-946a209c4cbd][ref-a5238144d468][^ref-507ad2d1ccbf]

References

[^ref-507ad2d1ccbf]: F. Baker, Requirements for IP Version 4 Routers, RFC 1812 (1995), §2.2.1, printed pp.17–18. Baker is credited as editor of this RFC. Full RFC Editor specification inspected. Places Internet Layer between Transport and Link and records the older Internet usage of “Network Layer” for Link Layer. The OSI/Internet Network role analogy in this entry is a cross-source inference, not a direct claim by this RFC.

[^ref-a5238144d468]: Jon Postel, Internet Protocol, RFC 791 (1981), §§1.1–1.4 and §2.4, printed pp.1–3, 9. Full RFC Editor specification inspected. Defines IP datagram transfer, addresses, path/gateway roles, upper and lower interfaces, and IP-specific connectionless/no-end-to-end-reliability limits.

[^ref-946a209c4cbd]: ITU-T, Recommendation X.200, Information technology, Open Systems Interconnection, Basic Reference Model, the Basic Model, 1994, §7.5, printed pp.41–44 (official PDF pp.44–47). Full official standard inspected. The published title uses punctuation between the title components; comma transcription here keeps the complete linked title legible to the reference binder. §§7.5.2–7.5.4 define the transport-facing network service, connection and connectionless modes, routing/relay, lower-facility use, error notification and optional receipt confirmation. This is a conceptual reference model, not a deployment report.