IETF Logo Mail Archive

Re: [Rsoc] RFC Series Editor (RSE) Statement of Work

Sarah Banks <sbanks@encrypted.net> Tue, 23 July 2019 00:18 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 2EA251200BA for <ietf@ietfa.amsl.com>; Mon, 22 Jul 2019 17:18:47 -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=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 h2RYzAAaSoDT for <ietf@ietfa.amsl.com>; Mon, 22 Jul 2019 17:18:45 -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 4AA0712008F for <ietf@ietf.org>; Mon, 22 Jul 2019 17:18:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by aws.hosed.org (Postfix) with ESMTP id 87FA78001B; Mon, 22 Jul 2019 20:18:44 -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 S8vvUHlFBzLY; Mon, 22 Jul 2019 20:18:44 -0400 (EDT)
Received: from [10.22.252.34] (mobile-107-92-59-43.mycingular.net [107.92.59.43]) by aws.hosed.org (Postfix) with ESMTPSA id 4322B8001A; Mon, 22 Jul 2019 20:18:44 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
Subject: Re: [Rsoc] RFC Series Editor (RSE) Statement of Work
From: Sarah Banks <sbanks@encrypted.net>
X-Mailer: iPhone Mail (16F203)
In-Reply-To: <6.2.5.6.2.20190722140432.13b71028@elandnews.com>
Date: Mon, 22 Jul 2019 20:18:42 -0400
Cc: Richard Barnes <rlb@ipv.sx>, ietf@ietf.org, rsoc@iab.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <577569C8-284F-4232-AF50-DD6F07F92EA2@encrypted.net>
References: <9817BB4B-D828-4128-A70C-A8B966E6642F@encrypted.net> <CAL02cgRcGF80R_h5it_u7eGQrMjavpZ6_noEKb5vY5i1HqJYaA@mail.gmail.com> <7e82f47a-6a1d-8d3e-b183-e5159a071481@gmail.com> <9f7e969e-0374-2f9f-4ec6-e2d85a2fb819@gmail.com> <CAL02cgSj4VcKsxawO140yNqAEtk==-Ek9=kvntvTb401BRrhYQ@mail.gmail.com> <6.2.5.6.2.20190722140432.13b71028@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lJ1E0KbCGZYtD8k0a460YiF3dVc>
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, 23 Jul 2019 00:18:47 -0000

Hi,
   Considering the vast amount of email that I’ve been swimming in, it seems I missed an email. I could go searching, but to expedite, help me understand what your ask was for, again?

Thanks
Sarah

> On Jul 22, 2019, at 6:29 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:
> 
> Hi Richard,
> At 06:56 AM 22-07-2019, Richard Barnes wrote:
>> Sorry to be so horribly prosaic, but I have some practical questions...
> 
> [snip]
> 
>> How should this search committee make its decision?  Do you envision them working from some sort of job description, or just "I know it when I see it"?
> 
> If I am not mistaken, there is usually a description for this type of search.  I am not sure whether there would be agreement on identifying and approaching people who might fit in the position [1] instead of only advertising the position.
> 
> RSOC did not respond to my request for information.  As a response to the last question in your email, that approach might not be practical for a search committee.
> 
> Regards,
> S. Moonesamy
> 
> 1.  I used the word "position" to keep it simple. 
> _______________________________________________
> Rsoc mailing list
> Rsoc@iab.org
> https://www.iab.org/mailman/listinfo/rsoc

v2.23.0 | Report a Bug | By Email