Kofax Communication Server 10.0.0 - Manual (Page 66)

Environment Guide Version 10.00.00
66 © Copyright Kofax. All information is subject to change without notice.
The interface has the following IPv6 addresses assigned:
1. unique-local address fd96:eb5f:7508:5760:204:23ff:feac:4172
Its interface identifier 204:23ff:feac:4172 is the EUI-64 representation of the MAC address 00-04-23-
AC-41-72
(the 16 bit sequence fffe is being inserted per EUI-64, the highest octet of the MAC address 00 has
been converted to 02 due to the fact that the Universal/Local bit in the highest octet of the MAC
address is per EUI-64 complemented, in this case from 0 to 1)
2. link-local address fe80:: 204:23ff:feac:4172
The link-local address has been generated automatically by the Windows 2008 / Windows 7 without
any router intervention.
6.4 IPv4 to IPv6 Migration Scenarios
Prior to KCS version 9.0, KCS product family has been using only IPv4 protocol stack as for the TCP/IP
communication for own inter-module connectivity but also for interconnections with external products. But in
the world the migration to IPv 4‟s successor – the IPv6 protocol stack – has already begun.
It is obvious that it is not possible to upgrade huge IPv4 based networks for IPv6 in one step (neither public
Internet nor large private networks) and therefore most enterprises will start performing the transition from
IPv4 towards IPv6 in a step by step manner.
There are three typical strategies how an enterprise can go for IPv6.
6.4.1 Scenario 1: Dual-Stack Network
Administrators start to equip their network nodes (host computers, routers, gateways) with the IPv6 protocol
stack and thus making them IPv4/IPv6 enabled nodes. Each node will be assigned both IPv4 and IPv6
addresses on the same network interface. IPv4/IPv6 enabled applications may communicate with each the
other via either IPv4 or IPv6 protocol. After all network nodes have been IPv6 enabled, the IPv4 support
could be eventually switched off, making the networks IPv6 only one.
The obvious disadvantage of this scenario is the necessity of having both IPv4 and IPv6 routing intact and
this making the network very complex.
6.4.2 Scenario 2: Adding IPv6 Infrastructure
Administrators leave their IPv4 network as it is but start adding IPv6 sub-networks, for example, by starting
to replace the network equipment of chosen subsidiaries. These IPv6-only sub-networks will be then
interconnected through the IPv4 networks using any of IPv6 through IPv4 tunneling techniques like 6to4,
ISATAP.