As author of RFC 7901, I see no issues with embedding dns chains that can be dnssec validated. Anything without validation is just too vulnerable to attacks.

But I also don’t believe the won time would actually go to the user - they would go to the advertiser auction times to get the highest bid for the ad served on the web content.

So I am unsure if this engineering effort is worth it.

Paul 


On Oct 30, 2026, at 19:17, Warren Kumari <[email protected]> wrote:


Dear DISPATCH, DNSOP & HTTPBIS[0],

Joe and I would really appreciate your review and feedback on this draft: draft-wobbly-dispatch-embedded-answers - "DNS Embedded Answers"

This idea is strong influenced by the "Resolverless DNS" discussions from 2018. 

We believe that the general concept deserves more discussion, and so we have written it up as a draft. 
Please keep an open mind - the emotions ran somewhat strong during the initial Resoverless DNS discussions. This is written up in the original spirit of request for comment - we'd like feedback and discussion on the idea and concept, as well as on the document itself. It clearly needs more work, but we'd like to either understand how to make this work, or why it won't. 

I have done some initial performance testing - depending on the network environment, resolver, phase of the moon, etc it seems that on average DNS is taking up between 0.5 - 6% of my browsing time (time from initial connection until Largest Contentful Paint (LCP)). 

We believe that it would be great for the user experience if we can reduce that, providing it can be done in a privacy (and security) protecting manner.

Please help us understand if we can do this, or if this is a bad idea,
Warren and Joe.

[0]: Sent to all three list desperately to cut down on cross-posting.

_______________________________________________
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