-
Key: DDSIRTP23-18
-
Legacy Issue Number: 16967
-
Status: closed
-
Source: Object Computing, Inc. - OCI ( Mr. Adam Mitz)
-
Summary:
Page: 123
Change: Scope of counts is underspecified: is a Heartbeat count scoped to one Writer; is an AckNack/NackFrag count scoped to a Reader itself or to a Reader's conversation with a given Writer? -
Reported: DDSI-RTPS 2.0b1 — Tue, 27 Dec 2011 05:00 GMT
-
Disposition: Resolved — DDSI-RTPS 2.3
-
Disposition Summary:
Clarify the scope of the HeartBeat and AckNack Submessage Count fields and how to deal with overflow in the count fields
The scope of the count fields of the HeartBeat and AckNack have been clarified to make it clear that it is up to the implementation if it keeps track of each endpoint separately or reuses the epoch across endpoints as long as the epoch changes from the previous one sent to an endpoint.
Clarification as to how overflow in these fields should be handled by an implementation has also been added.
-
Updated: Wed, 19 Dec 2018 16:38 GMT
DDSIRTP23 — Section 8.4.15.7: Scope of the count fields of Heartbeat and AckNack/NackFrag
- Key: DDSIRTP23-18
- OMG Task Force: DDSI-RTPS 2.3 RTF