On 4/09/2008, at 9:16 AM, Glen Eustace wrote:
TelstraClear have been providing tunnels to some existing IPv4
for a number of years.
I don't recall them responding so in the RFP but that
was quite some
time ago now.
They do not do it as a supported product.
It is very much a "you need to know who to talk to" thing.
tell us how much native IPv6 Massey has deployed and when
Our boundary is native IPv6, we are peered with the KAREN routers at 3
sites with IPv6 and now with AS 18061 as well. Internally, the core of
the network is v6 and the distribution layer is v6 but we have been
waiting for an IOS release for the Cisco 3750s and 4500s that supports
DHCP relaying. This is now available and will be deployed shortly.
That will give us v6 to the desktop. At the moment we have ISATAP
so that any windows platform with v6 turned on, MacOS or Linux can use
v6 if they want.
Our external name servers and mail MX'es have AAAA records and we
small amount of v6 mail, mainly from the UK and Europe.
At present we have not put AAAAs on any web resources. Until I get
setup and confirm that our miredo server is behaving as expected I
want to get complaints about poor response because all external v6
traffic goes via an offshore relay.
There are more problems than this - put a Windows Vista machine on a
filtered non-RFC1918 address, and you'll get breakage with 6to4.
As to how much is v6 being used, probably not a
lot but it was my
lead not to follow. Was there a demand ? Probably the same answer. v6
was rolled out after the workshop that Nathan and crowd did in
Wellington last year.
Cool. We just got done doing the same thing in Christchurch, and are
also doing it next week in Auckland. Good to see things are happening.
When more v6 content is available and when we are
able to offer v6
content, we will have the infrastructure in place.
There are still issues we haven't found answers too, one that is
frustrating me is the lack of v6 support in the Bluecoat web cache
appliances. With Massey's HTTP policy, one can not easily browse to
content if using the cache is enforced, which it is :-(
I hope you've told your vendor you won't upgrade/whatever unless they
do v6 :-)
(Squid works just fine... Some vendors are putting Squid proxies in
front of IPv4-only HTTP stacks in order to check the "IPv6 ready" box).
Thanks for the plug guys. :-)
Yes, Squid-3 does full v4/v6 multi-plexing in the Beta release code,
with a years worth of testing behind it now.
I'm your local IPv6 Squid developer and Squid-3 release maintainer. Here
for contact at squid3(a)treenet.co.nz, if anyone has issues or wants
Treehouse Networks Ltd