https://docs.google.com/
ISP | IPv6 | Prefix Length | Static? | Notes |
---|---|---|---|---|
Bigpipe | No | N/A | N/A | |
Compass | ? | Have asked - no response yet | ||
Earthlight | ? | Have asked - no response yet, but believe it is supported | ||
Inspire | Trial | /56 | Yes* | Prefix normally sticky, may change in future |
Maxnet | No | N/A | N/A | Not supported for home connections. Available on request for co-lo systems |
MyRepublic | No* | N/A | N/A | Not currently supported, but plan to offer by June |
Orcon | Trial | /56 | Yes* | Prefix normally sticky, may change in future |
Sinch | Yes | /56 | Yes* | Static allocations on request |
Slingshot | No | N/A | N/A | |
Snap | Yes | /48 | No | Not full production support. May be disabled occasionally. Outages will not be notified on network status page |
Spark | No | N/A | N/A | |
Trustpower | No | N/A | N/A | |
Vodafone | No | N/A | N/A | |
Vorco | Yes | /56 | Yes | Business-grade services/pricing, not residential |
Woosh | Yes | /56 | No | |
WorldxChange | Closed trial | /56 | Yes | "Trial" has been running for several years. Currently closed. |
https://ripe66.ripe.net/
Her study is expected to help policy-makers, vendors and managers understand the barriers organisations face in adopting IPv6, and the factors that enable them to overcome these barriers.
Awinder is looking to interview executives and managers from organisations that have implemented or are planning to implement IPv6.
More information about Awinder’s research is available below. If you are interested in participating, please email her at awkaur [at] aut.ac.nz.
]]>Sponsored by InternetNZ in conjunction with the New Zealand IPv6 Task Force, three expert speakers featured – Convenor of the New Zealand IPv6 Task Force Dr Murray Milner, InternetNZ technical policy advisor Dean Pemberton and REANNZ CIO Sam Sargeant – each of whom took to the subject-matter with gusto.
Milner began proceedings with a meaningful analysis of IPv6 and ‘what the problem is’. That problem, in a nutshell, is IPv4 address exhaustion and the fact that its replacement protocol – IPv6 – is not backwards compatible.
IPv4 is the addressing protocol that originated with the Internet. The number of IPv4 addresses, now exhausted, total only 4 billion – a paltry figure when one considers the press of humanity and astonishing growth of networked devices, especially mobile. One estimate suggests that by the year 2020 there could be 7 billion Internet users and 7 trillion devices. This emerging ‘Internet of Things’ will unquestionably be driven by IPv6 addressing.
In our now IPv4-scarce world there is a range of alternatives. For example, it is possible to buy IPv4 addresses on auction sites such as eBay. However, this starts to fragment address ranges and is not a sustainable option, says Milner. Another alternative is to stay with IPv4 and make use of NAT (Network Address Translation). NAT however comes with several fishooks, he cautions – including degraded network performance, scalability and cost.
These alternatives also do not take into account a more sobering reality – that three of the world’s largest-growing economies (China, India and Indonesia) are growing from very low to very large Internet penetration off the back of IPv6.
“As more entities and developing countries make use of IPv6-only addresses, innovation on the Internet will start to occur on the IPv6 Internet.”
This is not something that garden variety Internet users need lose sleep over, but enterprises must acquaint themselves with the issue. The only long-term sustainable solution for enterprise, says Milner, is IPv6 adoption.
Those enterprises without an IPv6 capability, warns Milner, risk missing out on business opportunities in these IPv6-only pockets and could even lose contact with customers and suppliers.
Pemberton followed up with an impassioned presentation, highlighting what he is seeing at a global level with IPv6 deployment. His messages were four-fold – IPv6 is real and here; IPv6 is essential for reaching the entire Internet; IPv6 will soon be the default training protocol and; if IPv6 is deployed correctly enterprises can minimise their investment.
The amount of IPv6 traffic on the Internet is growing day-by-day, increasingly being deployed on large-scale mobile networks and by content providers such as Google, Wikipedia, Akamai, Yahoo, Facebok and Verizon Wireless. Pemberton claims that these content providers are witnessing huge jumps in how much traffic is delivered over IPv6, with “exponential growth” at Google, the Amsterdam Internet Exchange regularly seeing “6-7 GBs of IPv6 traffic per second” and “a majority” of traffic at Louisiana State University now IPv6.
“IPv4 is now the also-ran. IPv6 is real, here and is being used by massive global players. Stop asking if and when. The question now is how can you join.”
Pemberton heavily stressed the need for enterprises to enable IPv6 if they wish to reach the entire Internet. He, too, noted that many of the countries exhibiting Internet growth are the least developed nations.
“New Zealand is an export driven economy and our export markets are deploying IPv6. We need to ensure that our customers can contact us and vice versa.”
IPv6 will soon be the default training protocol. APNIC – the regional Internet registry for Asia Pacific – is looking at ways to make IPv6 the default protocol taught in its workshops and Pemberton claims that at least one network engineering course at a New Zealand university is looking to do the same.
Wrapping up his suite of messages, Pemberton noted that if IPv6 deployment is approached in a sensible manner as part of normal hardware refresh cycles it will cost a minimal amount. But, engineering in a crisis will cost money. He wound up with a question directed squarely at the CIO audience – “Where would you like to spend your money? On ways to keep IPv4 working, on ways to reduce reliance on IPv4, or on deploying IPv6?”
Bringing a real-world deployment perspective into the frame, Sargeant succinctly outlined REANNZ’s IPv6 journey – a story previously reported at www.ipv6.org.nz/2011/09/07/reannz-lives-the-ipv6-story.
Copies of the three presentations are available below:
Dr Murray Milner – Introduction to IPv6 Adoption with New Zealand Enterprises
]]>Prepared by the Task Force in conjunction with InternetNZ (Internet New Zealand Inc), the whitepaper is intended to be used as a primer for enterprises in New Zealand, to encourage them to adopt IPv6 in a cost effective and low risk manner.
The 22-page whitepaper acts as a roadmap for the adoption of IPv6. The target audience for its ‘adoption’ message is any organisation which uses Internet Protocol technology within New Zealand.
The whitepaper can be downloaded and read at the following link:
NZ IPv6 Task Force whitepaper – IPv6 Adoption by New Zealand Enterprise
]]>In a post to the NZNOG mailing list, NZRS Chief Executive Jay Daley says that there is “new firmware on the boxes that fixes previous IPv6 issues”. ntp1.ntp.net.nz and ntp3 are now accessible over IPv6, albeit ntp2 has a minor provider-related IPv6 issue awaiting remedy.
Daley says NZRS is considering adding one more server to the NTP network and is researching a number of of kit possibilities.
Feedback on NZRS’ NTP service is welcome at anytime and can be emailed direct to Jay Daley at [email protected].
More information on NZRS’ NTP server network can be read online at http://ntp.net.nz.
]]>A full run-down of the meeting – including copies of all presentations – is available online at www.apricot2013.net/program/apipv6tf.
]]>
—-
IPv6 makes mobile networks faster
ExtremeTech – 16 January 2013
“At CES in Las Vegas, a panel of experts on Internet Protocol technology discussed IPv6 and the benefits of having mobile devices use IPv6 instead of IPv4. As it turns out, IPv6 offers some pretty substantial benefits over IPv4 for mobile networks and the devices that connect to them.”
http://www.extremetech.com/mobile/145765-ipv6-makes-mobile-networks-faster
PlusNet Tests IP Address-Sharing As IPv6 Fails To Take Off
TechWeek Europe – 15 January 2013
“PlusNet, the Sheffield-based ISP owned by BT, is testing a controversial scheme in which all its customers could share one IP address through Carrier Grade NAT (CGNAT). The move, made necessary by the slow progress of the new protocol IPv6, could limit customers’ Internet actions and cause problems with tracking abuse or criminal action.”
http://www.techweekeurope.co.uk/news/plusnet-ipv4-ipv6-nap-networking-104349
IPv6 can boost mobile performance, battery life, proponents say
Network World – 11 January 2013
“IPv6, the next version of the Internet Protocol, could make life easier and battery life longer for electronics-addicted consumers. Much of the push for IPv6 has been focused on the requirements of enterprises and the challenges they face in making the transition from the current protocol, IPv4. If device makers and service providers do their jobs right, consumers won’t even know it when they start using IPv6, but they do stand to benefit, proponents of IPv6 said in a panel discussion at International CES on Thursday.”
http://www.networkworld.com/news/2013/011113-ipv6-can-boost-mobile-performance-265733.html
IPv6 takes one step forward, IPv4 two steps back in 2012
Ars Technica – 5 January 2013
“IPv6 rollout is still inefficient with problems ahead, but there is slow progress.”
http://arstechnica.com/business/2013/01/ipv6-takes-one-step-forward-ipv4-two-steps-back-in-2012/
IPv6 shift puts cash-strapped telcos in a fix
The Times of India – 27 December 2012
“India’s much-delayed transition to the next-generation technology standard for internet communication-IPv6 – have put country’s telecommunication and internet services providers in a quandary as they must now spend on technology to prepare for the change.”
]]>NZNOG13 Is Upon Us
Register early for NZNOG13 and receive a free Mikrotik wireless access point and router!!
The New Zealand Network Operators Group (NZNOG) is holding its annual conference and training workshops and tutorials in Wellington from the 21st to 25th January 2012.
Training workshops and tutorials run from the 21st to the 23rd of January. The conference is then held on the 24th and 25th of January.
This annual conference provides both an opportunity to exchange technical information, and a high-value opportunity for NZ’s networking staff to ‘network’ amongst themselves. This is New Zealand’s only technical networking conference.
The event will be held at the Mecure Hotel in Wellington. Accommodation is available on site at a discounted rate for conference attendees as well as in the immediate area.
Registrations are open. The cost of attendance has been confirmed at $250, students receive a 60% discount and a fellowship scheme exists should you require assistance to attend.
Conference Presentations 24-25th January
Confirmed presenters for NZNOG13 include:
Plus updates from NZRS, APNIC, CityLink, IPv6 Task Force, WAND and InternetNZ.
Tutorials – 23rd January
Mikrotik wireless and routing systems (full day)
APNIC – Internet Resource Management IRMe (half day)
APNIC – DNSSEC (half day)
IPv6 Security – Karl Auer IPv6Now (half day)
TBC
Workshops – 21st – 23rd January
IPV6 BGP Routing – Philip Smith (APNIC)
This workshop is targeted at engineers and network administrators from both ISPs and SOHO/enterprise networks.
ISP network topology overview
ISP IP Addressing Plan
Introduction of Internet routing infrastructure
2 Byte and 4 Byte AS Numbers
BGP operation
Understanding BGP metric and path selection process
Configuring BGP within an AS [iBGP, route reflector]
Configuring BGP between ASes [eBGP]
Controlling routing update traffic [prefix list, distribute list, route map]
Route Summarization with BGP
BGP Traffic engineering [MED, Local Pref, AS-Path prepend]
It is highly recommended that participants bring their own laptop computers (At least Pentium 4, 1gb Ram, DVD drive, with administrative access to system) to practice the lessons learned during the workshops.
DNSSec Workshop – Phil Regnauld
The course is designed for network engineers, systems administrators, and anyone who is involved in managing DNS operations.
DNS concepts
BIND (DNS server) and Resolver (DNS client) configurations
Rever