Skip to content
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

Whether there are plans to support FEC or mutipath #568

Open
nilins opened this issue Feb 4, 2024 · 3 comments
Open

Whether there are plans to support FEC or mutipath #568

nilins opened this issue Feb 4, 2024 · 3 comments

Comments

@nilins
Copy link

nilins commented Feb 4, 2024

best wish
Whether there are plans to support FEC or mutipath

@kazuho
Copy link
Member

kazuho commented Feb 4, 2024

We have an open PR that implements the draft version of multipath: #559.

Adoption of both features depend on how the standardization goes.

@nilins
Copy link
Author

nilins commented Feb 6, 2024

We have an open PR that implements the draft version of multipath: #559.

Adoption of both features depend on how the standardization goes.


thanks for your reply。

quickly is support quic v1。

but as follow RFC, which is support ? which is not support?
RFC 9221 An Unreliable Datagram Extension to QUIC
RFC 9204 QPACK: Field Compression for HTTP/3
RFC 9114 HTTP/3
RFC 9368Compatible Version Negotiation for QUIC
RFC 9369 QUIC Version 2
RFC 9308 Applicability of the QUIC Transport Protocol
RFC 9312 Manageability of the QUIC Transport Protocol
RFC 9287 Greasing the QUIC Bit

@kazuho
Copy link
Member

kazuho commented Feb 6, 2024

  • 9221 is supported by quicly.
  • 9204 and 9114 is not QUIC but rather HTTP/3, they are supported by h2o, not quicly.
  • 9368, 9369, 9287 are not supported.
  • 9308 and 9312 are not protocol definitions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants