Re: Want to be on the IESG?

John C Klensin <john-ietf@jck.com> Tue, 09 November 2021 03:18 UTC

Return-Path: <john-ietf@jck.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 E8E973A041C for <ietf@ietfa.amsl.com>; Mon, 8 Nov 2021 19:18:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 hIaZPj_PhFR3 for <ietf@ietfa.amsl.com>; Mon, 8 Nov 2021 19:18:51 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A8203A05AC for <ietf@ietf.org>; Mon, 8 Nov 2021 19:18:50 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1mkHeo-000LF1-AF; Mon, 08 Nov 2021 22:18:46 -0500
Date: Mon, 08 Nov 2021 22:18:39 -0500
From: John C Klensin <john-ietf@jck.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, "Salz, Rich" <rsalz@akamai.com>
cc: IETF list <ietf@ietf.org>
Subject: Re: Want to be on the IESG?
Message-ID: <477FE490C6DF896A3AC338E3@PSB>
In-Reply-To: <CAKKJt-eLdBB10+uEgGWgazVOiwXZqQNnbCZ5SF3kmu0WVKtGCA@mail.gmail.com>
References: <2A8C8B98-CBA9-4BF0-82C5-594B0F309F07@akamai.com> <FA5A7C084BDEF72CE3FC510B@PSB> <CAKKJt-cMk74Da1EiESaJN3+LC+pg-212sYyZjcNgd5Pr-HFB-A@mail.gmail.com> <51D62E71-A33F-4D27-8633-9BB9ACFA536C@akamai.com> <CAKKJt-eLdBB10+uEgGWgazVOiwXZqQNnbCZ5SF3kmu0WVKtGCA@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3FjHZnKdzs8dkWX6f83W9zTeiU0>
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: Tue, 09 Nov 2021 03:18:56 -0000


--On Monday, November 8, 2021 09:23 -0600 Spencer Dawkins at
IETF <spencerdawkins.ietf@gmail.com> wrote:

> Hi, Rich,
> 
> On Mon, Nov 8, 2021 at 8:43 AM Salz, Rich <rsalz@akamai.com>
> wrote:
> 
>> 
>>    - And I still think evaluating incumbents, especially on
>>    the IESG, was a good idea, then, and now.
>> 
>> 
>> 
>> Did you have any specifics in mind?
>> 
> 
> I'd start by looking at
> https://www.ietf.org/archive/id/draft-klensin-nomcom-incumbent
> s-first-01.tx
> <https://www.ietf.org/archive/id/draft-klensin-nomcom-incumben
> ts-first-01.txt>t, and figuring out what needs to be updated.

Or at draft-klensin-nomcom-term-02
(<https://datatracker.ietf.org/doc/draft-klensin-nomcom-term/>)
-- the version discussed during gendispatch -- to see what I
botched in the update, because things have changed, because the
ideas were not fully baked the first time around, or because I
was just in too much of a hurry.

   john