Alert Standard Format (ASF) Specification

Alert Standard Format (ASF) Specification v2.0 DMTF Document DSP0136
DSP0136 23 April 2003 Page 42 of 94
3.2.4.13 RAKP Message 1 (C0h)
A management console sends this RAKP message to the managed client to begin the session
authentication process. The management console selects a Mgt Console Random Number, a
Mgt Console User Role, and an optional Mgt Console User Name and sends them to the
managed client along with the Managed Client Session ID specified by the client on the previous
Open Session Response (44h).
Upon receiving RAKP Message 1, the managed client verifies that the message contains an
active Managed Client Session ID and that a session can be created using the requested user
information by evaluating of the Device Security Policy. The managed client responds with an
RAKP Message 2 (C1h).
The format of an RAKP Message 1 message’s Data section is as follows:
Data
Byte(s)
Field Description
1-4
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.
5-20
Mgt Console
Random
Number
Random number selected by the Mgt Console
21
Mgt Console
User Role
The Role that the user at the Mgt Console wishes to assume for this
session. Defined Roles are:
Bit(s) Value/Meaning
7:4 Reserved for future definition by this specification, set to 0000b
3:0 0000b Operator
0001b Administrator
0010b-1111b Reserved for future definition by this specification
22-23 Reserved Reserved for future definition by this specification, set to 0000h
24
Mgt Console
User Name
Length
The length in bytes of the Mgt Console user name
00h No name present
01h-10h Name length
11h-FFh Reserved for future definition by this specification
25-40
Mgt Console
User Name
(optional)
A non-NULL terminated ASCII character Name that the user at the Mgt
Console wishes to assume for this session. No NULL characters (00h) are
allowed in the name.
3.2.4.14 RAKP Message 2 (C1h)
A managed client sends this RAKP message to a management console in response to the receipt
of an RAKP Message 1 (C0h). Once RAKP Message 1 has been validated (see page 30), the
managed client selects a Managed Client Random Number and computes an Integrity Check
Value over the values specified by the RAKP algorithm. The managed client sends those values
along with the Managed Client Globally Unique ID (GUID) and the Mgt Console Session ID (sent
by the console on the previous Open Session Request) to the management console.
Upon receiving RAKP Message 2, the management console verifies that the Mgt Console
Session ID is active and that the Managed Client GUID matches the managed client that the
management console has associated with the session. The management console then validates
the Integrity Check Value and responds with an RAKP Message 3 (C2h).
The format of an RAKP Message 2 message’s Data section is as follows: