Re: RSE Bid Process

S Moonesamy <sm+ietf@elandsys.com> Sun, 14 July 2019 21:43 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 13290120187; Sun, 14 Jul 2019 14:43:20 -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=c3EPhPRS; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=RNyHc/rQ
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 hla8KNN_wTco; Sun, 14 Jul 2019 14:43:18 -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 BE0FB12015D; Sun, 14 Jul 2019 14:43:18 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.129.22]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x6ELgxjW022690 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 14 Jul 2019 14:43:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1563140594; x=1563226994; bh=zIWnI6b5JouOLqtO4x0YhN1AM9PZleyk4ktBZ7LplHk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=c3EPhPRSQdVXqslzyVT98Syhl/kWlr0jpLBgLyII656kYdMQfbp/3oPer42BsBhqf zDbLtPkT1ccQ5j0UEb7FdxyUwWurSb3TLt4GRLSFm30YQc7Tvx39ljLoP61Xq/i6Z9 a4mnJM7R/w4psUpaahWB25BNC7HnP49lN29oWrB0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1563140594; x=1563226994; i=@elandsys.com; bh=zIWnI6b5JouOLqtO4x0YhN1AM9PZleyk4ktBZ7LplHk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=RNyHc/rQRv4PeDOiYbqgfCH2xnvP7M/3t2bmsTqipsaEuSVUXBi/wJe71ZFYpuOaj bBIEJdyDKfywYuAkGNVf3r3WQzsz8ZGfDVX2bwnrW+MtBg7uwvYnAOHCmksTYZ1BUj k5RpgKcFalW+llslFx7Wdmz6UPmLJashuCzjRzgo=
Message-Id: <6.2.5.6.2.20190714124531.0cc0fa40@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 14 Jul 2019 14:23:39 -0700
To: Ted Hardie <ted.ietf@gmail.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: RSE Bid Process
Cc: Internet Architecture Board <iab@iab.org>, rsoc@iab.org
In-Reply-To: <CA+9kkMAbvAdmFAkm5UnsmqWd51KEbFmSE=Jx2pXGUboEm-VYtA@mail.g mail.com>
References: <CA+9kkMALnyeoMJKOgwZ8QP1G+aeSTSBbu4HXAAxdyhcC0K=mDA@mail.gmail.com> <6.2.5.6.2.20190713065007.0c09c018@elandnews.com> <CA+9kkMAbvAdmFAkm5UnsmqWd51KEbFmSE=Jx2pXGUboEm-VYtA@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/X5yWIN1F8kX_e2cRi4PdkvjW8pk>
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: Sun, 14 Jul 2019 21:43:20 -0000

Hi Ted,
At 12:08 PM 14-07-2019, Ted Hardie wrote:
>Thanks for your comment.  You are correct that the SOW does contain 
>this text: "Section 2.1.5 (Workload) of RFC6635 is not applicable to 
>this Statement of Work." and that the RSOC does not conduct a yearly 
>performance review as called for in section 3.1 of 6635. This 
>latter, as you may recall, is because ISOC's human resources folks 
>pointed out that this was how you reviewed employees, rather than 
>the output of a contract.  The text cited above also discusses the 
>position in terms of employee hours rather than output.

I don't remember when the performance review issue was first 
identified.  Anyway, I would look at it in terms of whether the model 
is aligned which what actually happens while excluding the legal aspects [1].

>Addressing this along with other issues, should be part of any 
>update to the RFC Editor

I did a quick comparison of RFC 6635 and 
draft-ietf-iasa2-rfc6635bis-03.  Section 2.1.5 and Section 3.1 are 
similar except for minor changes.

>model.  A key question now is whether we conduct the hiring 
>according to a slightly
>modified SOW and have the new incumbent participate in the larger 
>discussion or conduct the discussion prior to recruiting a new 
>RSE.  The first strategy seems to be permitted by RFC 6635 under the 
>general rubric of the RSE's role in evolving the series.  The second 
>is also possible, but the result will likely be that there is no 
>overlap between a new incumbent and Heather.

One of the alternatives (if I understood correctly) is to have an 
overlap to ensure a smooth transition between the current RSE and the 
new RSE.  That also impacts on whether the larger discussion should 
happen now or next year.  My preference is to have the larger 
discussion now.  There would probably have to be a transition plan in 
parallel.

Regards,
S. Moonesamy

1. That could be discussed outside a RFC if anyone is interested in it.