Alert Standard Format (ASF) Specification

Alert Standard Format (ASF) Specification v2.0 DMTF Document DSP0136
DSP0136 23 April 2003 Page 43 of 94
Data
Byte(s)
Field Description
1 Status Code
Identifies the status of the previous message. If the previous message
generated an error, then only the Status Code, Reserved, and Mgt Console
Session ID fields are returned. See 3.2.3.5.1 for the status codes defined for
this message.
2-4 Reserved Reserved for future definition by this specification, set to 000000h
5-8
Mgt Console
Session ID
The Mgt Console Session ID specified by the RSSP Open Session Request
(83h) message associated with this response.
9-24
Managed
Client
Random
Number
Random number selected by the managed client.
25-40
Managed
Client
GUID
The Globally Unique ID (GUID) of the Managed Client. This value is
specified by the client system’s SMBIOS implementation. See 4.2.1 System
Information (Type 1) for details.
41-
variable
Integrity
Check
Value
An integrity check value over the relevant items specified by the RAKP
algorithm for Message 2 (see page 30). The size of this field depends on
the specific algorithm that was selected when the session was created.
3.2.4.15 RAKP Message 3 (C2h)
A management console sends this RAKP message to a managed client in response to the receipt
of an RAKP Message 2 (C1h). Once it validates RAKP Message 2, the management console
creates a Session Integrity Key using the values specified by the RAKP algorithm (see page 31).
The management console then computes an Integrity Check Value over the values specified by
the RAKP algorithm, and sends that along with the Managed Client Session ID (sent by the
managed client on the previous RMCP Open Session Response message) to the managed
client.
After receiving RAKP Message 3, the managed client verifies that the Managed Client Session ID
is active and then validates the Integrity Check Value. If the Integrity Check Value is valid, the
managed client creates a Session Integrity Key using the values specified by the RAKP algorithm
(see page 31). With the shared Session Integrity Key in place, integrity protected messages can
now be exchanged between the management console and the managed client.
The format of an RAKP Message 3 message’s Data section is as follows:
Data
Byte(s)
Field Description
1 Status Code
Identifies the status of the previous message. If the previous message
generated an error, then only the Status Code, Reserved, and Managed
Client Session ID fields are returned. See 3.2.3.5.1 for the status codes
defined for this message.
2-4 Reserved Reserved for future definition by this specification, set to 000000h
5-8
Managed
Client
Session ID
The Managed Client’s Session ID for this session, returned by the client on
the previous RSSP Open Session Response (44h) message.
9-
variable
Integrity
Check
Value
An integrity check value over the relevant items specified by the RAKP
algorithm for Message 3. The size of this field depends on the specific
algorithm that was selected when the session was created.