Australian isps are rushing to deploy ipv6 within the expected time they will run out of addresses, all of the big players have known it was coming and in true corporate style, only started playing with it when the date drew near there would be no more v4 addesses to give people
Internode already has full deployment of ipv6.
iinet Expect to have dual stacks running to the end user by the end of the year.
Tpg have been testing it for the last six months and intend to deploy it to the public within the next three
Only optus and telstra refused to give solid approximations, each saying they have been testing it for the last six months plus but deployment dates are unknown
We are in the birthing stage of proper isp level ipv6 deployment, why make life harder than it is? just support it in conjunction with your original v4 setup as well.
If your "The sky is falling" diatribe was even close to being true
You don't get the point, your argument is that we should do absolutely nothing until the sky has fallen. I am at a loss at why you must continue to go "We won't do anything until there is a major problem" when the problem can be avoided with very little preparation.
I'm guessing you don't actively administer and monitor your networks then either yes? wait until something breaks until you fix it?
This was what I was arguing against more than anything, the attitude of "if it isn't broken yet (or isn't broken for me) don't make plans for when it happens"
Unless you care to say that ipv6 will 'never' be adopted, what reason is there to not support it in ipcop. And moreso doesn't the fact that quite a few people (I'm not alone in posting things like this) actually wish to deploy it signal to you that it is getting deployment?
Not to mention the chicken and the egg problem, it is attitudes like 'why should I deploy ipv6, nobody else has' that makes end to end difficult when people like you don't bother with it, your site becomes another one that is inaccessible by it.
IPv4 will be the standard for several years to come, then it will be a nightmare mix of 6-to-4 and 4-to-6 networks, and finally, years and years and years from now, it will all be native IPv6.
This depends on what you mean by 'several'. Address demand has been going up exponentially for the last two decades, you really think it won't continue to go up exponentially for at least a while longer? The present allocations the local isp's have will be burned through like they are nothing in sectors of heavy growth, and then even when ipv6 is deployed demand will continue to grow exponentially. Just look at how quickly we are burning through addresses now as opposed to then. It is also worth noting that even five years ago it was predicted we would start running out of addresses around now.
The predictions have changed since then a little, but only in the way of they thought IANA would run out in 2012 or 2013, happened a little quicker than expected. The reason everyone has been all 'lets implement ipv6 also' the last decade is because it's use is inevitable. As an administrator, which is a better situation for you, being prepared for something when it happens or being found running around putting out fires because even though you knew it was coming, you did nothing. Some people like to prepare very early, some late. I'd say when IANA runs out of addresses is a good time to start preparing because the next stage is when you plain can't get a new ipv4 address from your isp (or more likely they'll just start charging more for accounts with them).
Also, you want your network to be part of the 6-to-4 and 4-to-6 network chaos?
Let me know when you can order a IPv6 circuit (cable/dsl/wifi) to your home, with IPv6 numbers, with a IPv6 only gateway, and IPv6 only name servers
I can get all of the above except it is still dual stack for the present moment, not just only 6. When the isp's are coming to realize they have to start this soon or they will be stuck up a river without a paddle, don't you think it's about time you started thinking about it at least?
Anyway, in regards to ipcop, I would love to hear why ipcop should 'never' implement ipv6, considering that unless you think that is the case it WILL have to support it at some point. Why leave implementation to the last minute so that when you need it it is untested?
i know that ipcop is essentially a front end for the linux command line utilities that do nice networking business and i've used them before. Linux has had ipv6 support for over a decade. I would just like to know why being prepared for something that will (unless you disagree) become necessary is a bad thing.
You individually may not need to deploy ipv6 for another few years, but why should those that do be forced to go without a lovely gui for their router needs?