Alert Standard Format (ASF) Specification

Alert Standard Format (ASF) Specification v2.0 DMTF Document DSP0136
DSP0136 23 April 2003 Page 47 of 94
3.2.6 RMCP Considerations for LAN Alert-sending Devices
For the RMCP protocol to function in an OS-absent state, the alert-sending device must be
capable of reporting its “network address / IP address” association to the local router. The ARP
(Address Resolution Protocol), defined in [RFC1188], is typically used to accomplish this task.
To guarantee inter-operability, the alert-sending device must:
• Receive ARP Requests and reply with ARP Replies in an OS-absent state.
• Allow ARP Request packets to go to the network software stack in OS-present states.
• Allow ARP Request packets and RMCP packets to cause wake-ups if configured for wake-up
in the default configuration.
For Ethernet and Token-ring devices, wake-ups from ARP Requests and RMCP packets are not
desired in a managed client because these operations are expected to function in low power
sleep states. However, the [NDCPM] requires that wake-up devices support detection of any
software programmed packets as well as subsequent wake-up generation. Alert-sending devices
that support wake-up generation are expected to meet the [NDCPM] in their default configuration.
However, it is recommended that these alert-sending devices and their software provide
configuration mechanisms to allow ARP Request and RMCP packets to be blocked from wake-
up.
Note: ARP Request packets and IP Directed packets (which include RMCP packets) are
standard packet configurations for wake-up in ACPI systems.