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

Ted Lemon <mellon@fugue.com> Wed, 09 October 2019 14:17 UTC

Return-Path: <mellon@fugue.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 7C493120854 for <add@ietfa.amsl.com>; Wed, 9 Oct 2019 07:17: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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=fugue-com.20150623.gappssmtp.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 AH58tEbd-rbu for <add@ietfa.amsl.com>; Wed, 9 Oct 2019 07:17:03 -0700 (PDT)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (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 448AF120841 for <add@ietf.org>; Wed, 9 Oct 2019 07:17:03 -0700 (PDT)
Received: by mail-qt1-x835.google.com with SMTP id j31so3649851qta.5 for <add@ietf.org>; Wed, 09 Oct 2019 07:17:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=mbYhLCmeUPJjpZ0Fab7hn8guZ0xCzu7n0sqTTAmgmj4=; b=w2tFAg7jLDqiO5NupZ57JVLG0jnfItg3mxno3yaYPA8o5SDjk22OYLz/hRe4vPOhsv MZxhn8pmiT2Nrqk4hafB5wvlG9BHXc271ilSVO5rxigZX8dq8k7iJKUs0rleFTROTpkt IP4JqR7iRBZpgvjUAwundKU1fQ51wzOohwdlvor3R36EFO26BkeIYnbXWDTIVgxBnzRr vDqUovFjPvBcjoBs495nrKvk2XhznteDm4tiPskuFW5LowEkid3p9Mw+4p8LurSbLeLm eRok7b5yuHOVG+nqcB3/m1He2l7rr5V/ILa0u3HOsGh2KF47MXZDcNrW9gHAM1hENTWI pOqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=mbYhLCmeUPJjpZ0Fab7hn8guZ0xCzu7n0sqTTAmgmj4=; b=U/0dow3vaeypX22rxwPQ0BTIieCS/JHh3vEquMp17yu0RHkLv2JK4e1T8ZyJHq41kZ V6r1h/EnAU4prRWN4iV9SOgFVStxfe1LwIA3z3DaqJcQ1X0LYtViXucMyUfHi2ElRBnB YThdWRv0qjszSxmIbXRx6ncTobcsR2TeAFalK5bcaVPI7+AVNWewCdwXGo5e/6XyoZXP waOyaNtuBBV8npsBZd+mBmbliSORs0+FtJcTdqTtFdYgg1E1oOLlC0sXDLuIFuGq3fNw 0LzuVhVgCcyOa6YfDiAEmUb5SpnrQ+U4XeavpbYPQ+bMCsgpP4YorC7MqkWZe1HWuZLG JjgQ==
X-Gm-Message-State: APjAAAVUlL+xthhDu8JghQoSCvl+H9KvQNhSIHPTLItriVbiaE3Rfk8a PotOjpUHArC//q+xVI3PW6DyQRZy3Is=
X-Google-Smtp-Source: APXvYqxbCcDQd4VAuvtbNm09bA7hNfe72omIUL3oelL5eLuIJbvOSrrrf6cF4Y4ZKLta9BezAZVl9w==
X-Received: by 2002:ac8:48d9:: with SMTP id l25mr3742337qtr.1.1570630621853; Wed, 09 Oct 2019 07:17:01 -0700 (PDT)
Received: from [10.0.100.56] (c-73-186-137-119.hsd1.nh.comcast.net. [73.186.137.119]) by smtp.gmail.com with ESMTPSA id s50sm1274660qth.92.2019.10.09.07.17.00 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 09 Oct 2019 07:17:00 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Ted Lemon <mellon@fugue.com>
Mime-Version: 1.0 (1.0)
Date: Wed, 09 Oct 2019 10:16:59 -0400
Message-Id: <7B345BCE-F23A-47F7-95EB-2201F57F84E7@fugue.com>
References: <CALaySJ+r0WAt+=33cV73q88KKc+gj3O6LtfcLxFOhDjcLP+U3A@mail.gmail.com>
Cc: add@ietf.org
In-Reply-To: <CALaySJ+r0WAt+=33cV73q88KKc+gj3O6LtfcLxFOhDjcLP+U3A@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: iPhone Mail (17A850)
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/KppVX7CYiR8ND2aMCU6D6vnauMc>
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 14:17:11 -0000

If the proposal was half baked due to hurry, maybe the right approach is to wait until March. If you really think it’s urgent, you could do it as a virtual BoF in January.  That’s what the IESG would say to me if I proposed something that was too rushed.  

Are you going easier on yourselves than you would on an outsider?  What is the rush?  Is there some goal that you are pushing to achieve that justifies this rush?

At present, the charter does not even discuss some of the most important use cases for dns services configured by the network operator, particularly the ones that involve surveillance. And we’ve had endless discussions on the exact topic of the proposed BoF here on the ADD mailing list with no evidence of consensus on the topics in the proposed charter. 

With that in mind, why does the IESG consider this a good use of meeting time? We already had this BoF in Montreal. We know there is no consensus on these topics. Can you make brief, crisp elevator pitch on why this is worth the IETF’s time?

> On Oct 9, 2019, at 09:31, Barry Leiba <barryleiba@computer.org> wrote:
> 
> 
>> 
>> Who wrote the charter? Shouldn’t the BoF proponents be 1-3 individuals, rather than a mailing list?
> 
> That's a fair question.  The answers are:
> 
> - The IESG write the charter proposal as something to float to the community.
> 
> - We took longer than we would have liked to get it done, and we
> wanted to be sure we had it ready for discussion as soon as possible,
> and to be sure we had a reasonable placeholder for BoF approval
> (today).  That was sloppy, and I'm sorry for that, but we also did not
> have time to get it socialized and to have people signed up as
> proponents and possible chairs yet.
> 
> So if it helps, consider "the IESG" as the charter proposal writers
> and "5 or 6 ADs" as the BoF proponents.
> 
> Barry
> 
>> On Wed, Oct 9, 2019 at 10:55 AM Rob Sayre <sayrer@gmail.com> wrote:
>> 
>>> On Wed, Oct 9, 2019 at 2:39 PM Barry Leiba <barryleiba@computer.org> wrote:
>>> 
>>> 
>>> I realize that the charter proposal isn't going to please everyone
>>> (and perhaps will please no one), but it's something that, at a first
>>> level of review, the IESG accepts and will likely want to move forward
>>> with.
>> 
>> 
>> Hi,
>> 
>> Who wrote the charter? Shouldn’t the BoF proponents be 1-3 individuals, rather than a mailing list?
>> 
>> The proposed charter looks extremely misguided to me. But a proposal that no one will put their name on doesn’t even deserve an argument.
>> 
>> thanks,
>> Rob
>> 
>> 
> 
> -- 
> Add mailing list
> Add@ietf.org
> https://www.ietf.org/mailman/listinfo/add