Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: ENCODINGS PR02
    • Fix Version/s: None
    • Labels:
      None
    • Environment:

      TAB Review

    • Resolution:
      Hide

      Rephrased it to: The time encoding works similar to reltime using a number of seconds or nanoseconds for the current time of the day. The provided number SHOULD NOT exceed a time representing 24:00:00.

      Show
      Rephrased it to: The time encoding works similar to reltime using a number of seconds or nanoseconds for the current time of the day. The provided number SHOULD NOT exceed a time representing 24:00:00.

      Description

      "3.3.7 Time Encodings

      reads in part:


              • 0 sec unsigned 32-bit number of seconds since midnight

      1 ns unsigned 64-bit number of nanoseconds since midnight

      Does not define midnight sufficiently for interchange of values. A 32-bit number can express unsigned 0 through 4,294,967,295. The maximum number of seconds in a day, leaving aside some leap year adjustments, is 864,000. The behavior of a conforming application that sends or receives more than 864,000 is undefined. The same argument applies to nanoseconds.

      "

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              toby.considine Toby Considine (Inactive)
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: