HP-UX IPv6 Transport Administrator's Guide (September 2004)

Features Overview
IPv6 Transport
Chapter 14
been no changes to the dual stack mechanism, but several important
changes to the tunneling mechanisms. The following RFCs are
supported in the HP-UX 11i v2 September 2004 release (the IETF
documents listed below are available at http://www.ietf.org):
RFC 2473 - Packet Tunneling in IPv6
RFC 2893 - Transition Mechanisms for IPv6 Hosts and Routers
RFC 3056 - Connection of IPv6 Domains via IPv4 Clouds
IMPORTANT As a result of supporting RFC 2893, tunnel configuration on HP-UX
11i v2 September 2004 software requires specific changes from
tunnel configurations on base (default) HP-UX 11i v2 software. For
detailed information, including specific configuration instructions,
refer to relevant sections of Chapter 2, “Configuration,”.
SAM has not been enhanced to support the tunneling enhancements
available with the HP-UX 11i v2 September 2004 release. HP-UX 11i
v2 September 2004 software tunneling configuration must be done
by editing the /etc/rc.config.d/netconf-ipv6 file or by using the
ifconfig command.
Configured tunneling is point-to-point with addresses
assigned to tunnel endpoints: In conformance with RFC 2893
(which obsoletes RFC 1933) configured tunnels are
pseudo-interfaces with associated addresses. Previously, when
conforming to RFC 1933, tunnels were implemented using
special routing entries. The RFC 1933 implementation did not
allow addresses to be associated with tunnels and hence, routing
protocol daemons were not able to operate over tunnels. To
overcome this problem, RFC 2893 specifies tunnels as IPv6
interfaces and requires them to be configured with at least (on
primary interfaces) link-local addresses.
As a result, the process for configuring tunnels using the
ifconfig and route commands and the
/etc/rc.config.d/netconf-ipv6 file is different than it was in
the base (default) HP-UX 11i v2 release.