-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QUIC implementation #2379
Comments
A few interesting points: Fastify was the first framework for Node.js to support HTTP/2 and this was part of the initial idea of using our own custom I would recommend you to join the discussion in core and see if you could help in implementing some of it. cc @jasnell |
@mcollina Thank you so much for considering me. I would love to take this opportunity. Do let me know if you need any help |
@mcollina Node.js v15 (Current) supports QUIC. Ref: https://github.com/nodejs/node/releases/tag/v15.0.0 |
I'd be happy to review some (external) modules/plugins etc that can enable us to use QUIC/HTTP3 internally. There is no HTTP/3 in core, nor any binary of Node.js with Quic enabled.... because we need a patch on top of OpenSSL that they are not adding: https://www.openssl.org/blog/blog/2020/02/17/QUIC-and-OpenSSL/. |
@aggarwaldev ... The quic support in Node.js 15 is still under active development, is not yet officially supported, and still has a long way to go, not to mention the fact that it relies on an unofficial patch to openssl that is unsupported. I'm currently exploring a few options to move things forward, but, given that the Openssl omc has decided not to pick up official quic support until well after openssl 3.0 is out the door, it's going to take some time |
Suppose Node.js releases a final working quic with nothing experimental could fastify core benefit from Quic out of the box or will the api have to be exposed in a certain manner to benefit from it? |
Out of the box, no, there would need to be some work in fastify to enable it because it would be a different set of APIs. Once that internal work is done, however, for end users of fastify it should require nothing more than a configuration option. |
How is it looking as of today with QUIC? |
Same as 9 months ago. |
Are the any behind the scenes happenings now that Node.js 17 uses OpenSSL 3.0? https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V17.md#openssl-30 - seems this can move forward? Edit: It is moving forward! More info here: nodejs/node#38233 |
Awesome, hope fastify will be first to use quic. |
hows this going? |
We need to wait this: nodejs/node#44325 |
🚀 Feature Proposal
Implementation of QUIC
https://tools.ietf.org/html/draft-ietf-quic-transport-27RFC: https://datatracker.ietf.org/doc/rfc9000/
More related RFCs:
About QUIC:
https://blog.cloudflare.com/http3-the-past-present-and-future/This shall pave way for implementation of HTTP/3 since HTTP over QUIC is proposed to be called HTTP/3. QUIC will likely be used for transporting more than just HTTP.
Motivation
Nodejs recently merged QUIC initial implementation with master branch. Landed in nodejs/node master nodejs/quic#390-- Implementation was removed: quic: remove experimental quic nodejs/node#37067
QUIC shall be essential for implementation of HTTP/3 and node is working hard on this: QUIC support nodejs/node#23064One should read this discussion, it's really interesting
Misc
This turned out to be true. Checkout WebTransport: https://datatracker.ietf.org/doc/draft-ietf-webtrans-http3/
Example
N/A
The text was updated successfully, but these errors were encountered: