Guest post: CIRA enables IPv6

3 Comments

Jacques Latour, Director of Information Technology at CIRA, wrote today’s post about IPv6. Enjoy.

Today is World IPv6 Day and as CIRA’s Director of Information Technology, I am proud to say that we are participating with a fully IPv6 enabled corporate website.

It took us five months to plan our IPv6 deployment. We started with an assessment of our infrastructure and services, conducted lots of training, and we developed a publicly available IPv6 Security Policy template.  Some of our equipment was not IPv6 compliant.  It was a major learning curve for our Operations & Security teams; we did a lot of testing in our lab before going live.

One challenge to overcome is network address translation (NAT), you NAT IPv4, but not IPv6.  The IPv6 addressing plan was also an interesting challenge.

We managed to get IPv6 transits (check our IPv6 routing paths) from our Toronto site as well a native IPv6 peering, not only is our web presence dual stack IPv4/IPv6, but we have our corporate LAN users dual stack as well, so we can enjoy the Internet in both IPv4 and IPv6.

All in all, it was a lot of work, but very important.

I just want to leave one final comment. The Internet is not just IPv4 or just IPv6, the Internet is IPv4 and IPv6.

Enjoy World IPv6 Day!

Share on Tumblr
  • http://RobinCheung.ca/ Robin Cheung

    I am extremely pleased to read this announcement (those of you who recall my post on the [perhaps premature?] day the new CIRA corporate website was released: http://ipv6.RobinCheung.ca/cira-ipv6 pointing out that it was inconsistent with its own stated initiatives and mandate on LinkedIn will also appreciate this announcement!)

    (I suggested it was premature, since, as I pointed out in http://ipv6.RobinCheung.ca/cira-ipv6 whereas I am a Finance PhD student who does not maintain a public mandate to champion and facilitate ipv6 adoption in Canada; however, I make the time–as I do in participating in CIRA’s Board of Directors elections as a Member-Nominee each year–not only to point out these inconsistencies, but rather to go ahead and demonstrate their feasibility by implementing them, myself (As pointed out, due to limitations of funding my own IT initiatives out of pocket as a PhD student, although all of the servers under my direct control *are* ipv6-routed, http://RobinCheung.ca/ which is not, will become so when I have the time away from my beginning-of-quarter PhD student commitments to migrate to the server I have already prepared.

    I would also like to point out that other organizations with funding are going the extra kilometre to facilitate ipv6 adoption as well: http://www.tunnelbroker.net (from Hurricane Electric) provides free Protocol 41 tunnels to those who are not behind NAT, with available routed /48 and routed /64 subnets included; http://www.sixxs.net provides a NAT-traversing solution; and in Toronto, my own “indenpendent ISP” (I thought that was what the “I” stood for in the first place, historically … :p) Teksavvy provides a Native IPv6 ADSL (currently in public beta) on request!

    Robin L. M. Cheung, BSc, MBA, F.CIM, PhD Candidate

  • http://www.seoservicesplus.ca SEO Services Company

    The implications of the change, is something I think we all appreciate. Thank you for the security.

  • http://www.traskdigital.com SEO Reseller Services

    Internet Protocal version 6(IPv6)is part of networking and i have few knowledge about networking but your writing skill and descriptive point is very good and i am impressed to your writing skill.