You are a mobile app developer or your business uses a mobile app, right? I know this is not news to you … or at least it should not be but here it goes anyway: http://www.internetsociety.org/deploy360/blog/2015/06/apple-will-require-ipv6-support-for-all-ios-9-apps/
In Apple’s words: ““Because IPv6 support is so critical to ensuring your applications work across the world for every customer, we are making it an AppStore submission requirement, starting with iOS 9.” ”
Or to put it plainly, no IPv6, no play in AppStore.
Now of course, you could always counter with: “That is OK, we just drop a translator in front of our backend and we are good”. Sure, why not and while you are at it, throw in a second translator just in case. You do know that all these hacks are not for free right? How big of a User Experience penalty are you comfortable with before the business guys call you up? Also, you had to put some time into fixing some of those glitches generated by network latency. How will that work for you with IPv6 and that nice translator?
My advice is: open up the books or eLearning and get familiar with IPv6. On one hand you might just build the app right from day one. On the other, you make the life easier for your sysadmin managing your cloud based backend. While you are at it, make sure you tell your Cloud provider that you expect native IPv6 access. And who knows, you might even find a way to make it better or a way to make it stand out. And don’t forget, all that monitoring you did for IPv4, has to be available over IPv6 as well. Otherwise you will simply not know what the customer is complaining about. By monitoring of course I mean User Experience as seen all the way to the RAN, maybe even to the end device.
Help us avoid stress, help yourself avoid embarrassment too. Just recently we started to see payloads with IPv4 addresses that include :. Better get back to that IPv6 Forum Silver engineer certification prep.