IPv6 at Anchor Systems

As discussed briefly in a recent blog post, Anchor is committing to rolling out IPv6. Why? Because it's in the best interests of us, our customers and the Internet as a whole. For that to happen, IPv6 needs to be demystified and most importantly, made available. We believe that by making our IPv6 plans public and documenting our progress through the deployment we'll help IPv6 on a larger scale.

Below is a timeline of our progress to date, and future steps we need to take to make IPv6 a reality at Anchor. Please check this page regularly as we'll be updating it whenever progress is made.


This is the overall plan for deploying IPv6. It is fairly high-level (and vague in parts) at the moment, but will become more detailed as the process is followed.

  • Create internal documentation.
  • Educate Level 2+ sysadmins on IPv6.
  • Create high-level presentation to deliver to all staff at a weekly meeting.
  • Request IPv6 allocation for Anchor network.
  • Request IPv6 allocation for Anchor office uplink.
  • Request IPv6 allocation from ISPs of network administrators responsible for IPv6 project (for testing).
  • Create internal address allocation policy.
  • Update internal administration systems to handle IPv6 (address allocation database).
  • Investigate upgrades necessary for the following systems and document:
    • border and core routers
    • switches
    • network monitoring systems
    • traffic accounting systems
    • DNS servers
    • VPN endpoint
    • load balancers / high availability systems
    • firewalls
    • host and network intrusion detection systems
    • control panels and customer-facing web interfaces
    • internal shared webserver scripts
    • configuration management systems
  • Create test deployment environment for border/core routers, border/core/infrastructure switches.
  • Test impact of minimal IPv6 deployment in test environment
  • Upgrade traffic accounting systems
  • Upgrade network monitoring systems
  • Upgrade firewalls
  • Create change procedures for live minimal IPv6 deployment
  • Roll out live minimal IPv6 deployment
    • Create AAAA record for main Anchor website.
  • Test and selectively upgrade remaining infrastructure piece by piece
  • Create client documentation
  • Inform client base of IPv6 availability
  • Work through client migrations

Current Progress

  • (30/01/09) This wiki page has been created to document our progress!
  • (30/01/09) There seems to be a dearth of good IPv6 resources on the Internet. Many are outdated, no longer available or only accessible via IPv6 hosts (in a terrible Catch-22)! I recommend the following:
    • Wikipedia IPv6 page (linked at the bottom of this page)
    • IPv6 Network Administration by Niall Murphy and David Malone, published by O'Reilly (ISBN 978-0-596-00934-2)
  • (06/05/09) Internal IPv6 documentation has been created, it will likely be a work in progress for some time.
  • (06/05/09) Preliminary investigation into our existing systems shows that a lot of support for IPv6 already exists. Changes to custom internal systems will likely be quite minor.
  • (12/05/09) A request for an IPv6 allocation has been made to APNIC. In the meantime we have been granted an additional IPv4 allocation from APNIC which should easily satisfy our IPv4 requirements until there is significant IPv6 uptake.

  • (14/05/09) Anchor has received an IPv6 allocation from APNIC - 2407:7800::/32

References/External Links