Mark,
LCUP does not describe any specific behavior for continuation references. The document only states that "the server returns a set of SearchResultEntries that fits the client's specification.". No mention of SearchResultReferences.
Was this the intent of the authors?
Assuming that for a search operation, the server would normally return continuation references, what is supposed to happen when the same search request contains a clientUpdate control that indicates the client's intent to initiate a synchronization session?
What is supposed to happen when the server acquires knowledge of a subordinated naming context on a different server, while synchronizing a client? What should happen in the opposite case: when knowledge of a subordinates naming context is removed from the server? etc.
Should the ManageDsaIT control be used when the client has interest in the knowledge information and its evolution? ...quite limiting, this sounds more like a work-around than a solution.
Thanks,
Mircea.