IETF Logo Mail Archive

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

Rob Sayre <sayrer@gmail.com> Sat, 27 July 2019 19:04 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 C199F12004F for <add@ietfa.amsl.com>; Sat, 27 Jul 2019 12:04:58 -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 5n9gYdmENLr9 for <add@ietfa.amsl.com>; Sat, 27 Jul 2019 12:04:56 -0700 (PDT)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 AC726120018 for <add@ietf.org>; Sat, 27 Jul 2019 12:04:56 -0700 (PDT)
Received: by mail-io1-xd2b.google.com with SMTP id g20so111618366ioc.12 for <add@ietf.org>; Sat, 27 Jul 2019 12:04:56 -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=Z7fC/1ntKSsZt4qzUlGvcz8PRePjrV1d+kj1QL8Hxdw=; b=HIzrk7D3DmAeTpsNL/Qip1cmfgNrg++qlpeMFT8VbrkQllwsODFL8oQOJbI0KauYHD H3cjygoyCnTGNcQdS4IpLkl6fDbiBqF85oFc5jg64a8ZXRfgnbpR4oylv31XrB6WrYvG 6oYetqgumJLYAlbWVRtjyE3svctzVrK1h/Rn8JaVEGkOsvLArmLwwpAGcP2MIPrFkoRq IKU4azdXF0FM2zSlk7EEpSSlY9RsB9Sh0WWF/0vVu3BhQU/i/zEeA2fA56mKQr/xJqLV iQ5Fqgpxn4F16tmyTZfra+ULHNSVEUWumc6+KqjdT39zaZKoAAFKeFUgUg8vSG4g+Xro 8GpQ==
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=Z7fC/1ntKSsZt4qzUlGvcz8PRePjrV1d+kj1QL8Hxdw=; b=SN53XFAXcDSDWS8agQ579HNRUF9a5sdQWSjSnReapLTmF9TyiHwqzcNvX/797ZSHhh jSEewxqD9SwLBJggIab+GUsNjgLfs40sm34KU64Fvx3l5Or7lfrK7sLdZte5LLU/5YG8 RAvkUoumMHURnU2HXfowYbPpJG5PFuXsKrxs8Ezm2pjXZm0D+2O+/576EmZUYhdRgxxo Ydd6etSFiYFckZVfJiFbj3XDUxtN20OwPtjBq2GnAg4tyE8g1njA9nGjnmRxshe+4Zte /dRVPlDLhr9q+kmjCF0JeShsG0iQBAWx8yrwnLFf2goNr4CyUU5IndLjekJijye2DEeJ Jr5Q==
X-Gm-Message-State: APjAAAVLK2ej7T45HlfaMNfHdFB1jiM2Ly9ke/8iBL1AbPYu/z6C/WZa hveP5iqJJ8cIKefnLoA5dn+7r5dpztCIbi4vbjABSxyJ5slj+k8F
X-Google-Smtp-Source: APXvYqz6QC6PHOIORd28QBrTzNwUirS7eyF29w36ewi0pvBkTbwaNYVt2Hft386jUvJsJ5izvVu+L6FIPi/suCO4jmo=
X-Received: by 2002:a02:5a02:: with SMTP id v2mr101336319jaa.124.1564254295809; Sat, 27 Jul 2019 12:04:55 -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> <25583.1564181379@dooku.sandelman.ca> <CAHbrMsCd_0xAsFYAVyO=Jo-t_Zw0WE9j=fNphQsAkL-_TwVf1w@mail.gmail.com> <CAChr6SwPue5VO8mP1YhZ_5jcbUBuQKK9rWTJsf7bWRpAQN9hGg@mail.gmail.com> <f3e49d87-7804-4b7e-7f5f-86a17b3bcf5b@cs.tcd.ie> <CAChr6Sx2L5P_M0u-ipW8dR=PtKHhzjvYqL=01VXue3AATgFraw@mail.gmail.com> <b43623ec-5681-37c6-d411-0ab77f36cb4a@cs.tcd.ie>
In-Reply-To: <b43623ec-5681-37c6-d411-0ab77f36cb4a@cs.tcd.ie>
From: Rob Sayre <sayrer@gmail.com>
Date: Sat, 27 Jul 2019 12:04:44 -0700
Message-ID: <CAChr6SxS0JA=yRrNuguZSsZjpd1qmnYkgP1sDmd7KvRUogZ_3A@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Ben Schwartz <bemasc=40google.com@dmarc.ietf.org>, add@ietf.org, Adam Roach <adam@nostrum.com>, Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary="000000000000a3e604058eae5552"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/HLffHSO2AFHE5Sy48NRZfQI5vc0>
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: Sat, 27 Jul 2019 19:04:59 -0000

On Sat, Jul 27, 2019 at 11:30 AM Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

>
> Evidence that it is really happening would be more interesting
> as part of this discussion, as, should that be the case, it'd I
> think provide a strong argument for the kind of TRR setup that
> mozilla seem keen on.


https://arstechnica.com/information-technology/2015/03/atts-plan-to-watch-your-web-browsing-and-what-you-can-do-about-it/

There's plenty of evidence that ISPs use DNS traffic to fuel their own ad
networks (again, no judgement). I also found some research that shows DNS
information being at least "shared":

https://blog.benjojo.co.uk/post/ISPs-sharing-DNS-query-data

In that context, I don't think a WG is going to be productive.

thanks,
Rob

v2.23.0 | Report a Bug | By Email