3 ms·
Ehhh I don't know about that. IP takes a while to understand for most of the reasons articulated in the post. DHCP and ARP, for example, are a bit strange. It's
by baryphonic 6y ago
Ehhh I don't know about that. IP takes a while to understand for most of the reasons articulated in the post. DHCP and ARP, for example, are a bit strange. It's just everyone already understands it, so explanations have been distilled pretty well.
That being said, I don't grok IPv6 myself, on account of never actually looking into it.
- wnoise 6y agoARP I'll give you (though even there it's only actually in the binding of IPv4 to ethernet-like lower layers. IP over e.g. PPP doesn't need it). DHCP isn't inherent in IPv4 at all though. You want to throw it in, because IPv6 has address autoconfiguration built-in. But this is actually just more evidence that IPv6 is more complex.
- baryphonic 6y agoI want to throw DHCP in because in practice, you need it to connect to random IPv4 networks. Besides, the counterpoint is even tougher. Should we expect beginners to configure static addresses when actually configuring their networks? Getting bogged down in the details of broadcast addresses, subnet masks and gateway addresses can be a bit unsettling for a total beginner. It's second nature to seasoned hackers, so we discount how foreign it was when we first learned it.