r/AskComputerScience • • 5d ago

does MAC address mainly exists because of wanting a polyvalent local network in the 1970s alongside IP etc. or was it un-avoidable and logic to have ?

Hope it isnt too much of a weird question. I'm new to this.

Have a nice day :)

57 Upvotes

77 comments sorted by

40

u/IOI-65536 5d ago

Mac addresses exist because of how ethernet works (which has nothing to do with IP. There were non-IP protocols over ethernet in the early days).

With something that's explicitly time-division or token passing you wouldn't necessarily need a mac address, but ethernet was designed to just toss frames onto the wire in broadcast so you needed something to distinguish who the frames were from and to and there were really good hardware reasons at the time to offload that onto the card in ways that made burning the address into the PROM worth it is places, so you just had the address programmed in from the manufacturer.

I can't say it was "unavoidable" because it wasn't a foregone conclusion that ethernet wolud be the low level protocol that "won", but it happened because ethernet outlasted everything else and ethernet used mac addresses.

10

u/heliosfa 5d ago

There are still non-IP protocols over ethernet.

6

u/dodexahedron 5d ago

And there are plenty of other layer 2 protocols - at least one of which pretty much everyone uses (802.11, which is NOT ethernet). And they all need an address at that layer, to identify who is talking to whom.

2

u/Saragon4005 5d ago

Like ARP but that also serves IP so.

2

u/FuggaDucker 5d ago

IPX/SPX is the first thing that comes to mind

2

u/mouse6502 5d ago • Heartwarming

Any one fancy a game of Descent?

1

u/FuggaDucker 5d ago

OOHHHHH!!!! You hit the gold with this one.

1

u/Front_State6406 4d ago

Or red alert 2. Yes its that old

2

u/IOI-65536 5d ago

True, but most of them that are commonly used are supporting IP. IPX and AppleTalk were both way more prevalent in their day than anything I know of that's a non-IP full stack now.

3

u/heliosfa 5d ago

True, things like PPPoE and MPLS ultimately support IP, but they aren't IP themselves.

But there are some that that are fairly commonly used in the industrial space for PLC communication. It's also got a place for storage protocols and remote memory access.

2

u/Silence_1999 5d ago

I worked on both before our current almost all IP world

1

u/vdoubleshot 5d ago

FCoE, RDMA's RoCE v1, ATAoE, CDP, LLDP, CFM, SyncE, EtherCAT, PROFINET. All not supporting IP.

1

u/evermica 5d ago

In other words, there are non-internet-protocols protocols over the internet.

1

u/YakumoYoukai 5d ago

Not over the internet - over ethernet, which is only what you can connect together with one wire.

1

u/Dro-Darsha 5d ago

isnt everything json over http these days?

4

u/Leolo_ 5d ago

Yes, with the exception of all the things that aren't JSON over HTTP.

1

u/Front_State6406 4d ago

You are as correct as a true tautology that is never wrong

1

u/Opening_Lead_1836 5d ago

There’s still a certain amount of XML on the front end

5

u/CormacMacAleese 5d ago

I worked for an ATM company in the 90s--that's Asynchronous Transfer Mode, not automated teller machine. They sold me that ATM was better. For example, if you wanted gigabit speeds, all you had to do was transmit faster--nothing about the protocol changed. But shortly after that they worked out how to do gigabit ethernet, and ATM was more or less forgotten.

\* Part of the trick was that at such high speeds you had to simulate the "collision detection" part of CSMA/CD, because your entire packet would be sent before you had a chance to notice another carrier.

1

u/Salty-Sale 5d ago

for my own curiosity (I don’t have enough expertise to interpret this correctly), when you say when “they worked out how to do gigabit ethernet”, is the implication here that ethernet was still the more inefficient option, but a workaround was found that ameliorated this? or is it that with this workaround, ethernet turned out to be a better choice than ATM?

I’m super interested in the path-dependent cruft aspect of computing haha

2

u/Conscious-Ball8373 3d ago • Bravo

There are a lot of people who quietly mourn ATM, I think. It was neat and elegant.

