Re: [Rfced-future] [IAB] Welcome to the RFC Editor Future Development Program

John C Klensin <john-ietf@jck.com> Wed, 01 April 2020 17:47 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2B6B3A148C; Wed, 1 Apr 2020 10:47:08 -0700 (PDT)
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=unavailable 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 XaLgmkmX1DpY; Wed, 1 Apr 2020 10:47:07 -0700 (PDT)
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 6D8823A1488; Wed, 1 Apr 2020 10:47:07 -0700 (PDT)
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 1jJhSB-00028y-GQ; Wed, 01 Apr 2020 13:47:03 -0400
Date: Wed, 01 Apr 2020 13:46:57 -0400
From: John C Klensin <john-ietf@jck.com>
To: Jari Arkko <jari.arkko@piuha.net>, Eliot Lear <lear=40cisco.com@dmarc.ietf.org>
cc: rfced-future@iab.org, IAB <iab@iab.org>
Message-ID: <4C3D0687FFB29333C9ED2F64@PSB>
In-Reply-To: <6C53846B-21A4-41E2-AA5F-4E9EA2FB27BB@piuha.net>
References: <97B63B78-0D49-4007-B8A2-101FB7849C0F@cisco.com> <CAA=duU0_pr_56HTR5vZg+AK981rkvGrMGFFi-UHgW4L=6=6mwg@mail.gmail.com> <D6A290EE-72E5-46A7-BA25-085CC2AAE35C@cisco.com> <0E6D83F8D11D8C1B9B7237B7@PSB> <73C27FFD-BD81-4CF3-9D9D-845DE9544A36@cisco.com> <097a60d7-2229-b849-1ca3-1f6d298cceed@nthpermutation.com> <yblpncthb1n.fsf@w7.hardakers.net> <ad40f5c1-5551-3e3e-9bc3-164ec3368b68@gmail.com> <16726C73-09AB-4F61-8C00-8224E3EF6F1B@mnot.net> <E9B2BFA7-4EFE-4608-AB00-42B46C4503E7@cisco.com> <6C53846B-21A4-41E2-AA5F-4E9EA2FB27BB@piuha.net>
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/rfced-future/nrt6ONQ1jFqc5iy3dJkKndnqF1Q>
Subject: Re: [Rfced-future] [IAB] Welcome to the RFC Editor Future Development Program
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2020 17:47:09 -0000

--On Wednesday, April 1, 2020 00:11 +0300 Jari Arkko
<jari.arkko@piuha.net> wrote:

>> Should the program worry about the structure of the series or
>> should the program worry about putting in place someone who
>> could lead the community in worrying about the structure of
>> the series (among other things)?  

> Definitely the latter.

Jari,

I think it is not as simple as the dichotomy in Eliot's question
implies. 

I'd like to assume, perhaps incorrectly, that the "among other
things" in that question implies the kind of expertise in
publications and editorial strategy that were part of Heather's
job description.   If that is true, then getting such a person
in place is going to require a job description that is
sufficiently specific to allow recruiting the type of person we
want (and excluding others).  Stephen's comment about the
relationship to the RPC is actually a good example of that.
I'll respond to that suggestions separately to keep this one
from becoming long, but the answer, one way or the other,
changes the RSE role significantly enough to probably make some
people qualified under one conclusion and others qualified under
either.  Of course we could write a job description that said
"well, maybe this will change and be added or deleted from the
job", but my experience, including with people with whom we
discussed the job that was ultimately given to Heather, is such
as statement will cause otherwise-qualified possible applicants
to decide it is not a job that they want.

On the other hand, if the only role we care about is to "lead
the community in worrying...", then almost anyone in the IETF
with a history (and wide community recognition and respect) of
being able to lead efforts, foster consensus, and stay
personally balanced on the issues rather than, even
unintentionally, trying to drive conclusions one way or the
other could do the job -- no specialized technical publications
strategy background required.  As an obvious example, you would
be excellent if you were willing to take it on and had the time.


The other problem, of course, is that going very far in that
direction might mean we wouldn't have an RSE in place until the
middle of 2021, if we concluded we need an RSE at all.

best,
   john