IETF Logo Mail Archive

Re: RFC Series Editor (RSE) Statement of Work

S Moonesamy <sm+ietf@elandsys.com> Mon, 22 July 2019 22:30 UTC

Return-Path: <sm@elandsys.com>
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 81245120094; Mon, 22 Jul 2019 15:30:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=YczvBvnp; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=JFIC+Bpd
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 kFhsBjD00Sdg; Mon, 22 Jul 2019 15:30:23 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B03212006B; Mon, 22 Jul 2019 15:30:23 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.179.13]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x6MMUAMJ022576 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Jul 2019 15:30:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1563834622; x=1563921022; bh=aLbQWfYJPJZUsyQuL/PdVRtMRa/GP/Ezrrg6Ufo+nbc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=YczvBvnpE6h2RJi3oOR3yFEcWdYpyyGLV/H7itwU2xHOCimjmFkGgDA3FZ32WGRvT MkFEHXFnoGRXR8GMKkzE/zH9S5kHbtP2Y9UusL1ThZA3DmXAJaO0mMVi8kkqO1Q8/G u+rG+cx5+DxlzsJRS7d9iW46xYH3SZoMUU6fvja8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1563834622; x=1563921022; i=@elandsys.com; bh=aLbQWfYJPJZUsyQuL/PdVRtMRa/GP/Ezrrg6Ufo+nbc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=JFIC+Bpd4pEfK1s/t3sxVwIlfvmkUzOAuxChs5ZaSeu/AJaKBtmY7PSxIjoTjDyKI KgXzatIt/EZxNPjZ88jqfXJgeTo4+KKKFAItnOPKxvUOm2oBgsbXDxLTS9iXeU2zJp 2/n3XXj/Ma1pEQd8l72536yrK/xwtxOBO2KOu+eg=
Message-Id: <6.2.5.6.2.20190722140432.13b71028@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 22 Jul 2019 15:29:27 -0700
To: Richard Barnes <rlb@ipv.sx>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: RFC Series Editor (RSE) Statement of Work
Cc: rsoc@iab.org
In-Reply-To: <CAL02cgSj4VcKsxawO140yNqAEtk==-Ek9=kvntvTb401BRrhYQ@mail.g mail.com>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tXNh-1TXETbkG884r0E5zML0M3M>
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, 22 Jul 2019 22:30:25 -0000

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.

v2.23.0 | Report a Bug | By Email