IETF Logo Mail Archive

Re: [Add] point of deploying DoH in access network (Re: meeting hum: should the IETF take up this work?)

Alec Muffett <alec.muffett@gmail.com> Fri, 02 August 2019 11:38 UTC

Return-Path: <alec.muffett@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 E427C120096 for <add@ietfa.amsl.com>; Fri, 2 Aug 2019 04:38:28 -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 EuYHgraybFo7 for <add@ietfa.amsl.com>; Fri, 2 Aug 2019 04:38:26 -0700 (PDT)
Received: from mail-yb1-xb34.google.com (mail-yb1-xb34.google.com [IPv6:2607:f8b0:4864:20::b34]) (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 5013E120033 for <add@ietf.org>; Fri, 2 Aug 2019 04:38:26 -0700 (PDT)
Received: by mail-yb1-xb34.google.com with SMTP id s41so4586270ybe.12 for <add@ietf.org>; Fri, 02 Aug 2019 04:38:26 -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=Ru5OWoUsBV+haBMZYty7PSBBmHoZHLXJP2pcvE5bHn4=; b=bfXriFmGyLwgGdsXZL1AjFfNeIVVwGH33clrKV8W3PjcTC24P8GJA3IDOAcYfvNsWf ZsJsRegRe+gLjWebzLcl+oE8zq90xRIXoslOxpB8iHrxZS3dbndh5UCFhD9Opwy3UKvI uu5PWR/i+WShjmoiVvmkFbIorhk0DX4CTUeR9k2dg8Sq4jhzGSDgHkfnQP9f2MTF1Ix6 cyAoVYMTMMtnmbYfaDm5lwsoEBrb1i6g5vZUpszsK537LMLavd3d2FIHBH62b1al+M+Q qw0inlML1rz/MOtbMG//BymdQak0jqZdknlzAkzOt5JA5ooPJFiuxnCkuJpxZgo0chqF e8kg==
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=Ru5OWoUsBV+haBMZYty7PSBBmHoZHLXJP2pcvE5bHn4=; b=FuPl498ulJ8ZluAP4It+cQQhGrwpE/v7WHbmaZYV/G1+3mf53iuFSwoLoHxUQsLEbc 5ov4BR5uzQ6zLHPu+PR9/VJ5gMzqBrlIf+Eecrkx5tzLL2QKaz9S8ecQhE0dudTzNof7 K0uZNTvvakdkwO2ZThAqxUBmtExLH1Sk3X2SGw57EBlCMX1TpcAo8a9wdI2FZSKeKE7e WVfCvibLG5E0dQ8Y2gN6WvAbM9QQP8k4x8unc+ghw51mUdldoWeRlpZXS/UEXRrf7D6m PpoL+kwsvyG8yQ9kTHwmv7/gXRn/7kVNiqHjLXT4JkbDFr8l5pRLuJdm/lCiZPBp9S3o 1J6Q==
X-Gm-Message-State: APjAAAX/M4e7kaQJpn2nRXTD5q/AJUf+GiaJ8yrxpu+CMzXt0GuyihE3 iw5Wk3nsDKVUsoOrQs9F8yDP6h1Z2lEhg3Kj3nJTDNs/r7k=
X-Google-Smtp-Source: APXvYqzzD1NZ/30O6FVobjFGVZbA3ERn3oC7O2EetUFPBvZqHRCG5Ni++yau8sJmJI3kgCWfMflj5S2IUdWuxuQvBko=
X-Received: by 2002:a25:f20d:: with SMTP id i13mr29922536ybe.170.1564745905244; Fri, 02 Aug 2019 04:38:25 -0700 (PDT)
MIME-Version: 1.0
References: <CAChr6Sx9TEt6CMzRRrdb-HwT_k987oW=4yF1FCbDF17zkaE2Vg@mail.gmail.com> <2D09D61DDFA73D4C884805CC7865E6114E23910C@GAALPA1MSGUSRBF.ITServices.sbc.com> <20190724171549.GD29051@laperouse.bortzmeyer.org> <CAJE_bqf=9r5yvCMY+CGuXMQBCNY+a-RFQTzjJ83wOtawhUHR0g@mail.gmail.com> <alpine.DEB.2.20.1908021048100.11612@grey.csi.cam.ac.uk> <26e4fa63-f50d-42d6-bcda-4d7e62b95704@getmailbird.com>
In-Reply-To: <26e4fa63-f50d-42d6-bcda-4d7e62b95704@getmailbird.com>
From: Alec Muffett <alec.muffett@gmail.com>
Date: Fri, 02 Aug 2019 12:37:48 +0100
Message-ID: <CAFWeb9KvoTyQqv1y+_Yoy+fHRrfYXsOE=iVLh=yt+YGVVXwxnA@mail.gmail.com>
To: Robert Mortimer <robm=40scramworks.net@dmarc.ietf.org>
Cc: ADD Mailing list <add@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d88df8058f20cb57"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/tawPq-FrXbP2cLpMQP5WeaooLSk>
Subject: Re: [Add] point of deploying DoH in access network (Re: 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: Fri, 02 Aug 2019 11:38:29 -0000

On Fri, 2 Aug 2019 at 12:18, Robert Mortimer <robm=
40scramworks.net@dmarc.ietf.org> wrote:

>  Just on the javascript in browser making DNS queries, already been done
> to control a spam campaign.
>
> https://www.bleepingcomputer.com/news/security/new-spam-campaign-controlled-by-attackers-via-dns-txt-records/
>
> So the bad guys at least are already doing this. They could of course use
> other methods etc. etc.
>

For anyone else who hasn't been through the archives, this one has already
been discussed on this maillist:

    https://mailarchive.ietf.org/arch/msg/add/6lkOu-0D6OWNfHwnsK7S1NkG6Oo

    https://mailarchive.ietf.org/arch/msg/add/OoEVkT3IdLnTqhBuE777MKPAlRo

- alec

--
http://dropsafe.crypticide.com/aboutalecm

v2.23.0 | Report a Bug | By Email