registry team mailing list archive

Thread
Date

[Bug 555210] Re: Please assign global scope to RFC 1918 addresses in getaddrinfo()

To: registry@xxxxxxxxxxxxxxxxxxx
From: Jeremy Visser <jeremy@xxxxxxxxxxx>
Date: Wed, 30 Jun 2010 08:08:42 -0000
Reply-to: Bug 555210 <555210@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

I agree with Gro-Tsen. I have better IPv6 connectivity than IPv4, and
while IPv6 is preferred for most connections, if they are hosted on a
6to4 (2002::/16) host, then IPv4 is used. Some applications can force
IPv6 (i.e. ssh -6, or telnet -6), but others cannot (i.e. Firefox or
Chromium).

Strange thing is that even though I'm *not* on a 6to4 connection, and
even if the *destination* host has 6to4, then IPv4 is preferred. That
logic doesn't sound right to me. If *I* had a 6to4 connection as the
source IP, then maybe preferring IPv4 to 6to4 would make sense, but not
for the destination.

-- 
Please assign global scope to RFC 1918 addresses in getaddrinfo()
https://bugs.launchpad.net/bugs/555210
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for GLibC.