We are not sure anything needs to be added to Part 80. This may be too detailed for that part and it is more appropriate in Part 81. However the AWG should provide guidance on the problem overall. We need to understand what conditions would force the EstablishConnections to be broken up into multiple commands. We will follow these steps:
1) Review Part 80 to determine if ANY statement is appropriate.
2) Ask the prototyping WG if they can provide us with some estimate of the method sized. (Also ask Georg because he had early data on this)
3) Review all of the calling parameters that could cause the packet sized to be large. Ideally we would calculate the bare minimum size of the buffer that would be needed to send and receive an EstablishConnections method. (Part 3 describes the max size of BrowseName and BrowsePath. Part 6 describes the mapping to TCP. Part 14 describes the PubSub config structure.)
4) Reassign this issue to Part 81 with AWG guidance.

This issue is waiting for the resolution of issue 7469, 7470, 7471, since if any text updates are needed for this issue, they would likely be in updates that result from those issue (addition of bundled commands - as long as a sever supports individual commands an ConnectionManager does not need to worry about size, if it gets an error it would just try the commands in individual steps. The the configuration command, which is the only command that is not bounded, can be broken up into smaller steps).

Should include in CM write/discussion a reference to the base UA specification of MaxMessageSize and MaxByteString

Statements in Part81 allow repeating of commands (including SetConfigurationData), thus no need for addtional statements for C2C

For C2D some issues remain, propose to split off a new Mantis for covering those and set to ACK

Added an error code - Bad_ ConfigurationError The applied configuration data is inconsistent. to allow for a consistency check

review in call , agreed to changes and closed issue