View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000851310000-006: MappingsSpecpublic2022-12-06 14:172023-04-04 15:47
ReporterDavid Levine Assigned ToRandy Armstrong  
PrioritynormalSeverityminorReproducibilityN/A
Status closedResolutionno change required 
Product Version1.05.02 RC1 
Summary0008513: Section 6.3 Time Synchronization needs clarification on use of timestamp in response header
Description

3rd para says:
"If a device operating system cannot practically support NTP then an OPC UA application can use the Timestamps in the ResponseHeader (see OPC 10000-4) to synchronize its clock."

This does not account for latencies and other network and time sync issues. It also appears to apply mainly for client apps, not server apps, as it calls for periodically contacting a discovery server, which most servers will not do. The text should describe what it is suitable for, e.g. certificate expiration checks, but not for timestamps applied to values.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Randy Armstrong

2023-03-31 04:56

administrator   ~0019070

A device that cannot support NTP can't support it so the question of whether an LDS derived clock is not accurate enough is moot because an inaccurate LDS derived clock is better than nothing.

What is the point of clarifying this?

Randy Armstrong

2023-03-31 04:59

administrator   ~0019071

Now state that an LDS derived clock may not be suitable for some uses in 6.3.

Randy Armstrong

2023-04-04 15:47

administrator   ~0019091

Decided that the fix was worse than the problem.

No changes are required.

Jim Luth

2023-04-04 15:47

administrator   ~0019092

Agreed to no-fix in web meeting.

Issue History

Date Modified Username Field Change
2022-12-06 14:17 David Levine New Issue
2023-03-14 15:18 Jim Luth Assigned To => Randy Armstrong
2023-03-14 15:18 Jim Luth Status new => assigned
2023-03-31 04:56 Randy Armstrong Status assigned => feedback
2023-03-31 04:56 Randy Armstrong Note Added: 0019070
2023-03-31 04:59 Randy Armstrong Status feedback => resolved
2023-03-31 04:59 Randy Armstrong Resolution open => fixed
2023-03-31 04:59 Randy Armstrong Note Added: 0019071
2023-04-04 15:46 Randy Armstrong Status resolved => assigned
2023-04-04 15:47 Randy Armstrong Status assigned => resolved
2023-04-04 15:47 Randy Armstrong Resolution fixed => no change required
2023-04-04 15:47 Randy Armstrong Note Added: 0019091
2023-04-04 15:47 Jim Luth Status resolved => closed
2023-04-04 15:47 Jim Luth Note Added: 0019092