nibanks

6 ms·

1. 1.▲
   by nibanks 6y ago

   Not yet. BBR is on the TODO list though.
2. 2.▲
   by nibanks 6y ago

   Not likely, unless we get a customer ask for it. But when we start accepting external contributions it shouldn't be too hard for someone else to add the support. We already (unofficially) support 3 different TLS libraries (schannel, op
3. 3.▲
   by nibanks 6y ago

   Just to pile on here, running in kernel mode was the primary reason for using C. Windows kernel does support some limited set of C++ features, but we decided to go with pure C instead because of the confusion of which C++ features were avai
4. 4.▲
   by nibanks 6y ago

   We do work with the Everest team. We have unofficial support on top of miTLS (which they produce). We haven't looked into actually using F* for any of the QUIC code though.
5. 5.▲
   by nibanks 6y ago

   It's definitely on the TODO list. We're looking into it.
6. 6.▲
   by nibanks 6y ago

   Yes, msquic should be a good general purpose transport. We already have usage from SMB (file sharing) and HTTP in Windows. Both are very different and provided good test cases for msquic.