|
No IPv6
Router
A network that has a smaller scope of connectivity for IPv6 as it does
for IPv4 could be a problem in some cases. Hosts will attempt to
communicate with IPv6 destinations that are outside the scope of the
IPv6 routing, and depending on how the scope boundaries are enforced,
applications may not be notified that packets are being dropped at the
scope boundary. If applications aren't immediately notified of the lack
of ability to reach IPv6 destinations, then they aren't able to
efficiently fall back to IPv4. |
Poor IPv6
Network Performance
Another problem is the poor performance of IPv6’s network. By default
applications will try IPv6 destinations first under the dual stack
nodes. If the IPv6 connectivity to those destinations is poor while the
IPv4 connectivity is better, applications will still communicate over
IPv6. There is no information available to applications in this case to
advise them to try another destination address. |
Security
Security is another issue that has come up. The enabling of IPv6 on a
host implies that the services on the host may be open to IPv6
communication. If the service itself is insecure and depends on security
policy enforced somewhere else on the network then there is potential
for new attacks against the service. A firewall would not work in this
case because it may not be enforcing the same policy for IPv4 as for
IPv6 traffic. It could have a more flexible policy for IPv6 traffic.
|
