} finally {
        monitor.leave();
      }
    } else {
      // It is possible due to races that we are currently in the expected state even though we
      // timed out. e.g. if we weren't event able to grab the lock within the timeout we would never
      // even check the guard. I don't think we care too much about this use case but it could lead
      // to a confusing error message.

      } finally {
        monitor.leave();
      }
    } else {
      // It is possible due to races that we are currently in the expected state even though we
      // timed out. e.g. if we weren't event able to grab the lock within the timeout we would never
      // even check the guard. I don't think we care too much about this use case but it could lead
      // to a confusing error message.

- **Phases 1-2**: 2-3 months (High priority)
- **Phases 3-4**: 2 months (Medium priority)
- **Phases 5-6**: 2-3 months (Low priority)

### Infrastructure
- Windows Server test lab
- RDMA-capable test hardware
- Continuous integration environment
- Performance testing infrastructure

## Success Metrics

1. **Functional Completeness**: All features pass Windows Protocol Test Suite

          if (protocolNegotiationEnabled) {
            Platform.get().configureTlsExtensions(sslSocket, null, protocols)
          }

          sslSocket.startHandshake()

          // Wait until after handshake to grab the buffered socket
          socket = MockWebServerSocket(sslSocket)

          if (protocolNegotiationEnabled) {
            val protocolString = Platform.get().getSelectedProtocol(sslSocket)
            protocol =