Re: [dnsoverhttp] Configured as trustworthy

as with most things https, the protocol doesn't try to define a policy for
the client - though I think this could still use a little more
non-normative exploration of the possibilities..

the existing text just asks you to consider the scope of authority for the
server when considering poisoning attacks. (so a dns api server configured
for the role of recursive resolver is basically configured as trustworthy
for everything, but other roles have lesser scope..)

On Fri, Jun 16, 2017 at 5:40 PM, Göran Eriksson AP <
goran.ap.eriksson@ericsson.com> wrote:

> Hi,
>
> Minor question on draft-hoffman-dns-over-https-01:
>
> Section 9 states:
>
>  Instead, a client MUST only trust DNS API server that is configured as
> trustworthy.
>
> Perhaps obvious to many but may I ask for a more precise definition of
> what is meant by “configured as trustworthy”?
>
> Best Regards
> Göran
>
> _______________________________________________
> dnsoverhttp mailing list
> dnsoverhttp@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsoverhttp
>
>