Re: [Add] Proposed charter and BoF request for IETF 106

[Eric Rescorla <[e-mail]>]

On Wed, Oct 9, 2019 at 9:56 AM Vittorio Bertola <
[e-mail]> wrote:

>
> Il 9 ottobre 2019 13:58 Eric Rescorla <[e-mail]> ha scritto:
>
> > Achieving these
> > objectives while providing confidentiality and tamper-resistance will
> > generally require that network operators shift to one of the available
> > encrypted transports for their resolvers and that clients include
> > configuration options to select them.
>
> This entirely misses the point, which isn't just to do a lot of encryption
> but to provide security for the user. Just having network operators
> transition to secure transports while continuing their current practices
> does not address the issue.
>
> Sorry, now it is my turn to dot the i's: certainly *some* network
> operators in your country adopt *some* current practices that Mozilla do
> not like, and neither do I. But you cannot generalize this like that, and
> then use it as a reason not to enable the other network operators to shift
> to encrypted transport while continuing their practices exactly like they
> are, for the full satisfaction of their existing users.
>
> And by the way, making judgements on whether the commercial practices of a
> given company are acceptable really looks like a policy issue.
>

You're misunderstanding me. I'm not saying that we should not enable
network operators to shift to encrypted transport. As I said in the section
of my message that you cut, I'm more than happy to have the IETF
standardize a mechanism for the network to tell endpoints that it supports
encrypted transport. I'm merely observing that this does not address the
issue that Mozilla is trying to address with our DoH/TRR deployment.

-Ekr


> --
>
> Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
> [e-mail]
> Office @ Via Treviso 12, 10144 Torino, Italy
>
>