# Can We Skip the Network Layer?

DevFeed: [Can We Skip the Network Layer?](<https://devfeed.tech/articles/can-we-skip-the-network-layer-10950.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2024/02/skip-network-layer/>)

Published: 2024-02-12T09:52:00Z

Content type: article

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [Network](<https://devfeed.tech/topics/network.md>), [Ethernet](<https://devfeed.tech/topics/ethernet.md>), [Protocol (disambiguation)](<https://devfeed.tech/topics/protocol.md>), [Terminal](<https://devfeed.tech/topics/terminal.md>)

Tags: [boot](<https://devfeed.tech/tags/boot.md>), [bridging](<https://devfeed.tech/tags/bridging.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [cycles](<https://devfeed.tech/tags/cycles.md>), [digital](<https://devfeed.tech/tags/digital.md>), [ethernet](<https://devfeed.tech/tags/ethernet.md>), [memory](<https://devfeed.tech/tags/memory.md>), [network](<https://devfeed.tech/tags/network.md>), [networking-fundamentals](<https://devfeed.tech/tags/networking-fundamentals.md>), [physics](<https://devfeed.tech/tags/physics.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [run](<https://devfeed.tech/tags/run.md>)

## AI overview

The article examines proposals to omit network-layer addressing from local solutions by using Ethernet data-link addresses with transport protocols directly above them. It recounts how DEC's LAT and MOP protocols placed local terminal services over Ethernet, and explains how requirements spanning multiple Ethernet segments exposed the approach's limitations and led to transparent bridging.

## Source excerpt

I mentioned that you don't need node addresses when dealing with only two entities. Now and then, someone tries to extend this concept and suggests that the network layer addressing isn't needed if the solution is local. For instance, if we have a solution that is supposed to run only on a single Ethernet segment, we don't need network layer addressing because we already have data link layer addresses required for Ethernet to work (see also: ATAoE). Too often in the past, an overly ingenious engineer or programmer got the idea to simplify everyone's life and use the data link layer addresses as the ultimate addresses of individual nodes. They would then put the transport layer on top of that to get reliable packet transport. Finally, put whatever application on top of the transport layer. Problem solved. Read more ...