Re: RFC Series Editor Resignation

Michael StJohns <mstjohns@comcast.net> Wed, 19 June 2019 14:45 UTC

Return-Path: <mstjohns@comcast.net>
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 642A712021C for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2019 07:45:42 -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_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 my9pLH7xgkEr for <ietf@ietfa.amsl.com>; Wed, 19 Jun 2019 07:45:40 -0700 (PDT)
Received: from resqmta-ch2-05v.sys.comcast.net (resqmta-ch2-05v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C14F71204A8 for <ietf@ietf.org>; Wed, 19 Jun 2019 07:45:33 -0700 (PDT)
Received: from resomta-ch2-06v.sys.comcast.net ([69.252.207.102]) by resqmta-ch2-05v.sys.comcast.net with ESMTP id darOhsJ92jKaudbq8hY630; Wed, 19 Jun 2019 14:45:32 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1560955532; bh=U/5fEPlfXDxf2Du6tsKPPMYz1BvkiwAqpFu3FJr7ywQ=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=O0wDz64u0kaUc8rv40ZxXSEzuWgwcwNZAIrrVGECGYWaOsxOehAWjY/00N/CpHZBV a/XTl2yafk2vjz5gi6sKSZsaLPfJEGk//MwvFEPVSE8w4eNR1PqNvLSgRzgv+EH0NI c3XWc0UKb/zVItaoO4jMA0e8XQsC488NESGLYfod8/h42zpUAL63yiQ76mAyRWb5ML jRWffB8B0xHvtkfaen4bDmYDxApHmPJA1QJVDW2yhh08tWzYdmjEUxeS7QoQYkapvm n/65jhGPtgL+pigEr4NwB2EUWX9GJV3IhG4H7cjjB38UtDuWVkgdX/XarnWSYzOhUq TKpyvFijxZcwA==
Received: from [IPv6:2601:152:4400:437c:70c6:5a3f:8c95:727b] ([IPv6:2601:152:4400:437c:70c6:5a3f:8c95:727b]) by resomta-ch2-06v.sys.comcast.net with ESMTPSA id dbq7hLEXxj6gwdbq8hp260; Wed, 19 Jun 2019 14:45:32 +0000
X-Xfinity-VMeta: sc=0;st=legit
Subject: Re: RFC Series Editor Resignation
To: ietf@ietf.org
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>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <f4dd608d-aeb9-84ac-e879-50dc7cac3736@comcast.net>
Date: Wed, 19 Jun 2019 10:45:31 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <cdcaf342-618a-c148-6864-59b4f8ee7f6b@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vXbEmPDjO4NHzDhQPRUTwUZpco4>
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 14:45:43 -0000

On 6/19/2019 1:24 AM, Brian E Carpenter 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.

Especially doing so 2.5 years in advance.   That seems to be a bad 
business practice to lock yourself (or your successors actually) into a 
set of actions 2 years into the future.    And seriously, I've done 
dozens of RFP like actions over the years during my time with the US DOD 
- there's not a lot of "refining" that needs to be done, or that can't 
be done during the process of the RFP (clarifications and precisions 
process).

Hmm.  What do the LLC minutes say about this?  Where would we look?

And nominally, the IAB gave themselves oversight over the RFC process 
with their original charter, but we've since gone through the IAOC and 
LLC processes.  Given that neither the IAB nor the RSOC is a contracting 
entity, I'm unclear why they are making the decision on renewal without 
community input to the LLC?

Later, Mike


>
> 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
>>>>>