= Сообщение: 1463 из 12549 ====================================== ENET.SYSOP = От : Kees van Eeten 2:280/5003.4 22 Nov 14 15:42:18 Кому : BjЎrn Felten 22 Nov 14 15:42:18 Тема : IPv6 FGHI : area://ENET.SYSOP?msgid=2:280/5003.4+5470a32d На : area://ENET.SYSOP?msgid=2:203/2+54709c94 = Кодировка сообщения определена как: LATIN-1 ================================ ============================================================================== Hello BjЎrn!
22 Nov 14 15:24, you wrote to me:
KvE>> Both IP levels use the same infrastructure and KvE>> when tunnels are used the encapsulation adds extra traffic.
BF> True. But once you've passed the IPv4 bottleneck and are out on the BF> IPv6 highway, all responses are much faster.
I am out of touch with the real world for to long. But I cannot imagine, that there is a separate infrastucture for IPv6. I expect everything to be dual stack now.
BF> You usually can see this just by pinging a site with both IPv4 and BF> IPv6. The mean time for IPv4 is somewhat shorter (for the bottleneck BF> reason) but the time difference is bigger, indicating that there's a lot BF> of traffic -- with a lot of busy DNS servers involved. With native IPv6 BF> all the way, this should become even more obvious.
BF> At least I notice a significant speed improvement when I'm surfing on BF> IPv6. YMMV.
If I make a request for an IP-address for www.google.com, I get 6 answers for IPv4 and one for IPv6. There seems to be no commonality between the IPv6 and one of the IPv4 addresses. For administrative reasons, the lowest value is often kept in the range of 0-255 for to match the low order byte of the IPv4 address.
So it is possible that the offered ipv6 host is a separate server that only serves IPv6 customers, and still has a low load. But surfing is not only going to google.
Kees
--- FPD v2.9.040207 GoldED+/LNX 1.1.5 * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
