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

support 62-bit error codes #601

Closed
kazuho opened this issue Jan 7, 2025 · 0 comments · Fixed by #602
Closed

support 62-bit error codes #601

kazuho opened this issue Jan 7, 2025 · 0 comments · Fixed by #602

Comments

@kazuho
Copy link
Member

kazuho commented Jan 7, 2025

The error code space of quicly is based on the old draft that used 16-bit values.

Specifically, errors are signaled using int, which is divide into:

range usage
0x000000?? picotls (TLS alerts from host)
0x000001?? picotls (TLS alerts from peer)
0x000002?? picotls (internal errors)
0x0000ff?? quicly internal error codes1
0x0002???? QUIC transport error codes
0x0003???? QUIC application error codes

We eventually need to switch to a scheme that supports full 62-bit range for QUIC transport and applications.

[1] Even though the value space is internal, some are used to signal transport errors. In such case, the values are converted to transport error codes upon emission.

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

Successfully merging a pull request may close this issue.

1 participant