Re: RFC Series Editor Resignation

Alexander Neilson <alexander@neilson.net.nz> Wed, 19 June 2019 08:00 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 5D7BD12002F for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2019 01:00:08 -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 56Qun47d4iVp for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2019 01:00:06 -0700 (PDT)
Received: from mail-pl1-x641.google.com (mail-pl1-x641.google.com [IPv6:2607:f8b0:4864:20::641]) (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 78502120408 for <ietf@ietf.org>; Wed, 19 Jun 2019 01:00:04 -0700 (PDT)
Received: by mail-pl1-x641.google.com with SMTP id cl9so6856408plb.10 for <ietf@ietf.org>; Wed, 19 Jun 2019 01:00:04 -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=/IA+PQiuRm1+DasrufD1FTD6kXINO8L49ISdtnc84ZY=; b=AWfgyiaEnH5DiwcTMwefyBJpPOJeDpBFe/cYyyVIHX+DaXLZc8Z8WFivL+n2RcUaAY E+eVnh9tSBgP2GmdqLauzn5u3FRwlGlQlyEakltcBYgz/X2h7IIDw0M5Z2tC8RQ/6lM5 eUDErIULQ72E/SbviF+w0BWloFZMKC1vurXIYZbDrf6G5KxDsUcGi4JpDhmp2wpo99/w anKU/0Z2SPOYbBjGcVRMlFEd37i8gCN06mlCXkNer0LwwPVfrhezUxuldaI66xUflK6i 3EUNB4MZXhobRnS413hn6aEYauhcPxQYp6sWPmBo+NntMCIpcrgAZ5syRWnRkVUobXZb 9K2w==
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=/IA+PQiuRm1+DasrufD1FTD6kXINO8L49ISdtnc84ZY=; b=lVTYMyDDsFwWzfBl31ltuXJX3R9KQbf03z6PyJhg7ANczjqeWBIxKjovunnCnLKU/e pc5ViKhw8Pb4OKcP6jNTKigCOXapLMSpbOUsoplRgTRO6liCAKy46CSAfMMzy5G/HCO5 cPZTkTa2CX91kQmD09rd60VuaOdYZVTi/kZJaCwZt/JCeSXzm7qLFvOkI2XiSsDynxtp IZZqGbylA6ALFKGSDdJGnQgC6kW2Mt9glNy7SVLanyzr+82gsgjzOCZas5GRbgDzyGOH QMkkdAPK9aWClt3W/Urlvv2er5iQoODUhV3esaojyrxoZQZY9qigh9LM/v1uzJpj+4Xj yK8A==
X-Gm-Message-State: APjAAAWdVzomqQKYAbM5vbJH6dX4fWrE/TCP2D52pF1/r7AQ4Sffpnbr MmZiNj1R73PZEqUJyxDjxzvUrg==
X-Google-Smtp-Source: APXvYqyT6qaHP9OaTpQyWoHC0qkXzgyk/UTbYoBMdbPBMiSzMpcRI9N752bUPkT1D2F04mDsVy8Gvg==
X-Received: by 2002:a17:902:3225:: with SMTP id y34mr518352plb.135.1560931203856; Wed, 19 Jun 2019 01:00:03 -0700 (PDT)
Received: from [10.250.0.60] (house.neilson.net.nz. [45.118.188.13]) by smtp.gmail.com with ESMTPSA id c26sm627395pfr.172.2019.06.19.01.00.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Jun 2019 01:00:03 -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: <cdcaf342-618a-c148-6864-59b4f8ee7f6b@gmail.com>
Date: Wed, 19 Jun 2019 19:59:58 +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: <4958FD15-3070-48AB-A78B-00DC767E44E9@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> <989B1B67-78B4-4CF3-BDD7-701F297880D3@neilson.net.nz> <cdcaf342-618a-c148-6864-59b4f8ee7f6b@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZQe6HLIDzojFWfGBGz-CSVoOMho>
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 08:00:09 -0000

If that is the decision made then one partner to a business relationship telling the other their intentions is not unusual for business people. 

Business thrives on certainty and holding back on telling the other party so they can plan with plenty of notice seems likely to cause more damage to the relationship. 

Especially if the next stage was to publish the terms of reference for the review including what they think needs to be looked at particularly and their proposed plan (including timeline for concluding the review, implementing the changes - which may have included putting the contract out to tender anew). Then this next step would be very negative having not told the other person the plan before they find out from third parties. 

Regards
Alexander

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

> On 19/06/2019, at 17:24, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> They seem to have pre-announced there would be no second renewal. That is not a normal way of doing business, to my mind.
> 
> Regards
>   Brian Carpenter
> 
>> On 19-Jun-19 17:19, Alexander Neilson wrote:
>> 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
>>>>> 
>>> 
>> 
>