Re: RFC Series Editor Resignation

Alexander Neilson <alexander@neilson.net.nz> Wed, 19 June 2019 05:19 UTC

Return-Path: <alexander@neilson.net.nz>
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 A247C12004F for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2019 22:19:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=neilson.net.nz
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 TF0Xd9_NFaua for <ietf@ietfa.amsl.com>; Tue, 18 Jun 2019 22:19:19 -0700 (PDT)
Received: from mail-pf1-x441.google.com (mail-pf1-x441.google.com [IPv6:2607:f8b0:4864:20::441]) (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 D2448120235 for <ietf@ietf.org>; Tue, 18 Jun 2019 22:19:16 -0700 (PDT)
Received: by mail-pf1-x441.google.com with SMTP id i189so8998053pfg.10 for <ietf@ietf.org>; Tue, 18 Jun 2019 22:19:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neilson.net.nz; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=E1frb0FpYLsSktnsOBV1X6r5ATsH1aFkJY+3r019JN8=; b=gYoseVxQECUVsEkjstkjUY/HdJ/z39TFCYRuv0509qcvCA8GUidyOl9jTNtikWIFEA 88b/UfhK711rE2L1I4K0pO8/MoGjp9CHLdFohYCEMbtmMT4TbBM2HgV+vMAyBRR0pca8 Hy7mwAQJz8s+ijTW9L/EqYdqddTHVaGys4rQ/1rIrhvwSeIASg6VZ4ZD52azIYZ+Yb3L EV3pqJdoWi5JvSM2t7/Z3hNgAJhkkpNjMprcFPF/wYv5LkcYa3aeRRprP/zU5S2+RlWd Jx0jWF5uw0a4qVKlnDs9n47jdYPiRxSdcy20dZri0mlOAR8kiaI65B7mKUsvDSNEZ5fE 5n7A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=E1frb0FpYLsSktnsOBV1X6r5ATsH1aFkJY+3r019JN8=; b=DobDFfIQ+78icPMnJwseQr+cbJVFw9yqlnAEfVz9GKy5HtHwgc/WkR4cDFsOuAHySl u6ekuonWjhdCZ/cY9eZ2WSHTnIia91BysqOvb0Desg3MyWtjyPprpMRLzoyXsv7MviuX 1kO0q1ro3vxnvwATsG0gECnol2WHYqPpYEDOjQQKSyIQozEsQ3KI+P5CZFMcUZ0tPrUb 5VuVO2vDs1NK1buP7ARJp+CbK70Oo8gKnprgFz+B7uteHu+6h5yqleUMWK4skxbZcl9J ASD6XSKWhccHOS9zpBdU52/SWv47pjmmQlqZCz54GSumLn0jZyqljybPixZ5c9LJoPJ3 8zyw==
X-Gm-Message-State: APjAAAX9Rvjg+d+yFfo24uKTKY68snAj8mjnIEr+cR3j3g5nTkFiVELf oGLBNBE4bCZtR6gM6K3Szktxm4Qc7hJg7Q==
X-Google-Smtp-Source: APXvYqwUe9GrsPTIXaF8s8Rdw94JcmiY4UX+y6I7BOdCb4zXL7+N/HJ5CpUDd/zDf+ANpeIvSaMNvA==
X-Received: by 2002:aa7:8108:: with SMTP id b8mr8618135pfi.205.1560921556129; Tue, 18 Jun 2019 22:19:16 -0700 (PDT)
Received: from [192.168.8.38] (gl-ex01.internal.gl.co.nz. [45.118.188.115]) by smtp.gmail.com with ESMTPSA id 30sm1224946pjk.17.2019.06.18.22.19.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Jun 2019 22:19:15 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
Subject: Re: RFC Series Editor Resignation
From: Alexander Neilson <alexander@neilson.net.nz>
X-Mailer: iPhone Mail (16F203)
In-Reply-To: <e4251435-b786-4bb4-0065-c76bc96f1eeb@gmail.com>
Date: Wed, 19 Jun 2019 17:19:10 +1200
Cc: Aaron Falk <aaron.falk@gmail.com>, IAB Executive Administrative Manager <execd@iab.org>, LLC-Board@ietf.org, IETF Discussion <ietf@ietf.org>, IAB IAB <iab@iab.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <989B1B67-78B4-4CF3-BDD7-701F297880D3@neilson.net.nz>
References: <685B34F6-E0E2-4050-B9DD-615F475F62B7@encrypted.net> <58D30A55-FB45-476B-997F-1D9D58E89AE0@gmail.com> <A24BDAB9-B118-4A8A-A6DF-D2094ABF3E33@neilson.net.nz> <e4251435-b786-4bb4-0065-c76bc96f1eeb@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1ur9d43iZCQlYIBviqAiAG3x4v0>
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: Wed, 19 Jun 2019 05:19:22 -0000

Hi Brian

Just to quibble on one point. 

The term is for two years with two possibly extensions if mutually agreed. 

So in this case it sounds like the intention was signalled to take up one renewal option by one party and the other decided not to take a renewal. 

I don’t think it is any signal of unreliability. The term itself is almost at its conclusion. The contract considered an option to extend which has not been taken up. 

Regards
Alexander

Alexander Neilson
Neilson Productions Limited
021 329 681
alexander@neilson.net.nz

> On 19/06/2019, at 16:46, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> Well, I'm confused too. It's not as if the house was burning down, except that now it is.
> 
> What Sarah's message didn't make quite clear is that the 2021 re-bid would be two years early, given that the full term of the current contract ends 6 years from 1/1/2018. (https://iaoc.ietf.org/documents/RSE-2018-Independent-Contractor-24Oct17-Public.pdf,
> Clause 3 "TERM"). In other words the RSOC and/or IAB had already decided to truncate the contract. This makes us (legally personified as IETF LLC) look like an unreliable business partner.
> 
> So what precipitated this disruption? From my point of view, everything was running well, even if occasionally some nominal target numbers were missed; it's great to have a series editor who actually has appropriate professional knowledge and experience, unlike all her predecessors. So the decision to prematurely run a bidding process seems to have been a really bad idea. Something about ain't broke, don't fix. The attempted fix has apparently caused serious breakage. This deserves a transparent explanation to the community.
> 
> The phrase "expressly for the purposes of refining our RFP process" literally makes no sense to me as an explanation for breaking off a satisfactory contract. If there's something wrong with our RFP process, we seem to have thrown away almost all the time available to improve it, given that the normal date for the rebid would be sometime in 2023. That seems like the exact opposite of what the community needed from the RSOC and the IAB.
> 
> Regards
>   Brian Carpenter
> 
>> On 19-Jun-19 15:55, Alexander Neilson wrote:
>> I may be wrong but I read it as meaning a renewal of the current contract to allow time to refine the process and that new process would be the structure the RFP for a new contractor went out under. 
>> 
>> Regards
>> Alexander
>> 
>> Alexander Neilson
>> Neilson Productions Limited
>> 021 329 681
>> alexander@neilson.net.nz <mailto:alexander@neilson.net.nz>
>> 
>>> On 19/06/2019, at 14:52, Aaron Falk <aaron.falk@gmail.com <mailto:aaron.falk@gmail.com>> wrote:
>>> 
>>> I’m not sure whether my question below should be addressed to the RSOC, IAB, IETF Exec Dir, or IETF LLC, so maybe one of them will enlighten me.
>>> 
>>> Regarding
>>> 
>>>    Although the RSOC had recommended renewing the RFC Series Editor (RSE) contract for another two years, and then put the contract back out to bid in 2021 expressly for the purposes of refining our RFP process
>>> 
>>> I’m wondering what exactly it means to put a contract out to bid “to refine the RFP process”. For example, is someone bidding on the RSE contract supposed to assume they are just providing information and not actually going to be a candidate for the award? (Is that even legal?) Or, should we presume that this is an actual competition for the RSE work? I can’t understand how you can solicit bids for the RSE but say is is just to refine the process. Can someone explain this curious wording?
>>> 
>>> If the goal is to replace the current RSE, perhaps someone can explain why.
>>> 
>>> --aaron
>>> 
>