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.6 Packet sizes<br />

If the algorithm used to encrypt the payload requires cryptographic<br />

synchronization data, for example, an Initialization Vector (IV), this data is carried<br />

in the Payload field.<br />

Any encryption algorithm that requires an explicit, per-packet synchronization<br />

data must indicate the length, any structure for such data, <strong>and</strong> the location of this<br />

data.<br />

If such synchronization data is implicit, the algorithm for deriving the data must<br />

be part of the algorithm definition.<br />

Note that the beginning of the next layer protocol header must be aligned relative<br />

to the beginning of the ESP header. For <strong>IP</strong>v6, the alignment is a multiple of 8<br />

bytes.<br />

All <strong>IP</strong>v6 nodes are expected to dynamically determine the maximum<br />

transmission unit (MTU) supported by all links along a path (as described in RFC<br />

1191 – Path MTU Discovery) <strong>and</strong> source nodes will only send packets that do<br />

not exceed the path MTU. <strong>IP</strong>v6 routers will, therefore, not have to fragment<br />

packets in the middle of multihop routes <strong>and</strong> allow much more efficient use of<br />

paths that traverse diverse physical transmission media. <strong>IP</strong>v6 requires that every<br />

link supports an MTU of 1280 bytes or greater.<br />

350 <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!