Use Case

As a driver engineer
I want ensure that we have distinct control over the BSON settings that impact protocol BSON messages and user data BSON payloads
So that we have less type handling and clearer insight into command construction.

User Impact

• Hard to capture.

Dependencies

• Our BSON library

Unknowns

• How can we modify the BSON API to allow us to have this fine control?
• What's the best approach? seems like well known keys for determining payload from protocol is a good way

Acceptance Criteria

Implementation Requirements

• TBD
• Stub out type information for all the protocol messages we send, this will make it clearer where we need add flexibility to the BSON API to allow fine control over certain key parsing.

Testing Requirements

• TBD

Documentation Requirements

• This should have no user facing impact

Follow Up Requirements

• n/a