I’ll add my 200%

Instead let’s move to make QUIC a first class transport method to end any transport size issues.

This is also why I felt we shouldn’t dictate how to do PQ based on anything size related and why we shouldn’t further hack the dns with proposals for custom protocol modifications to support PQ.

Just fix the transport packet size issues. DNS servers can keep a little state these days to deal with streams.

Paul

On Oct 31, 2026, at 08:32, Ted Lemon <[email protected]> wrote:


200% agree.

As for the DO bit, it should always be set, because we should always be validating. Asking people not to set it if they aren't validating is planning for failure. No. 

On Fri, Oct 30, 2026, at 11:51 PM, Joe Abley wrote:
Hi Warren,

On 30 Oct 2026, at 23:33, Warren Kumari <[email protected]> wrote:
This draft updates[0] RFC4034 - "Resource Records for the DNS Security Extensions" to recommend that recursive resolvers only set the DO bit if they, or their clients, are validating.  This does mean that the resolver will need to track how the data entered it's cache, and will have to additional queries if an incoming query with DO arrives for an cache entry which was populated without DNSSEC info. This trades complexity and additional queries for less TCP fallback. 

My opinion is that the DNS needs less UDP, not more of it. I am not in favour of band-aids that prolong the tolerance of transport protocols that constrain response sizes.

I think we should be doing everything we can to move the mainstream to (ideally encrypted) stream-based transport protocols which have no response size constraints beyond those of the DNS message format, transport protocols that have no need for protocol modifications of the kind you describe above.

The future of UDP transport should be best-effort support for legacy devices.


Joe

_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to