4 ms·
AWS has heavy support for IPv4 because back-end stuff is all IPv4 and there isn't any push to change. IPv6 doesn't add any real value for servers that are all l
by ben509 8y ago
AWS has heavy support for IPv4 because back-end stuff is all IPv4 and there isn't any push to change. IPv6 doesn't add any real value for servers that are all living in a private address space anyway, it adds an overhead to each packet, and learning off your addressing schemes is far easier with dotted quad.
- dcow 8y agoIP isn’t supposed to have “private address space”. The only reason it does is because the address space is scarce. NAT does not make your network “private” or provide security, firewalls and good host software do that. NAT literally breaks IP.
- jon-wood 8y agoRFC 1918 (Address Allocation for Private Internets) disagrees with you, and has done since at least 1996.
- Cincinnati 8y agoEnd-to-end principle disagrees with you. As does my network. All routable IP space baby. Makes things a breeze.
- dcow 8y agoRFC 1918 describes space for entirely private networks, not “private extensions” to the public globally routable internet. There’s a subtle but important difference. The private addresses strictly aren’t routable on the public internet. NAT (which there’s also an RFC for) is what what allows packets to flow between private disjoint IP networks. IP is only scoped to work within a single network, whether it’s public or private or triangle.
- rlpb 8y agoThat screws up when two private entities merge and discover that they're using the same RFC1918 block. (or just want to interoperate, even)
- Sami_Lehtinen 8y agoIPv6 got a private address space, even if we shouldn't run out of IPv6 addresses anytime soon.