View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000611610000-004: ServicesSpecpublic2020-10-02 15:532021-03-02 16:54
ReporterPaul Hunkar Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Summary0006116: Client behavior for available sequence number > current Sequence number
Description

What should a client do if the list of available sequence number is greater than the current sequence number . I.e. I receive seq 99, with a list of available seq number 99, 100, 101, 200 (so all of them are in the future)

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Jim Luth

2020-10-13 15:39

administrator   ~0013044

Describe required or acceptable behavior of a Client in this case.

Matthias Damm

2020-12-08 16:30

developer   ~0013402

Add a clarification that the list for diagnsotic purpose and client should log differences to the expected list.

Matthias Damm

2021-03-02 16:30

developer   ~0013890

Added following clarification:
This information is for diagnostic purpose and Clients should log differences to the expected sequence numbers.

Added in
OPC 10000-4 - UA Specification Part 4 - Services 1.05.0 Draft15.docx

Jim Luth

2021-03-02 16:54

administrator   ~0013892

Agreed to changes in Virtual F2F.

Issue History

Date Modified Username Field Change
2020-10-02 15:53 Paul Hunkar New Issue
2020-10-13 15:39 Jim Luth Note Added: 0013044
2020-10-13 15:39 Jim Luth Assigned To => Matthias Damm
2020-10-13 15:39 Jim Luth Status new => assigned
2020-12-08 16:30 Matthias Damm Note Added: 0013402
2021-03-02 16:30 Matthias Damm Status assigned => resolved
2021-03-02 16:30 Matthias Damm Resolution open => fixed
2021-03-02 16:30 Matthias Damm Note Added: 0013890
2021-03-02 16:54 Jim Luth Status resolved => closed
2021-03-02 16:54 Jim Luth Fixed in Version => 1.05
2021-03-02 16:54 Jim Luth Note Added: 0013892