check to make sure it is clear enough - that pubSub configuration is just applied.

Behaviour is stated as follows:

Section 6.7.4.3.1 - end of the section:

The ConnectionManager shall ensure the expected result of the requested Action as follows:
• Calling ProcessConnectionConfigurationSets with Action set to ActionEstablishConnectionsEnabled shall establish all logical connections contained in the ConnectionConfigurationSets with a disabled communication model in the SetCommunicationConfigurationCmd and the ConnectionManager shall include EnableCommunicationCmd in the command sequence to enable the communication.
• Calling ProcessConnectionConfigurationSets with Action set to ActionEstablishConnectionsDisabled shall establish all logical connections contained in the ConnectionConfigurationSets with a disabled communication model in the SetCommunicationConfigurationCmd and the ConnectionManager shall omit EnableCommunicationCmd from the command sequence.
• Calling ProcessConnectionConfigurationSets with Action set to ActionEstablishConnections shall establish all logical connections contained in the ConnectionConfigurationSets with the communication model in its initial state. The ConnectionManager shall omit EnableCommunicationCmd from the command sequence. Depending on the initial state of the configuration elements, parts of the communication model may be enabled. This allows, for example, to have a subset of the connections enabled and the rest disabled.

and section 6.2.4.3.9.2 second paragraph

The EstablishConnections implementation shall add the supplied PubSubConfiguration to PubSub as described in OPC 10000-14. If an error is returned, the EstablishConnections implementation shall abort processing as described in 6.2.4.3.11. The SetCommunicationConfigurationCmd will apply the PubSubConfiguration, including the values of all Enabled flags for the configuration elements. This may result in enabled PubSub communication without passing the EnableCommunicationCmd.

We could add in both places, that a mixed behaviour could result, when a bidirectional connection is only partially enabled. Leave that to a decision in the team

Suggest several clarifications to Part 81.

6.7.4.3.1:

• for the ActionEstablishedConnectionsEnabled/Disabled, explicitly state that the "Enabled" variables in the communications config shall bet set to enabled/disabled.
• for the ActionEstablishConnections, rather than "communications model in its initial state", state that the value of the Enabled flags in the communications config shall be as configured by the configuration tool. And then note that it is the responsibility of the tool to properly and consistently configure the values of the Enabled variables

6.2.4.3.9.2:

• to the last sentence, also add that this "may result in some parts of the PubSub comminications with Enabled variables being set to enabled and others being set to disabled" (or something like that). And then further note that it is the responsibility of the configuration tools to properly configure the Enabled variables.

Added clarifications as proposed to 6.7.4.3.1 and 6.2.4.3.9.2.

Additional clarification in CloseConnection needed

Added clarifications to 6.7.4.3.1 (ConnectionManager), 6.2.4.3.9.2 (SetCommunicationConfigurationCmd) and 6.2.5.2 (CloseConnections)

Reviewed changes, agreed to updates in call and closed issue