4 ms·
What would a 64bit address space solve that a 128bit would break?
by cm2187 9y ago
What would a 64bit address space solve that a 128bit would break?
- scbrg 9y agoThe possibility of remembering addresses.
- tomschlick 9y agoDNS. You're not supposed to remember ip addresses.
- paulddraper 9y agoI remember 8.8.8.8
- tomschlick 9y agoLonger, but still memorable. 2001:4860:4860::8888
- therein 9y agoI remember 208.67.222.222 and 208.67.220.220 being someone who grew up in a country with DNS-level censorship way before Google announced their Public DNS.
- deleted 9y ago[deleted]
- nikanj 9y agoWe are the sorry sods working on your VPNs, LANs and the like. There's no DNS for routable blocks yet.
- zurn 9y agoConfiguration systems for those typically do support symbolic prefixes for easy renumbering and deployment of sibling networks. Also, most people dealing with rfc1918 networks would much rather get rid of addressing conflicts and other problems resulting from non-unique addresses, like security problems arising from ambiguous addressing. (Or don't know what they're missing...)
- nazgul17 9y agoIf you're talking about local addresses, can't you just use the short notation and use even-shorter-than-64-bits addresses? If not, DNS is there for that.
- dingo_bat 9y agoPassing around an IP address in a single register. Today's CPUs are powerful enough to not need hardware forwarding chips to route up to 1Gbps of traffic easily, without much custom software optimisation. However that only holds true for IPv4 traffic. Throw in IPv6 traffic and suddenly each compare takes twice as much time in the CPU. Functions cannot pass addresses and masks in the registers, requiring stack juggling or worse, memory access.
- tyingq 9y agoAsk yourself who benefits from this...slower networking on commodity hardware. Then look at who had the most influence over ipv6 in the IETF, etc. No big surprises.
- legulere 9y agoCompile a function that takes a 128 bit struct as an argument and look at the assembly. It is simply passed in 2 registers.
- DaiPlusPlus 9y agoDepends on the ISA and optimization level - and the OS. Win32's x86-only __stdcall convention always passes arguments on the stack instead of in registers.
- tveita 9y ago> Throw in IPv6 traffic and suddenly each compare takes twice as much time in the CPU So an operation responsible for less than 0.1% of the total time spent routing a packet now takes twice as much time... or it would if CPUs weren't superscalar for a long time now. That's paid back in tenfold just by the omission of the header checksum. Do you have any benchmarks showing a real-world difference? https://www.unix-experience.fr/2013/ipv4ipv6-performances-comparison/ https://www.unix-experience.fr/2013/ipv4ipv6-performances-co... shows performance to be identical on modern computers.