Alert Standard Format (ASF) Specification
Alert Standard Format (ASF) Specification v2.0 DMTF Document DSP0136
DSP0136 23 April 2003 Page 21 of 94
Contents Type Offset Value
Version 1 byte 00h Copied from the received message
Reserved 1 byte 01h Copied from the received message.
Sequence Number 1 byte 02h Copied from the received message.
Class of Message 1 byte 03h Bit(s) Description
7 Set to 1 to indicate acknowledgement.
6:0 Copied from the header of the received message.
RMCP Header for
Acknowled
g
e
Notes:
1. The RMCP Acknowledge does not have an RMCP Data block; only the RMCP Header is
returned.
2. An RMCP Acknowledge must not, itself, be acknowledged.
3.2.2.2 RMCP Header
The RMCP header fields are as specified in the following table. Sequence numbers are used to
ensure reliability over an inherently unreliable protocol (like UDP) and facilitate message ordering
and recognition of identical messages. The Sequence Number is incremented each time a
unique message is sent from the same source (e.g. a management console or a client system).
When the message initiator retries a message, possibly due to a missing RMCP Acknowledge,
the initiator sends the exact message of the original transmission with the same Sequence
Number; this allows the initiator to match an RMCP message to its associated acknowledgement.
Contents Type Offset Value
Version 1
byte
00h This field identifies the version of the RMCP header. A value of 06h in the
field indicates RMCP v1.0.
0-5 Legacy RMCP
6 ASF RMCP Version 1.0
7- 255 Reserved for future definition by this specification.
Reserved 1
byte
01h Reserved for future definition by this specification, set to 00h.
Sequence
Number
1
byte
02h The sequence number associated with the message. Sequence numbers
should increase monotonically from each RMCP message source, in the
range 0 to 254, and then rollover back to 0. A Sequence Number field of
255 (FFh) has special meaning — it identifies that the receiver of the
message must not
provide acknowledgement.
Class of
Message
1
byte
03h This field identifies the format of the messages that follow this header. All
messages of class ASF (6) conform to the formats defined in this
specification.
Bit(s) Description
7 Message Type. Set to 1 to indicate an Acknowledge message
(see 3.2.2.1); set to 0 otherwise.
6:4 Reserved for future definition by this specification, set to 000b.
3:0 Message Class. Set to one of the following values:
0-5 Reserved
6 ASF
7 IPMI
2
8 OEM-defined
9-15 Reserved for future definition by this specification.
RMCP Header
2
The format and specification of messages under this class will be specified in the IPMI
(Intelligent Platform Management Interface) specifications. Information on IPMI can be obtained
from the IPMI web site: http://developer.intel.com/design/servers/ipmi