Which extension header uses a variable-length Initialization vector (IV)?

Which extension header uses a variable-length Initialization vector (IV)?

Which extension header uses a variable-length Initialization vector (IV)?

A.
Authentication.

B.
Fragment.

C.
Encrypted security payload.

D.
Routing.

Explanation:
Payload Data is a variable-length field containing data described by the Next Header field. The
Payload Data field is mandatory and is an integral number of bytes in length. If the algorithm used
to encrypt the payload requires cryptographic synchronization data, e.g., an Initialization Vector
(IV), then this data MAY be carried explicitly in the Payload field. Any encryption algorithm that
requires such explicit, per-packet synchronization data MUST indicate the length, any structure for
such data, and the location of this data as part of an RFC specifying how the algorithm is used
with ESP. If such synchronization data is implicit, the algorithm for deriving the data MUST be part
of the RFC. (Reference RFC 2406)
Incorrect Answers:
A: These extension headers do not have the Initialization Vector.
B: These extension headers do not have the Initialization Vector.
D: These extension headers do not have the Initialization Vector.



Leave a Reply 0

Your email address will not be published. Required fields are marked *