Summary

The CSOT spec doesn't currently specify that timeoutMS should be an option for each method on the ClientEncryption object.  After talking with shane.harvey@mongodb.com , we decided it makes sense for these methods to accept a timeoutMS option, like other driver helper methods.

Motivation

Who is the affected end user?

Client Encryption users.

How does this affect the end user?

Users are unable to specify timeoutMS per-operation for operations on the ClientEncryption.

How likely is it that this problem or use case will occur?

Main path? Edge case?

If the problem does occur, what are the consequences and how severe are they?

Minor annoyance - users can configure a new ClientEncryption with timeoutMS for the operation that they want to use CSOT if they want a different timeoutMS value for a single operation.  

Is this issue urgent?

no.

Is this ticket required by a downstream team?

no.

Is this ticket only for tests?

no.

Acceptance Criteria

What specific requirements must be met to consider the design phase complete?