Re: RFC Series Editor (RSE) Statement of Work

Michael StJohns <mstjohns@comcast.net> Wed, 17 July 2019 16:18 UTC

Return-Path: <mstjohns@comcast.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 ACD60120771 for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2019 09:18:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=comcast.net
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 hq9yaPe04dbr for <ietf@ietfa.amsl.com>; Wed, 17 Jul 2019 09:18:15 -0700 (PDT)
Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C318212068A for <ietf@ietf.org>; Wed, 17 Jul 2019 09:18:15 -0700 (PDT)
Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-09v.sys.comcast.net with ESMTP id nk4OhgHDPViXOnmdDh47CH; Wed, 17 Jul 2019 16:18:15 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1563380295; bh=eP19k4OCtcRtjHmdVvkJn8QUKMScQyesvW8mHbamZ8k=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=qHEzvO18l8BhCPjINGKroZwI8ejGk0Zk1X1xIccxvWSsCGd8n2Lgd7k9SfdR8W8E4 BwiQC145Alk7NFJMUCi1Humdtfhv9svBXTU0R6CdgFF6hnLaldx6nkgR9sb57XrjFD nwkHAVMUvA4uWrEytcNH+MO/qLI8N4T0cfaHmojg2I7HjYQLT8l+It8X0F6udPFPrL pl6AiFv2n22YelM0n16OYvP7xPK89X6MJMkeoy6IFj2w4LSg2o7YSsHStlPF0v2PGh p2MQBgCUvkDO9sF9qJ0eiHLGuBIMraVJPqMw+1R6qrlUuv9LWKgBG797BEgudBBBJF oDIDvwFiugkkA==
Received: from [IPv6:2601:152:4400:437c:a5c4:55c:1b4f:568c] ([IPv6:2601:152:4400:437c:a5c4:55c:1b4f:568c]) by resomta-ch2-05v.sys.comcast.net with ESMTPSA id nmdBhXNUU73WtnmdCh5TQb; Wed, 17 Jul 2019 16:18:14 +0000
X-Xfinity-VMeta: sc=0;st=legit
Subject: Re: RFC Series Editor (RSE) Statement of Work
To: ietf@ietf.org
References: <9817BB4B-D828-4128-A70C-A8B966E6642F@encrypted.net> <429ed9b6-89ab-8530-b898-e72e04e37171@mnt.se> <66B08F82-E1F7-4525-89D3-60CCC1B975F7@akamai.com> <DBC2F5CA-0B23-4B2C-9618-15025C39E609@encrypted.net> <BD77100D-3331-42FE-85B2-548E5D5BCB1B@vpnc.org> <CACOFP=hAveH4GzaAVYmER8zhBZowCg2KO+LRnoEernCAqbYg3w@mail.gmail.com> <FE97934D2FBF1FB5488F0CD7@PSB>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <0607512b-35e7-91b6-6421-15752924070e@comcast.net>
Date: Wed, 17 Jul 2019 12:18:11 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <FE97934D2FBF1FB5488F0CD7@PSB>
Content-Type: multipart/alternative; boundary="------------09378F4348CE146C3FCF207A"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IcMYYdw8jL7jW9VhtHeFgsTG3zg>
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, 17 Jul 2019 16:18:18 -0000

Hi - John's note makes a lot of different very good points, and he does 
note that some could be made on one of the other threads.  I've 
extracted a few points that are particularly germane to the SOW thread 
primarily for emphasis and added ellipsis to shrink some of those 
hopefully without changing meaning.  I recommend all of you read John's 
original post - but if you don't have the time, this at least attempts 
to pull out points that frame the role of the RSE and the depth of the 
problem we're going to have finding a new one.

Mike


On 7/16/2019 10:38 AM, John C Klensin wrote:
>
>  *
>     Unless "we" are trying to make changes in how the RFC Editor
>     Function works that go far beyond what is (or is not) in what is
>     in the draft SOW, there have been several misconceptions in this
>     thread and the related ones.
>
>  *
>     This is not a
>     copy-editing role.  it is not even a technical editing role.
>
>  *
>     Instead, this is a strategic leadership and management role.  In
>     retrospect, maybe we would have less confusion about, e.g., copy
>     editing, if we had called the position "RFC Series Publisher"
>     when we made up the "RSE" title, but, given how few people seem
>     to understand what a publisher actually does, maybe it would
>     have made no difference.
>
>  *
>     If the RSOC and IAB are looking for someone who will quietly do
>     the job, follow their lead about strategy directions, and not
>     try to educate (and, if necessary, push back based on greater
>     specialist expertise, then they are making a really fundamental
>     change in the role.
>
>  *
>     Something Nevil didn't mention was that plausible candidates
>     were not easy to find, even with no incumbent to compete
>     against.
>
>  *
>     Unless we are making significant changes to the role, the RSE
>     should probably be seen as less even responsible to the IAB and
>     RSOC on day to day details than the IETF LLC Executive Director
>     is to the LLC Board.
>
>  *
>       For a position like this, even describing the
>     position search a and process as a "bid" is offensive and likely
>     to convince some people we would like to have as candidates to
>     say "they either don't understand what they are doing or are not
>     interested in anyone like me" and then move on.
>
>   * Olaf obviously had a great deal of IETF experience....However,he
>     did not ... have the
>     depth of technical and standards publishing,and publishing
>     strategy, experience ... I think it was very important ... that he
>     did have an RSOC that contained multiple people with at least
>     significant pieces of those types of experience. That RSOC saw its
>     missionmuch more in terms of supporting him and helping him
>     succeed in the role -- including giving advise on the strategic
>     publication issues to which he was happy to listen-- than as
>     "oversight" or supervision or evaluation of contractual compliance.
>
>  *
>     More generally, putting someone into the RSE role --either
>     "acting" or semi-permanently -- who has good community
>     experience and relationships, little or no strategic publication
>     leadership perspective and experience, and without the support
>     of in-depth expertise in the RSOC (or some other arrangement to
>     which a supportive RSOC is prepared to defer in matters of
>     expertise) is a recipe for disaster... or at least major changes
>     in the character of the Series whether intentional or not and
>     whether reflecting community consensus or not.
>
>