Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Each payload in Authenticated Internet Protocol messages starts with the Generic payload header, as specified in [RFC2408] section 3.2.
The following diagram shows the Generic payload header packet structure.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Next_Payload |
RESERVED |
Payload_Length |
|||||||||||||||||||||||||||||
Next_Payload (1 byte): Indicates the payload type of the next payload in the message. If the current payload is the last in the message, this field MUST be 0.
RESERVED (1 byte): Unused. This field MUST be set to 0. The responder MUST ignore this field.
Payload_Length (2 bytes): The length, in bytes, of this payload, including the Generic payload header.