DDS12 — Blocking of write() call

Blocking of write() call depending on RESOURCE_LIMITS, HISTORY, and RELIABILITY QoS

Summary:
Section 2.1.2.4.2.11 states that even writers with KEEP_LAST HISTORY QoS can block and describes some scenarios.
Some of these scenarios may no longer be valid depending on whether the implementation is willing to sacrifice reliability.

In the table in Section 2.1.3, it states the max_blocking _time in the RELIABILITY QoS only applies for RELIABLE and KEEP_ALL HISTORY QoS.
In Section 2.1.3.14 it is only mentioned that the writer can block if the RELIABILITY QoS is set to RELIABLE.

Proposed Resolution:
At the very least, remove mention of the requirement that the HISTORY QoS be KEEP_ALL for blocking to apply in the table in Section 2.1.3.

Proposed Revised Text:

Section 2.1.3 QoS Table
On the entry for the RELIABILITY QoS max_blocking_time
Replace:
This setting applies only to the case where kind=RELIABLE and the HISTORY is KEEP_ALL.
With:
This setting applies only to the case where kind=RELIABLE.

see above