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

Jim Reid <jim@rfc1035.com> Tue, 23 July 2019 22:25 UTC

Return-Path: <jim@rfc1035.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 772BB1209F5 for <add@ietfa.amsl.com>; Tue, 23 Jul 2019 15:25:24 -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, LOTS_OF_MONEY=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 fp3nJVI-s_jC for <add@ietfa.amsl.com>; Tue, 23 Jul 2019 15:25:23 -0700 (PDT)
Received: from shaun.rfc1035.com (shaun.rfc1035.com [93.186.33.42]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 006A81209AA for <add@ietf.org>; Tue, 23 Jul 2019 15:25:22 -0700 (PDT)
Received: from dhcp-8a04.meeting.ietf.org (dhcp-8a04.meeting.ietf.org [31.133.138.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 4F9B9242109D; Tue, 23 Jul 2019 22:25:20 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <CAChr6Sx9TEt6CMzRRrdb-HwT_k987oW=4yF1FCbDF17zkaE2Vg@mail.gmail.com>
Date: Tue, 23 Jul 2019 23:25:18 +0100
Cc: add@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <AAEA003A-58DB-4FEE-81B2-BBFE9BBB2A37@rfc1035.com>
References: <CAChr6Sx9TEt6CMzRRrdb-HwT_k987oW=4yF1FCbDF17zkaE2Vg@mail.gmail.com>
To: Rob Sayre <sayrer@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/wbqAIm_T0kZHMKv7dtXGNfCee8k>
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: Tue, 23 Jul 2019 22:25:31 -0000


> On 23 Jul 2019, at 23:09, Rob Sayre <sayrer@gmail.com> wrote:
> 
> Mozilla's presentation accurately stated that DNS is no longer an effective control surface.

That statement will come as news to those in the multi-million (billion?) dollar business of using DNS to protect against malware, phishing, spam, botnets and so on. Like this:
https://www.nominet.uk/cyber-defence-invisible-but-pivotal

I quote from that article "our PDNS service has blocked over 30 million attempts by public sector organisations to access malicious domains since the service began. On average, the PDNS blocks over 10,000 malicious domains every month.". IMO those numbers meet any reasonable definition of effective.