|
Top posting and in line:
Hi Ted -
Thanks for this outline. However, I'm
not sure that going forward with the RFP before fixing the
structural issues with the relationships between the IAB, RSOC,
RSE and LLC makes sense. Patrick's note is on point.
Unfortunately, figuring out how to fix those relationships,and
getting agreement is probably not possible in the next 2-3
months. Given the small size of the community of
editor/publishers we are going to try and draw from and our
current missteps, my estimation is that we're unlikely to get more
than one bid if that, and that any contract terms we're offered by
a given bidder are going to be much tighter and much more
restrictive on things like IAB/RSOC "management" and
"oversight". There's going to want to be more assurance by the
bidders that independent contractor means "independent". I would
also expect that bidders will want more assurances against
arbitrary termination of the contract.
Considering all of the above, let me
make an alternate proposal. First that we ask back the previous
RSOC in place of the current group and ask them to serve until we
resolve the issues with the various relationships (e.g. the next
publication of 6635 as a community - not IAB - document). We give
them the responsibility for running the bid process and for the
ultimate selection of the final candidate with the advice and
agreement of the LLC. We use the existing SOW to the greatest
extent possible. We mostly divorce the IAB from the RSOC/RSE
until the relationship issues are resolved - note that may require
a contract modification with the RSE at some point.
The previous RSOC does have experience
with this bidding process which should mitigate some possible time
sinks in getting up to speed.
More inline - applies even if we don't
take the above suggestion.
On 7/3/2019 3:02 PM, Ted Hardie wrote:
As folks are aware, there is ongoing discussion on Heather’s decision not to continue as RFC Series Editor (RSE) and about how the situation has been handled. Firstly, we’d like to express our regret at how things have transpired and our willingness to have an open discussion with the community about where we can all best go from here. This mail sets out our view of how recent events unfolded, and our understanding of the process for finding the next RSE.
The RSE currently has a two year contract which began in 2018 and which permitted two extensions of up to two years each. As part of their duties under RFC 6635, the RFC Series Oversight Committee (RSOC) reviewed the contract in May of this year. On June 6th, they notified Heather Flanagan, the current RSE, that they would recommend the contract be extended for two years. At the same time, they noted an intent to prepare a Request for Proposals during that two year period, in order to address some concerns that were raised about response rates after the last bid process. Immediately afterwards, the RSOC notified the IAB both of their recommendation to renew the contract in 2020 and their intent to prepare an RFP for 2022.
Initial discussions within the IAB would normally have been held at the following IAB meeting, on June 10th. On June 7th, however, the RSE notified the IAB, the IETF LLC Board, and RSOC that she did not intend to renew the contract. The IAB is grateful that she provided early notice and that she has agreed during the remaining months of the existing contract to help the RSOC and IETF community to consider the requirements needed for the next RFC Series Editor.
Discussions on the requirements are ongoing on the IETF list. While we expect additional community discussions of future processes or models, we also want to take advantage of the time Heather’s courtesy provided as best we can. As a result, we believe we should begin the RFP process as set out in RFC 6635 now, with an aim to getting an RSE and a contract in place with sufficient transition time. Since the last running of this process, the IAOC has concluded and the IETF LLC taken shape, so we wanted to lay out to the community our understanding of that process with the IETF LLC in place. As with other aspects of the IAOC to LLC transition, the RSOC and IAB will aim for minimal change to the current process, and zero unexpected changes. That would give the following steps:
0) The RSOC prepares a short paper on how a
succession plan for the RFC editor might work, and how
recruiting in this space might work. That paper needs to cover
what happens if the RFP fails to receive even one bidder.
1) The RSOC prepares a statement of work based on RFC 6635 and previous RFPs.
2) The RSOC sends the SOW out for public comment.
If IAB members, the IAB, or the IETF LLC board have comments, they occur during this period. There is no separate review for them.
3) After the RSOC finalizes the SOW, it notifies the IAB, which requests the IETF LLC issue an RFP.
Instead, the RSOC provides the SOW to the LLC which turns it over
to the lawyers.
Note: this is not an approval step, just the mechanics of who has the token to turn this crank.
4) The RFP is issued by the IETF LLC.
5) The RSOC, or a committee formed from within the RSOC, reviews the proposals and interviews candidates. Depending on the number of candidates this could involve steps for creating a short list before running interviews.
This is the one that bothers me the most. Given the
missteps its unclear this is the right group of people to be
picking the next RSE. Instead, pick a search committee (as
described I think in the previous SOW), consisting of folks that
have at least a little knowledge in the publication/editing
space. These don't actually need to be IETF participants
especially if the SOW is tightly written.
6) The RSOC recommends an appointment to the IAB.
7) The IAB approves the appointment, subject to contracting.
Here's another possible issue. It's unclear that
the community and the IAB/RSOC are aligned with what they want
as an RFC editor. I'm not sure that will matter in the end
especially if we get only one or two bidders.
8) The IETF LLC negotiates a contract with the appointed RSE.
9) After timing is agreed, the new RSE is announced and a transition begins.
Once again, we regret how things have transpired and will be engaging with the community on the longer term handling of how the IAB, RSE and IETF relate to one another. That may include a new version of RFC 6635. Until those conclude, however, we believe we need to move forward with the current process. As part of that, we want to confirm with the community our understanding of the process required under the existing model and procedures.
If you have comments on this point, please send them by replying to this mail or to iab@xxxxxxx and rsoc@xxxxxxx. Note that both lists include the current RSE as a member. If you have comments on the SOW, e.g., on appropriate length or renewal intervals, please send them to RSOC after the SOW has been published for community review. For comments on the broader situation, the ietf@xxxxxxxx list is, as always, available.
As an immediate structural change, we need either the IAB or the
RSOC, not both, to have their fingers in the RSE pie. If that's
the RSOC, then it should probably be selected by the community,
not by the IAB.
Later, Mike
Regards,
Ted Hardie
for the IAB
|
