Technical data

For more information about tunnels refer to Compaq TCP/IP Services for
OpenVMS Guide to IPv6.
TCP/IP Services Version 5.3 includes support for a new tunnel IPv6 transition
mechanism called 6to4, as defined in RFC 3056.
For more information about the 6to4 mechanism, refer to the TCP/IP Services
release notes.
9.3 Developing an Implementation Plan
The following three scenarios, in order of increasing complexity, serve as models for
deploying IPv6 in your network:
• Intranet
• Intranet-to-internet
• Intranet-to-internet-to-intranet
The following sections describe each scenario.
9.3.1 Intranet Scenario
In this scenario, you deploy IPv6 hosts on a small subnet in your network. These
hosts communicate with each other using link-local addresses. If you add an IPv6
router to the subnet and advertise an address prefix, each IPv6 host autoconfigures
a global IPv6 address and uses that address to communicate with other IPv6 hosts.
As you become more experienced with using IPv6, for the next phase you can add
an IPv6 host or hosts on other subnets in your network. Communications between
IPv6 hosts on different subnets occur using configured router-to-host tunnels and
host-to-router tunnels. The existing IPv4 routing infrastructure is used to get
the packets end to end.
The following figures illustrate an intranet scenario in which a corporation has
three departments in a local geographic area. Department A has deployed v4/v6
hosts and a v4/v6 router. Departments B and C have deployed only one v4/v6
host each, with a majority of v4 hosts.
In Figure 9–1, to communicate with host F, native IPv6 traffic is routed from host
A to host F via router A.
9–4 IPv6