IETF Logo Mail Archive

Re: [Add] meeting hum: should the IETF take up this work?

Rob Sayre <sayrer@gmail.com> Wed, 31 July 2019 07:56 UTC

Return-Path: <sayrer@gmail.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 806D91200C3 for <add@ietfa.amsl.com>; Wed, 31 Jul 2019 00:56:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 zh5b-ylZKkc2 for <add@ietfa.amsl.com>; Wed, 31 Jul 2019 00:56:40 -0700 (PDT)
Received: from mail-io1-xd43.google.com (mail-io1-xd43.google.com [IPv6:2607:f8b0:4864:20::d43]) (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 EC50A120098 for <add@ietf.org>; Wed, 31 Jul 2019 00:56:39 -0700 (PDT)
Received: by mail-io1-xd43.google.com with SMTP id o9so30688174iom.3 for <add@ietf.org>; Wed, 31 Jul 2019 00:56:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JewZzA9f2DfXbZ0owRem8QgTtL7CotFIeatkkGsaxVA=; b=ebRAo8C3jr55NXiJTjIU1HVZJDyxrB0RTWDKHALGxrb0hBHxdR4smcZvY9emU76Dqw WizlCvaeRkqJaLl2jpn69Mrc4DPfQ275sgxyOrw4viFFNNtbkUMVnfHeOiZFo9OIeu+u lkdKZ5rzK9QtZrTtgCxQRTGWSUUNsLCCf+QZ/0E1HoumYBdmIWWGJxmOcoB+QcPwmIpt W9pQ0T84zi2+CN92s0TD6Mf4TJNiaapAIVOZ1tthobjWb0MDyLW0rHGMvajv6p9N170N qorJRP+JyPjBsbWWVh+mYeb6OmVizUD8+poFDKjigMnhEISEN4J4lVzDrbiY8JM3SqTW HG2A==
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=JewZzA9f2DfXbZ0owRem8QgTtL7CotFIeatkkGsaxVA=; b=RdwNbzUlCZVgSyCwjgZiiqRmpX9YfNoIRQDj8Im4kkNSqHtzUtVX63zgbj6p2jKfh0 LJ3v/LL+DVTn/2VtMRkqdIMcR0UnBV5ogYmKr0PHjqGbJlzTZqOwRpS+5encBrfg0eMp 83ZfWZQf+MRJmMakQWs2ueRkjXgjzAI2Q7FBiN1JtFG2BNYKu+z4PMsLNP21p79hhBIy Mep9ytSkFyP5kr6r9hdYXK2E5r+H4Pf6AsWt0lHcxvFVDjQXguKGpnsbPxySsPPxdhCv nu/Wrsj5v6ofuhiclRnTOcJaPorTnLKgIsh9NByBs7WPCzTq7i0wBZ+Q5Mjc37U9kxuQ 16rw==
X-Gm-Message-State: APjAAAWROTw2ek9xNtz3RVjVbIUQ0FOHkFvwTvw92DvLZp+9my0Oon5N 64pU2WVK5mrV5zbBA3uRBiE5Ee9zv5jm3Jd6o6s=
X-Google-Smtp-Source: APXvYqwNGuRSint23FoRhgQKkM0qwTQpTjVTnXSiPTEc7a+zMn7pzNz/4or7bL9SxGRd79Nxw6SCseNOU0A6WmDRKxs=
X-Received: by 2002:a02:5a02:: with SMTP id v2mr120541663jaa.124.1564559799162; Wed, 31 Jul 2019 00:56:39 -0700 (PDT)
MIME-Version: 1.0
References: <CAChr6Sx9TEt6CMzRRrdb-HwT_k987oW=4yF1FCbDF17zkaE2Vg@mail.gmail.com> <AAEA003A-58DB-4FEE-81B2-BBFE9BBB2A37@rfc1035.com> <CAChr6SwA+HM4u5-xpUxQXPH8G8k7sfm6AETJJ019HE=bsq+OXA@mail.gmail.com> <8F094057-DFBC-4732-9DA4-BE46E7914C8A@rfc1035.com> <20190724165951.GB29051@laperouse.bortzmeyer.org> <821B448B-F7EA-46A5-837D-DA0E8C60643A@open-xchange.com> <d653d422-4a71-9fab-fd2e-b8ddaa476f91@nostrum.com> <488E2CE0-73D5-4B9E-A5AD-28FDCB95ED2A@cable.comcast.com> <20190730221100.C71B315E88D1@fafnir.remote.dragon.net>
In-Reply-To: <20190730221100.C71B315E88D1@fafnir.remote.dragon.net>
From: Rob Sayre <sayrer@gmail.com>
Date: Wed, 31 Jul 2019 00:56:27 -0700
Message-ID: <CAChr6SwRoV9UVquqfC4FoG2-EexReaTMS2CkCEzf9YQiJp5NEA@mail.gmail.com>
To: Paul Ebersman <list-add@dragon.net>
Cc: "Livingood, Jason" <Jason_Livingood@comcast.com>, add@ietf.org
Content-Type: multipart/alternative; boundary="0000000000000f1c18058ef577b9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/sUZ643gboYpe6sAxRsY5Lo-f4H4>
Subject: Re: [Add] meeting hum: should the IETF take up this work?
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, 31 Jul 2019 07:56:42 -0000

On Tue, Jul 30, 2019 at 3:11 PM Paul Ebersman <list-add@dragon.net> wrote:
> Being able to tie DNS queries and individual browsers is yet another step
down that slippery slope to privacy loss.

Well, browsers are actively working on fingerprinting.

Another situation to consider: maybe operating systems will start shipping
their own default DNS servers. It doesn't seem like that would be out of
bounds for ChromeOS or iOS, for example. They already rely on several
online services. It also seems like they would probably make
enterprise/parental controls available, since they already do that.

It looks like we're considering a legacy case, where the local network
provider runs an unencrypted DNS server. I don't think there's anything for
the IETF to do here, as I wrote at the very beginning of this thread.

thanks,
Rob

v2.23.0 | Report a Bug | By Email