Re: Request for feedback - IESG thoughts about new work proposals
Keith Moore <moore@network-heretics.com> Sat, 14 October 2017 12:18 UTC
Return-Path: <moore@network-heretics.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 69CCB133207 for <ietf@ietfa.amsl.com>; Sat, 14 Oct 2017 05:18:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level:
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.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 7W1hL7ESASAZ for <ietf@ietfa.amsl.com>; Sat, 14 Oct 2017 05:18:00 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B0DE1331D2 for <ietf@ietf.org>; Sat, 14 Oct 2017 05:18:00 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 1EFDA209AD; Sat, 14 Oct 2017 08:17:59 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Sat, 14 Oct 2017 08:17:59 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=cMr8tZjym7rY1RhyXJvBNaE+6DTky ajeLD3xzqUn1e4=; b=Mx+TRNt4YIw/5wOIKZ4vHw7TwDPeI+Xsr7tWlrVRqQEwt lRlvMGZMKZXGPeYVDcFu1Tt79qIUQwdCemMbhtyzQJ5uh59dobxHDXSAm5HZH+1+ Nl5j/rmnQGlIVBsSwPSJmtrKQLR6Hw8KahXHvtMfyIMimUDqMSsgMrRmAjoZHkWV SYi2DsRlyACH6YsYGXRw3G7LxmXSEmXZ3iAjXzFPgeWqvPXrEBnKdY3BClEeQVvF I83U/3lJkuXY/2afH4aZVW5h8/kxcTx1AdBTKVHKG3K6A8mMKu8j55ARITaP0CCY RfuHjnV2K4Ps94MByWB6BFym9YVoLG9Zpd2kxAGBQ==
X-ME-Sender: <xms:dwDiWYscJFBLZSycvK8AhyIrn_lzylcWMeUeE3kfbkTaGtIZg33EvA>
Received: from [192.168.1.66] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 882987F961; Sat, 14 Oct 2017 08:17:58 -0400 (EDT)
Subject: Re: Request for feedback - IESG thoughts about new work proposals
To: ietf@ietf.org
References: <CAKKJt-fAaNPeeuSfS0Dv6vTAOXR=OS2XSKqPVMyxxr1O1tLwBg@mail.gmail.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <e29d2547-3ad1-9402-c4b7-a005982d003a@network-heretics.com>
Date: Sat, 14 Oct 2017 08:17:57 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <CAKKJt-fAaNPeeuSfS0Dv6vTAOXR=OS2XSKqPVMyxxr1O1tLwBg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------7FD2873F0266F2D493C48E29"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qh-Nc-SAVBz2YkGZQRuDQgcAdQo>
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: Sat, 14 Oct 2017 12:18:01 -0000
On 10/11/2017 09:21 AM, 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. We want to share our > expectations about BOF requests and new work proposals with the > community because we are interested in feedback. > So I understand the scope of this request for feedback to be about improving IESG's ability to charter new work, and that's an admirable goal on IESG's part. However, I wonder if IESG has come to think of the purpose of BOFs as being to lead to new WG charters in the short term. If true, I think it's unfortunate. One of IETF's biggest problems IMO is the tendency to silo work, to fail to recognize when there is a need for broadly applicable work rather than point solutions. This in turn leads to a great deal of unnecessary complexity in network code and applications, and a tremendous amount of wasted effort. The resulting tendency is to produce too many working groups, too many standards documents, and standards documents with too-limited scope or applicability. Note that I said this is IETF's problem, not specifically IESG's problem. But I see essentially no effort within IETF to try to identify common ground between different concerns, or to look for opportunities to address multiple concerns with a common framework. And it's much easier to do this before working groups are chartered, than after. IAB has sometimes tried to do this by holding meetings, but the meetings have seemed fairly exclusive (there are high barriers to participation) and also have taken a long time to produce results. I'd like to see an effort to encourage IETF participants in general (not just a few handpicked people) to think more broadly. I'd like to see more meeting time devoted to identifying common ground and opportunities for more broadly applicable work. Such efforts should NOT be expected to propose working groups, at least not in the near term. It's fine if they do, but the expectation should not be there. And I don't care what such sessions are called, but I think BOFs were originally supposed to be able to serve such purposes. And maybe IESG is too busy to charter them, because it needs to be focused on working groups. Maybe that should be left to IAB or some committee appointed for that purpose. But there should be a clearly visible path by which IETF participants can request such sessions. Keith p.s. It is tempting, if the only tool you have is a working group, to treat every problem as if the solution were more protocol specifications.
- Request for feedback - IESG thoughts about new wo… Spencer Dawkins at IETF
- Re: Request for feedback - IESG thoughts about ne… Eliot Lear
- Re: Request for feedback - IESG thoughts about ne… Michael Richardson
- Re: Request for feedback - IESG thoughts about ne… Spencer Dawkins at IETF
- Re: Request for feedback - IESG thoughts about ne… Brian E Carpenter
- Re: Request for feedback - IESG thoughts about ne… Spencer Dawkins at IETF
- Re: Request for feedback - IESG thoughts about ne… George Michaelson
- Re: Request for feedback - IESG thoughts about ne… Ted Lemon
- Re: Request for feedback - IESG thoughts about ne… Stewart Bryant
- Re: Request for feedback - IESG thoughts about ne… Michael Richardson
- Re: Request for feedback - IESG thoughts about ne… Michael Richardson
- Re: Request for feedback - IESG thoughts about ne… tom p.
- Re: Request for feedback - IESG thoughts about ne… Keith Moore
- Re: Request for feedback - IESG thoughts about ne… Eliot Lear
- Re: Request for feedback - IESG thoughts about ne… Spencer Dawkins at IETF
- Re: Request for feedback - IESG thoughts about ne… Eliot Lear
- Re: Request for feedback - IESG thoughts about ne… Alia Atlas
- Re: Request for feedback - IESG thoughts about ne… Keith Moore
- Re: Request for feedback - IESG thoughts about ne… Spencer Dawkins at IETF
- Re: Request for feedback - IESG thoughts about ne… Brian E Carpenter
- Re: Request for feedback - IESG thoughts about ne… Keith Moore
- Re: Request for feedback - IESG thoughts about ne… Spencer Dawkins at IETF
- Re: [EXTERNAL] Request for feedback - IESG though… Deen, Glenn (NBCUniversal)