DDSIRTP22 — Reader-side Heartbeat response suppression

Source:
Real-Time Innovations, Inc. (Ken Brophy, ken@rti.com)
Summary:
The specification does not prevent multiple Heartbeats from arriving in rapid succession. For example, the piggyback heartbeat of a repair message may immediately be followed by a periodic wildcard heartbeat. In order to prevent duplicate repair sessions, the specification should define heartbeat suppression on the reader's side. This heartbeat response suppression should be handled by a reader attribute that controls the duration for which duplicate heartbeats would be ignored.

Resolution:
Add reader attribute, heartbeatSuppressionDuration, that defines the duration in which received heartbeats are suppressed from triggering duplicate ACKNACKs.

Revised Text:
Revised figure 8.21:

This issue was already resolved as part of the FTF, in that report it is labeled as
issue 11041. It appears that a typographical mistake was made in the report (or else
something changed in the database) so that the issue was not closed in the OMG
database.
Revised Text:
Disposition: NoChange