Re: [Add] What to do in this potential working group

Eric Rescorla <ekr@rtfm.com> Wed, 21 August 2019 17:15 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CC2A120BFE for <add@ietfa.amsl.com>; Wed, 21 Aug 2019 10:15:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-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 61Gv534Dz4uU for <add@ietfa.amsl.com>; Wed, 21 Aug 2019 10:15:36 -0700 (PDT)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (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 8DBFE1201DC for <add@ietf.org>; Wed, 21 Aug 2019 10:15:35 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id h15so2846599ljg.10 for <add@ietf.org>; Wed, 21 Aug 2019 10:15:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9/NeqI6tpbl66gNdIykKM6B7FgM7mGqbwuCGYWe+cYs=; b=2Fwirh2jb005Mx/BFMudUknNNrts8XWFgG6Fja/MVIO+j+4ZvDdoKwpZEBcD2DBRtG /eQCZznDklPKPyqJzVa071eBxgg2Q86xThI+AunjzXV9+ZBWtpLIiFq8rl08B4as1C4h 1h9Rfo3gPTedmz1ypMPw1+b3tsVfSyNqivEaEyZ9iOyXx1L9Tl1+8wQoqWrS1J2SviFY jTBu12lD05GvmEPoQ/J+BuoG8A6ln9sJassuMdW/GP17DWRbn4/i7zFPKKopkrJwuWKm T9r1cfWLeU/5D+rCTjr0ZMAiK77OBopJZiwTvc0usrqpvFEY8jKhF4VAhHOFcZEfM/Gi o8rw==
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=9/NeqI6tpbl66gNdIykKM6B7FgM7mGqbwuCGYWe+cYs=; b=WbL1T3C2l0QkI3ITY9VcI+MhZ7dAewjZfHZb1ELsnv0aSxqVo5O43XE3bSXC2oiJyE sjRjBJLGpA8rwbMONgar7NmyegFfKWu2Qelb8GHY02WZ7fnTDdYVez1hmpCFZzgJ+kEO BzF7Vy+Ed8iUiO9qHLT8ZaZhLqm6qd/BLBCE0RnPwINp5Zsw3k33D73iE1v/Te17kmrt hDoFQtFyj6GFJ9KHiaJ2DtYsj3s28O3hcLYun3gECCTgN5h3L1wD/goHle1+SA1t0V29 7gpdn/hfUiwEJBLCBQsgeM06porQmCGMA2+zfJQSIkwFY3buHfvOgbWHQSW6+nP3vuI/ Yx6Q==
X-Gm-Message-State: APjAAAU95mv1wL1ZwWrc8RTkLTpCs7q/oD5Af8u7p4i1x9SOgTps5BLV jAfrEAsjKfLJm/uGteKUjPD5ojQrehD8t93Jx3DCSg==
X-Google-Smtp-Source: APXvYqwC5F9UjyX2PijBFcs2O1/aUurHXowzwicvNikIU+DJ7mHwEyNNb7I2cNFpy2H/J0kpZpbMNHDu38Ptr37tItQ=
X-Received: by 2002:a2e:5c43:: with SMTP id q64mr6661902ljb.14.1566407733764; Wed, 21 Aug 2019 10:15:33 -0700 (PDT)
MIME-Version: 1.0
References: <A1128702-1E19-4657-9740-E84AE09992F2@piuha.net> <CABcZeBMfOTjq-8hDDoKMtJvfHUA5nC8o60zuk-2Xe-ZhfwriJQ@mail.gmail.com> <766112E1-F532-4C6B-8CA8-A096671E02EE@piuha.net> <CABcZeBO1nqtSOn8hmcC58Ys5rC9=fXLPQhWStgWL0oSfMQ072g@mail.gmail.com> <a250ce7e-db59-8b74-3ac7-9c5d751b1cb8@bellis.me.uk> <CABcZeBMmAqsRwA1YwdzCyRT_tNzkHEDe3u916c7KhWWBeKqPkg@mail.gmail.com> <b48d7314-e931-1543-30bc-0b2602f1daab@bellis.me.uk>
In-Reply-To: <b48d7314-e931-1543-30bc-0b2602f1daab@bellis.me.uk>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 21 Aug 2019 18:14:57 +0100
Message-ID: <CABcZeBOMPreon+Tn8BUB0DZF-sAg8ijH-vFFf7kjSg1MhZH+Eg@mail.gmail.com>
To: Ray Bellis <ray@bellis.me.uk>
Cc: ADD Mailing list <add@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008b767e0590a3b8f6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/J9k4V0tzL8cDfRJbAXYFrzcuF10>
Subject: Re: [Add] What to do in this potential working group
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2019 17:15:38 -0000

On Wed, Aug 21, 2019 at 6:05 PM Ray Bellis <ray@bellis.me.uk> wrote:

>
>
> On 21/08/2019 18:01, Eric Rescorla wrote:
>
> > Indeed: this is what I was referring to when I said "ways to minimize
> > centralization". Specifically, ISPs could commit to strong privacy
> > policies and join our TRR program.
>
> Or Mozilla could embrace DNSSEC and DoT thereby encouraging their
> deployment for the benefit of all internet users...
>

I feel like everything meaningful to be said about DNSSEC has already been
said, so I'll spare people that.

The issue isn't DoH versus DoT. but rather having a connection with an
authenticated resolver with defined privacy policies. DoT (or for that
matter DoH) to an arbitrary network-provided resolver doesn't provide that.

Ekr


> Ray
>
>