On Thu, 18 Mar 2021, Neil Cook wrote:
I oppose adoption. For precisely the same reasons that Tomas lays out below,
I am also opposing adoption.
The issue is not that we need another transport protocol. We need a
better way to decouple the stub/client data from the resolver/auth
data. How the client reaches their resolver should not be relevant
to this problem. What is relevant is how resolver pooling can decouple
the stub from the auth server.
I would rather see a new method where caching resolvers can feed each
other in a pool in such a way as to give endusers their query privacy.
Additionally, those why require this can already use TOR, which is such
a transport mechanism that is not just specified as a DNS transport.
Paul
On 18 Mar 2021, at 12:02, Tomas Krizek <[email protected]> wrote:
I oppose adoption.
The draft introduces huge amount of additional complexity, both for
implementors and operators of DoH. This raises the bar for both smaller
vendors and operators, thus leading to more centralization.
Additionally, the problem it attempts to solve is not DoH-specific, or
even DNS-specific, yet it only provides a solution for DoH.
On 17/03/2021 14.00, Brian Haberman wrote:
All,
This starts a DPRIVE WG call for adoption for
draft-pauly-dprive-oblivious-doh
(https://datatracker.ietf.org/doc/draft-pauly-dprive-oblivious-doh/).
Please reply to the mailing list with your views (positive or negative)
on the WG adopting the document and your supporting arguments.
This call will end on March 31, 2021 at 11:59pm UTC.
Regards,
Brian & Tim
_______________________________________________
dns-privacy mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dns-privacy
--
Tomas Krizek
PGP: 4A8B A48C 2AED 933B D495 C509 A1FB A5F7 EF8C 4869
_______________________________________________
dns-privacy mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dns-privacy
_______________________________________________
dns-privacy mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dns-privacy
_______________________________________________
dns-privacy mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dns-privacy
