-
Key: DDSIRTP22-17
-
Legacy Issue Number: 16975
-
Status: closed
-
Source: Object Computing, Inc. - OCI ( Mr. Adam Mitz)
-
Summary:
Page: 153
Change: In NTP, TIME_ZERO represents a point in time in 1900. If this was followed by RTPS with its 31-bit field for positive seconds, the maximum point in time would be in 1968, long before RTPS was invented. Therefore the meaning of TIME_ZERO must be specified here. Additionally, leaving only 31 bits for positive seconds and assuming 1970 is used as TIME_ZERO, RTPS times are only valid through 2038. Is there a need for a sign bit in “seconds”? -
Reported: DDSI-RTPS 2.0 — Tue, 27 Dec 2011 05:00 GMT
-
Disposition: Resolved — DDSI-RTPS 2.2
-
Disposition Summary:
The format used is similar to NTP in that is uses seconds and fractions of a second
(to make arithmetic simple) rather than seconds and nanoseconds. However it uses
a signed seconds such that signed arithmetic can be applied.
For these reasons and to facilitate conversion to operating system times (timeval and
timespec) the time origin TIME_ZERO is defined to be the Unix prime epoch 0h, 1
January 1970 -
Updated: Fri, 6 Mar 2015 20:58 GMT
DDSIRTP22 — Section: 9.3.2, Table 9.4
- Key: DDSIRTP22-17
- OMG Task Force: Data Distribution Interoperability 2.2 RTF