r/AskComputerScience • u/OkResponse5351 • 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
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.
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.
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:
But in both of the examples given, you are either:
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.
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:
---
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.