Re: Request for feedback - IESG thoughts about new work proposals

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 12 October 2017 19:44 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 208B7127517 for <ietf@ietfa.amsl.com>; Thu, 12 Oct 2017 12:44:40 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 0-7X_U4OIHim for <ietf@ietfa.amsl.com>; Thu, 12 Oct 2017 12:44:37 -0700 (PDT)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::234]) (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 237BD126B6E for <ietf@ietf.org>; Thu, 12 Oct 2017 12:44:37 -0700 (PDT)
Received: by mail-pf0-x234.google.com with SMTP id l188so6346447pfc.6 for <ietf@ietf.org>; Thu, 12 Oct 2017 12:44:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=rQHJPabSDDhl3eFXEz4rSoMqDc0cfNQAXMBOdajleLw=; b=iifIMuANOWaoZhJRrfxzLGtryEzwZjTY7uCI8lKkpxHD3P6UZSAOVx8UlQj9AS2Pqb yU3Xfv5RNWML8Y3qexl7GHrEV1xdjywfwSKNnBQo5dfsu7tRdFTIJ8SIF8XFE3qm2SGX 3R5POPTC4KoP4kmoMdtaj7ALN6Q5hCK1IQYhN9C5eT672yNORh0lnczF8HHyX94brGHr UdIXGWU4AZfEP2/WjzO/L2pqVrzGk51jVCs46Dyg87AcyM0/InVvwptKWVvjmHQqydaW BcSjvMd0+xS5snKtWlKD2aom9AYuyFnW9cgcAbuJJC23+FvVuLenCOzUvggeIr2ux0nK 5VaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=rQHJPabSDDhl3eFXEz4rSoMqDc0cfNQAXMBOdajleLw=; b=fK48UKDOdao1n6G6QvgNYfllfizCEx+CFC+QcMG3SebMXHlJhM/pJQN24xQaH2rntb ueBBx2oJFsxK78//4I1vnsEq5+fc/hFDZc9bU5QeJqSxx0Fx6RJ7j8+6icFRW3YBOGwu TbHpVe0fj2SQgO0pFnPpKIPIAtg4jY7ESR8RJT48hWZO1mT90EyOgnv5LMnulKejhOGf kN/uCd+6DnwErlW1RuuxAOdFhCC8rIVD4Zm5dYCYL2qV4Ols7MTGoQ9/QTiHsyRZJPCC 7WWGsdBg21oONJobbeRnqF3MalMgWPWmWRWkOaGWMTWYO0ymHDs47MqjegPxXrvLGxnN 1wSQ==
X-Gm-Message-State: AMCzsaU+3ElU37SI7RxYHAo6AnffnXA9tKh110sxpPihUAvKB6Vp6LEo N7wtpQ7p883pcuko0YBszaOEGA==
X-Google-Smtp-Source: AOwi7QBFvpMP9CnRwRHxU5xyXm6UwXhh6C7PIOn6PtLHsnUOzaTulPbXTr6Ycpt4BEnfaSWWZAHPxQ==
X-Received: by 10.98.73.134 with SMTP id r6mr3091476pfi.145.1507837476227; Thu, 12 Oct 2017 12:44:36 -0700 (PDT)
Received: from ?IPv6:2406:e007:6d3c:1:28cc:dc4c:9703:6781? ([2406:e007:6d3c:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id l5sm23615452pfi.165.2017.10.12.12.44.33 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Oct 2017 12:44:35 -0700 (PDT)
Subject: Re: Request for feedback - IESG thoughts about new work proposals
To: ietf@ietf.org
References: <CAKKJt-fAaNPeeuSfS0Dv6vTAOXR=OS2XSKqPVMyxxr1O1tLwBg@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <7d45859d-6efc-5576-e413-8c9162c42776@gmail.com>
Date: Fri, 13 Oct 2017 08:44:40 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <CAKKJt-fAaNPeeuSfS0Dv6vTAOXR=OS2XSKqPVMyxxr1O1tLwBg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/v3VYLPybR_SmLhkXRoIWfxhN6R4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Oct 2017 19:44:40 -0000

Spencer,

On 12/10/2017 02:21, Spencer Dawkins at IETF wrote:
> The IESG has spent considerable time discussing how we can improve our
> ability to charter new work as soon as it’s ready and ensure proposals have
> the resources needed for success.

I pretty much support the proposed approach as far as WG-forming BOFs
are concerned; and I think we should also support the IESG's right to
Just Say No too. I've been amazed for years by this apparent constant
of nature: the number of IETF WGs is approximately 120. Why?

However:
...
> The IESG has received some BOF requests that describe interesting problems
> at considerable length but do not clearly identify what the BOF proponents
> want the IETF to do. When that happens, we cannot approve a BOF intended to
> form a working group.
> 
> In some cases, area directors might approve a non-WG-forming BOF to tease
> out the details of the BOF proposal, but often that isn’t the best way
> forward.

This bothers me, because it makes non-WG-forming BOFs sound like second
class citizens, and I think that's wrong. A non-WG-forming BOF has two
possible outcomes (in general terms):

1. There's something here that seems to need doing. Start working towards
a WG-forming BOF.

2. There's nothing coherent here. Forget about it for now, as far as
the IETF is concerned. (There may be subsidiary outcomes here, like
suggesting some IRTF activity, but as far as IETF resources go, it's
over.)

Both of these are good outcomes from the IETF's viewpoint.

    Brian