2.2.3 Payload Types
The Authenticated Internet Protocol reuses the following payload types from [RFC2408] section 3.1.
|
RFC 2408 payload types |
Value |
|---|---|
|
NONE |
0x00 |
|
0x01 |
|
|
Proposal (P) |
0x02 |
|
Transform (T) |
0x03 |
|
0x04 |
|
|
Identification (ID) |
0x05 |
|
Hash (HASH) |
0x08 |
|
Nonce (NONCE) |
0x0A |
|
Notification (N) |
0x0B |
|
Vendor ID |
0x0D |
The Certificate, Certificate Request, Signature, and Delete payload types are not used by the Authenticated Internet Protocol. Certificate-based authentication is performed in this protocol through GSS-API, as described in [MS-AUTHSOD].
This protocol also defines the following additional payload types. The payload types are allocated from the private use range as defined in [RFC2408] section 3.1.
|
AuthIP payload types |
Value |
|---|---|
|
Security Support Provider Interface Token (GSS-API) as defined in [GSS] |
0x81 |
|
Crypto payload (CRYPTO) |
0x85 |
|
GSS-API Endpoint Name (GSS_ID) |
0x86 |
|
Authentication (Auth) |
0x87 |
Implementers can add additional payload types for their own purposes.