3 ms·
I am one of the authors of a draft that describes how to make the transition, at least for the "client" apps (like HTTP), more straightforward: http://tools.ie
by ay 16y ago
I am one of the authors of a draft that describes how to make the transition, at least for the "client" apps (like HTTP), more straightforward:
http://tools.ietf.org/html/draft-wing-http-new-tech http://tools.ietf.org/html/draft-wing-http-new-tech
Also, for the rogue RAs, there is a solution
too: http://tools.ietf.org/html/draft-ietf-v6ops-ra-guard http://tools.ietf.org/html/draft-ietf-v6ops-ra-guard
(currently shipping in some products already).
For security, there are better approaches that do not compromise the applications transparency as much as the filters do:
http://tools.ietf.org/html/draft-vyncke-advanced-ipv6-security http://tools.ietf.org/html/draft-vyncke-advanced-ipv6-securi...
To summarize, knowing Iljitch personally, I hoped for a more sober article. v4->v6 transition is not going to be easy, sure. But the article does come through as having a slightly hysteric tone, which is unfortunate.
As for "no customers" stance that I hear every now and then: Just today I had a chat with a large-ish service provider. They have quite a lot of enterprise customers for IPv6 today. XS4ALL provides IPv6 in .nl today. free.fr has been doing it for years already.
Finally, to end on a cheerful note - some folks have found this video funny, hopefully you might as well: http://www.xtranormal.com/watch/7011357/ http://www.xtranormal.com/watch/7011357/ - though I do not claim to have the best sense of humor.
- tptacek 16y agoWhat's the value proposition of an IPv6 address to any of (a) my mom, (b) a YC web app founder, or (c) a Fortune 500 company in the industry standard best-practices configuration of private non-routable addresses for internal hosts sitting behind a series of firewalls and proxies set up for policy reasons? A customer use case for any one of these scenarios would be enlightening.
- ay 16y ago(a) - When she would have to choose whether to pay $10 or $30 per month for the facebook. (b) - Experience, when down the road a year or two from now it will mean some real eyeballs. If you do not care about serving to mobile users, no need to bother. Maybe there are startups that are not just about webapps. (c) - they already have IPv6. On Vista and Windows7. Just that it travels over Teredo. Reason: visibility into the end-station traffic. I am not trying to convince you that IPv6 is the panacea. If you show me the compelling argument towards the standard p2p substrate that would not abuse the links between the ISPs too much, is standardized, has implementations in all the major OSes as part of standard distribution with similar API - or freely available in the source code form with the BSD or MIT license - I'd be happy to see it. Oh yes - and you can show the business cases for it for the above three participants, too, if you like. Oh, and of course it has to traverse multiple layers of NATs too. I'd seriously use it in some of the pet projects.
- tptacek 16y agoI'm not seeing the scenario where IPv4 costs my mom $20/mo for commodity web access. And even my mom has IPv6 software. Mysteriously enough, none of my clients --- large F-500's with network groups mature enough to have security teams sponsoring security reviews of applications --- none of them use IPv6 in production. Pretend I'm one of them and sell me an IPv6 deployment project.
- ay 16y agoI am not a sales guy. Surely you will he fine with NATs for some time. But this time is not infinite. And when it ends, you will be up for a harsh awakening. So, plan which of the scenarios is more appealing to you. If you plan a parachute in a year, do not bother. Otherwise discounted cash flow may help. Maybe it does not make sense to you now, fine. And let's chat in a year. No. I am not selling ipv6. It is there. Facebook and YouTube and tpb is on ipv6. Probably the only remaining part of internet not migrated yet is Craigslist.