RFC Production Center management transition

IETF Executive Director <exec-director@ietf.org> Sun, 05 January 2025 23:34 UTC

Return-Path: <jay@staff.ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F20BC23AE4E for <ietf-announce@ietfa.amsl.com>; Sun, 5 Jan 2025 15:34:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=staff-ietf-org.20230601.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VWQjmzZHmBL4 for <ietf-announce@ietfa.amsl.com>; Sun, 5 Jan 2025 15:34:38 -0800 (PST)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5779C331E00 for <ietf-announce@ietf.org>; Sun, 5 Jan 2025 15:30:54 -0800 (PST)
Received: by mail-pl1-x62b.google.com with SMTP id d9443c01a7336-2166f1e589cso239178975ad.3 for <ietf-announce@ietf.org>; Sun, 05 Jan 2025 15:30:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1736119853; x=1736724653; darn=ietf.org; h=to:date:message-id:subject:mime-version:content-transfer-encoding :from:from:to:cc:subject:date:message-id:reply-to; bh=Ueq4r4zWKXaAv8WSVWAqeYSlYvdbMs4Vx0XjZsnICk4=; b=Rw2fiDULyKWlP36zlvO0Lp4jP5RTHXMNl/W8BPpNnhcZqcTin/2uOLMcfmwWg4nQQi 2zwYI//L00gnmfbV92t2Tm6xgCnGKWS5RO6m1ebxaQhJfF0NkhXKWj78LIYASrSycd0k QApDcIGkwrOtfABmNaqiYuiO+66K2XJdFgP8L+yoy4+5REzUVhWYRVSbWQNJ7S4Q2jr5 hJ6NfaRvlT67mDhUXiMNQIae9U3mmPbVcliO9PRmwQNkEOL8mGBZF90NorWQAfODIaQa wjRNnlp81xeUPXuXy0EB4IkIRPYac0fZxMLEiKAalH1a5b0ZcD6MWUxw7LnyG3FxJ4HB ZL0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736119853; x=1736724653; h=to:date:message-id:subject:mime-version:content-transfer-encoding :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Ueq4r4zWKXaAv8WSVWAqeYSlYvdbMs4Vx0XjZsnICk4=; b=O2ZD1BFsVN9mtJ23Sjj9FzEkKzXIm1XFxuKj9WDeFNdseWxTs8+lVz8rX54GilyLKi x8K62nOOqowbSLHntAUAms4Ah/g+WVE0yew+kU06LWAL5O6sV4GhkFVArwzTQf/TfRoZ CTILO/gh4DApnOHyt8kRdzJV+J4iqml3TeDz4XgIYNtG77TUWwDmo1dKqRiRcjlFGLBD k+BB63fqIuxZmNmSyXSqDnzHcZ2y7wNPjFX77HnCRA48MUYlr0USxMZQ2p7zIhNmAgox m+jsphtLKdX8mXJfaIvo7Ay4vxGEKJTqBWC5OjViTtjtE8xdk2w8/7lQbMQaeiR8XrHt REIA==
X-Gm-Message-State: AOJu0YxKfN42e2vFcACAH0v+P864kCfsB8lLwtze8abUU+O86HrYGUJf PJ9GWImzHpzhIONLBb92YdV+RKqzuOdeqMro2pz0upI3LKg5lipPo2Dg0VZevrVf2F42EQDVj7R 2jxTce22k
X-Gm-Gg: ASbGncvAQLSwwGiT6AvrkHh6KmbHhNSooRfZ+5t8V9rYJGhjg8vn7LXhfMogJQ2u7po 8v759V+okfRmt8xQQnfa5WgNtAeSobZFnov3bB8ArOFYYgweObrZcEsLKm+weuN8zWZqFs+IRgR vpS0EmjLaRYivQolaXIDx5eUPrppa9uD2R4kwtFvQsLwNRSeXh3NvD7f5e0BaXgWJtM6F31q6eT vcZLTGoZPyUxljPhpdH3Ft9O0l3J31PBhw3Y+3L8qNlq/drl5gkzGdIjgwYajPsqRN6jj61o5w7 XupOCzGKYy05r0DJ8ZCOG7MthKvrk5w3CJc1sVUod/BaDWtoYtA=
X-Google-Smtp-Source: AGHT+IFtjFUmeenY4OhhhB6jFjhyG8ro+4366cuWeHdk/RnAzrTA3VyKBw3IggH81WcO+AbpYmal4w==
X-Received: by 2002:a05:6a20:e68c:b0:1e1:ab03:8653 with SMTP id adf61e73a8af0-1e5e043f509mr96862323637.9.1736119853066; Sun, 05 Jan 2025 15:30:53 -0800 (PST)
Received: from smtpclient.apple (203-96-137-90.dsl-dynamic.connections.net.nz. [203.96.137.90]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-72aad8fd820sm30081208b3a.170.2025.01.05.15.30.51 for <ietf-announce@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 05 Jan 2025 15:30:52 -0800 (PST)
From: IETF Executive Director <exec-director@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.1\))
Subject: RFC Production Center management transition
Message-Id: <A27631DB-55DE-4B2F-8974-0150D65C6965@ietf.org>
Date: Mon, 06 Jan 2025 12:30:39 +1300
To: ietf-announce@ietf.org
X-Mailer: Apple Mail (2.3776.700.51.11.1)
Message-ID-Hash: O5J52ZIKSSM7LSC5OVPHRJQEISFOSYW3
X-Message-ID-Hash: O5J52ZIKSSM7LSC5OVPHRJQEISFOSYW3
X-MailFrom: jay@staff.ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/fb3tUA760X4KWRkRQZJ5nonJ95Q>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

