25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

► If the destination is not on the same subnet but there is at least one default<br />

router on the subnet that is <strong>IP</strong>v6-capable, or there is a route configured to an<br />

<strong>IP</strong>v6 router for that destination, send it to that router using <strong>IP</strong>v6. Otherwise, if<br />

the address is an <strong>IP</strong>v4-compatible address, send the packet using automatic<br />

<strong>IP</strong>v6-over-<strong>IP</strong>v4 tunneling. Otherwise, the destination is a node with an<br />

<strong>IP</strong>v6-only address that is connected through an <strong>IP</strong>v4-routed area, which is not<br />

also <strong>IP</strong>v6-routed. Therefore, the destination is unreachable.<br />

Note: The <strong>IP</strong> address must be <strong>IP</strong>v4-compatible for tunneling to be used.<br />

Automatic tunneling cannot be used to reach <strong>IP</strong>v6-only addresses,<br />

because they cannot be addressed using <strong>IP</strong>v4. Packets from <strong>IP</strong>v6/<strong>IP</strong>v4<br />

nodes to <strong>IP</strong>v4-mapped addresses are not tunnelled to because they refer<br />

to <strong>IP</strong>v4-only nodes.<br />

These rules emphasize the use of an <strong>IP</strong>v6 router in preference to a tunnel for<br />

three reasons:<br />

► There is less inefficiency, because there is no encapsulating <strong>IP</strong>v4 header.<br />

► <strong>IP</strong>v6-only features are available.<br />

► The <strong>IP</strong>v6 routing topology will be used when it is deployed in preference to<br />

the pre-existing <strong>IP</strong>v4 topology.<br />

A node does not need to know whether it is attached to an <strong>IP</strong>v6-routed or an<br />

<strong>IP</strong>v4-routed area; it will always use an <strong>IP</strong>v6 router if one is configured on its<br />

subnet <strong>and</strong> will use tunneling if one is not (in which case it can infer that it is<br />

attached to an <strong>IP</strong>v4-routed area).<br />

Automatic tunneling can be either host-to-host, or it can be router-to-host. A<br />

source host will send an <strong>IP</strong>v6 packet to an <strong>IP</strong>v6 router if possible, but that router<br />

might not be able to do the same, <strong>and</strong> will have to perform automatic tunneling to<br />

the destination host itself. Because of the preference for the use of <strong>IP</strong>v6 routers<br />

rather than tunneling, the tunnel will always be as “short” as possible. However,<br />

the tunnel will always extend all of the way to the destination host. Because <strong>IP</strong>v6<br />

uses the same hop-by-hop routing paradigm, a host cannot determine if the<br />

packet will eventually emerge into an <strong>IP</strong>v6-complete area before it reaches the<br />

destination host. In order to use a tunnel that does not extend all of the way to<br />

the recipient, configured tunneling must be used.<br />

The mechanism used for automatic tunneling is very simple:<br />

1. The encapsulating <strong>IP</strong>v4 datagram uses the low-order 32 bits of the <strong>IP</strong>v6<br />

source <strong>and</strong> destination addresses to create the equivalent <strong>IP</strong>v4 addresses<br />

<strong>and</strong> sets the protocol number to 41 (<strong>IP</strong>v6).<br />

382 <strong>TCP</strong>/<strong>IP</strong> <strong>Tutorial</strong> <strong>and</strong> <strong>Technical</strong> <strong>Overview</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!