PyKMIP emits a specific exception in its message handling loop when it believes that a socket fatal condition has occured. This exception is used to terminate the KMIP session. On Linux, it's able to pretty reliably detect a closed connection. On Windows, the socket stack emits an error like ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host. PyKMIP does not map this ConnectionResetError exception into its equivalent internal exception type.

We should perform this mapping, in order to get PyKMIP to gracefully respond to client hangups on all platforms, and not emit huge amounts of log messages on Windows.