Re: RSE Bid Process
Ted Hardie <ted.ietf@gmail.com> Sun, 14 July 2019 19:07 UTC
Return-Path: <ted.ietf@gmail.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 D30A412015F for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2019 12:07:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 PbEL9sss-vPc for <ietf@ietfa.amsl.com>; Sun, 14 Jul 2019 12:07:49 -0700 (PDT)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 431AC1200C1 for <ietf@ietf.org>; Sun, 14 Jul 2019 12:07:49 -0700 (PDT)
Received: by mail-io1-xd2b.google.com with SMTP id q22so30775030iog.4 for <ietf@ietf.org>; Sun, 14 Jul 2019 12:07:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=8+wZ1Ay+qzqQEtdyK0o5y3ETwp48Sv43C1b8LflZWCw=; b=DVjCMDAZkLNNZjptyPkr5d22MXArdQgHgD/kh9hnnbS8BNx8UUAJkSzVEEiQ409wsx 3wRpRc31fRDTxjt1V2x8vbgr/0tftm8eNWuvT27wkaUwpGwQHs11hQfHOQcWaHxmVnBu XFi6OMdPMBwVRfB9i6vKB3M0EOWgRLB4NLAFMVxwQzQz07GO4DCGlleTlVMjKENLmCgT wO0XmXEF5yOI1oGvjevqpe+Aiqcdq+h3JUAUg2QxFDI6C14ojMQXflECdNZL4D5VCT/z 9lplgyRKfgIqevdS1ygy4ZjrnWnWsBHed+ETP8be6S6/ip6RsoQOTLuqJ4kAMFb6XNpc eWzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8+wZ1Ay+qzqQEtdyK0o5y3ETwp48Sv43C1b8LflZWCw=; b=WLi/6yIWuloI2FdyH7i9KUsx1b4DSCaHF/M+P1Cv3txfoejFnYL5GjipYhj0VgKviM jcGny21Wwxu58nuPR2xdEEnEdtv9WhLiYEonK6lPW17kgbAkJoNnvOZGHROnjaNO6HPi RTGnrLe9sfEf+HsPB0JLVjNNkiilEK8J8LRq3h8hnhck4egULwPtk8K/Xg3whdlZv+VD OqLrTBHr2qBnKd5SYZDVEOs6t0b5so9b7RzyWWV/wkJCBvrjwI5Qtr+Ov6rmwvHc4VvQ HHwyKig4aBKDddEHl2lvQoPciWH/Wiaj0RvdeNnc3ysa1wu4d3Ly48o8zwVl9t/tLYGT W21A==
X-Gm-Message-State: APjAAAWAVpR27/SbKguvH+qhYHaDQRk9RxCkyArC+JHf/odk6LeEMVsH dGiN8QIdm1Y/qz/Mmwc273FBmgcvtqvKLvv3Ls2Pt1hY
X-Google-Smtp-Source: APXvYqx1yXze4j0kBk099i4a+JU7PCQkp2of7UIJPwI2GqU+GmIDs6r9LgcgZZotHJ91sgzplPwdrf3hsoH2DFr7h4Y=
X-Received: by 2002:a5e:9506:: with SMTP id r6mr10165051ioj.219.1563131268154; Sun, 14 Jul 2019 12:07:48 -0700 (PDT)
MIME-Version: 1.0
References: <CA+9kkMALnyeoMJKOgwZ8QP1G+aeSTSBbu4HXAAxdyhcC0K=mDA@mail.gmail.com> <6.2.5.6.2.20190713065007.0c09c018@elandnews.com>
In-Reply-To: <6.2.5.6.2.20190713065007.0c09c018@elandnews.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Sun, 14 Jul 2019 12:08:50 -0700
Message-ID: <CA+9kkMAbvAdmFAkm5UnsmqWd51KEbFmSE=Jx2pXGUboEm-VYtA@mail.gmail.com>
Subject: Re: RSE Bid Process
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: IETF <ietf@ietf.org>, Internet Architecture Board <iab@iab.org>, rsoc@iab.org
Content-Type: multipart/alternative; boundary="000000000000f9ca1e058da8db4e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/n4M6e--bdaBO4dHqFGGkT_l9PWQ>
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 19:07:52 -0000
Hi SM, 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. Addressing this along with other issues, should be part of any update to the RFC Editor 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. regards, Ted On Sat, Jul 13, 2019 at 7:44 AM S Moonesamy <sm+ietf@elandsys.com> wrote: > Hi Ted, > At 12:02 PM 03-07-2019, Ted Hardie wrote: > > The following is one of the steps in the proposed process: > > >3) After the RSOC finalizes the SOW, it notifies the IAB, which > >requests the IETF LLC issue an RFP. > > > > > >Note: this is not an approval step, just the mechanics of who has > >the token to turn this crank. > > Why are such mechanics needed? > > The process is something for the different committees or entities to > figure out. The statement of work from 2016 overrides Section 2.1.5 > of RFC 6635. This will be the second time that the Internet > Architecture Board (IAB) is unable to follow what is written in the > RFC which it approved. Although it produced a less than satisfactory > outcome, the IAB and the RFC Series Oversight Committee is still > proceeding with it. That does not look like a good idea . > > Regards, > S. Moonesamy > >
- RSE Bid Process Ted Hardie
- Re: RSE Bid Process Terry Manderson
- Re: RSE Bid Process Ted Hardie
- Re: RSE Bid Process Sean Turner
- Re: RSE Bid Process Patrick McManus
- Re: RSE Bid Process Ted Hardie
- Re: RSE Bid Process Michael StJohns
- Re: RSE Bid Process Patrick McManus
- Re: RSE Bid Process Ted Hardie
- Re: RSE Bid Process Michael StJohns
- Re: RSE Bid Process Ted Hardie
- Re: RSE Bid Process Adam Roach
- Re: RSE Bid Process Alissa Cooper
- Re: [Marketing Mail] Re: RSE Bid Process Pei Zhang (联通集团网络技术研究部)
- Re: RSE Bid Process S Moonesamy
- Re: RSE Bid Process Ted Hardie
- Re: RSE Bid Process Stephen Farrell
- Re: RSE Bid Process S Moonesamy
- Re: RSE Bid Process Ted Hardie
- Re: RSE Bid Process Stephen Farrell
- Re: RSE Bid Process Eliot Lear