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 0-RTT in DNS over QUIC #1716

Merged
merged 1 commit into from
Jun 4, 2022
Merged

Conversation

msoxzw
Copy link
Contributor

@msoxzw msoxzw commented Jun 4, 2022

Quote from RFC 9250

Using 0-RTT for DoQ has many compelling advantages. Clients can
establish connections and send queries without incurring a connection
delay. Servers can thus negotiate low values of the connection
timers, which reduces the total number of connections that they need
to manage. They can do that because the clients that use 0-RTT will
not incur latency penalties if new connections are required for a
query.

In addition, DoQ server may send Retry Packets to use the Address Validation, and send NEW_TOKEN frames to clients after the client address is validated in order to avoid the 1-RTT penalty during subsequent connections by the client from the same address. However, unfortunately, quinn, the QUIC implementation in trust-dns, has not yet supported the NEW_TOKEN mechanism.

Copy link
Member

@bluejekyll bluejekyll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this PR, looks good.

@bluejekyll bluejekyll merged commit 170e3f7 into hickory-dns:main Jun 4, 2022
@msoxzw msoxzw deleted the 0-RTT-DoQ branch June 9, 2022 19:59
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 this pull request may close these issues.

None yet

2 participants