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.

348 <strong>TCP</strong>/<strong>IP</strong> <strong>Tutorial</strong> <strong>and</strong> <strong>Technical</strong> <strong>Overview</strong><br />

receiver to identify the Security Association (SA) to which<br />

an incoming packet is bound.<br />

For a unicast SA, the SPI can be used by itself to specify<br />

an SA, or it can be used in conjunction with the <strong>IP</strong>Sec<br />

protocol type (in this case AH).The SPI field is m<strong>and</strong>atory.<br />

Traffic to unicast SAs described earlier must be supported<br />

by all AH implementations.<br />

If an <strong>IP</strong>Sec implementation supports multicast, it must<br />

support multicast SAs using a special de-multiplexing<br />

algorithm.<br />

Sequence Number This unsigned 32-bit field contains a counter value that<br />

increases by one for each packet sent, that is, a per-SA<br />

packet sequence number.<br />

For a unicast SA or a single-sender multicast SA, the<br />

sender must increment this field for every transmitted<br />

packet. Sharing an SA among multiple senders is<br />

permitted, though generally not recommended.<br />

The field is m<strong>and</strong>atory <strong>and</strong> must always be present even<br />

if the receiver does not elect to enable the anti-replay<br />

service for a specific SA. Processing of the Sequence<br />

Number field is at the discretion of the receiver, but all AH<br />

implementations must be capable of performing the<br />

processing, Thus, the sender must always transmit this<br />

field, but the receiver need not act upon it.<br />

The sender's counter <strong>and</strong> the receiver's counter are<br />

initialized to 0 when an SA is established. The first packet<br />

sent using a given SA will have a sequence number of 1;<br />

if anti-replay is enabled (the default), the transmitted<br />

sequence number must never be allowed to cycle.<br />

Therefore, the sender's counter <strong>and</strong> the receiver's counter<br />

must be reset (by establishing a new SA <strong>and</strong> thus a new<br />

key) prior to the transmission of the 232 packet on an SA.<br />

Extended (64-bit) Sequence Number (ESN)<br />

To support high-speed <strong>IP</strong>Sec implementations, a new<br />

option for sequence numbers should be offered, as an<br />

extension to the current, 32-bit sequence number field.<br />

Use of an Extended Sequence Number (ESN) must be<br />

negotiated by an SA management protocol. The ESN<br />

feature is applicable to multicast as well as unicast SAs.<br />

Integrity Check Value (ICV)

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

Saved successfully!

Ooh no, something went wrong!