[75020] in North American Network Operators' Group
Re: IPv6 support for com/net zones on October 19, 2004
daemon@ATHENA.MIT.EDU (Niels Bakker)
Thu Oct 28 07:46:28 2004
Date: Thu, 28 Oct 2004 13:45:28 +0200
From: Niels Bakker <niels=nanog@bakker.net>
To: nanog@merit.edu
Mail-Followup-To: nanog@merit.edu
In-Reply-To: <Pine.BSF.4.58.0410281236430.7880@atlas.fccn.pt>
Errors-To: owner-nanog-outgoing@merit.edu
* cfriacas@fccn.pt (Carlos Friacas) [Thu 28 Oct 2004, 13:38 CEST]:
> From AS1930 (Portugal, Europe): [it works...]
>
> ;; Query time: 544 msec
> ;; SERVER: 2001:503:231d::2:30#53(2001:503:231d::2:30)
> ;; WHEN: Thu Oct 28 12:11:40 2004
> ;; MSG SIZE rcvd: 504
>
> ;; Query time: 547 msec
> ;; SERVER: 2001:503:a83e::2:30#53(2001:503:a83e::2:30)
> ;; WHEN: Thu Oct 28 12:43:23 2004
> ;; MSG SIZE rcvd: 504
Query times using IPv6 seem significantly higher than those for IPv4 to
both a and b.gtld-servers.net, but as far as you can trust traceroute it
doesn't seem as if the IPv4 and IPv6 addresses for each host end up in
wildly different places...
Anyone else care to comment? The hop count is suspiciously lower for
IPv6 than for IPv4, and has twice the latency (coming from Europe too).
But again, this is traceroute `wisdom'.
-- Niels.
--
Today's subliminal thought is:
