Section 5.12.2.1 says the following in terms of CreateMonitoredItems validation:

"When a user adds a monitored item that the user is denied read access to, the add operation for the item shall succeed and the bad status Bad_NotReadable or Bad_UserAccessDenied shall be returned in the Publish response. This is the same behaviour for the case where the access rights are changed after the call to CreateMonitoredItems. If the access rights change to read rights, the Server shall start sending data for the MonitoredItem. The same procedure shall be applied for an IndexRange that does not deliver data for the current value but could deliver data in the future."

We have a test-case/script that uses IndexRange to test the above. Basically, the test specifies an index range that is out of range of what the node is currently defined (e.g. array size is 5, but index range = "99").

The question is this: if the array dimensions are fixed then they cannot change, in that case should a server be allowed to reject the item and return an error code (BadIndexRangeNoData etc.) as part of the response?

If the answer is yes, then the follow-on question will be if this will be a requirement that all servers behave this way (responsing to CreateMonitoredItems) or if its permissable for server to accept the request but respond with the same error code in the Publish response.