Iljitsch van Beijnum wrote: > Limiting myself to the www.ietf.org webservers (yes, this address > points to two different hosts) it appears this site runs on: > > Server: Apache/2.0.46 (Red Hat) > Server: Apache/2.0.40 (Red Hat Linux) DAV/2 mod_ssl/2.0.40 OpenSSL/ 0.9.7a www1.ietf.org @ cnri/reston.va.us/cogent + www2.ietf.org @ foretec/uunet This is done for failover/bombproof etc reasons, not the perfect thing to do but that will change one day with HIP/shim6/sctp/lot of other hard work that many people are doing. > Even though these Apache versions are 2 - 3 years old (with many > vulnerabilities found and fixed in the mean time), they're fully > capable of supporting IPv6, as are Red Hat Linux versions of around the > same age. The problem here seems to be more the fact that, in the US, getting IPv6 connectivity can be quite tiresome. Cogent, the current IPv4 upstream, doesn't do IPv6 (they have 2001:500:2::/48) for instance. UUnet could maybe do IPv6. Maybe the secretariat would wants to try out some tunnels? In any case http://www.ietf.org.sixxs.org also works, though it might indeed be nice if this trick was automatic without appending the domain. Greets, Jeroen PS: I assume RedHat backports fixes so that 2.0.40 actually is a 2.0.53 but with a different version number...
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf