There are more place then this one place that would have to be updated if the links become optional

The lack of exposing the PubSub configuration does make it difficult to diagnose issue - since the publish information is not available for Wireshark to determine which set of messages are associated with this connection. It could be possible to ensure that this information is saved in the CCS on the CM side, but this is also not mandated at this point in time.

this issue will require more thought and discussion - leaving it open for now

Discussed in call - this is a topic we need to have a larger group discussion on - scheduled in advance to ensure all can be present - topic: do we really want to make this change?

This is a limitation of an SDK - should it affect a specification? prior discussion was to point to a hidden node (not visible) - general thought is that we should not change what was decided before.

agree in call to add a variable that is a string array, with the path to the node that would the the equivalent to the writer - since the node do not have to be exposed. This path of object names can be used to look at the configuration in the FileObject for a PubSub Configuration, it could also be used to browse to the node is the configuration is exposed. when Client?server is added a similar path can be created for the session Object/Subscription object exposed in diagnostics.