IETF Logo Mail Archive

Re: NomCom 2019 Call for Community Feedback

Kyle Rose <krose@krose.org> Mon, 04 November 2019 22:56 UTC

Return-Path: <krose@krose.org>
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 7F1631208A6 for <ietf@ietfa.amsl.com>; Mon, 4 Nov 2019 14:56:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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 (1024-bit key) header.d=krose.org
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 ZpDlMyqrTCuM for <ietf@ietfa.amsl.com>; Mon, 4 Nov 2019 14:56:09 -0800 (PST)
Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) (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 20A211208DF for <ietf@ietf.org>; Mon, 4 Nov 2019 14:56:09 -0800 (PST)
Received: by mail-yb1-xb2b.google.com with SMTP id b2so8581607ybr.8 for <ietf@ietf.org>; Mon, 04 Nov 2019 14:56:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nQkl4u6L+s/u9980dPzKNIz8kSCOTPkbsReEEZ9Du6g=; b=mfgHW+GrMc3su+uegbWcRgkXfeq8Rd7whQtr2vgohiaF2SvpucUIatX2iGjxPKibRS BwO7d65mflRk52r4Jm/I75VOph4fyc7LQ9AXtYl7r0to+e+MptHWFf7zXzOAJtOtcyHk ixVTL57sjEI5v9yNdEUhZkzp88H4UVPJklxrI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nQkl4u6L+s/u9980dPzKNIz8kSCOTPkbsReEEZ9Du6g=; b=ewbEv4gm+JSO9Z6qu8Cyd9fYHdGUtXvOBdYW8sHWcsuwGZYgWrm0gofyQmAJa6rVT5 zxrBg6whP3gAtha6Ymkl99kQsSLSdNdtxBj00gjNFqQBHXfK5epWLhO8Pl70k8YYNVnh U6QEmSF2fSfd6J6pnbt3ntC/BcZF15b9pWvlbBC6oPE/iuuIpZJxVmHk21ikOsmmR6HC MrErwM2jPMHEx3a612i9DhiuGOb01LJqGx6Dz4Sem3u0f7yp0YbkoZx6i0CeaLA9PIXP Iz2/KKl7WZEvHeTjXlbion4nmLBVgla/9UUuv90zWS8ErsTbO60xfg7+DSpfvTY5vf+1 KswQ==
X-Gm-Message-State: APjAAAVTMrnKie34rOevvo35u1oj8kktpki9ZpsyLxp2ellXWZTnsZd0 PYVE7l214rC3NNdcwLwKUE+jyTt531vcAo2QoB2HxQ==
X-Google-Smtp-Source: APXvYqyyhwbDX4mZzjOhZ+ZpOCSsQw5SBgnACjg9wbmRe+DK9I2Q/eZ1T2BeVZkJSYdOFULb1Oss8Vrj4758RkPhj8M=
X-Received: by 2002:a25:d14f:: with SMTP id i76mr11429150ybg.247.1572908167882; Mon, 04 Nov 2019 14:56:07 -0800 (PST)
MIME-Version: 1.0
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>
In-Reply-To: <09886edb-4302-b309-9eaa-f016c4487128@gmail.com>
From: Kyle Rose <krose@krose.org>
Date: Mon, 04 Nov 2019 17:55:56 -0500
Message-ID: <CAJU8_nXOKrf80Q1JjGUBMy2e_+kjE6HrUQekUyaJ8yYYqQ-FdQ@mail.gmail.com>
Subject: Re: NomCom 2019 Call for Community Feedback
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: "Salz, Rich" <rsalz@akamai.com>, "Livingood, Jason" <Jason_Livingood@comcast.com>, Paul Wouters <paul@nohats.ca>, "nomcom-chair-2019@ietf.org" <nomcom-chair-2019@ietf.org>, ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009c80c305968d3845"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/72xMRxgqWLjudGDkEm9GkQwQpMg>
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: Mon, 04 Nov 2019 22:56:19 -0000

On Mon, Nov 4, 2019 at 4:29 PM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> If we want the IESG job to be more reasonably sized, we have to take work
> away from the ADs. As far as I can see, that means taking away their duty
> of acting as final reviewers. I don't want to name names because I don't
> think the ADs are to be blamed individually, but some of them spend
> *enormous* effort on detailed reviews. Either we have to trust the WGs
> more, or we have to trust the various review teams more, and allow the IESG
> to steer, which its name implies is its main job. And sign off on drafts
> that are good enough, rather than seeking perfection.
>

Agreed, and with Stephen's advocacy of delegation as a path forward. But to
get there, the IETF (and the folks with dots, in particular) need to become
more comfortable with the idea of decentralizing authority to a greater
degree than they have been used to: that means empowering---and trusting,
and training, and reviewing the output of---the directorates to a greater
extent than happens today. The buck may still stop with the ADs, but they
should be willing and able to choose to delegate to a greater degree,
preserving their time and brain cycles for the truly critical stuff that
they either seek out or that is escalated to them.

We may also want to take a serious look at re-empowering the IAB's
historical role in architectural oversight, with an appropriate set of
checks and balances to prevent a recurrence of the kerfuffle that resulted
in the current structure.

Kyle

v2.23.0 | Report a Bug | By Email