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

Simon Hicks <simon.hicks@culture.gov.uk> Fri, 02 August 2019 12:42 UTC

Return-Path: <simon.hicks@culture.gov.uk>
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 2E36912009E for <add@ietfa.amsl.com>; Fri, 2 Aug 2019 05:42:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=culture.gov.uk
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 8nnEvP0Md8Xx for <add@ietfa.amsl.com>; Fri, 2 Aug 2019 05:42:18 -0700 (PDT)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (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 7CB8D120033 for <add@ietf.org>; Fri, 2 Aug 2019 05:42:17 -0700 (PDT)
Received: by mail-lj1-x236.google.com with SMTP id d24so72693905ljg.8 for <add@ietf.org>; Fri, 02 Aug 2019 05:42:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=culture.gov.uk; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Ucw6VyaaXOFWNViaOVdSgtkwyLFd9OpTAMNwCC9bBQY=; b=VTLtY81u9yzq4fmKtHxrM7EMjTX92xQcEyl4avkUsl7cKI3t+xFomIvTlRaTt3nLh5 YvibiE6kw5/RDyySBZenJpDdLREbTcCumKbr0nFbFP2wMxmsSVtgyf44wq74uJFtNm8N KX1eJqzeENrcsdF2th+QLjhLTwQksvqoAHx+TSrr9EVmrIQdQM1BYYzZOHx9rjOr2H1H oTArUGovgs50gcTAN6E6cLCsuDEycih5GqECXDXUHRyvuteCi3QoLZDX9fHW7MRDu+An eQgy6PP0fO9TqpkXpBGflwxzr7jeXH+qkD5QGOXPdSJOqYthrqWwBNULsAec56DfUdRG AC/A==
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; bh=Ucw6VyaaXOFWNViaOVdSgtkwyLFd9OpTAMNwCC9bBQY=; b=qj67Z0J0+7mQJ9uVwBrVBdWSWUJdPEUDbC5gRzgkqtbEh3JITNHXT2JnL1028NzK8b lJHDaQFD/epIpe+C9LHocWdEGX3KYcuTe/RsXHbVh+jpS80uYDQ96g6wx1Z4iToQ4ATA OkOV46nn5D225CEErmtlMgMUpJaz9jtm32skVbNNvzVzubsBKepKONVC6/bgbM93SlCy 5RPASP6VAEHoH221sBM8DThsKbvsnpFJRU5CjufRkovZbYOljZIgjrqLPsecqYxLR/TG QmAKg1nJKgQ5dMcm4Kh4t3MBUrq+2sIvQcX7do7ffSBFGJ1WQgP71lD0+mocVE94vVuW PFmQ==
X-Gm-Message-State: APjAAAVn8grMZLERWzGTQgp9sp4jYHWk/bZwZ63qy8M617zmB84swCgX EkiQEGY0/4f5MnDhvAwcqJMfWtqj3pLNGveu2lBnqyo9
X-Google-Smtp-Source: APXvYqxCG/RRni/7MZNc0QIwoK3s2Z6iQ0biy+vBcgE4SDdjMYbfrVU8HhTPB51Os16mppAZ6x3FX8CertSDPrVLyuc=
X-Received: by 2002:a2e:8396:: with SMTP id x22mr73296446ljg.135.1564749734702; Fri, 02 Aug 2019 05:42:14 -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> <CAFWeb9KvoTyQqv1y+_Yoy+fHRrfYXsOE=iVLh=yt+YGVVXwxnA@mail.gmail.com> <B72AE2A8-AFCB-4DBB-936E-EE3D4909D4E4@fugue.com>
In-Reply-To: <B72AE2A8-AFCB-4DBB-936E-EE3D4909D4E4@fugue.com>
From: Simon Hicks <simon.hicks@culture.gov.uk>
Date: Fri, 02 Aug 2019 13:42:03 +0100
Message-ID: <CAOb=54SGXXagPnJyB_=fCcNOq-5iQ4Z90a+S774FkFW0o5zzKQ@mail.gmail.com>
To: ADD Mailing list <add@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000019916c058f21b0d9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/YC2fRyoZiXW60cWgoc7C-w37Xwc>
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 12:42:21 -0000

>
> Indeed, a wiki allows us to assemble material and thoughts in one place,
> rather than repeat (and forget) the same arguments in an  email chain.  It
> does not presuppose the need, or not, for a group.   It just gets on one
> page the arguments and allows us to see what a group could do
>
Regards
Simon








On Fri, 2 Aug 2019 at 13:36, Ted Lemon <mellon@fugue.com> wrote:

> Someone in another thread pointed out that it’s too soon to create a wiki.
> This discussion is a clear example of why a wiki would be good.
>
> It’s fairly clear to me that there isn’t a clear understanding of the
> threat models for which mitigations are being discussed. Clearly describing
> the threat models we believe exist in a wiki would allow us to evaluate
> proposed solutions to see if they address these threat models.
>
> Right now we are discussing mitigations that have already been shown not
> to address actual threats, but because we aren’t documenting the
> discussion, that has been forgotten and so we are repeating ourselves.
>
> Sent from my iPhone
>
> On Aug 2, 2019, at 7:37 AM, Alec Muffett <alec.muffett@gmail.com> wrote:
>
> 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
> <http://dropsafe.crypticide.com/aboutalecm>
>
> --
> Add mailing list
> Add@ietf.org
> https://www.ietf.org/mailman/listinfo/add
>
> --
> Add mailing list
> Add@ietf.org
> https://www.ietf.org/mailman/listinfo/add
>