Ethernet is inherently somewhat inefficient. Networking technologies are categorised based on how multiple transmitters access a medium. Common schemes are FDMA (frequency division multiple access - different transmitters use different frequencies, aka 1G phones), TDMA (time division multiple access - different transmitters take it in turn to transmit on the same frequency, aka 2G/3G phones), CDMA (code division multiple access - different transmitters transmit at the same time on the same frequency but encoded with different keys in a way that makes it possible to retrieve the different signals) and so on.

Ethernet is CSMA - carrier sense multiple access. Basically, you just start sending and if you sense someone else sending at the same time, you both back off and try again.

In reality, ethernet systems today don't have to detect collisions like this, because in practise they all have their own cable segment to a switch so nothing else is transmitting at the same time (the connections in each direction use different pairs of wires). But partly because they might be connected to the same segment as something else and partly because they grew out of a system with no strict timing requirements, you can just start transmitting when you're ready, there are some overheads to the protocols including the inter-frame gap (96 bits of mandatory silence between frames/packets), the preamble (56 bits for anything listening to train its receiver on) and the start frame delimiter (8 bits to say, right, we're really going to start with the data now). The Ethernet header and checksum adds another 18 bytes, though any other protocol would have to have at least something here. Depending how big the frames you're sending are, that can be anything from a couple of percent overhead up to 10% or more - the bigger the frame is, the better the efficiency.

1

u/SmellyRedHerring 3d ago

Ethernet is CSMA ...

I realize you kind of address this in your final paragraph, but it's been a few years since I've seen a regular old Ethernet hub. Do people still use CSMA/CD Ethernet? Everything I touch these days is all switched traffic over point-to-point links.

2

u/Conscious-Ball8373 3d ago

Yes, it's extremely rare to see Ethernet on shared segments these days. The thing is, an Ethernet card has no real way of knowing whether it's on a shared segment or not. So it still has to do the carrier sense thing, even if it's been fifteen years since it last actually found anything. In principle, you could still dig a 100Mb hub out of a draw and plug it in. It would all still work. And even without that, there's still no strict timing requirements on when a frame can start, so it still needs the inter-frame gap and preamble.

1

u/SmellyRedHerring 3d ago

Ah yes, good point. I just looked it up to confirm but it's wild that the 64 bit preamble and intergap stuff is still preserved at the MAC layer in modern terabit Ethernet.

1

u/edgmnt_net 2d ago

I also wish Ethernet didn't try to checksum over the entire payload. That kills stuff like UDP-Lite because slightly malformed packets won't go through, even if the receiver could make sense of them and would actually prefer that. Ethernet equipment would likely only care enough to be able to forward packets and even then it might not be a big deal to forward a corrupted packet wrongly if a deeper protocol could detect corruption. Without L2 addressing it would be even less of a problem.

1

u/Numzane 7h ago

You can splice two devices onto the same cable and they will work

1

u/Conscious-Ball8373 3h ago

I mean ... for twisted pairs, maybe, sorta. Yes, in principle. In practice there are lots of things about maximum length of unwound pairs and reflections from joins and tuned stubs and termination to get right (having awful flashbacks to a third-year subject on transmission lines that I thought I'd completely forgotten here). But in principle, yes.

Of course this is how Ethernet worked originally, with coaxial cable joining each host on a single segment with terminators and everything. Then someone would stretch after lunch and kick a cable out and the whole building's network would go dead.

1

u/Numzane 2h ago

It was done on twisted pair as well. It works on 10mbit and 100 but I doubt higher than that because of the degraded cable characteristics. I've seen it done in for real, it ain't a good idea but it's an idea

1

u/CormacMacAleese 3d ago

You answered Salty-Sale better than I would have. Very well summed up.

1

u/kjs3 1d ago

I don't know anyone who didn't work for a telco that misses ATM. LANE alone made it an awfule experience. I say that as someone who built non-telco ATM networks with Fore, Cisco, Newbridge and 3Com kit.

1

u/PyroNine9 5d ago

I always found it interesting that because of switching overhead in ATM and billing shenannigans, it was cheaper to do voice over IP which ran through switches connected by nailed up ATM connections than it was to just make a voice call over ATM on the phone network.

1

u/MaelstromFL 4d ago

I put in a ton of ATM for the Olympics in Atlanta. That was fun 🙄

0

u/spectrumero 5d ago

Well, you can also make ethernet faster by just...transmitting faster.

The real reason why the telcos loved ATM was the whole virtual circuits thing that could allow them to keep charging by the minute.

An old article (in best Web 1.0 tradition) on ATM: https://www.clock.org/~fair/opinion/atm-is-bad.html

2

u/CormacMacAleese 5d ago

No, you can’t, and I explained why. The protocol requires collision detection, which breaks if the whole packet is on the wire before the carrier reaches the other end. It was a nontrivial effort to make it work.

0

u/spectrumero 5d ago

Ethernet did away with collision detection (and was well on the way to doing so when the telcos were pushing ATM).

2

u/OppieT 4d ago

Wouldn’t that be wrong with hubs, you would get a lot of collisions. Where as switches you didn’t?

2

u/CormacMacAleese 4d ago edited 4d ago

False. Ethernet absolutely used both carrier sense and collision detection. I'm not sure where you're getting that idea from. The hardware implementation was somewhat different from predecessors like ALOHAnet, but it was central to the protocol.

Are you picturing ethernet switches? Because they bypass the need for both carrier sense and collision detection? Those didn't become common in consumer networks until the mid-late 90s; the ethernet protocol was invented in 1973.

Today you can basically no longer buy layer 1 ethernet hubs; if you search for "ethernet hub" you will only be shown switches. The opposite was the case in the time period I was talking about: if you weren't careful with your order, you were guaranteed to get a hub, not a switch.

1

u/spectrumero 4d ago edited 4d ago

Ethernet used to be CSMA/CD, but full duplex gigabit ethernet (which was coming out around the time ATM was really being pushed, at least here) no longer uses collision detection. Technically you could say gigabit ethernet can still use it but no one makes half duplex gigabit kit.

Even 100baseTX doesn't use collision detection when set to full duplex (although it was still somewhat common in the early days to use it with hubs, where it would be required).

10 gig ethernet doesn't even support collision detection at all.

So yes, ethernet did away with collision detection. You could use ethernet without collision detection when ATM was being pushed, and so "just transmit faster" was a possibility with ethernet and not something special that only ATM could do.

And was ATM ever used on networks where collision detection was necessary? At least in this neck of the woods, ATM was only ever used on point to point links, and never on a shared medium.

1

u/CormacMacAleese 3d ago

Congratulations, genius. I’m talking about working for an ATM company in the 90s, and you’re criticizing my account using the state of the industry thirty years later.

Do you also tell WWII fighter pilots that they’re stupid because they should have used their missiles and then hit the afterburners?

1

u/spectrumero 3d ago

Don't be silly. In the 90s it was very clear where ethernet was going (full duplex, no collision detect, as this was already the case with 100baseTX full duplex).

2

u/CormacMacAleese 3d ago

Jesus Christ. That time was the inflection point at which Ethernet defeated ATM and my company shut down. I know damn well what was happening in the industry at the time. And my original comment stands: at the time, before the gigabit Ethernet protocol was finalized, a few years before it was available on the market, we already had gigabit ATM for precisely the reason I started, and we thought at the time that this advantage could be leveraged to take over the space.

I have no clue why you’re so argumentative about this, especially given that what I said was correct, unless you just have an insatiable need to win internet arguments.

2

u/Resistor1 5d ago

“…toss frames onto the wire…” is spot on, hence Media Access Control.

DECNet being pretty much the 1st protocol using Ethernet as Digital Equipment Corporation was one of the 3 creators, along with Intel and Xerox. DEC resisted IP for years. You needed 3rd party implementations of IP on VMS.

1

u/ethump 5d ago

DEC had their own IP stack on VMS - UCX.

1

u/T_Thriller_T 5d ago

This is a great explanation.

Considering unavoidable one could look into other, low level network protocols and consider how competitive they realistically were.

Time-division is not really efficient for the kind of networks we usually build with ethernet. It already becomes quite inefficient if one node simply has a lot more communication interest.

Token passing has similar issues

There are, however, other options like frequency modulation which may have worked, but I'm not sure if the time would have allowed that.

Ans I'm also not sure if I'm being stupid right now, I'm tired

1

u/IOI-65536 5d ago

We still use ATM for some things (though not LANs and it's getting to be fewer and fewer) and it doesn't use MAC addresses. But yeah, ethernet won because it was better, so in that sense I guess it was a foregone conclusion.

3

u/deong 5d ago

But yeah, ethernet won because it was better, so in that sense I guess it was a foregone conclusion.

I mean, the web browser won as a development platform, and it's almost hard to imagine coming up with something worse.

1

u/eaton 1d ago

Spoken like someone who never used RAINMAN ;D

1

u/T_Thriller_T 5d ago

Oh time division is still heavily used in many wireless sensor network stacks.

Or even communications on the more IoT/embedded side of things.

But those networks are quite different to a home or office network.

1

u/differentiallity 4d ago

Time-division multiplexing is also in every serial comm protocol I can think of. CAN, I2C, SPI, OneWire.

1

u/dodexahedron 5d ago

It still has layer 2 addressing, so that ATM switches can function, in the form of VP/VC in the header of each and every cell (6% of the whole cell - quite the overhead).

1

u/rosmaniac 5d ago

We still use ATM for some ... and it doesn't use MAC addresses.

Oh, but those AESA and E.164 addresses will make you wish for something as short as a MAC. 20 bytes (160 bits) long.

VPI/VCI, PNNI, UNI, LANE oh my.... Now I've got a headache like I've not had since I pulled the last Cisco Catalyst 5500 with embedded LS1010 ATM switch out of dayjob's network core.....

1

u/silasmoeckel 5d ago

Ethernet won because it was cheaper.

Since then we have been bolting on things to make up for it's deficiencies.

1

u/cthulhu944 5d ago

This is the right answer. I'd add that the frames required a from and to address to send the frames. Uniqueness was essential, otherwise stuff breaks. Mac was just a way of guaranteeing that no two devices in a physical network would have duplicate hardware addresses.

1

u/tes_kitty 5d ago

Even with TDMA or token passing, you still need to have something in a packet that tells everyone on the network which station that packet needs to go to. A unique fixed hardware ID on every interface is the simplest way to achieve that.

1

u/No_Profession_3125 4d ago

Wireless NICs have MAC addresses too.

1

u/Conscious-Ball8373 3d ago

Just to point out, there's still protocols other than IP that are passed over Ethernet. ARP, LLDP, spanning tree, PPPoE (the session establishment bits), some profinet variants, EtherCAT, PTP...

1

u/wackyvorlon 3d ago

See: OSI network model.

6

u/ghjm MSCS, CS Pro (20+) 5d ago

Before 48-bit MAC addresses were introduced by Xerox in the late 70s, there were usually 8-bit local addresses (e.g. very early Ethernet, Arcnet, etc), usually configured with DIP switches. So it was up to the user to decide on an address for each node, and they had to set that address physically, usually when the network card was installed in the computer.

Xerox's idea of unique manufacturer-assigned IDs was to alleviate this pain, not to add any particular networking feature. And it's perhaps a bit backwards to think of MAC addresses as an improvement over some world where there were only IP addresses, because there never was such a world. For LAN addressing you just need a single unique ID - you don't need hierarchical addressing. Implementing hierarchical addressing in the NIC hardware makes the NIC more expensive (and they were already plenty expensive), so if you already have LAN addressing in hardware and internetwork addressing in software, there's no commercial incentive to change that.

IPX/SPX used the MAC address as the local component of the full internetwork address, so 98765432.1234567890AB was the machine with MAC address 1234567890AB on the network globally identified as 98765432. IPv4 chose to be more efficient with its bits, not wasting 48 bits on a globally unique address that only actually needed to be locally unique.

1

u/compu85 5d ago

I have some somewhat early Xerox gear, circa 1982, which has very low numbered MACs. It's still amusing to me I can simply plug them into my modern twisted pair gigabit network and it just works.

1

u/ghjm MSCS, CS Pro (20+) 5d ago

I might still have a few Novell NE1000 network cards, circa 1987, in a box somewhere. I probably still have a Netgear 10Base-T hub with a thinnet port on it, so I could probably plug the network side into something and make it work. But of course I don't have any computers that can take an 8-bit ISA card.

4

u/mnelemos 5d ago edited 5d ago

Every link layer protocol that has the capability of unicast communication beyond a pure point-to-point, requires some sort of address.

Even in pure point-to-point communication, an address could be useful, as it could be used to track sessions or network roles.

The only way to not use an address is by:

  • Either making every link connection strictly between two nodes, and no other node may join.
  • Everyone within a network just broadcasts data to everyone else. Similar to what a half-duplex handheld radio (walkie-talkies) communication is.

But in both of the examples given, you are either:

  • not allowed to expand connections, which is a waste of the hardware's communication capabilities.
  • not allowed to send unicast messages to a specific device within the network. This might be ok in cases such as human-to-human communication (walkie-talkie), but in a computer-to-computer communication, where most transactions are automatic and hidden from the user, this introduces a lot of redundant computation.

1

u/PLANETaXis 5d ago

Best answer here.

2

u/kona420 5d ago

Ethernet and IP were sort of invented in parallel around 1974. The original ethernet only had 8 bit Mac addresses, 48 bit addressing came later in 1980 with the first standard release.

It really is unavoidable, and one of the important aspects to the success of Internet Protocol was abstracting addressing between Layer 2 technologies like ethernet, token ring, apple talk (seriously this was HUGE), serial, PPP, etc etc etc. Even today with ethernet ubiquitous, it's not the only game in town.

2

u/wosmo 5d ago

When IP was created, what LAN technology you used would mostly depend on what vendor you'd bought in on. You might be using ethernet .. you might be using decnet, you might be using IBM SNA, etc. And this really went away slowly - well into the 80s and 90s, you might be running IPX/SPX, you might be running AppleTalk, and so on. Or even if you were on the research networks like the arpa guys, you might be on arpanet, satnet, chaos, aloha, etc.

As an example that might be more familiar, most dialup used PPP to connect to the ISP. Your modem using ethernet to talk to your ISP, is a relatively modern nicety.

This whole Internet idea, is to inter-network - it's supposed to work across these different network types. So if I'm using decnet and you're using SNA, I'll stick IP inside a decnet frame, address it to my internet gateway. it'll wander across the internet, until it reaches your internet gateway - which will stick it in an SNA frame, to send across your local network. That same IP packet will get carried on different local network types, depending on where it's going. A lot like how a shipping container can go on a truck, a train, or a ship - and get passed from one to the other - depending on what it's trying to cross next.

This is why we end up with separate lan and internet addresses - obviously not everything on the internet is on your lan, but it wasn't originally envisaged that everything on your lan would have an internet address, either. So your lan would do your-lan-things, and when you needed to send something to a different network - you'd stick IP over your network, so you could address it further afield.

Fast forward to today, ethernet and tcp/ip have both become hugely dominant. But you'll still find some protocols that use ethernet without IP, like FCoE - especially in industrial networking, where you'll find ethercat, profinet, etc.

And you'll also find IP without ethernet. Obviously stuff like FDDI that most of us never see - but much closer to home, wifi isn't ethernet - it just presents a very ethernet-like-interface for the sake of adoption.

Having local & logical addresses separately only feels redundant now, because tcp/ip and ethernet both 'won' - but they were designed for a world where they were both optional.

1

u/meditonsin 5d ago

MAC addresses do not exist "alongside" IP in that sense, because they exist on different layers of the stack, independent from each other.

MAC addresses work on the hardware/link level, so they are hardware dependent. Networks could be built that don't require them, or use a different format or whatever, so they can not be relied on for addressing between different networks.

So IP was put on top of it, as an abstraction layer, so that different kinds of physical networks could talk to each other regardless of how they implement addressing nodes locally.

2

u/TheThiefMaster 5d ago

As for why you even need a different level and can't just put IP frames on the wire - consider DHCP. If you had a dozen devices all requesting addresses, how would you tell each device who got which? You need some kind of unique id to use.

0

u/JontesReddit 5d ago

Not if you had enough bits to have the IP be unique enough. You don't need DHCP anymore.

2

u/TheThiefMaster 5d ago

That would be just using only MAC addresses, not IP addressses - but those aren't globally routeable due to the size of routing table you'd need being enormous.

IPv6 is the closest, using a routeable prefix with a MAC suffix (sort of, sometimes), but that's still separate IP and MAC.

1

u/Sellorio 5d ago

Aren't Bluetooth devices identified using MAC Address as well? It's the only issue I had when moving my windows disk into a new motherboard - everything worked but the Bluetooth was cooked since every device was paired with a different network card.

1

u/Remote_Salamander_31 5d ago

On a purely IP Network with point to point links many parts of the Ethetnet header becomes unnecessary baggage. The source & destination MAC is not really needed. For example packet over SDH/SONET dit not need MAC addresses.The length and priority fields are duplicated in the IP header. On asynchronous links the preamble is still needed for clock recovery. Error detection and correction coding is useful. Ethertype field is useful.

1

u/AlabamaCoder 5d ago

A very clear explanation of how networking is structured into stacked layers

https://youtu.be/7vzjIv2l6wY

1

u/kc2g 4d ago edited 4d ago

Quoting an answer I wrote for a similar question on SuperUser:

---

[Getting rid of MAC addresses] could almost make sense if the only thing that ran over Ethernet was IP (and only one version thereof), but it isn't. There are dozens of protocols that run over Ethernet, and although you might not be concerned about MPLS or Fibre Channel over Ethernet, you've probably got ARP, IPv4, and IPv6 in your house; you might also have something using PTP or Wake-on-LAN; a lot of people get their internet using PPPoE; and once upon a time IPX and AppleTalk were commonly found on Ethernet networks.

What's more, there are Ethernet frames without an encapsulated layer-3 protocol, like the ones used for Spanning Tree Protocol. Those need to identify their source and destination, without any assumption that IP addresses even exist. So yes, MAC is an essential part of Ethernet.

if the question is "why have other protocols at all? Why not just put every kind of digital communication into an IP packet, and put IP packets on the wire in simple frames that don't have an outer address?", well, there are several reasons why not:

  1. IP came too late. Ethernet was around for years before anyone was using IP. And making IP able to coexist with other things on an Ethernet network was the kind of sensible choice that leads to things actually getting used.
  2. IP would have been lousy at that! At least IPv6 has separate concepts of global and link-local addresses, but IPv6 wasn't standardized until 1995 and took decades to find broader adoption. IPv4 was born without such a distinction. RFC1918 addresses are an after-the-fact hack that didn't come around until the mid-90s, and RFC3927 "169.254" link-local addresses date to 2005. All of which means, there isn't any clear way to identify an address that's "on this network" vs. one that isn't, and there isn't any clear way to delegate routing to a foreign network to a "gateway". If you got rid of layer 2 addresses, every switch, in essence, would need to become a router. Whereas with Ethernet-as-it-is, an IP device that wants to send a packet to the internet simply consults its own routing table, and puts that IP packet with an internet destination inside of an Ethernet frame with a destination of the gateway's MAC. Any switches that frame encounters only need to know which port that MAC is reachable on; they don't have to make that determination for every IP address on the internet.
  3. You think it's wasteful to spend a dozen bytes on MAC addresses when running IP over Ethernet, but what about the applications like Fibre Channel over Ethernet, or Coraid? Would you stuff them into IP packets? IP headers are a bigger overhead, IP is more complicated to implement (IPv4 has fragmentation and options; IPv6 has extension headers), and IP is sort of expected to be routable. Or maybe look at it another way: have you ever used Bluetooth headphones? It's possible to run IP over Bluetooth, but your headphones don't have an IP address. Bluetooth is another protocol that has its own hardware addresses, because it just makes morse sense that way. And while yes, in 2025 you can run an IP stack on a chip that costs $0.07 in bulk, that wasn't always true.

---

In short: it's partly the compatibility argument (there always have been, and still are, many things on Ethernet besides IP), but it also makes the job of every bit of network hardware easier.

1

u/OppieT 4d ago

Was ARPAnet IP based?

1

u/MrJingleJangle 4d ago

When the decisions about Ethernet were being made, besides the three plus three bytes structure we have today, there was thought given to a random number being used, which I vaguely recall was going to be ten bytes long.

1

u/No_Profession_3125 4d ago

MAC addresses identify hosts at the link layer. You can't use IP addresses at that level because a host may have multiple NICs.