IETF Logo Mail Archive

Re: RFC Series Editor (RSE) Statement of Work

Sarah Banks <sbanks@encrypted.net> Mon, 15 July 2019 16:47 UTC

Return-Path: <sbanks@encrypted.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 A9B08120147 for <ietf@ietfa.amsl.com>; Mon, 15 Jul 2019 09:47:39 -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=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 dl5Cy325cjWG for <ietf@ietfa.amsl.com>; Mon, 15 Jul 2019 09:47:38 -0700 (PDT)
Received: from aws.hosed.org (aws.hosed.org [50.16.104.137]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2767012017C for <ietf@ietf.org>; Mon, 15 Jul 2019 09:47:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by aws.hosed.org (Postfix) with ESMTP id 67C8A8001C; Mon, 15 Jul 2019 12:47:36 -0400 (EDT)
X-Virus-Scanned: Debian amavisd-new at aws.hosed.org
Received: from aws.hosed.org ([127.0.0.1]) by localhost (aws.hosed.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mABu9ywNa-sL; Mon, 15 Jul 2019 12:47:36 -0400 (EDT)
Received: from [192.168.1.211] (corelight.static.monkeybrains.net [208.90.215.182]) by aws.hosed.org (Postfix) with ESMTPSA id A25F08001B; Mon, 15 Jul 2019 12:47:33 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: RFC Series Editor (RSE) Statement of Work
From: Sarah Banks <sbanks@encrypted.net>
In-Reply-To: <66B08F82-E1F7-4525-89D3-60CCC1B975F7@akamai.com>
Date: Mon, 15 Jul 2019 09:47:32 -0700
Cc: Leif Johansson <leifj@mnt.se>, "ietf@ietf.org" <ietf@ietf.org>, "rsoc@iab.org" <rsoc@iab.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <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>
To: "Salz, Rich" <rsalz@akamai.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/m9pR2Gu_08rx_4yeTIa8dLCpMZI>
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 16:47:40 -0000

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. Also, it's not a requirement, just a desirable skill :)

/S

> On Jul 15, 2019, at 9:39 AM, Salz, Rich <rsalz@akamai.com> wrote:
> 
>>   I don't think its a good idea to include "experience as an RFC author"
> 
> Strongly agree.  We want a good technical copy-editor, which strikes almost all RFC authors from consideration, IMO.
>

v2.23.0 | Report a Bug | By Email