The context of this issue is the Browse service call, but should apply to all that have the concept of a continuationpoint.

The https://reference.opcfoundation.org/Core/docs/Part5/6.3.2/ does say a value of 0 means unlimited number of continuationpoints are supported. It is possible to do an implementation (and such implementations exists already) that doesn't allocate any memory on the server for the continuationpoint (e.g. the returned ByteString for the continuationpoint could contain all the info required for continuing the operation etc.) and those implementations truly support an infinite number of continuationpoints.

However if such implementation was not used (meaning server must use memory to hold the continuationpoint), then the server shouldn't support infinite number of them, since otherwise it can run out of memory if clients never continue the Browse operation. Thus I would recommend adding a sentense to 6.3.2 that only if no resources are allocated by the server for a continuation point using the "limit" of 0 would be allowed. This might be testable for CTT/Lab (alloc 100k+ continuationpoints via crafted Browse calls to always result in a point and see if server's memory consumption didn't increase) as well.