After an extensive review of recent developments in the RFC Editor function, the IETF Administration LLC (IETF LLC) and Association Management Solutions LLC (AMS) have agreed that the IETF LLC will assume management of existing RFC Production Center (RPC) staff, under an Employer of Record arrangement with AMS, the employer of the RPC team.

# Background to the RPC

The RPC is the team of professional editors that prepares and publishes the output of the Editorial, IAB, IETF, IRTF, and ISE Streams, which make up the RFC Series. Once Internet-Drafts are approved by the various streams, the RPC editors format and edit the documents, and then work with the authors to produce publication-ready RFCs per defined policies and guidelines.

The RPC has been hosted at several organizations since it began, including ISI/USC, CNRI, and most recently AMS on contract to the IETF LLC.

# Need for change

The RFC Editor function has been going through a period of major developments for the last two to three years, and this is likely to continue for at least another two years. These developments include the introduction of XML, the new RFC Editor model in RFC 9280 that introduced the RSWG/RSAB and removed the RSE role, the RPC tools modernisation, the ongoing requests for GitHub and Markdown editing, and the need to develop a new SLA. 
These developments have brought the RPC closer to the IETF community by giving it more responsibility for editing decisions, more direct contact with community members who want different services, and more direct community reporting requirements.  Ultimately, these developments acknowledge the integral and vital role of the RPC, but they have put the RPC leadership in a difficult position as arms-length contractors. 

# Changing how the RPC is managed

After an extensive review, the IETF LLC and AMS have concluded that the best way to address these issues is for the IETF LLC to assume management of existing RPC staff, under an Employer of Record arrangement with AMS, the employer of the RPC team.  This arrangement will allow the IETF LLC to directly manage RPC strategic direction, evolution, training, and resource allocation, while ensuring that RPC staff retain the stability of the AMS home which they have enjoyed over the past 15 years. This employment arrangement is in line with how most of the LLC staff are employed, including the Executive Director, not as direct employees of the LLC but contracted through a professional services firm. 

This will provide the RPC with the alignment and authority needed to address these developments and so help to ensure the RFC Series continued evolution and stability while providing management oversight and appropriate resource allocation. 

While the IETF LLC and AMS were conducting this review, AMS was also reviewing the internal management of the RPC and the distribution of the increased workload.  AMS, the IETF LLC, and the staff concerned have agreed to introduce a new management structure for the RPC, starting at the same time as the transfer. This sees the role of Director, RFC Production Center split into two; Director of RPC Operations and Director of RPC Communications and Strategy.

# Change to cost structure

The new arrangement with AMS is forecasted to provide a cost savings due to the transfer of management responsibilities to existing LLC staff. 

# Implementation

The change is effective from Jan 1, 2025.

-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org