Dan York - Migrating Applications to IPv6

Copyright 2011 Dan York

OReilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (.

Nutshell Handbook, the Nutshell Handbook logo, and the OReilly logo are registered trademarks of OReilly Media, Inc. Migrating Applications to IPv6 , the image of a brant goose, and related trade dress are trademarks of OReilly Media, Inc.

Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and OReilly Media, Inc., was aware of a trademark claim, the designations have been printed in caps or initial caps.

While every precaution has been taken in the preparation of this book, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.

How badly will IPv6 break your application? What do you need to consider to make your application IPv6-ready? What questions should you ask?

In the ideal world, your application should just work on IPv6, just as it does on IPv4. However, in the real world, application issues crop up. These could be as simple as having a user interface field that only allows the input of dotted-decimal IPv4 addresses, or something more fundamental, such as an application binding exclusively to an IPv4 transport interface.

While there have been many books published about IPv6, including OReillys own IPv6 Essentials and IPv6 Network Administration , almost all existing books focus on understanding the protocol itself and using it at a network layer. They contain much discussion about using network-level tools and even about creating applications that interact directly with the network. However, the concerns related to IPv6 at the upper application layers are mentioned only briefly, if at all. The Internet Engineering Task Force (IETF) has published RFC 4038, which addresses many of these concerns, but the concerns have not found their way out into mainstream books.

This short book is designed to help you understand what you need to think about to be sure that your app will work as well with IPv6 as it does with IPv4. This book is not so much about all the solutions but rather about the questions you need to be asking.

For IPv6 to truly be adopted on a large scale, ultimately the applications running on our desktop systems, laptops, and mobile devices all need to play nice with IPv6. That is the end goal of this bookto help enable individuals, companies, and organizations to migrate their apps to IPv6 so that they can transition their networks into IPv6 networks .

Given that now, in 2011, many companies are just starting to pay attention to IPv6, and given that many apps are just now moving to IPv6, this book will continue to evolve to address issues identified as more applications make the move. Id love to receive any feedback you have on issues you encounter in migrating your apps to IPv6and I expect that youll see updates to this book come out over time.

Are you an application developer? A product manager? A product marketing manager? A documentation author? A training instructor? A system/network architect? This book is designed to help you understand what issues you need to explore with your application .

Developers, you will come away with enough information to go through your application and make the necessary changes. Product managers, you will gain an understanding of what points you need to considerand what you need to ask of your technical teams. If you are in marketing, documentation, or training, you will get a good sense of what youll need to think about changing in your materials. And if you are a system/network architect looking at your overall IPv6 implementation, you should leave with a better sense of what changes may need to be considered across the applications that are deployed in your infrastructure.