[PR #1716] [MERGED] Support 0-RTT in DNS over QUIC #2540

New issue

Closed

opened 2026-03-16 10:07:01 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 10:07:01 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/hickory-dns/hickory-dns/pull/1716
Author: @msoxzw
Created: 6/4/2022
Status: ✅ Merged
Merged: 6/4/2022
Merged by: @bluejekyll

Base: main ← Head: 0-RTT-DoQ

📝 Commits (1)

27392f9 support 0-RTT in DoQ

📊 Changes

1 file changed (+9 additions, -1 deletions)

View changed files

📝 crates/proto/src/quic/quic_client_stream.rs (+9 -1)

📄 Description

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.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/hickory-dns/hickory-dns/pull/1716 **Author:** [@msoxzw](https://github.com/msoxzw) **Created:** 6/4/2022 **Status:** ✅ Merged **Merged:** 6/4/2022 **Merged by:** [@bluejekyll](https://github.com/bluejekyll) **Base:** `main` ← **Head:** `0-RTT-DoQ` --- ### 📝 Commits (1) - [`27392f9`](https://github.com/hickory-dns/hickory-dns/commit/27392f9d789f47ba12a249a7eea4a4f7e13ac443) support 0-RTT in DoQ ### 📊 Changes **1 file changed** (+9 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `crates/proto/src/quic/quic_client_stream.rs` (+9 -1) </details> ### 📄 Description Quote from [RFC 9250](https://datatracker.ietf.org/doc/rfc9250/) > 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](https://github.com/quinn-rs/quinn/blob/4395b969a69b9e39bef1333e44312bf2548d4e1c/quinn-proto/src/connection/mod.rs#L2544-L2553). --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>