Re: Quality of Directorate reviews

Jared Mauch <jared@puck.nether.net> Wed, 06 November 2019 17:49 UTC

Return-Path: <jared@puck.nether.net>
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 28D8B120144 for <ietf@ietfa.amsl.com>; Wed, 6 Nov 2019 09:49:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 nYybYUgOwDX9 for <ietf@ietfa.amsl.com>; Wed, 6 Nov 2019 09:49:07 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0959412012A for <ietf@ietf.org>; Wed, 6 Nov 2019 09:49:07 -0800 (PST)
Received: from [10.0.0.129] (173-167-0-106-michigan.hfc.comcastbusiness.net [173.167.0.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id D6C765400F5; Wed, 6 Nov 2019 12:49:03 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Subject: Re: Quality of Directorate reviews
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <7d7b2541-c5b2-dbfc-e503-36fffc6fabeb@network-heretics.com>
Date: Wed, 6 Nov 2019 12:49:03 -0500
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <8A7F75B1-9CB8-4E78-9180-427C76523EB1@puck.nether.net>
References: <157279399807.13506.13363770981495597049.idtracker@ietfa.amsl.com> <0EF64763-BA25-468A-B387-91445A61D318@gmail.com> <CAJU8_nUovmFmgNiYx0ez_1f+GPdU9xGViDYWfowEEomrn0pyDw@mail.gmail.com> <alpine.LRH.2.21.1911040841160.27600@bofh.nohats.ca> <CE06CC6D-E37F-4C90-B782-D14B1D715D4B@cable.comcast.com> <38E47448-63B4-4A5D-8A9D-3AB890EBDDDD@akamai.com> <09886edb-4302-b309-9eaa-f016c4487128@gmail.com> <26819.1572990657@localhost> <2668fa45-7667-51a6-7cb6-4b704c7fba5a@isode.com> <2C97D18E-3DA0-4A2D-8179-6D86EB835783@gmail.com> <7d7b2541-c5b2-dbfc-e503-36fffc6fabeb@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PCt3DDf7I8wE7N4o6AAeq3vLk7c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 06 Nov 2019 17:49:09 -0000


> On Nov 6, 2019, at 9:52 AM, Keith Moore <moore@network-heretics.com> wrote:
> 
> On 11/6/19 6:03 AM, Ralph Droms wrote:
> 
>> We shouldn't be depending on last-minute quality checks to maintain the quality of our output.  Working groups should be producing documents that are ready to publish, and develop trust that their documents are high quality.
> 
> As long as working groups are as siloed as they are, this is unlikely any WG that affects interests that are outside of its narrow scope.   And it's very dangerous to assume that WGs are competent to produce high quality work in isolation at least with our current processes.   Though I'd certainly be in favor of some kind of explicit extra-WG review earlier in a WG's or document's lifespan.
> 

I have to agree here.  There’s things that happen where some better cross-area would be useful, but we also face the fact that with a growing community it’s not possible to have all the implications in mind.  A subtle change in one area with one protocol or how that transport happens may have ops impact for the protocol.

A great example is that the large providers are often well represented but people who are still building services themselves just end up dealing with the changes vs having the bandwidth to participate with people whose full time job it is to e-mail the lists.

The subject line of this is also possibly quite problematic as it may be about one or more ADs today or just an abstract problem.  We should be cautious to not have this turn into painting the aircraft carriers bike shed while it turns lest we go overboard. :-)

- Jared