Randy Bush wrote:
imiho, the big barriers to ipv6 deployment are vendors, education, and senior engineer time. we're working the vendors, and there is progress. and apnic and the other rirs continue to put serious effort into education, thanks. dunno what to do about engineer time.
Agreed.We've worked on the vendors so that my MAC comes with IPv6 as part of the system, Microsoft ship their software with IPv6 included, the various flavours of *nix all have it even though almost no-one asks for it on any of these systems. Junipers and Ciscos come with IPv6 as standard.
Shouldn't we do the same for the addresses?You push back on IPv6 marketing - isn't that what APNIC's education program is to a large degree? So this is one more piece of that puzzle.
In lots of places I deal with engineer time on IPv6 happens because people are curious about how IPv6 works and they start "playing" with it. In many cases if they try to create a business case to get IPv6 resources from APNIC (and until recently getting IPv6 space would often change people's membership tier) then it's not going to happen.
That pricing has changed to reflect the notion that IPv6 is a commodity but we're talking here as though it's something else.
as far as policy goes, we can not set prices, the ec does that. but we can make it easy to get what you want when you want it. do we have any barriers in place we should seriously review?
People on this list deal with APNIC on a regular basis I suspect. Those that don't often think the process is hard. I get asked to help people who want to apply for address space (IPv4 and IPv6) and AS numbers reasonably often.
So I say that applying for address space is a barrier to some - late last year I went back to work part-time at the local university. They hadn't applied for IPv6 space, I pushed and we now have a /32 and work is happening to deploy IPv6. You can argue that it was my pushing this that caused that change but I think that having the address space and feeling some obligation to use it hasn't hurt.