0006236: Subscription publish Min 02 - retransmission queue - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0006236	NodeSets, XSDs and Generated Code	Api Change	public	2020-11-10 16:49	2021-02-23 17:46

Reporter	Jim Luth	Assigned To	Randy Armstrong
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	fixed

Summary	0006236: Subscription publish Min 02 - retransmission queue
Description	States that support for a retransmission queue is not required, but this statement does not provided enough details on how the server should function with regard to acknowledgement of sequence numbers. This cause interoperability issue with regards to clients that send an ack for the received sequence number. The specification say to return an error is the sequencenumber is not in the list. This conformance unit should either: 1) not allow a 0 size, but at least have a size of 1 (i.e. the message that just went out (which will allow clients to ack it) [preferred] 2) add text about behavior with regard to client ack of the sequence number - i.e. all number passed if no queue is present are always just accepted (no Bad_SequenceNumberUnknown is returned - just a good) - review all other specification section since multiple other location in the spec describe that a retransmission queue is required and describe behavior related to it. - this may require updates more updates in other parts also.
Tags	No tags attached.

Commit Version
Fix Due Date

Jim Luth 2020-11-10 16:49 administrator ~0013150	Add return code: Good-RetransmissionQueueNotSupported to be returned in the Publish. Possibly add a ServerCapabilities to indicate support for Retransmission (Part 5).

Matthias Damm 2020-11-10 16:49 reporter ~0013151	5.13 Subscription Service Set 5.13.1.1 Description Replace i) with the following text: Sessions maintain a retransmission queue of sent NotificationMessages. NotificationMessages are retained in this queue until they are acknowledged. The Session shall maintain a retransmission queue size of at least two times the number of Publish requests per Session the Server supports. A Profile in OPC 10000-7 may make the retransmission queue support optional. The minimum number of Publish requests per Session the Server shall support is defined in OPC 10000-7. Clients are required to acknowledge NotificationMessages as they are received if the Publish response parameter availableSquenceNumber is not an empty array. An empty array in availableSquenceNumber indicates that the Server does not support a retransmission queue and acknowledgemet of NotificationMessages. In the case of a retransmission queue overflow, the oldest sent NotificationMessage gets deleted. If a Subscription is transferred to another Session, the queued NotificationMessages for this Subscription are moved from the old to the new Session. 5.13.5 Publish Table 95 – Publish Service Parameters Replace availableSequenceNumbers description with the following text: A list of sequence number ranges that identify unacknowledged NotificationMessages that are available for retransmission from the Subscription’s retransmission queue including the sequence number of this response if it is not a keep-alive Message. This list is prepared after processing the acknowledgements in the request (see 7.8 for Counter definition). The list shall be empty if the Server does not support the retransmission queue. If the list is empty, the Client should not acknowledge sequence numbers. Table 97 – Publish Operation Level Result Codes Add status code to table Good_RetransmissionQueueNotSupported The Server does not support retransmission queue and acknowledgement of sequence numbers is not available. Updated in OPC 10000-4 - UA Specification Part 4 - Services 1.05.0 Draft11.docx Errata is prepared

Jim Luth 2020-11-10 16:49 administrator ~0013152	Add new error code .

Randy Armstrong 2020-11-16 07:38 administrator ~0013226	Added to UA-1.05-2020-11-20.

Jim Luth 2021-02-23 17:46 administrator ~0013786	agreed to changes in telecon.

Date Modified	Username	Field	Change
2020-11-10 16:49	Jim Luth	New Issue
2020-11-10 16:49	Jim Luth	Status	new => assigned
2020-11-10 16:49	Jim Luth	Assigned To	=> Randy Armstrong
2020-11-10 16:49	Jim Luth	Issue generated from: 0006033
2020-11-10 16:49	Jim Luth	Note Added: 0013150
2020-11-10 16:49	Jim Luth	Note Added: 0013151
2020-11-10 16:49	Jim Luth	Note Added: 0013152
2020-11-10 16:49	Jim Luth	Relationship added	related to 0006033
2020-11-16 07:38	Randy Armstrong	Status	assigned => resolved
2020-11-16 07:38	Randy Armstrong	Resolution	open => fixed
2020-11-16 07:38	Randy Armstrong	Note Added: 0013226
2021-02-23 17:46	Jim Luth	Status	resolved => closed
2021-02-23 17:46	Jim Luth	Fixed in Version	=> 1.05
2021-02-23 17:46	Jim Luth	Note Added: 0013786