Re: [Add] Food for thought?

[tirumal reddy <[e-mail]>]

On Wed, 22 Jan 2020 at 19:53, Ted Lemon <[e-mail]> wrote:

> On Jan 22, 2020, at 8:50 AM, Mohit Sethi M <
> mohit.m.sethi=[e-mail]> wrote:
>
> Rather than distinguishing between private/local networks vs. Internet, it
> could distinguish home/enterprise networks or whether infrastructure is
> available to aid the discovery or not. For example, some enterprise
> networks may have servers (such as a Windows Active Directory Domain
> Service) to help assist in the discovery of DNS resolvers. This would not
> be possible in many home networks on the other hand.
>
>
> Practically speaking, it might help to think of this in terms of scenarios
> rather than types of networks.   It’s true e.g. that a corporate network
> may have WADDS, but it may also not.  What matters is whether it has it,
> not whether it is a corporate network.   It might help with clarity if we
> think about it this way, although I agree with your basic point.
>
> And then what is it about WADDS that makes it able to help the client to
> find a secure resolver, as compared to unauthenticated DHCP?
>

Policies can be configured on both the OS and browsers in the endpoint via
Active directory, Discovery of DoH/DoT servers is not required. For
instance, see
https://support.mozilla.org/en-US/kb/customizing-firefox-using-group-policy-windows,
the policy can specify the Enterprise DoT/DoH server the browser should use.

The challenge is with BYOD devices or Enterprise networks that have
limited/no configuration control on endpoints.

Cheers,
-Tiru


> Is it a property that is unique to WADDS, or is WADDS implementing an
> example of some property that other services might also be able to
> implement?
>
> --
> Add mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/add
>