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

Michael Richardson <mcr@sandelman.ca> Tue, 23 July 2019 23:49 UTC

Return-Path: <mcr@sandelman.ca>
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 14776120991 for <add@ietfa.amsl.com>; Tue, 23 Jul 2019 16:49:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 ayshYz8MePJx for <add@ietfa.amsl.com>; Tue, 23 Jul 2019 16:49:03 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B35112098D for <add@ietf.org>; Tue, 23 Jul 2019 16:49:03 -0700 (PDT)
Received: from dooku.sandelman.ca (dhcp-8960.meeting.ietf.org [31.133.137.96]) by relay.sandelman.ca (Postfix) with ESMTPS id E21301F44B; Tue, 23 Jul 2019 23:49:01 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 670981BBF; Tue, 23 Jul 2019 19:49:24 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Rob Sayre <sayrer@gmail.com>
cc: Jim Reid <jim@rfc1035.com>, add@ietf.org
In-reply-to: <CAChr6SwA+HM4u5-xpUxQXPH8G8k7sfm6AETJJ019HE=bsq+OXA@mail.gmail.com>
References: <CAChr6Sx9TEt6CMzRRrdb-HwT_k987oW=4yF1FCbDF17zkaE2Vg@mail.gmail.com> <AAEA003A-58DB-4FEE-81B2-BBFE9BBB2A37@rfc1035.com> <CAChr6SwA+HM4u5-xpUxQXPH8G8k7sfm6AETJJ019HE=bsq+OXA@mail.gmail.com>
Comments: In-reply-to Rob Sayre <sayrer@gmail.com> message dated "Tue, 23 Jul 2019 15:30:10 -0700."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6245.1563925764.1@dooku.sandelman.ca>
Date: Tue, 23 Jul 2019 19:49:24 -0400
Message-ID: <6246.1563925764@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/zo_YWlM2kI2tV0L3QZf32HRu_Fo>
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 23:49:05 -0000

Rob Sayre <sayrer@gmail.com> wrote:
    > I think that's a fine position to hold. If adoption of DoH is harmful
    > along the lines you describe, it won't succeed. I don't think the IETF
    > has a role in deciding that preemptively, though.

But, perhaps we can both.