Re: [Doh] Request for the DOH WG to adopt draft-hoffman-resolver-associated-doh

Ted Lemon <mellon@fugue.com> Wed, 23 January 2019 18:52 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A36D1310C3 for <doh@ietfa.amsl.com>; Wed, 23 Jan 2019 10:52:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.042
X-Spam-Level:
X-Spam-Status: No, score=-2.042 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FBdO_QSWm1Cd for <doh@ietfa.amsl.com>; Wed, 23 Jan 2019 10:52:35 -0800 (PST)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D44913126A for <doh@ietf.org>; Wed, 23 Jan 2019 10:17:07 -0800 (PST)
Received: by mail-qt1-x82b.google.com with SMTP id n32so3434103qte.11 for <doh@ietf.org>; Wed, 23 Jan 2019 10:17:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BskkAHOVFas6sMq63wVavmT8+H1xd6RiVBXNU+lsnzE=; b=f7mIrWfvSuQl4su/XqsyHoKWsfg5qg0aFUx0kyS+GEgQTXJ1RXau8Y+yrZxrAo76Sd IGee4by90EJcAmg0dHcrNDMIKv5qefYzw1jdcctbt7+I0Wp2OIlDTs32GqtInZnipiOY vkmSC86KcVGXxwxplP0IJaBQgG1jYX+zc2fSrdM0HireGq88kmL1lcPVQjD48KUC0+df 3AtsOuXpy6ZSm1W+lnEHa7B05ZY5iqqoTUmO8NsVOtAg8l+J/F/ZOEkgdStyQmd7WSdS OWiLfliIU5oFrxN0RapgrCPmuBTtV4RVZvSc9A33R5VAzSVpGjROAycp8XNov3RFv/UJ yYFQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BskkAHOVFas6sMq63wVavmT8+H1xd6RiVBXNU+lsnzE=; b=TPXHqZv6zZ65SuTgEjG/aIh/+6nCgnERO/vNwzIrh/sO7c28/gSMow5bGG1w42lsE8 JcpDWBvj2h9LcsanwB8xTouOhGRXuUsr2E7cw14ZPU/jYplZiJkV4nEndzbHDbvPCDe4 k+DRsFBKWPM1WCre9vp2hgXasvkAFOZ6xXhzxPZ0CeSCp+SkelG+z2/h5nWnbkJO3zpu xQlHJaME5YrC5x3WDn7VLYl3LuGQmzxWXKdp8Mwr46l3HKlcI8uH2v27OEkEHUcbUSZA PoVZ57fubwhWeA81bp/TABWemoy94skh/DNLqntA+Ip865n4TbTsTWeCmPuhXD/e0HHt gZ2A==
X-Gm-Message-State: AJcUukcTKfuhnAvIVUbvVhar6KV6D7YXx5d1Bcgo9C+Y13ai/zG2mrKf dUISxQoAHXlwqC3MJDEFYe3+ByE0CkiyPDCon13LLvnn
X-Google-Smtp-Source: ALg8bN6l7Z7bJfrNNMJpH99Wu/fBHnnXksby4ffK9BK1xEyIhp4640AaTO4QyVtYQbJ2IdyLq/a3eqg5ocRkvlDDJAg=
X-Received: by 2002:a0c:d4a7:: with SMTP id u36mr2824005qvh.38.1548267426224; Wed, 23 Jan 2019 10:17:06 -0800 (PST)
MIME-Version: 1.0
References: <8999D6F3-600E-4F1A-903C-10F8CAA6E4F3@icann.org> <alpine.DEB.2.20.1901230812390.17402@tvnag.unkk.fr> <2112742428.56808.1548254385497@appsuite.open-xchange.com>
In-Reply-To: <2112742428.56808.1548254385497@appsuite.open-xchange.com>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 23 Jan 2019 13:16:30 -0500
Message-ID: <CAPt1N1kimeJKkd=t18hH6PsbcO=OC69ULYGgE+T0Br+xbX+vwg@mail.gmail.com>
To: Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>
Cc: Daniel Stenberg <daniel@haxx.se>, DoH WG <doh@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f531e705802419b1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/rjtxoFuPk0rfWnnKaBTetLjQQp8>
Subject: Re: [Doh] Request for the DOH WG to adopt draft-hoffman-resolver-associated-doh
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2019 18:52:43 -0000

Okay, but for that use case, why not DoT rather than DoH?   What's the
advantage of DoH in this use case?

On Wed, Jan 23, 2019 at 9:39 AM Vittorio Bertola <vittorio.bertola=
40open-xchange.com@dmarc.ietf.org> wrote:

> > Il 23 gennaio 2019 alle 8.25 Daniel Stenberg <daniel@haxx.se> ha
> scritto:
> >
> > For me, one of the key elements and features with DoH is that I as a
> user have
> > picked a DNS provider I decide to trust. Be it a global CDN provider or
> my own
> > cloud instance. Any other way, with the ISP or my local network admins
> telling
> > me what server to use, is a major setback in my view.
>
> This could be true for you and me, but average users have no idea of what
> the DNS is - they only make one choice, they pick an *ISP* that they decide
> to trust. They pay to get "Internet access" from that company and expect
> that company to provide all it takes for "the Internet to work", including
> DNS resolution, without them having to do anything; this has been the
> default situation for the last 20 years at least.
>
> So it's fine if smarter users make changes to this default and pick a DNS
> provider different from their connectivity provider, and it's fine to
> empower them to do so, but it's not fine to break the way the Internet
> normally works for most people, which includes an automated and effortless
> mechanism to get the DNS resolution service from the ISP when connecting to
> the network.
>
> Regards,
> --
>
> Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
> vittorio.bertola@open-xchange.com
> Office @ Via Treviso 12, 10144 Torino, Italy
>
> _______________________________________________
> Doh mailing list
> Doh@ietf.org
> https://www.ietf.org/mailman/listinfo/doh
>