IETF Logo Mail Archive

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

Eric Rescorla <ekr@rtfm.com> Wed, 09 October 2019 13:52 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 5981B12012D for <add@ietfa.amsl.com>; Wed, 9 Oct 2019 06:52:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 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] 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 DFsc_bigFCse for <add@ietfa.amsl.com>; Wed, 9 Oct 2019 06:52:09 -0700 (PDT)
Received: from mail-lf1-x134.google.com (mail-lf1-x134.google.com [IPv6:2a00:1450:4864:20::134]) (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 C3DE6120154 for <add@ietf.org>; Wed, 9 Oct 2019 06:52:08 -0700 (PDT)
Received: by mail-lf1-x134.google.com with SMTP id 72so1731658lfh.6 for <add@ietf.org>; Wed, 09 Oct 2019 06:52:08 -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=cH9G22bkTzYAG53GFQV5UOOAS/TKU9J896GrALIN9G4=; b=p4iJar/uzKyeMM8CNJFEfIeDKHGYqDgtx5jjMq8XpaIoqjWBMqAWdHzl11C1hPuwL0 TxdncgeebCmkF0nWmvvEwo6syg1BUTYrCLnGfOiYokanoG4MShrFBiRouJf1NTGco2AW EewLXZhHR8Uq9a3OlMSChRekvwy1Utb3qTzT6BbYGV+LZVvySQ/d69ki9r8fjGr3fLjD 0laagz/c3+V2Vpc9rjH6OzWQijSd93Ry2+n8B5DaNsBMMauj0UthPx7ztasb9123Xw4r wr4joqHIak2LpsXVAu6ibR+cQTJmqIYDZT1X1mzZhfjCMEajrRon/x2DPWzJsPiXt+gl G2qg==
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=cH9G22bkTzYAG53GFQV5UOOAS/TKU9J896GrALIN9G4=; b=QbpOkvBqJjCg57czbKmt6ZlQdBIh0RlcmQeIGWunR3gJjs+E28+Ke2VivNRSNx/KfV lCV+501dMUAahi7OOu45qk866BX4mlZBdz5xvRI9LmFGep+gDNVVwv89K2XM/hxvCYR/ C/iE4CMwUbRXP40MfuWJfLDyeOn3h2DarCEZoP/jjzVG/SSzC4ZRrq4zIBwdHksQ59G2 eiPB6IkDeBvRxqhGQak/Ngl/yR5BWKjQW+UCYLmCWHEQY0qvYjns0rpquqQOC0B3X8qG ZnO01yzCVmdIf5amj3TlVuP6H6G1CchDJnL4d9fYmHMsgcrtwKKWrNG6h7YHzkmlEFLF 5VNw==
X-Gm-Message-State: APjAAAXhwnzO3nU6G+JzfS8y8QM0paCunp6GiNZibgtRQT1tjujbuvva YXtsTmUmbNnRxTohi9dOe9C6WxaUjfMmjzCCOHZHqQ==
X-Google-Smtp-Source: APXvYqx3R28XigmSdOU59fK5kSwwuZzGD5cPuimcI1ZV8cjhFeGDbaeTdW9ASmVGxA8HbbZUb3YmeEJOQCJGVo74+LI=
X-Received: by 2002:a19:4a02:: with SMTP id x2mr2036280lfa.17.1570629127081; Wed, 09 Oct 2019 06:52:07 -0700 (PDT)
MIME-Version: 1.0
References: <CALaySJLxXVuHQNfTnaeKZ_R9xtBYWfbta+A1bWcE-ZQZwd3VZg@mail.gmail.com> <CABcZeBMkAFZW9mWjw92v+OR0Fa8ed+P80yc78eY07hCpsCNY6Q@mail.gmail.com> <LO2P123MB2256A416C25822B08BCCF9409B950@LO2P123MB2256.GBRP123.PROD.OUTLOOK.COM>
In-Reply-To: <LO2P123MB2256A416C25822B08BCCF9409B950@LO2P123MB2256.GBRP123.PROD.OUTLOOK.COM>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 09 Oct 2019 06:51:30 -0700
Message-ID: <CABcZeBOnn7WOG3nz1XMP0jGux2gaYGgQskLoFzAvHift+teRtw@mail.gmail.com>
To: chris.box@bt.com
Cc: ADD Mailing list <add@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000031a1c405947a97d3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/4Mes5sArWvV3HU2_H9zEmuHUXGk>
Subject: Re: [Add] Proposed charter and BoF request for IETF 106
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, 09 Oct 2019 13:52:11 -0000

On Wed, Oct 9, 2019 at 6:36 AM <chris.box@bt.com> wrote:

> > This list of practices would be much more accurate if it included the
> > resolver-level DNS practices that we are trying to mitigate using DoH,
> > including NXDOMAIN synthesis and collection of user browsing history
> > data.
> > Just having network operators transition to secure transports while
> > continuing their current practices does not address the issue.
>
> Please point me to an operator that is arguing for the continuing of
> NXDOMAIN monetisation.


Arguing or not, it continues to happen, at least on T-mobile.

-Ekr

v2.23.0 | Report a Bug | By Email