507   ClockNotSynchronized

Created: 18 Apr 2007

Status: Ballot Period

Part: Part 7-2 (2003)

Links:

Page: 24

Clause: Table 8

Paragraph: § 5.5.3.7.3.3

Category: Issue for edition 2 of this part

Issue

Is there any reason to have O as M/O value in table 8 for the attribute ClockNotSynchronized ?

In addition in the text p 25, it is not written which meaning is attached to the value TRUE/FALSE (note such an information is detailed for LeapSecondsKnown).

Proposal

Change the M/O value for ClockNotSynchronized by replacing O with M.

Precise that TRUE means clock not synchronized and FALSE means clock synchronized (or the opposite).

Discussion Created Status
Accepted.

1. ClockNotSynchronized

The mapping in 8-1 has this attribute anyway.

Change the M/O value for ClockNotSynchronized to M.

Some discussion:
If the attribute would be Optional and not be communicated this could mean the clock is or is not synchronized.
If the sender does not know if the time is synchronized or not and if the parameter is Mandatory, what should it communicate? A TRUE or FALSE? I guess this is the reason to define it Optional: not available means: Sender does not know.
Is that true?

2. Add the definition of TRUE and FALSE in Clockfailure and ClockNotSynchronized.
17 Feb 08 Ballot Period

 

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1