Go To Phase 0 QoS Profile Model
The Control Plane QoS profile supports operational coordination, commands, acknowledgments, registration, retry, recovery, and status-request interactions.
Control Plane communication must prioritize clear delivery semantics and command accountability. A command-producing participant must know whether a command was received, accepted, rejected, completed, failed, or timed out according to the Phase 0 command and acknowledgment conventions.
Table 13-1: Control Plane QoS profile.
| QoS Concern | Phase 0 Treatment |
|---|---|
| Runtime Plane | FX Logical Control Plane |
| Example DDS Topics | Control.FX.ControlCommand; Control.FX.CommandAcknowledgement |
| Communication purpose | Operational coordination, command exchange, acknowledgment, retry, pause, resume, stop, restart, status request, and recovery coordination |
| Reliability expectation | Reliable delivery where Phase 0 requires command accountability |
| Durability expectation | Sufficient durability to support late-joining participants where Phase 0 requires command or acknowledgment review |
| History expectation | Retain enough command and acknowledgment history to support Phase 0 review and troubleshooting |
| Ordering expectation | Preserve command order where command sequence affects Node behavior |
| Liveliness expectation | Support detection of unavailable command-producing or command-consuming participants where Phase 0 requires it |
| Compatibility expectation | Command producers and consumers use compatible QoS profiles for relevant command and acknowledgment Topics |
| Traceability expectation | QoS profile traces to FX Control Command Endpoint, FX Control Command, FX Command Acknowledgement, and FX Logical Control Plane |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.