Issue 11041: Reader-side Heartbeat response suppression                                                                                                                                                              (dds-interop-ftf)
Source: Real-Time Innovations (Mr. Kenneth Brophy, ken@rti.com ken.brophy@rti.com)
Nature: Uncategorized Issue
Severity: 
Summary: 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:
 

Revised table 8.66

Attribute	Type	Meaning	Relation to DDS
heartbeatSuppressionDuration	Duration_t	Protocol tuning parameter that allows the RTPS Reader to ignore heartbeats that arrive 'too soon' after a previous heartbeat was received.	N/A

Resolution: see above
Revised Text: see pages 47 and 48 of ptc/2007-06-2
Actions taken:
May 23, 2007: received issue
November 7, 2007: closed issue
Discussion: 
Add reader attribute, heartbeatSuppressionDuration, that defines the duration in which received heartbeats are suppressed from triggering duplicate ACKNACKs.


End of Annotations:=====
s is issue #11041 (SEE ATTACHED ALSO)

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:
 

Revised table 8.66

Attribute	Type	Meaning	Relation to DDS
heartbeatSuppressionDuration	Duration_t	Protocol tuning parameter that allows the RTPS Reader to ignore heartbeats that arrive 'too soon' after a previous heartbeat was received.	N/A



=============================================================