Re: RFC Series Editor Resignation

[Brian E Carpenter <[e-mail]>]

Mike,

> I'm unclear why they are making the decision on renewal without 
> community input

I think this is a key issue. I completely agree that the community
should not micro-manage either RSOC or IETF LLC in this matter. However,
community input on how the RFC Series is working and what needs to
be adjusted would be the obligatory first step, IMNSHO.

Regards
   Brian Carpenter

On 20-Jun-19 02:45, Michael StJohns wrote:
> 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
>>> [e-mail]
>>>
>>>> On 19/06/2019, at 16:46, Brian E Carpenter <[e-mail]> 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
>>>>> [e-mail] <mailto:[e-mail]>
>>>>>
>>>>>> On 19/06/2019, at 14:52, Aaron Falk <[e-mail] <mailto:[e-mail]>> 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
>>>>>>
> 
> .
>