DDS11 — (T#38) request-offered behavior for LATENCY_BUDGET

In par. (2.1.3.7) is described that latency budget will neither prohibit connectivity nor send notifications if incompatible. However it also describes the RxO compatibility rule that will never be visible to applications. This is somewhat confusing and this description is only required because this QoS attribute is specified to be subject to the RxO pattern, however, since the description states that the latency budget is a hint to the service and that the service may apply an additional delay for optimizations then are we really speaking of RxO between datawriters and datareaders?
Resolution:
Make latency budget truly RxO by making connectivity dependent of compatibility rules and adding appropriate error notifications.
Revised Text:
Remove the "therefore the service will not fail to match…" from section 2.1.3.7
Add new text that describes the RxO consequences

No Data Available