{"id":9061,"date":"2016-07-20T17:13:21","date_gmt":"2016-07-20T15:13:21","guid":{"rendered":"https:\/\/daniel.haxx.se\/blog\/?p=9061"},"modified":"2016-07-20T17:13:21","modified_gmt":"2016-07-20T15:13:21","slug":"curl-wants-to-quic","status":"publish","type":"post","link":"https:\/\/daniel.haxx.se\/blog\/2016\/07\/20\/curl-wants-to-quic\/","title":{"rendered":"curl wants to QUIC"},"content":{"rendered":"

The interesting Google transfer protocol that is known as QUIC<\/a> is being passed through the IETF<\/a> grinding machines to hopefully end up with a proper “spec” that has been reviewed and agreed to by many peers and that will end up being a protocol that is thoroughly documented with a lot of protocol people’s consensus. Follow the IETF QUIC mailing list<\/a> for all the action.<\/p>\n

I’d like us to join the fun<\/h2>\n

Similarly to how we implemented HTTP\/2 support early on for curl<\/a>, I would like us to get “on the bandwagon” early for QUIC to be able to both aid the protocol development and serve as a testing tool for both the protocol and the server implementations but then also of course to get us a solid implementation for users who’d like a proper QUIC capable client for data transfers.<\/p>\n

implementations<\/h2>\n

The current version (made entirely by Google and not the output of the work they’re now doing on it within the IETF) of the QUIC protocol is already being widely used as Chrome speaks it with Google’s services in preference to HTTP\/2 and other protocol options. There exist only a few other implementations of QUIC outside of the official ones Google offers as open source. Caddy<\/a> offers a separate server implementation for example.<\/p>\n

the Google code base<\/h2>\n

For curl’s sake, it can’t use the Google code as a basis for a QUIC implementation since it is C++ and code used within the Chrome browser is really too entangled with the browser and its particular environment to become very good when converted into a library. There’s a libquic<\/a> project doing exactly this.<\/p>\n

for curl and others<\/h2>\n

The ideal way to implement QUIC for curl would be to create “nghttp2” alternative that does QUIC. An ngquic<\/em> if you will! A library that handles the low level protocol fiddling, the binary framing etc. Done that way, a QUIC library could be used by more projects who’d like QUIC support and all people who’d like to see this protocol supported in those tools and libraries could join in and make it happen. Such a library would need to be written in plain C and be suitably licensed for it to be really interesting for curl use.<\/p>\n

a needed QUIC library<\/h2>\n

I’m hoping my post here will inspire someone to get such a project going. I will not hesitate to join in and help it get somewhere! I haven’t started such a project myself because I think I already have enough projects on my plate so I fear I wouldn’t be a good leader or maintainer of a project like this. But of course, if nobody else will do it I will do it myself eventually. If I can think of a good name for it.<\/p>\n

some wishes for such a library<\/h2>\n