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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Option 2 (target link layer address)<br />

Gives link address of router B so that node X can reach it<br />

without a neighbor solicitation.<br />

Option 4 (redirected header)<br />

Includes the original packet sent by node X, full <strong>IP</strong><br />

header, <strong>and</strong> as much of the data that will fit so that the<br />

total size of the redirect message does not exceed 576<br />

bytes.<br />

Neighbor unreachability detection<br />

An additional responsibility of the neighbor discovery function of ICMPv6 is<br />

neighbor unreachability detection (NUD).<br />

A node actively tracks the reachability state of the neighbors to which it is<br />

sending packets. It can do this in two ways: either by monitoring the upper layer<br />

protocols to see if a connection is making forward progress (for example, <strong>TCP</strong><br />

acknowledgments are being received), or issuing specific neighbor solicitations<br />

to check that the path to a target host is still available. When a path to a neighbor<br />

appears to be failing, appropriate action is taken to try <strong>and</strong> recover the link. This<br />

includes restarting the address resolution process or deleting a neighbor cache<br />

entry so that a new router can be tried in order to find a working path to the<br />

target.<br />

NUD is used for all paths between nodes, including host-to-host, host-to-router,<br />

<strong>and</strong> router-to-host. NUD can also be used for router-to-router communication if<br />

the routing protocol being used does not already include a similar mechanism.<br />

For further information about neighbor unreachability detection, refer to RFC<br />

2461.<br />

Stateless address autoconfiguration<br />

Although the 128-bit address field of <strong>IP</strong>v6 solves a number of problems inherent<br />

in <strong>IP</strong>v4, the size of the address itself represents a potential problem to the<br />

<strong>TCP</strong>/<strong>IP</strong> administrator. Because of this, <strong>IP</strong>v6 has been designed with the<br />

capability to automatically assign an address to an interface at initialization time,<br />

with the intention that a network can become operational with minimal to no<br />

action on the part of the <strong>TCP</strong>/<strong>IP</strong> administrator. <strong>IP</strong>v6 nodes generally use<br />

autoconfiguration to obtain their <strong>IP</strong>v6 address. This can be achieved using<br />

DHCP (see 9.5, “DHCP in <strong>IP</strong>v6” on page 371), which is known as stateful<br />

autoconfiguration, or by stateless autoconfiguration, which is a new feature of<br />

<strong>IP</strong>v6 <strong>and</strong> relies on ICMPv6.<br />

Chapter 9. <strong>IP</strong> version 6 363

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

Saved successfully!

Ooh no, something went wrong!