Alert Standard Format (ASF) Specification

Alert Standard Format (ASF) Specification v2.0 DMTF Document DSP0136
DSP0136 23 April 2003 Page 40 of 94
3.2.4.6 Open Session Response (43h)
A managed client sends this RSSP message to the management console in response to an Open
Session Request (83h) message. Following the Status Code, Mgt Console and Managed Client
Session ID fields, this message contains a single Authentication payload and a single Integrity
payload. These payloads represent the proposals that the managed client selected from the list
offered by the management console. The format of this 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 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 RSSP Open Session Request
(83h) message associated with this response.
9-12
Managed
Client
Session ID
The Session ID selected by the Managed Client for this new session. The
Bypass Session ID (see 3.2.3.1) is not valid in this context.
13-20
Authentication
Payload
This payload defines the authentication algorithm proposal selected by the
client to be used for this session (see 3.2.4.11 for the definition of this
payload).
21-28
Integrity
Payload
This payload defines the integrity algorithm proposal selected by the client
to be used for this session (see 3.2.4.11 for the definition of this payload).
3.2.4.7 Close Session Response (44h)
A managed client sends this RSSP message to the management console in response to a Close
Session Request (84h) message. The format of this message’s Data section is as follows:
Data
Byte(s)
Field Description
1 Status Code
Identifies the status of the previous message. See 3.2.3.5.1 for the status
codes defined for this message.
3.2.4.8 Presence Ping (80h)
A management console sends this RMCP message to the managed client to request a client to
respond with a Presence Pong (40h) message — if the client so responds, it signifies that it is
ASF-aware. Data Length for the sent message is set to 00h, no additional data is sent.
3.2.4.9 Capabilities Request (81h)
A management console sends this RMCP message to the managed client to request the client to
respond with a Capabilities Response (41h) message. Data Length for the sent message is set
to 00h, no additional data is sent.
3.2.4.10 System State Request (82h)
A management console sends this RMCP message to the managed client to request the client to
respond with a System State Response (42h) message. Data Length for the sent message is set
to 00h, no additional data is sent.