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.

► Identification, fragmentation flags, <strong>and</strong> fragment offset<br />

Fragmented packets have an extension header rather than fragmentation<br />

information in the <strong>IP</strong>v6 header. This reduces the size of the basic <strong>IP</strong>v6<br />

header, because higher-level protocols, particularly <strong>TCP</strong>, tend to avoid<br />

fragmentation of datagrams (this reduces the <strong>IP</strong>v6 header processing costs<br />

for the normal case). As noted later, <strong>IP</strong>v6 does not fragment packets en route<br />

to their destinations, only at the source.<br />

► Header checksum<br />

Because transport protocols implement checksums, <strong>and</strong> because <strong>IP</strong>v6<br />

includes an optional authentication header that can also be used to ensure<br />

integrity, <strong>IP</strong>v6 does not provide checksum monitoring of <strong>IP</strong> packets.<br />

Both <strong>TCP</strong> <strong>and</strong> UDP include a pseudo <strong>IP</strong> header in the checksums they use,<br />

so in these cases, the <strong>IP</strong> header in <strong>IP</strong>v4 is being checked twice.<br />

<strong>TCP</strong> <strong>and</strong> UDP, <strong>and</strong> any other protocols using the same checksum<br />

mechanisms running over <strong>IP</strong>v6, will continue to use a pseudo <strong>IP</strong> header<br />

although, obviously, the format of the pseudo <strong>IP</strong>v6 header will be different<br />

from the pseudo <strong>IP</strong>v4 header. ICMP, IGMP, <strong>and</strong> any other protocols that do<br />

not use a pseudo <strong>IP</strong> header over <strong>IP</strong>v4 use a pseudo <strong>IP</strong>v6 header in their<br />

checksums.<br />

► Options<br />

All optional values associated with <strong>IP</strong>v6 packets are contained in extension<br />

headers, ensuring that the basic <strong>IP</strong> header is always the same size.<br />

9.2.1 Extension headers<br />

Every <strong>IP</strong>v6 packet starts with the basic header. In most cases, this will be the<br />

only header necessary to deliver the packet. Sometimes, however, it is<br />

necessary for additional information to be conveyed along with the packet to the<br />

destination or to intermediate systems on route (information that would<br />

previously have been carried in the Options field in an <strong>IP</strong>v4 datagram). Extension<br />

headers are used for this purpose.<br />

Extension headers are placed immediately after the <strong>IP</strong>v6 basic packet header<br />

<strong>and</strong> are counted as part of the payload length. Each extension header (with the<br />

exception of 59) has its own 8-bit Next Header field as the first byte of the header<br />

that identifies the type of the following header. This structure allows <strong>IP</strong>v6 to chain<br />

multiple extension headers together. Figure 9-3 on page 334 shows an example<br />

packet with multiple extension headers.<br />

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

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

Saved successfully!

Ooh no, something went wrong!