Re: Things that used to be clear (was Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)

Ted Lemon <mellon@fugue.com> Fri, 05 July 2019 17:06 UTC

Return-Path: <mellon@fugue.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 9AE6712009E for <ietf@ietfa.amsl.com>; Fri, 5 Jul 2019 10:06:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 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_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 1WdW1HAgm9wb for <ietf@ietfa.amsl.com>; Fri, 5 Jul 2019 10:06:03 -0700 (PDT)
Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (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 430A2120189 for <ietf@ietf.org>; Fri, 5 Jul 2019 10:02:22 -0700 (PDT)
Received: by mail-qk1-x732.google.com with SMTP id t8so8392943qkt.1 for <ietf@ietf.org>; Fri, 05 Jul 2019 10:02:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=TJsFAzm/VBSBqQa6//QnWoLaD/GyDGS/HyEzQrK25UY=; b=gT1KUAtA+v1/Du5mVQLSqJWyicD3m+h/vonG/+AaaET2lw2S94Hm9UdeKrbTPSj9Ca eU28rIQdJYMZML4Fao4UCrTgiXYrN6Z9NSDMIPf/2gmJm6qG5PDihxF7sR87j21gYUgG kRS0uO7eHeL7f3U03IFndNtQor/xzMerSlRkKY6hMBffsXy2FGNIp8xgY0RCUMhxTLY8 cC1SUFEfGBOP1yfylqdZRofJsSk7iwNXx//yinzSffmb/+OqNZY9Y/Es98XnJeVY2y+H 30IBXUZY/Uav74Sl+YFzhAMTnqATOlfFUGhqnn7PXx98CEg12kk8qq6X+AnlETHP+uYF NTKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=TJsFAzm/VBSBqQa6//QnWoLaD/GyDGS/HyEzQrK25UY=; b=LKjgm+KvgXu0tzOMXbkbNLNCA/8Lic77Dek/PhDrWTf9YhlZY3LxDomVPomjEzOsYF AOg4D1MoAUybiMPIPJcwf9N7iGxqXf3LGoFVw+4NeHxK1+37bV+lRnusvs8YegXq+7hj KpIHyKL3pxbizDIrqgvp+Ok30+vsm48LHhmDbqRss58AyDW+6VJu6UwNALYo6H2d/V6P q8QHvDkZBOtvlbClH2q/pV3aAsEtaWjBE0iqdDEBixfgRiEi7F4WctnQTMxeUea46T/9 ESJ3KYApvxbYf/8m3pCLyEthH3mQJF4tCxXCWf/BPZocMIL6Fzmm0Lo4u2eeEh5fFo9e 5VhQ==
X-Gm-Message-State: APjAAAUXC41PjIocIVbdLiGk8IZR5+EvBqLU7kEx4mDFLsGsMCeWh9vX LcGfgKC2b9clbIXflVgD2nDajz3H4Ko=
X-Google-Smtp-Source: APXvYqyi5dDr8FT6KEeOHwPnbMXeKhTllkWul8wr4IG+2lft6Zaur8MMSPXBfYASVazuurCEldmwcQ==
X-Received: by 2002:a05:620a:1443:: with SMTP id i3mr4084576qkl.11.1562346141376; Fri, 05 Jul 2019 10:02:21 -0700 (PDT)
Received: from ?IPv6:2001:470:c1a2:1:1898:c480:1567:a6a6? ([2001:470:c1a2:1:1898:c480:1567:a6a6]) by smtp.gmail.com with ESMTPSA id e18sm3845088qkm.49.2019.07.05.10.02.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 Jul 2019 10:02:20 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <E49856E1-4DBC-488E-AE15-D48B5357E61D@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E5DC5F2C-E2C8-43C3-837E-A702BF81376D"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Things that used to be clear (was Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)
Date: Fri, 05 Jul 2019 13:02:18 -0400
In-Reply-To: <20190705163101.GJ3508@localhost>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, IETF discussion list <ietf@ietf.org>
To: Nico Williams <nico@cryptonector.com>
References: <796c1f6c-cd67-2cd5-9a98-9059a0e516f8@network-heretics.com> <20190704013009.dlifopcbm2umnqo7@mx4.yitter.info> <b18809df-ee98-fb29-b6c4-04ed579e163a@network-heretics.com> <20190704052335.GF3508@localhost> <CABcZeBOw6w2tm4YYFdmLwC23ufPDupt2D1Vzwjn4Pi9bbf6R-w@mail.gmail.com> <20190704192057.GI3508@localhost> <CABcZeBMC-VRfea3YqLSs6yhtEq4VtfdO5L56v87KH=vMR4y=+A@mail.gmail.com> <5c9048ef-ba2b-a362-3941-82eacc664b64@mnt.se> <CABcZeBPv8xUMbSt+SDL_X56SBB_CPyBMKZaQMbPd=6M-xT+hpQ@mail.gmail.com> <19233.1562339969@localhost> <20190705163101.GJ3508@localhost>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OgXnrHgq5AFBGUkELTN363ePbrg>
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: Fri, 05 Jul 2019 17:06:07 -0000

On Jul 5, 2019, at 12:31 PM, Nico Williams <nico@cryptonector.com> wrote:
> At IETF we have commitment reviews, naturally, but we only have
> inception reviews for WGs and their initial work items, but no inception
> reviews for subsequent work items, and no interim reviews.

Isn’t a call for adoption an inception review?   If not, it should be.

We actually kind of suck at commitment reviews, in a lot of cases: the work is done, after all, and everybody who thought it was a good idea at adoption time is tired of looking at it.   So it’s not uncommon (and I’ve seen it on documents I’ve finished) that the document is done and polished, and then there’s no response at all to the WGLC.

From a process perspective, I actually consider “adopted -> completed + no objection” to mean that there is WG consensus to publish, because otherwise this phenomenon can easily kill a completed document.   But this is also a process failure in the sense that commitment reviews are important.

The problem the IETF has is that unlike at your former job, there is no way to enforce this process other than by killing documents, and that often only impacts the people who are working on them and the people who would benefit from publication, and not all the people who thought it was a good idea at adoption time, but have wandered off during the course of the work.