from the errata related to retransmission queue updates:
"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."

also the following was added
"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."

The specification has been updated via errata back to 1.03, but new conformance units / profiles have not been created.

The CTT should look for the behavior described and handle it correctly (in 1.05). This behavior is only an option for certain profiles (which should limit what test cases are run) - In general since it can be omitted from support, we need to restructure what is tested in what conformance Units - for release 1.05