I am dealing with some proprietary software that will happily connect and search lldap for users, as part of a user import, but fails the entire import because it assumes search results are always pageable, and is unable to locate the Paged Results Control in the response.

In my case, the software will happily accept any number of results, so a search response containing all results, and a Paged Results Control indicating no futher results available, would satisfy the implementation and allow the import to go through. I could imagine this to be a common usage pattern.

So, I'd like to propose we extend the search result response with a control list containing the Paged Results Control, with a zero length "cookie" indicating no further results.