201708 - apenwarr


61 bookmarks. First posted by jgordon august 2017.


"Anyway, I digress. The salient detail here is that unlike real IP services, bootp and DHCP need to know about ethernet addresses, because after all, it's their job to hear your ethernet address and assign you an IP address to go with it. They're basically the reverse of ARP, except we can't say that, because there's a protocol called RARP that is literally the reverse of ARP. Actually, RARP worked quite fine and did the same thing as bootp and DHCP while being much simpler, but we don't talk about that. The point of all this is that ethernet and IP were getting further and further intertwined. They're nowadays almost inseparable. It's hard to imagine a network interface (except ppp0) without a 48-bit MAC address, and it's hard to imagine that network interface working without an IP address. You write your IP routing table using IP addresses, but of course you know you're lying when you name the router by IP address; you're just indirectly saying that you want to route via a MAC address. And you have ARP, which gets bridged but not really, and DHCP, which is an IP packet but is really an ethernet protocol, and so on."
a:Avery-Pennarun  p:apenwarr  d:2017.08  w:5500  network  history  from instapaper
25 days ago by bankbryan
At that point, all we'd have to do is eliminate all remaining UDP and TCP from the Internet, and then we would definitely not need layer 2 bridging anymore, for real this time, and then we could get rid of broadcasts and MAC addresses and SDN and DHCP and all that stuff. And then the Internet would be elegant again.
history  internet  present  technology  communication 
september 2017 by soobrosa
The world in which IPv6 was a good design
from twitter
august 2017 by becked
Why is IPv6 such a complicated mess compared to IPv4? Wouldn't it be better if it had just been IPv4 with more address bits? But it's not, oh goodness, is it ever not. So I started asking around. Here's what I found.
ipv6  history  networking  internet  QUIC 
august 2017 by lidel
did you see btw?
from twitter
august 2017 by avi
"And then the Internet would be elegant again."
history  networking  ipv6  AveryPennarun  via:torbiak 
august 2017 by campbellr
"And then the Internet would be elegant again."
history  networking  ipv6  AveryPennarun 
august 2017 by torbiak
Networking history explained with
internet  ipv4  ipv6  networking  tutorial 
august 2017 by slyskawa
RT : The world in which IPv6 was a good design
from twitter
august 2017 by peba
The IETF people, when they were thinking about IPv6, saw this mess getting made […] and they said, hey wait a minute, stop right there. We don’t need any of this crap! What if instead the world worked like this? […] It would have been beautiful. Except for one problem: it never happened.
!  networking  history  ipv6  internet  recommended 
august 2017 by ap
Long discussion of networking legacy and IPv6, with many entertaining digressions.
history  internet  ipv6  networking 
august 2017 by emk
A very good explanation of some of the details of ethernet and internet networking explained via historical context.
internet  networking  ipv6  history  via:HackerNews 
august 2017 by mcherm
The evolution of Internet Protocol and Ethernet
august 2017 by jcrites
great history of networking leading to TCP/IP etc
internet  http 
august 2017 by tomcam
The world in which IPv6 was a good design
from twitter_favs
august 2017 by joseph
I thought this would be agreat chance to really try to figure out what was going on. Why is IPv6 such a complicated mess compared to IPv4? Wouldn't it be better if it had just been IPv4 with more address bits? But it's not, oh boy, is it ever not. So I started asking around. Here's what I found.
internet  ipv6  ip  ipv4  quic  network  explainer 
august 2017 by bezthomas
He worked on arcnet!
s 
august 2017 by jgordon