HP-UX IPv6 Porting Guide (September 2004)
Table Of Contents
- About This Document
- 1 Introduction
- 2 IPv6 Addressing
- 3 Data Structure Changes
- 4 Migrating Applications from IPv4 to IPv6
- 5 Overview of IPv4 and IPv6 Call Set-up
- 6 Function Calls Converting Names to Addresses
- 7 Function Calls Converting IP addresses to Names
- 8 Reading Error Messages
- 9 Freeing Memory
- 10 Converting Binary and Text Addresses
- 11 Testing for Scope and Type of IPv6 addresses using Macros
- 12 Identifying Local Interface Names and Indexes
- 13 Configuring or Querying an Interface using IPv6 ioctl() Function Calls
- 14 Verifying IPv6 Installation
- 15 Sample Client/Server Programs
- A IPv4 to IPv6 Quick Reference Guide
Introduction
Do Existing IPv4 Applications Require Changes?
Chapter 1 3
Do Existing IPv4 Applications Require Changes?
No. Current IPv4 applications can remain unchanged. Modify applications only to take
advantage of new IPv6 features.
Does implementing IPv6 require a complete transition
from IPv4?
No. Networks can migrate to IPv6 gradually, using transition mechanisms defined by IPv6
Protocol Specifications. IPv4 and IPv6 will coexist for a long time. IPv6 Protocol Specifications
provide two major transition mechanisms:
Dual Stack: Dual-stack hosts have both IPv4 and IPv6 interfaces configured and can
communicate with both IPv4 and IPv6 hosts.
Tunneling: Tunneling is a mechanism that has been defined to allow IPv6 packets to be
encapsulated in IPv4 packets. A Dual-Stack host can send IPv6 packets through an IPv4
tunnel to a remote IPv6 host, without requiring an IPv6 infrastructure.