IETF Logo Mail Archive

Re: RFC Series Editor (RSE) Statement of Work

"Paul Hoffman" <paul.hoffman@vpnc.org> Mon, 15 July 2019 17:06 UTC

Return-Path: <paul.hoffman@vpnc.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 D9D9512023D; Mon, 15 Jul 2019 10:06:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 EqpvNTgCCovq; Mon, 15 Jul 2019 10:06:29 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 6608E12023F; Mon, 15 Jul 2019 10:06:29 -0700 (PDT)
Received: from [10.32.60.59] (50-1-99-176.dsl.dynamic.fusionbroadband.com [50.1.99.176]) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id x6FH6Tm5026337 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 15 Jul 2019 10:06:30 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-99-176.dsl.dynamic.fusionbroadband.com [50.1.99.176] claimed to be [10.32.60.59]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: Sarah Banks <sbanks@encrypted.net>
Cc: ietf@ietf.org, rsoc@iab.org
Subject: Re: RFC Series Editor (RSE) Statement of Work
Date: Mon, 15 Jul 2019 10:06:22 -0700
X-Mailer: MailMate (1.12.5r5635)
Message-ID: <BD77100D-3331-42FE-85B2-548E5D5BCB1B@vpnc.org>
In-Reply-To: <DBC2F5CA-0B23-4B2C-9618-15025C39E609@encrypted.net>
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>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gjlkIfFxzN9Ww9fTxh4S5aY2xGk>
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, 15 Jul 2019 17:06:31 -0000

On 15 Jul 2019, at 9:47, Sarah Banks wrote:

> This isn't a "yes/no" comment, but rather, a bit of colour - I think 
> requiring the experience with having written an RFC means the 
> candidate would have been through the process previously and hence, 
> has some experience with it.

Heather Flanagan did not have RFC writing experience before she became 
the RSE. Thus, the one data point we have speaks against this as even a 
desirable skill.

> Also, it's not a requirement, just a desirable skill :)

Then the SOW needs to be revised. "Experience as an RFC author desired" 
is listed in a section called "EDUCATION AND EXPERIENCE REQUIRED:". In 
fact, three of the five bullets in that section, and the first bullet of 
the next section, confuse "desired" and "required".

--Paul Hoffman

v2.23.0 | Report a Bug | By Email