View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001449 | 10000-004: Services | public | 2010-12-16 18:46 | 2019-02-20 17:29 | |
Reporter | Assigned To | Matthias Damm | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 1.01 | ||||
Fixed in Version | 1.02 | ||||
Summary | 0001449: RequestHeader.Timestamp (utcTime) - Clarification needed | ||||
Description | According to Table 157, the Timestamp parameter is described as: But what is the TRUE purpose of this parameter? Should the Server use this information to determine how old/stale a request is from a Client? (likewise when a Client receives a response from a Server) Even if time-synchronization is not in place and a Client sent a date that was 1-year old, what should the Server do? Should the Server care about this parameter? if not, then do we need this parameter? Obviously some clarification is needed, some thoughts: 1.) Server can be configured with a user-definable setting to determine the age of a request (based on this parameter) that should be allowed. Messages with a timestamp outside of this tolerance are rejected. 2.) Server merely uses the setting as part of diagnostics capturing/logging, i.e. the Client issued the call at {client time} which was received at {server time} etc. 3.) Specify that the parameter is optional, but when implemented it should do... and when not implemented then... | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
related to | 0004616 | closed | Paul Hunkar | View Services/View Minimum Continuation Point 01/Err-010.js |
|
Telco March 7, 2011 Add clarification that the parameter is only used for diagnostics (2) |
|
Added clarification in Table 157 that the parameter is only used for diagnostic purposes in the server. Change is part of the draft version "OPC UA Part 4 - Services Draft 1.02.02 Body.doc" |
|
Closed in Walldorf |
Date Modified | Username | Field | Change |
---|---|---|---|
2010-12-16 18:46 |
|
New Issue | |
2011-02-14 06:21 | Randy Armstrong | Status | new => assigned |
2011-02-14 06:21 | Randy Armstrong | Assigned To | => Matthias Damm |
2011-03-07 18:39 | Matthias Damm | Note Added: 0002343 | |
2011-03-12 12:58 | Matthias Damm | Status | assigned => resolved |
2011-03-12 12:58 | Matthias Damm | Resolution | open => fixed |
2011-03-12 12:58 | Matthias Damm | Note Added: 0002372 | |
2011-05-23 17:04 | Randy Armstrong | Status | resolved => closed |
2011-05-23 17:04 | Randy Armstrong | Note Added: 0002748 | |
2012-02-09 22:39 | Jim Luth | Fixed in Version | => 1.02 |
2019-02-20 17:29 | Matthias Damm | Relationship added | related to 0004616 |