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

Jim Reid <jim@rfc1035.com> Wed, 09 October 2019 08:41 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 600BA1200A3 for <add@ietfa.amsl.com>; Wed, 9 Oct 2019 01:41:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.4, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 HgNPkwX3OgXS for <add@ietfa.amsl.com>; Wed, 9 Oct 2019 01:41:33 -0700 (PDT)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 453AD12000F for <add@ietf.org>; Wed, 9 Oct 2019 01:41:33 -0700 (PDT)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (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 8D555242141F; Wed, 9 Oct 2019 08:41:30 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <db01389b-6dde-1c66-7b67-c12dfa21e0a1@cs.tcd.ie>
Date: Wed, 09 Oct 2019 09:41:29 +0100
Cc: Barry Leiba <barryleiba@computer.org>, add@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <67CDBD8A-9726-430A-BE9B-B556A2633B1B@rfc1035.com>
References: <CALaySJLxXVuHQNfTnaeKZ_R9xtBYWfbta+A1bWcE-ZQZwd3VZg@mail.gmail.com> <db01389b-6dde-1c66-7b67-c12dfa21e0a1@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/snsVQSse9La2ZOHc9QXaUzvX6rs>
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 08:41:34 -0000


> On 9 Oct 2019, at 08:51, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> 
> I see two main problems:
> 
> 1) What is out of scope? The current text seems to leave
> everything related to DNS privacy and it's impacts as being
> in scope. 

What aspects of DNS privacy should be out of scope for the proposed WG?

At first glance, the proposed charter looks fine.

I accept a broadly scoped WG could be awkward. Though what’s being proposed here seems reasonably well scoped. If the WG has strong leadership and everyone uses common sense, I think it would work. Famous last words...

BTW, it’s “its impact”. Yes, I need to resign from the apostrophe police and get out more. :-)

> 2) "This working group will coordinate with the DNSOP (OPS
> Area), DPRIVE (INT Area), and DOH (ART area) working groups,..."
> seems to me to mean that the confusion with proposals and
> discussions we've seen will continue. Moving from 3 WGs and
> a non-WG list, to 4 WGs, doesn't seem likely to help that
> aspect. For a specific example DPRIVE is already working
> on a BCP that would likely overlap with one of the initial
> focus areas listed here. That makes no sense to me.

One possibility for dealing with this overlap could be for the new WG to look at the deployment and operational considerations surrounding whatever DNS-privacy-friendly technologies emerge from DPRIVE. I suppose that could mean the BCP that’s under development moves to the new WG.

One meta-question: would ABCD be in the art area? I think ops might be a better home for it.