Moin! On 30 Oct 2026, at 16:16, Warren Kumari 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" > <https://datatracker.ietf.org/doc/draft-wobbly-dispatch-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. Ok. I only now read the document, but my concerns about it are the same as they were during the resolver less discussion back then, and are now more relevant with a more and more people see DNS as a security perimeter against attacks and privacy violations. The main threat to privacy are not resolvers be they public, at the ISP or in my home network (e.g as PI-hole). IMHO the main threat to privacy is the ad industry that wants to profit on your personal data and this would give them new very hard to defend against way to do this. The document sort of acknowledges that in the security and privacy considerations, however it talks about clients wich are browsers which most users have not control over in contrast to what is done with DNS So no, we should not do this. So long -Ralf ——- Ralf Weber _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
