====== 16.4 Logical Communication Requirements ======
[[fxdemo:02-part:16-logical-requirements:start | Go To Logical Requirements ]]

This section identifies the normative requirements established for the Logical Communication Model. The canonical requirement statements are maintained in [[dido:99_annexes:annex-d-requirements:part-02:start|Annex C: Requirements, Part 2, Section 16.4]].

<WRAP table-caption>
**Table 16-3:** Logical Communication requirements.
</WRAP>

^ Requirement ID ^ Statement ^
| [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-001|P2-REQ-16-4-001]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-001#statement&noheader&nofooter}} |
| [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-002|P2-REQ-16-4-002]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-002#statement&noheader&nofooter}} |
| [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-003|P2-REQ-16-4-003]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-003#statement&noheader&nofooter}} |
| [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-004|P2-REQ-16-4-004]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-004#statement&noheader&nofooter}} |
| [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-005|P2-REQ-16-4-005]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-005#statement&noheader&nofooter}} |
| [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-006|P2-REQ-16-4-006]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-006#statement&noheader&nofooter}} |
| [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-007|P2-REQ-16-4-007]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-007#statement&noheader&nofooter}} |
| [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-008|P2-REQ-16-4-008]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-008#statement&noheader&nofooter}} |

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>