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.

9.2.2 <strong>IP</strong>v6 addressing<br />

Fragment header<br />

The source node determines the maximum transmission unit or MTU for a path<br />

before sending a packet. If the packet to be sent is larger than the MTU, the<br />

packet is divided into pieces, each of which is a multiple of 8 bytes <strong>and</strong> carries a<br />

fragment header. We provide details about the fragmentation header in “<strong>IP</strong>v6<br />

packet fragmentation” on page 351.<br />

Authentication header<br />

The authentication header is used to ensure that a received packet has not been<br />

altered in transit <strong>and</strong> that it really came from the claimed sender. The<br />

authentication header is identified by the value 51 in the preceding Next Header<br />

field. For the format of the authentication header <strong>and</strong> further details about<br />

authentication, refer to 9.2.5, “<strong>IP</strong>v6 security” on page 347.<br />

Encapsulating Security Payload<br />

The Encapsulated Security Payload (ESP) is a special extension header, in that<br />

it can appear anywhere in a packet between the basic header <strong>and</strong> the upper<br />

layer protocol. All data following the ESP header is encrypted. For further details,<br />

see 9.2.5, “<strong>IP</strong>v6 security” on page 347.<br />

Destination options header<br />

This has the same format as the hop-by-hop header, but it is only examined by<br />

the destination node or nodes. Normally, the destination options are only<br />

intended for the final destination only <strong>and</strong> the destination options header will be<br />

immediately before the upper-layer header. However, destination options can<br />

also be intended for intermediate nodes, in which case, they must precede a<br />

routing header. A single packet can, therefore, include two destination options<br />

headers. Currently, only the Pad1 <strong>and</strong> PadN types of options are specified for<br />

this header (see “Hop-by-hop header” on page 335). The value for the preceding<br />

Next Header field is 60.<br />

The <strong>IP</strong>v6 address model is specified in RFC 4291 – <strong>IP</strong> Version 6 Addressing<br />

Architecture. <strong>IP</strong>v6 uses a 128-bit address instead of the 32-bit address of <strong>IP</strong>v4.<br />

That theoretically allows for as many as<br />

340,282,366,920,938,463,463,374,607,431,768,211,456 addresses. Even when<br />

used with the same efficiency as today's <strong>IP</strong>v4 address space, that still allows for<br />

50,000 addresses per square meter of l<strong>and</strong> on Earth.<br />

The <strong>IP</strong>v6 address provides flexibility <strong>and</strong> scalability:<br />

► It allows multilevel subnetting <strong>and</strong> allocation from a global backbone to an<br />

individual subnet within an organization.<br />

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

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

Saved successfully!

Ooh no, something went wrong!